Digital transformation the Swiss way: precision first

Switzerland is regularly described as a slow adopter of digital technology. The description is accurate and the conclusion drawn from it is usually wrong.

Swiss organisations move more deliberately than their European peers. They also abandon fewer programmes, and the systems they put into production tend to stay in production. Those two facts are related.

The Swiss paradox: digital maturity without chaos

The paradox is that a market often called cautious produces some of the most reliable digital infrastructure in Europe — banking, insurance, healthcare, logistics.

The mechanism is not caution for its own sake. It is that Swiss buying processes ask uncomfortable questions early:

• Who is accountable when this fails?
• Where does the data live, and who can reach it?
• What does the exit look like?
• Is the supplier still here in five years?

These questions slow the start and remove most of the failure modes that stall transformation elsewhere. A programme that cannot answer them does not begin — which looks like slowness and functions as filtering.

The cost of this approach is real: genuinely useful things get delayed while the questions are worked through, and there is a version of it that becomes procrastination with a compliance justification. That version exists and is worth naming.

Where the advantage is currently under pressure

Three pressures are narrowing the margin that deliberateness buys.

Legacy systems reaching the end of the people who understand them. In many Swiss mid-market companies the core system is stable, documented informally, and maintained by a small number of people approaching retirement. That is a scheduling problem with a date on it, whether or not it has been scheduled.

Regulatory load increasing in parallel. revDSG since September 2023, the EU AI Act for anything reaching EU users, ongoing FINMA expectations. Each is manageable; together they consume capacity that would otherwise go to modernisation.

Engineering capacity that is scarce and expensive. The profiles needed for modernisation work — cloud architecture, data engineering, MLOps — are hard to hire in Switzerland, and slow to hire when possible.

Data sovereignty as an advantage, not a constraint

The most common mistake in Swiss transformation planning is to treat data protection purely as a cost.

For companies selling into Germany and Austria, the ability to answer residency and access questions with documentation rather than assurances shortens procurement measurably. It is a differentiator that competitors in less regulated markets cannot easily claim.

Getting the framing right matters:

• Residency and access are different questions. Storing data in a Swiss region does not answer who can reach it from where. Swiss and German procurement asks both.
• “Aligned” is the claim that stands up. Regulations are not certifiable. ISO 27001 and ISO 9001 are certified; SOC 2 Type II produces a report; revDSG and GDPR are aligned. A buyer’s compliance officer knows the difference, and overstating it costs more credibility than the claim was worth.
• An exit path is part of the answer. For FINMA-supervised clients it is a requirement, not a nicety.

Modernisation without stopping the business

The practical question is not whether to modernise but how, given that the system being replaced is the one running the company.

The approach that works is incremental and reversible — covered in full in seven principles of legacy modernisation without downtime. In summary:

• Cut by business capability, not technical layer. A capability can be replaced and rolled back on its own; a layer cannot.
• Route traffic gradually behind a facade, so each step is reversible in minutes rather than over a weekend.
• Measure against a baseline captured before anything moves. It cannot be reconstructed later.
• Retire what nobody uses. Most estates carry functionality that has had no users for years, and finding it is the cheapest win available.

What good looks like, concretely

An organisation doing this well has a small set of observable properties:

• A named owner for each core system, and that person is not the only one who understands it
• A documented dependency map that someone updated this year
• Modernisation running as a series of quarterly deliverables rather than a programme with a distant end date
• Compliance artefacts produced as a by-product of delivery, not assembled before an audit
• A sourcing model where internal people hold business knowledge and external capacity brings repeat experience — and leaves a team behind

None of that is dramatic. It is also what distinguishes companies where transformation compounds from companies that restart it every three years.

Choosing a partner: what to insist on

Since most Swiss mid-market modernisation involves outside capacity, the selection criteria matter as much as the plan:

• A Swiss contracting party, so accountability sits in the same jurisdiction as the obligation
• Named people, not an anonymous pool — continuity is the thing that actually determines quality here
• Evidence from comparable work. European references are more informative than larger ones from elsewhere; our Palisis and Zeus Bioscience engagements are the ones we would put forward
• Cautious timelines. A supplier who says twelve to fourteen weeks where others say twelve is telling you something useful about how they estimate

The point

The Swiss approach is slower at the start and cheaper over the life of a system, because it removes the failure modes before they are expensive. Its weakness is not caution — it is caution applied indefinitely, where the questions never stop being asked and nothing ships.

The organisations that do best keep the rigour and put a date on it.

Related: application modernization and dedicated engineering teams.

If you have a core system that works and nobody wants to touch, book a call — no obligation, and a concrete read on where the first step should be.