Decide Under Pressure

Find the best move when options are limited.

Decide Under Pressure

What this fixes

Half your team has just been reassigned. The deadline hasn’t moved. Within minutes, everyone is suggesting solutions - but every idea seems to hit the same invisible wall.

The real barrier is usually somewhere else. It’s not the constraint - it’s the barrier underneath: nobody really believes it can be done, the team can’t agree on what to drop, no one owns the hard calls. This activity surfaces that barrier first - before the team spends its energy planning around the wrong problem.

How this works

Imagine your team’s budget has just been cut by 25%, but the deadline and quality standards hold.

Before anyone suggests a solution, everyone privately answers one question: it’s six weeks from now, and the team couldn’t adapt - why? The answers go up on a board and cluster into the real barriers. The team then forces one to the top: the barrier most likely to derail the response. That - not the constraint - is what to deal with first.

Time required

Team ✓ · About 25–30 minutes, with a facilitator

The time required is indicative and will depend on the nature of the problem and the size of the team.

The facilitator should read the short facilitation guide first - about 10 minutes. It’s a downloadable PDF on this page.

When to use

Use it the moment a real constraint arrives and the team is about to jump into “what do we do?” - a budget cut, a deadline brought forward, a key person or resource removed, a scope increase, a new rule the team must absorb.

What you get

  • The one barrier most likely to stop the team from adapting - named out loud
  • A shared understanding that the constraint isn’t the real problem
  • A team ready to plan against the right problem, not the obvious one

You have done it well when: the team agrees on the single biggest barrier to adapting - even though it hasn’t made a plan yet. Finding the barrier is the win.

What you’ll notice

  • The real barrier is rarely the constraint everyone was focused on
  • People will name a future failure they’d never admit as a present fear
  • The barrier is often about belief, agreement, ownership, or decision-making - not just the constraint itself
  • Once the barrier is named, planning usually becomes much simpler

Why this works

People defend the present. They explain the future more honestly. Imagining failure six weeks out makes the hidden barrier - the belief, the disagreement, the missing owner - much easier to say out loud.

What you need

A board. Any whiteboard or wall - where the failure reasons are posted and grouped into barriers.

Sticky notes. A pad for each person - one reason per note, so everyone writes privately before anything goes up.

A few markers. People write their own notes; the facilitator uses one to name the clusters and mark the top barrier.

Roles

Facilitator  Keeps time, runs the premortem, clusters the answers on the board, and holds the team to one barrier - not a plan.

Team  Each person writes their own failure reasons, then helps cluster and rank them to the single biggest barrier.

Steps

  1. Name the constraint (3 min). The facilitator writes the live constraint on the board in one line - for example, “Our budget has been cut by 25%, but the deadline and quality standards hold.”
  2. Run the premortem (7 min). Everyone works alone and silently. Answer one question:
  • “It’s six weeks from now. The team failed to adapt to this constraint. Why?”
  • Write what stopped the team from responding well. Focus on the team’s response - not the constraint itself, and not what happened to the team. Up to 3–5 reasons, one per sticky note. Write the real version. Not the polite one.

Good: “nobody believed the target was achievable” · “we couldn’t agree how to respond” · “nobody owned the hard decisions” · “we kept waiting for perfect information”.

Avoid: the constraint restated (“the budget was cut”) or outside events (“the customer changed requirements”, “a vendor failed”). Those happened to the team - they’re not how the team responded.

  1. Post and cluster (5 min). Everyone puts their notes on the board. The facilitator groups similar notes together into clusters and names each one - for example: “nobody believed it was possible”, “couldn’t agree what to cut”, “no one owned the hard calls”.
  2. Force one barrier to the top (7 min). As a team, answer one question: which of these would kill us first? Force one cluster to the top - not a ranked list, one barrier. Settle ties by asking which one makes all the others worse.
  3. Name the barrier (3 min). The facilitator says it plainly: the constraint was never the real problem - this barrier is. Write one barrier on the board. Stop here. Don’t start solving - finding the barrier is the outcome.

Output / Takeaways

  • The single biggest barrier to adapting, named and agreed
  • The other barriers, captured for later
  • A shared view that the constraint wasn’t the real problem

The facilitator photographs the final board and sends it to all participants before everyone leaves.

Important rules

  • Use a real, live constraint - not a hypothetical one
  • Start with failure, not solutions - the premortem comes before any planning
  • Everyone writes their own reasons first - alone, no discussion
  • Force one barrier to the top - not a ranked list
  • Stop at the barrier - don’t drift into making the plan
  • Finding the barrier is success, even with no plan yet

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.