What A Director Of Operations Does, And When To Hire

What the role actually does

A director of operations owns how the business runs, as a design question. Not whether this week's projects shipped — that is an operations manager's remit — but whether the way projects are structured, resourced and reviewed is the right way, and changing it when it is not.

Concretely, they own capacity planning across the whole delivery function, the standards that define how work is done, hiring and structure within operations, the relationship between what sales commits to and what delivery can absorb, and the operating cadence — which meetings exist, what they decide, and what evidence they run on.

They also own the boundary conversations. What work the business will and will not take, when a delivery date is not achievable, when a process needs to change even though changing it costs a quarter. Those are the decisions that distinguish the role, and they are the ones that require real authority.

The step up from operations manager is authority rather than experience. An excellent operations manager executes a structure. A director of operations is accountable for whether the structure is right, which means they must be able to change it without asking.

One useful signal that this role is missing rather than merely absent: recurring problems that survive changes of personnel. If the same delivery failures happen regardless of who is running the projects, the structure is producing them, and nobody currently owns the structure.

When you genuinely should hire one

Hire when delivery has more than one team or more than one distinct service line, and somebody needs to make trade-offs across them. Allocating capacity between two teams is a decision that cannot be made inside either one, and if the founder is making it, that is the founder doing this job.

Hire when the operations problems you face are structural rather than executional. If your delivery issues are about how work is organized rather than whether people did it, an operations manager will manage the symptoms diligently and the structure will remain.

Hire when you are ready to genuinely delegate operational strategy, including the parts you would have done differently. That readiness is the actual gate, and it is the one founders most often misjudge about themselves.

Compensation is meaningfully above the operations manager band — general US market context for a director-level operations role tends to run somewhere from the low hundreds upward depending on scope and sector, and small-business figures vary widely. Take that loosely; the useful signal is that this is a leadership salary, and a business hiring at this level is committing to a structural change rather than adding capacity.

Where the hire fails

It fails when the authority does not match the title, which is the most common failure by a distance. A director hired to own operations, who then has every structural change reviewed by the founder, is doing an operations manager's job at a director's price and will read the situation accurately within a few months.

It fails when the business is too small for the role to have anything to direct. Directing implies people and structure. In a business of eight where the founder still sells and delivers, there is one team and one process, and the role collapses into doing the work — which is fine, except you have paid for something else.

It fails when they inherit no documented architecture. A director walking into a business where every project runs differently and nothing is written down will spend a year reconstructing how things work before they can improve anything. Many are good enough to do it, and it is an expensive first year, and the reconstruction lives in their head.

And it fails in the way this whole axis warns about: the hire becomes the architecture. A strong operations director in an undocumented business ends up personally holding the structure together, which relieves the founder and creates a second single point of failure at a higher salary.

It also fails when it is hired as a title upgrade to retain an existing operations manager. That is a reasonable impulse and a different decision — the person may be excellent at execution and have no appetite for structural authority, and giving them the title without the remit satisfies nobody.

What has to exist first

Enough delivery structure to be worth directing. More than one team, or more than one service line, or enough volume that capacity allocation is a genuine trade-off rather than an obvious answer.

A written definition of authority. Which decisions this person makes alone, which they make and tell you about, which need you first. This is the single most important artifact for this role and the one most likely to be skipped, because it requires the founder to decide in advance what they will accept being overruled on.

Some description of how work currently happens. Not a full manual — the stages, owners and exit conditions for your main engagement types. A director can improve a described process quickly; reconstructing an undescribed one takes a year and produces knowledge that lives in one person.

And a capacity number that exists before it is needed. Committed load across a rolling window, and a threshold for what happens when it is exceeded. Without it, the boundary conversations this role is hired for become arguments about impressions.

How to tell which you need

Ask what is going wrong. If the problem is that things are not getting done — dates slipping, work falling through, nobody chasing — you need an operations manager, and a director will be overqualified and probably bored. Hire the manager; it is the cheaper and more effective answer.

If the problem is that the way the work is organized is wrong — the same failures recur regardless of who is executing, capacity is allocated by whoever shouts, and every fix is temporary — that is structural, and it is what a director is for.

Then ask the authority question honestly, because it decides whether either hire works. If you are not ready to be overruled on how delivery is structured, name that, and hire the manager. There is nothing wrong with wanting to keep that decision; there is a great deal wrong with hiring someone senior and then keeping it anyway.

And if nothing about how you deliver is written down, the first thing this role would do is document it. That is worth doing before the hire rather than after, because it takes weeks as a project and a year as a side effect of onboarding.

And be realistic about the size of the surface. A director with one team of four to direct will spend most of their week doing the work alongside them, which is a fine outcome and a poor use of the salary.