Article
Governance as a Way Not to Decide
A review committee, a steering group, or a multi-stage sign-off chain can look like careful oversight while actually functioning as a way to defer an uncomfortable decision indefinitely, because each additional review step looks rigorous and simultaneously postpones the moment someone has to actuall
- Published
- July 30, 2026
- Updated
- August 19, 2026
- Reading time
- 9 min

The Global Signal
In February 2011, Nokia's then chief executive Stephen Elop distributed an internal memo, widely known afterward as the "burning platform" memo, describing Nokia's competitive position eroding rapidly against Apple's iOS and Google's Android ecosystems while Nokia's own Symbian platform struggled to keep pace; the memo's full text was published by multiple technology outlets, including Engadget, shortly after it was sent. Nokia's board and leadership had reportedly been reviewing platform strategy and competitive positioning through internal committees for several years prior to Elop's memo, without arriving at a decisive strategic shift. Nokia ultimately announced the sale of its Devices and Services business, its entire handset operation, to Microsoft in September 2013, a deal that closed in April 2014 for approximately €5.44 billion, a fraction of the value the handset business had commanded at its peak market position earlier in the decade.
The strategic question Elop's memo forced into the open, that Nokia's smartphone platform strategy was not competitive and needed a decisive change, had reportedly been circulating through internal reviews for years before it was named that directly. Each review cycle could point to legitimate reasons for caution; none of them converted the review into an actual deadline-bound decision.
The tell is a process that keeps adding reviewers without ever adding a deadline.
What changes when a deadline is attached to governance
A review process without a deadline can continue indefinitely and still look like careful oversight.
Setting a hard deadline at the start of any governance process, and treating any extension as an explicit decision, closes the gap that let Nokia's platform strategy circulate for years.
Why the Visible Metric Misleads
A governance process's own thoroughness, the number of reviews conducted, the depth of analysis requested, the number of stakeholders consulted, is often treated as evidence the organization is handling a hard decision responsibly, when thoroughness without a deadline is functionally identical to never deciding at all. The more revealing measure is not how many review cycles a decision has passed through, but whether a specific date exists by which a final call must be made, regardless of whether every possible question has been answered by then. Nokia's internal reviews of platform strategy, whatever their individual thoroughness, had no such deadline attached before Elop's 2011 memo forced the question into the open under external competitive pressure rather than internal governance discipline.
The Leadership Move
The right move is not to reduce governance or skip due diligence on hard decisions. It is to attach a hard deadline to every governance review from the outset, so that additional analysis can extend the deadline only through an explicit, visible decision to do so, rather than through the review process quietly continuing without one.
- Ownership
The committee or function running a governance review typically owns the quality of the analysis it produces. Leadership needs to own setting, and defending, the deadline by which that analysis must produce an actual decision, since the reviewing function is rarely positioned to be the one that declares its own review finished.
- Tradeoff
A hard deadline means a decision will sometimes be made with less information than an unbounded review process might eventually gather, and that is a real cost. The alternative, Nokia's platform strategy sitting under internal review for years before an external memo forced the question, and the handset business ultimately selling for a fraction of its earlier value, shows the cost of unbounded deferral is frequently larger.
- Human consequence
Nokia's employees inside the handset business worked for years under a strategy that internal governance reviews had not decisively resolved, and the eventual outcome, a sale to Microsoft at a steep discount to the business's earlier value, arrived only after external competitive pressure made further deferral impossible.
Implication for Operators
Any organization running a multi-stage review process for a genuinely hard decision should assume that thoroughness without an attached deadline functions as indefinite deferral, regardless of how rigorous each individual review stage is. The practical shift is setting a hard deadline at the start of any governance process and treating any extension of that deadline as its own explicit, visible decision, rather than something the process drifts into by default.
Nokia's strategic problem was not a lack of internal awareness or review; the platform question was reportedly discussed through internal committees for years before Elop's 2011 memo named it directly. The organization was not blind to the competitive threat. It was blind to the fact that its own governance process had no deadline attached, so review could continue indefinitely without ever becoming a decision.
The decision blindness here is not insufficient analysis. It is a governance process thorough enough to look responsible while structurally incapable of producing a decision, because no deadline forced it to.
When a governance forum reviews a difficult choice, does it add a decision deadline and owner, or mostly add another layer of review?
FAQ
Was Nokia's platform decision simply too difficult to have been made earlier?
The underlying competitive pressure, a shift toward Android and iOS, was visible externally for years before Nokia's 2013 sale to Microsoft. The difficulty was real, but the pattern the "burning platform" memo describes is one of internal review continuing without a forcing deadline, not a decision that was genuinely impossible to make sooner.
How is this different from ordinary careful due diligence?
Due diligence with a deadline produces a decision by a known date, informed by whatever analysis was completed in that window. This pattern describes due diligence without a deadline, which can continue indefinitely because no point exists at which the process is required to conclude in an actual decision.
How can an organization tell if its governance process is actually deferring a decision?
Ask whether a specific date exists by which the process must produce a final decision, and whether extending that date requires an explicit, visible choice or simply happens by default because the review "isn't finished yet." If extension happens by default, the governance process functions as deferral.
Does setting a hard deadline risk rushing a genuinely complex decision?
A deadline can be set generously, matched to the decision's actual complexity, and can still be extended through an explicit decision when genuinely warranted. The distinction is whether extension is a visible choice someone must justify, or an invisible default the process falls into.
Who should set and defend the deadline for a governance review?
Leadership, not the committee conducting the review, since the reviewing body has limited incentive to declare its own work finished and every incentive to request one more round of analysis before committing to a decision.
Related intelligence
Article
Steering From Lagging Indicators
Strategic choices are routinely built on the most recent quarter's or year's results, indicators that are, by construction, a record of conditions that have already changed by the time they are reported. Leadership can steer confidently, using genuinely accurate numbers, toward a destination defined
Article
Automating a Decision Nobody Had Actually Made
Organizations frequently automate a workflow, a trading rule, a routing decision, a pricing exception, before anyone has explicitly decided what that workflow should optimize for, what should happen at its edges, or who owns the exceptions it will inevitably produce. Automation does not remove a dec
Article
The Decision With No Name on the Door
Decisions that span two or more functions, a safety concern, a vendor risk, a customer escalation, often default to whoever moves first, speaks loudest, or simply stays in the room longest, because no one has been formally named as the accountable owner of a decision that crosses functional lines. A