Backward Reframing

The PM Audit Canvas

Revisit a past role or project. Surface the product decisions that were always there — simply unnamed. For applying product thinking forward, use the Forward Learning Canvas.

Look back → Name it → Carry it forward
Use once per past role or significant project.

What was I working on?

Canvas A

Describe the role, project, or moment in plain terms — the way you would have described it at the time, before any PM vocabulary.

Write this section in the past tense and in the language of that time. The reframe comes later.

How / when thinking

Canvas B

Describe the work as a project manager would have seen it: coordination, timelines, resources, deliverables.

What / why thinking

Canvas C

Reread the same experience through a PM lens. Use product vocabulary to name what you were actually doing.

What was I deciding — without knowing it?

Canvas D

Translate past actions into PM primitives. Match what you did to the vocabulary it belongs to.

Discovery
Prioritisation
Stakeholder alignment
Delivery & iteration
Outcome measurement
What you would do differently now

You are not rewriting history. You are recovering the product judgment that was always embedded in your work — and naming it precisely.

How do I describe this now?

Canvas E

Synthesise. Write the version of this experience you would give in an interview, a portfolio entry, or an article — using PM language, without distorting what happened.

In [context], I was responsible for [what you managed]. Seen through a product lens, this meant [what you were actually doing: discovery / prioritisation / alignment / delivery] for [who the real user was], with the goal of [the outcome, not the output].

Backward reframing is not revision — it is excavation. The product judgment was always there. This canvas gives it a name.