Login

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

What the team wants this project or cycle to become

Roman

Roman

That we ship the migration without a weekend release
Maria

Maria

That the new hire feels productive by the end of month one
Fears

What could go wrong — said out loud while it is still cheap

Anna

Anna

That peak season traffic finds the bottleneck for us
Daria

Daria

That the scope keeps growing and nothing gets finished
Try Template

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.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
Good Bad Better Best
A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.
Likes / Wishes / Wonders
A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.
OKR Template
A goal-focused format that ties reflection to objectives and key results. The team reviews its objectives, examines the key results that measure progress and aligns on the initiatives that will drive them forward. It's a strong choice for connecting day-to-day retrospectives with the bigger goals the team is accountable for.
Retrospective Template: WWW
A nuanced take on the classic what-went-well format that adds a middle ground. Instead of a strict worked-or-didn't split, the team also captures what kinda worked — the partial successes and half-measures. That extra shade often holds the most useful insights, where small adjustments can turn a near-miss into a win.
Safety Check for Retrospective
A short anonymous poll that measures how safe people feel to speak openly before the real retrospective begins. Everyone rates their comfort from 1 to 5, and the aggregated result tells the facilitator whether the team is ready for candid conversation. It's a valuable warm-up for new teams or after tense periods, where psychological safety can't be taken for granted.
Fishbone Analysis Retrospective Template
Also known as the Ishikawa diagram, this format helps the team trace a problem back to its root causes. Possible causes are grouped across categories like people, process, tools, program and environment before the team converges on solutions. It's a methodical choice when a recurring issue needs a structured investigation rather than a quick fix.
Try Template