---
title: "Yelling at team members"
url: "https://www.5whys.com/articles/yelling-at-team-members.md"
canonical: "https://www.5whys.com/articles/yelling-at-team-members.html"
published: "2011-06-17T21:08:02.095000+00:00"
updated: "2011-06-17T21:08:02.095000+00:00"
tags: ["Anti Patterns"]
author: "Roy Osherove"
description: "Why yelling at team members destroys trust and solves nothing, and the steps a team leader should take right after losing their temper."
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/"
---

# Yelling at team members

This is perhaps one of the worst things a team leader could ever do with a team. Multiply that by 10 if that yelling is done in public.

It does not matter \*how much\* frustration you feel. It does not matter \*how\* much that team member might actually deserve it.

> Do not yell at your team members.

### By yelling, what happens is:

- You remove any good will by that team member to ever want to work with you again
- You personally hurt their feelings (a little or a lot, depending on their character, but you do)
- If you're not hurting them, they view you as weak and unable to control the way you behave in public or in person
- You are NOT solving the problem. you are just venting.
- They are not really listening to you. they are looking at you, shouting.

### "What can i do if I just can't control it?"

That is the weakest most pathetic argument I've heard people say. You \*have\* to control it, and it's not a matter of yes or no. The only time you get to be a yelling-at-your-team-members team leader who doesn't get kicked out after a few months is if you're the owner, or you're part of the owner's family.

Get a hobby that involves punching something. Or get a different type of job.

### Take the following steps every time you find yourself yelling at someone:

- STOP yelling immediately, and excuse yourself  - "I'll be back in a few minutes"
- When you come back after taking a breather, APOLOGIZE to the person you just yelled at, in private.
- Don't talk to them about the subject you just yelled at them for. Wait ONE FULL DAY.
- The next day, make a short list of the points you wanted to make, in a calm mood. Use the word "I" to describe what you feel - "I feel like you just don't care what I ask you to do"
- That's a start.
- When you're not in a more calm type of conversation, you're on a better way than you were.

## Read next

- [12 Behavior Anti Patterns You Will Face As a Software Team Leader](https://www.5whys.com/articles/12-behavior-anti-patterns-you-will-face-as-a-software-team-l.html): Twelve team member behavior anti-patterns and three outside disruptions a software team leader faces in survival mode, with how to respond to each one.
- [Three reasons not to have your own private office](https://www.5whys.com/articles/three-reasons-not-to-have-your-own-private-office.html): Why a team leader should sit with the team rather than in a private office, to stay in the loop, lead by example and handle problems early.
- [my worst team leaders](https://www.5whys.com/articles/my-worst-team-leaders.html): A short list of traits shared by the worst team leaders Roy Osherove worked for, from never coaching or challenging him to ignoring impediments.


---

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