Hit every target. Lost customers.
The dashboard stayed green all year. Customers left anyway, and nobody saw it coming until the churn report.
InsteadTargets stay tied to what customers feel.
The video
Video planned52 secondsHow every video is made
The script
- The one point
- Every target carries a counter-metric customers feel; when they diverge, the metric owner hears early.
- Why a video
- Time passing: a green year compressed into seconds while customers quietly leave on another screen; then the same second month shown twice, and the owner’s click held live.
- Picture
- Brand mark and sound, then the heading ‘Hit every target. Lost customers.’ on the site’s background, fading straight into the guide with no black.
- On screen
- Hit every target. Lost customers.
- Picture
- Guide in the usual place and framing. Lower third: guide’s first name, Soundly Run guide.
- Voice
- The dashboard stayed green all year. Customers left anyway, and nobody saw it coming until the churn report. When each team owns its own dashboard, nobody owns the gap between them.
- On screen
- Soundly Run guide
- Picture
- Two dashboards side by side. Months tick past; on the left the target line climbs green. On the right, customer dots fade out one by one, unseen. The churn report lands a quarter later, stamped late. No numbers.
- Voice
- Watch a year. The target climbs. Customers slip away on another screen. The churn report arrives a quarter late, after the time to act has gone.
- On screen
- Lost customers show up a quarter late (lagging churn)
- Picture
- Drawn Analytics screen, Example tag top left, context ‘Priya’s crew’. Cursor walks heading, then First reply time, Counter-metric, Accounts lost, Owner, then the drafted note, in order. Step band on prepare, then review.
- Voice
- The target is paired with a counter-metric customers feel. First reply time, better three months running. Repeat complaints, up two months running. Six accounts lost, each citing a repeat issue. Priya hears it now, not at quarter end.
- On screen
- Replies got faster. Repeat complaints rose.
- Picture
- Step band on decide. Cursor on ‘Add to the weekly review’, Change and Pass visible; click held two seconds. Confirmation appears, then the counter-metric row reads ‘on Thursday’s review agenda’. Guide in picture-in-picture.
- Voice
- Priya, the support process owner, owns the target: add to the weekly review, change, or pass. In the review, she decides what changes.
- On screen
- Added to Thursday’s review. Priya decides what changes.
- Picture
- Guide back in the same framing. Beside her, Example tag top left, the same second month twice: before, one green line alone; after, both lines together, the split flagged.
- Voice
- Nobody waits for the churn report to find the split any more. The helper flags it; Priya decides. It does not change a target, and it does not watch, score or replace anyone.
- On screen
- Targets stay tied to what customers feel.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Hit every target. Lost customers.
On screen as proof
- Analytics screen with the Example tag, its rows and drafted note walked in order
- Approval click on ‘Add to the weekly review’ held two seconds, Change and Pass visible
- The same second month before and after: one line, then both with the split flagged
Before and after
- Before
- People hit the number they’re judged on (a proxy metric); customers judged something else
- After
- Each target paired with a measure customers feel (a counter-metric)
- Before
- The target stays green; lost customers show up a quarter late (lagging churn)
- After
- A split flagged at month two, not quarter end
- Before
- Nobody owns the gap between two dashboards
- After
- The metric owner sees both lines, with time to act
How it works
Every target carries a counter-metric customers feel; when they diverge, the metric owner hears early.
- Each target is paired with a counter-metric customers feel; the target's owner approves the pair or swaps it.
- When the pair splits two months running, the owner hears it, with the lost accounts, and chooses whether to raise it.
- In the weekly review, the owner decides what changes: the target, the method, or nothing at all.
AnalyticsExample
Priya's crew · Example
Replies got faster. Repeat complaints rose.On Thursday's support review
- First reply time
- 4.1 hours, better 3 months running
- Counter-metric
- Repeat complaints, up 2 months runningRepeat complaints: on Thursday's review agenda
- Accounts lost
- 6 this quarter, each citing a repeat issue
- Owner
- Priya, support process owner
Replies got faster while repeat complaints rose. Worth checking whether quick first replies are closing issues too early.
Source: help desk, 14 Oct
Add to the weekly reviewChangePassAdded to Thursday's review. Priya decides what changes.
Built to work in the email, calendar, chat, finance and sales tools you already use.
What it never does
- Acts alone only inside limits a person sets; asks first for anything else.
- Reaches only what its job needs.
- Never watches, scores or replaces anyone.