The Four Boundaries Every Team Has

Every growing company spends years taking walls down and putting new ones up. Some look to turquoise organizations for inspiration: self-managing teams, no fixed bosses, decisions made by the people closest to the work. Others sit much nearer the red end, where one strong leader holds the power and everyone knows it. (Both colors come from Frederic Laloux's map of how organizations develop.)

Whatever the model, every team works inside boundaries. They are what keep a team and an organization intact. They tell people who decides, who does which part, whose interests count and who belongs. Their shape changes as a company grows and reorganizes, but they always come back to the same four.

A team that can't see its boundaries keeps tripping over them, and people call the result personality clashes, politics or "a culture problem." Each boundary comes with a question people carry into every meeting, usually without saying it out loud, and a set of feelings that show up when nobody answers it.

1. Authority: who is in charge of what?

Every team has someone who leads and people who execute. In a self-managing team that authority may sit with a role or a process, but it still sits somewhere. The relationship works in both directions. The people executing have to challenge the person leading, because a leader nobody argues with ends up making avoidable mistakes. The person leading has to stay open to that challenge and still make the call.

Teams that run well put this boundary in writing. In a RACI chart (Responsible, Accountable, Consulted, Informed), the letter that matters most is the A. One Accountable person per decision. A decision with two As effectively has none.

Apple's version is the DRI, the Directly Responsible Individual: every action item from a meeting has one name next to it. GitLab put the DRI into its public handbook. Others give input, but the DRI makes the decision, and consensus isn't required.

What a DRI fixes is the authority vacuum. Picture a steering group of equals with no tiebreaker. Conflicts have nowhere to land, so each person defends their own corner and the group stalls. Naming one owner gives the conflict a place to end. That is what authority is for: holding the tension so people can argue hard and the work still moves.

When this boundary is clear, people feel trusted and take initiative. When it's blurry, they turn rebellious or passive, and the people at the top become suspicious and controlling.

2. Task: who does what?

This is the R and the C. Specialized work has to be divided and then put back together so the product still makes sense.

The risk is that a clean RACI chart makes it easy to say "my column ends here." Good teams draw the line and look across it anyway. People own their part and take an interest in the parts they depend on but don't control.

When this works, people feel competent and proud, and relying on each other feels normal. When the work is badly divided, they feel anxious, incompetent and sometimes ashamed of what they've delivered.

3. Politics: what's in it for us?

Sales wants the discount. Finance wants the margin. Product wants the roadmap protected. These are legitimate interests, and a leadership team needs all of them on the table to see the whole picture. Politics only goes bad when groups can't bargain, or when they define their interest so narrowly that every deal turns into win-lose.

RACI shows this boundary too, in the gap between C and I. Being Consulted means your interests are in the room. A group that keeps ending up as "Informed" on decisions that hit them will feel unrepresented, and sooner or later they find other ways to be heard.

When this boundary holds, people feel empowered and fairly treated. When it fails, they feel powerless and used.

4. Identity: who belongs to "us"?

Engineering. The Kraków office. The founding team. The people who were here before the acquisition. Group identity gives people pride, loyalty and energy for the work.

The challenge is to feel pride without looking down on other groups, and to stay loyal to your own without undermining outsiders. When that balance holds, people are loyal to their group and still respect the others. When it tips, team spirit turns into contempt and distrust.

Where the four collide

The boundaries never act alone. The most common failure starts at the top. A leader wants an empowered team, steps back and names no one in charge. The team fills the gap with closeness. Its identity grows so strong that members hold back their differences of skill and opinion to keep the peace, and nobody draws the task and political lines. The team fails because it feels too much like a team.

The steering group of equals fails the other way: no authority, so every disagreement becomes turf.

Both failures start at the authority boundary, and the other three hold better once it is clear. That's why the A in RACI and the DRI matter as much as they do, whether the company leans turquoise or red.

What this looks like in an OKR meeting

Take a leadership team with one key result that matters more than the rest, say net revenue retention. The KR has one owner, the head of customer success. The authority boundary is drawn.

But that number only moves if sales brings in customers who fit, product fixes what churned accounts complained about, and finance prices renewals sensibly. The owner is accountable for a result that four people produce.

A check-in can go one of two ways. In the first, each person reports their own KRs and the others wait for their turn. The task boundary works like a wall, and everyone's identity stays tied to their function: my KRs, my department.

In the second, people get involved in each other's key results. The product lead asks what the churned accounts said. The sales lead admits two deals from last quarter were a poor fit. Finance offers the renewal data nobody asked for. Each of them is pushing on a boundary: taking an interest in work they don't own, and putting their own function's interests on the table where the team can see them.

The owner still makes the call. That is what makes the pushing safe. Because the authority boundary is clear, a hard question about someone's KR reads as help.

Over a few cycles, the team's identity moves. People stop sitting in the meeting as the head of their function and start sitting in it as members of the leadership team, what Patrick Lencioni calls the "first team." Relationships get stronger because people find out they can disagree, press each other and still be on the same side. A clear owner makes the pushing possible, and the pushing turns a group of function heads into a team.

Use your feelings to find the boundary

The feelings in each section are diagnostic. When a check-in leaves you defensive, ashamed, unheard or quietly contemptuous of another group, the feeling is pointing at a boundary. Ask which of the four questions has no answer right now: who is in charge of what, who does what, what's in it for us, or who belongs to us. (More on this in Your feelings are data.)

Three questions for your next OKR meeting:

• Does every key result have exactly one name next to it?
• Did anyone ask about a KR they don't own, beyond "is it on track?"
• Who was "informed" about a decision they should have been consulted on?