---
title: "Three reasons not to have your own private office"
url: "https://www.5whys.com/articles/three-reasons-not-to-have-your-own-private-office.md"
canonical: "https://www.5whys.com/articles/three-reasons-not-to-have-your-own-private-office.html"
published: "2011-10-02T19:39:36+00:00"
updated: "2011-10-02T21:42:46.833000+00:00"
tags: ["Anti Patterns", "Influence"]
author: "Roy Osherove"
description: "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."
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/"
---

# Three reasons not to have your own private office

When I was just starting out as a team lead, I remember bemoaning to myself how I wasn't being 'appreciated' enough to have my own office. For geeks like it is can often feel like a status symbol.
But the more time goes by, the more I would rather sit in the same room with the team.

Here are some reasons why, if given a choice to have my own office or have a space with my team, I'd choose to sit with the team:

### **Be in the loop.**

If you're in your own office, you're out of the loop. You're not hearing the rustle and bustle of things being done (or not done). You're not sensing happiness, or frustration, or lack of interest in all things to do with your project from your team. You're just not there to absorb what life is really like being in _your_ team.

### **Lead by example**

If you're in your own office, you can't lead by example as effectively as you can sitting right next to your team. If you're (mostly) always at your team's room, they can see how you act in various situations - from talking with the marketing folks who come by asking for features, to solving time-scheduling problems, to talking on the phone with people (when that conversation can be made in the team room), to managing your own work environment.
Act they way you'd like to see them act in these situations. Lead by example. If you keep your cool on tough technical problems, or dilemmas, or if you lose your temper - people will learn how it's OK or not ok to act in these situations.

### **Handle things before they happen**

If you're right next to the team, and you notice something that, based on your experience, will have important effects that need to be handled (choosing a bad technical route to solve a problem, inability to decide on something, people taking on too many tasks they can't handle..) , you can have a chance to deal with this before something has been 'committed to paper'. you can help either change the course of a decision before it becomes fact. How you act will depend on which team stage your team is in, of course, but regardless of stage, earlier is better, even if you intend to do nothing but shutup and watch people learn something the hard way.

### **What about 'me' time?**

When I suggest this to leaders, they tell me:

- "but I need some privacy, some 'me' time"

    Well, now you know how some of your team members feel. If you can solve that 'me' time problem for yourself without having your own office all the time, you might solve that problem for your team as well - for example you can have a couple of empty meeting rooms with machines or phones where people can spend some time alone or talking 1 on 1.

- "where will I hold me private meetings?"
    In those usually-empty couple of meeting rooms we just discussed.

## 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.
- [How to deal with bad decisions made by the team](https://www.5whys.com/articles/how-to-deal-with-bad-decisions-made-by-the-team.html): How a team lead can steer a self-directing team away from bad technical decisions by asking hard questions, based on Mike Cohn's Succeeding with Agile.
- [Assume you are wrong](https://www.5whys.com/articles/assume-you-are-wrong.html): A tense chat log shows how people tell themselves stories about each other, and how describing facts and assuming good intentions defuses the conflict.


---

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