Eighteen interviews to find out who owned it

Everyone followed the process. Nobody owned it.

An 8 to 10 week sprint. One senior analyst and two juniors. A €1B Nordic food company. Part two of three on where supply chain work stalls. Part one was about a decision rule nobody had written down. This one is about an owner nobody had named.

The client’s supply chain lacked clearly defined core processes and standardised documentation, and the result was inconsistent execution across sites. That is the page’s own summary and it is worth slowing down on, because the two halves are not the same complaint. Undefined is one problem. Undocumented is another. A company can have a process that everyone genuinely follows and still have nothing written down that says what it is.

What was actually missing is named precisely: process owners, clear KPIs, and detailed process maps. The consequence is named too, and it is a chain rather than a list. No owner means no accountability. No accountability means performance cannot be tracked. Nothing tracked means improvement has nothing to push against.

The costs landed downstream, in planning inefficiencies, more last-minute production changes, higher operating costs, and missed opportunities to improve service levels.

A process with no owner is not a process. It is a habit that several people share.

Writing down what you already do feels like the least urgent work in the building

Nobody schedules a quarter to document a process that is running. The plants are shipping, the orders are going out, and the process, whatever it is, is evidently working well enough that nothing has stopped. That is exactly the condition under which documentation never happens.

There is a second reason and it is less comfortable. Naming an owner is a political act. A process map with a name against each step tells people who is accountable when that step fails, and until the map exists that accountability is comfortably diffuse. Diffuse accountability is not something anyone defends out loud, but it is something a lot of people quietly prefer.

So the work sits in the gap between two things that are both true. It is not urgent, because nothing is broken this week. And it is not comfortable, because it ends with names against boxes.

This is a general shape, not a claim about this client. What is specific to them is on the page: the absence of owners, KPIs and maps, and what that absence cost.

Three figures, all stated as delivered, and a ten week sprint that could not have watched them happen

All three are stated flatly, as things that happened.

An eight to ten week sprint that maps a hierarchy, runs eighteen interviews, assigns owners and KPIs and rolls out Level-4 templates has produced an operating model. It has not produced a year of on-time in-full readings. Delivery reliability is observed over quarters of operating, not at the moment a template is handed over.

This is now the fourth page in this programme with the same pattern, after the maintenance page, the culture page and the assessment in the operational improvement coda. Two pages could be a slip. Four is the house default, and it is worth naming as such. The out-of-box failures page shows the estate can do it correctly: it reports a reduction potential identified, which is a different kind of statement and an honest one.

We carry the figures here in the page’s own words rather than quietly rewriting them, and then say what the sprint can and cannot have measured. That is the only honest way to use them, and a reader who checks will find the same thing.

The senior decided what a level is. The juniors found out what actually happens at level four.

One senior analyst and two juniors, which is the model and the reason the arithmetic works.

The senior’s judgement was the hierarchy itself: what counts as a core process, where a subprocess begins, and what level four has to contain to be useful. That decision governs everything downstream. Draw the levels wrong and eighteen interviews produce a beautifully consistent map of the wrong things.

The juniors’ work was volume and patience. Eighteen interviews across sites is roughly three working weeks once scheduling, travel and writing up are counted. Then every answer has to be reconciled against the hierarchy, which is slower than collecting it, because that is where two sites saying the same words turn out to mean different things.

The company knew its own supply chain far better than any outside team will learn in ten weeks. What it did not have was three uninterrupted weeks of somebody’s attention, and a person with no stake in whose name ends up against which box.

The owners and the KPIs are the product. The maps are the packaging.

It is tempting to read the Level-4 maps as the deliverable, because they are the thing you can hold. They are not. A map documents what happens. An owner with a KPI is what makes the next version of it better.

Which is why the third objective mattered more than it reads: create and roll out the maps and templates across all sites. A framework that lives at one site is a pilot. A framework that lives at all of them is a standard, and the difference is entirely in the rollout rather than in the design.

The client’s own description is the tidiest summary of what changed, and it names all three parts in order: clear owners, KPIs, and documentation standards. Owners first.

Three things, and the first is the number everybody will quote

Whether the 15%, the 25% and the 35% arrived. They are stated on the page as achieved. What the sprint delivered was the operating model that would produce them if it is used. Whether it was used, and for how long, is not something we observed and it is not something we can vouch for.

Whether the owners stayed owners. Names against boxes hold for as long as the people are in the roles and the KPI is still reported. Neither is guaranteed, and the most common failure of this kind of work is not that the map was wrong but that it quietly stopped being maintained a year later.

Whether level four was deep enough. Four levels was the judgement made at the start, and it was the right depth for the processes in scope. A different process, or a more automated one, might only reveal its real behaviour at level five. Depth is a decision, not a discovery, and it bounds what the map can show.

Where every figure comes from

From the published case study page. The €1B Nordic food company descriptor, the eight to ten week sprint, the 4-level process map and the eighteen interviews conducted. The three outcome figures, carried in the page’s own wording, 15% improved on-time in-full delivery, 25% fewer last-minute production plan changes and 35% faster issue resolution and handoffs, and questioned above rather than restated as observed results. The statement that the supply chain lacked clearly defined core processes and standardised documentation, producing inconsistent execution across sites. The three objectives set for the sprint. The client’s Director of Operations described the outcome as turning unclear processes into a structured operating model with clear owners, KPIs, and documentation standards.

From our internal engagement record. That the sprint was run by one senior analyst and two juniors.

Deliberately not used. The process hierarchy itself, and which sites diverged from it. That is the client’s operating detail, it is the most useful thing in the engagement to anyone competing with them, and it is not ours to publish. Every argument here is about the method that produced the map, which is the part that transfers.

Not claimed anywhere. That delivery reliability improved. We handed over an operating model. What happened next is theirs.