Five people walk into a room.

The athlete. The brain. The basket case. The princess. The criminal.

Different worlds. Different skills. Different reasons for being there. But Principal Vernon decided they all belonged in the same Saturday detention — and by the end, at least one of them had figured out that the categories were the problem all along.

The Chief of Staff pipeline works exactly like this, except nobody figures it out by three o'clock. Instead, the wrong people get put in the same room, handed the same title, and everyone acts confused when the results are different.

It always starts the same way.

Someone is exceptional at their job. They're organized, perceptive, deeply loyal to their executive, and better at anticipating needs than anyone in the building. Their boss notices. Their colleagues notice. Eventually, someone says, “You should be a Chief of Staff.”

And because the Chief of Staff role has never had a clear definition, thanks in large part to a 2017 article that convinced an entire generation of startup founders the role is basically "EA plus COO minus direct reports" and the internet ran with it, nobody in that room has any idea whether that's true. Not the person being encouraged. Not the executive doing the encouraging. Not the HR leader nodding along. Nobody.

So they do it anyway. And sometimes it works. And a lot of the time it doesn't. And when it doesn't, everyone loses—the person who took the role, the executive who hired them, the organization that needed something the role was never set up to deliver. And then they all quietly agree that the role is hard to hire for, the talent pool is thin, and maybe they should try again with someone else.

The role didn't fail. The pipeline failed. There's a difference, and it matters enormously. Nobody puts that on the exit interview.

What the Pipeline Actually Selects For

The EA-to-CoS pipeline selects for one thing above all others: proximity to power.

EAs are exceptional at proximity. It's core to the job. They understand their executive's rhythms, preferences, and blind spots at a level of granularity that takes years to develop. That is genuinely valuable. It is also not the same as the ability to integrate a C-suite, navigate organizational politics without a formal mandate, or walk into a room full of people who outrank you and change the direction of a conversation through sheer credibility and judgment.

Cutting open bodies doesn't make someone a surgeon. Sitting next to power doesn't make someone a Chief of Staff.

Proximity to power is not the same as the ability to wield it. A great EA and a great Chief of Staff both sit close to the throne. So does the person who polishes it.

Those are three different jobs. We keep pretending there are only two.

Who the Pipeline is Ignoring

When your pipeline starts and ends with "excellent at supporting an executive," you systematically exclude the people who are most naturally wired for this role.

Communications professionals who've spent careers translating between power and people, managing narrative across an organization, and understanding that what gets said is never the whole story. They know how to hold complexity, read a room, and move an agenda forward without anyone realizing they just did it. That is Chief of Staff work. Nobody told them.

Policy and government professionals who've operated inside bureaucracies so large and so politically fraught that "managing up without authority" isn't a concept—it's a Thursday. They've negotiated competing interests, protected a principal's agenda while keeping seventeen stakeholders from revolt, and understood that the unofficial org chart is the one that actually matters. Also, not in the pipeline.

Lawyers. Strategists. People who've led volunteer organizations where the only currency is trust and the only authority is earned. People who've managed through ambiguity so long they've stopped noticing it. All of them—somewhere else entirely, often already doing the work without the title—while the conveyor belt keeps moving and we wonder why we can't find the right candidates.

They're out there. We just built the pipeline in the wrong direction.

What Actually Predicts Success

I've conducted over 150 interviews with women Chiefs of Staff. I've held the role four times — at the Gates Foundation, at the CFPB, at the USDA, and in a fractional capacity. Before any of that, I supported the Chief of Staff to the President of the United States. I watched the original model operate at the highest level of organizational power in the world—not from a distance, but from inside the room. And the single most consistent predictor of success has nothing to do with which jobs came before it. It's a particular mindset—a way of seeing organizations, people, and power—that either exists in someone's wiring or doesn't. As Melanie Jones says, “Being a great CoS isn’t just a skillset, it’s a mindset.”

You cannot certify for it. You cannot pipeline for it. You can, however, stop pretending the shrug is an acceptable answer.

The problem isn't that people lack ambition. The problem is that the question has never had an honest answer, because the people best positioned to answer it have always had a financial interest in saying yes. So almost nobody says no. And the people who needed a no get handed a badge instead. And then they take a job they weren't built for. And everyone fails. And then we all agree the role is hard to hire for.

It's not hard to hire for. It's just never had an honest diagnostic.

Until now.

What we Built and Why It's Different

Suzi Coul and I spent a long time on a deceptively simple question: what actually determines whether someone will succeed in this role? Not what looks good on a résumé. Not what impresses in an interview. What actually determines it.

The answer is twelve qualities—and they don't sort neatly by job title or years of experience. They sort by wiring.

The first layer is the hardest to talk about honestly, which is exactly why nobody does. These are the foundational instincts—ego management, self-regulation, the ability to operate without a formal mandate, and discretion as active judgment. When these are absent, nothing else compensates for them. Not intelligence. Not work ethic. Not charm. The assessment surfaces them through situational scenarios built around the actual moments that reveal how someone is wired, because self-report alone will never get you there. People are spectacularly unreliable narrators of their own ego.

The second layer covers the practiced skills — political navigation, relational authority, communication under pressure, organizational instinct. These matter enormously, and unlike the first layer, they're developable. The reason this distinction matters is that most people who don't get an honest answer to "am I ready?" don't know which category their gaps fall into. They don't know if they're facing something fundamental or something fixable. That uncertainty is expensive, and it's entirely unnecessary.

The third layer covers contextual judgment—how well someone reads a specific environment, calibrates to a specific leader, holds organizational complexity without losing the thread. This is the layer that explains why someone can succeed brilliantly in one organization and struggle in another, and why, "She was great at her last company," is one of the least predictive things anyone says in a hiring conversation.

The assessment takes 75–90 minutes, completed on your own schedule within a 72-hour window. Every report is practitioner-reviewed before delivery—not automated, not algorithm-generated. Your report arrives within three to five business days.

What Your Results Tell You

Your results land in one of three places.

You're ready. The wiring is there. The report tells you what's strong and where to keep developing. Several placement firms have committed to referring to our vetted candidate list when conducting Chief of Staff searches, and we are in conversations with others. To be clear: neither they nor we can guarantee you a job. What we can guarantee is that when they're searching, this list is where they will look. We’re not building a dead end. We’re building a door. Whether it opens depends on the search, but you'll be on the right side of it.

You have gaps, but close-able ones. This is not a consolation prize, and we're not going to dress it up as one. Knowing specifically where your gaps are, named clearly in a practitioner-reviewed report, is the most actionable information anyone in a Chief of Staff job search can have. We've compiled a list of coaches we'd send our own clients to—people we've personally vetted and know, not people paying us referral fees—who work on exactly these dimensions. You leave with a roadmap. Bring a pen.

This isn't your moment. That is a legitimate and valuable result, and we mean that without a shred of condescension. It is dramatically cheaper—financially, professionally, emotionally—to hear it now than six months into a role that is quietly dismantling your confidence, your manager's patience, and your reputation simultaneously, with no warning and no parachute. The report tells you why. It also tells you what to pursue instead. Because the answer to "not Chief of Staff" is not "nothing." It's something else entirely, and you deserve to know what it is.

The Pilot

The pilot price is $599 for the first ten candidates. After that, the standard price is $799. During the pilot phase, if you hit a technical issue and need to retake it, that's on us; no questions, no additional charge.

The entry assessment fee is credited in full against the full assessment if you choose to go deeper within 90 days. The full assessment adds a structured 60-minute interview, public profile analysis, and a complete outcome verdict with leader archetype fit recommendation.

We built this because someone needs to say no when no is the right answer. And yes when yes is. And because the question—could I be a Chief of Staff?—has always deserved a better answer than a shrug.

Here it is. As a subscriber, you get exclusive access to it before we launch on Friday. Thanks for being here with us.