Running a project retrospective on a canvas

The project’s done. Or it’s done enough. Now’s the moment to look back before everyone scatters to the next thing.

A good retro isn’t a blame session or a pat on the back. It’s a short, honest look at what happened, with a plan at the end.

A canvas is a great place for it. The whole project fits on one board, and everyone can see the same picture.

Before the session

A little prep goes a long way.

• Invite the right people. Everyone who did the work. Keep it small enough that everyone gets to speak.
• Set the tone in the invite. “We’re looking at how we worked, not who got what wrong.”
• Gather the facts. Key dates, launches, changes of plan. You’ll need them for the timeline.
• Book enough time. Rushed retros skip straight to action items and miss the reasons.

Lay out the board

Draw the canvas before anyone arrives. Zones, left to right:

1. The timeline, across the top.
2. Went well, a big open area.
3. Was hard, another big area.
4. Patterns, a row of empty frames.
5. Next time, a strip at the bottom.

Add a small header with the project name and the question: “What do we want to repeat, and what do we want to change?”

Step 1: Draw the timeline together

Start with the shared story. It’s surprising how differently people remember the same project.

Put the key dates on the line: kick-off, first demo, the scope change, launch. Then invite everyone to add their own moments.

• “The week the design came back.”
• “When the client changed the brief.”
• “The Friday we found the bug.”

Ask people to mark each moment with a colour or a face: a high, a low, or neutral. You’ll soon see a mood line forming above the dates. That alone sparks conversation.

Step 2: Quiet writing

Now everyone writes notes on their own. One idea per note.

• Green notes in Went well.
• Orange notes in Was hard.

Give it a visible timer. Quiet first means the quieter people get their say before the discussion picks a direction.

Push for specifics. “Daily check-ins kept the Bengaluru and Delhi teams in sync” is useful. “Good communication” isn’t.

Step 3: Read and group

Take turns reading notes aloud, briefly. No debating yet, only clarifying.

Then cluster. Drag similar notes together in each zone. Stack duplicates. A tall stack is a signal worth noticing.

Name each cluster in a short sentence:

Weak name	Useful name
Testing	Testing started too late to catch the big issues
Client	Weekly demos kept the client close
Scope	Scope changes weren’t written down anywhere

Step 4: Find the patterns

Move the strongest clusters into the pattern frames. Look for links between the zones.

Often a Was hard cluster has a matching Went well one. For example, “Scope changes weren’t written down” sits opposite “Weekly demos kept the client close”. The fix might be as simple as noting changes during those demos.

Draw arrows between them. This is where a canvas shines. You can see cause and effect, not only lists.

Go back to the timeline too. Do the lows on the mood line line up with any cluster? That’s your story.

Step 5: Decide what to change

Head to the Next time strip. For the top few patterns, ask: what will we do differently on the next project?

Keep the list short. Three actions people actually take beat ten that sit in a document.

Each action needs:

• A clear action. “Write scope changes in the project doc within a day.”
• An owner. One name.
• A check-in point. When you’ll look at whether it’s working.

Also note what to keep. Things that went well don’t continue by accident.

Track the actions somewhere everyone can see. A simple kanban board with to do, doing and done columns works well for the check-in.

Step 6: Present it back

Save a few minutes at the end. Walk the room through the canvas, frame by frame.

• Start zoomed out on the whole board.
• Go along the timeline.
• Visit each pattern.
• End on the actions.

Everyone sees the full picture once, and mistakes get spotted before people leave.

Share it afterwards

Turn the canvas into a short summary deck for people who weren’t there, or for the next project’s kick-off.

A simple running order:

1. The project in one line.
2. The timeline with the mood line.
3. What to repeat.
4. What to change, with owners.

If you’d rather not start that deck from blank, Presentations.AI can give you a first draft in this order to edit.

There’s a fuller plan for this kind of recap in how to run a workshop that ends in a presentation.

Keep it kind

• Talk about the work, not the person.
• Thank people specifically, by name, for things that helped.
• Let the facilitator stay neutral. If you led the project, ask someone else to run the retro.

When the next project starts, open this canvas on day one. If the strategy itself needs a reset, how to present a strategy on one page is a good next step. CanvasDeck is a natural fit for the whole loop: one board for looking back, and frames ready to present.