Bottom line
Most organizations that invest in decision making software achieve partial adoption at best and active abandonment within 12 months at worst. The failure is almost never attributed to what actually caused it. The official narrative is usually a software problem — too complex, too rigid, not integrated enough. The real cause is almost always an organizational problem: the software was deployed without addressing the behavioral, cultural, and political conditions that determine whether any new decision process succeeds.
The first barrier: decisions are not owned.
Company-wide adoption of decision making software requires that someone owns the decision process for significant decisions — a person or function responsible for ensuring that the process is followed, the documentation is complete, and the reasoning is reviewed. Most organizations do not have this ownership structure. Decision making is diffuse: it happens in conversations, in email, in Slack, in meetings, with no clear process owner. Into this ambiguity, a tool that requires structured process compliance cannot take hold. Adoption requires process ownership before software deployment, not as a byproduct of it.
The second barrier: status quo bias is structural.
Decision making software threatens the informal authority that comes from being the person who knows how decisions are made. In organizations where a small number of senior individuals function as the de facto decision filters — not because of their formal role but because of their accumulated knowledge of the company's strategic logic — software that makes decision making more transparent and structured is politically threatening. The resistance to adoption in these organizations is rational from the perspective of those who benefit from the opacity, and it is rarely expressed openly. It shows up as 'the tool is not quite right for us' or 'we need to customise it further before rolling out'.
More on Decision Science — every week.
Join 2,400+ leaders getting the decision intelligence briefing.
The third barrier: the wrong starting point.
Company-wide adoption typically fails when it starts at the periphery — deploying the tool for low-stakes decisions first, to build familiarity before applying it to high-stakes ones. The logic is understandable but the outcome is consistently poor: the tool becomes associated with process overhead for decisions that did not need it, and the organization never reaches the high-stakes decisions where it would have produced genuine value. Successful adoption follows the opposite pattern: start with the decisions that matter most, demonstrate clear value there, and let that evidence drive broader deployment.
What successful adoption looks like.
Organizations that achieve lasting company-wide adoption of decision making software share a common pattern: executive sponsorship that is genuine rather than nominal, a clear set of decision categories where the tool is mandatory rather than optional, and a review process that evaluates the quality of documented reasoning — not just the presence of documentation. The tool becomes part of how the organization works when the consequence of not using it is visible: the decision that went badly, the reasoning that could not be reconstructed, the assumption that was never challenged. Successful adoption is not an IT project. It is a governance project that happens to involve software.
Research context
In a McKinsey survey, 72% of senior executives said bad strategic decisions were as frequent as good ones or were the prevailing norm.
McKinsey & Company: Untangling your organization's decision making (2017)This independently published statistic provides context for the topic; it does not substantiate every claim in this essay.
More on Decision Science, weekly.
One essay. Every week. No noise.