---
title: "The three stages of learning team leadership"
url: "https://www.5whys.com/articles/the-three-stages-of-learning-team-leadership.md"
canonical: "https://www.5whys.com/articles/the-three-stages-of-learning-team-leadership.html"
published: "2009-09-10T23:11:49+00:00"
updated: "2009-09-13T22:10:10.197000+00:00"
tags: ["Meta", "Ri", "ShuHaRi", "cockburn"]
author: "Roy Osherove"
description: "How Shu-Ha-Ri applies to learning team leadership and TDD: start with practices, then learn the principles, and earn the values over time."
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# The three stages of learning team leadership

or anything else, for that matter: **Shu-Ha-Ri** :

- Practices
- Principles
- Values

\*see related to this:

- Source: [ShuHaRi and competence](http://blog.shino.de/2009/08/20/shu-ha-ri-related-to-competence/)
- [Cockburn on ShuHaRi](http://alistair.cockburn.us/Shu+Ha+Ri+to+Practices+Principles+Values)

This blog is right now at the "Practices" stage: Lots of "Do this" and "Don't do that", with just a little "Principles" thrown into the mix.

The values? Those take time to develop. It's those "Values" that will make people write comments on these blog posts that don't agree with the post's sentiment, as they talk about a practice, instead of a value (when they coexist nicely).

For example, on my "Own your team and territory" post, i got quite a few comments that say "You must let the team learn how to do these things etc, which is more in terms of a "value" system.

But in the context of a "Learn initial practices" system, it does make sense, since that person has not yet masterd and feels comfortable with the accompanying princinples and values attached. when they will (and they will eventually) they can (and should!) start questioning their tactics - for at this point, in this context, those initial practices are the right thing:

\= they are easy to follow

\= they will bring some peace to the team and the lead so they can start focusing on more principles

\= the values will have to be "earned" during time.

Test Driven Development is the same way:

1. you start out with the 3 rules of TDD (practices - failing test, code to pass, refactor)
2. you learn why they matter (the principles - test the test, think small, have partial work etc..)
3. you learn the values of a SOLID designed system, and the ability to take and get quick feedback, and start aiming how and when you use TDD within those values.

## Read next

- [Five Questions to ask yourself when getting advice about team leadership](https://www.5whys.com/articles/five-questions-to-ask-yourself-when-getting-advice-about-tea.html): Questions for testing any team leadership advice against the three team maturity stages, plus bonus questions about the author's hidden assumptions.
- [The 3 maturity stages of a software team and how scrum fails to identify them](https://www.5whys.com/articles/the-3-maturity-stages-of-a-software-team-and-how-scrum-fails.html): The chaotic, mid-life and mature stages of a software team, the leadership each one needs, from dictator to coach, and why Scrum Masters miss them.
- [Leadership and the mature team](https://www.5whys.com/articles/leadership-and-the-mature-team.html): Mike Burrows responds to the three maturity stages, arguing self-organization goes beyond self-management and mature teams still need leadership.


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/
