Step #1 – Claim Your Territory, Own your team
Saturday, September 5, 2009
Roy Osherove in First Steps during chaos, Shu

Many dev leads don’t seem to easily see that their territory is constantly compromised by people from the outside.

Compromising territory can be in many simple forms, but they all hurt the leadership and ownership aspect you have as a lead. as yourself these questions:

Internal team implementation decisions that weren’t specifically asked by a customer or have nothing to do with a feature’s integration with other technologies usually should stay fully internal to the dev team. Things like what technology or language to use, what type of database to use and others are things the dev team needs to figure out for themselves.

It’s up to you to go up to whoever is doing this and say “The way we implement features is not your problem. Just tell us what you need, don’t tell us how to build it”.

A good technique to see why this is happening is to ask yourself and whoever is telling you this, why they feel compelled to tell you how to do your job. you’ll find that most times there is a deeper issue underneath that needs to be solved.

this is where the five whys technique helps a lot.

You should be the only entry point to your team. Your team depends on you to make sure they get as least distractions as possible from the outside.

Go up to whoever keeps asking them things find a way to make sure you are the one asking people to do things, and not anyone else. In fact, if you are using some sort of a kanban system, such a thing will not even be necessary.


The key takeaway is that you must be in charge of the boundaries that your team operates within, or you quickly lose control of what is really going on, and find yourself mostly running around trying to see what people are actually doing instead of making sure that the right things get done.

Article originally appeared on Elastic Leadership (
See website for complete article licensing information.