Office Politics Is What Fills a Decision Nobody Owns
Watch the video version:
A decision lands on your desk that sits between two teams. Say it is who decides when a shared service can change its interface. The platform team says it is theirs. The product team says it is theirs. Nobody ever wrote it down. By the time it reaches you, one side has already framed it. Someone caught you after the standup or booked fifteen minutes on Thursday, and they have told you what the problem is, why it is urgent, and what the obvious answer is. The engineer who knows that service best has not said a word. Nobody asked, and there was no meeting to be in. You decide on the version you heard.
Most advice calls this politics, and it offers two answers. The first is to learn to play it: build relationships above you, keep a running list of your wins, manage up, and reach the decider before the meeting does. The second is to stamp it out: treat it as a culture problem, model transparency, and call out back-channeling when you see it. Both treat politics as behavior. Neither asks which decision had no written owner.
A decision with no written owner goes to whoever has access to the decider, not whoever has the information. That is most of the politics a team runs into day to day. The first answer makes it worse. It teaches managers to win the gap, and whoever keeps winning it has every reason to keep the decision unwritten. If you are winning that race right now, this piece is not on your side.
Here is how it runs. With no written owner, a recurring decision between two teams goes up to the leader they share. That is The Escalation Default: decisions route upward because the structure never said where they belong. Once the decision is on its way up, it is a race. Whoever frames it to the leader first, and most often, wins. The engineer who knows the system best is rarely in that conversation.
The team learns from every round. Access beats information, so people escalate sooner and stop settling things peer to peer. The quiet ones stop bringing their case at all. When a polished document stops proving anyone thought, seniority fills the gap. When nobody owns the decision, access fills it.
It costs you twice. First, your calendar: an unowned decision moves only as fast as the best-connected person can reach you, and you become the switchboard. Second, the decision itself. The losing side reopens it at their next moment of access, so the same decision gets made two or three times, each time late, at the top, by the person with the least context. The best technical judgment on the team loses to proximity, and those people either leave or go quiet.
Writing the owner down does not end lobbying. It changes what the lobbying is about: people still argue, but they argue the case to the owner, with the information on the table, instead of racing each other to you. If you have tried this before with a chart of roles and watched it die, look at what it named. It named roles, not decisions, and nobody above the leader ever confirmed it, so the first senior person who disagreed reopened it.
So stop refereeing the race and close the gap. Start with the hard part, which is you: you have been deciding these on whoever framed them first. The race runs through you, so you are the one person who can end it. The next time someone brings you a decision that belongs to another team, or sits between two, send it back to the owner, even when the person in front of you is right. If they are right, they will win the case with the owner too. Everything else here depends on that step, because written ownership breaks at the leader's exception. The first "just this once" teaches the team that access still works, and a decision boundary holds for exactly as long as someone keeps re-proving it.
Then write the owners down. I call it the Owner Line: one written line per recurring decision, naming who owns it, at what level, and who they have to hear from before they decide. Those lines are your team's Decision Boundaries. Build the list from the last month: every decision that reached you through access instead of through an owner. Give each one a level in the Five-Level Decision Framework. I built the Five-Level Decision Framework to assign decision ownership: at Level 1, the team decides and acts without reporting; at Level 5, the leader decides alone. Most of these decisions belong to one team, at Level 1 or 2: the owner decides and either acts without reporting or informs afterward. A genuine boundary decision, where each side holds something the other lacks, goes to Level 3, decided jointly.
Write down who the owner has to hear from before deciding, usually whoever knows the system best. That line puts the quiet engineer back in the decision. Then have the level above you confirm the boundaries before the next ambiguous case arrives, so a senior reopen runs into a written decision someone above already backed. Once a decision has an owner, reaching you first stops mattering.
Take the last three decisions that crossed a team line and ended with you. Write two names next to each: who brought it to you, and who knew the most about it. If the names differ, the decision went to access, and you are the one who ruled on it. Check whether it has a written owner today. If it does not, it will come back the same way. The next time someone brings you a decision first, ask whose decision it is before you hear the case. If nobody owns it, write an owner down, with the level and who they have to hear from, before anyone decides.
LeadershipOS™ walks through Decision Boundaries: who owns which decisions, under what conditions, and when to escalate, along with The Escalation Default that routes unowned decisions up to you: https://TheLeadershipOSBook.com
Why "you're empowered to decide" makes a capable team freeze, and the one definition that lets them act without asking.
