Operations doesn't runon the org chart.
It runs on the person who knows why that one shipment always gets flagged, which supplier actually picks up when the main one goes dark, and the workaround for the system that's never quite worked right. None of that's written down. It's just what whoever's been there long enough knows.
What walks out the door
The process doesn't slow down politely. It breaks exactly where nobody thought to explain it.
OakHive interviews them before they go. This is what comes back.
The shipment that always gets flagged
There's a reason, and it's a good one. It's also in one person's head, so the next flag becomes a ticket, then a call, then a delay.
From the handover guide, written to whoever takes the role next.
The supplier who picks up when the main one goes dark
The backup isn't in the vendor list, because it was never formally a vendor. It's a phone number and a favour, and it walks out with whoever earned it.
From the guided session that walks the role chapter by chapter.
The workaround for the system that never worked right
Everyone relies on it; nobody wrote it down. The first time it's needed after the handover, someone new is trying to keep things running while they rediscover it mid-crisis.
From the chat, answering after they have gone.
The gap that doesn't stay contained
Because operations touch everything else, one missing explanation shows up as a missed delivery, a client escalation, a fire nobody remembers how to put out.
From the manager's summary, ready before the last day.
Who to interview
Whoever's been doing the job long enough to know which shipment gets flagged and why. The supervisor with the backup supplier's number. The person who keeps the old system running.
Whoever takes over inherits the shortcuts, not the crisis.
Questions operations teams ask
That's the usual case. The handover guide and the guided session wait for them and are delivered the day they start. In the meantime the manager has the summary and checklist, and the team can already ask the chat.
It's designed not to. Answers in the chat come from what was said in the interview, and the manager's summary lists what wasn't covered. No AI is perfect, so the documents show you where the interview ran thin.
Setup for a departure is the person's name and role, so the first interview can happen inside the same notice period. OakHive takes on a small number of companies at a time.
Bring us the questionyour company keepsanswering twice.
Thirty minutes, no deck. You describe something your team has explained more than once, and we show you what OakHive does with it.
We are taking on a small number of companies at a time, so this is a conversation rather than a signup.