What it is
A useful organizational model for agentic work splits roles into coaches and players. Coaches are experienced people who understand architecture, system history, business context, risk, and taste; they may not write much code directly, but they help others frame problems, ask better questions, design validation, and steer agents toward outcomes that hold up. Players are the people driving agentic work day to day — engineers, PMs, interns, analysts, operators, domain experts — whose value is less about deep implementation skill and more about agency, curiosity, clarity, and a willingness to work through the machine. The model matters because leverage no longer comes only from senior people doing senior work with their own hands; it comes from senior judgment being injected into many agent-driven workflows at once. Because durable handoff artifacts — specs, plans, logs, decisions, open questions — make context portable, work can also be routed by temperament rather than trapped in one person's head: a starter opens the problem space, a planner decomposes it, an implementer drives execution, a critic hunts for flaws, a finisher polishes, an operator deploys, and a coach intervenes precisely where judgment is the bottleneck. This routing is not automatic and the coaching is not optional; agents expand who can build, but people still need mentorship, review, and deliberate judgment transfer, and tools do not replace that.
When to reach for it
- When a few senior people are the constraint: turn their review style, risk instincts, and product taste into reusable steering for many players rather than a queue for their hands.
- When staffing agentic work: pair experienced coaches who frame and validate with players who have the agency and curiosity to drive agents through the day-to-day.
- When work is bottlenecked on one person's context, invest in durable handoff artifacts so the work can be picked up by whoever has the right temperament next.
- When a workflow spans distinct phases — opening, planning, building, critiquing, finishing, operating — route each phase to the person whose temperament fits, and reserve coach intervention for the judgment-heavy moments.
- When onboarding less-experienced or nontechnical builders, give them a coach, not just a tool.
When NOT to
- Do not treat "coach" as a title for people who have disengaged; coaching only creates leverage when the senior judgment is actively shaping real decisions, not rubber-stamping.
- Do not use this model to deskill players into mere prompt typists — their agency and clarity are the point, and flattening that loses the leverage.
- Temperament routing depends on genuinely durable artifacts; do not promise fluid handoffs on top of context that still lives only in someone's head.
- This is not a replacement for mentorship and judgment transfer — if you use it to justify cutting coaching, you have inverted it.
Exemplars
- Ibarra & Scoular, "The Leader as Coach" (*Harvard Business Review*, Nov–Dec 2019) — https://hbr.org/2019/11/the-leader-as-coach — classic antecedent: argues that the primary value of a senior leader shifts from having all the answers to unlocking capability in others through coaching; a precursor to the coach-player split this pattern applies to agentic work