---
title: "A Manifesto For Software Team Leaders - Take 1"
url: "https://www.5whys.com/articles/a-manifesto-for-software-team-leaders-take-1.md"
canonical: "https://www.5whys.com/articles/a-manifesto-for-software-team-leaders-take-1.html"
published: "2011-12-08T05:21:52+00:00"
updated: "2014-05-22T22:58:02.063000+00:00"
tags: ["Conference", "Meta"]
author: "Roy Osherove"
description: "The first draft of a manifesto for software team leaders, a list of leadership values open for reader comments, written ahead of the Stoos summit."
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 Manifesto For Software Team Leaders - Take 1

It occurs to me that a manifesto for a software team leader is not a bad idea. And, I intentionally not want it to be an "Agile" related manifesto, but more of a management/people/leadership manifesto that applies to the software industry.

Perhaps later we can say that it applies to a broader scope, but software is where I am focusing, until proven otherwise.

I would love to hear your thoughts on what items would appear in such a manifesto. Here are some things I would think would make a good fit, but I don't think I can articulate them well enough to be concise and to the point enough to make a manifesto:

- **Adjusting leadership to the problems the team is facing**, over blindly leading in your preferred manner
- **Experimenting with humans**, over status quo
- **Challenging yourself as a leader to become better,** over staying safe
- **Embracing yours and your team's fear and discomfort as learning,** vs. staying in safe, calm and cool waters
- **Spending more time with your team** , vs spending more time in meetings
- **Also Focusing on People Skills** vs. just learning methodological practices
- **Taking Personal Risks** vs. keeping status quo
- **Challenging and teaching your team to solve their own problems** vs. Solving everyone else's problems yourself
- new: everyday - you and your team are better at something, than you were yesterday

Dear reader - if you think you have more ideas, or that some of these are crap - I'd love to know, and why. if you think you can word these better (and I'm sure that should be pretty easy) - please help me out in the comments.

**Trying this out in real life**

In my [upcoming team leader course in Norway next week,](http://www.programutvikling.no/kurskalenderoversikt.aspx?mid_1=1352&mid=1535&id=1269909) I will try to create a shared manifesto like this for the first time. We'll see what we get…!

**Stoos**

I'll be pondering this out loud in the [Upcoming Leadership Summit in Stoos.](http://www.noop.nl/2011/12/global-management-warming-starts-in-switzerland.html) I'm honored to have been asked to attend,and if you read that blog post carefully, you'll see that one of the things he writes there is "probably not another manifesto". so, there - our first disagreement? should be interesting!

## Read next

- [Software Team Leader Manifesto - Take #2](https://www.5whys.com/articles/software-team-leader-manifesto-take-2.html): The second draft of the team leader manifesto: adapt leadership style to the team, embrace risk, fear and experimentation, and lead people.
- [Team Leader Manifesto - Take #3](https://www.5whys.com/articles/team-leader-manifesto-take-3.html): The third draft of the team leader manifesto, which defines a leader's success as the team's growth in self-organization and adds slack time to learn.
- [Team Leader Manifesto - Take #4](https://www.5whys.com/articles/team-leader-manifesto-take-4.html): Roy Osherove's Team Leader Manifesto in full: great teams are grown, not hired, by continuously growing people's skills to the point of self-organization.

## Topic

- [Team Leader Manifesto](https://www.5whys.com/topics/team-leader-manifesto)


---

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