Signs Your Business Needs a Chief of Staff, Not Another EA

Most businesses don’t set out to hire a Chief of Staff. They set out to hire a better EA. The job spec grows, the seniority bar rises, the salary climbs, and somewhere in that process the role quietly stops being an EA role at all. It just hasn’t been renamed yet.

This mismatch is more common than it looks, and it rarely announces itself. It shows up later, in a hire who is technically excellent but structurally set up to fail, because the job they were given and the job they were briefed on were never quite the same thing.

Why the confusion happens

The EA and Chief of Staff titles sit close enough on paper that it’s easy to assume the difference is just seniority. It isn’t. A senior EA can be exceptional at calendar strategy, stakeholder logistics, and executive protection, and still be doing a fundamentally different job to a Chief of Staff, whose remit sits closer to the business’s operating rhythm than to any one executive’s diary.

The blur gets worse because job titles in this space are inconsistently applied across companies. One organisation’s “Senior EA” is doing Chief of Staff work. Another’s “Chief of Staff” is doing high-level EA work with a “bigger” title attached. Candidates learn to read past the title and interrogate the actual remit, and businesses hiring without that same scrutiny often end up scoping the wrong role.

What actually separates the two

The clearest distinction isn’t seniority, it’s direction of focus.

An EA’s core function is protecting and extending an executive’s time and effectiveness. The relationship is one-to-one, even when the EA also supports the wider team. Excellence looks like flawless execution: nothing dropped, nothing double-booked, nothing that reaches the executive before it’s been filtered and prepared.

A Chief of Staff’s core function is protecting and extending the business’s operating capacity. The relationship is one-to-many, spanning departments, projects, and often the leadership team as a whole. Excellence looks like alignment: initiatives that don’t stall between meetings, priorities that stay consistent across functions, and a leader who can trust that what they’ve decided is actually happening.

Both roles demand judgement, discretion, and the ability to work close to sensitive information. Where they diverge is scope. One is built around a person. The other is built around an organisation.

Five signs the role in front of you is a Chief of Staff role

The job spec keeps growing sideways, not just upward. If the brief has expanded from diary and inbox management into project tracking, cross-team coordination, and chasing outcomes across departments, seniority alone won’t fix that. That’s a different job.

You find yourself saying “someone who can just make sure things actually happen.” This is one of the most common phrases we hear from founders and leadership teams scoping a hire, and it’s almost always a Chief of Staff signal. EAs execute against a leader’s priorities. Chiefs of Staff are hired to ensure those priorities survive contact with the rest of the business.

The business has grown faster than its operating structure. Fast-growth businesses often reach a point where the founder or CEO is the only person holding the full picture together. A Chief of Staff exists to relieve exactly that bottleneck, something a traditional EA role isn’t scoped to do.

You’re hiring to fix a communication or accountability gap, not a scheduling one. If the underlying problem is that decisions aren’t translating into action across teams, that’s an operational leadership gap. No amount of diary efficiency solves it.

You keep comparing candidates against people who “basically ran the business” for their last employer. That instinct is usually correct, and it’s usually describing a Chief of Staff, even if the job ad still says EA.

Why getting this wrong is costly

Our own market data shows role scope expanding faster than job titles and salary frameworks have kept pace with, across the Business Support market generally. Chief of Staff hiring is where that gap tends to show up most sharply, because the risk runs in both directions. Under-scope the role and you hire a strong EA into a job that will frustrate them within six months. Over-title the role and you set expectations, and a salary, that don’t match what’s actually being asked, which creates its own retention risk once the mismatch becomes obvious.

A mis-scoped senior hire is expensive in a way a mis-scoped junior hire isn’t. The search takes longer, the salary is higher, and the disruption of getting it wrong lands closer to the top of the business.

Getting the brief right before the search starts

The businesses that get this right tend to do one thing consistently: they define the problem before they define the title. What’s actually not happening right now that needs to happen? Who is the bottleneck, and what would relieve it? Answering that first makes the EA-versus-Chief-of-Staff question answer itself.

If you’re currently scoping a senior Business Support or Chief of Staff hire and want a second opinion on where the role actually sits, get in touch with the Lily Shippen team. We spend a lot of time untangling exactly this distinction before a search ever begins.