Where digital transformation should start in a service business

“Digital transformation” is too large to be a useful starting instruction. It encourages organisations to inventory every system, interview every department and buy a platform broad enough to promise everything. Months later, the business has produced a map of its complexity without improving an outcome.

A service business should begin with one vertical slice: a meaningful customer outcome and all the work required to produce it. That boundary is small enough to change and broad enough to expose the real dependencies.

Why transformation programmes stall

They organise around departments

Customers do not experience departments. They experience a promise crossing marketing, sales, administration, delivery and finance. Improving one team’s task can simply move the delay to the next team.

They treat software as the strategy

A CRM, practice system or automation platform can support a good operating model. It cannot decide who owns a hand-off, what information is genuinely needed or which exception deserves human judgement.

They make the scope too safe or too large

A cosmetic pilot avoids the difficult dependencies and proves little. An enterprise programme creates so many dependencies that no single change can reach users quickly. A vertical slice sits between them.

Choose a vertical slice

Pick an outcome with visible pain, commercial value and an identifiable owner. Examples include:

• from first clinic enquiry to a prepared first appointment;
• from vehicle intake to customer-ready listing;
• from referral receipt to a clinical decision;
• from accepted proposal to an accurately scheduled service.

Then follow recent cases, not the documented “happy path”. Observe the actual emails, calls, forms, workarounds and decisions. Ask four things at every step:

1. What information arrives, and can it be trusted?
2. What decision is being made, by whom, and using what evidence?
3. What is waiting while this happens?
4. What repair work occurs when the step fails?

Redesign before you automate

Remove information nobody uses. Combine approvals that protect against the same risk. Make ownership explicit. Separate common work from genuine exceptions. Only then decide where forms, integrations, automation or software can reduce effort.

This discipline often produces an unfashionable result: a simpler process with a small amount of technology. That is a successful transformation if cycle time, errors or customer uncertainty fall.

Measure the operational change

A transformation metric must be close enough to the work to move within weeks. Useful measures include elapsed time, number of hand-offs, touches per case, percentage requiring rework, avoidable contact, or time spent reconstructing status.

The first slice should also leave a repeatable method: evidence, decisions, a working change and a clear account of what remains. That creates confidence to address the next outcome without pretending the whole business must be redesigned at once.