If you’ve ever walked out of a meeting thinking, “Great talk…but who’s actually doing what?”
You’ve just stumbled onto the most expensive problem in your business: unclear roles.
Teams don’t stall because people are lazy. They stall because the work lives in a fog. Titles masquerade as responsibilities. Decisions float. Accountability hides. And leaders—you—wonder why velocity is gone and your calendar is stuffed with “alignment meetings.”
Let me be blunt: clarity isn’t a nice-to-have. It’s oxygen.
And without it, good teams suffocate.
A high-growth product company brought me in the week a major release slipped…again. They had talent. They had budget. They had Slack channels for their Slack channels. What they didn’t have?
Clarity.
The Monday standup should’ve been crisp. Instead, it was déjà vu hell.
“Who owns the release notes?”
“Who decides on the final feature set?”
“Who’s point if the integration fails?”
Each question got the same answer: “We’ll handle it as a team.”
Which, of course, meant nobody handled it at all.
By Wednesday, the week was drowning in meetings. By Friday, the CEO slumped in her chair and said the line every leader thinks explains it: “We just can’t get aligned.”
Wrong. Alignment wasn’t the issue. Clarity was.
Nobody knew who was responsible, who had to be consulted, who should just be informed, or who could actually make the call.
We didn’t fix it with more headcount or more processes. We fixed it by drawing lines. Within one release cycle, the fog lifted. Same team. New clarity.
Night and day difference.
Think of work like a relay race. You can have the fastest runners in the world, but if the baton handoff is sloppy, you still lose. That’s what happens when ownership is fuzzy: everyone touches the baton, nobody takes responsibility for carrying it forward.
Leaders often mistake role confusion for underperformance. But most of the time, it’s not the people—it’s the system.
Here’s how the symptoms show up:
Teams hold endless pre-meetings before the “real” meeting. Translation: no clear owner, so politics are doing the work.
Calendars fill with “quick questions” that could’ve been answered if decision rights were clear.
Heroics are celebrated while handoffs are broken. Translation: you’re rewarding rescue missions instead of building a system that doesn’t need rescuing.
When you see these patterns, don’t swap out the players. Redraw the lanes.
When we mapped the launch team’s work as a system—who starts, who owns, who decides, who executes, who closes—it became obvious where things were breaking. Two roles thought they “owned” the same task, which meant nobody did. Five people had to “approve” messaging, which guaranteed a bottleneck.
I use a simple lens:
No more “we” language where you need a name. No more “team decides” where you need a tie-breaker.
Call your shot.
Once we named a single owner and a single decider for each lane, momentum snapped back. Meetings shrank. Escalations cleared. The baton moved.
Defining roles is the first step. But once you draw the lanes, you need to protect them with clear rules—otherwise the fog creeps right back.
Here’s where leaders often dig their own grave: confusing consensus with collaboration.
Consensus feels safe. It keeps everyone “involved.” But it also keeps everything slow. While you’re chasing unanimous agreement, your competitors are shipping.
One exec I coached had a multi-dollar idea stuck in limbo because every decision had to go through “group agreement.” By the time they inched forward, the market had moved without them. He wasn’t protecting harmony. He was protecting indecision.
Consensus is a tax. Pay it only when a decision is values-loaded or irreversible. For everything else, empower the owner and move.
Decision rights belong to a name, not a committee. Your job as a leader is to give the owner boundaries and a brief: here’s the scope, here are the guardrails, here’s when you escalate, here’s the clock you’re working against.
Then let them run with it.
Will they make mistakes? Absolutely. But an imperfect decision made fast beats a perfect one made too late.
Escaping the consensus trap takes discipline. Your role as a leader is to defend the lanes, not keep everyone comfortable.
Every industry leader tells me the same thing: “….but Tish, we’re different. We’re complex.”
Of course you are. Everyone is. Complexity isn’t a reason to avoid clarity. It’s the reason you need more of it. And if you’re leaning on job descriptions as your answer? Those are legal artifacts, not operating clarity.
Job descriptions describe status. Roles define outcomes.
If you’re scaling, role clarity isn’t a one-time workshop. It’s an operating habit. Every time you add a product, a region, or a leader, redraw the lanes. Because clarity decays as fast as you grow.
Which raises the question: how do you put this into practice?
Here’s a way to test your team’s clarity and reset the lanes where they’ve blurred.
List the top 10 recurring workflows (e.g., product launch, enterprise deal, incident response, hiring). For each, create a one-page Role Charter with these fields:
Owner, Decider, Executors, Consulted, Informed
Purpose (why the role/work exists)
Critical Outcomes (3–5)
Decision Rights (can decide / must consult / must escalate)
Interfaces & Handoffs (who receives, what “good” looks like)
Meet with each team member. Ask only these questions:
“What do you believe you own end-to-end?”
“Where are you unclear or waiting for permission?”
“Where do your responsibilities overlap with someone else’s?”
“Which decisions do you think you can make—vs. ones you feel you must escalate?”
Bring the team together. Share the truth, on a wall or in a doc. Circle conflicts and orphans (work with no owner). Appoint one owner per outcome. Name the decider. Simplify the consulted list.
Define budgets, timelines, and risk thresholds. Establish when standups happen for work, and when reviews happen for decisions. Different meetings. Different goals.
Re-run the audit every quarter or after any major change (new product, new market, new leader).
Leadership isn’t about knowing all the answers. It’s about building a system where the right people make the right calls at the right speed, without you playing traffic cop.
That launch team we talked about in the beginning didn’t suddenly get smarter. They got clear. And once they did, everything moved.
Define the role. Align the lanes. Protect the process.
Do that, and your team won’t just move faster, they’ll move with confidence. And when a team has clarity, a company becomes dangerous…in the best way.
