---
title: "Spend at least 50% of your time with your team"
url: "https://www.5whys.com/articles/spend-at-least-50-of-your-time-with-your-team.md"
canonical: "https://www.5whys.com/articles/spend-at-least-50-of-your-time-with-your-team.html"
published: "2009-09-10T06:36:37+00:00"
updated: "2014-05-22T22:18:48.003000+00:00"
tags: ["First Steps during chaos", "Shu", "meetings", "schedule"]
author: "Roy Osherove"
description: "Why a team lead should block 50% of each day as team time, and how to use the Five Whys and assertiveness to cut down on meetings that add no value."
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/"
---

# Spend at least 50% of your time with your team

To be an _effective_ team lead, you need to actually spend time with your team. Otherwise, you won't be able to [do daily stand-ups](https://www.5whys.com/articles/daily-standup-meetings-introduction-and-5-useful-tips.html), do [code reviews](https://www.5whys.com/articles/step-4-start-doing-code-reviews-seriously.html), or sit down and pair with a team member every once in a while.

And no, "I have too many meetings" is _not_ a good excuse.

### "But I _do_ have too many meetings to attend each day!"

Then it's time to stand up for your team's rights  - their basic right is to have a team lead present to help solve problems and bottlenecks that the team can't figure out alone, and to have a lead that helps them learn how to overcome problems.

- Go to your outlook schedule and _book_ 50 % of each work day during the week under "team time". Make this a recurring meeting that no one can override.
- Look at the list of current meetings you attend and start trimming them down to meetings you really do need to attend, and ones where the team or you are not getting any value out of. It's sometimes valuable to start asking the Five Whys for each meeting, and see whether you can find a way to solve the problem that the meeting is trying to solve. For example:

-    
    - Meeting: "Daily meeting of department heads"
    - Length: 1-2 hours
    - Time I actively participate in the meeting: 5-10 minutes
    - Time I actively listen in the meeting: 30-40 minutes
    - Why do I have to be in this meeting? _I'm not sure_
    - What do people usually ask me in this meeting? _general questions about my projects progress._
    - _Why? Because they don't have any other way to know_
    - _Why? because **there is no clear and visible progress on my projects**_
    - _Why? Because I haven't made this a reality yet_

Do you know what you should do now to avoid this meeting?

### Be assertive

at the very least you could take these actions about various meetings where you only need part of the time to be inside or none at all:

- Tell (don't ask!) who ever is running the meeting that you will no longer be available to be in it

If they ask "But then how will **I**..." then you know what it is you need to deliver in terms of knowledge so as to make the meeting unneeded.

If they ask "But then how will **YOU**..." then you will realize that you may not need that information, or are getting it in a different way, or that you may indeed need to be in this meeting, but for a shorter  period of time.

- Tell (don't ask!) who ever is running the meeting that you will only be available for 30 minutes during the meeting (otherwise development will suffer).

After 30 minutes - leave the meeting. Stand up for your decisions. See what happens.

## Read next

- [Daily Standup Meetings - Introduction and 5 useful tips](https://www.5whys.com/articles/daily-standup-meetings-introduction-and-5-useful-tips.html): How to run a daily standup meeting with the three questions, why each question matters, and five hard-learned tips for keeping it under 15 minutes.
- [Step #4 - Start doing code reviews – Seriously](https://www.5whys.com/articles/step-4-start-doing-code-reviews-seriously.html): A team leader's guide to serious code reviews: what to look for, reviewing every check-in yourself at first, then training the team to review its own code.
- [Step #1 – Claim Your Territory, Own your team](https://www.5whys.com/articles/step-1-claim-your-territory-own-your-team.html): Why a dev lead must claim the team's territory: keep implementation decisions inside the team, be its single entry point, and ask why outsiders interfere.


---

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