---
title: "Call for content – what do new team leads need to know on the first day?"
url: "https://www.5whys.com/articles/call-for-content-ndash-what-do-new-team-leads-to-know-on-the.md"
canonical: "https://www.5whys.com/articles/call-for-content-ndash-what-do-new-team-leads-to-know-on-the.html"
published: "2009-09-05T22:43:33.247000+00:00"
updated: "2009-09-05T22:43:33.247000+00:00"
tags: []
author: "Roy Osherove"
description: "A call for reader input on what new software team leads need to know on day one, including tips, essential topics and lessons not covered in any book."
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/"
---

# Call for content – what do new team leads need to know on the first day?

About 5 minutes after I posted about eh existence of this blog on twitter, I’ve gotten lots of great feedback (and various little nitpickings) about the content, what I shoudl talk about and things that I might cover.

This is your chance to influence the topics this blog covers : What topics do you think are **essential** for new team leads to learn if they’ve never done it before?

What tips or tricks would you give them?

What topics would you make sure they learn?

What topics have you learned about leading teams that are not covered in \*any\* book?

## Read next

- [Video: Influence Strategies](https://www.5whys.com/articles/video-influence-strategies.html): A pointer to Richard Banks' video on influence strategies based on Linda Rising's work, and why team leads must influence others. It is no longer hosted.
- [Technical Anti Patterns Arising from Social Inadequacy](https://www.5whys.com/articles/technical-anti-patterns-arising-from-social-inadequacy.html): On Jerry Weinberg's Roundtable on Technical Leadership, listing its chapter five anti-patterns, like not asking for help, that stem from social gaps.
- [12 Lessons Learned for a New Team Lead](https://www.5whys.com/articles/12-lessons-learned-for-a-new-team-lead.html): Guest post by Oren Ellenbogen with 12 lessons for a new team lead, from writing down daily decisions and handling cynicism to making others shine.


---

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