The Two Chiefs Protocol

The Problem

You read The Ferguson Protocol. You get it — you need a second chief. But knowing you need one and actually installing one are different problems. The hire is strange. The role is ambiguous. Most founders who attempt it end up with an expensive EA or a glorified project manager, and six months later they're right back to routing every decision through their own skull.

This protocol is the implementation manual. How to find the right person. How to wire them into your operation. How to make them dangerous in 30 days.

Who This Is For

Founders or CEOs who have already hit the Complexity Wall described in The Ferguson Protocol and are ready to act. You've accepted you're the bottleneck. Now you need the step-by-step.

Also useful for operators who've been asked to step into a Chief of Staff role and want to understand what good looks like from the inside.

What You'll Need

• Time commitment: 2 hours to design the role profile. 30 days of daily debriefs (15-30 minutes each) during integration. This is not optional.
• Prerequisites: The Ferguson Protocol, read and understood. A genuine willingness to let someone see everything — your inbox, your calendar, your mistakes.
• Tools: An agreement tracker (spreadsheet, Notion, whatever you'll actually use). A daily sync slot for the first 30 days. A LinkedIn account for the search.

The Protocol

Phase 1: The Profile

Before you search, you need to know what tier of CoS you're hiring. Get this wrong and you'll build expectations neither of you can meet.

Tier 1: The Super-EA

This is a manager-level hire. Their product is your time. They own your calendar, your inbox triage, your travel. They make you efficient. They don't make decisions for you. If you're drowning in logistics but your judgment still works fine when you have space to think — start here.

The mantra: "My time is your product."

Tier 2: The Amplifier

This is a director-level hire. Their product is your voice. They draft your communications, run your meetings, translate your half-formed strategy into language the team can execute against. They don't just protect your time — they extend your reach. If the problem is that you can't be in enough rooms — start here.

The mantra: "My voice is your product."

Tier 3: The Proxy

This is a VP-level hire. Their product is your judgment. They attend meetings you skip and make the call you would have made. They're not relaying your instructions — they've internalized your algorithm. This is the Sarah Imbach tier. The one where Reid Hoffman could be absent and the room didn't notice.

The mantra: "My judgment is your product."

Most founders think they need Tier 3 immediately. They don't. Start at the tier that matches your actual pain, not your ambition.

Phase 2: The Search — The Fan Filter

Here's what makes this hire different from every other one you'll make: the best CoS candidates don't know they want the job.

They're not on job boards looking for "Chief of Staff" roles. They're operators, ex-founders, consultants, people who are weirdly good at pattern-matching and can't help themselves from fixing broken systems. They don't have a CoS career path. They have a compulsion.

The LinkedIn Post That Works

Post something like this — in your own words, not these exact ones:

"I am looking for a right hand. You will see everything I see. In exchange, I will teach you everything I know. It is a 2-year MBA in reality."

That framing does two things. It filters out people looking for a stable ops job. And it attracts people who are fans of your life — who want proximity to the decisions, the chaos, the learning.

Filter for enthusiasm over experience. A Tier 3 CoS with 15 years of corporate experience who treats this as "just a role" will never outperform a hungry operator who wants to absorb everything you know. You're looking for someone who treats your company like a masterclass they'd pay to attend.

Phase 3: The Integration — The Shadow Protocol

You've found your person. Now comes the 30 days that determine whether this works or becomes an expensive mistake.

The Access Ritual

Day one: cc them on everything. Every email thread. Every Slack channel. Every board update. Every messy internal debate. They attend every meeting you attend. For the first two weeks, they are silent observers.

This feels uncomfortable. It should. If you're holding back access — "they don't need to see this yet" — you've already undermined the hire. A CoS who sees a curated version of your company will build a curated version of your judgment. Useless.

The 30-Minute Debrief

Every day for 30 days, you sit with your CoS for a debrief. Not a status update. A debrief. They ask the questions. You explain the why.

"I saw you override the VP of Sales in that meeting. Why?"

"You read that email from the investor and didn't respond. What are you waiting for?"

"The product team presented two options. You picked Option B in about four seconds. What did you see?"

This is how they download your intuition into their own operating system. Every "why" question they ask is another line of code in the algorithm they're building to replicate your judgment. Skip these debriefs and you'll have a shadow who watched everything and understood nothing.

Phase 4: The Mochary Mandates

Once the 30-day shadow period ends, the CoS takes on three operating mandates. These come from Matt Mochary's playbook and they're non-negotiable.

Mandate 1: The Router

The CoS owns the Agreement Tracker. Every time someone in a meeting says "I will do X by Friday," the CoS writes it down. Then they chase it. Relentlessly. Not with passive Slack reminders — with direct, specific follow-ups.

Most teams suffer from commitment amnesia. Decisions evaporate between meetings. The Router mandate kills that. Your CoS becomes the institutional memory your company never had.

Mandate 2: The Sensor

The CoS becomes your emotional radar. They check in with your direct reports — not as surveillance, but as a safe harbor. "You seemed off in that meeting. What's going on?"

People will tell your CoS things they won't tell you. That's not a failure of your leadership. It's physics. The power dynamic between a CEO and a direct report makes certain conversations impossible. Your CoS sits outside that dynamic. They surface the raw data — the frustration, the fear, the confusion — so you can act on it before it becomes a resignation letter.

Mandate 3: The Referee

The CoS runs your weekly leadership meeting. They keep time. They police the agenda. They stop the VP who's been talking for nine minutes about something that belongs in a Slack thread.

This is the Ferguson move. You step off the training pitch. You stop refereeing and start observing. With the CoS running the mechanics of the meeting, you can watch body language, spot the tension between two leaders, catch the thing that wasn't said. You participate in the debate without managing it.

Day 1: The Shadowing Script

Print this. Hand it to your CoS on their first morning.

Be Invisible. Your job today is to disappear into the walls. Don't introduce yourself in meetings unless asked. Don't offer opinions. Don't try to add value. Just watch.

Be The Historian. You're not taking minutes. You're tracking decisions. Who made them. Who disagreed. Who stayed silent when they clearly had something to say. The decisions are the data. The minutes are noise.

Be The Mirror. At the end of today, we sit for 30 minutes. You tell me what you saw. Not what happened — what you noticed. The patterns. The gaps. The moments where the room shifted. That's your debrief. That's how we start.

What You'll Find

The first week is disorienting for both of you. You'll catch yourself filtering what the CoS can see. Stop. Every time you hold something back, you're training them on a partial dataset.

By week two, the debriefs get sharper. Your CoS stops asking "what happened" questions and starts asking "why did you" questions. That's the inflection point. That's when the algorithm starts forming.

By week four, something strange happens. Your CoS starts finishing your sentences in meetings. Not because they're guessing — because they've genuinely internalized how you think. The first time they make a decision in your absence and you would have made the same call, you'll feel a physical weight lift off your shoulders.

The less expected discovery: the Sensor mandate will surface problems you didn't know existed. Someone on your leadership team has been sitting on resentment for months. A process that you thought was working is held together by one person's overtime. Your CoS will bring you information that hurts. That's them doing their job.

Adaptations

You can't afford a full-time CoS yet. Start with a fractional arrangement — 2 days a week for the first 90 days. Run the Shadow Protocol on those days only. Give them the Router mandate first, because that's where the gap between "decided" and "done" is most visible. If the gap scares you, you'll find the budget for full-time.

Your candidate is internal. Better in some ways, worse in others. They already know the team dynamics, which accelerates the Shadow Protocol. But the authority shift is harder — yesterday they were a peer, today they speak for the CEO. You must announce the role publicly and explicitly. No soft transitions. No "they're just helping me out." That ambiguity will poison everything.

You're a solo founder with no leadership team. The Referee mandate doesn't apply yet. Focus on the Router and Sensor mandates, aimed at your key contractors or early hires. A CoS at this stage is really a co-builder who keeps you honest about what you said you'd do versus what you actually did.

You tried this before and it failed. Check the tier. Most failed CoS hires are a Tier 1 person in a Tier 3 seat, or vice versa. The second most common failure: the founder never did the debriefs. Without those 30 daily conversations, the CoS is just an expensive observer.

Where This Came From

Alex Ferguson's Harvard Business School case study showed what it looks like when a leader steps off the pitch and gains total visibility. Matt Mochary's CEO coaching methodology — specifically his refusal to work with founders who don't have a Chief of Staff — gave the role its operational teeth. And Mark Organ's First Round Review account of watching Sarah Imbach run Reid Hoffman's meetings at LinkedIn made the Proxy tier tangible. This protocol stitches those sources into a single hiring-to-integration playbook.

Related Protocols

• The Ferguson Protocol — The framework behind this protocol. Read it first to understand why the Two Chiefs model exists before you try to implement it.
• The Herb Brooks Protocol — How to build the team culture your CoS will be protecting. A CoS without a defined culture to defend is just another manager.
• The Decision Authority Matrix — Once the CoS is installed, you need to map which decisions belong to whom. This prevents the Authority Trap where the team doesn't know whether to listen to you or your CoS.