I am not clairvoyant. I am something considerably more inconvenient — I have heard this story enough times to finish your sentences. And your next three paragraphs. And especially the part where you say, "But our situation is different."
Let me guess. (I’m not guessing.)
You’ve been running at 140% for eighteen months. Your calendar looks like a hostage negotiation that only Samuel L. Jackson can get you out of, and he’s unavailable for the foreseeable future (because he’s him, and you’re, well, you). Your board wants a strategy refresh, but doesn’t have a lock on the definition of “strategy” or “refresh,” though micromanaging seems to be something they’ve mastered so thoroughly that they should have their own podcast and a book deal. (Proposed Title: “I’ll See You in Hell Before I’ll Let This Go.”) And your EA—bless them—has started giving you the look every time you add a 7 a.m. Monday meeting to the schedule or, worse, schedule over the time you’ve set aside as “Focused Work.”
So, you do the thing every overwhelmed CEO eventually does. After talking about it to the CEO in the building next door, where he tells you all about the unicorn miracle worker who’s even better than Mary Poppins (except she takes equity), you think, “Huh. Maybe I need a Chief of Staff, too.” You Google “hiring a Chief of Staff,” read two Medium posts and one Harvard Business Review article from 2017, and decide you need one.
You’re right. You probably do.
But here’s where it goes sideways.
The Introduction That Costs You Everything
Two weeks from now, you’re going to stand in front of your leadership team and introduce your new Chief of Staff. And in the thirty seconds it takes you to do it, you’re going to make or break the role.
I know this because I’ve watched it happen countless times. I’ve been the person standing next to the CEO while they did it. And I can tell you with absolute certainty: most executives get it catastrophically wrong.
Here are the greatest hits:
“She’s going to be my right hand.” Your C-suite just heard: assistant. As in Andy Sachs in The Devil Wears Prada. (And yes, you’re Miranda Priestly in this scenario.)
“He’ll be helping me stay organized and on track.” Your VPs just heard: a calendar manager who could be replaced by Claude Cowork but somehow reports to the CEO.
“She’ll be a catch-all for whatever needs doing.” Everyone just heard: a dumping ground that rivals the Apex Regional Landfill in Nevada (the largest in the world).
Congratulations. You just told your entire leadership team they can juke past the person who's supposed to coordinate them like Saquon Barkley through a secondary. (Go Birds!) The role was dead on arrival. Your Chief of Staff just doesn’t know it yet.
This is not a communication problem. It’s a design problem. You haven’t figured out what this role actually is, so you introduced it as vibes instead of architecture. And architecture is the only thing that holds.
Your Chief of Staff Has Three Jobs. You’ve Given Them One.
Here’s the mental model almost every CEO gets wrong: they think the Chief of Staff is an extension of themselves. A proxy. A Garth to your Wayne.
The Chief of Staff is not your proxy. The Chief of Staff is an organizational function that sits at the intersection of three jobs:
1. Strategic integration. They connect the dots your C-suite can’t see because everyone’s running their own lane. Your VP of Product doesn’t know your VP of Sales just promised a client something that resembles the sun, the moon, and the stars. Your Chief of Staff does. Or should.
2. Operational orchestration. Not project management. Not “helping you stay organized.” Orchestration, in this context, means ensuring the organization's operating rhythm actually lands somewhere — not just convenes, discusses, and disperses like a flock of middle-management pigeons. It’s less of a Trello dashboard, more of an air traffic control board crossed with a Tetris game board.
3. Executive management. This is the one nobody talks about, and it’s the one that matters most. Your Chief of Staff manages you. Not your calendar. You. Your blind spots, your decision patterns, the wake you leave behind that you never see. But let’s agree that a Chief of Staff isn’t “Your Right Hand.” Because that means someone is overindexing for you instead of spending time reading rooms, meeting with people to better understand their perspectives, and building trust.
The best Chiefs of Staff are the people who will walk into your office and tell you the thing nobody else will. (Respectful, yes. But brutally honest? Also, yes.) Not because they're brave. Because it's Tuesday and someone has to.
If your job description has none of these three functions in it—and most don’t—you haven’t hired a Chief of Staff. You’ve hired an expensive project manager/event planner/administrative assistant/lunch procurer with an inflated title and a front-row seat to your dysfunction. But don’t worry, they’re not really paying attention to any of that. They’re too busy playing a very expensive and sophisticated Co-Pilot — you know, reading your emails and being tasked with tracking — to spend any time examining what went wrong to create the pervasive dysfunction you’ve appeared to invite into the company as a VIP.
The Problem Isn’t Them. It’s the Blueprint.
I started my career in the Clinton White House, supporting John Podesta as Chief of Staff to the President. I went on to help build the Consumer Financial Protection Bureau from employee number nineteen to a fully staffed federal agency. I served as Chief of Staff at the Gates Foundation, working with global health leaders and heads of state, navigating the most complex institutional environment imaginable. And over the past several years, I’ve interviewed more than 150 practicing Chiefs of Staff.
You know what every single one of them told me?
The role wasn’t broken because of them. It was broken before they walked in the door.
The CEO hadn’t thought through the authority structure. The executive team didn’t understand the reporting relationship. The job description was a hoarder’s garage of admin tasks, strategic projects, and “whatever else comes up.” Nobody had designed the operating environment in which the Chief of Staff would be working.
My co-author, Suzi Coul, has a name for this. She calls it the Leader Operating Environment—the conditions a leader creates, often unknowingly, that every person around them has to navigate. She’s spent a career in and around the upper echelons of UK politics and some of the most important private industry innovators of our time reading leadership patterns. She’s built a nine-dimensional diagnostic model that maps a leader’s operating signature with a precision that makes most executive coaches look like they’re reading tea leaves with a set of tarot cards on the side (just in case).
Here’s the uncomfortable truth her framework reveals: the environment you create as a leader is the environment your Chief of Staff inherits. If you’re chaotic, they’re firefighting. If you’re avoidant, they’re making decisions you should be making. If you’re a bottleneck, they’re either stuck behind you or going around you—and neither of those ends well.
The Chief of Staff isn’t failing. Your architecture is.
The $200K Mistake Nobody Talks About
The average Chief of Staff hire costs $150K to $200K in total compensation. That’s before you factor in the recruiter fees, the onboarding time, the six months of organizational drag while your leadership team figures out whether this person actually has authority or is just sitting in on meetings.
Most of these hires fail within eighteen months. Not because the person was wrong. Because the role was wrong.
And here’s the part that should keep you up at night: when the Chief of Staff fails, the CEO almost never learns the right lesson. They think, “We hired the wrong person,” and they go hire another one. Same broken architecture. Same result. Rinse, repeat, wonder why this keeps happening.
It's Groundhog Day, but instead of Bill Murray learning piano and punching Ned Ryerson, you're burning through $200K hires every eighteen months. Your board keeps politely asking why your operational cadence feels like a never-ending episode of Chicago Fire — all the drama, none of the resolution. And your C-suite is starting to assume you'll bring the same logistical finesse to this role that the Fyre Festival brought to theirs.
There are 35 million businesses in the United States and 6 million in the UK. Most have never had a Chief of Staff. Almost all of them need one. (Really. I think even tiny organizations are ripe for miscommunication. After all, if you need to keep a secret between three people, two of them need to be dead.) 1 Virtually no one knows how to get it right.
That’s the gap The Coul & Gold Briefing was built to close.
Every week, you’ll get one issue written by one of us. Mine — from inside the role, from having done it at the highest levels, studied it across 150+ organizations, and yes, been asked to pick up dry cleaning (after I served as a federal clerk on the District and Third Circuit courts). And Suzi’s—from the blueprints, from the diagnostic architecture that reveals why your leadership environment is producing the results it’s producing, whether you like those results or not.
Free subscribers get the sharp end: the provocative takes, the pattern recognition, the posts CEOs forward to their work wives at midnight. Paid subscribers get the operating system—the frameworks, diagnostic tools, and decision guides you can apply to your organization the same week you read them.
Because here’s the thing about architecture: once you can see it, you can’t unsee it. And once you can’t unsee it, you’ll want the tools to rebuild it.
Before Your Next Hire
If you’re reading this and you’ve already hired a Chief of Staff: take a breath. It’s probably not too late. But it is urgent. The longer a poorly designed role stays in place, the more organizational scar tissue builds up around it. Your Chief of Staff is quietly compensating for a structural failure, and eventually they’ll either leave or start performing to the broken expectation of task management and coffee orders, which is worse.
If you’re about to hire one: stop. Read the next three editions of this newsletter before you post that job description. What you learn will save you somewhere between $150K and your credibility with your own leadership team.
And if you’re a Chief of Staff reading this and nodding so hard your neck cramps—forward this to your CEO. Not with a passive-aggressive note. Just the link. If they get it, they’ll get it.
Next issue: Suzi Coul on The Nine Dimensions of a Leader’s Operating Signature—what to look for, why it matters, and what it reveals about the environment you’re creating without realizing it. Available to paid subscribers.
THE SIGNAL
Leadership isn’t a personality. It’s a pattern. And the Chief of Staff is the only person in your organization whose job it is to read it.
FOUNDING MEMBER OFFER
The first 100 paid subscribers lock in Founding Member pricing at $99/year for life. Every framework, every diagnostic tool, every roundtable, every edition—for less than the cost of one bad hire’s first week of wasted salary. After the first 100, the rate moves to $149/year.
I’m supposed to see you in two weeks. But I couldn’t help myself, so I’ll see you in two days.
— Rachael
The Coul & Gold Briefing
P.S. If you’re a Chief of Staff who just forwarded this to your CEO, good. If your CEO just forwarded this to you, even better. Either way, you’re both in the right room now. The question is whether you’re going to keep designing the role on instinct or start doing it on purpose.
1 It’s unclear who said this first. I was told it came from Ben Franklin, but others have suggested Mark Twain was the originator. Regardless, it’s accurate.






