---
title: "A good leader won't need to ask"
url: "https://www.5whys.com/articles/a-good-leader-wont-need-to-ask.md"
canonical: "https://www.5whys.com/articles/a-good-leader-wont-need-to-ask.html"
published: "2011-06-06T17:43:20.042000+00:00"
updated: "2011-06-06T17:43:20.042000+00:00"
tags: ["Anti Patterns"]
author: "Roy Osherove"
description: "Why a team leader who has to ask people what they did well this year has not been paying attention, and a quick way to compile and fix that."
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/"
---

# A good leader won't need to ask

A good team leader would not need to ask you about the good things you've done in the past year. They should be attentive enough to your personal progress, and helping you shape your learning, that they might actually know about more things you did great this year than you.

If you are that team leader, and you need to ask, it may be good to take 30 minutes of personal time, and review within yourself, what you think that person has done good this year. If you can't, try the following approach:

Ask colleagues of that person about one good thing they have seen him do this year (or month). compile a list of five such things.

Now, compile a list of actions that you **will** take,   in the coming month, and year, to make sure this never happens again.

## Read next

- [Yelling at team members](https://www.5whys.com/articles/yelling-at-team-members.html): Why yelling at team members destroys trust and solves nothing, and the steps a team leader should take right after losing their temper.
- [The Chaos Addiction](https://www.5whys.com/articles/the-chaos-addiction.html): How survival mode becomes a self-reinforcing addiction that cuts quality and learning time, and why a team leader must take a risk to break the cycle.
- [The Fear Of Failure And What To Do About It](https://www.5whys.com/articles/the-fear-of-failure-and-what-to-do-about-it.html): Using a Milton Glaser video on the fear of failure, a look at why team leaders must take personal risks and how timed experiments can lower them.


---

## 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/
