Why Operations Modernization Fails at Nordic Mid-Caps (And the Approach That Works)

There is a specific kind of company across the Nordics — Sweden especially, but the pattern holds across the region — that has run profitably for fifteen or twenty years on Excel files, email chains, and supplier PDFs. It is a good company. It makes a real product, it has long-tenured staff, and its numbers come in year after year.

It has also, almost certainly, been through at least one transformation program that under-delivered. And the leadership team has developed a quiet, patient skepticism toward the next one.

This post is about why those programs fail in this particular market, and what works instead. The argument is short: the programs did not fail on strategy. They failed on scope.

The Excel files are not the problem you think they are

Start with the most common misreading, because getting it wrong loses the room in the first meeting.

It is tempting — especially for someone arriving from outside, a consultancy or a new executive — to look at those Excel files and see negligence. A company that never got around to modernizing. That reading is wrong.

The Excel files are not negligence. They are the company's actual operating system. Someone designed each one. Someone has maintained it for years. The formulas, the cross-references, the sheet structure — they encode real operational reasoning, much of which was never written down anywhere else. A spreadsheet that has run a workflow for a decade is not a gap in the company's modernization. It is the company's modernization, the version the company could build with the tools it had.

Treat those files as something to understand fully before replacing, and you have the basis of a working relationship. Treat them as embarrassing legacy to be swept away, and you have told a competent, long-tenured employee that the work they carefully refined for ten years was wrong all along. That is not a technical message. It is a social one, and in this market it is fatal.

Two features of the Nordic mid-cap that kill big-bang programs

Two characteristics of these companies explain why transformation programs meet the resistance they do.

The first is decentralized authority. Decisions are made by the people closest to the work. This is a genuine strength — it is part of why the company is well-run — but it means workflows accumulate local variations, each one sensible for the person who runs it, none of them standardized. A program that arrives top-down, mandating one standard way, violates a norm the company actually values.

The second is centralized loyalty. Employee tenure is long. People know each other. Disrupting how a respected colleague has worked for fifteen years carries a real social cost, and that cost is felt across the whole team, not just by the individual. A program that replaces long-running practices quickly violates this norm too.

Most transformation programs manage to violate both at once — top-down and fast. And then they meet a very particular kind of resistance. Not loud opposition. Not a fight. Polite, patient, complete agreement that change is good and important, followed by nothing actually changing. The program is not defeated. It is outlasted.

Why it can be outlasted

There is a third feature underneath the other two, and it is the one that makes the resistance effective: these companies are not under existential pressure. They are profitable, often have been for decades, and can defer modernization more or less indefinitely while the numbers still come in.

This matters because it removes the forcing function. A company in crisis will push a difficult program through because the alternative is worse. A comfortable, profitable mid-cap has no such pressure. A program that creates friction does not have to be fought — it can simply be waited out, and the company will be entirely fine in the meantime.

So the modernization gap does not close. It also does not cause a crisis. It just widens, slowly, year over year — a little more key-person risk, a little more manual work, a little more fragility — none of it ever urgent enough to force the issue.

What works: one workflow at a time

The alternative to a failed transformation program is not a better-designed transformation program. It is a smaller unit of work.

Modernization at the scale that actually holds in this market happens one workflow at a time. You pick a single workflow — deliberately, usually one with a visible, costly, well-defined problem the leadership team already recognizes. You modernize it end to end: documented, given a system of record, measured, structured, and only then AI-augmented. You run the modernized version in production, in parallel with the old way, long enough for the operating team to genuinely trust it. Only then do you move to the next workflow.

This works for a precise reason, and it is the mirror image of why big-bang programs fail. A single modernized workflow is small enough not to trigger the organizational resistance — it does not ask everyone to change at once, and it does not threaten anyone's fifteen years of refined practice wholesale. And it is concrete enough that it cannot be outlasted — it is not an abstract argument that can be politely waited out, it is a workflow that visibly works better than it did, that the team uses every day, that the leadership team can point at.

It is quiet. It is deliberate. It is measurable. It does not make for an impressive launch announcement, and that is a feature, not a flaw.

Where to start

The honest first step is not to commission a program. It is to pick one workflow and look at it clearly — ideally with a structured audit, so the choice of where to start is based on evidence rather than instinct. The best first workflow is usually the one that combines a clearly visible cost, a well-defined scope, and a result the leadership team would immediately recognize as a win.

Modernize that one. Run it in production. Let it be the evidence. Then have the conversation about the next one — which, by then, will be a much easier conversation, because it will be about something real instead of something promised.