You finally did it: you hired (or promoted) a Head of Delivery, Director of Client Services, VP of Delivery… maybe even a COO.
You expected relief. But instead, things feel harder.
- More questions.
- More “Can you weigh in?”
- More awkward overlaps.
- More friction between leaders who mean well… but don’t yet know how to work together.
As one agency owner told me: “People are hard.”
That’s true—and also incomplete. Because when leader integration goes sideways, it’s often not a people problem. It’s a design problem. Specifically: you hired a leader, but you didn’t fully integrate them into the agency’s operating system—roles, decision rights, handoffs, and communication norms.
This article is a practical 30–60–90 day plan to make leadership expansion go smoother—especially when you add your first Head of Delivery or an operations leader, especially if you’ve hired externally.
Why adding one leader makes everything feel harder
Leadership communication gets more complex overnight.
When you go from two leaders to three on your executive team, you don’t get a 50% increase in complexity. You get a lot more potential communication paths—more opportunities for misreads, overlaps, and “wait, who owns this?” moments.
That’s not a reason to avoid building a leadership team. But it is a reason to stop expecting things to “just work out” via goodwill.
Two predictable failure modes show up fast
Watch out for two common challenges.
Failure mode 1: leadership vacuum
If you don’t explicitly define who owns what, your leaders will do their best… and still collide. They’ll step in where they see a need. They’ll “help,” react, and fill gaps.
And in the process, they’ll create confusion, friction, and slowdowns—because nobody designed the boundaries.
Failure mode 2: shadow leadership
The old leader (or the owner) keeps doing the work “for now,” because the new leader is still ramping up, the stakes feel high, and you (and they) don’t want anything to slip.
This is understandable—but it’s also dangerous. If the new leader can’t truly lead, they’ll either disengage… or leave.
The integration plan: 30–60–90 days
Before we get into the timeline, there’s one decision you must make: first, define what “success” means.
Don’t define the role as a list of responsibilities. Instead, define it as outcomes.
Examples for a Head of Delivery / COO-type leader:
Here are examples of outcomes you might expect from a new Head of Delivery or similar.
- Delivery predictability improves (fewer surprises).
- Margins are protected (scope doesn’t silently leak).
- Client communication is consistent (no mixed messages).
- Teams aren’t chronically overloaded (less burnout, better retention).
Also define what success is not—“They magically fix delivery while we keep doing everything the same.”
Now, let’s look at the timeline to make this happen.
Days 0–30: stabilize and clarify
Your goal in the first month is not transformation. It’s stabilization plus clarity.
1) Run a “role handshake” meeting
This is a short, explicit alignment meeting between:
- Owner(s)
- Incumbent leader(s) affected by the change,
- New leader(s)
Agenda for the alignment meeting:
- What the new leader owns now
- What the incumbent leader owns now
- What the owner still owns
- What’s a gray area (case-by-case)
- How escalations work in the meantime
The output: a one-page living doc.
If you skip this, you’re not being “flexible”—you’re creating a leadership vacuum.
2) Build an ARCI (or RACI) matrix—but don’t over-build it
Owners often avoid this because it feels overwhelming: “There are too many scenarios.” That’s true… if you try to map everything at once.
Instead, start with the highest-friction recurring workflows—then add edge cases as they appear. A two-pronged approach works best: proactive + reactive.
Start with:
- Client escalation paths
- Forecasting and capacity planning
- Who communicates when an account is out of hours / out of scope
- Who runs which recurring meetings (and what “runs” means).
Example: The vague Slack handoff
An incumbent leader tries to be helpful and loop in the new leader: “Hey, I noticed this client used up all their hours. Do you want to communicate that to them?”
The intent is good. The execution is a mess.
Why? The new leader doesn’t know the agency’s default approach:
- Who typically communicates this?
- What do you say?
- When do you warn the client?
- Is this an Account Leader job? And what if there isn’t a formal account manager?
In the first 30 days, vague handoffs are friction magnets. Fix the pattern, not the person.
3) Install a “no vague handoffs” rule
New leaders don’t know your unwritten rules yet. So you must make the handoffs explicit.
Replace “looping you in” with:
- What decision is needed, and by when?
- Who owns the follow-up?
- What’s the default next step if no response?
A simple template:
- Context: “Client is at 98% of hours.”
- Owner: “AM owns client comms.”
- Ask: “Can you draft the message and send by 3pm?”
- Fallback: “If we don’t hear back, we pause non-critical work tomorrow.”
This isn’t bureaucracy. It’s integration.
4) Reduce triangulation before it becomes culture
Triangulation is when Leader A complains to you about Leader B instead of addressing it directly.
Some triangulation is unavoidable. Leaders sometimes need coaching.
But if you become the complaint department, you train your leaders that:
- Issues get solved by escalation, not collaboration.
- The owner is the referee.
- Peers don’t need to build conflict-resolution muscles.
So define what’s allowed vs not.
- Allowed: “I want advice on how to address this directly.”
- Not allowed: “I’m venting. You fix it.”
Here are some “redirect” scripts for you as the owner:
- “What did you say to them?”
- “When will you bring it to them?”
- “Do you need me in the room, or do you want coaching on how to say it?”
Done consistently, this reduces noise—and increases leadership maturity.
Days 31–60: transfer authority, not just tasks
Month two is where most integrations fail—because the new leader is “doing work,” but not building authority.
5) Stop inviting the wrong people to the wrong meetings
Meeting invites are a power signal. If the new leader owns the process, the incumbent leader should not be “optional” by default. Optional often becomes influential—especially if they have strong opinions and history.
If the incumbent needs input, get it asynchronously, in a pre-meeting, or via a short 1:1. But don’t invite them to the meeting where the new leader is trying to establish ownership.
Example: The “optional invite” meeting hijack
A new leader is building a process with internal stakeholders. They—or the owner—invite the prior leader as “optional” to be polite.
The prior leader joins and starts redirecting the plan—not maliciously, not as a power play, just… inertia.
The result is predictable:
- The new leader loses momentum.
- The team gets mixed signals.
- The owner ends up mediating.
- Everyone’s unhappy.
The fix is simple: “If you don’t own it, you don’t attend the working session.” And, “If you have concerns, share them in a pre-meeting or async feedback.”
This protects the new leader’s authority while still honoring useful input.
6) Define decision rights explicitly
Create three buckets:
- New leader decides
- Owner decides
- Joint decision (rare; be sure to define criteria)
Then pre-decide a few common triggers:
- Client is out of hours / out of scope
- Staffing changes on key accounts
- Discounts / write-offs
- Who is the client’s primary contact during transition
If you don’t define these, you’ll get hedging, meeting sprawl, and constant escalations to the owner.
7) Have the “incumbent fear” conversation early
When you hire a Head of Delivery or COO, an incumbent leader often feels threatened—even if they don’t say it out loud.
They may become overly critical, obstructionist, or vague (“this won’t work”). Sometimes they self-censor, then you have to drag concerns out of them later.
Have a direct, calm conversation:
- “Your role is changing, and I know that can feel threatening.”
- “This isn’t about replacing you—it’s about redistributing responsibility.”
- “I need you to support the transition, and I need your concerns to be specific.”
- “If you think something won’t work, tell us what would make it workable.”
Also be clear about consequences—not as a threat, but as a reality. Obstruction costs the agency—and often makes the new leader want to quit. Losing a promising new leader is often the most expensive outcome.
Days 61–90: harden the system and reduce owner load
By month three, you’ve seen enough real scenarios to turn “integration lessons” into durable systems.
8) Convert integration learnings into operating system docs
Update these assets based on what actually happened:
- Meeting cadence list: purpose, owner, required attendees, pre-work, follow-up enforcement.
- Client inventory visibility: account leader + secondary/supporters.
- ARCI/RACI matrix: version 1.0 → 1.1 (now grounded in reality).
Your current team can be more productive once you account for the hidden “tax” of confusion and rework. Your goal is to reduce that tax.
9) Engineer relationship capital between peer leaders
If your leaders are remote and haven’t met in person, don’t pretend Slack or Teams will build trust.
Plan an in-person meetup:
- Neutral location
- Explicit business goals (planning, decisions)
- Explicit relationship goal (“get to know each other so you can work better”)
- Light structure + small budget for shared activity
- You might join the beginning, to set the agenda—but then you leave them to work together
This doesn’t fix everything. But it increases positive intent—and positive intent is jet fuel for collaboration.
10) Run a 90-day integration debrief
You’re not reviewing the person—you’re reviewing the system.
Prompts:
- Where did ambiguity cost us time?
- What decisions should never escalate again?
- What meetings should stop existing?
- What must be true for the owner to be optional here?
Output:
- Revised decisionmaking authority
- Updated meeting ownership
- Next-quarter focus list
- Role refinements
Example: The forecasting prep confusion
In one agency, the weekly forecasting meeting became a friction point right away. The new leader did what a good operator does: they gathered numbers and prepared the doc.
But nobody explicitly defined the prep roles. That meant:
- The new leader over-checked some areas
- The incumbent leader weighed in inconsistently
- The owner was annoyed it wasn’t just working
The work got done—but it wore down the entire team because it didn’t feel smooth.
That’s the difference between “competent people” and a “competent system.” Even competent people will struggle to succeed in dysfunctional systems.
Troubleshooting: four integration problems you’ll likely encounter
To help you plan ahead, here are four common integration problems you might encounter—both the cause and the likely solution.
Problem: “The new leader is frustrated they can’t do their job”
- Likely cause: shadow leadership + unclear authority
- Fix: reset decision rights + meeting ownership
Problem: “The incumbent blocks everything”
- Likely cause: fear + identity loss + vague feedback habits
- Fix: direct conversation + require specificity (“tell me what would make this workable”)
Problem: “Everyone keeps coming to the owner”
- Likely cause: triangulation + unclear escalation paths
- Fix: redirect scripts + explicit escalation policy
Problem: “We’re drowning in meetings now”
- Likely cause: uncertainty masquerading as collaboration
- Fix: meeting operating system + fewer attendees by default
What this changes for agency scale and exit readiness
If your agency depends on you to resolve ambiguity, you’re not optional yet. And if you’re not optional, scale and exit-readiness stay fragile.
When you get it right, leadership integration reduces owner dependence by design:
- Decisions speed up
- Margin leaks decrease
- Leaders collaborate directly
- The agency becomes more resilient
If you’re seeing leaders pulled in different directions, it’s also worth asking whether the friction is a symptom of deeper misalignment—because misalignment creates drag that quietly stalls growth and valuation.
For more, see my prior articles: Why agency growth can plateau when leaders aren’t aligned and Why agencies struggle to scale without an independent #2.
Want outside clarity on what’s really causing the friction?
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 is built to uncover. AVA gives you a clear, data-informed snapshot of where the agency is strong, where it’s straining, and where leadership alignment—or misalignment—is quietly reducing profitability, momentum, and valuation.
Want to fix this, so you can increase 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 your next step to improve how you integrate new leaders at your agency?
