The Forecast That Nobody Challenged: Why Strategic Plans Need a Dissent Protocol Before Commitment, Not After Failure

Every strategic plan contains assumptions. Some of those assumptions are explicit, written into the planning document as stated dependencies. Most are not. They live beneath the surface of revenue projections, market share targets, and capability timelines as unexamined beliefs about how the world will behave once the plan is in motion. The problem is not that organizations make assumptions. Planning without assumptions is impossible. The problem is that most planning processes are structurally better at building confidence in a plan than at testing whether that confidence is warranted.

The result is predictable. By the time a plan reaches final approval, the people presenting it have invested months of analysis and iteration. The people reviewing it have seen progressively polished versions. Dissent, at that stage, feels like obstruction. It reads as a failure to be a team player, or worse, as a last-minute objection that should have been raised earlier. So it goes unspoken. The plan is approved. And the assumptions inside it, never formally examined, quietly govern execution until reality contradicts them loudly enough that something must change.

The Structural Source of the Problem

This is not a culture problem, though culture can make it worse. It is primarily a process problem. Most planning cycles are designed around synthesis: gathering inputs, modeling scenarios, aligning stakeholders, and producing a coherent document. That synthesis function is necessary, but it works against the kind of adversarial scrutiny that would catch fragile assumptions before they are locked in.

The people who build a plan are also, usually, the people who present it for approval. Their incentive, even unconsciously, is to show that the plan is sound. The people who review it are often evaluating the team as much as the plan itself. In that dynamic, the plan that gets approved is frequently the plan that generated the most confidence, not necessarily the one with the best-examined foundation.

A dissent protocol changes that dynamic structurally rather than culturally. It designates a specific moment in the planning process, before final commitment, when the explicit organizational task is to find what the plan got wrong. Not to reject the plan, but to stress-test the assumptions underneath it so that leaders can distinguish between commitments grounded in evidence and commitments grounded in optimism.

What a Dissent Protocol Actually Requires

The mechanism matters. A general invitation to raise concerns rarely produces the scrutiny that a structured protocol delivers, because general invitations still leave individuals to calculate the social cost of objecting. A dissent protocol removes that calculation by making dissent the required role, not the voluntary one.

One approach is to assign a small review group, separate from the planning team, the explicit task of producing a written challenge to the plan's core assumptions before the final approval meeting. That group is not evaluating whether the plan is good. They are identifying which assumptions would, if wrong, cause the plan to fail in ways leadership has not yet accounted for. Their output is a list of named risks tied to specific assumptions, not a general critique.

A second approach borrows from the premortem technique: before approving the plan, the leadership team is asked to project forward to a hypothetical in which the plan has failed, and to work backward to identify the most plausible cause. Critically, this exercise should be conducted in writing before the discussion, so that individual judgments are not immediately anchored to whoever speaks first. Written responses, collected and read aloud without attribution, surface concerns that participants would not volunteer in open session.

Either approach achieves the same structural outcome: assumptions that were implicit become explicit, and the people accountable for results have a chance to decide, deliberately, whether those assumptions are sound enough to build binding commitments on top of them.

What Happens to the Assumptions You Find

The goal of a dissent protocol is not to produce a longer risk register. Most organizations already have risk registers that nobody meaningfully consults during execution. The goal is to produce a short list of the assumptions most critical to the plan's validity, paired with a deliberate decision about how each will be monitored.

For each critical assumption identified, leaders should be able to answer three questions before approving the plan. First, what evidence would confirm or disconfirm this assumption within the first ninety days of execution? Second, who is responsible for watching for that evidence and bringing it to the right decision-maker? Third, what would change in the plan if this assumption turned out to be wrong?

If those three questions cannot be answered for a given assumption, that assumption is carrying more weight than the plan acknowledges. That does not necessarily mean the plan should not proceed. Sometimes the honest answer is that the assumption cannot be tested in advance and leadership is making a judgment call. But naming that clearly is a materially different position than treating an untested belief as established fact.

Why Timing Determines Whether This Works

The dissent protocol must occur before the plan is submitted for final approval, not as part of the approval conversation. Once a plan enters the approval meeting, participants have already formed positions. A challenge to assumptions reads as reopening a settled question. Careers and credibilities feel implicated. The psychological and political cost of changing direction rises steeply.

When the dissent process is positioned as a standard stage of planning, it carries none of that weight. It is simply what the organization does before committing. No plan is considered ready for approval until it has been through the challenge stage. That framing depersonalizes the scrutiny entirely. The challenge is not directed at the planning team. It is directed at the assumptions, which are a normal feature of any plan rather than evidence of poor analysis.

Senior leaders set this norm by participating in it consistently, not by asking teams to challenge their own work while exempting executive-level plans from the same review. When leaders visibly subject their own strategic thinking to the same structured dissent they require of others, the process becomes organizational practice rather than a procedural formality.

The Commitment That Survives the Challenge

A plan that has been through a genuine dissent protocol is not a weaker plan. It is a better-understood one. Leaders who approve it know which parts rest on solid ground and which parts rest on judgment. They have named the monitoring responsibilities. They have thought through what they would do if a key assumption fails. That is not pessimism. It is the difference between a commitment made with awareness and a commitment made by default.

The organizations that sustain strategic execution over time are generally not the ones that choose better plans at the outset. They are the ones that learn faster when reality diverges from expectation, because they built the mechanisms for that learning before they needed them.