Phase 4 · Scale
Turn the pilot into a repeatable operating model.
Test whether your workflow transfers, then make a grounded decision about the next rollout wave.
The program at a glance
One shared practice. Five phases.
- Phase 0 · Suggested week 0
Prepare
Pod, backlog, access, baselines, tools, and structure.
Explore phase - Phase 1 · Suggested week 1
Execute
Agree the design together before generating a change.
Explore phase - Phase 2 · Suggested week 2
Guardrails
Keep changes reviewable and run the quality gates.
Explore phase - Phase 3 · Suggested week 3
Trust
Use AI to understand, explain, and debug the code.
Explore phase - Phase 4 · Suggested week 4
Scale
Transfer the playbook with coaches and rollout waves.
Current phase
Your destination
What success looks like at the end of this phase
The first pod is a source of reusable practice and internal coaching. A receiving pod can apply the playbook, leadership can review delivery and quality together, and the next rollout wave has named coaches, governance, and measurement. Expansion proceeds when delivery improves and quality holds.
The performance step
Grow the gain across more teams.
- What improves
- A receiving pod uses the playbook on its own work. Coaching and reusable skills spread the practice, increasing the organization’s accepted delivery capacity.
- What to measure
- Compare each pod with its own baseline. Track accepted work, delivery time, quality, adoption, and coaching hours as more teams join.
- Build on it
- Use the measured gain and rollout coverage to update the organization-wide model in Outcomes.
Where you are now
The pilot has working practices, but important knowledge may still live with the original pair or coach. Other teams want to try it.
What you will learn: Transfer the workflow and distinguish a promising pilot from readiness for wider use.
What to do in this phase
Step 01
Codify the engineering playbook
Capture five parts of the actual practice: the daily workflow of pairing, alignment, generation, and review; prompt patterns with failure modes and verification; commit, test, security, performance, and documentation standards; versioned reusable skills with expected outputs; and a scorecard covering delivery, quality, business value, and adoption.
Step 02
Make the original pod the coaching spine
Have pilot engineers teach the method and review another team’s artifacts. Explain the decisions behind the workflow instead of handing over prompt transcripts alone. Provide enough protected coaching time and named support so the pilot pod does not become an unreachable example or a bottleneck.
Step 03
Run the next coached wave
Move from the pilot pod to a receiving pod using representative work. Let the receiving team do the implementation while the original pod coaches. Record differences in repositories and experience, repair missing context, and update the playbook from actual transfer feedback.
Step 04
Build the ongoing operating model
Plan later waves with clear governance, measurement definitions, exception owners, and a community of practice. Assign owners to maintain the playbook and skills. Keep weekly practice reviews so new learning changes the standard workflow rather than staying in individual chat histories.
Step 05
Scale only when delivery improves and quality holds
Review pilot outcomes against the baseline with consistent definitions and representative work. Examine quality, review burden, business value, and coaching capacity together. If evidence is too limited or quality is deteriorating, repair the workflow or extend the evaluation before expanding. Completing the curriculum does not itself prove rollout readiness.
Your working session
Try this with your team
Give a receiving pair the playbook and a representative ticket in their own context. Observe where they need help. Update the playbook, complete the pilot evidence review, and recommend a supported rollout, a repair exercise, or a longer evaluation.
Make this: A versioned playbook, transfer feedback, pilot evidence review, and a bounded next-wave recommendation.
See it on the page The receiving-pod handoff →
Use a practice guide when you reach this step:
A worked example
A receiving pod uses the invitation workflow but cannot apply the original repository’s test command. The pilot pair adds local setup guidance and clarifies the common acceptance standard. The receiving pod then produces a specified, validated change. This demonstrates a transfer in that context; leadership still needs support capacity and quality evidence before a wider wave.
How success feels
- We can teach another pod how to work this way without taking over its work.
- The practice is becoming part of how our organization operates.
- We know which practices are ready to expand and can explain that decision with evidence.
Use the signals below to check your progress with the team.
Signals of success
- The playbook contains the daily workflow, prompt patterns, standards, versioned skills, and scorecard.
- A receiving pod completes representative work using the method and provides transfer feedback.
- Pilot engineers can coach the next pod without doing its implementation.
- Delivery improvement and quality are evaluated together against the baseline; evidence gaps are explicit.
- The next wave has named coaches, support capacity, governance, measurement, and playbook owners.
If you are stuck
- Only the original pair succeeds. Make tacit decisions explicit and repeat a smaller transfer exercise.
- The headline gain depends on easy tickets. Report representative work and context, and narrow the claim.
- Expansion outruns coaching. Demonstrate support capacity before adding more teams.
Coach checkpoint
Before you move on
Review the receiving pod’s work, repaired playbook, scorecard, and next-wave plan with the sponsor and coach. Approve expansion when delivery improvement is supported and quality holds. If the evidence is incomplete, finish with a clear repair or evaluation plan and keep the rollout bounded. Scale remains part of this program.
Your next action: Present the playbook, receiving-pod feedback, delivery-and-quality scorecard, and proposed rollout wave to your sponsor.
Reading independently? Use these questions for self-review. Discuss participation and artifact feedback with a coach through a cohort enquiry.
Continue to Outcomes to plan the next wave and explore the 50-engineer value example.