← Insights · Executive Roles
By Mike Dickerson | CEO and Managing Partner, The Tacitus Group, LLC
I spent twenty-plus years inside the Intelligence Community and the Department of Defense. I ran organizations with hundreds of highly cleared, highly motivated people. I managed task order portfolios worth hundreds of millions of dollars. I stood up offices from scratch when the mission demanded it, and I sat in seats labeled Chief of Staff, Staff Director, program manager, and contractor lead across multiple IC agencies.
The titles changed. The work didn't. In every one of those jobs, I was doing the same thing; making the organization function behind the scenes. Not setting strategy. Not picking the hill to take. Building the machine behind whatever leadership decided and keeping it running.
That isn't a Chief Operations Officer. That's a Chief Administrative Officer. Most CEOs don't know there's a difference, and the cost of not knowing is high.
When a growing company starts feeling operational pain, the instinct is almost always the same: "We need a COO. The CEO is buried, things are breaking, somebody has to take ownership." So they post a COO job or start reaching into their networks for referrals.
That's where it goes wrong. COO is the most overloaded title in business. Ask ten companies what their COO does and you'll get ten answers; some own revenue, some own delivery, some are a strategic thought partner to the CEO, and some are running everything in sight. When a title means everything, it means nothing. When you hire for a title that means nothing, you tend to end up with the wrong person solving the wrong problem.
A Chief Administrative Officer is not a junior COO. It's a more precise role.
The CAO owns the operating infrastructure of the organization; the internal machinery that lets the company function. HR and talent. Finance and budget execution. IT and enterprise systems. Facilities, compliance, contracts, and the business processes that tie it all together. The CAO doesn't set strategic direction. The CAO builds the engine that executes whatever direction leadership picks.
We had a name for this in the IC. Sometimes it was Executive Director. Sometimes Staff Director. Sometimes Chief of Staff. The badge changed by agency but the job was the same. You were the person who made the trains run on time. You made sure the laws and policies were followed, the budget was managed, the personnel decisions got made, and the processes existed in the first place. You kept the mission-focused people focused on the mission by taking everything else off their plate.
That's the CAO function. It's structurally different from the COO function.
The COO faces outward. The COO owns the company's core operations; the product, the service, the revenue engine. In a GovCon firm that means program execution, contract performance, and client delivery. The COO is usually the CEO's number two on the mission side of the house.
The CAO faces inward. The CAO owns the organizational backbone that supports the mission; HR, finance, IT, legal, compliance. The CAO makes sure the company can actually deliver what the CEO and COO have promised. Without the CAO's infrastructure, the COO has nothing to operate with.
When companies conflate the two, one of two things happens. Either external operations suffer because the leader is buried in internal administration, or internal infrastructure rots because the leader is consumed by client delivery. I've watched both. Neither ends well.
The distinction is sharpest in federal contracting, and that's also where I see the most confusion.
GovCon firms in the growth stage (call it ~$10M to $500M in revenue) are almost always program-heavy and infrastructure-light. They grew by winning work, which was the right priority at the time. The back office never caught up. HR is reactive. Finance is somebody's spreadsheet. IT is a pile of tools nobody integrated. Compliance is a prayer. The org chart is whatever happened to be standing when the music stopped.
These companies don't need a COO. They already have people who can execute programs; that's how they got here. What they need is somebody who can build the organizational infrastructure to support the growth they've already achieved and the growth they're planning for. That's the CAO seat, and in most of these firms it doesn't exist.
Whatever else you want to say about the Intelligence Community, operationally unsophisticated isn't accurate. Every major IC element separates mission leadership from enterprise leadership. The Director sets direction. The Deputy Director or a senior mission lead runs operations. The Executive Director or Agency Chief of Staff (the CAO, in corporate terms) runs the organization; budget, people, facilities, IT, security, business processes, all of it.
That structure exists because the IC learned, the hard way and over decades, that you cannot ask the same leader to run the mission and build the machine that supports the mission. The skill sets don't overlap. The time horizons don't overlap. Honestly, the temperaments don't overlap either.
When I was the Staff Director for Mission Integration at ODNI, I wasn't deciding intelligence priorities. I was making sure the Directorate had the budget, the people, the processes, and the structure to execute whatever priorities leadership set. I represented the Directorate across the IC, DoD, and oversight bodies, and I managed the front office staff and the Chiefs of Staff across MI's components. That was a full-time job. It would have been impossible to do well if I'd also been responsible for mission execution.
When a title means everything, it means nothing.
If you're a CEO or a PE partner trying to figure out whether you need a COO or a CAO, look at where the pain actually is.
If the pain is in program execution, client delivery, or revenue ops, you need a COO.
If the pain is in the organizational machinery (broken HR, a budget process held together with hope, IT systems that don't talk to each other, compliance running on duct tape, an org structure that no longer matches the operating model), you need a CAO. If you're honest with yourself, it's usually the second one.
The hire is not the charismatic operator who closes deals and runs programs. It's the quiet one who builds the systems, fixes the processes, manages the budgets, develops the people, and lifts the whole organization a level. The person whose work you don't notice until it stops getting done.
That person is a CAO. For most growth-stage firms in GovCon and national security, they're the hire that actually moves the company forward.
Mike Dickerson is the CEO and Managing Partner of The Tacitus Group, LLC, a fractional executive leadership firm serving growth-stage federal contractors and national security companies. He brings 20+ years of IC/DoD operational leadership experience, including senior roles at ODNI, the Joint Staff, NRO, and DIA, including 12 years managing IC task order portfolios at Booz Allen Hamilton.