The practice · Thursday AM
Thursday AM – KPI Learnings
Solo, no meeting – each Definer reads their layer
Thursday AM – KPI Learnings
Solo, and not a meeting. Each Definer on the core team reads what customers actually did for their own part, and preps for the Collab that afternoon. AI drafts the learnings first.
Thursday AM · solo, no meeting · CX, Product, UX and Engineering, each on their ownKPI Learnings
- 1
Before the morning starts, AI drafts the KPI Learnings brief – all three layers, the customer quotes and what changed since last week.
- 2
Product reads the KPIs against what the business was promised.
- 3
CX reads the customer voice – the "Yes, better" quotes, and every "Not yet."
- 4
UX reads where customers hesitated. Engineering reads errors, load and the flag.
- 5
Each Definer gives their layer a call – keep, change, expand or roll back – and every call gets a name, left in the AI project.
- 6
By 1 pm, the brief is clean. It's the first thing the AI moderator uses when the Collab opens.
- Goes in
- Live activity, "Was this better?" responses, and the KPIs from two and four weeks back
- Comes out
- The KPI Learnings brief, with a call for every layer, ready for the Collab
- Done when
- Every layer has a call and an owner, and the brief is ready by 1 pm
Generated and Iterated Thursday AM
| Artifact | Drafted from | Cleaned up by | Used next |
|---|---|---|---|
| KPI Learnings brief | The Dashboard data and "Was this better?" | Product and CX | The Collab, that afternoon |
| A call for every layer | Each Definer's solo read | The Definer who owns the layer | Flags, the live queue |
| Actions, with owners | Each Definer's solo read | Each named owner | The Collab |