Most organisations have one decision they keep getting wrong. Not a different decision each time, the same one, dressed up in slightly different clothes. It might be a hiring call, a pricing move, a scope change, or a resource allocation. The details vary. The outcome is consistently worse than it should be. A decision audit is a structured way to find out why.

Pick the right decision to audit

The best candidate for an audit is a decision that recurs at least quarterly, has a measurable outcome, and has gone wrong at least twice in the past 18 months. It should be specific enough to trace. 'Our strategy' is not a decision. 'Whether to take on clients outside our core sector' is. Start by listing every recurring decision your team makes. Then mark the ones where the outcome has been consistently below expectations. Pick the one that stings the most.

Trace the inputs

For each instance of the decision in the past 18 months, write down: what information was available, who was in the room, what the alternatives were, and what was assumed to be true. Do this for every instance, not just the ones that went badly. You are looking for the pattern. In most audits, the problem shows up in the assumptions column. Something was taken as given that was not actually verified. That assumption is usually the same one every time.

Map the gaps

Once you have the inputs mapped, look for what was consistently missing. Common gaps include: data that existed but was not consulted, a stakeholder who was not in the room, an alternative that was never seriously considered, and a time constraint that forced a decision before the information was ready. Write each gap as a specific sentence, not a category. 'We did not check the margin data before agreeing to the discount' is useful. 'Insufficient data' is not.

Build the corrected process

The corrected process is a checklist, not a framework. For each gap you found, write one step that closes it. Keep it short enough to actually use. A good decision checklist for a recurring decision has between five and nine steps. If it is longer than that, it will not get used. Test it on the next instance of the decision before you declare it finished. Adjust based on what you learn.

Log it and review it

Put the corrected process in a decision log alongside the audit findings. Set a reminder to review it after three instances of the decision. The first version will not be perfect. The point is to have something written down that the team can improve together. Most organisations that do this find that the decision quality improves noticeably within two or three cycles.

A decision audit does not require outside help. It requires honesty about what went wrong and discipline about writing it down. If you want a structured version of this process with an outside perspective, the Decision Audit engagement at Mindwave Vault Zone runs two weeks and produces a corrected framework you can use immediately.