Manual sections
The Crew
Specialisation, not specialists.
A specialist team waits. A generalist team covers.
The Accelerator and the Shield are the delivery framework: phases with a fixed purpose, and walls that hold until the exit. The Crew is who travels the tunnel. It is the team that works from the signed scope the Lens produces.
| The framework: what the work passes through | The operating model: what the organisation agrees to | |
|---|---|---|
| Intake | The Lens | The Portal |
| Delivery | The Accelerator and the Shield | The Crew |
The principle
A team of specialists waits. Each person waits for the next task in their area, and every area depends on one person. A team of AI-enabled generalists overlaps. Every capability has more than one person who can carry it, so the team keeps moving when someone is away and quality holds when someone leaves. Jack of all trades, master of some.
Don't replace experience with AI. Replace specialties with AI. Keep the experience and spread the specialties, until the bus factor applies to every capability. A specialist team waits. A generalist team covers.
How it applies the core
The Crew is not a new principle. It is the core, applied to who does the work.
| Principle | In the Crew |
|---|---|
| The Clarity Contract | If it's not in writing, it cannot be done. Intent is written, challenged and signed before work starts. |
| Rigid Mobility | Work runs through the Accelerator's phases. The purpose of a phase is fixed. The path inside it is the crew's to choose. |
| The Tunnel | There is no Scrum Master. The walls that role used to hold are now in writing: the Portal, sign-off and the Change Forum. |
| The Same Room | Work goes to the room, not to a person. |
| Audit Exhaust | Accountability comes from the record, not from ceremonies. |
| The Assumption Tax | A capability only one person can carry is a debt that falls due the day they are away. |
The baseline crew
| Role | Leads | Also carries |
|---|---|---|
| Solution Architect | Direction against the enterprise architecture. Also codes. | Backend, platform, automated tests |
| Senior Backend | Complex solutions, platform | Architecture, automated tests, data |
| Senior Fullstack | Backend and frontend | UX, platform, automated tests |
| Test Manager | Scenario and case testing | Automated tests, product |
| Product Owner / PM | Enhance, enrich and protect the product and the team | Scenarios |
Developers own unit, smoke, performance and penetration tests. UX comes from a design library and a machine-checkable design contract. Platform and operations belong to every developer. Systems thinking is a requirement.
How the crew decides
A role says what a person can carry. It does not say who decides. One person often holds several roles, and a crew of ten may have no product owner at all. So agreement is counted per person, never per role, and the crew chooses how it decides before the work starts:
| Way of deciding | Who agrees | Fits |
|---|---|---|
| Solo | One person signs. | A crew of one. |
| Small crew | Named people sign. | A crew where everyone knows who carries what. |
| Crew vote | An agreed share of the crew. | Three people or more. With two, two-thirds is everyone, so it is just Small crew. |
- Objections are written. An objection stops a decision until it is resolved or overridden. The person who spots the risk cannot be quietly outvoted.
- Anyone can override, and everyone sees it. The override is announced to the whole crew, and the person who made it becomes the named Risk Owner for it. Shared decision, single owner.
- The rules are set before sign-off. After it, changing how the crew decides is a change like any other: recorded, and visible to everyone in the tunnel.
Why there is no Scrum Master
The best argument for a Scrum Master is a fair one. A product owner under pressure from stakeholders can't also be the one protecting the team from that pressure. Someone neutral has to be able to say "that's a redirect."
We agree that someone has to say it. It doesn't have to be a person. Here, the written record says it: nobody says yes on the spot, only the product owner moves work to Ready, and every override names what it pushes out. That applies to the product owner too. A redirect is visible and has to be signed again, so it costs something without anyone guarding the door.
The product owner's job
Enhance, enrich, protect. Protecting the product protects the team: less disruption, then higher quality and pace. A product owner who overrides the record breaks the role.
How people grow
- Juniors get the design contract, the existing repositories and the principles through their AI tooling, set to explain what and why instead of producing boilerplate.
- Everyone mentors everyone, because everyone's areas overlap.
- Tools come before the transition. Remove dependencies on individuals first. The planning question: what if I was gone tomorrow?
What happens to specialists
The question is not what happens to specialists. It is what happens to specialisation. Deep specialties do not disappear: at scale they become delegation, while the crews stay generalist. Everyone gets the tooling and the support. The move is not optional. You cannot decline that much time back and stay on a team built for the years ahead.
At scale
Generalist crews, specialised delegation. For regulated organisations, Audit Exhaust is what makes the model defensible.
The test
If any one person was gone tomorrow, would all their work still have someone who could carry it?
Try it
The Bus Factor tool builds a crew and shows which capabilities depend on a single person. It is free and needs no account.