Before You Commit · 6 of 10Before You Commit
Imagine It Failed
Why a pre-mortem can reveal what optimism leaves hidden—and turn plausible failure pathways into warning signals, safeguards and better decisions.
Imagine it is twelve months from now.
The idea has failed.
The launch attracted attention but few customers.
The programme struggled to recruit participants.
The partnership collapsed.
The technology worked in the demonstration but failed under real operating conditions.
Costs increased.
The team became exhausted.
The audience misunderstood the proposition.
The community did not trust the organisation.
The funding never arrived.
The project delivered what it promised, but the promise turned out not to matter enough.
Now ask:
What happened?
This is the central question of a pre-mortem.
Unlike a post-mortem, which examines a failure after it has occurred, a pre-mortem moves imaginatively into the future and works backwards.
It does not ask whether the idea will fail.
It temporarily assumes that it has.
That change in perspective can make risks easier to see.
When people are developing an idea, they naturally concentrate on how to make it work.
They imagine the successful launch.
The full venue.
The growing customer base.
The positive reviews.
The funding award.
The productive partnership.
The new technology operating exactly as expected.
This optimism is not necessarily naïve.
Ideas need belief before they can become real.
But belief can also create blind spots.
People become attached to a preferred future and unconsciously interpret uncertainty in its favour.
Weak signals are dismissed.
Difficult questions are postponed.
Dependencies remain unexamined.
Concerns are softened because nobody wants to appear negative.
A pre-mortem creates permission to look in the opposite direction.
For a limited period, the task is not to defend the idea.
It is to explain its failure.
That can reveal what optimism has made difficult to see.
The Pre-Mortem Is Not a Prediction
A pre-mortem does not claim to know what will happen.
It is not forecasting disguised as certainty.
It is not a declaration that the idea is doomed.
It is not an invitation to produce the most dramatic disaster imaginable.
It is a structured decision exercise.
The question is not:
How will this definitely fail?
It is:
If it did fail, what might plausibly have caused that failure?
That word matters.
Plausibly.
The objective is to surface credible ways in which the proposition could become weaker, more expensive, less trusted, less relevant or impossible to deliver.
Some of those possibilities will prove unimportant.
Some will already be controlled.
Some may be impossible to prevent.
But a few may reveal decisions that deserve attention now.
The value of the exercise lies in discovering those risks while the organisation still has options.
Before the contract.
Before the production run.
Before the public promise.
Before the technology has been integrated.
Before the programme has been announced.
Before the budget becomes difficult to change.
From Several Futures to a Failed Future
Article Five introduced scenario thinking.
One idea can encounter several futures.
Demand may be stronger than expected.
Costs may rise.
A major partner may withdraw.
Technology may change.
Participation may be uneven.
A new opportunity may emerge.
Scenario thinking examines how a proposition behaves across a range of plausible conditions.
A pre-mortem performs a related but more concentrated task.
It selects one outcome—failure—and asks how the idea might have reached it.
This creates a form of prospective hindsight.
Instead of standing in the present and wondering what could go wrong, participants imagine that something already has.
They then construct the path backwards.
The shift can make thinking more specific.
Compare:
“What risks should we consider?”
with:
“It is September next year. The programme has been discontinued after one cycle. What happened?”
The second question creates a situation.
People may begin to see the empty sessions.
The unspent partnership commitment.
The inaccessible booking system.
The delayed payments.
The exhausted coordinator.
The negative community response.
The report nobody had capacity to implement.
The failure acquires a sequence.
Once the sequence becomes visible, intervention becomes possible.
An Idea Can Fail Without You Being a Failure
Pre-mortems can be emotionally difficult because people frequently identify closely with their ideas.
For a founder, the business may represent years of work.
For an artist, the project may contain something deeply personal.
For a community organiser, the programme may emerge from lived experience and a genuine desire to improve something.
For a small team, the proposition may already have required sacrifice.
When the idea is questioned, the person can feel questioned.
That makes it important to establish a distinction:
The proposition is being examined. The person is not being judged.
An idea can contain a weak assumption without its creator being foolish.
A project can require revision without its purpose becoming unimportant.
A business model can fail while the underlying need remains real.
A pilot can produce disappointing results and still generate valuable knowledge.
A decision to stop can protect the person, organisation or community from a much more damaging outcome.
The purpose of a pre-mortem is not to prove that someone was wrong to believe in the idea.
It is to help the idea encounter serious challenge before reality delivers that challenge without preparation.
Failure Needs a Definition
Before conducting a pre-mortem, define what failure would mean.
This is more complicated than it appears.
For a commercial venture, failure might mean:
revenue below the level required to sustain delivery;
customer-acquisition costs becoming uneconomic;
insufficient repeat purchase;
cash flow becoming unmanageable;
or the founder being unable to maintain the workload.
For an artist, a project could sell poorly but generate important critical recognition, relationships or future commissions.
Was it a failure?
A community programme could meet its attendance target while failing to include the people it was designed to serve.
Was it a success?
A cultural event could receive excellent feedback while exhausting the staff and volunteers responsible for delivering it.
Should the outcome be considered successful?
An AI system could reduce processing time while producing decisions that customers experience as opaque or unfair.
Has the organisation improved?
The answer depends on what counts.
That is why the first pre-mortem question should not be:
Why did we fail?
It should be:
What would failure mean for this idea—and who gets to define it?
Whose Definition of Failure Counts?
Different people can experience the same project differently.
A funder may consider a programme successful because the required outputs were delivered.
Participants may consider it unsuccessful because they had little influence over its design.
The organisation may celebrate attendance.
The local community may remember that the project disappeared as soon as the funding ended.
A technology supplier may point to efficiency gains.
Employees may experience greater surveillance and less autonomy.
A founder may consider growth the primary objective.
The team may regard maintaining quality and manageable workloads as equally important.
Failure therefore cannot always be reduced to one number.
A culturally intelligent pre-mortem asks:
Who benefits if this succeeds?
Who carries the cost if it fails?
Whose outcome is being measured?
Whose experience could disappear inside an average?
Who possesses the authority to declare the project successful?
Who may experience harm without having the power to stop it?
These questions do not replace commercial or operational analysis.
They make it more complete.
Why People Do Not Always Raise the Risk
A pre-mortem only works if people can say what they actually see.
That requires psychological safety.
In many organisations, people do not remain silent because they have no concerns.
They remain silent because expressing those concerns carries risk.
A junior employee notices an operational weakness but assumes the senior team has already considered it.
A community partner doubts the proposed approach but does not want to threaten future funding.
A freelancer recognises that the timetable is unrealistic but fears losing the contract.
A staff member knows the AI-generated output is unreliable but worries about appearing resistant to innovation.
A trustee questions the demand forecast but does not want to undermine the founder’s enthusiasm.
Power affects which risks become speakable.
A pre-mortem should therefore be designed to reduce the personal cost of disagreement.
That might involve:
collecting concerns independently before group discussion;
allowing anonymous contributions where appropriate;
asking senior leaders to speak last;
inviting external challenge;
separating idea ownership from facilitation;
or ensuring community participants can contribute in formats that work for them.
If the person with the greatest authority defines the failure first, everyone else may simply elaborate their view.
The exercise then becomes performance rather than investigation.
The Founder Should Not Defend the Idea During the Exercise
This can be difficult.
Someone says:
“The project failed because the audience never understood what it was for.”
The founder responds:
“But the marketing plan explains that.”
Someone says:
“The price was too high.”
The founder says:
“Competitors charge more.”
Someone says:
“The community did not trust us.”
The project lead says:
“We have worked in the area for years.”
Each response may contain useful information.
But immediate defence changes the atmosphere.
People begin editing what they say.
During the initial generation of failure explanations, the idea owner should listen.
Clarification can come later.
The purpose is not to agree with every concern.
It is to make the concerns visible before deciding what they mean.
Look Across the Whole Proposition
Failure rarely belongs to one category.
A pre-mortem should examine the proposition from several directions.
Commercial
Did enough people want the offer?
Did they understand it?
Did they value it at the proposed price?
Did interest convert into purchase?
Did people return?
Did the organisation depend too heavily on one customer, channel or source of demand?
Financial
Were costs understood?
Was sufficient working capital available?
Did payment delays create pressure?
Was the pricing sustainable?
Did the model depend on unpaid or underpaid labour?
Could the organisation absorb an unexpected expense?
Operational
Could the team deliver consistently?
Were roles clear?
Did the timetable reflect reality?
Did success create more demand than the organisation could handle?
Were important processes concentrated in one person’s knowledge?
Technological and AI-related
Did the technology perform reliably outside the demonstration?
Was the underlying data suitable?
Were human checks realistic at the expected volume?
Did integration create hidden costs?
Did the organisation become dependent on a supplier whose product, price or terms changed?
Could staff recognise when the system was wrong?
Cultural
Did the organisation understand the people and context surrounding the idea?
Did its language carry meanings it had not recognised?
Did the proposition assume that a diverse group shared one preference?
Did participation require trust that had not been established?
Were histories, identities or power relationships treated as secondary details?
Ethical
Could the proposition create harm even while meeting its commercial objectives?
Were people adequately informed?
Was data used responsibly?
Were participants asked to contribute knowledge without fair recognition or benefit?
Did the organisation promise inclusion without transferring meaningful influence?
Reputational
What promise did the organisation make?
What would happen if the experience contradicted it?
Could one poorly handled incident reveal a larger gap between the brand and its behaviour?
Was the organisation prepared to respond openly if something went wrong?
These categories overlap.
That is precisely the point.
A technical failure can become a reputational failure.
A cultural misunderstanding can reduce participation.
Low participation can undermine funding.
Funding pressure can lead to operational shortcuts.
Those shortcuts can damage trust.
Failure often travels through a system.
Symptoms Are Not Root Causes
Suppose a programme fails because attendance is low.
That is a result.
It is not yet an explanation.
Why was attendance low?
Perhaps people did not know about the programme.
Why?
The promotional channels did not reach them.
Why?
The organisation relied on its existing mailing list.
Why?
The team assumed the intended participants already had some relationship with the institution.
Now the root issue may not be “poor marketing.”
It may be an untested assumption about who the organisation already reaches.
Or consider a product launch.
The immediate explanation is:
Sales were disappointing.
Why?
Website conversion was low.
Why?
Visitors did not understand why the product cost more than available alternatives.
Why?
The brand communicated materials and craftsmanship but did not explain the value those differences created for the customer.
Again, the symptom and cause are different.
A useful pre-mortem keeps asking:
What allowed this to happen?
Map the Failure Chain
Many failures develop through chains rather than single events.
For example:
A key partner delays confirming participation.
↓
The project team postpones promotion because important details remain uncertain.
↓
The booking period becomes shorter.
↓
Early registration is weak.
↓
The organisation increases advertising expenditure.
↓
Acquisition costs rise.
↓
The budget loses its contingency.
↓
A later production expense cannot be absorbed.
The final financial problem began with a partnership dependency.
Without mapping the chain, the organisation might respond by increasing the marketing budget.
That would address a later symptom while leaving the original vulnerability intact.
A failure-chain map asks:
What happened first?
What did that make more likely?
Which dependency transmitted the problem?
At what point could the chain have been interrupted?
The answer identifies possible safeguards.
Dependencies Deserve Particular Attention
A dependency is something the proposition needs but does not entirely control.
Examples include:
a venue;
a software platform;
a funder;
a distribution partner;
a specialist supplier;
a community relationship;
a particular employee;
a social-media channel;
a regulatory approval;
a licensing agreement;
or a founder’s continuing availability.
Some dependencies are unavoidable.
The important questions are:
How important is this dependency?
How visible is its status?
What would happen if it became unavailable?
How quickly would we know?
Do we have an alternative?
A project can appear robust until one quiet dependency disappears.
Example One: The Creative Founder
Imagine a ceramic artist planning a premium limited collection.
The proposed launch includes:
a professionally designed online shop;
high-quality photography;
special packaging;
a paid social campaign;
and an initial production run of 120 pieces.
The pre-mortem prompt is:
It is six months after launch. The collection has not recovered its production and marketing costs. What happened?
Possible explanations emerge.
The audience admired the work but considered the price too high.
The artist’s existing followers were interested in the process but were not collectors at this price level.
Packaging costs were underestimated.
Breakages increased replacement and delivery costs.
The production run consumed so much time that the artist could not maintain other income.
The launch attracted one-time attention but created no mechanism for continuing discovery.
The photography communicated visual quality but not scale, weight or material detail.
International interest existed, but shipping costs prevented purchase.
Several of these risks connect.
A large production run increases financial exposure.
The production workload reduces other income.
Weak conversion leaves more unsold stock.
Storage then becomes another cost.
The founder does not need to abandon the collection.
The pre-mortem may suggest a different next step:
produce a smaller numbered edition;
test the proposed price through pre-orders;
show the work physically to potential collectors;
validate packaging and delivery with a short shipping test;
and define the sales threshold required before producing the remaining pieces.
The exercise has not made the idea less ambitious.
It has made the commitment more proportionate to the evidence.
Example Two: The Cultural or Community Programme
Imagine a cultural organisation developing a weekend programme intended to involve families from nearby communities that have historically had limited engagement with the venue.
The programme includes workshops, performances and a final public event.
The pre-mortem prompt is:
The programme was delivered, but participation from the intended communities was low and relationships were weaker afterwards. What happened?
Possible explanations include:
The organisation designed the programme before speaking with intended participants.
The programme timing conflicted with work, care or religious commitments.
The venue was geographically close but did not feel socially welcoming.
Promotional language described communities as people to be “engaged” rather than people already creating culture.
The project depended on community organisations to recruit participants without paying for their time.
Accessibility was treated as a final delivery detail rather than part of programme design.
The organisation measured attendance but not influence.
People contributed ideas during consultation but could not see how those ideas changed the programme.
The final event generated strong photographs and reporting material, while participants experienced little continuing benefit.
This example shows why success measures matter.
The programme could meet an output target and still fail relationally.
A stronger response might include:
paid early involvement from community partners;
shared definition of outcomes;
accessible timings and formats;
clear communication about which decisions participants can influence;
budget for relationship-building rather than recruitment alone;
and an agreed continuation or closure process.
The pre-mortem reveals that the primary risk may not be attendance.
It may be trust.
Example Three: The AI-Enabled Small Business
Imagine a small professional-services company introducing an AI assistant to answer customer questions, draft proposals and summarise client information.
The expected benefits are faster responses and lower administrative pressure.
The pre-mortem prompt is:
Nine months after implementation, the organisation has restricted the system after several customer complaints and a significant loss of staff confidence. What happened?
Possible causes include:
The assistant generated plausible but inaccurate answers.
Staff relied on summaries without checking the underlying information.
Sensitive client material entered workflows that had not been properly governed.
Customers could not tell when they were interacting with an automated system.
The AI reproduced outdated service information.
The promised time saving disappeared because employees had to correct poor outputs.
Management measured the quantity of generated work but not the quality of decisions.
Staff concerns were interpreted as resistance rather than operational evidence.
The business became dependent on a tool whose pricing changed.
Responsibility for errors remained unclear.
A superficial response would be:
Improve the prompt.
The deeper pre-mortem reveals a governance problem.
The organisation may need:
defined permitted and prohibited uses;
verified source material;
clear human review points;
records of consequential decisions;
customer disclosure where relevant;
staff training;
quality checks;
an incident process;
and a manual alternative if the system becomes unavailable.
The technology may remain useful.
But the operating system surrounding it needs to become more intelligent.
Prioritise Without Pretending to Know More Than You Do
A pre-mortem can produce a long list of possible failures.
Not all deserve equal attention.
A practical review can examine three questions.
How plausible is this?
Does the concern follow from current evidence, known dependencies or credible experience?
How consequential would it be?
Would it create a minor inconvenience, require substantial revision or threaten the proposition?
How preventable or manageable is it?
Can the risk be reduced through a reasonable action now?
The purpose is not to produce a scientific-looking score unsupported by data.
Terms such as low, medium and high may be sufficient if the reasoning is recorded.
The discussion matters more than artificial numerical precision.
A low-probability risk with catastrophic consequences may still require preparation.
A highly likely inconvenience may be accepted.
A moderate risk that can be cheaply prevented may deserve immediate action.
Judgement remains necessary.
Not Every Risk Should Be Eliminated
Innovation involves uncertainty.
Attempting to remove every risk can remove the possibility of doing anything new.
The objective is not zero risk.
It is conscious exposure.
For each priority risk, an organisation may decide to:
Prevent
Change the proposition so the failure becomes less likely.
Mitigate
Reduce the probability or consequence.
Transfer
Use insurance, contracts, specialist support or another mechanism to allocate part of the risk elsewhere.
Accept
Acknowledge the risk because the cost of addressing it exceeds the likely harm or because uncertainty is unavoidable.
Test
Run a small experiment before making a larger commitment.
Revise
Change the audience, price, model, scale, timing or delivery method.
Pause
Delay commitment until a critical uncertainty can be resolved.
Stop
Conclude that the proposition is no longer credible or responsible enough to justify further investment.
The important thing is that the risk produces a decision.
A pre-mortem that generates anxiety but no action has not completed its work.
Early-Warning Signals
One of the most valuable outputs of a pre-mortem is an early-warning system.
Suppose the imagined failure is:
The pilot launches, but there is insufficient demand.
Possible warning signals might include:
few people completing expressions of interest;
high attention but low movement towards booking;
frequent questions indicating that the proposition is unclear;
positive feedback without behavioural commitment;
or strong demand only after substantial discounting.
Or suppose the imagined failure is:
The team becomes unable to deliver the service consistently.
Warning signals might include:
missed internal deadlines;
increasing reliance on unpaid overtime;
quality checks being skipped;
customer responses slowing;
or knowledge becoming concentrated in one person.
An early-warning signal should be observable.
“Things feel difficult” is too vague.
“Three consecutive delivery deadlines are missed” is clearer.
A signal does not automatically prove that failure is coming.
It tells the organisation to look more closely.
A Signal Needs a Trigger Point
Monitoring alone is not enough.
The organisation should decide what it will do if the signal appears.
For example:
If fewer than twenty people register interest by the first review date, conduct interviews before committing the full production budget.
If the cost per confirmed participant exceeds the agreed limit, revise the recruitment approach.
If error rates in AI-generated customer responses exceed the acceptable threshold, suspend unsupervised use.
If the delivery team exceeds its agreed capacity for two consecutive weeks, pause new sales.
If a key partner has not confirmed by the decision date, activate the alternative venue plan.
These are trigger points.
They prevent the organisation from repeatedly noticing a warning and then continuing unchanged because momentum has taken over.
Give Each Safeguard an Owner
“Improve accessibility” is not an action.
“Review the budget” is not an action.
“Monitor AI quality” is not an action.
Each priority safeguard needs:
an owner;
a deadline;
a clear output;
a review point;
and, where relevant, a trigger.
Without ownership, risk management becomes a collective intention for which nobody is responsible.
This is particularly important in small organisations, where everyone may assume the founder is holding the entire system.
The founder may be the least able to monitor every risk while also delivering the idea.
Do Not Turn the Exercise Into Blame
A poorly facilitated pre-mortem can become an opportunity to assign future fault.
“The marketing team failed to promote it.”
“The community did not engage.”
“The staff resisted the technology.”
“The artist did not produce enough work.”
“The partner let us down.”
These statements locate failure inside a person or group without examining the system surrounding their actions.
A better question is:
What conditions made this outcome possible?
Perhaps marketing began late because the proposition remained unclear.
Perhaps participation was low because the organisation designed access around its own convenience.
Perhaps staff resisted the technology because they understood operational risks leadership had ignored.
Perhaps the production target was incompatible with the artist’s actual capacity.
Perhaps the partnership failed because responsibilities were never formalised.
Accountability matters.
But blame can stop investigation too early.
Beware Performative Pessimism
There is another danger.
A team may generate an impressive list of disasters because that is what the exercise appears to require.
The list becomes theatrical.
The organisation imagines catastrophic press coverage, total market collapse, technological breakdown and every partner withdrawing simultaneously.
Everyone leaves feeling that the idea has been thoroughly challenged.
Nothing useful changes.
This is performative pessimism.
It mistakes dramatic imagination for decision intelligence.
A strong pre-mortem remains connected to the proposition.
It asks:
What failure pathways are plausible enough to deserve attention?
What evidence supports the concern?
What would we observe first?
What can we do now?
The objective is not to frighten the team.
It is to improve the decision.
The CIS Pre-Mortem Framework
A Cultural Intelligence Studio pre-mortem can be organised into nine stages.
1. Define the Decision
What commitment is currently being considered?
Launch?
Investment?
Funding application?
Technology adoption?
Partnership?
Full-scale production?
2. Define Failure
What would failure mean commercially, operationally, culturally, ethically and reputationally?
Whose definition has been included?
3. Move Into the Future
Choose a realistic point in time.
State clearly:
The idea has failed. What happened?
4. Generate Independently
Ask each participant to record possible causes before group discussion.
This reduces conformity and allows quieter concerns to appear.
5. Build the Failure Chains
Connect symptoms to causes.
What happened first?
What did it trigger?
Which dependency transmitted the problem?
6. Examine the Whole System
Review commercial, financial, operational, technological, cultural, ethical and reputational dimensions.
Ask whose experience or risk may be missing.
7. Prioritise
Which risks are plausible, consequential and capable of changing the decision?
Which are preventable or testable?
8. Design Safeguards
Identify prevention, mitigation, testing, alternatives, owners and early-warning signals.
Establish trigger points.
9. Reassess the Decision
Does the idea now justify:
Proceed?
Revise?
Pause?
Stop?
The pre-mortem ends where better judgement begins.
What the Pre-Mortem Adds to the Simulation Lab
Within the Cultural Intelligence Simulation Lab, the pre-mortem is one layer of a larger decision process.
The Evidence Ledger distinguishes what is known from what remains assumed.
Load-bearing assumption analysis identifies what must be true.
The Red Team challenges the proposition from an intelligent opposing position.
Scenario thinking examines the idea across several plausible futures.
The pre-mortem then asks:
If this idea nevertheless failed, how did the failure develop?
Each method produces different intelligence.
The pre-mortem is especially valuable because it turns abstract risk into sequence.
It helps reveal:
hidden dependencies;
weak safeguards;
unspoken concerns;
early-warning signals;
and points where intervention remains possible.
Those findings can then shape the CIS Decision Report, the next tests and the final direction:
Proceed.
Revise.
Pause.
Stop.
A Pre-Mortem Can Strengthen Confidence
This may appear contradictory.
How can imagining failure increase confidence?
Because confidence becomes more credible when it survives challenge.
There is a difference between saying:
“We are confident because we believe in the idea.”
and:
“We are confident because we have examined how the idea could fail, tested its most important assumptions, reduced avoidable risks and established what we will do if conditions change.”
The second confidence is less dramatic.
It is also more useful.
It does not claim certainty.
It shows preparedness.
Sometimes the Failure Reveals a Better Idea
A pre-mortem does not always lead to more safeguards around the original proposition.
Sometimes it reveals that the proposition itself should change.
The artist planning 120 pieces discovers that scarcity and pre-ordering create a stronger model.
The cultural organisation discovers that its intended participants should become paid programme partners.
The small business discovers that AI should support internal preparation rather than communicate directly with customers.
The founder discovers that the audience values a smaller part of the service more than the full package.
The community project discovers that the problem it intended to solve was defined from the institution’s perspective rather than the community’s.
These are not merely risk controls.
They are strategic improvements.
The imagined failure creates enough distance for another version of the idea to become visible.
When the Result Is Stop
There will be occasions when the pre-mortem exposes a weakness that cannot be responsibly managed.
Perhaps the model requires a level of demand for which no credible evidence exists.
Perhaps the project depends on a partner who cannot commit.
Perhaps the economics only work through unpaid labour.
Perhaps the technology introduces risks the organisation cannot govern.
Perhaps community trust cannot be established within the proposed timescale.
Perhaps the potential harm is disproportionate to the benefit.
In those circumstances, stopping can be the most intelligent result.
The organisation has not failed to be courageous.
It has refused to confuse momentum with wisdom.
Resources remain available for a stronger opportunity.
Reputation is protected.
Relationships are not placed under avoidable pressure.
Time is recovered.
Stopping before commitment can be one of the most valuable outcomes a simulation produces.
Conclusion: Give the Idea a Chance to Fail Safely
Every serious idea deserves belief.
But belief should not require blindness.
Before launching, investing, producing, announcing or promising, create a space in which the idea is allowed to fail imaginatively.
Let the customer say no.
Let the venue become unavailable.
Let the budget tighten.
Let the technology make a mistake.
Let the partner withdraw.
Let the community interpret the proposition differently.
Let the team reach capacity.
Let the public promise encounter the operational reality.
Then look closely at what happens next.
Where does the failure begin?
Which assumption is carrying too much weight?
Which dependency has no alternative?
Which person recognised the risk but did not feel able to say it?
Which warning would appear first?
What safeguard could interrupt the chain?
What evidence would justify greater confidence?
What needs to change before the organisation commits?
The point is not to become pessimistic.
It is to become prepared.
A pre-mortem gives optimism a structure strong enough to withstand disagreement.
It separates the value of the person from the vulnerability of the proposition.
It turns fear into questions.
Questions into risks.
Risks into signals.
Signals into actions.
And actions into better decisions.
Ideas rarely need protection from every possible future.
They need protection from the failures that were visible early enough to address but remained unspoken, unexamined or mistaken for somebody else’s responsibility.
Imagine the idea failed.
Not because you expect it to.
Because while the failure remains imaginary, you still have the power to change what happens next.
Continue Exploring
This article is Part Six of Before You Commit, a Cultural Intelligence Studio series exploring evidence, assumptions, proportionate testing, constructive challenge, scenario thinking, pre-mortems and better decisions under uncertainty.
Previous Article
One Idea, Several Futures
Why Scenario Thinking Is More Useful Than Pretending You Can Predict What Happens Next
Article Five explored how one proposition can behave across different plausible futures—and how changing demand, costs, participation, technology and external conditions can expose hidden dependencies.
Next Article
How Much Evidence Is Enough?
Setting Decision Thresholds Before Hope, Fear or Momentum Make the Choice for You
Article Seven will examine how organisations decide when they have learned enough to proceed, revise, pause or stop. It will explore decision thresholds, acceptable uncertainty, evidence standards, trigger points and why the criteria for commitment should be established before the results arrive.
Explore the Cultural Intelligence Simulation Lab
The Cultural Intelligence Simulation Lab helps founders, artists, creative entrepreneurs, cultural and community organisations, and small businesses test promising ideas before major commitment.
It combines evidence analysis, cultural lenses, Red Team challenge, scenario thinking, pre-mortems and proportionate experiments to produce a clearer decision:
Proceed. Revise. Pause. Stop.