Most organisations are reasonably good at making decisions. Very few are good at learning from them. The gap between the two is not a matter of intent. Almost every leadership team will tell you they review what worked and what did not. The gap is a matter of honesty, and of building evaluation into the process before the decision is made, not as an afterthought once the outcome is known and the opportunity to learn from the reasoning has largely passed.
Done well, evaluation is one of the highest-return activities available to a leadership team. Done poorly, or not at all, it ensures that the same mistakes are made with increasing confidence each time, because the organisation has learned to call its outcomes successes without examining whether the decisions that produced them were actually sound.
The most common form of evaluation in organisations is the post-mortem: a structured review conducted after something has gone wrong. It has genuine value. But it has two significant limitations that, taken together, mean it is a considerably less powerful learning tool than it appears.
The first is survivorship. Post-mortems happen after failures. The decisions that went well, for reasons that were partly luck, partly timing, partly factors that had nothing to do with the quality of the decision itself, rarely receive the same scrutiny. Over time, this produces leadership teams with a detailed and often accurate understanding of how they fail, and a significantly inflated understanding of how well they decide when things go right. The result is a skewed self-model that overestimates the reliability of the processes that produced good outcomes and underestimates the role of circumstances in doing so.
The second limitation is hindsight bias. Once an outcome is known, it becomes almost impossible to evaluate the decision that produced it on its own terms: the information that was actually available at the time, the genuine uncertainty that existed, the options that were genuinely on the table. The tendency is to judge the decision by its outcome, which tells you very little about whether the process was sound.
A good decision can produce a bad outcome. A poor decision can produce a good one. Conflating the two is not just intellectually imprecise. It actively degrades the quality of future decisions by reinforcing the processes that got lucky and discrediting the processes that were sound but unfortunate.
The most underused form of evaluation happens before the decision is finalised, not after. It involves asking, explicitly and as a formal part of the decision process: how will we know if this was the right decision? What would we expect to observe, and over what timeframe, if the assumptions underlying this choice are correct? What would signal that those assumptions were wrong?
These questions force a precision that most decision-making processes avoid. They require the leadership team to commit to the logic of the decision in a way that makes it testable, that creates a specific and observable baseline against which actual outcomes can be measured, not against the comfortable standard of things turning out reasonably well, but against the conditions the decision was specifically designed to produce.
This is not complicated. It requires perhaps thirty minutes of disciplined conversation at the end of a decision process that may have taken weeks or months to reach. It is done rarely, because it creates a form of accountability that most organisations would prefer to keep implicit: accountability not just for the outcome, but for the reasoning that justified it.
In organisations where evaluation is genuinely embedded, decisions are treated as hypotheses. The reasoning behind them is documented clearly enough to be revisited when the evidence comes in. Outcomes are tracked against the specific assumptions that justified the decision, not just against financial targets or activity measures. And when the evidence suggests the original logic was flawed, that finding is treated as valuable information rather than an uncomfortable verdict on the people who decided.
The leadership behaviours that enable this culture are specific and observable. Leaders who model intellectual honesty about their own past decisions. Leaders who distinguish clearly and consistently between process quality and outcome quality, and who hold those two things separate even when the social pressure to conflate them is significant. Leaders who treat being demonstrably wrong about something, and saying so openly, as evidence of a functioning learning system rather than a career risk.
The organisations that evaluate well do not just avoid repeating mistakes. They build something more valuable over time: a clearer, more calibrated understanding of where their judgement is reliable and where it is not. They develop an institutional self-knowledge that is rare, difficult to replicate, and enormously valuable in the conditions of uncertainty and complexity that define the operating environment of every organisation in Queensland's public and social sectors.
That kind of capability does not appear on a balance sheet or a funding report. But it compounds, quietly and durably, into a decision-making capacity that is genuinely difficult for others to match. And it begins with the simple discipline of asking, before a decision is made, how we will know if we were right.
Our consultants take the time to understand your situation before offering any perspective on scope or method. There is no obligation attached to an initial conversation, and no expectation that you arrive with a fully formed brief. The clearer your thinking, the more quickly we can advise, but we are equally comfortable helping you develop that clarity as the first step. You might find our Getting Started Guide helpful in this process.
View: Our Contact Page
View: Our Getting Started Guide
Next Article: Governance and Decision Quality