Swim lanes for leaders: Fewer meetings, faster decisions

At a certain stage, your agency doesn’t add meetings because you love meetings. You add meetings because decisions aren’t sticking.

The same topics keep coming up. Leaders need to get aligned… over and over again. People keep adding stakeholders to the invite list, “just in case.” And as the owner, you keep getting pulled in as the tie-breaker—often because nobody is sure who’s allowed to make the call.

If this feels familiar, you may not have a people problem—you may have a design problem. The most expensive leadership issues in agencies often come from things nobody formally designed: decision ownership, role boundaries, escalation paths, and what “good” looks like for each leader.

Fortunately, the solution is simpler than it sounds: define “swim lanes” for leadership decisions—including guardrails and escalation rules—so your leaders can make decisions without needing a meeting sequel.

Meetings aren’t inherently bad, and some are unavoidable. But over-meeting is a problem.

What I mean by “swim lanes for leadership decisions”

Swim lanes are a shared definition of who’s in charge of what—so people stay out of each other’s way and focus on results instead of second-guessing.

When we apply this to your leadership team, two layers are especially important:

• Decision authority: who gets to make decisions in this lane
• Escalation rules: when (and how) it bumps up a level

Some people call this “decision rights”—but the name is less important than using the concept.

The practical version is: Who decides what, within what guardrails—and what requires escalation.

When you get that clarity right, two things happen: leaders stop hedging, and meetings stop multiplying.

Why unclear leadership swim lanes create more meetings

When authority is unclear, smart people protect themselves. That usually looks like:

• Hedging: “Maybe” language instead of a call.
• Attendance creep: “Let’s invite them just in case.”
• Re-litigation: “Let’s revisit” because nothing feels final.
• Escalation by default: You become the safety net—not because you insist on it, but because the system quietly requires it.

This is why meeting-reduction efforts fail when they start with the calendar.

Your team needs to know who makes key decisions, or you’ll struggle to cut meeting sprawl. You have to make decisions stick.

The leadership decision categories that need to swim lanes

You do not need to map every possible decision. Start with the categories that create recurring leadership debate.

Here are five that cover most agencies:

• Strategic direction: positioning, service lines, target market shifts
• Pricing decisions: pricing changes, discounting, write-offs
• Client risk decisions: escalations, staffing changes, scope enforcement
• People decisions: hiring/firing thresholds, promotions, comp exceptions
• Operating system decisions: process/tool changes that affect multiple teams

If your leadership team debates the same issue repeatedly, it likely lives in one of these categories—and your swim lanes aren’t clear enough yet.

The model: authority, guardrails, escalation, and ARCI

Here’s how to make swim lanes operational without turning it into a bureaucratic project.

Assign the decider

The fastest way to reduce meetings is to stop treating every decision as a group decision.

For each lane, assign one decider. Others can provide input, and the decisionmaker should be willing to debate topics if someone else feels strongly about them—but one person owns the call.

This prevents the most common leadership failure mode: “everyone has a vote, so nobody decides.”

Example: “Why am I not on every account meeting?”

A leader complains they aren’t included on every account meeting—often because they’re used to being central, or because they want visibility.

Here’s a non-dysfunctional solution:

1. Clarify that the senior Account Leader owns account meetings.
2. Assign the leader to talk directly with that Account Leader.
3. Create the boundary that they’ll only escalate to you if they can’t resolve it peer-to-peer.

That does two things at once: it reinforces the lane (the Account Leader decides) and it prevents triangulation (you don’t become the first stop).

The swim lane isn’t “who gets invited”—it’s “who owns the function and the decisions in it.”

Add guardrails

Deciders need boundaries. Otherwise you get chaos—or you get leaders who won’t decide because they’re afraid of stepping on others’ toes.

Guardrails are those boundaries. You can set them based on:

• Dollar thresholds
• Client tier
• Risk level
• Strategic impact
• Timing/commitment constraints

One common guardrail pattern: a leader can authorize exceptions up to a threshold, and must escalate above it. For example, you might decide an account manager can make decisions up to $5,000. An account director can make decisions up to $15,000. Your VP of accounts can make decisions up to $50,000. And anything beyond that, it escalates to the owner.

That’s a complete swim lane in miniature:

• Decider: the leader
• Guardrail: “up to X”
• Escalation: “above X”

Define escalation rules

Guardrails aren’t enough unless you also define what escalates and how. Be sure to define what escalates vs. what doesn’t, and what a “good escalation” looks like.

A good escalation includes the issue, options considered, and a recommendation.

If escalations show up as vague “heads up” messages, you end up doing you team’s job again—and owner optionality disappears.

Use ARCI/RACI to clarify involvement after you know who decides

While swim lanes answer “who’s in charge of what,” and guardrails and escalation rules answer “where are the boundaries,” ARCI/RACI helps answer who is consulted before making a decision. And it includes who is informed (often after the decision)—and who’s responsible for executing the plan.

Swim lanes answer “who’s in charge of what”—and then guardrails and escalation rules answer “where are the boundaries.”

At the leadership level, ARCI is especially helpful for preventing a swoop-and-poop—because everyone can see whether they’re in the Consulted lane or the Informed lane.

Three examples of leadership decision swim lanes in the real world

These are the kinds of decisions that quietly create meeting sprawl when they aren’t lane-ified.

Example 1: Pricing decisions between Sales and Delivery

This is extremely common: Sales wants speed. Delivery wants realism. Nobody wants to be the bad guy.

In one agency, the Head of Delivery and Head of Sales kept butting heads about pricing and commitments. The owner created two pricing lanes, plus an escalation path:

• If it’s productized scope, the Head of Sales can sign off on what a salesperson plans to tell the client.
• If it’s custom scope, the Head of Delivery must be consulted before commitments are made.
• If they disagree, it escalates to the owner (who oversees growth and final tradeoffs).

There’s clarity for every step:

• Authority: Sales decides in the productized lane
• Guardrail: productized vs. custom
• Consultation: Delivery consulted for custom
• Escalation: agency owner breaks ties when needed

The result is fewer arguments and fewer meetings—because you (and your executive team) aren’t re-solving the same conflict every week. Meetings can be shorter, too.

Example 2: Commitments that don’t match reality (and the missing operating system)

Here’s a different kind of swim lane problem: everyone blames a person… but the system doesn’t exist.

During an Agency Value Audit, an owner grumbled that the VP of Client Services was making commitments to clients that didn’t reflect the agencywide project calendar.

I confirmed that was, indeed, a problem, and asked: Who’s in charge of the agencywide calendar?

The answer: There isn’t one. Instead, scheduling lived informally in several people’s heads.

In that scenario, you don’t have a VP problem—you have a gap in your operating systems. You can’t enforce a swim lane if the system doesn’t exist.

For this agency, the swim lanes needed to start earlier:

1. Create the agencywide calendar.
2. Assign a primary owner.
3. Define how commitments get checked against it.
4. Define what can be promised without checking with the owner.
5. Define what must escalate.

Once you do that, client commitments become predictable—because the swim lane exists, not because someone tries (or argues) harder.

Example 3: Promoting up without backfilling down

A new client had recently promoted a key team member from VP of Accounts to CEO—but decided to wait to backfill the VP role.

Now, the “new CEO” was struggling to do two jobs:

1. CEO work (running and growing the agency)
2. Accounts work (managing the AMs and otherwise leading the Accounts function)

No one was happy. The owner kept getting pulled back in because the CEO was stretched and the Accounts lane didn’t have a clear decider. Client-facing decisions piled up, because the now-CEO had less time for the old account-related decisions.

I helped them accelerate backfilling the Accounts leadership role, so that the CEO could actually function like a CEO—and the owner stopped being the default backstop.

The underlying lesson: if you shift someone’s swim lanes, you must “reassign” the lanes they used to own. Otherwise, decisions default back to you.

How to implement leadership swim lanes in 60 minutes (and refine over 30 days)

This isn’t a months-long org design project. It’s a fast first pass, plus iterative refinement.

Step 1: List the top 10 recurring leadership debates

Start with what keeps coming up. For example: pricing disputes, staffing shifts, client escalations, priority conflicts, or “who owns this process?”

You don’t need to fix everything at once. Pick the top 10.

Step 2: For each, define lane + guardrails + escalation

For each topic, write:

• Decider: _____
• Guardrails: _____
• Escalation threshold: _____
• Consulted: _____
• Informed: _____

One page (per topic) is enough. And if you can’t decide, that’s an indicator itself; you may need an outside advisor, coach, or facilitator to help.

Step 3: Test it live in the next two leadership meetings

Every time a recurring topic comes up, ask:

• “Whose lane is this?”
• “What are the guardrails?”
• “Does this escalate—or can we decide here?”

This trains the team to use the system rather than defaulting to debate.

Step 4: Publish it where leaders can find it

Don’t bury it in a doc or folder that nobody opens. Instead, link it in the leadership meeting agenda, the leadership team hub, and onboarding for new leaders.

Make it part of the conversation, too. During your weekly one-on-one meetings, point back to the swim lanes when those topics come up. Over time, you’ll find your leaders start bringing up the swim lanes preemptively.

From the 3As delegation model, you’ll hear more “Aware” and less “Advise” (or “Action”). That means fewer meetings—and less work—for you. And your team feels more confident, because they can move ahead without waiting for you.

Step 5: Enforce it calmly

Your team doesn’t need you to be intense—but they need you to be consistent. Swim lanes fail when you override decisions silently, or leaders keep lobbying for exceptions.

Consistency makes the swim lanes real. And if you conclude a swim lane needs to evolve, make the change intentionally rather than reactively.

Common failure modes (and fixes)

Watch out for these common problems. If they pop up, I share suggestions to fix things.

“Everything becomes a joint decision”

Solution: Define when joint decisions are warranted, and make them rare.

If everything is a joint decision, you’re not collaborating—you’re recreating consensus paralysis.

“You keep overriding lane decisions”

Solution: Set an override rule. If you override, explain why and update the guardrails so it doesn’t happen again.

Otherwise, leaders learn that lanes are performative.

“Leaders avoid deciding”

Solution: Tighten guardrails, require recommendations with escalations, and coach decisionmaking in the gray areas.

Avoiding decisions is often fear masquerading as professionalism. Don’t let things fester; leadership vacuums hurt your agency.

“You defined lanes, but meetings didn’t shrink”

Solution: Enforce swim lanes in the meeting invite list, stop re-litigating decisions, and reinforce “final means final” norms.

If you keep revisiting past decisions (or don’t make decisions in the first place), you don’t actually have swim lanes—you have fuzzy suggestions, and your team will keep over-escalating to you.

What changes when leadership swim lanes are clear

When swim lanes are clear, you can enjoy these benefits:

• Meetings shrink because fewer things require group processing.
• Progress accelerates because decisions stick.
• Triangulation drops because leaders resolve issues peer-to-peer.
• You become more optional because escalation is intentional—not default.

That’s what “fewer meetings” is really about. It’s less about calendar hygiene, and more about decision clarity.

For more on this topic, see my articles on creating leadership alignment.

Does this problem sound familiar?

If this feels familiar, you may not have a people problem—you may have a design problem. The most expensive leadership issues in agencies often come from things nobody formally designed: decision rights, role boundaries, escalation paths, and what “good” looks like for each leader.

That’s what the Agency Value Audit (AVA) is built to uncover. AVA gives you a clear, data-informed snapshot of where your agency is strong, where it’s straining, and where leadership alignment (or misalignment) is hurting the business. Plus, you’ll get a custom roadmap for what to prioritize next. From there, owners can add ongoing support—either Executive Advisory (for owners + execs) or Agency Growth Coaching—to implement the changes and keep your leadership team aligned as complexity grows.

Want to fix this, so you can increase agency enterprise value and reduce owner dependence? Please get in touch and I’ll confirm if we’re a match to work together.

QUESTION: What’s an executive-level Swim Lane you should create next?