Signals & Momentum
What makes a rhythm signal actually useful?
Most KPIs are surprisingly easy to move without changing anything that matters. Rhythm signals are the opposite: you can't improve them unless the underlying behavior changes. That’s what makes them powerful — and rare.
The problem with “easy-to-move” metrics
Many metrics look precise, but behave like smoke. People can improve them without changing the way work flows. Examples:
- Closing tickets quickly — by slicing them thinner.
- Velocity increases — by reducing scope quietly.
- More meetings — but fewer decisions.
These metrics create the illusion of progress. Rhythm signals do the opposite: they reveal whether the system is actually behaving better.
The three tests every good rhythm signal passes
For a signal to matter inside a 30-day Reset, it has to meet three requirements:
1) It must be behavior-linked
You should be able to point to real behaviors that move the signal:
- How long decisions sit without ownership.
- Whether priorities survive the week intact.
- Whether issues surface early or late.
If a signal can change without behavior changing, it’s not a signal — it’s noise.
2) It must be hard to game
A team should not be able to “improve” a signal by rearranging work theatrically. Useful signals can only improve when the underlying pattern improves.
A simple test: “Could someone fake this number without fixing the actual problem?” If yes, drop it.
3) It must be readable in under 30 seconds
Leaders steer under pressure. They don’t have time to decode a dashboard. A good rhythm signal acts like a compass:
- Is the pattern holding?
- Is something wobbling?
- Where should we zoom in?
Five examples of good rhythm signals
These are signals we repeatedly see working in real teams:
- Clarity Drift — how consistently teams describe the current 30-day focus.
- Decision Latency — time from needing a decision to receiving one.
- Reset Integrity — weeks in a row the weekly rhythm is maintained.
- Escalation Timing — how early risks are surfaced.
- Attention Scatter — how many active topics the team is pushing at once.
Signals inside a 30-day Reset
A Reset Plan cycle includes a small set of 2–3 signals tied to that month’s focus. Teams review them weekly — not to score the team, but to observe the pattern.
- Pick a driver under pressure.
- Choose 2–3 related signals.
- Watch for pattern shifts weekly.
- Adjust behavior, not slides.
The point of rhythm signals isn’t to measure more. It’s to steer earlier — calmly — with less noise and fewer surprises.