Hopes and Fears

When to use

Project kickoff. New team forming. After a re-org, when nobody quite knows what the new normal is. Pre-merger, pre-migration, pre-anything-significant. Skip it mid-project — by then the failure modes are real, not hypothetical, and a regular retro is the right tool. Skip it on a team in active conflict; the fears column will be a vehicle for the conflict instead of the project.

How it runs

1. Set anonymity up front

   Tell the team the fears column is anonymous before they write. If you don't, the senior people's fears will anchor the room and the juniors will write thin agreement. This step is non-negotiable.

2. Silent write, eight minutes

   Each person writes one to three hopes and one to three fears. Hopes signed (or not — your call); fears unsigned. Use sticky-note tooling that hides authorship for the fears column.

3. Cluster Fears first, not Hopes

   Group duplicate fears. Read each cluster aloud — duplicates are the signal. If three people wrote a version of the same fear, that's the project's actual risk register starting to form.

4. Distinguish wishes from commitments in Hopes

   'Ship on time' is a wish. 'We'll do code review properly this time' is a commitment. The commitments column is the useful one — circle them.

5. Save the artefact for halfway

   Pin the board. Put a calendar invite at the project's halfway point to revisit. Most teams collect fears, then forget them; the calendar invite is the difference.

Why it works

Naming a fear is cheaper than naming a problem. People will write 'I'm worried this will slip into Q4' as a fear at kickoff who would never raise it as an objection in a planning meeting. The two-column structure also keeps it psychologically safe — the Hopes column lets people stay forward-looking, the Fears column catches the things they couldn't otherwise say.

Variations

• Hopes and Concerns — softer phrasing for a team that finds 'fears' melodramatic. Same activity.
• Add a third column, Assumptions, for the things the team is implicitly relying on. Useful when the project depends on another team you don't control.
• Run it as a check-in for a six-month project: Hopes/Fears at month one, again at month three, compare the lists.

Facilitator notes

The senior person on the project should not write first and should not read first. If the boss reads their fear out loud first, the rest of the room turns into a chorus. Mix the cards before reading; even with anonymous tooling, writing order can be guessed. And don't editorialise the fears as you read them — read them flat.

Pitfalls

• Skipping anonymity. If the boss can read who wrote what, you'll get a list of polite hopes and three fears about 'communication.'
• Letting Hopes turn into a wishlist nobody owns. Tag the commitments and ignore the wishes.
• Treating the fears as items to discuss-and-dismiss in the meeting. They're a watch-list, not a backlog.
• Forgetting to revisit at halfway. Without the comeback, the meeting was theatre.

Remote tips

Use a tool with explicit anonymous mode for the Fears column (Miro, FunRetro, Parabol all support this). Open the board 24 hours before the call so people write fears in private, not under live time pressure — fear cards written in 90 seconds are always thinner than fear cards written overnight.

Example outputs

• Fear: 'The auth migration in week six will collide with the platform team's release freeze and nobody's checked.'
• Fear: 'We don't have a clear owner for the data pipeline. We'll spend three weeks figuring out it's mine.'
• Hope (commitment): 'We'll merge by end of day or revert. No more week-long branches.'
• Hope (wish): 'Ship by Q3.' (Don't action this one.)

FAQ

Hopes and Fears or Sailboat-as-pre-mortem?

Hopes/Fears is a sit-down meeting; Sailboat-as-pre-mortem is a workshop. If you have 45 minutes, Hopes/Fears. If you have 90 and want a richer picture (winds, rocks, anchors, island), Sailboat. They're the same family of move at different scales.

Should I really make Fears anonymous?

Yes. Without anonymity it becomes Hopes and Mild-Concerns. The senior person's fear sets the ceiling for what anyone else writes — anonymity is the whole point.

What do we do with the Fears list?

Pin it. Put a calendar invite at the project's halfway point to revisit. Tick the ones that came true, mark the ones that didn't, talk about why. Without the comeback, the meeting was theatre.

Related activities

Recommended use cases