Before the next material technology proposal reaches a decision, ask whether each director can explain what management wants to do, why it matters, and what could change the recommendation. Use the answers to identify the explanation still needed.
This is a practical way to focus director learning on a live choice. The aim is shared understanding sufficient to examine the proposal, including its limits. Directors may disagree about the right decision while understanding the same underlying assumptions.
COSO’s Corporate Governance: Guiding Principles for Board Oversight discusses continuing director education and a shared knowledge base on page 18. Its introduction describes the guidance as directional and adaptable to the organization, with day-to-day operations remaining with management. Those are useful boundaries for the exercise below. The proposed briefing is our editorial recommendation, not a COSO requirement or a tested measure of board effectiveness. Read COSO’s guidance.
Start with the decision the board actually faces
Ask management to open the paper with the specific choice being brought forward. Identify what requires board consideration under the organization’s existing arrangements and what management can decide within its authority.
For example, a proposal might concern expansion of an AI-assisted customer service pilot. The paper should state whether the board is considering an investment, a change in risk appetite, or another reserved matter. Avoid presenting every technical configuration choice as a board decision.
Then ask for a short briefing built around four questions. Keep supporting technical material available for directors and advisers who need to examine it.
What benefit is intended
Request a description of the operating problem in everyday language. What happens today? What would change? Who would experience the improvement, and how would management determine whether the expected benefit has appeared?
For the hypothetical customer service pilot, “improve efficiency” needs more explanation. Does management intend to reduce waiting time, help employees locate information, or handle additional requests? Ask which of those outcomes supports the recommendation and what evidence is available so far.
Separate observed results from forecasts. Where the business case relies on an assumption, name it. Ask what comparison management used and whether a simpler option has been considered. The briefing should leave directors able to explain the proposed benefit without borrowing the vendor’s language.
Who is affected
Ask management to describe the people whose work or experience would change. Include the employees expected to use the system and the customers who may encounter its outputs. Consider whether a person affected by a decision has a practical way to ask for help or correction.
In the pilot example, ask what a customer would experience when an answer is incomplete, and what the employee handling that case would be expected to do. Follow the proposed process far enough to understand who carries the additional work.
Treat these as questions to investigate. Do not assume that the existence of a help channel establishes that it works for everyone who may need it.
What remains uncertain
Invite management to distinguish what it has tested, what it expects, and what it cannot yet conclude. Ask which uncertainty is important enough to affect the decision now.
A pilot briefing might leave questions about unusual customer requests, the quality of source material, or the staff time needed to check outputs. These are hypothetical examples, not findings about a particular system. Request the evidence relevant to the actual proposal and an explanation of where that evidence stops.
Give directors room to identify unfamiliar terms. Ask for an operating example when a definition alone does not explain the consequence. Record an unanswered question plainly rather than replacing it with a reassuring label.
What would change the recommendation
Ask management to identify the evidence or conditions that would lead it to narrow, delay, revise, or withdraw the proposal. Specify who would reassess the recommendation and when the matter would return through the appropriate governance route.
This question can be used before approval and at a later review. For the pilot example, ask which unresolved issue must be addressed before expansion and what evidence would demonstrate that it has been addressed. Avoid adding a threshold merely because it looks precise. Ask management to explain the basis for the threshold it proposes.
Use the remaining questions to focus specialist advice
After the briefing, invite directors to explain the choice in their own words and identify what they still need to understand. Use that discussion to define the question for a relevant technical, operational, legal, or other adviser.
Ask the adviser to state the scope of the work, the evidence examined, and the limits of the conclusion. A narrowly scoped review should not be presented as approval of the whole proposal.
Close with a concise record of the decision, any unresolved question, the person responsible for the response, and the next review point. Fit it into the records the organization already uses.
A plain-language briefing does not establish legal compliance, technical safety, or future performance. Its immediate purpose is to make the reasoning behind one decision easier to examine. Start there, and judge the briefing by the questions it helps the board resolve.
For concise Board Reviews and research that help directors prepare informed questions, explore Touch Stone Executive Intelligence Membership.