Embedded delivery

The interim who became the dependency.

An interim becomes the dependency when they’re hired to hold a role rather than to make the business less reliant on whoever holds it. The fix is to write the exit, the future owners and the capability transfer into the brief from day one, and to check against them every month.

By Simon Wakeman, Principal Consultant & Fractional COO
· 4 minute read

An interim arrives so the business can stop depending on one person. Eighteen months later it has managed that, and now depends on the interim instead. In most cases the fix is a better brief rather than a better interim.

How does an interim end up as the new bottleneck?

One reasonable step at a time. It usually starts with a sensible decision. Everything runs through you, or through one overstretched leader, so you bring in an experienced interim to take the weight. They’re good. Within weeks, things are calmer.

Then the pattern sets in. The interim answers questions faster than anyone else, so people bring them more questions. They know the context, so they end up in every meeting that matters. They fix things themselves because it’s quicker than explaining. The contract gets extended once, then again.

A pattern Mallard sees often is a founder who is genuinely relieved to have stepped back, and genuinely alarmed when they realise what would happen if the interim left next month.

Why does this keep happening?

Because the brief was about the seat, not the system. Most interims are asked to keep a role running. Very few are asked to make the role less necessary. So they do what they were hired to do, and they do it well.

Three things make it worse.

  • Speed beats teaching. Every time a capable outsider solves a problem themselves, the team misses a chance to learn how. It’s faster this week and slower every week after.
  • Knowledge stays in one head. The interim learns how everything fits together, but rarely writes it down. When they go, the context goes with them.
  • Nobody is learning the job. People can’t take ownership of work they don’t feel competent to do. If no one in the team is being developed to take over, the handover has nowhere to land.

None of this is a criticism of interims. Plenty do outstanding work. But an interim who never plans their own exit isn’t solving your dependency problem. They’re becoming it.

What should you design in from day one?

Treat the exit as part of the job, not something you deal with when the contract runs out. Four things make the difference.

Write the exit before the job description. In one paragraph, describe what the business will be able to do without this person and by when. This becomes the real measure of success, more than how smoothly things run while they’re there.

Name the future owners. For each area the interim will cover, name the person in your team who will own it afterwards. If you can’t name anyone, that’s your real gap, and it may be a hiring or development question rather than an interim one.

Make the transfer visible. Ask the interim to work alongside those future owners, not instead of them. That means talking through decisions out loud, showing the reasoning and letting the future owner take the lead on more each month, with support. Write down how things work as you go, so the knowledge lives somewhere other than one person’s head.

Check it at a fixed rhythm. Review progress against the exit paragraph every month, with the interim and the future owners in the room. The question isn’t “how’s it going?” but “what can the team now do without you that it couldn’t a month ago?”

How do you know if it’s already happened?

You may already have swapped founder dependency for a dependency on someone outside the business. Some signs:

  • People say “check with them first” about decisions that should sit in the team.
  • Extensions keep happening without a new, specific goal attached.
  • When they’re on holiday, decisions wait for them to come back.
  • Nobody can explain how a key process works without asking them.
  • You feel uneasy at the thought of telling them the engagement is ending.

If two or three of those sound familiar, don’t panic and don’t end things abruptly. Reset the brief instead. Agree the exit paragraph now, name the owners and start the transfer.

What can you change this month?

  • Write the exit paragraph for any interim, contractor or outside adviser you have now – even if they’ve been there a while.
  • List what only they can do. Ask them to help. Every item on that list is a handover you need to plan.
  • Pick one area to transfer first. Choose something important but reversible, name the owner and agree a date by which the owner leads it, with the interim in support.
  • Put a monthly review in the diary with the interim and the future owners, using one question: what can the team do now that it couldn’t last month?
  • Decide the end date. Agree a fixed date rather than a rolling extension, with the outcomes that need to be true by then.

How Mallard approaches outside help

Mallard works on the principle that outside help should make itself unnecessary. We’re operators, not just advisers, and we build the exit in from the start.

An Improve sprint is time-boxed by design. For three months, a senior Mallard operator works inside your business alongside your team to fix your biggest bottleneck end to end, with success measures agreed up front. The capability is transferred as we go, so your team owns the result, and we stay on for 90 days afterwards to make sure the change holds.

If you’re weighing up what kind of help to bring in, our guide to choosing between a fractional COO, a consultant, an interim or a full-time COO sets out the options side by side. And for more on making change last after outside help has gone, see how to make operational change stick.

Some commonly asked questions from founders…

Why do interims so often become a dependency?

Because they’re usually hired to keep a role running, not to make the business less reliant on that role. A capable interim answers questions quickly, so people bring them more questions. Without a planned exit and named owners, every month makes them harder to remove.

Is it the interim’s fault if the business comes to depend on them?

Rarely. Most interims do exactly what they were asked to do, which is keep things running. The dependency comes from the brief. If nobody wrote down what the business should be able to do without them, nobody was working towards it.

How do I plan an interim’s exit from the start?

Write an exit paragraph before you sign anything: what the business will be able to do without them, who will own each part of their work and by when. Agree it with the interim, review it every month and treat a missed handover as seriously as a missed target.

What does capability transfer actually look like?

It looks like the future owner doing the work while the outside person is still there to help. In practice that means pairing on decisions, explaining the reasoning out loud, writing down how things work and handing over one area at a time. If the team only watches, nothing has transferred.

How long should an interim stay?

Long enough to steady the role and hand it over, and no longer. Fixed terms with clear outcomes work better than rolling extensions. If you find yourself extending without a new, specific goal, that’s usually a sign the dependency has already formed.

How is a Mallard Improve sprint different from hiring an interim?

An interim holds a seat. A Mallard Improve sprint fixes a specific bottleneck. For three months a senior Mallard operator works inside your business alongside your team, with success measures agreed up front, and the capability is transferred so your team owns the result. Mallard then stays on for 90 days to make sure the change holds.

Stop being a bottleneck in your own business

Book your free 30 minute
founder review call