Remember the Future

When to use

Project kickoff, quarterly planning, anything bigger than a sprint. Run it before pre-mortem to paint the win, then run pre-mortem to surface the threats. Skip it for incremental work where 'success' is obvious. Skip it on teams that won't hold the past-tense grammar — without the discipline the exercise collapses into a wishlist meeting and produces nothing actionable.

How it runs

1. Pick the timeframe deliberately

   Six weeks is a sprint. Six months is a project. Six years is a strategy. Different timeframes produce different exercises; pick the one that matches the decision the meeting needs to inform. State the date out loud — 'today is November 15th, six months from now' — and hold the team to it.

2. Frame the press release

   Imagine it's the date you picked. Something good happened — write the press release. Two paragraphs, past tense. 'On October 14th, the platform team shipped X. The release reduced Y by Z percent. Customers reported A.' Concrete numbers, named outcomes, past tense.

3. Silent write, fifteen minutes

   Each person writes their own version. Independent writing is the format — group writing produces consensus on the safest version of success, not the actual one. Past tense throughout, no exceptions. The grammar enforces specificity.

4. Read aloud, cluster the consistent details

   Read each press release. Note the details that show up in three or more — those are the team's shared picture of success. The disagreements are equally interesting; surface them, don't paper over them. Two people writing 'we shipped on time' and two writing 'we shipped six weeks late but with the right scope' is a real disagreement that needs resolving now, not in month four.

5. Reverse-engineer the path

   Once the team has agreed on what success looked like, work backwards. 'For the customer quote in the release to exist, what had to happen by month five? Month four? Month one?' This is the planning artefact you came for — the press release is the prompt, the reverse path is the output.

Why it works

Backward inference is cognitively richer than forward speculation. Asked 'what should we do?' people produce a wishlist; asked 'what did we do, looking back from success?' people produce a plan. The grammar is the format's enforcement mechanism — past tense forces specificity ('we shipped' demands a what, when, and how) where future tense permits vagueness ('we will ship' tolerates a wave of the hand). The press-release framing borrowed by Amazon is the tightest version of this: a customer-quote requirement forces the team to name a real outcome.

Variations

• Working-backwards memo (Amazon's variant) — same idea, longer document, includes a hypothetical FAQ. Worth the time on six-month or longer projects.
• Tweet-from-the-future variant — write a 280-character tweet describing the shipped outcome. Faster, more memorable, weaker on detail.
• Customer-testimonial version — write the quote a customer would give six months out. Especially sharp for product teams; forces customer-language thinking.
• Pair with pre-mortem in a single workshop: Remember the Future first (paint the win), pre-mortem second (name the threats). Two halves of the same kickoff.

Facilitator notes

Hold the past tense ruthlessly. Every present-tense or future-tense sentence is a ducked question — 'we ship reliably' is a value statement, not a memory. Push back gently and consistently. The senior person on the project should write last and read last; their press release sets the room's ceiling and you want the team's picture, not the boss's. If the press releases are uniformly vague, stop and re-prompt — 'name a number, name a date.'

Pitfalls

• Present-tense sentences. The grammar is the format; without it you've run a values workshop.
• Group writing. Consensus on the safest version of success is not the team's actual picture.
• Skipping the reverse-engineering step. The press release alone is theatre — the path back is the artefact.
• Picking too short a timeframe. Six weeks rarely produces enough surface area; six months is the practical floor for the format to do real work.

Remote tips

Async-first wins. Give the team 24 hours to write their press releases independently before the live session, then meet for 30 minutes to read aloud and reverse-engineer. Live writing on a video call produces thinner releases — the time pressure pushes people to safe content.

Example outputs

• 'On October 14th, the platform team shipped passwordless auth across all customer-facing apps. Login time dropped from 11 seconds to 2. The support team logged a 40% drop in password-reset tickets. The CEO sent a Friday email titled "Best login flow in the industry."'
• 'On November 1st, we sunset the legacy billing system. Migration ran across nine weekends without a single Saturday page. The finance team archived the old codebase ceremonially.'
• Wishlist-version (don't accept this): 'We will have a great release. The team will be proud of it. Customers will love it.' No date, no number, no detail. Send it back and ask for the press release.

FAQ

Remember the Future or Pre-mortem?

Run both. They're siblings. Remember the Future surfaces what success looks like; pre-mortem surfaces what could kill it. Either alone is half the picture. Order: Remember the Future first (paint the win), pre-mortem second (name the threats to it). The strongest pre-project facilitation runs both at kickoff.

Remember the Future or Hopes/Fears (the hopes column)?

Hopes/Fears collects wishes; Remember the Future collects evidence-of-success in past tense. The grammar is the difference. 'I hope we ship on time' is a wish; 'we shipped on November 1st with the right scope' is a memory of a possible future. Remember the Future produces concrete plans; Hopes/Fears produces emotional alignment. Pick by which output you need.

How long a timeframe should I pick?

Six weeks for sprint planning, six months for a project, six years for strategy. Match the timeframe to the decision the meeting needs to inform. Too short and the exercise is trivial; too long and it's science fiction. Six months is the most common useful default.

Related activities

Recommended use cases