The Operating Role at Three Company Sizes

The operating role changes as a company grows, but the core duty remains the same. At every stage, the operator is the person who makes the company work without the founder doing everything. The methods differ. The purpose does not.

Most confusion about what a chief operating officer does comes from comparing the title across companies of different sizes. The role at a startup is not a smaller version of the role at a mature company. It is a different role with a different constraint.

The anti-pattern is the title without the context

A familiar anti-pattern runs through companies hiring their first operator. They copy a job description from a larger company, hire someone with experience at that scale, and discover that the skills do not transfer.

The operator at a large company manages systems that already exist. They optimize processes, allocate resources, and coordinate across functions that are already staffed. The operator at a small company builds those systems from nothing. They document processes that have never been written down, create functions that do not yet exist, and decide what to postpone.

These are different jobs. The person who excels at one may struggle with the other. The company that hires for the wrong stage gets someone who is either overwhelmed by the blank page or bored by the maintenance work.

Do not copy, define

A calmer response to the hiring question begins with a clear definition of what the company needs at its current stage. Before any search begins, the founder needs to know which of three operating modes the company is in.

Mode one is build. The company has few documented processes, unclear decision rights, and functions that overlap or are missing entirely. The operator needed here is an architect. They design the systems that will make the company scalable.

Theory of constraints clarifies what architects should build first. Output is governed by a single limiting step, so the architect must identify that step before designing anything else. Building around the wrong constraint produces systems that look good and change nothing.

Mode two is stabilize. The company has processes but they are inconsistent, dependent on specific people, or producing errors that require constant intervention. The operator needed here is an engineer. They fix the systems that exist and make them reliable.

Mode three is optimize. The company has reliable processes and the operator is looking for incremental improvements, capacity planning, and strategic alignment. The operator needed here is a scientist. They run experiments on systems that already work.

Most companies believe they are in mode three when they are actually in mode one. That misclassification is expensive because it leads to hiring someone who runs experiments on systems that do not yet exist.

The systemic fix is stage-matched hiring

A serious position on what is a coo in business treats the role as stage-dependent rather than as a universal function. The job description, the interview process, and the success metrics all change with the mode.

In mode one, the success metric is documentation. How many functions have a written process, a named owner, and a done condition by month six. The interview should test for comfort with ambiguity and ability to create structure from chaos.

In mode two, the success metric is reliability. How often the process produces the expected outcome without intervention. The interview should test for diagnostic skill and systematic troubleshooting.

In mode three, the success metric is improvement. How much throughput moves with the same resources. The interview should test for experimental design and data interpretation.

A RACI grid is useful across all three modes, because most operating failures turn out to be ownership failures. Somebody knew the process yet nobody was named responsible for keeping it current. Somebody saw the problem yet nobody had the authority to fix it.

Why this is an intellectual discipline question

The discipline here is honest classification. Most founders want to believe their company is further along than it is. Hiring for mode three when the company is in mode one is not optimism. It is a category error that produces frustration on both sides.

That discipline protects the company from the churn that follows a mismatched hire. The operator who arrives into mode one work expecting mode three responsibilities will either leave or try to impose experiments on a system that has not been built yet.

The intellectual core is straightforward. Match the person to the stage, not to the title. A chief operating officer at one company may be doing work that at another company would be done by a founder, a consultant, or a department head. The title is less important than the match.

What this looks like in practice

Consider a founder-led company that had grown to twenty people and decided to hire a chief operating officer. The job description emphasized strategic planning, performance management, and process optimization. The person hired had done all three at a larger company.

Six months later, the founder was still resolving daily operational exceptions because the new operator was focused on strategic initiatives. The real need was mode one. Processes were undocumented, handoffs were unclear, and every customer issue routed back to the founder.

An honest stage assessment would have produced a different job description. The first six months would have been measured in documented processes, not strategic plans. The operator would have been hired for architecture, not for optimization.

Organizations that match the operator to the stage report a consistent effect. Their operators stay longer and their founders work less, because the person was hired for the work that actually needed doing.

Why this protects human capital

A mismatched operator hire forces the internal team to compensate for gaps that the new person was not hired to fill. The team continues to hold undocumented processes in memory while the operator works on initiatives that the company is not ready for. That dual burden exhausts everyone.

Stage-matched hiring is a form of care because it sets the operator up to succeed and the team up to be supported. The person hired for mode one work knows that documentation is the goal. The team knows that clarity is coming. Neither is asked to pretend the company is further along than it is.

The moral core is straightforward. People should not be hired into roles that require them to compensate for structural gaps with personal heroism. The company should know its stage and hire accordingly.

What compounds

Firms that build a stage-matching habit accumulate operational coherence that no single hire can deliver. They learn to see the progression from build to stabilize to optimize, which makes every subsequent operator transition smoother. The company that knows its stage will not mistake maintenance for architecture.

A balanced scorecard is useful here because it forces the company to state what operational excellence means at its current stage before claiming any hire delivered it. If the company is in mode one, the measure is documentation. If the company is in mode three, the measure is throughput.

A VRIO analysis adds another lens by asking whether the operational capability being hired for is valuable, rare, inimitable, and organized. Hiring an optimizer into a company whose processes are not organized is a mismatch that the framework exposes before the offer is made.

That clarity creates shared expectations between the founder and the operator. Both parties know what the first six months are for and how success will be judged. That alignment is a collaboration outcome that compounds.

Every company that knows its operating stage before hiring is a company that will find the right person. Every company that hires from a generic job description is a company that will wonder why the operator did not fix what was broken.

Frequently Asked Questions

What does a chief operating officer do at different company sizes?

At small companies, the operator builds systems from nothing. At mid-sized companies, the operator stabilizes systems that exist but are unreliable. At large companies, the operator optimizes systems that already work. The skills for each stage are different.

Why do chief operating officer hires fail at small companies?

Because the company hires for optimization when it needs architecture. The operator arrives expecting to improve processes that have never been documented. The founder expects strategic leadership and gets documentation work. Both are disappointed.

How do you know which operating mode your company is in?

Count the documented processes with named owners and done conditions. Most functions lacking documentation and named owners means mode one. Functions with documentation but inconsistent results means mode two. Reliable functions where the question is improvement means mode three. The measure must match the mode.

What should the first six months focus on?

In mode one, documentation. In mode two, reliability. In mode three, improvement. The measure should match the mode, because measuring strategic impact in mode one is like measuring speed in a car that has no engine.

Can one person operate across all three modes?

Some can, but most have a natural affinity for one. Architects who thrive in mode one often find mode three maintenance tedious. Optimizers who excel in mode three often struggle with the ambiguity of mode one. Honest assessment of affinity prevents mismatches.

When does outside help make sense?

When the company cannot classify its own stage because everyone inside is too close to the work. An outside operator brings the assessment framework and the distance needed to see whether the gap is build, stabilize, or optimize.