Comparing cycles: trend beats a point · From Zero to Goals, lesson 15 of 17
Comparing cycles: trend beats a point
Read two quarters side by side and judge the trajectory, not the single score.
Comparing cycles: trend beats a point
One quarter is a point; two are a line. The line is where goal-setting starts paying compound interest. But cycle comparison has a trap: scores only compare when you know what KIND of goals produced them.
Brightside has two scored quarters now, two area boards, and a founder with one spare coaching hour a week. Where it goes depends entirely on how Dana reads four numbers.
Two boards, two lines
Growth (Priya): Q2 average 0.7 (the 0.2 win rate dragging two strong scores) → Q3 average 0.8. Same kinds of goals both quarters: stretch-heavy, same shape.
Delivery (Sam): Q2 average 0.9 (Dana’s sheet scored the kept invoicing 1.0 and the broken churn promise 0.8, “because it was only one client”) → Q3 average 0.6. One thing changed: in Q2 the board was all commitments; in Q3, after module 1 reached him, Sam set his first real stretch goals.
Dana looks at the four numbers and reaches for a conclusion: “Growth is improving, Delivery is slipping. My coaching hour goes to Sam.”
Is Dana reading the numbers right?
The numbers, split. Now place the hour
Dana redoes the sheet by kind. Delivery Q3: commitments 2 of 2 kept, first-ever stretch goals averaging 0.6. Growth Q3: stretch average 0.8, no commitments on the board. (And Q2’s broken churn promise gets its own line: kept/broken, never a 0.8.)
The story flipped: Delivery didn’t get worse, it got braver. But the coaching hour still exists, and it still has to land somewhere this quarter.
Where does the one coaching hour go?
Composition beats trend, trend beats point
Read cycle comparisons in that order: what KINDS of goals made each number → which way the line moves within each kind → only then the point. Commit-rate (kept/broken) and stretch-average are different instruments; a board that mixes them into one number has built a broken speedometer.
And the test for any metric you compute at the close: what would this number make us DO differently? If the answer is nothing, stop computing it. Cycle reviews die of dashboard obesity more often than of missing data.
Put your last two cycles side by side
Even roughly: for each of your last two quarters, write commitments kept/broken and the stretch average separately. Then one sentence about the line, and one thing the comparison makes you do differently next quarter.
Saved in this browser only. Keep it on a free account and it stops depending on this one.
More on reading your numbers
All optional, and none of it is needed for the certificate. Each opens in a new tab, so your place in the lesson is kept.
- OKR grading and scoring, including what scores mean ↗Scoring in detail, including why 0.7 is a landing and a broken commitment is never an average.9 min read
- Progress tracking for teams ↗Reading progress across a cycle rather than at a single point, which is the habit this lesson is built on.6 min read