Contents
Why a routine rather than an action plan
Most action plans die in the weeks after their launch. The plan was sound; nobody had planned a regular meeting to keep it alive. The frontline manager is caught up in the day's emergencies, the indicators arrive at the end of the month, and the priority decided by the executive committee becomes one intention among many.
A short, fixed routine solves this problem. It provides a protected moment in which the team looks at what is really happening, decides what to do and checks whether what it did had any effect. It is the KAPER method applied at team level, every week, without outside intervention.
The five steps of the Cadence
| Step | Indicative time | Question | Output |
|---|---|---|---|
| K · Know | 15 min | What happened this week? | Three to five indicators discussed, two or three real customer cases or files examined |
| A · Aim | 5 min | What is next week's priority? | A single priority, stated as an observable result |
| P · Pave | 10 min | Who does what, by when? | Two to four actions, each with an owner and a date |
| E · Empower | 5 min | What capability are we passing on? | A decision delegated, a method demonstrated, a case explained by a team member |
| R · Reflect | 10 min | Did last week's actions change anything? | Action continued, adjusted or stopped, with the reason |
The Reflect step can also open the session: starting by checking the previous week's commitments makes the Cadence credible from the second week.
Start from real cases, not just figures
An indicator says a problem exists; a case says why. Each week, the team examines two or three concrete situations: a complaint, a blocked file, a cancelled sale, a control not carried out. The aim is not to find someone to blame but to understand what, in the process, the tool or the rule, produced the situation. It is the same reasoning as handling complaints through root causes, applied at team level.
Research on teams shows that this kind of review only works if members can report a mistake without fear of being penalised. Amy Edmondson (Administrative Science Quarterly, 1999) showed that psychological safety within a team is associated with more learning behaviour. A Cadence that turns into a tribunal quickly stops bringing the real problems to the surface.
Choosing the right indicators
Three to five indicators are enough. Beyond that, the session becomes a dashboard review.
- At least one leading indicator the team can move within the week: repeat contact rate, files pending beyond a set time, escalations to the manager, overdue controls.
- One outcome indicator, looked at over a longer period: first-contact resolution, recurring complaints, cancelled sales. Our guide to contact-centre quality suggests several.
- No indicator the team cannot influence. Tracking it every week produces nothing but frustration.
The roles
| Role | Responsibility during the Cadence |
|---|---|
| Manager | Prepares the indicators and cases, facilitates, makes the call when the team does not converge, escalates what goes beyond their authority |
| Team members | Present the cases they have handled, propose actions, take ownership of an action |
| Timekeeper | Ensures the order and timing of the five steps are respected (rotating role) |
| Next level up | Receives escalated points and responds within a stated time |
Escalation is essential. A team that reports the same obstacle every week without a response stops reporting it. Decisions beyond the manager's authority fall under decision rights, which sometimes need to be redefined.
Setting up the Cadence in four weeks
- Week 1: prepare. Choose three to five indicators, set a fixed 45-minute slot, prepare a one-page template covering the five steps.
- Week 2: first session. The manager facilitates, strictly following the order. A single priority, two to four written actions.
- Week 3: first check. The session starts with the previous week's actions. This is when the team discovers that commitments are followed up.
- Week 4: first adjustment. Drop the indicator nobody looks at, and hand facilitation of the Empower step to a team member.
After two to three months, the Cadence can be extended to other teams, with a monthly session in which managers compare what they have learnt.
The most common mistakes
- Turning the Cadence into an information meeting. Announcements go through other channels.
- Choosing several priorities. With three priorities, none moves forward.
- Leaving actions without a date or owner. An action "to be looked at" is not an action.
- Skipping the check. Without the Reflect step, the Cadence becomes a list of intentions.
- Looking for culprits. The team then stops bringing the difficult cases, which are the most useful.
Your checklist
- A fixed 45-minute slot, every week, protected in diaries.
- Three to five indicators, including at least one leading indicator.
- Two or three real cases prepared before the session.
- A single written priority for the following week.
- Actions with an owner and a date.
- A capability passed on at every session.
- A systematic check of previous actions.
- An escalation route with a stated response time.
Further reading
- 6 min read
- 7 min read
- 3 min read
- 7 min read
Frequently asked questions
How does the KAPER Cadence differ from a standard team meeting?
A standard meeting is often used to pass on information or comment on figures. The KAPER Cadence always follows the same order: look at facts and real cases, choose a single priority, assign dated actions, pass on a capability, then check what the previous week's actions have changed. It ends with written decisions, not minutes.
How much time does it take?
About 45 minutes a week for the team, and 15 minutes of preparation for the manager. Regularity matters more than length: a cadence held every week has more effect than a long quarterly seminar.
Which indicators should be tracked during the Cadence?
Three to five indicators at most, including at least one leading indicator the team can influence within the week, for example the repeat contact rate, files pending for more than five days or overdue controls. Outcome indicators, such as satisfaction or revenue, are looked at over a longer period.
What if an action depends on another department?
The Cadence must not become the place where everything that cannot be resolved piles up. An action that depends on another department is escalated to the next level with an owner and an expected response date, then followed up the next week like any other action.
Can the Cadence be used for compliance, not just customer service?
Yes. The same five steps apply to a team that maintains the record of processing activities, the inventory of AI systems or the anti-money laundering controls: the week's facts, priority, actions, capability passed on, check on the effect.
General information, not legal advice.
Report an error