Stage 4
Value-driven
“Is this worth doing?”
The tribe works on data about value, not just about delivery. The planning horizon is no longer just a boundary that can be safely planned for - it's a frame within which the tribe deliberately organises the work to maximise the value delivered. Leaders make decisions based on business goals - and can say “no” to low-value work.
The question “are we doing the right things?” - the tribe's goals stop being just a board and start to genuinely shape priorities. The tribe has a mechanism for turning down work that doesn't justify the investment.
Note: a goals mechanism already appears at stage 2, regardless of method. The difference is qualitative - at stage 4 the agreed goals win over “the new topic that has to go in”. The tribe can say “no” - and the organisation respects it.
How to recognise this stage
- The tribe can say “we can do A or B, not both” - and back it up with data
- Decisions about initiatives include an assessment of value (revenue, conversion, risk), not just a description of scope - at this stage it's still the business's perspective, not necessarily validated directly with the customer.
- The order of work is decided by what will bring the most value - not by the order of requests or pressure from stakeholders.
- The tribe can deliberately say “no” or “not now”, basing the decision on data.
- Teams are responsible for maintaining what they build (build-run-maintain)
- We know how much work the tribe can realistically take on. That way, the conversation about further initiatives is based on facts, not promises.
- The tribe's goals help decide what we work on first - they're not just a general direction.
- During the planning cycle we can change an earlier decision - e.g. replace a less valuable initiative with one that delivers more value.
- Technology decisions (refactoring, migration, paying down technical debt) compete for time on the same terms as business initiatives - we look at their value, cost and risk.
- Improvement also covers hypotheses about value and the product, not just the process - the tribe tests and discards ideas based on data, not just gut feeling
Recognise this stage in your tribe? Let's talk about what usually blocks the move to stage 5 and where to start in your case.
Transition 4 → 5
How to move to stage 5
Signal that it's time to start
Despite mature decisions about value, work still gets stuck at the boundaries of teams and tribes - cascading dependencies that can no longer be “planned in advance” but have to be solved structurally. A question arises that stages 3 and 4 don't ask: “are we organised around the right things, or just around how the organisation happened to grow?”
Who leads
The tribe lead, but with the organisation accepting the very principle that the tribe can change its own structure - this transition is no longer just the tribe's internal matter.
When you need someone from outside the tribe
This is a deliberate boundary of the framework: the pain ultimately shifts to the organisation's governance, budgeting and decision-making structures - that's no longer something the tribe can solve on its own.
First tangible result
The first restructuring of the tribe, clearly justified by data, accepted by the organisation as a legitimate way of working rather than a one-off exception.
Warning sign
A signal that can no longer be solved by the tribe alone: the pain shifts to the organisation's governance, budgeting and decision-making structures, which can't keep up with how the tribe works. This is a deliberate boundary of the framework - further change requires decisions at the level of the whole company, not the tribe, and goes beyond what this document can prescribe.
We agree the specific steps in a conversation, because they depend on your context.