Insights

Train first, then run

Most operations help installs systems over a team that was never taught why they exist. Provenance trains the team first, so the systems still run after the consultant leaves.

---

Here is a scene I have watched more times than I can count. An owner brings in help to fix operations. The consultant maps the processes, writes a set of SOPs, builds a KPI dashboard, and sets up a Monday meeting. At handoff it looks excellent. The binder is thick, the dashboard is colourful, everyone nods. Six weeks later the dashboard has not been updated since the consultant walked out the door, the SOPs live in a shared folder nobody opens, and the Monday meeting has quietly slid back into a status update where people read their tasks aloud. The owner is once again the answer to every question in the building.

The work was not bad. The problem is that the system got installed over a team that was never taught why it exists.

A system is tested on the busy week, not the calm one

Any operating system looks fine the week you hand it over. The real test comes later, and it is specific. Three people are off. A large order lands. A supplier is late and a customer is loud. That is the week you find out whether the team actually runs the new system or falls back to whatever they understood before you arrived.

If they never understood the new way, they drop it. Not out of laziness. People protect what they understand and abandon what they do not. A scorecard nobody can read gets ignored the first hour things get hard. An SOP nobody helped write feels like a rule imposed from outside, and rules from outside are the first thing to go when the floor gets loud. A system nobody can explain is a system nobody will defend.

What I learned reading controls for a living

I spent years as a tax auditor, and most of that work was comparing what a set of records claimed against what had actually happened. I read a lot of controls that existed on paper and not in practice. The signature was there. The reconciliation was scheduled. On the page everything held. In the room, nobody could tell me why the control was there or what it was supposed to catch, so it had quietly stopped catching anything.

The gap was almost never the document. The document was usually fine. The gap was that the people expected to run the control did not understand it and did not believe in it. I see the exact same failure in operations. An owner does not have a documentation problem. He has an understanding problem wearing a documentation costume.

In Lean, the standard belongs to the people who do the work

This is the part most operations help gets backwards. In Lean, standard work is not a procedure written for a team by someone smarter in a corner office. It is a standard the people doing the work own, follow, and improve when they find a better way. The document is just where today's best-known method is recorded. When the method improves, the people who do the job change the standard. That is the whole engine of continuous improvement, and it only turns if the team understands the machine well enough to touch it.

Hand a team a standard they did not build and do not understand, and you have not installed continuous improvement. You have installed a photograph of it. It will not adapt, because the only people close enough to improve it were never taught how.

So we train first, then run

Provenance does it the other way around, on purpose. Before we install anything, we teach the team how good operations actually work. What a KPI is for and why the wrong one quietly steers the business into a wall. Why a bottleneck forms and why adding effort everywhere else makes it worse. What a weekly cadence is supposed to produce, and how to tell a real operating meeting from a status recital. This is the Operations and Management training, and it is bilingual, in French or English, because a team that has to translate the idea in their heads before they can use it never fully owns it.

Then the systems go in. The rhythm, the SOPs, the scorecard, the delegation, the controls. The difference is that now the people running them know what each one is for. When the busy week comes, they do not abandon the system. They lean on it, because they understand what it is doing for them. And when they find a better way, they improve the standard themselves, without me in the room, because improving it is exactly what we taught them to do.

Two halves of one method, not two services

People ask whether Provenance does training or fractional operations, as if they were two aisles in a store. They are one method. The fractional COO work installs and runs the operating system. The training gives the team the literacy to run it after the engagement ends. Buy one without the other and you get one of two disappointments. Training alone gives you a team that understands good operations and has no system to run. A fractional COO alone gives you a clean system that collapses the moment the retainer does.

Together they compound. The training makes the installed system make sense, and the running system gives the training something real to bite on. That is the honest reason the improvements last after I leave. I am not trying to make the business need me forever. A fractional COO who has done the job right works himself out of being irreplaceable, because he spent the engagement teaching the team to run the thing without him.

The measure that matters

Judge an operations engagement by one number. Not how good the dashboard looked at handoff. How much of it is still running a year after the consultant is gone. That number is set almost entirely by how well the team was taught before the systems went in, not by how polished the systems were on day one. Train first, then run. It is slower to start and it is the only version that survives the busy week.

If you want a system your team can still run after the engagement ends, that is the work Provenance does. You can read how the fractional operations and training halves fit together, get in touch, or book a 30-minute call at cal.com/provenance/30min and tell me which of your systems already died last busy week.