You Don't Need a Digital Transformation. You Need One Problem Solved.

I’ve sat in a lot of boardrooms. I’ve watched a lot of “digital transformation” programs kick off with fanfare, run for twelve months, and produce a 47-page strategy document that nobody acts on.

The business is still using the same spreadsheets. The same manual processes. The same workarounds that everyone quietly hates but nobody has the authority — or the energy — to fix.

This is not a failure of ambition. It’s a failure of scope.

The Problem With Transformation

“Digital transformation” is a seductive idea. Fix everything. Modernise the whole operation. Come out the other side as a leaner, smarter, technology-enabled business.

The trouble is, when you try to fix everything at once, you end up with a sprawling initiative that’s too big to move quickly, too complex to govern cleanly, and too abstract to show results. Six months in, the steering committee is still arguing about priorities. The frontline staff have stopped believing it will change anything. And the consultants are writing another update report.

I’m not being cynical. I’ve lived this from the inside — fifteen years in enterprise IT, from the service desk through to application development and leading delivery teams. The pattern repeats regardless of industry or budget.

The programmes that actually change how businesses operate? They almost never start with transformation. They start with one problem.

One Pain. That’s Your Starting Point.

Every business has a single constraint — one process, one gap, one recurring headache — that, if you removed it, would save the most time or money right now. Not in theory. Right now.

It might be that your team spends four hours every Monday morning manually compiling a report that nobody reads but everyone assumes someone else needs. It might be that new client onboarding takes three weeks when it should take three days, and you’re losing people in that window. It might be that you’re paying staff to answer the same ten questions by email, every single day.

The question I ask every business I work with isn’t “what technology do you need?” It’s: what is costing you the most right now?

Find that. Start there.

Why This Works (And Why It Compounds)

When you solve one concrete problem, several things happen.

First, you get a result. A real one — measurable, visible, and felt by the people doing the work. Not a report, not a recommendation, not a roadmap. An actual change in how much time something takes or how much it costs.

Second, you build trust — internally and with whoever helped you get there. Your team sees that change is possible. That technology can actually help them, rather than being something imposed on them from above.

Third — and this is the part most people don’t expect — the next problem becomes obvious.

Once the manual reporting is gone, you can suddenly see clearly that the data feeding into those reports is also a mess. Once onboarding is faster, the next bottleneck becomes client communication. Once your team stops answering the same emails, they have time to notice that your quoting process is slower than it needs to be.

Progress compounds. Each solved problem reveals the next one. That’s not a flaw in the approach — it’s the whole point. You’re not doing one thing and walking away. You’re building a real picture of how the business works, one layer at a time.

Over time, this becomes something more valuable than any transformation program: a technology partner who actually knows your business. Who understands your industry, your team’s workflows, your constraints, and what’s realistic. That’s not something you can buy with a project plan. It’s built through repeated, successful delivery.

What Good Scoping Looks Like

Before you can fix the right problem, you have to find it. That’s not a five-minute conversation.

Good scoping means talking to the people doing the work, not just the people managing it. It means understanding what the process actually looks like on a Tuesday afternoon, not what it’s supposed to look like on paper. It means being honest about budget, timeline, and what “good” actually means to the business.

This is real work. It takes time, expertise, and experience to do well. On smaller projects, I often work this into the engagement. On larger ones, scoping is a paid piece of work in its own right — and it should be.

A scoping engagement should give you clarity on what problem you’re actually solving, why it’s the right one to start with, and what success looks like. If someone is offering to scope a complex project for free, ask yourself what their incentive is. The answer is usually to sell you the implementation, not to find the best starting point.

The Enterprise Difference

I’ve spent the past fifteen years inside large, complex organisations. I’ve seen what works at scale and what collapses under its own weight.

That experience shapes how I work with smaller businesses. I’m not bringing enterprise bureaucracy with me. I’m bringing the pattern recognition — the ability to spot what’s actually the constraint, what’s a symptom of something deeper, and what’s genuinely worth fixing first.

I also build with the same AI tools I recommend. I’m not advising from a distance. When I tell you that a particular approach will save your team twelve hours a week, it’s because I’ve built versions of that solution myself and I know what it takes to make them work in practice.

That’s the difference between a practitioner and a theorist. Practitioners have skin in the game. They’ve seen things break, fixed them, and learned what not to do next time.

Start Small. Build From There.

If you’re thinking about technology — whether that’s AI, automation, a new system, or just a better way of doing something you currently do manually — don’t start with transformation. Start with your biggest pain.

Write it down in one sentence. “We waste [X hours/dollars] every [week/month] on [specific thing].” If you can write that sentence clearly, you’ve found your starting point.

Then figure out what it would take to fix that one thing. Not everything. That one thing.

Fix it. See what changes. Then talk about what’s next.

That’s how real progress works. Not initiative by initiative — problem by problem.

---

If you want to work through what your biggest pain actually is and whether it’s solvable, I’m happy to have that conversation. No pitch, no pressure. Just a straight conversation about what’s costing you the most and what might be worth doing about it.