Value Sequencing
Value Sequencing is the queue: goals ordered by value and pulled at the speed they close, finishing early when the outcome is reached, stopping when stopping is the right call and the reasons are kept, or running longer when the outcome genuinely needs it. It answers which goal comes next, and why that one.
This is chapter 8 of From Trading to Scaling, “The Work”. The book is free and takes about an hour.
The obvious bit
A goal should take as long as the outcome takes.
That is all this is. And once it is said out loud, the alternative looks strange: goals sized to a date in the finance calendar, whatever the work actually needs.
The quarterly rhythm is worth keeping. A shared clock means everyone reviews together, reports honestly, and stays aligned. We keep all of it.
The quarter stays. The waiting goes.
What the quarter is genuinely good at
The quarterly rhythm earns its place. A shared clock synchronises reviewing across teams, makes reporting honest and comparable, and keeps strategy and work aligned without endless coordination. None of that is the problem, and none of it changes. The heartbeat stays.
Duration is not the heartbeat
Value Sequencing separates two things the container habit fuses together: the duration of a goal and the heartbeat of the company. Where that habit comes from, and the four ways it shows up, is the subject of the sibling note. A goal takes as long as the outcome takes, and the quarterly rhythm keeps doing its job around it. The decision about when a goal may start is a separate move, and it has its own note: Continuous Goal Setting.
The two good endings
A goal ends well in exactly two ways. The outcome is reached, whenever that is. Or stopping is the right call, made deliberately, with the reasons written down and kept, so the hours flow to the next goal and nobody repeats the attempt blind. A stop with reasons is a decision, not a failure. What a goal never does is end because the calendar says so.
How a stopped goal is actually treated becomes the fastest lesson anyone learns, faster than anything written down about it. Call a stop with reasons a decision, not a failure, then treat the person who made that call even slightly differently afterward, and the document has already lost to what people watched happen. The first stop sets the pattern everyone else quietly measures themselves against.
There is a second thing worth keeping alongside the reasons: reference. A genuinely creative or ambitious attempt becomes a real, tellable instance, true whichever ending it reached, and it only does its work if it is told back to the team, not filed for a report upward. Tell it only for the goals that succeeded and the lesson quietly narrows to safe bets, since people learn what gets celebrated faster than what actually mattered. Tell it for both endings and the lesson is the one you actually meant.
The same narrowing can happen along a different axis. Reference that only ever attaches to goals dramatic enough to have a formal ending leaves the steady, compounding ones invisible by comparison, and invisible work reads as unvalued work, whatever the numbers actually say. Reference the compounding goals on the same rhythm as the dramatic ones, not just when they finally add up to something impossible to ignore. Big and visible gets seen by default. Steady and valuable has to be told on purpose, or it will not be.
Sequencing by value, pulling the next goal
Goals are ordered by value, a value stream, and pulled, not batch-allocated. When one closes, the team banks the learning and pulls the next most valuable goal immediately. Finish, then flow. No idle time between goals. Over a year this is where the pace comes from: more goals achieved, more value from every one, and each new goal starting smarter than the last because the learning is kept.
The capacity arithmetic
The gain is not subtle. A team that closes a goal in week six of a thirteen-week quarter and waits for the review ceremony has idled roughly half its strategic capacity for that cycle. Pull the next goal instead and the same team ships materially more each year with the same hours. The capacity story puts numbers on it.
“We make you fast, and fast does not wait for the calendar.”
The quarter stays. The waiting goes.
The honest part
The failure modes above are what we see, repeatedly, across ten years and more than a hundred organisations. The design is our answer to them, and we publish the confidence behind it, along with what would prove us wrong. We would rather show you that than claim certainty we have not earned.
Do OKRs have to take a quarter? +
No, and the quarterly rhythm still stands. Syncing reviewing, reporting and alignment on a quarter has real advantages, and we keep them. What changes is what happens inside it: a goal takes as long as the outcome takes, and when it closes early the next goal in the value stream is pulled immediately. The quarter stays. The waiting goes.
Is stopping a goal early a failure? +
No. A goal stopped for reasons you can articulate and keep is a decision, not a failure. It frees the hours for the next goal, and the reasoning stays so nobody repeats the attempt blind.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
Value Sequencing is a discipline of endings: finishing when the outcome is reached, stopping with the reasons kept, and pulling the next goal without waiting. We install it, coach the rhythm, and make the endings safe.