Most Stage 3 teams have docs. They have process documents, brand guidelines, customer-handling protocols, escalation paths. The docs are usually pretty good. The capability gap isn't documentation — it's translation. Written process never becomes team capability without a deliberate training rhythm that turns docs into muscle.
The default approach at Stage 3 is to send the team the doc, hope they read it, correct them when they get it wrong. This is training by accident — slow, inconsistent, and expensive. The team learns the standard by being corrected after they miss it, which means the customer often experiences the miss before the team learns from it.
A deliberate training rhythm fixes this. It's mundane, but it's the difference between a team that has documents and a team that has capability.
The weekly 30-minute training session
Lock it in the calendar. Same time every week. 30 minutes. Whole team or sub-team if that fits the size. The format is application, not lecture.
Pick one playbook entry. From the Playbook Library. Could be the one you just shipped, could be one that's relevant to a problem the team faced this week, could be a weak spot the operator noticed. One entry per session.
Walk through a real example. A real customer interaction, a real operational decision, a real situation the team handled or is about to handle. Not a hypothetical. The team applies the playbook to the actual case in the room.
Debrief. What worked, what would change next time, where the playbook itself needs sharpening. The session doesn't end with 'good job team' — it ends with either a small playbook update, a skills-gap entry for someone, or a flagged-pattern for the operator to track.
30 minutes is enough because the discipline is the rhythm, not the duration. A weekly 30-minute session compounds; a quarterly 4-hour offsite doesn't.
The check-work ritual
This is the piece most teams skip and then wonder why their training doesn't transfer. The Stage 3 success criterion #3 — 'Help Your Team Help You' — has four pieces: write down how, train properly, give them tools, check their work. Most teams do the first three. The fourth is what makes the first three actually transfer.
Check-work means: the operator (or operator + founder for the first month) takes weekly samples of the team's work and scores them against the playbook. Sample size depends on volume — 2-3 cases per team member per week is usually enough. The score is structured: did they apply the right playbook, did they execute the steps in order, did they hit the acceptance criterion, where did the work diverge from the standard.
The scoring is conversation, not punishment. The team member sees the score, sees what the operator would have done differently, and the playbook either updates (if the team's instinct was right and the doc was wrong) or the team member's skills-gap log updates (if the work missed the standard).
Two to three weeks of check-work and the team's instinct shifts. They stop asking 'is this right?' and start asking themselves 'does this match the playbook?' That shift is when written process becomes team muscle.
The skills-gap log
Per team member, a running log: where they're strong, where they're stretching, where they need targeted training. Not a performance review document — a working log the operator updates after each check-work session.
The log surfaces the specific weaknesses. Maybe one team member is great on customer comms but slow on quality gates. Another is sharp on quality but weak on scope-creep recognition. Generic team training would address neither well; targeted training to each gap compounds fast.
The training rhythm shapes itself around the gap log. The weekly session covers playbook entries that map to the team's actual gaps that week. Six weeks of targeted training usually closes 60-70% of the gaps that existed at engagement-start.
Why the rhythm matters more than the docs
The Stage 3 founder's instinct is to write more docs. If the team's capability is patchy, the doc must be missing something — write a more detailed version. Add an appendix. Make a video walk-through.
The instinct is wrong. The doc is usually fine. The capability is patchy because the team has never been deliberately trained on the doc, never had their work checked against it, never had the gap surfaced and addressed.
Adding more documentation to a team that doesn't have a training rhythm is like adding more books to a library no one visits. The fix is the rhythm, not the documents. Once the rhythm is in place, even imperfect docs produce good capability because the team is practising and being checked.
What this looks like when it's working
By Week 8 of a 12-week engagement: the weekly training session has run 4+ times, the check-work ritual is operational, the skills-gap log is populated for each team member, at least one team member has demonstrated a playbook entry independently to the standard.
By Week 12: the team is running the rhythm without the founder needing to chair it. The operator runs the session, captures the gap log updates, and surfaces patterns to the founder weekly. Capability has visibly compounded — delivery is more consistent, customer complaints have dropped, and the team handles edge cases without escalating.
By Operate Phase: the rhythm runs on autopilot. New hires step into a culture where weekly training and check-work are normal. The capability gap that took six weeks to close at engagement-start now takes two weeks to close for new hires because the discipline is structural.
The bottom line
Most Stage 3 teams confuse documentation with capability. They write more docs and wonder why the team is still inconsistent. The fix is the training rhythm — weekly session, application not lecture, check-work ritual, skills-gap log per team member.
It's mundane. It's not glamorous. It's the difference between Stage 3 graduation and Stage 3 plateau.
Frequently Asked Questions
Why doesn't writing more documentation work?
Because documentation doesn't transfer to capability without practice and check-work. The team learns the standard by applying it, getting feedback, and adjusting — not by reading a longer doc. Most Stage 3 founders write more docs because that's the lever they can pull alone, and skip the training rhythm because it requires sustained discipline.
What format should the weekly training session take?
Application, not lecture. Pick one playbook entry, walk through a real (not hypothetical) recent example, debrief what worked and what would change. 30 minutes total. The team applies the playbook to actual cases in the room. Lecture-format training is forgotten by Friday; application-format training compounds.
What does check-work actually involve?
Operator (or operator + founder for the first month) samples 2-3 cases per team member per week and scores them against the playbook. Did they use the right playbook, execute the steps, hit the acceptance criterion, where did the work diverge. The score is a conversation — the team member sees it, the playbook updates if needed, the gap log updates if the team member missed the standard.
How do you handle a team member who consistently misses the standard?
Same way you handle anything else: surface the pattern, document it in the gap log, target training to the specific weakness, give it 6-8 weeks. If after 8 weeks of targeted training the gap doesn't close, you have a different problem — usually role-fit or motivation, neither of which more training will fix.
Does the rhythm continue into Operate Phase?
Yes. The teams that graduate Stage 3 keep the rhythm running indefinitely. Operate Phase typically lighter — the operator runs it, the founder reviews monthly. New hires step into the rhythm as part of onboarding, which is why they ramp faster than the original team did.