8 questions every board should ask before approving a strategic initiative

Approving a strategic initiative commits the organisation to a view of the future, a use of capital, and a level of risk that the board must be able to defend. 

Most boards recognise this in principle. The harder question is whether their approval process gives directors enough time, evidence, and space to challenge management's recommendation properly. A proposal may arrive after months of internal development, with a confident business case and a clear executive sponsor. By the time it reaches the board, momentum may already have formed. 

That is where scrutiny can become too narrow. Directors may test the numbers, ask about risks, and approve the paper, without fully examining whether the initiative fits the agreed strategy, whether the assumptions are resilient, or whether the organisation has the capability to execute. 

John G. Smale, former chairman of General Motors, put the accountability point plainly when he wrote that "The board is responsible for the successful perpetuation of the corporation. That responsibility cannot be relegated to management." 

The eight questions below are designed to help boards make approval decisions with more discipline. They are not a compliance checklist. They are a practical framework for turning a management proposal into a board-level decision. 

8 questions boards should ask before approving a strategic initiative 

The questions move from strategic fit to execution, risk, accountability, capital, information quality, and security. Used well, they help the chair structure a discussion in which challenge is specific, constructive, and tied to the board's oversight responsibilities. 

1. Does this align with our agreed strategic direction? 

The first question is whether the initiative executes the strategy the board has already approved, or whether it changes that strategy by implication. 

This distinction is easy to miss. Management may present a proposal as a natural next step, when it actually introduces a new risk profile, a different growth model, or a material shift in capital allocation. A European manufacturer that has agreed to prioritise margin improvement, for example, may later be asked to approve an acquisition aimed primarily at market share. Both objectives may be defensible. They are not the same strategy. 

Directors should ask whether the initiative would have been predictable when the strategy was last agreed. If not, the board may need to revisit the strategic direction itself before considering approval. 

The OECD's corporate governance principles state that key board functions include "Reviewing and guiding corporate strategy, major plans of action, annual budgets and business plans." That framing is useful because it places approval decisions within the board's wider responsibility for strategic direction. 

A strategic departure may still be the right decision. The governance risk arises when the board approves it without acknowledging that the strategy has changed. 

2. Have we pressure-tested the assumptions? 

Most board papers contain dozens of assumptions. Only a handful genuinely determine whether the initiative succeeds. 

A projected return of 18% may look attractive until directors discover that the case depends heavily on one market-growth assumption. A transformation programme may appear financially compelling until the board realises that it assumes the organisation can recruit specialist talent in a market where those skills are already scarce. 

The useful question is not whether assumptions exist. They always do. The useful question is which assumptions carry the most weight. 

A practical test is to ask management: if the board could monitor only three assumptions over the next 24 months, which three would they be? The answer often reveals more than another review of the financial model. 

Directors should also ask what would most likely explain failure three years from now. Implementation complexity, customer adoption, regulatory delay, integration cost, and management bandwidth are common places to look. 

Strategic initiatives rarely fail because every assumption is wrong. They fail because the board did not identify which assumptions mattered most.

Pressure-testing is not a sign of distrust. It is how directors determine whether confidence in the proposal is supported by evidence, or whether optimism has become part of the business case. 

3. What are the key risks, and how are they being managed? 

The board is not approving a risk-free initiative. It is deciding whether the expected benefit justifies the risks being accepted. 

That requires more than a risk register attached to the business case. Directors need to distinguish between risks management can control, risks management can mitigate, and risks the board itself must be willing to accept. A technology programme may involve delivery risk. A market-entry decision may involve regulatory risk. A partnership may involve dependency risk. A transaction may introduce reputational exposure that is difficult to reverse once the decision is public. 

The board should ask which risks fall outside existing risk appetite, whether the CISO, CFO, general counsel, or other relevant executives have assessed them, and what conditions would need to be met before the initiative proceeds. 

Cyber and data risks deserve particular attention when an initiative involves new platforms, customer data, sensitive commercial information, or third-party integrations. A board does not need to manage those risks operationally, but it does need to understand their significance. 

Cybersecurity consultant Joseph Steinberg captures the oversight distinction well: “Every company really needs somebody on their board today who understands how to oversee the management of cyber risk,” Steinberg explains, “but, while there are many people who know how to manage cyber risk far fewer know how to oversee the management of cyber risk.”  

The board's job is not to remove risk. It is to ensure risk is visible, understood, and deliberately accepted. 

Cyber and data security questions: If the initiative involves sensitive data, a new technology platform, or third-party access, the board should ask for the CISO's assessment before approval. Directors should understand the residual risk, the mitigation plan, and whether the proposal sits within the organisation's agreed risk tolerance.

4. Do we have the right management team to execute this? 

A strong business case can still fail in the hands of an overstretched organisation. 

Boards often spend considerable time examining the strategic rationale and financial case, while giving less attention to execution capacity. That can be a mistake. Many strategic initiatives fail not because the idea was poor, but because the organisation lacked the leadership, attention, capability, or discipline to deliver it. 

The board should ask who owns the initiative, whether that person has the authority to make decisions, and whether they have enough bandwidth alongside existing responsibilities. A named sponsor is not enough if the initiative depends on several functions that are already carrying major programmes. 

Directors should also examine track record. Has the management team delivered comparable initiatives before? Where execution has previously fallen short, what has changed? If external capability is required, is the organisation realistic about the time and cost of securing it? 

This is a governance question, not a vote of no confidence. The board owes it to management to ensure the team is set up to succeed before approving a major commitment. 

A useful chair's question is: what would management stop, slow, or deprioritise to make this initiative deliverable? If the answer is unclear, the board may be approving ambition without capacity. 

5. What does success look like, and how will we track it? 

Approval should not be the final governance moment. It should establish the basis for future oversight. 

Before approving a strategic initiative, the board should agree what success looks like, which milestones matter, and what would trigger a review. Without that discipline, directors may find themselves receiving progress updates that describe activity rather than performance. 

Good answers are specific. They identify financial and non-financial indicators, timing, accountability, and red flags. A transformation programme may require milestones around adoption, cost reduction, customer impact, and operating resilience. A market-entry initiative may require thresholds for revenue, margin, regulatory progress, and local leadership capability. 

The board should also consider conditional approval. Approval in principle, subject to defined conditions precedent, can be a responsible governance tool. It allows management to proceed while preserving board oversight over unresolved issues. 

Approving an initiative without defining success is delegation without a reliable accountability mechanism.

The strongest boards do not wait until failure is obvious before asking whether assumptions have changed. They agree in advance when an initiative should return to the board, what evidence will be required, and who is accountable for follow-through. 

Sherpany's Tasks and Decisions capability is relevant here because it allows boards to capture approvals, conditions, owners, and follow-up actions in the same governance environment as the meeting record. 

6. What are the implications for capital allocation? 

Every strategic approval is also a capital allocation decision. 

That remains true even when the proposal is not presented in those terms. A new initiative consumes capital, leadership attention, organisational capacity, and sometimes reputational headroom. Approving it means not doing something else, or at least doing something else with less focus. 

Directors should therefore ask for the full cost of the initiative, not only the headline investment. Implementation, integration, technology, people, external advisers, transition costs, and management time all matter. So does opportunity cost. 

This is particularly important when a proposal is strategically attractive but financially marginal. The board should ask whether the same capital could produce a better risk-adjusted outcome elsewhere in the organisation. 

For boards, the point is that capital allocation cannot be treated as a finance appendix. It is central to strategic oversight. Directors should know what the organisation is choosing, what it is giving up, and whether the trade-off is deliberate. 

7. Are we making this decision with the right information? 

A board can have access to information without having the information it needs. 

This is one of the most common weaknesses in strategic approval processes. The board pack may be long, but length is not the same as clarity. The executive summary may be polished, but the underlying assumptions may be difficult to interrogate. Directors may receive the materials on time, but not early enough to form a considered view. 

Herbert Simon's observation remains relevant decades later: "a wealth of information creates a poverty of attention". For boards, the scarce resource is rarely information itself. It is the director's ability to identify what matters before the meeting. 

Richard Rosenthal, a principal at Deloitte & Touche LLP, makes the same point in boardroom terms: "An inability to extract salient information in a timely manner could make it difficult for boards to discern actionable insights." 

Directors should ask whether they have seen the underlying data and models, not only management's interpretation. They should also ask whether the pack gives enough attention to alternatives, downside cases, and assumptions that would change the recommendation. 

This is also where AI-assisted analysis has become relevant. A 2026 FT Longitude survey of 1,000 dealmakers commissioned by Datasite found that 62% believe relying on human-only decision-making in complex decisions is now indefensible. The finding should not be read narrowly as an M&A point. It reflects a broader shift in what senior decision-makers expect when evaluating complex, high-stakes proposals. 

Sherpany's Document Copilot supports this preparation challenge by allowing directors to interrogate board papers and supporting materials with natural-language questions before the meeting. 

8. How are we keeping this information secure? 

Strategic approvals often involve the organisation's most sensitive information: market plans, transaction documents, pricing assumptions, restructuring options, customer data, and leadership assessments. 

The board should therefore ask how the information supporting the decision is being handled. Who has access to the materials? Are permissions role-based? Is there an audit trail? Can access be revoked if circumstances change? Are documents watermarked, version-controlled, and protected from onward circulation? 

This is a governance question, not an IT preference. Boards that still rely on email attachments for highly sensitive strategic materials may be creating unnecessary exposure. Once a document is forwarded, downloaded, or stored locally, the organisation may lose control over who can access it. 

The OECD principle that board members should have access to "accurate, relevant and timely information" should be read alongside the obligation to protect that information. Timely access and secure access are both part of effective governance. 

For initiatives involving transactions, partnerships, regulatory matters, or market-sensitive disclosures, the board should also ask whether the organisation has a clear confidentiality protocol. That includes directors, advisers, executives, and any third parties with access to the decision materials. 

Secure governance infrastructure matters because the board's own deliberations are part of the risk environment. Sherpany supports this through centralised document management, version control, role-based permissions, watermarked documents, immutable audit logs, remote wipe, Swiss data residency, AES-256 encryption, ISO 27001, and SOC 2 Type II certification. 

How to use board meetings to work through these questions 

The eight questions are only useful if they shape the board's actual discussion. 

That starts before the meeting. Directors should receive materials with enough time to read, annotate, and form an initial view. The meeting itself should not be the first moment the board encounters the proposal. It should be the point at which individual preparation turns into collective judgement. 

Agenda design matters. An item titled "Update on Project Atlas" invites a presentation. An item framed as "Should the board approve Project Atlas on the terms presented?" invites a decision. Better still, the chair can structure the discussion around the questions that matter most: strategic fit, assumptions, risk, execution capacity, capital allocation, and conditions for approval. 

The chair also needs to manage the room. Challenge should be specific, not performative. A NED with sector expertise should have space to test market assumptions. The audit or risk chair may need time to examine controls. The company secretary should ensure that decisions, reservations, conditions, and follow-up actions are captured accurately. 

In-camera time can be valuable where questions concern management capability, capital trade-offs, or unresolved reservations. It gives directors space to test whether the board is genuinely ready to approve. 

Conditional approval should also be treated as a normal governance outcome. The board does not have to approve or reject outright. It can approve subject to defined conditions, request further evidence, require milestone reviews, or stage the decision. 

Digital board platforms support this discipline when they improve preparation, version control, access permissions, agenda structure, annotations, voting records, and the formal capture of decisions. The technology should serve the governance process, not become the process itself. 

The best approval discussions do not feel adversarial. They feel precise. 

Approving well is a board discipline 

The eight questions are not designed to slow management down. They are designed to improve the quality of board approval. 

A strong board does not simply ask whether a proposal is attractive. It asks whether the proposal fits the agreed strategy, whether the assumptions can withstand scrutiny, whether the risks are acceptable, whether management can execute, and whether the board has enough information to stand behind the decision. 

That is what distinguishes approval from endorsement. 

Boards that approve well create clarity before commitment. They define success before execution. They preserve accountability after the vote. 

That discipline is easy to overlook when a proposal is compelling and momentum is strong, but that's also when discipline matters most. 

If you'd like to enhance the way your board manages strategic discussions, book a free consultation today and find out how Sherpany can help.