Skip to content

The Coach-Mentor Duality

Definition

"Agile coach" is a single job title hiding two structurally different helping relationships. Professional coaching helps a person see new perspectives and choose their own next step — the coachee's agenda rules, and the coach withholds their own opinions. Mentoring instead transfers the mentor's own accumulated agile knowledge and experience directly. An agile coach is both at once: coaching for team performance and mentoring for agile expertise, unlike a purist professional coach who works only from the coachee's agenda.

In the Book

Lyssa Adkins locates this distinction in her own history: she spent years coaching agile teams using only project-management technique before a colleague told her, bluntly, "you call yourself a coach, but you're really not one." Going to coaching school revealed the missing half — professional work/life coaching skills — and she names the ethical gap explicitly: real professional coaches hold the coachee's agenda as the "single guiding light," but an agile coach cannot fully do this, because they also carry their own agenda of wanting the person or team to use agile well. Chapter 5 ("Coach as Coach-Mentor") builds the rest of the book's role taxonomy — teacher, facilitator, problem solver, conflict navigator, collaboration conductor — on top of this founding duality, and repeats it at the whole-team level: coaching improves the team's performance in steps the team itself chooses, while mentoring transfers the coach's specific agile knowledge as it becomes relevant.

Why It Matters

Naming the duality prevents two common failure patterns: coaching-only helpers who never actually teach anything (leaving teams to reinvent agile badly) and mentoring-only "coaches" who are really just directive experts in coach's clothing (undermining the team's own capability). Any helping role built on borrowed expertise — teaching, consulting, technical leadership — faces the same tension between drawing out someone else's answer and supplying your own, and naming which mode you're in, moment to moment, is what keeps the two from silently collapsing into one.