Hopes and Fears

A forward-looking format best used at the start of a project, quarter or initiative. The team shares its hopes for what could go right alongside its fears about what might go wrong. Naming both early builds shared understanding and surfaces risks while there's still time to act on them.
Hopes
Fears

What is the Hopes and Fears retrospective?

The Hopes and Fears retrospective is a lightweight format for surfacing what a team wants to happen and what worries them, usually at the start of a project, a quarter, or a new initiative. It works best as an inception or kickoff exercise, but it is equally useful mid-flight when momentum stalls or uncertainty grows. By naming both aspirations and risks out loud, the team builds shared understanding, defuses unspoken anxiety, and turns vague feelings into concrete topics for action. The format uses two columns:

  • Hopes — what people want to achieve and the outcomes they are excited about.
  • Fears — concerns, risks, and things that could go wrong.

Hopes

In the Hopes column, each person writes what they genuinely want from the project or period ahead. These can be outcomes ("ship the new onboarding flow"), ways of working ("fewer last-minute changes"), or personal goals ("learn the payments stack"). Encourage specific, positive statements rather than generic wishes. Reading hopes aloud helps the team see where ambitions overlap and where individual motivations differ, which is invaluable when setting priorities.

Fears

The Fears column is where people voice what keeps them up at night: unclear scope, fragile dependencies, tight deadlines, or the risk of repeating past mistakes. Naming a fear is not pessimism — it is the first step to managing it. Group similar fears together, then decide which ones can be turned into mitigations, owners, or experiments. Many fears shrink simply by being said out loud and acknowledged by the group.

Benefits of the Hopes and Fears retrospective

  • Aligns the team on shared goals before work begins.
  • Makes hidden risks visible early, when they are cheap to address.
  • Builds psychological safety by normalizing honest concerns.
  • Creates a clear backlog of mitigations and action items.
  • Takes under 30 minutes, so it fits any kickoff.
  • Gives quieter team members an equal voice.

How to run a Hopes and Fears retrospective

  1. Create a board in QRetro from the Hopes and Fears template and share the link with your team.
  2. Set the context: explain the project or period the retro covers and what good looks like.
  3. Give everyone 5–7 minutes to add notes silently to the Hopes and Fears columns.
  4. Group similar cards, then read each cluster aloud and discuss patterns.
  5. Vote on the fears worth tackling and turn the top ones into owned action items.
  6. Save the board so you can revisit hopes and fears at the next checkpoint.
Try Template