An Interim COO Is Coverage, and Coverage Is a Knowledge Transfer Problem

How to Hire an Interim COO - Kamyar Shah, Fractional COO

An interim chief operating officer is a fixed-term executive brought in to stabilize operations and document what was never written down. Engagements run three to six months and close on a defined date. The work is neither advisory nor transformation. It is the recovery of operating knowledge before that knowledge leaves the building.

Coverage and Construction Are Different Products

Interim work stops an active loss, and fractional work builds capacity that compounds over years. The monthly rates are similar, which is why the two are so often confused, but the engagement shapes differ entirely. One is full-time attention across a short window, and the other is part-time attention across a long one. Only the second is designed to produce continuity.

Confusing the two produces predictable disappointment in both directions. A company that buys coverage and expects transformation will judge a successful engagement as thin. An organization that buys construction during an active crisis will find the pace intolerable. Name which product is being purchased before negotiating the rate.

The Trigger Is an Event, Not a Condition

Interim coverage answers a dated occurrence: a departure, a merger, a funding round that forces a hiring wave, or a diligence process that exposed undocumented operations. Each has a beginning, a peak, and an end. That shape is what makes a fixed term appropriate.

Conditions that recur without a triggering event are structural and will outlast any temporary engagement. A company that has replaced its operations leader three times in four years does not have a vacancy problem. Check whether the gap has a date attached, because that single test routes the decision correctly.

What Actually Leaves With a Departing Operations Executive

The organization chart shows one vacancy. The operating reality is that vendor relationships, approval judgment, escalation paths, and the reasons behind a dozen process exceptions leave in the same week. Teams keep working, but every decision that used to take an hour begins taking three days.

The loss is rarely visible in the first month, because momentum carries the existing work through. It appears in the second month as a queue of small unresolved questions that nobody feels authorized to close. Inventory what the departing role decided, not what it managed.

Tacit Knowledge Is the Asset at Risk

Nonaka drew the distinction between explicit knowledge, which is written and transferable, and tacit knowledge, which lives in practice and judgment. Operating leadership runs heavily on the tacit form. Tacit knowledge does not appear in any handover file, because nobody thinks to write down what feels obvious.

Converting it is the central task of an interim engagement, and conversion requires a person asking structured questions while the knowledge is still reachable. Exit interviews do not accomplish this, since they are scheduled after the departure decision and framed around sentiment. Schedule the conversion as work with a deliverable attached.

Map the Value Chain as Practiced

The first structural artifact is a model of how work actually moves, built from observation rather than from the documentation the company believes it follows. Orders enter somewhere, get approved by someone, and stall in a place nobody has named.

Practiced flow and documented flow diverge most at exactly the points that cause delay, which is what makes the comparison useful rather than academic. The divergence is also where undocumented judgment is concentrated. Map what happens, then set it beside what was supposed to happen.

Count the Single Points of Failure First

Any step that depends on one person’s memory is a failure waiting on a calendar. Counting those steps produces a ranked list far more useful than a general assessment of operational health. The exercise takes an afternoon and reframes the entire engagement around a finite set of dependencies.

The count is also the clearest number to report to a board, because it converts a vague concern into a finite list with accountable owners. Boards that receive the count instead of a narrative consistently report shorter meetings and faster approvals. Rank the list by how much revenue flows through each dependency.

The First Ten Days Are Diagnostic

The interim executive interviews department leads, reviews ninety days of operating and financial data, and maps the top recurring processes. The output is a two-page memo separating immediate risks, structural gaps, and quick wins.

Length signals effort while brevity signals judgment, and a company in an operational crisis has no capacity to read forty pages. The memo should be readable in one sitting by a board member with no operating context. Deliver it on day ten and let it set the sequence for everything after.

Days Eleven to Twenty Are Triage

Three to five small process changes are implemented in this window, chosen because they restore movement rather than because they are ambitious. Their function is partly evidential. A team that has been stuck learns within two weeks that change is possible and that the new executive can execute.

Momentum is a real input to everything that follows, because the harder structural work requires cooperation that has to be earned first. Selecting a difficult change here trades credibility for scope and usually loses both. Pick the changes that produce visible relief fastest.

Days Twenty-One to Thirty Produce the Roadmap

The thirty-day deliverable is a ninety-day stabilization framework naming the processes to document, the owner of each, the deadline, and the measure of completion. It also names who inherits each process after the engagement closes and what training that handoff requires.

A roadmap without named successors is a report rather than a plan. Every item should sit with an accountable person who will still be present next year, which is a constraint that changes what goes on the list. Teams that see their own names against the work describe the handover as shared rather than imposed. Assign the owners before finalizing the scope.

Approval Thresholds Are the Cheapest Structural Fix

A large share of operational delay traces to approval workflows that route every transaction to one signature regardless of size. A tiered threshold model, where routine amounts clear at the department level and only material ones escalate, restores cycle time within days and costs nothing to implement.

The change is small and the recovered velocity is not, which makes it an unusually good first move. Companies that publish tiered thresholds in the first month describe approval queues clearing before any headcount changes. Set the thresholds early, because the result funds credibility for the harder work.

Evaluate on Documentation Discipline, Not Experience Alone

Ask a candidate to show prior work product: a gap analysis, a stabilization plan, or a documented process from an earlier engagement. Documentation discipline is the single best predictor of what survives the engagement, and an executive who cannot produce artifacts manages people well while leaving nothing behind.

Documented processes are valuable, rare, difficult to imitate, and organizationally embedded, which is the definition of a durable asset under the VRIO test. An interim engagement that produces no such asset has bought only attendance. Score the artifacts before scoring the biography.

Exit Design Separates an Operator From a Placeholder

The strongest interim executives describe their exit in the first conversation: what transfers, to whom, and what condition signals completion. Vague answers about staying as long as needed indicate an engagement optimized for duration rather than outcome.

An interim role that becomes indefinite has quietly converted into an expensive permanent hire without the accountability of one. That drift is common and rarely noticed until a budget review. Require the exit criteria in writing before signing.

Contract Structure Should Match the Nature of the Work

Crisis coverage is continuous rather than milestone-shaped, so monthly billing fits it and milestone billing does not. A thirty-day termination clause protects both parties when the diagnosis changes what the engagement should cover.

Rates in the range of eight to fifteen thousand dollars per month reflect fixed-term senior attention rather than project delivery. Structure the agreement around coverage, and schedule a formal scope revisit at day thirty once the diagnostic memo exists.

Temporary Gap or Structural Gap

If the gap was created by a single dated event and a permanent hire is achievable within six months, use interim coverage as a bridge. When the organization has cycled through several operations leaders in a few years, the gap is structural and another temporary executive will reproduce the pattern.

Where the founder remains the decision routing layer, the constraint is the operating model rather than the vacancy, and no hire at any level will resolve it. Both an event and a structural condition are frequently present at once. Cover the event first and schedule the structural work behind it.

Coverage Buys Time, and Time Has to Be Spent

An interim engagement is best understood as purchased time, and time is only valuable if something is built during it. Companies that treat coverage as a holding action return to the same condition the week the engagement ends.

Companies that treat it as a documentation window emerge with an operating system they did not previously have. Those companies consistently report that the next transition costs a fraction of the first. The price of the two approaches is identical. Decide which one is being bought before the engagement starts.

What the Team Needs While the Search Runs

Transitions are experienced by staff as uncertainty about who decides and what happens if they are wrong. Written procedures, published approval thresholds, and named owners protect the team from that uncertainty faster than any reassurance from leadership. Clarity travels further than encouragement during a disruption.

The documentation an interim executive produces is a form of care as much as a form of control. It tells people what is expected of them while the organization is unsettled. Build it early, since the team is carrying the disruption while the search continues.

Every operating role eventually ends, planned or otherwise, and the only question is whether the knowledge stays. An organization that documents while it is calm never needs coverage. One that documents only under pressure will pay for the same knowledge twice, which is the argument for writing things down long before anyone gives notice.

Evaluation criteria, engagement structure, and the five scenarios that justify coverage are laid out in how to hire an interim COO.

Chief Operating Officer @COO