Think about the last meeting that went nowhere. The one that ran 30 minutes over, circled the same point five times, and ended with “let’s take it offline.” What actually happened in that room?
More often than not, it was this: someone was doing someone else’s job. A stakeholder was relitigating a decision that wasn’t theirs to make. And everyone was too polite - or too invested - to say the quiet part out loud: this isn’t your call.
You were hired for a role. That role is what you get paid for, and it is why you specifically were chosen. Everyone around you is in the same position - hired for their role, trusted with their responsibilities. The single most underrated skill in a team is respecting that. Let me make the case.
The line between input and override
Let’s be precise, because this gets misread instantly. Respecting roles does not mean staying silent. Your perspective, your experience, your concerns - share them, loudly and early. That is your job too.
The line is what happens after you share. There is a world of difference between:
- Input: “Here’s what I’m seeing, here’s a risk you might be missing, here’s how we solved this before.”
- Override: “Do it my way.”
A project manager can raise a deadline concern. A project manager telling a developer how to implement the feature has crossed the line. A tech lead can flag that a campaign feels off-brand. A tech lead telling the marketing lead how the business works has crossed it too.
Input improves a decision. Override steals it. And when you steal a decision, you don’t just make a worse call - you tell a capable person you don’t trust them to do the job you hired them for.
Why this quietly decides whether you ship
This is not soft stuff. Role clarity is one of the sharpest predictors of whether an organization actually performs:
- Organizations with clear decision rights see 23% greater revenue growth than those with ambiguous authority.
- Teams with clearly defined roles and accountability are three times more likely to reach top-quartile organizational health.
- Teams that make decision ownership explicit (who is accountable, who is merely consulted) report 70% fewer “who decides?” questions and 25% faster cycle times.
Flip those numbers over and you get the cost of not respecting roles: slower delivery, endless “who owns this” debates, and meetings that generate heat instead of decisions. When everyone can veto everything, nothing moves.
What disrespecting roles actually costs
When people don’t respect roles, the damage is rarely a single bad decision. It’s the slow rot around it:
- Decision paralysis - if any voice can reopen any call, no call is ever final.
- Demoralized experts - the specialist you hired stops bringing their best thinking, because it gets overruled by someone with less context anyway.
- Turf wars - people start defending their territory instead of doing their work.
- Meeting sprawl - every decision needs everyone, because no one trusts the owner to decide alone.
I have watched brilliant teams grind to a halt on exactly this - not because they lacked talent, but because nobody would let anyone else own anything.
Respecting roles is an act of trust, not passivity
Here is where I want to reframe it, because “stay in your lane” sounds like a shrug. It isn’t.
For me, as a servant leader, respecting someone’s role is one of the most powerful things you can do for them. It says: I trust your judgment. This is yours. Own it. That trust is not a nicety - it is fuel. People who feel trusted to own their work bring more of themselves to it, take more responsibility, and grow faster.
The strongest version of this is a principle I’d tattoo on every team: disagree and commit. Argue hard while the decision is open. Bring every concern. Then, once the person who owns the call has made it - commit to it fully, even if you’d have chosen differently. Not grudgingly. Genuinely. Because you trusted the role, and relitigating it later is how you drain a team dry.
How to do it without going silent
Respecting roles is a skill, and here is the practical shape of it:
- Make ownership explicit. For any significant decision, name who is accountable - the one who decides and signs off. Ambiguity is what invites the turf war.
- Offer context, not commands. “Here’s information that might change your decision” beats “here’s your decision.”
- Consult on merit. Pull someone in when their input genuinely improves the outcome - not out of habit, and not to build consensus theater.
- Then defer - and mean it. Once the owner decides, back them. Publicly. Even when you’d have gone the other way.
- Escalate the process, not the decision. If you truly believe the wrong person owns a call, that’s a conversation about responsibilities - not a reason to hijack this one.
And the counterbalance, so this doesn’t curdle into silos: respecting roles is not the same as building walls. Share context generously across boundaries. The goal isn’t isolation - it’s clear ownership inside a team that still talks constantly.
Eleven positions, one game
Watch a football team that actually wins. The striker doesn’t sprint back to tell the keeper how to dive. The keeper doesn’t wander upfield to take the free kick. Not because they don’t have opinions - a striker has plenty of opinions about goalkeeping - but because they understand something simple: eleven people each doing their own job, and trusting the other ten to do theirs, beats eleven people all chasing the ball.
The moment everyone rushes to play everyone else’s position, you don’t get eleven experts. You get a crowd around the ball and an open goal behind you.
Respect the role. Play your position. Trust your teammates to play theirs. That is not stepping back - it is how the team scores.