A project can miss its targets, exceed its budget, lose momentum, or eventually be discontinued. But its real cost may be much greater if the organization moves on without understanding what happened. The same mistakes can quietly return in the next initiative, under a different name, with a new team and another set of expectations.

For busy leaders, it is tempting to treat a completed initiative as yesterday's problem. There are new priorities to manage, deadlines to meet, and decisions waiting for attention. However, moving forward without examining important decisions can create a cycle in which teams repeatedly encounter the same obstacles without understanding why.

This is where a strategic initiative postmortem becomes valuable.

A postmortem is not simply a meeting about what went wrong. It is a structured examination of the decisions, assumptions, resources, and circumstances that shaped an initiative from beginning to end. Its purpose is to understand what the organization believed would happen, compare those expectations with reality, and determine what should change in future decisions.

More importantly, it should examine successful initiatives as well as unsuccessful ones. A project that delivers impressive results can still contain weaknesses, fortunate circumstances, or decisions that would not produce the same outcome again.

The goal is not to find someone responsible for a disappointing result. It is to make sure the experience produces knowledge that the organization can actually use.

One of the biggest challenges in reviewing completed projects is remembering what people actually believed when decisions were made.

Once the outcome becomes clear, it is easy to look backward and convince everyone that the result should have been obvious. A decision that seemed reasonable at the time can suddenly appear careless, while an unexpected success can make an uncertain decision look like a brilliant plan.

This is a form of hindsight bias. People naturally reinterpret earlier expectations using information they only learned afterward.

That is why an effective postmortem should begin with three questions:

These questions move the discussion beyond a simple review of deadlines, budgets, and completed tasks.

For example, imagine a company expanding its operations because leadership expects customer demand to increase significantly over the next two years. The company hires additional employees, purchases equipment, and commits to higher operating expenses.

However, demand grows much more slowly than expected.

A basic review might conclude that the expansion was unsuccessful because the company hired too quickly. A deeper examination would investigate whether the original demand forecast was reasonable, whether the market conditions changed, whether leadership committed too many resources too early, and whether there were opportunities to adjust the expansion before costs became difficult to reverse.

Those are very different lessons.

The first explanation identifies an outcome. The second helps the organization make better decisions the next time it considers expanding.

Tip: Document the assumptions behind major decisions before implementation begins; record expected demand, timelines, costs, risks, and the conditions that would justify changing direction.

Most organizations already have some form of performance review. They monitor targets, evaluate completed work, and discuss whether teams delivered what was expected.

Yet reviewing performance is not necessarily the same as understanding decisions.

Several obstacles make meaningful postmortems difficult to conduct.

Many companies revisit their overall direction once a year. This creates a natural opportunity to discuss performance, but it can also make individual initiatives disappear inside a much larger conversation.

A project might finish in March, while the next comprehensive strategy review happens several months later. By then, the people involved may have moved to other responsibilities, and important details may already be difficult to recover.

A better approach is to treat major initiatives as individual commitments with their own starting points, objectives, and completion conditions.

When an initiative ends, its review should follow naturally rather than waiting for an annual planning exercise.

This also makes it easier to identify which decisions deserve deeper examination. Not every routine task requires a formal postmortem, but significant initiatives involving substantial resources, organizational changes, or important long-term commitments should receive one.

A team may remember what it accomplished, but that does not mean it remembers exactly why certain decisions were made.

Without written records, a postmortem becomes an exercise in reconstructing conversations, searching through old documents, and comparing conflicting memories.

This wastes time and makes the discussion less reliable.

For example, a team might remember that leadership expected a new service to attract more customers. However, the original forecast may have depended on a particular customer segment, a competitor's expected pricing, or a specific adoption timeline.

Those details matter because they reveal which part of the original reasoning was accurate and which part needs reconsideration.

Documenting assumptions creates a reference point that remains useful even when the original decision-makers are no longer involved.

For busy teams, reviewing completed work can feel like an additional responsibility rather than a useful part of the job.

There is always another deadline, another customer request, or another initiative competing for attention.

However, skipping reflection does not necessarily save time. It can simply transfer the cost of unresolved problems into future projects.

When organizations repeatedly encounter similar issues, employees spend time solving problems that could have been prevented through earlier learning.

A short, focused review can therefore be more valuable than allowing the same mistakes to consume several months of future work.

Strategic initiatives often have champions: people who proposed the idea, secured support, or became responsible for delivering it.

When an initiative fails, these individuals may feel personally exposed. Some may have already moved into different positions, while others may worry that participating in the review could damage their credibility.

This creates a problem when the organization needs honest explanations but the people with the most relevant information are uncomfortable sharing them.

A productive postmortem separates accountability from personal blame. People should be expected to explain their decisions, but the discussion should recognize that they acted with the information and circumstances available at the time.

That distinction makes it possible to examine difficult decisions without turning the process into a search for someone to punish.

Not every discussion produces genuine agreement, and not every disagreement needs to be eliminated.

Different departments may have experienced the same initiative differently. Operations may have struggled with insufficient resources, while the leadership team believed the project had received adequate support.

Both perspectives deserve examination.

When organizations prioritize consensus too heavily, uncomfortable details can disappear from the final explanation. The result is a polished summary that everyone accepts but nobody learns much from.

AI tools can introduce another complication when employees use them as substitutes for conversations with colleagues. Although AI can help organize information and explore possible explanations, it cannot replace the firsthand context, professional judgment, and differing perspectives of the people involved.

Tip: Schedule postmortems when major initiatives conclude rather than waiting for annual reviews; preserve original decision documents and encourage employees to challenge explanations without making the discussion personal.

Even when organizations conduct postmortems, the process can fail if the discussion focuses on the wrong things.

When an initiative produces disappointing results, it is easy to conclude that the original idea was simply bad.

But an idea can have potential and still fail because it was poorly defined.

Consider a company that wants to improve customer retention. The objective sounds reasonable, but what exactly does the company intend to change? Which customers are most likely to leave? What specific actions could improve retention? How will success be measured?

Without clear answers, employees may interpret the initiative differently, making it difficult to coordinate their efforts.

A meaningful review should examine whether the original decision had a clear explanation of how it would create value, whether its boundaries were defined, and whether the organization understood what it would stop doing to support the new priority.

Sometimes the underlying idea was reasonable, but the company never translated it into a sufficiently clear commitment.

Missed deadlines and coordination problems are visible, so they often become the easiest explanations for disappointing results.

However, poor execution may actually be a symptom of a deeper problem: the organization never properly mobilized the initiative.

Mobilization means turning an approved decision into an actual organizational commitment.

It involves assigning clear ownership, establishing appropriate targets, reallocating resources, adjusting budgets, and ensuring that other priorities do not undermine the work.

Imagine leadership announces a major technology transformation and appoints a project leader. However, the leader receives no additional budget, existing responsibilities remain unchanged, and the departments expected to support the transformation continue prioritizing their previous work.

The initiative may eventually fall behind schedule.

Calling this an execution failure overlooks the more important question: did the organization provide the conditions necessary for the initiative to succeed?

A project cannot reasonably be expected to deliver its intended results when its authority, resources, and priorities remain unchanged.

Most important initiatives involve several interconnected decisions and circumstances.

A disappointing result may involve an inaccurate forecast, changing customer behavior, insufficient resources, delayed decisions, and unexpected competition.

Reducing all of this to one explanation creates a convenient story but an incomplete understanding.

It can also encourage people to defend their own contributions rather than examine the entire process.

A useful postmortem should preserve the complexity long enough to identify the most important contributing factors. The objective is not to produce the longest possible explanation. It is to avoid simplifying the experience before the evidence has been properly examined.

Tip: Before accepting an explanation such as poor execution or weak leadership, investigate the original decision, its clarity, the resources committed, and the circumstances surrounding the outcome; one visible problem rarely explains an entire initiative.

A thorough postmortem should examine five areas. Reviewing them in a deliberate order helps prevent teams from jumping immediately to operational mistakes.

Start with the reasoning behind the initiative.

What conditions did the organization expect? What made the opportunity attractive? What capabilities did it believe would provide an advantage? Were the expected benefits realistic?

The objective is to identify which assumptions remained valid and which ones failed.

For example, a company introducing a new product may have correctly identified customer demand but underestimated the time required to establish distribution. The product concept may still be sound, even though the original timeline was unrealistic.

Understanding this distinction prevents an organization from abandoning a promising idea simply because one part of its original design was incorrect.

Next, examine whether the initiative was sufficiently developed before approval.

Was its purpose clear? Were the expected benefits supported by reasonable evidence? Were the risks understood? Did leadership identify what would need to change for the initiative to remain worthwhile?

A decision should be judged based on the information available when it was made, not solely on the result.

This is particularly important because good decisions do not always produce successful outcomes, just as poorly considered decisions can occasionally benefit from favorable circumstances.

Determine whether the organization actually committed what the initiative required.

Look at leadership ownership, employee responsibilities, budgets, staffing, incentives, and competing priorities.

If a project was described as a top priority but never received the necessary resources, the problem may have started long before employees began missing deadlines.

This is also where leaders should examine whether existing work was stopped or reduced to make room for the new commitment.

Adding another priority without removing anything else often creates an unrealistic workload.

Only after examining the decision and mobilization should the review turn to implementation.

Were responsibilities understood? Were important milestones completed? Did teams communicate effectively? Were problems addressed early enough? Did the organization adapt when new information became available?

Execution still matters, but it should not become the automatic explanation for every disappointing result.

A team may have performed its responsibilities well under difficult circumstances while the overall initiative remained unsuccessful because the original assumptions were incorrect.

Finally, examine what happened outside the organization's control.

Unexpected market changes, sudden disruptions, regulatory developments, or unforeseen customer behavior can affect even carefully considered decisions.

This introduces an important distinction: the quality of a decision and the outcome of that decision are not always the same.

A sensible decision can produce an unfavorable result because circumstances changed. A poorly considered decision can produce a favorable result because conditions happened to work in its favor.

This does not mean organizations should ignore disappointing outcomes. It means they should avoid judging the entire decision using information that was unavailable when it was made.

Tip: Review design, decision quality, mobilization, execution, and external circumstances separately; this makes it easier to identify what should genuinely change instead of correcting the wrong problem.

One of the most overlooked opportunities for organizational learning comes from projects that appear to have gone well.

When an initiative succeeds, teams naturally want to celebrate the result and move on. However, success does not automatically prove that every decision was correct.

A project may have exceeded expectations because of unusually favorable timing, unexpected customer demand, or assistance from another department. If the organization assumes that every part of the original approach should be repeated, it may carry an unreliable process into its next initiative.

For example, a marketing campaign might produce exceptional results because a particular product unexpectedly becomes popular. The team may attribute the outcome entirely to its promotional strategy, even though external interest played a significant role.

Without reviewing the circumstances, the company could repeat the same campaign structure and expect similar results under completely different conditions.

Examining successful initiatives helps distinguish repeatable practices from fortunate outcomes.

Research involving Israeli soldiers also illustrates the value of reviewing both successful and unsuccessful exercises. The study by Shmuel Ellis and Inbar Davidi found that soldiers who reviewed both types of experiences improved more than those who reviewed only failures.

The broader lesson is important: learning should not begin only when something goes wrong.

Tip: Conduct short reviews after major successes as well as failures; identify which decisions, processes, and circumstances actually contributed to the result before turning them into standard practices.

A useful example of strategic learning comes from Shopify's 2022 workforce reduction.

During the pandemic, Shopify expanded its operations based on the expectation that the rapid growth of ecommerce would represent a lasting shift in consumer behavior.

The underlying reasoning was understandable. Online shopping had accelerated significantly, and Shopify occupied a strong position in the ecommerce market. If consumers permanently shifted toward online retail at a much faster rate, the company would need to expand its capabilities to support that demand.

However, the company made a major assumption about how permanent and substantial that change would be.

When consumer behavior began returning toward pre-pandemic patterns, the expected growth did not materialize at the pace Shopify had anticipated.

In July 2022, founder and CEO Tobi Lütke announced that approximately 10% of the workforce would be laid off. His explanation acknowledged that the company had incorrectly anticipated the permanence and scale of pandemic-driven ecommerce growth.

The important lesson was not simply that Shopify had hired too many people.

The company had built its operating structure around a growth expectation that proved too optimistic. Its expansion decisions were connected to a belief about how quickly the market would change, and when that belief proved inaccurate, its cost structure needed to be reconsidered.

There is also an important distinction here: the long-term opportunity in ecommerce had not disappeared. The mistake was largely in estimating the speed and permanence of the acceleration.

That difference matters because a temporary change in growth expectations does not necessarily invalidate an entire long-term direction.

Shopify's experience demonstrates why leaders should connect major commitments to the assumptions that justify them. When those assumptions change, organizations need to understand which decisions must be adjusted and which underlying beliefs remain valid.

It also demonstrates the value of communicating mistakes clearly. Employees are more likely to understand difficult organizational decisions when leadership explains the reasoning behind them instead of offering vague statements about changing priorities.

Tip: When communicating a difficult decision, explain what the organization originally expected, what changed, and which decisions are being reconsidered; clear explanations build understanding without shifting blame onto employees.

A postmortem has limited value if its conclusions remain inside a meeting document.

The real benefit appears when the organization uses what it learned to improve future decisions.

This requires distinguishing between assumptions and broader beliefs.

An assumption relates to a particular situation. For example, a company may believe that a new service can attract 20,000 customers within its first year.

A belief is broader. It might be that customers are willing to pay more for convenience, or that a particular distribution channel consistently produces better results.

One unsuccessful project does not automatically prove that a broader belief is wrong. Likewise, one successful initiative does not establish that the belief is always correct.

Leaders should examine how strongly the evidence supports or challenges their existing understanding.

Over time, this creates a more informed approach to decision-making. Rather than repeatedly starting from scratch, teams can build on lessons from previous experiences.

One practical way to strengthen this process is to conduct a premortem before starting the next major initiative.

Instead of waiting until the project ends, imagine that it has already failed. Ask the team to explain what might have happened.

Perhaps the timeline was unrealistic. Maybe the project depends on a supplier that cannot meet demand. Perhaps the required employees are already committed to other priorities.

The exercise encourages people to identify weaknesses before they become expensive problems.

The same approach can be used to imagine a successful outcome. What conditions would need to be present? Which capabilities would make the difference? What should the team protect as the initiative develops?

This gives employees an opportunity to challenge assumptions while there is still time to make adjustments.

A postmortem cannot become a consistent organizational practice if leaders treat it as an administrative requirement.

Leadership must demonstrate that examining decisions is a normal part of doing meaningful work.

That starts with asking better questions. When an initiative misses its objectives, leaders should resist accepting the first explanation. They should investigate the reasoning behind the decision, the resources committed, and the circumstances that influenced the outcome.

It also means creating an environment where employees can discuss mistakes without automatically expecting punishment.

This does not eliminate accountability. People should still be responsible for their decisions, commitments, and actions. However, accountability should focus on understanding what happened and improving future performance rather than simply identifying someone to blame.

Leaders also need to communicate what they learn outside formal review meetings. Internal discussions, team meetings, and company-wide updates can help employees understand how past experiences are shaping current decisions.

When leaders openly acknowledge incorrect assumptions and explain what has changed, they establish a stronger standard for the rest of the organization.

The most valuable outcome is a workplace where people are comfortable questioning existing practices, presenting conflicting evidence, and identifying problems before they become larger.

Tip: Make postmortems a regular leadership responsibility rather than an optional exercise; demonstrate that honest reflection, clear ownership, and practical improvements matter more than protecting the appearance of being right.

Every completed initiative leaves behind more than its final results. It also leaves evidence about how people make decisions, how teams work together, and how an organization responds when reality differs from expectations.

Without reflection, much of that information disappears.

The next project begins, employees face familiar challenges, and leadership makes decisions using the same assumptions that may have contributed to earlier problems.

A thoughtful postmortem interrupts that cycle.

It helps organizations distinguish a weak idea from a poorly supported decision, an execution problem from a mobilization failure, and a genuine mistake from an unfavorable outcome caused by circumstances beyond anyone's control.

Most importantly, it turns experience into something useful.

For leaders managing multiple priorities, the goal should not be to review every small task or create another layer of meetings. It should be to identify the important decisions worth understanding and make sure their lessons influence what happens next.

A successful organization is not one that never makes mistakes. It is one that becomes less likely to repeat them because it takes the time to understand why they happened.

The best question after a major initiative ends is therefore not simply whether it succeeded or failed.

It is: What does this experience teach the organization that it did not know before?

Hit reply and tell me: what is one lesson from a past project that your team still hasn't acted on? I read every answer.

Keep going, one small spark at a time.

Erwin