Why Your Ops Manager Is Drowning (And It’s Not a Hiring Problem)

You hired an operations lead 14 months ago. Good person. Strong background. They're working 55-hour weeks. Escalations still reach your desk twice a week. The natural conclusion — maybe you hired wrong — misses where the hours are actually going.

This is one of the most common diagnostic patterns Cendia encounters in services firms between 30 and 100 people. A founder who ran operations personally until $5-8M in revenue makes a smart hire: an Ops Director or VP of Operations with relevant experience. The hire ramps up, takes on coordination, starts managing workflows. Within 6-12 months, the hire is buried. The founder is still getting escalations. The reflex is to question the person. The structural reality is that the role is absorbing coordination cost that belongs in documented workflows.

Where the 55 hours actually go

When Cendia maps a drowning ops manager’s week, the breakdown is remarkably consistent across firms. The specific numbers vary, but the proportions hold.

A typical week for an Ops Director at a 50-70 person services firm:

Add that up. The coordination rows total 26-36 hours per week. The actual improvement work — redesigning workflows, building SOPs, implementing systems — gets 4-8 hours. The person hired to fix operations spends 60-70% of their time on coordination and 10-15% on the work they were hired to do.

The Cost-Per-Workflow framework makes this visible. When you decompose the Ops Director’s week into direct labor cost, coordination cost, and failure cost, the coordination layer dominates. The role has become a human routing system — the person through whom all operational questions and decisions flow because the workflows don’t have documented answers.

Why adding seniority doesn’t fix it

The instinct after 12 months of a drowning ops hire is to upgrade. Hire a more senior VP of Operations. Bring in a fractional COO at $10-15K/month. Find someone who can “handle more.”

A more senior operator will handle the same coordination load with better judgment. They’ll triage faster, escalate less, and make better decisions under time pressure. What they won’t do is reduce the coordination load itself. The number of undocumented handoffs stays the same. The number of process questions without written answers stays the same. The number of chase-downs required because no workflow has a defined SLA stays the same.

Cendia’s data across 20+ engagements: when firms replace a drowning Ops Director with a more senior hire (or a fractional COO), the new person typically reaches the same saturation point within 4-6 months. The throughput is slightly higher because the person is more experienced. The ceiling is the same because the structure hasn’t changed.

The Fractional vs. Internal vs. Consulting framework helps diagnose this correctly. A fractional COO is the right answer when the firm knows what needs to be done and needs execution bandwidth. An internal Ops Director is the right answer when the operational workload is durable and the firm is large enough to justify a full-time role (typically 75+ people). Neither role fixes the underlying problem when the problem is structural — when the workflows themselves lack documented decision rules, defined ownership, and handoff triggers.

The five structural gaps that create a drowning ops role

Cendia finds the same five gaps in nearly every services firm where the ops hire is saturated. Each gap pushes coordination cost onto the ops role that should live in the workflow itself.

Gap 1: No documented handoff triggers. When a project moves from sales to operations, what triggers the handoff? In most firms, the answer is “someone tells someone.” The ops manager becomes the relay point — the person who notices the contract was signed and manually kicks off the next phase. Documenting the trigger (“when contract status changes to Signed in the CRM, the onboarding checklist auto-generates and assigns to the designated PM”) removes the ops manager from the loop entirely.

Gap 2: No defined ownership at transition points. A project moves from phase to phase, but nobody is explicitly assigned to the next phase until the ops manager assigns them. The ops manager becomes a human dispatch system. Defining pre-assigned ownership based on project type, client tier, or capacity removes the dispatch function.

Gap 3: No written decision rules for common exceptions. “What do we do when the client misses the asset deadline by more than 5 business days?” Most firms answer this question through escalation — the PM asks the ops manager, the ops manager decides or asks the founder. Writing a decision rule (“if client assets are 5+ days late, PM sends the standard delay notice, timeline shifts automatically, and the scope review triggers at the 10-day mark”) turns a 20-minute escalation into a 2-minute execution.

Gap 4: No SLAs on internal work. The designer finishes the mockup. When does the developer start? In most services firms, the answer is “whenever they get to it.” The ops manager spends 4-6 hours per week chasing down internal deliverables that have no defined response time. Adding SLAs to the top 5 internal handoffs (“development begins within 24 hours of design sign-off; if the SLA breaks, the project lead is notified automatically”) eliminates most chase-down time.

Gap 5: Meetings used for information sharing instead of decision making. The ops manager runs or attends 12-15 meetings per week, most of which exist to share information that a 5-minute written update would handle. Converting information-sharing meetings to written artifacts and keeping only decision-making meetings typically recovers 6-10 hours per week for the ops role.

The math: what these five fixes produce

Cendia’s typical engagement timeline for an ops-role diagnostic:

Week 1-2: Measurement. Map the ops manager’s actual time against the three Cost-Per-Workflow components. Identify the top coordination cost drivers. Most firms are surprised by the numbers — coordination at 60-70% of total ops hours is the norm, but few have measured it explicitly.

Week 3-4: First structural fix. Document handoff triggers and decision rules for the top 3 coordination cost drivers. This typically recovers 8-12 hours per week for the ops role — hours that shift from coordination to actual operational improvement work.

Week 5-8: Sustained implementation. Add SLAs to the top 5 internal handoffs. Convert 3-4 information-sharing meetings to written artifacts. Define pre-assigned ownership at major transition points.

90-day result across Cendia engagements: the ops role’s coordination cost drops from 60-70% of their week to 35-40%. The time freed up — roughly 12-18 hours per week — goes to the operational improvement work the person was originally hired to do. Escalations to the founder drop by 60-75% within 90 days because the workflows now contain the decision rules that previously lived in the ops manager’s head.

The dollar impact: at a loaded cost of $85/hour for the ops role, recovering 15 hours per week represents $66,300 per year in redirected capacity. Add the founder’s time recovery (typically 5-8 hours per week at $200-300/hour effective rate), and the total 90-day impact is $120,000-$180,000 in recovered capacity.

The ops manager is working 55-hour weeks because the workflows route every question, exception, and transition through a human being. Document the decision rules and the hours come back.

What this isn’t

Scope notes:

• This isn’t a critique of the hire. The ops manager working 55-hour weeks is doing exactly what the structure requires. The problem is the structure, not the person. Replacing the person without changing the structure produces the same result with a different name on the door.
• This isn’t an argument against ops hires. Services firms between 30 and 100 people absolutely need operations leadership. The argument is that the hire’s time should go to building operational infrastructure, not to being operational infrastructure.
• This isn’t about one person’s calendar. The ops manager’s drowning is a symptom of organization-wide coordination cost. Fixing the ops role fixes the symptom; fixing the workflows fixes the cause. The Surface vs. Structure Lens applies here.

Where to start this week

Two actions, both completable before Friday:

1. Ask your ops lead to categorize last week’s hours. Three buckets: coordination (meetings, handoffs, chase-downs, answering process questions), direct improvement work (building SOPs, redesigning workflows, implementing tools), and everything else. The ratio tells you whether you have a capacity problem or a structure problem.

2. Pick the single most frequent escalation. The question or decision that reaches the ops manager (or you) most often. Write the decision rule for it. Post it where the team can find it. Measure whether escalation frequency drops over the next 2 weeks.

If coordination is consuming more than 50% of your ops lead’s week and you want a structured diagnostic — a measured breakdown of where the hours go, the five structural gaps, and a 30-day fix plan — that’s what a Cendia engagement produces. The 30/90/365 Sizing model applies: 30 days to first measurable change, 90 days to structural shift, 365 days to compounding returns.

This article is part of Cendia’s Hidden Costs series. Companion pieces cover Coordination Cost, the Handoff Cost Model, and the Margin Leak Map — the three diagnostic lenses that explain why growing services firms leak margin in predictable places.