The Missing Middle

The Argument

There is a seat almost every scaling company forgets to name

Ask most founders to describe the support around a CEO and you get two roles. The Executive Assistant, who guards the calendar and clears the noise. The Chief of Staff, who sits close to strategy and helps decide where the company points next. The org chart treats this as a clean binary: tactical below, strategic above.

It is not clean. Somewhere between the two, a third body of work quietly accumulates and belongs to no one. The quarterly business review that runs but never quite lands. The decisions made in the room that evaporate before Friday. The leadership meeting that fills an hour without moving anything. The board book that three people rebuild from scratch every cycle. The offsite that felt good and changed nothing. This is not calendar work, so the Executive Assistant cannot fully own it. It is not strategy, so it keeps slipping down the Chief of Staff's list. So it falls into the gap, and the company runs a little slower than it thinks it does.

That gap has a name. It is Executive Operations: the discipline of owning a company's operating rhythm, the recurring system of cadence, planning, follow-through, information flow, and governance that turns a leadership team's intentions into reliable motion. It is the missing middle. This guide makes the case for the role, then hands the person sitting in it a toolkit for doing it well, including the highest-stakes rhythm of all: board operations.

"Most people misunderstand the Chief of Staff role. They think it's calendars, comms, and coordination. In reality, the best Chiefs of Staff focus on creating clarity where ambiguity lives, alignment where silos form, and momentum where decisions stall." From the Benadom Insights collection. Executive Operations is where that momentum is manufactured.

The Framework · Benadom Original

The Three Altitudes

The cleanest way to separate these roles is not by seniority or title. It is by the object each one leverages. Everyone in the office of the CEO is a force multiplier, but they multiply different things. One multiplies the principal's hours. One multiplies the company's execution. One multiplies the principal's judgment. Read the three roles by their object of leverage and the overlap that confuses everyone dissolves.

Read left to right, the object of leverage climbs from time to systems to strategy. That is the altitude. The Executive Assistant works at the altitude of a day, the Chief of Staff at the altitude of a quarter or a year, and Executive Operations at the altitude of a week and a cycle: high enough to see the whole operating system, low enough to still be turning the crank on it. This is why the middle role is so easy to miss. It is the only one of the three defined by a tempo rather than a proximity to the principal.

A caution on the word "between." Executive Operations is not a junior Chief of Staff or a senior Executive Assistant. It is a distinct discipline with its own object of leverage. In a small company one person may hold all three altitudes at once. As the company grows, the middle is usually the first to need its own dedicated owner, because rhythm does not scale on goodwill.

The Evidence

What the credible sources actually say

The middle role is under-named in job titles but it is not invented. It appears, unlabeled, inside the best writing on the office of the CEO. Three threads converge on it.

The Chief of Staff literature already contains a ladder

In Harvard Business Review, Dan Ciampa's "The Case for a Chief of Staff" (May to June 2020) describes the role at three levels of responsibility. The first level is typically promoted from an executive-assistant background and manages the leader's time, prework, and follow-up. The higher levels move toward strategic initiatives, business development, and sitting on the executive committee. Ciampa is explicit that, unlike an assistant, a chief of staff works autonomously and does not manage the leader's day-to-day schedule. Read carefully, the article describes a spectrum, and the operating-rhythm work lives right at the hinge between his levels. Naming it as Executive Operations is not a departure from the HBR account; it is a clarification of it.

The force-multiplier field already splits administration from operations

Writing on the executive-support profession (the Founder and Force Multiplier body of work) draws a line between business administration, which is about alignment, keeping people, processes, and priorities arranged so leaders can lead, and business operations, which is about execution, the daily systems that actually produce and deliver. Executive Operations is the name for the person whose center of gravity has crossed from administration into operations while still working from inside the office of the CEO rather than out in a functional line.

The BizOps distinction points at the same gap from the other side

Practitioner writing comparing Chief of Staff to Business Operations frames it as design versus optimization: the Chief of Staff builds the operating environment, and Business Operations optimizes execution inside specific functions. Executive Operations sits precisely where that framing has a seam. It is not analytics for one function (that is BizOps), and it is not company architecture (that is the Chief of Staff). It is the operating rhythm of the leadership team itself, the connective cadence that both of those roles quietly assume is already running.

A note on sourcing. This guide leans on named, checkable writing rather than anonymous forum consensus, and it avoids precise headcount or salary statistics, because credible figures for a role this loosely titled do not exist yet. Where a claim is a judgment rather than a citation, it is written as one. Full sources are listed at the end.

The Diagnostic · Benadom Original

The Missing-Middle Signal Test

A role that no one has named is hard to hire for, because the pain shows up as symptoms rather than a job description. Here is how the empty seat announces itself. If several of these are true, the operating rhythm is orphaned, and the fix is a dedicated owner, not another tool or another all-hands.

The Toolkit · Benadom Original

The Operating Rhythm Stack

This is what the person in the seat actually owns. Not a list of tasks, but a stack of five layers, each one depending on the one beneath it. Weakness low in the stack cannot be fixed by polish higher up: a beautiful board deck built on an unreliable commitment ledger is just a well-designed fiction. Executive Operations builds and maintains the stack from the bottom.

The stack is also a maturity model. A company with layers one through three running reliably has a functioning operating rhythm. Most companies have a ritual layer and a cadence map with a hollow middle, which is exactly why their offsites feel good and change nothing.

The Apex · Benadom Original

The Board Operating System

If the operating rhythm has a summit, it is the board. Board operations is where Executive Operations stops being an internal convenience and becomes a governance function: the same discipline of cadence, pre-reads, follow-through, and information flow, but with a fiduciary body watching, a zero margin for error, and the company's most senior relationships on the line.

This is the piece most role descriptions miss entirely. An Executive Assistant can schedule a board meeting. A Chief of Staff can shape the strategic narrative the board hears. But someone has to own the machine: the annual board calendar, the board book, the agenda built with the CEO and chair, the portal, the minutes, the resolutions, the committee coordination, and the action items that must close before the next meeting. That machine is Executive Operations at its highest altitude. National Association of Corporate Directors (NACD) guidance treats full board operations and agenda-setting as a distinct governance craft, not an administrative afterthought, and it is exactly the craft this role carries inside the company.

The Board Cadence

Five phases that repeat every cycle. The operator owns the loop; the CEO and chair own the judgment inside it.

Governance detail (fiduciary duties, filing requirements, committee charters, and jurisdiction-specific rules) varies by company and country and often sits with the corporate secretary or general counsel. Treat this section as the operating cadence of board work, not legal advice, and coordinate the legal specifics with counsel.

In Practice

What good looks like in the seat

The tell of strong Executive Operations is counterintuitive: the better it is done, the less visible it becomes. A well-run operating rhythm feels like the company is simply organized, the way a healthy body feels like nothing in particular. The work shows up as absence, of dropped decisions, of duplicated reporting, of meetings searching for a purpose.

The Boundary Map · Benadom Original

Who owns what

The fastest way to end the turf confusion is to map the same recurring artifacts across all three roles. Owns means accountable for the outcome. Supports means contributes but does not carry it. Light means minimal or no involvement. The pattern is the point: the middle column is not empty, and it is not a copy of either neighbor. Notice how much of the board cluster lands squarely in the middle.

Notice the diagonal. The Executive Assistant owns the top rows, the Chief of Staff owns the bottom rows, and Executive Operations owns the dense middle band (including the entire board cluster) that both neighbors only support. Where a company has no dedicated middle, that band is what falls into the gap.

The Career Arc

A spectrum you can actually walk

One reason to name Executive Operations is that it turns a confusing leap into a walkable path. The old story, that a great Executive Assistant might somehow become a Chief of Staff, skips the discipline that connects them. The honest version is a progression through the object of leverage: from mastering the principal's time, to owning the company's rhythm, to influencing the company's direction.

This matches how the Chief of Staff literature already describes its own entry level as promoted from executive-assistant roots. Executive Operations makes the middle rung explicit and respectable in its own right. Not everyone in the seat wants to become a Chief of Staff, and they should not have to. Owning the operating rhythm of a scaling company, board included, is a career, not a waiting room. But for those who do want the climb, this is where the strategic muscle is actually built, because you cannot advise on where a company should go until you have felt, in your hands, exactly how it moves.

The Executive Assistant makes the leader's day possible. Executive Operations makes the company's week reliable and the boardroom flawless. The Chief of Staff makes the company's year wiser. Three altitudes, one office, and a middle that finally has a name.

Sources

Where this comes from

This guide blends original framing (The Three Altitudes, The Missing-Middle Signal Test, The Operating Rhythm Stack, The Board Cadence, and The Boundary Map are Benadom frameworks) with the following named, checkable sources. Figures were deliberately avoided where credible data for this loosely titled role does not yet exist.

Verification note: source titles, authors, and URLs above were drawn from live search at time of writing. Because titles and links can change, confirm any citation before republishing. The original Benadom frameworks in this guide are interpretive tools, not empirical claims.