Operating Playbooks · Resource 15 of 15
The Missing Middle: Executive Operations
The role between the Executive Assistant and the Chief of Staff, defined and equipped with original operating-rhythm tools.
The Operations Library · No. 15
The Missing Middle
Executive Operations: the role between the Executive Assistant and the Chief of Staff
The Executive Assistant protects the principal's time. The Chief of Staff shapes the principal's direction. Between them sits the person who owns something neither one does: the operating rhythm of the whole company, all the way up to the boardroom.
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.
Executive Assistant
The Diary
"Is the principal's day handled?"
Leverages the principal's time. Owns the calendar, inbox triage, travel, correspondence, and the daily friction that would otherwise steal the leader's attention.
Executive Operations
The Rhythm
"Is the company's operating system running?"
Leverages the company's execution. Owns the operating cadence, the planning cycle, the follow-through system, the flow of information, and the board operating rhythm.
Chief of Staff
The Roadmap
"Are we working on the right things?"
Leverages the principal's judgment. Owns strategic framing, the hardest cross-functional bets, honest counsel, and the questions the CEO has not yet asked.
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.
Decisions evaporate. Things are agreed in the room on Tuesday and un-remembered by the following week. There is no single ledger of who committed to what, so follow-through depends on whoever happens to care.
The reviews are theater. The quarterly business review runs on time and looks polished, but no decision changes because of it. Preparation is a fire drill and the deck outlives its own conclusions.
The board book is a fire drill. Every board cycle, materials get assembled from scratch at the last minute, deadlines slip, and the pack lands late with numbers that do not always reconcile.
The Executive Assistant is drowning in strategy. The assistant is being pulled into agenda design and program follow-up that sits above the calendar, and the calendar is suffering for it.
The Chief of Staff is drowning in logistics. Your most strategic partner is spending Thursday chasing status updates and formatting slides instead of thinking about the hardest bets.
The leadership meeting has no spine. The weekly leadership meeting exists, but its agenda is improvised, its purpose drifts, and different functions are effectively planning to different calendars.
Offsites feel good and change nothing. The company invests in summits and offsites that generate energy and no durable operating change, because nothing carries the outcomes into the rhythm afterward.
Reading the result
One or two of these is normal noise in a growing company. Four or more, recurring across quarters, is a structural signal: the operating rhythm has become a job, and it is currently being done badly in the seams of other people's roles. That is the moment Executive Operations pays for itself, usually well before a company is large enough to justify a full Chief of Staff or a Chief Operating Officer.
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 Cadence Map
The full inventory of recurring leadership forums (weekly leadership meeting, monthly business review, quarterly planning, board and committee cycle, all-hands, skip-levels) with an explicit purpose, owner, input, and decision-type for each. The foundational act of Executive Operations is making the meeting architecture deliberate rather than inherited. Every forum should be able to answer: what decision does this room exist to make?
The Planning Spine
The connective tissue that links annual strategy to quarterly goals to the weekly meeting, so the top of the house and the front line plan to the same calendar. Owns the OKR or goal cycle as a process (not as a document), the timing of each planning window, and the translation of a yearly ambition into what a team commits to this quarter.
The Commitment Ledger
The single, trusted record of decisions made and commitments owed, carried forward between meetings so follow-through stops depending on memory or goodwill. This is the layer most companies are missing, and the one that most quickly earns the role its credibility. A decision that is not written down and re-surfaced did not really happen.
The Signal Flow
The reliable movement of information into and out of the leadership team: the standing metrics that feed each forum, the reporting packs assembled once and reused, and the communication that carries a decision from the leadership room to the people who must act on it. Owns the reusable source of truth so no reporting cycle starts from a blank page. At its apex, this layer becomes board reporting, covered in its own right below.
The Ritual Layer
The high-stakes, low-frequency moments that set tone and reset direction: leadership offsites, summits, strategy days, and the executive workshops where the rhythm is re-tuned. The top of the stack is the most visible and the least valuable if the four layers beneath it are weak. Done well, rituals inject outcomes back into the cadence rather than floating free of it.
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.
Phase 01
Set the Calendar
Lock board and committee dates a year out, aligned to the fiscal and planning cycle so the board rhythm and the company rhythm never fight for the same weeks.
Phase 02
Build the Book
Curate pre-reads from the exec team, enforce deadlines, make the pack tell one coherent story, and distribute through the portal (Nasdaq Boardvantage, Diligent, and similar) on time, every time.
Phase 03
Shape the Agenda
Work with the CEO and chair on what the board must actually decide, allocate time to match, balance oversight with strategy, and prime the audit, compensation, and governance committees.
Phase 04
Run the Room
Quorum, presenters prepped, timing held, executive sessions handled, and decisions captured in real time so nothing said in the room is lost by the time everyone leaves it.
Phase 05
Close the Loop
Minutes and resolutions recorded, action items tracked to completion between meetings, governance hygiene maintained, and shareholder or investor follow-through carried out.
Why the board makes the operator indispensable
Every other rhythm in the company tolerates a dropped ball. The board does not. A late book, a missed resolution, or an untracked action is not an inconvenience, it is a governance failure with the company's most senior audience. That is precisely why owning board operations flawlessly is the fastest way an Executive Operations leader earns board-level and investor trust, a standing that neither a calendar-focused assistant nor a strategy-focused Chief of Staff is structurally positioned to build. Run the boardroom rhythm well and you become the person the CEO cannot go into a board cycle without.
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 mindset
Systems over heroics. The goal is not to personally chase every commitment, but to build the mechanism that makes chasing unnecessary. If the rhythm only works when the operator is in the room, the rhythm is not yet built.
The unit of work
The cycle, not the task. Executive Operations thinks in loops that repeat (the week, the quarter, the board cadence) and asks how each loop can run tighter, cleaner, and with less friction next time around.
The relationship to the CEO
Close, but not the same closeness as the Chief of Staff. The operator earns trust by making the leader's commitments reliably happen, which is a different currency than being the leader's strategic sounding board.
The failure mode
Process for its own sake. The discipline curdles when cadence becomes ceremony. The craft of the role is knowing which meeting to kill, which report to retire, and which ritual has outlived its 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.
| Recurring artifact | Executive Assistant | Executive Operations | Chief of Staff |
|---|---|---|---|
| CEO calendar and inbox | Owns | Light | Light |
| Travel and correspondence | Owns | Light | Light |
| Weekly leadership meeting | Logistics | Owns agenda and follow-up | Shapes content |
| Quarterly business review | Light | Owns the process | Owns the narrative |
| OKR / planning cycle | Light | Owns the cadence | Owns the strategy |
| Decision and commitment tracking | Light | Owns | Supports |
| Board calendar and agenda | Scheduling | Owns the process | Shapes with CEO/chair |
| Board book and pre-reads | Light | Owns the mechanics | Owns the message |
| Minutes, resolutions, action tracking | Light | Owns | Light |
| Committee coordination (audit, comp, gov) | Light | Owns | Supports |
| Investor / shareholder touchpoints | Scheduling | Owns logistics | Owns narrative |
| Leadership offsite / summit | Logistics | Owns design and delivery | Owns objectives |
| The hardest cross-functional bet | Light | Supports execution | Owns |
| Strategic counsel to the CEO | Light | Light | Owns |
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.
Harvard Business Review
Dan Ciampa, "The Case for a Chief of Staff," Harvard Business Review, May to June 2020. Source of the three-levels-of-responsibility framing and the distinction that a chief of staff, unlike an assistant, does not manage the leader's day-to-day schedule. hbr.org
Note: the HBR article is behind a paywall. The levels framing here is drawn from a secondary summary and is consistent with the widely cited version of the article. Verify specifics against the original if quoting precisely.
Corporate governance
National Association of Corporate Directors (NACD), Full Board Operations and Setting the Board Agenda resources. Basis for treating board operations and agenda-setting as a distinct governance craft. nacdonline.org
Note: some NACD resources are member-gated. Confirm current links before citing publicly, and treat governance specifics as a matter for counsel.
Executive-support profession
The Founder and Force Multiplier body of work on the distinction between business administration (alignment) and business operations (execution), and the idea that force multipliers straddle both. founderandforcemultiplier.com
Practitioner analysis
"Chief of Staff vs Business Operations Manager (BizOps): What's the Real Difference?" framing the split as design (Chief of Staff builds the operating environment) versus optimization (BizOps refines execution inside functions). the-lbm.com
Operating rhythm in practice
Public examples of a documented operating rhythm, useful as concrete reference for the cadence layer, including the GitLab manager operating rhythm handbook. handbook.gitlab.com
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.