logo
Most organizations have meticulous records of what happened in their business: every transaction, every customer interaction, every system event logged, timestamped, and stored. Far fewer have any reliable record of why a specific decision was made, what evidence informed it, or what outcome was actually expected at the time. Six months later, when someone asks “why did we decide to do this,” the honest answer is often nobody quite remembers, and the explanation gets reconstructed after the fact to fit whatever happened.
Decision logs exist to close that gap, applying the same discipline to recording decisions that organizations already apply to recording data, and the absence of this practice is one of the more quietly costly gaps in how most companies actually operate.
Why This Asymmetry Exists
It’s worth asking directly why organizations invest heavily in data infrastructure but almost never invest equivalently in decision infrastructure. The data exists as a byproduct of running the business, transactions happen and get recorded automatically. Decisions, by contrast, happen in conversations, meetings, and someone’s head, and recording them requires a deliberate extra step that nothing in the normal workflow forces anyone to take.
This means decision documentation only happens if someone makes it happen on purpose. Without that deliberate effort, decisions simply evaporate as formal records the moment the meeting ends, leaving only fragmented, inconsistent memories that get reconstructed differently by different people whenever the decision gets questioned later.
What Gets Lost Without a Decision Log
The Actual Reasoning Disappears, Leaving Only the Outcome
A year after a strategic pricing decision, what typically survives is the fact that prices changed and roughly when. What’s almost always lost is the specific reasoning at the time: what data was considered, what alternatives were rejected and why, what assumptions the decision depended on, and what outcome was actually expected. Without that reasoning preserved, it’s impossible to honestly evaluate whether the decision was a good one given what was known then, as opposed to judging it unfairly against information that only became available afterward.
The Organization Can’t Learn From Its Own History
Without a record of past decisions and their reasoning, an organization facing a similar choice later has no way to draw on its own accumulated experience. It either repeats analysis that’s already been done before, sometimes reaching a different conclusion for no good reason other than different people happened to be in the room, or it repeats a mistake that was already made and already understood, because nobody documented what was learned the first time clearly enough for it to be found and applied again.
Accountability Becomes Impossible to Establish Fairly
When a decision turns out badly, the natural organizational instinct is to look backward and assign responsibility. Without a contemporaneous record of who decided what, based on what information, that process degenerates into people’s competing memories of what was said, which tends to shift conveniently depending on how the decision turned out. A decision log that was written at the time, before anyone knew the outcome, is a far more honest basis for evaluating whether the decision was reasonable given the information available, rather than judging it unfairly with hindsight.
Evaluating Decision Quality Separately From Outcome Quality Becomes Impossible
This is perhaps the most important and most overlooked benefit. A genuinely good decision can produce a bad outcome through bad luck, and a genuinely bad decision can produce a good outcome through good luck. Without a record of the reasoning at the time, organizations almost inevitably collapse this distinction, judging decisions entirely by their outcomes rather than by whether they were sound given what was actually known. This produces a systematically distorted sense of what good decision-making actually looks like, because the organization’s only available signal is whether things happened to work out.
What a Useful Decision Log Actually Contains
A decision log doesn’t need to be an elaborate system. It needs to consistently capture a few specific things, recorded at the time the decision is made, not reconstructed afterward.
The decision itself, stated clearly and specifically. Not a vague summary, but the actual choice that was made, precise enough that someone reading it later understands exactly what was decided.
The alternatives that were considered and why they were rejected. A decision rarely exists in isolation. Recording what else was on the table, and the specific reasoning for why those alternatives were set aside, preserves context that the decision alone doesn’t convey.
The evidence and assumptions the decision relied on. What data informed the choice, and equally important, what wasn’t known and had to be assumed. This is the piece most critical for fair evaluation later, because it lets someone assess whether the decision made sense given the information available at the time.
The expected outcome and timeframe. What result was actually anticipated, and by when. Without this stated explicitly in advance, it’s tempting later to retroactively redefine what counts as success based on whatever actually happened.
Who made the decision and who else was consulted. Not for blame, but for accountability and for knowing who to ask if the reasoning needs to be understood more deeply later.
Why This Is Harder Than It Sounds, Organizationally
The practical obstacle to decision logs isn’t technical. Recording this information requires no sophisticated tooling, a structured document or a simple shared template is sufficient. The obstacle is behavioral: it requires someone to take the extra step of writing the decision down clearly, at the moment it’s made, when the natural instinct is to move on to the next item on the agenda.
This is also where the political discomfort lives. Writing down the specific reasoning and expected outcome for a decision creates a record that can later be checked against what actually happened, which is precisely the kind of accountability that some decision-makers instinctively resist, even when the underlying intention is organizational learning rather than blame. Building genuine buy-in for decision logs requires establishing clearly, and demonstrating consistently over time, that the purpose is learning and fair evaluation, not creating ammunition for later criticism.
Where to Start Without Building an Elaborate System
Organizations don’t need to log every decision to get real value from the practice. The highest-leverage place to start is the small set of genuinely significant, hard-to-reverse decisions, major strategic choices, significant resource allocations, key hiring decisions at senior levels, where the cost of getting it wrong is high and the value of being able to learn from the reasoning later is correspondingly high.
A simple, consistent template applied to just those decisions, reviewed periodically against what actually happened, builds an organizational memory that compounds over time in a way that no individual person’s memory, however good, can replicate or sustain as people move roles or leave the company entirely.
The Underlying Principle
Organizations that document their data meticulously but their decisions barely at all have built infrastructure for understanding what happened in their business, while leaving almost entirely undocumented the much harder and more valuable question of why specific choices were made and whether that reasoning was actually sound. Decision logs apply the same basic discipline that data infrastructure represents, systematic, consistent recording, to the part of the business that determines outcomes most directly: the actual decisions.
Making good decisions, and being able to learn honestly from the ones that didn’t work out, requires the same disciplined thinking that good data analysis demands. IMP’s Data Analysis & Business Intelligence Diploma is built to develop exactly that kind of practical, evidence-based judgment.
