Key takeaways
- Treat transformation as an operating habit, not a one-time capital project.
- Start with an expensive, measurable problem — never with a platform.
- Ship thin vertical slices in production early instead of stacking dependency-heavy phases.
- Automate the boring, rules-heavy work first for fast, trustworthy ROI.
- Budget for adoption and behaviour change as seriously as for the technology.
Transformation is not a project. It's a habit.
Most digital transformation efforts die in the gap between the slide deck and the shipping. A leadership team commits to a bold vision, a consultancy produces a beautiful roadmap, and eighteen months later very little has actually changed in how the organisation works. The technology was rarely the problem. The problem was treating transformation as a one-time capital project rather than an operating habit.
We've worked with teams across e-commerce, services and industry, and the pattern that separates the ones who succeed is unglamorous: they start small, ship real things quickly, and let each win fund the next. Ambition is essential — but ambition without a bias for shipping is just anxiety with a budget.
Start with a painful problem, not a platform
The fastest way to lose momentum is to begin by choosing a platform. Buying a shiny system before you understand the workflow forces your people to bend around software instead of software serving your people. Instead, start with a single expensive problem — one that costs real hours, real money or real customers every week.
- Name the cost. Quantify what the problem drains today. If you can't measure it, you can't prove the transformation worked.
- Map the actual workflow. Not the documented one — the real one, with its workarounds and shadow spreadsheets.
- Define what "solved" looks like. A concrete, measurable end state within 60–90 days.
This keeps the effort honest. A problem you can measure is a problem you can prove you fixed.
Ship in slices, not in phases
Traditional roadmaps stack dependencies: finish phase one before phase two, integrate everything, then go live. That structure hides risk until the very end. We prefer thin vertical slices — small end-to-end pieces of value that run in production early, even if they only cover 10% of the eventual scope.
A slice that quotes prices automatically for one product category beats a full pricing engine that launches next year. Real usage surfaces the assumptions your workshops missed, and every slice in production is a slice generating feedback and returns rather than sitting in a backlog.
Automation and AI: leverage, not magic
The current wave of AI tooling makes it tempting to automate everything at once. The pragmatic move is the opposite. Find the repetitive, rules-heavy tasks that consume skilled people's time — data entry, first-line support triage, content drafting, reporting — and automate those first. These give fast, defensible ROI and build organisational trust in the technology. Reserve the more ambitious, judgement-heavy use cases for once your team has the confidence and data foundations to support them.
The real bottleneck is adoption
The most elegant system delivers zero value if people route around it. Transformation is 30% technology and 70% behaviour change. Ambitious teams over-invest in the human side:
- Involve the people doing the work in designing the solution, not just receiving it.
- Remove the old path. As long as the spreadsheet still works, the new tool will be optional — and optional means ignored.
- Appoint internal champions who understand both the work and the tool, and give them time to support colleagues.
Adoption is where transformation is won or lost. Budget for it as seriously as you budget for licences.
Build for change, not for permanence
The single most important design principle is that requirements will change. Companies that hard-wire today's process into rigid systems pay for it every time the market shifts. Favour modular architecture, clean data foundations and integrations over monoliths. The goal isn't a finished system — it's an organisation that can keep changing cheaply.
This is what pragmatic transformation really means: not a heroic leap to a distant future state, but a compounding series of small, measured improvements that make the next improvement easier. Ambitious teams don't need a bigger plan. They need a faster loop between deciding and doing.
If you're weighing how to turn a bold digital ambition into something that actually ships, we'd be glad to talk it through — no deck required. Let's discuss where your most expensive problem is hiding and what a first slice might look like.
