Building the conditions that produce better decisions at scale
If decision making is the hidden skill behind strong leadership, the next question is whether organizations can develop it at scale. The answer is yes. But the standard methods — leadership training programs and executive coaching engagements that have dominated this field for decades — mostly don't work.
The reason has nothing to do with the quality of any particular program. It has to do with where decisions actually happen. Decisions aren't made in a classroom. They're made in the daily operating environment of a business, under pressure, with imperfect information, alongside dozens of other decisions competing for attention. A leader trained well in a workshop comes back Monday to the same environment that produced poor decisions the week before. The training fades. The environment stays.
Organizations that meaningfully improve decision quality understand this. They stop trying to train better decision makers and start building the conditions that produce them.
Decision making capability is partly a property of the individual and partly a property of the environment around them. The same person, placed in two different operating conditions, will produce decisions of measurably different quality. The conditions aren't background. They're part of the mechanism.
A capable decision maker in a poorly designed environment will still make poor decisions, because the environment produces the same friction, time pressure, sloppy framing, and depleted attention that produced bad decisions before. A less naturally gifted decision maker, dropped into a well designed environment, will often outperform the more capable one whose conditions were never improved.
This is the central shift. Better decision making in an organization isn't built primarily by developing the people. It's built by designing the conditions in which the people decide.
One of the simplest, highest leverage moves any organization can make is to stop treating all decisions the same.
A decision to change the office snack vendor and a decision to acquire a competitor need different processes. Both happen in most businesses with no formal distinction between them. Some companies push the small decision through a thirty page approval process and rush the large one in a thirty minute meeting, because the process applies uniformly regardless of stakes.
The first move is to categorize decisions along two dimensions:
Reversible, low stakes decisions should be made quickly and pushed close to the work, because the cost of being wrong is small and the cost of slowness is real. Irreversible, high stakes decisions deserve the opposite treatment, regardless of how much pressure exists to decide fast.
Naming this distinction is one of the cheapest changes a business can make. It costs nothing to implement. It does require the organization to be honest about which decisions belong in which category, which is sometimes harder than it sounds.
Most organizations have decision authority clustered at the top, often without ever having designed it that way. The pattern accumulated. The founder made every decision when the company was small, and as the company grew, no one redistributed the authority on purpose.
The result is a decision flow that's slow, low quality, and dependent on a handful of people whose attention is already stretched. Decisions get made by people with the least context, because they have the formal authority, while the people with the most context wait for permission to act.
The fix is structural. Identify the categories of decisions that should live closer to the work. Name who has the authority to make them. Accept that some distributed decisions will be wrong. They will. The wrongness isn't the problem. The problem is the assumption that centralized decisions, made slowly by people far from the situation, are systematically better than distributed ones. The research doesn't support that assumption.
Most organizations review outcomes. Fewer review decisions.
The distinction matters because outcomes are often shaped by luck, external factors, and forces unrelated to the choice that was made. A good decision can produce a bad outcome through no fault of the decision. A bad decision can produce a good outcome because conditions were favorable. Reviewing only outcomes teaches an organization to optimize for luck instead of judgment.
Decision review is different. It asks a separate question. Given what was known at the time, was this the right choice? Was the question framed correctly? Was the right evidence considered? Was the decision made at the right speed for its category? These questions can be asked even when the outcome is still unknown, and they produce different lessons than outcome review does.
Some organizations build this through formal decision journals, where consequential decisions get recorded along with the reasoning, the evidence considered, and the alternatives weighed. The journal gets reviewed quarterly or annually, separately from any business review. Over years, this kind of practice produces an organization that actually learns from its decisions rather than from its results.
A significant share of poor organizational decisions are well executed answers to the wrong question.
Building a small organizational habit of pausing to check the question before answering it is one of the cheapest, most effective improvements available. It can be as simple as one line at the top of every decision memo: What is the question we are actually answering? Is that the right question?
Most teams skip this step. The ones that do it consistently end up making fewer decisions in total, because they catch the misframed ones before they become projects.
Decision quality is affected by mental load. A leader making thirty important decisions in a day isn't making the thirtieth one with the same care as the first. The brain doesn't work that way.
Organizations can design around this. Schedule structure matters — spreading high stakes decisions across a day instead of stacking them in the afternoon. Building deliberate spaces for thinking instead of back to back meetings. Limiting the number of important decisions any one leader is responsible for in a given week.
Information access matters too. So does having someone whose job is to push back. So does deliberate exposure to disconfirming evidence. None of these are exotic interventions. They're operational design choices most organizations have never made, because no one named decision quality as a thing worth designing for.
A small but growing number of firms work in exactly this space. Pinpoint Management, for example, treats decision making conditions as part of the operational design of a business — on the premise that decision quality is too important to depend on whether a given leader happens to be sharp on a given day.
The work of creating better decision makers isn't the work of better training. It's the work of building an operating system that produces better decisions as a byproduct of how the business runs.
Organizations that take this approach get two compounding advantages. The decisions themselves improve, which improves outcomes over time. And the people working inside the system develop better decision making skill, because they're practicing the skill every day inside a structure designed to support it. The training happens inside the work, continuously, instead of in a workshop once a year.
Without these structural moves, even well intentioned organizations find themselves making the same poor decisions over and over. (See "Why Bad Decisions Repeat in Companies" for more on this pattern.)
The leaders an organization develops are the leaders the operating system produces. Improve the system, and the leaders improve with it. Leave the system unchanged, and the next generation will inherit the same conditions that limited the last.
Recent reading on decision quality and the conditions that shape it: