Prioritise Under Pressure

Prioritise what matters most under pressure.

Prioritise Under Pressure

What this fixes

Under pressure, people don’t see the same priorities. They’re looking at different work, different risks, and different consequences - so the team can’t agree what comes first.

The problem usually isn’t disagreement. It’s that nobody is looking at the same picture. This activity makes those differences visible before the team commits to a plan.

How this works

Imagine this: your team has capacity for three initiatives, but seven urgent requests are pending. Every request sounds important, and the conversation keeps going in circles.

Everyone creates their own priority list first - alone, one task per sticky note - and decides where “now” ends and “later” begins.

The lists then go up side by side, so the team can see the differences. The team talks them through, builds one shared priority list, draws one now-line, and commits.

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 must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Use a real, live problem - a project breakdown, an urgent deadline, an escalation - any moment when the team has too many competing priorities and must decide what comes first.

What you get

  • A clear view of where the team agrees - and where it doesn’t
  • One shared order: what to do first, second, and third
  • A now-line: what gets done now and what waits
  • An owner and a timeline for every task above the now-line

You have done it well when: the team has seen how differently each person read the situation, and still leaves with one agreed order and one clear next move.

What you’ll notice

  • People were responding to the same problem, but prioritising it differently
  • People were looking at different work - not just a different order
  • The gaps between lists create the most useful discussion
  • Once the team is looking at the same picture, agreeing the order becomes surprisingly easy

Why this works

Different people notice different risks, so they quietly build different priority lists. Writing those lists alone first makes the differences visible - before the most dominant voice shapes the discussion.

What you need

A board   Any whiteboard or wall with space for several task lists side by side, and a line drawn across them.

Sticky notes   A pad for each person - one task per note.

A few markers   Most rooms have a few. Everyone can write and draw their own line; the facilitator draws the final shared one.

Roles

Facilitator   Keeps time, surfaces the differences between lists, and holds the team to one shared order.

Team   Each person writes their own tasks and draws their own line, then helps build one shared list.

Steps

  1. Name the goal (2 min). The facilitator states the live pressure and the goal in one line - for example, “Restore service as fast as possible.”
  2. Write the tasks (5 min). Everyone works alone and silently. Write the 3–5 most important team tasks needed to achieve the goal - one per sticky note.
  • Write team tasks, not your personal to-dos. Think about the situation as a whole.
  • Decide your own order, and where your now-line should be - but don’t draw it yet.

For example, if the goal is “meet a deadline shortened by three weeks”, you might write: re-cut scope · identify critical dependencies · secure extra resources · freeze new requests.

  1. Put every list on the board (3 min). Each person posts their notes in the order they chose, highest at the top, then draws their now-line on the board where they’d decided - the line that separates what must happen now from what can wait. All lists go up side by side.
  2. Reveal the differences (4 min). The facilitator points out tasks that appear on only one list, different top priorities, and now-lines drawn in different places.
  3. Talk through the gaps (7 min). For each difference, ask: why is this above your line but below theirs? What breaks if it waits? The aim is to understand the differences, not to win.
  4. Build one shared order (4 min). Merge duplicate tasks into one list. Rank it - no ties - settling any disagreement with “what breaks if we don’t do it now?” If two tasks depend on each other, place them next to each other rather than arguing which is first. Draw one shared now-line.
  5. Commit (3 min). Assign an owner and a timeline to every task above the now-line. Say out loud what the team is not doing right now. The facilitator photographs the board and sends it to everyone.

Output / Takeaways

  • The shared, ordered list of tasks
  • One now-line showing what happens now versus later
  • An owner and a timeline for every task above the now-line
  • The work that is postponed, named

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

Important rules

  • Use a real, live, urgent problem - not a routine plan
  • Everyone writes their own list first - alone, no discussion
  • Don’t explain your list while writing it - build it first, discuss it later
  • Write team tasks, not personal to-dos
  • The differences between lists are the point - surface them, don’t skip them
  • Settle disagreements by asking what breaks if you wait - not by who feels strongest
  • No ties - one shared order
  • Name the tasks that are being postponed

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

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