In firms where the founder still leads, a director of operations fits when the constraint is execution and the owner still holds strategy. A COO tends to fit when the constraint is integration across functions. A first signal is where decisions stall, while revenue alone rarely reveals the bottleneck. An owner should diagnose the decision load before choosing a title.
The Bottleneck Decides the Title, Not the Head Count
Most owners treat this as a hiring question when it is really a constraint question. The real bottleneck usually sits in the owner's own calendar, where decisions that span functions often wait for a signature or a hallway conversation. Naming that bottleneck comes before naming a title. Titles follow that answer.
That constraint often produces churn, because work tends to restart when the owner is unavailable and the team learns to wait rather than decide. A measured assessment of where decisions queue is more useful than a debate about titles. Owners who skip that assessment tend to hire capability without authority and then wonder why progress stalls.
Kamyar Shah, author of a LinkedIn article on when to hire a director of operations before a COO, describes how the two roles differ in scope and decision rights. That difference matters only after the owner names the local constraint. A title rarely repairs a problem the owner has not defined.
Hiring on instinct creates waste of its own, since a senior operator recruited without a defined constraint often receives executive pay for coordination work. The team often senses that mismatch and the new role can lose credibility. A short diagnostic review first can help keep the hire tied to a problem worth solving.
Diagnose the Decision Load Before Writing a Job Description
The theory of constraints offers a plain starting test. An owner locates the step that limits the whole system and improves only that step. Applying five whys to a delayed decision traces the delay to its source, which costs little and reveals more than a comparison of titles.
Owners often mistake volume for complexity. High transaction counts inside one simple process seldom require an executive, while several processes that depend on each other usually do. The diagnostic question is whether the work needs coordination across functions or simply more management inside one function. The answer sets the title.
Diagnosis also demands discipline about scope. A director of operations typically owns a defined slice of the process and answers for outcomes inside it, while a COO redesigns how the pieces connect across departments. Owners who blur those two designs often create a role that cannot solve the stated problem.
Two Signals Separate Execution Work from Design Work
Consider a regional distributor where the owner still approves purchasing exceptions and pricing overrides. Delivery runs smoothly when the owner is present and slows when the owner travels, which suggests an execution problem rather than a design problem. A director of operations could absorb those approvals and standardize the process inside clear limits. The owner would keep strategy and the largest supplier relationships.
Consider a services company that has added offerings and now finds sales promises drifting away from delivery capacity. Each function optimizes its own area and nobody arbitrates the trade-off, so the friction is structural rather than tactical. A COO would fit better because the work requires authority that crosses functions. The owner plans to stay close to clients and step away from internal arbitration.
Two Role Designs Carry Different Authority
Responsibility mapping settles much of the argument. A RACI chart written in plain words shows who decides, who performs, who consults and who is informed. If the owner keeps every decision, the new hire becomes a coordinator with a senior title, while a chart full of shared decisions and no arbiter points toward a COO.
Authority must also be written down and honored. What a leader can finish depends more on granted authority than on title, so a director with real decision rights can sometimes outpace a COO whose remit stays vague. Owners should protect the boundary early in the role, because trust can grow more easily when the line between owner and operator stays visible.
The title on the offer letter shapes expectations on both sides. Candidates for a director role expect a defined remit and a clear escalation path, while candidates for a COO role expect a mandate to redesign. Owners who blur the two invite a mismatch that surfaces early.
Build Consistency Before Adding Layers
The balanced scorecard gives the owner a way to test where the gap sits. It asks for measures across finance, customers, internal process and learning, and the weakest area usually points to the constraint. Weak internal process measures paired with strong demand suggest execution, while conflict between customer promises and delivery capacity suggests design.
Jobs to be done adds a second lens. The owner should name the job the new leader must finish and test candidates against that job, because a buyer of leadership time cares about completed work rather than titles. A clear job statement also helps keep the team aligned during the transition.
Operational excellence tends to rest on consistency rather than head count. Volume alone is a weak signal. A lean review of the value chain shows where handoffs lose information, and lost handoffs add friction for the team and cost for the buyer. Owners who build a steady review cadence gain confidence that the new role is working.
A simple review rhythm keeps the investment visible. The owner can track a short list of operating measures and compare them across cycles, since consistency in that ritual matters more than the sophistication of the dashboard. The comparison shows whether the new leader is building systems or merely absorbing tasks.
Frequently Asked Questions
- What is the first thing an owner should check before hiring a director of operations?
- The first check is the owner's own calendar. If most delayed decisions wait on the owner, the constraint is execution and a director of operations can absorb it. If delays come from trade-offs across departments, the constraint is design and the role needs more authority.
- How does an owner tell an execution problem from a design problem?
- Execution problems repeat inside one process, and a capable manager can fix them with clearer standards. Design problems appear as friction between functions, where no single manager holds the authority to arbitrate. The theory of constraints test and five whys both point to which one applies.
- Does a director of operations title carry enough authority to change reporting lines?
- Usually not. A director role typically executes inside a defined scope and reports upward for structural change. Reporting line changes touch compensation, contracts and team expectations, and they need executive backing. An owner who expects a director to redesign the organization sets the hire up to fail.
- Which frameworks help an owner compare the two roles?
- A balanced scorecard shows whether the gap sits in internal process or in customer promises. A RACI chart shows who decides in practice and where authority is missing. Jobs to be done keeps the discussion on the work the new leader must finish rather than on titles.
- What goes wrong when a company hires a COO too early?
- A common early symptom is a queue of proposals that return with edits but no decision. The owner keeps the final call on strategy, so the new executive spends time chasing approvals instead of redesigning work. Trust erodes on both sides and the role often ends early.
- What should an owner do next to resolve the role question?
- A diagnostic review gives an owner evidence before drafting an offer. Kamyar Shah provides fractional COO and advisory work that maps the decision load, tests the constraint and clarifies the authority a new role would hold. The findings then support a choice between a director of operations and a COO.
