methodatlas
Method guideProduct Discovery

Working Backwards

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time4-8 h, mehrere Iterationen
Participants2-6
FormatWorkshop + async
MaturityEstablished
Plan Working Backwards
01

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Working Backwards are stated as a concrete question.

Without scope, PR/FAQ becomes arbitrary.
Complete firstAccess to relevant perspectives

Customer problem and evidence, strategic goals, technical and economic assumptions and domain decision makers are available.

Without these perspectives, central claims in PR/FAQ remain unsupported.
02

Preparation

What needs to be ready before start

Materials

Customer problem and evidence, strategic goals, technical and economic assumptions, shared workspace, source links, and decision log.

People / roles

Product lead · Customer/Research · Tech · Operations · Finance

Pre-read

Collect Customer problem and evidence, strategic goals, technical and economic assumptions in advance and mark open assumptions.

Time needed

Several writing and review rounds

Setup

Prepare future press release plus customer and internal FAQ visibly and calibrate assessment terms before starting.

03

Core question

The one question this method answers

What concrete customer benefit would make credible news, and which questions must be answered before building?

04

Flow

Phases with goal, actions, output and pitfall

Working Backwards states target customer, problem, benefit, experience, and evidence in a future press release. Customer and internal FAQs test hard questions, assumptions, operations, and economics.

PR/FAQ

Fictional worked example

future press release plus customer and internal FAQ as a precise working structure with a fictional example.

Customer/problem

Customer/problem information to record

Regulierte Projektleiter suchen stundenlang.

Press release

Press release information to record

Entscheidung in 30 Sekunden finden.

Customer FAQ

Customer FAQ information to record

Import, Rechte, Preis und Vertrauen beantwortet.

Internal FAQ

Internal FAQ information to record

Datenresidenz, Support und Unit Economics geprüft.

The example demonstrates the domain logic of Working Backwards; worksheets remain blank.

Amazon: Working Backwards

  1. 1

    Customer/problem

    Customer/problem

    Goal

    Produce customer problem so the core question “What concrete customer benefit would make credible news, and which questions must be answered before building?” can be answered with stronger support.

    Inputs for this step

    • Customer problem and evidence
    • strategic goals
    • technical and economic assumptions

    Actions

    • Specify target customer, situation, and evidenced problem.
    • Record source, rationale, and open uncertainty directly in customer problem.

    Output

    customer problem

    customer problem · source · uncertainty · next decision

    Quality check

    Is today's disadvantage concrete?

    Pitfall

    The press release becomes marketing copy and the FAQ defers hard risks to implementation. Use a concrete customer situation and evidence; mark hard questions with owner and decision date.

    Timing: 10–20 minutes

  2. 2

    Press release

    Press release

    Goal

    Produce future press release so the core question “What concrete customer benefit would make credible news, and which questions must be answered before building?” can be answered with stronger support.

    Inputs for this step

    • customer problem
    • strategic goals
    • technical and economic assumptions

    Actions

    • Write headline, benefit, experience, and credible evidence.
    • Record source, rationale, and open uncertainty directly in future press release.

    Output

    future press release

    future press release · source · uncertainty · next decision

    Quality check

    Can a customer retell the benefit?

    Pitfall

    The press release becomes marketing copy and the FAQ defers hard risks to implementation. Use a concrete customer situation and evidence; mark hard questions with owner and decision date.

    Timing: 10–20 minutes

  3. 3

    Customer FAQ

    Customer FAQ

    Goal

    Produce customer FAQ so the core question “What concrete customer benefit would make credible news, and which questions must be answered before building?” can be answered with stronger support.

    Inputs for this step

    • future press release
    • strategic goals
    • technical and economic assumptions

    Actions

    • Answer usage, boundaries, price, trust, and switching.
    • Record source, rationale, and open uncertainty directly in customer FAQ.

    Output

    customer FAQ

    customer FAQ · source · uncertainty · next decision

    Quality check

    Are objections answered concretely?

    Pitfall

    The press release becomes marketing copy and the FAQ defers hard risks to implementation. Use a concrete customer situation and evidence; mark hard questions with owner and decision date.

    Timing: 10–20 minutes

  4. 4

    Internal FAQ

    Internal FAQ

    Goal

    Produce internal FAQ so the core question “What concrete customer benefit would make credible news, and which questions must be answered before building?” can be answered with stronger support.

    Inputs for this step

    • customer FAQ
    • strategic goals
    • technical and economic assumptions

    Actions

    • Decide technology, operations, economics, and risks.
    • Record source, rationale, and open uncertainty directly in internal FAQ.

    Output

    internal FAQ

    internal FAQ · source · uncertainty · next decision

    Quality check

    Do unresolved existential risks block build?

    Pitfall

    The press release becomes marketing copy and the FAQ defers hard risks to implementation. Use a concrete customer situation and evidence; mark hard questions with owner and decision date.

    Timing: 10–20 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Working Backwards · Future Press Release und FAQProduktidee zuerst aus Kundensicht erzählen, harte Fragen beantworten und erst dann Umsetzung ableiten
Working BackwardsDas Visual zeigt Kunde und Zielzustand, eine Future Press Release mit Headline, Problem, Lösung und Kundenquote sowie FAQ und Entscheidung.Vor dem Bauen die fertige Kundengeschichte schreibenWorking Backwards zwingt eine Produktidee in klare Kundensprache, Nutzenlogik und überprüfbare Fragen.Kunde und Zielzustandwer hat welches Problem gelöst?Future Press ReleaseHeadlineklarer KundennutzenProblem + Lösungwarum es jetzt relevant istKundenquotekonkreter Nutzen im AlltagFAQharte interne und externe FragenEntscheidungbauen, ändern oder stoppennicht Featureliste, sondern StoryEinwände erzwingen KlarheitRoadmap folgt erst danach
Form

Versioned PR/FAQ with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of PR/FAQ.

Tool alternatives
  • PR/FAQ as board or document
  • Source and evidence register
  • Decision and action log

working-backwards-working-template.md

Plan Working Backwards around its domain steps and the concrete decision question.

Working Backwards: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Establish and review the practice Time: Several writing and review rounds

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Customer problem and evidence, strategic goals, technical and economic assumptions, shared workspace, source links, and decision log.
  • Roles: Product lead · Customer/Research · Tech · Operations · Finance
  • Advance information: Collect Customer problem and evidence, strategic goals, technical and economic assumptions in advance and mark open assumptions.
  • Overall time needed: Several writing and review rounds
  • Setup: Prepare future press release plus customer and internal FAQ visibly and calibrate assessment terms before starting.

Prepare for the work steps

Customer/problem: Customer/problem

  • Customer problem and evidence
  • strategic goals
  • technical and economic assumptions

Press release: Press release

  • customer problem
  • strategic goals
  • technical and economic assumptions

Customer FAQ: Customer FAQ

  • future press release
  • strategic goals
  • technical and economic assumptions

Internal FAQ: Internal FAQ

  • customer FAQ
  • strategic goals
  • technical and economic assumptions

PR/FAQ

Customer/problem

Customer/problem information to record

...

Press release

Press release information to record

...

Customer FAQ

Customer FAQ information to record

...

Internal FAQ

Internal FAQ information to record

...

Enter only real input, sources, and decisions.

Amazon: Working Backwards

Customer/problem: Customer/problem

Expected artifact: customer problem

customer problem · source · uncertainty · next decision

Entry:

...

  • Is today's disadvantage concrete?

Press release: Press release

Expected artifact: future press release

future press release · source · uncertainty · next decision

Entry:

...

  • Can a customer retell the benefit?

Customer FAQ: Customer FAQ

Expected artifact: customer FAQ

customer FAQ · source · uncertainty · next decision

Entry:

...

  • Are objections answered concretely?

Internal FAQ: Internal FAQ

Expected artifact: internal FAQ

internal FAQ · source · uncertainty · next decision

Entry:

...

  • Do unresolved existential risks block build?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/working-backwards/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

working-backwards-beispiel.md

Concrete filled scenario, fictional example

Headline: regulated teams find every review decision in 30 seconds. The press release names target customer, current search, export, and pilot evidence. Customer FAQ covers import and permissions. Internal FAQ tests data residency, support, price, and migration cost. The open residency question stops build pending decision.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Customer/problemThe press release becomes marketing copy and the FAQ defers hard risks to implementation.View in phase
  2. Press releaseThe press release becomes marketing copy and the FAQ defers hard risks to implementation.View in phase
  3. Customer FAQThe press release becomes marketing copy and the FAQ defers hard risks to implementation.View in phase
  4. Internal FAQThe press release becomes marketing copy and the FAQ defers hard risks to implementation.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

PR/FAQ answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.

Method after Amazon. Curated with 1 sources.

Sources: Amazon: Working Backwards

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.