The Director's Technology Questions for the Year Ahead

Ask directors what holds them back from technology oversight and the answer is usually some version of "I am not technical." It is a misplaced worry. Oversight was never about understanding the machinery; it is about asking the questions that keep the machinery honest.

Five questions, asked consistently through the year, are most of the job. None of them requires knowing how anything works. All of them require the discipline to keep asking when the answers get slippery.

Key takeaways

• Technology oversight is a questioning discipline, not a technical one.

• What would hurt us most? The crown-jewel question anchors everything.

• What are we relying on that we have not tested? Assumptions are where risk hides.

• What changed since last quarter? Change is where oversight belongs.

• What do you need from this board? Oversight is a two-way obligation.

The Five Questions

What would hurt us most?

Every other question hangs off this one. If the business cannot name the two or three systems, data sets or relationships whose loss would genuinely wound it, no amount of monitoring or reporting produces oversight.

Ask it at the first meeting of the year and listen carefully to whether the answer has changed. A business whose crown jewels shifted, a new platform, a new dependency, without the protection shifting too, has found its year's theme for you.

What are we relying on that we have not tested?

Backups everyone assumes work. The recovery plan nobody has walked through. The vendor who would surely tell us. Every business runs on a layer of untested assumptions, and this question is the polite way of lifting the corner of the rug.

Ask it quarterly and the answer gradually shrinks, because management starts testing before you ask. That is the question doing its job.

What changed since we last met?

Not the metrics; the change. New systems, new vendors, new people with powerful access, new features switched on by default. Risk lives in the delta between meetings, and this question is how a board tracks the delta.

The answer should be short and specific. A quarter in which nothing changed is either a very quiet business or an answer that did not get prepared.

Who is watching, and how would we know?

For each thing that matters, someone should own watching it, and the board should know the shape of that arrangement. Not the technical detail; the accountability. Who notices when the backup fails, and how long between failure and notice?

Newer directors can build this muscle quickly, and the onboarding rhythm in a new director's first 90 days is a good place to start.

What do you need from this board?

The closing question, and the one directors ask least. Management sometimes needs a decision, air cover for an unpopular fix, or simply the board's patience while something gets done properly. An oversight relationship that only flows one way gradually stops flowing.

Ask it genuinely and mean the answer. The board that can be asked for things is the board that gets told things, and being told things is the entire foundation of oversight.

Frequently asked questions

Do we ask all five at every meeting?

The first and the change question, yes. The others rotate through the year, so the answers stay fresh and the meeting keeps its shape.

What if the answers are vague?

Vague answers are findings. Ask once more, plainly, and if the vagueness persists, that is a reportable oversight observation, not a failure of the director.

Should these go in the minutes?

The questions and the substance of the answers, yes. A consistent record of good questions is evidence of oversight, and it protects both the board and management.

A practical next step

Take the five questions into the year's first meeting, in writing, and ask them in order. If the answers reveal an oversight relationship that needs rebuilding, a Decision-Clarity Call is a good place to start.