Bottom line
Decision making software adoption at the leadership level has a persistently high failure rate. Tools are purchased, onboarded, and then quietly abandoned — usually within six months of initial deployment. The explanation that typically gets offered is a software problem: the tool was too complex, or too rigid, or did not integrate well enough with existing workflows. These explanations are sometimes partially correct. But the more fundamental reason is that most decision making software is designed around a rational model of how leadership decisions work — and leadership decisions do not work that way.
The rational model problem.
Most decision making software assumes that decisions follow a sequential, visible process: define the problem, gather options, evaluate against criteria, reach a conclusion, document it. This is a reasonable model for committee decisions with clear parameters. It is not a good model for leadership decisions, which are typically messier: the problem definition shifts as the discussion proceeds, the criteria are contested rather than agreed, the conclusion emerges from conversation rather than analysis, and the documentation happens, if at all, as an afterthought. Software designed for the rational model encounters friction at every stage when deployed into real leadership processes.
The political layer that software ignores.
Leadership decisions also have a political layer that most software is not designed to address. The right answer to a strategic question is often known to one or more people in the room before the formal decision process begins — but surfacing it requires navigating power dynamics, managing the risk of being wrong publicly, and accounting for the relationships that will be affected by the conclusion. Decision making software that assumes everyone is optimizing for the same outcome, and that disagreement will be expressed through the platform's built-in debate functionality, tends to find that the real deliberation happens in the corridor before the meeting rather than in the tool.
More on Decision Science — every week.
Join 2,400+ leaders getting the decision intelligence briefing.
What actually drives successful adoption.
The leadership teams that successfully adopt decision making software share a common pattern: they use the tool to structure the pre-deliberation preparation rather than the deliberation itself. The software generates the analytical framing before the meeting — the options, the key assumptions, the stress tests, the documented perspectives — so that the meeting can focus on the genuinely difficult judgments rather than the assembling of context. This positions the tool as preparation infrastructure rather than a meeting substitute, which is a much more natural fit for how leadership teams actually want to work.
The design implication.
Software designed to improve leadership decision quality needs to meet leaders where their decision process actually is — which means handling ambiguity, accommodating political reality, and operating at the pace and format of executive work. It also means generating enough value in the preparation phase that the platform earns the right to sit alongside the decision, rather than claiming to replace the human judgment that leadership is paid to provide. Adoption succeeds when the tool makes leaders better at the thing they are already doing — not when it asks them to do something new.
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.