Set Up a Continuous Improvement Cadence
Team & Leadership · Ongoing · Beginner
The job
Establish a recurring rhythm of retrospectives and improvement tracking.
What the sponsor gets
Each canvas and map from this playbook — Retrospective Canvas, OKR Canvas, Prioritisation Matrix — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Assess your current improvement habits
Audit what improvement activities happen already — retrospectives, post-mortems, suggestion boxes, incident reviews. Note their frequency, who attends, and whether actions actually get implemented.
Tip: If you run retrospectives but never check whether the actions were done, you don't have a continuous improvement process — you have a venting session.
Run a foundational retrospective
Create a Retrospective canvas to kick off the cadence. Focus on: what's working well (protect it), what's frustrating (fix it), and what should we try (experiment with it).
Tip: Limit to 3 actions per retrospective. If you're generating 10 actions, you're collecting, not prioritising.
Set improvement objectives
Create an OKR canvas with 1–2 improvement-focused objectives for the quarter. These sit alongside your delivery OKRs, not in competition with them.
Tip: If improvement work always loses to delivery work, make improvement a key result within a delivery OKR — "Ship feature X with zero rework" rather than "Improve code quality."
Design the cadence
Set the rhythm: fortnightly retrospectives (30 minutes), monthly improvement reviews (60 minutes), quarterly improvement planning. Book them all now — if they're not in the calendar, they won't happen.
Tip: The fortnightly retro should be short and focused — one thing to improve, one action, one owner. Save the big-picture review for the monthly.
Create an improvement backlog
Collect all improvement ideas from retrospectives into a single backlog. Use a Prioritisation Matrix quarterly to decide which ones to pursue, which to park, and which to drop.
Tip: Make the backlog visible to everyone — an improvement board next to the delivery board signals that improvement is real work, not an afterthought.
Track and celebrate
At each monthly review, report on improvement actions completed, their impact, and what you learned. Celebrate improvements that stuck — it reinforces the behaviour.
Tip: Share one improvement win per month with the wider organisation — it spreads the practice without mandating it.
The canvases and maps
- Retrospective Canvas
- What went well and what to improve, then start, stop and continue, so reflection ends in actions rather than a list of complaints.
- OKR Canvas
- One objective, three key results and the initiatives beneath them, so ambition and measurement sit on the same page and no initiative floats free of a result.
- Prioritisation Matrix
- Impact against effort in four quadrants — quick wins, major projects, fill-ins and avoid — so the team trades off instead of calling everything a priority.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.