What templates are good for
| Exercise | The structure that helps |
|---|---|
| Retrospective | Three or four labelled columns and nothing else. |
| Process mapping | A swimlane per role, left to right. |
| Rollout planning | A column per wave, with an owner slot in each. |
| Decision | Options across, criteria down. |
| Brainstorm | A large empty area and a small labelled one for the output. |
The pattern in that table is that good templates are almost empty. A template with forty pre-written prompts is somebody else's workshop; a template with four labelled regions is a structure your team can fill.
Templates
Save current board as template
Retrospective — 4 columns
Went well · Did not · Confused us · Try next
Process map — swimlanes
One lane per role
Rollout waves
Wave columns with owner slots
Decision grid
Options across, criteria down
Making your own
- Run the session once on an empty board.
- Delete everything that was content, keeping only the structure that helped.
- Save that as a template.
- Name it after the exercise, not the meeting it came from.
A template made before the first session is usually wrong
You do not know what structure helps until you have watched people struggle without it. Templates built from a session that worked are used; templates built in advance are opened once.
What this does not do
No shared template library across organisations
Templates belong to your workspace.
No template versioning
Editing replaces.
No locked regions
A template's structure can be moved like anything else.
Questions
Can we start from a built-in template and change it?
Yes.
Can a template include images?
Yes.
Who can create one?
Anyone with the module.