You've seen the org chart. Boxes connected by solid lines. Dotted lines. Maybe a few squiggly ones nobody can explain. Plus, it looks clean on a slide deck. In practice? It's where most execution goes to die But it adds up..
Establishing lines of authority isn't about drawing pretty diagrams. It's about deciding who can say "yes," who has to ask "why," and who gets stuck saying "I'll check with my manager" while the competition ships product Still holds up..
What Is Establishing Lines of Authority
At its core, this is the organizing function of management — the deliberate design of who reports to whom, who decides what, and how information and decisions flow through an organization. Textbooks call it "defining the hierarchy of authority" or "creating the chain of command." Real operators call it "figuring out who owns what so stuff actually gets done.
Easier said than done, but still worth knowing.
It's not just reporting relationships. It spans:
- Decision rights (who approves the budget vs. who spends it)
- Accountability boundaries (where one role ends and another begins)
- Escalation paths (what happens when two leads disagree)
- Communication protocols (who needs to know what, and when)
Formal vs. Informal Authority
Here's what most guides miss: the org chart is the formal structure. The informal structure — who people actually listen to, who holds tribal knowledge, who the "go-to" person is for getting things unblocked — often carries more weight No workaround needed..
Smart leaders design for both. They know the dotted-line relationship on paper means nothing if the person holding the pen doesn't respect it.
Centralized vs. Decentralized Authority
This isn't binary. It's a spectrum, and different decisions sit at different points Worth keeping that in mind. But it adds up..
Centralized — key decisions made at the top. Faster alignment, slower execution, bottleneck risk. Works for crisis mode, highly regulated environments, or early-stage startups where the founder is the strategy And that's really what it comes down to. Less friction, more output..
Decentralized — decisions pushed to the edges. Faster execution, better local context, higher coordination cost. Requires clear guardrails and high trust. The default for mature product orgs and distributed teams.
Most companies need a hybrid. Product scope and hiring decentralized. Strategy and capital allocation centralized. The mess happens when nobody explicitly decides which is which.
Why It Matters More Than You Think
Ambiguous authority doesn't just cause confusion. In practice, it creates drag. Silent drag. The kind that doesn't show up in Jira but shows up in missed deadlines, duplicated work, and the slow erosion of trust.
The Cost of Unclear Lines
- Decision paralysis — two people think they own the call, so nobody makes it
- Shadow hierarchies — work routes around the official structure through backchannels
- Accountability gaps — "I thought you were handling that" becomes the default post-mortem
- Talent drain — high performers leave when they can't get decisions made
I've watched a six-person decision-making body form organically because nobody clarified who owned a product line. Still, six people. For a feature that needed a yes/no. It took three weeks.
The Hidden Benefit: Psychological Clarity
When people know their lane — and know others' lanes — they stop second-guessing. Think about it: they stop CC'ing five people "just in case. " They operate with autonomy within boundaries. Worth adding: that's not bureaucracy. That's freedom with guardrails.
How to Design Authority Lines That Actually Work
This isn't a one-time exercise. It's a design problem you revisit every reorg, every strategy shift, every time the team doubles Small thing, real impact..
1. Start With Decisions, Not Titles
Don't start by drawing boxes. Start by listing the critical decisions your organization makes repeatedly:
- What goes on the roadmap? On top of that, - Who gets hired (and fired)? Plus, - How is budget allocated? - What defines "done" for a release?
- Who resolves cross-team conflicts?
Map each decision to a single owner. Which means " One person. Practically speaking, not a committee. Not "the team.Then define who they consult, who they inform, and who can veto But it adds up..
2. Use RACI — But Don't Worship It
RACI (Responsible, Accountable, Consulted, Informed) is a tool, not a religion. Use it for the 20% of decisions that cause 80% of the friction. Skip it for the rest.
Pro tip: If your RACI chart has more than three "Accountable" people for any decision, you don't have a RACI problem. You have an authority problem.
3. Define Span of Control Intentionally
Span of control = how many direct reports a manager has. It depends on:
- Complexity of work (creative vs. Classic theory says 5–7. Modern reality? repetitive)
- Experience of reports (senior ICs need less oversight)
- Coordination needs (high-interdependence teams need tighter spans)
- Manager scope (player-coach vs.
A manager with eight senior engineers doing independent work is fine. A manager with four junior PMs on interdependent features is drowning.
4. Clarify Dotted Lines Before They Become Tripwires
Dotted lines exist for coordination — not authority. So it's solid. If a dotted-line manager is giving performance feedback, assigning work, or blocking promotions, the line isn't dotted. And someone forgot to update the chart It's one of those things that adds up..
Rule of thumb: Dotted-line relationships should never carry:
- Compensation authority
- Hiring/firing power
- Final say on prioritization
If they do, make it solid. Or kill the dual-reporting entirely.
5. Build Escalation Paths Before You Need Them
Two peers disagree on priority. Their managers disagree. Now what?
Every org needs a pre-agreed escalation ladder:
- Peers attempt resolution (timeboxed: 24–48 hours)
- Managers align (timeboxed: 48 hours)
Publish this. Practice it. The first time you use it shouldn't be during a crisis.
6. Review Quarterly — Not Annually
Authority lines rot. A reorg happens. So naturally, a product pivots. In real terms, a key person leaves. The chart stays the same Small thing, real impact..
Put a recurring 30-minute review on the calendar with your leadership team. Ask:
- What decisions are stuck?
- Where are people confused about ownership? So naturally, - What informal paths have become critical? - Does the chart reflect reality?
Update it. Communicate the change. Move on Surprisingly effective..
Common Mistakes That Keep Happening
Mistake 1: Confusing Collaboration With Shared Authority
"We're a collaborative culture" is not an authority model. It's a values statement. On top of that, collaboration works within clear ownership. Without it, you get consensus theater — meetings where everyone nods, nobody commits, and the loudest voice wins by default Easy to understand, harder to ignore. Less friction, more output..
Mistake 2: Over-Engineering the Matrix
Matrix structures sound sophisticated. Dual reporting. This leads to shared resources. That's why cross-functional squads. In practice, they create two bosses for every employee and zero accountability for outcomes Easy to understand, harder to ignore..
Unless you're a global enterprise with genuine multi-dimensional complexity (geography × product × function), you probably don't need a matrix. You need clear product ownership with strong functional guilds for standards and career growth.
Mistake 3: Delegating Without Authority
"I'm giving you ownership of this initiative!" — but you need VP approval for any spend over $5K, legal sign-off on every vendor, and HR approval for contractor hours. That's not ownership Easy to understand, harder to ignore..
glorified task list.
If you're delegate ownership without the corresponding decision-making power, you create a bottleneck by design. You aren't empowering your team; you are setting them up to fail by forcing them to ask for permission at every milestone. True ownership requires a defined "budget of autonomy"—a clear threshold of what an individual can decide, commit, and execute without seeking higher approval.
Conclusion: Clarity is a Competitive Advantage
Organizational charts are often treated as static artifacts—dusty diagrams in a handbook that no one reads. Which means in reality, they are the operating system of your company. When the OS is buggy, full of conflicting commands and broken permissions, the entire machine slows down No workaround needed..
A clear authority model isn't about creating silos or rigid hierarchies; it’s about creating speed. When everyone knows who makes the final call, who provides the technical standard, and where the escalation path leads, the friction of "who's in charge?" vanishes. This allows your people to stop navigating politics and start solving problems.
Stop building complex matrices to solve simple communication problems. Stop hiding ambiguity behind "collaboration." Define the lines, respect the boundaries, and empower your people to actually do the work they were hired to do.
