Futurespectives

What it is

Futurespectives invert the retro: instead of asking what went wrong, they ask what is going to. Hopes and Fears, pre-mortems, Remember the Future — variants of the same move. They work because people will name a future risk that they wouldn't name as a present complaint, and because the artefact gives the team a list to come back to at the project's halfway point. The two formats that matter are siblings — pre-mortem (failure-focused, threat-surfacing) and Remember the Future (success-focused, path-engineering). Either alone is half the picture.

When to use

The week before a project kicks off. The day a new team forms. After a re-org, when nobody quite knows what the new normal is. Skip them mid-project — by then the failure modes are no longer hypothetical and a regular retro is the right tool. Skip them on a team in active conflict; the fears column will be a vehicle for the conflict, not the project. And skip the pre-mortem if you can't enforce anonymity — without it, the senior person's fears anchor the room and you've measured the senior person's fears, not the team's.

Which one to pick

Project kickoff, want to surface risks

Pre-mortem. Anonymous or you wasted the meeting. Pair with Remember the Future.

Project kickoff, want to align on success

Remember the Future. Press release dated six months out — concrete plans beat emotional alignment.

Project kickoff with a new or post-conflict team

Hopes and Fears. Lower-stakes than pre-mortem; the fears column is anonymous; the hopes column is the warm-up.

Cross-functional kickoff with legal, exec, or compliance stakeholders

Hopes and Fears. 'Mortem' lands wrong outside engineering — same shape, gentler register.

Engineering-led project where directness is welcome

Pre-mortem. Run it after Remember the Future — paint the win first, name the threats second.

Strongest pre-project facilitation pattern in the catalogue

Run Remember the Future then Pre-mortem in one workshop. Either alone is half the picture.

Common mistakes

• Skipping anonymity on the pre-mortem. The senior person's fears anchor the room; juniors write polite versions of the same and the real risks never appear.
• Running a futurespective mid-project. By then failures are real, not hypothetical. A regular retrospective is the right tool.
• Stopping at 'discuss findings.' Without owners and dates on the top threats, the meeting is a fear-collection exercise — pre-mortem theatre.
• Picking only one of pre-mortem or Remember the Future. They're siblings, not substitutes — pre-mortem maps the threats, Remember the Future maps the path.
• Running it on a team in active conflict. The fears column becomes the vehicle for the argument and the project gets buried.

All futurespectives