Less than 20% of professional services firms have a formal customer experience strategy. Among Fortune 2000 companies, the figure is 88%. That gap doesn't exist because managing partners at law firms or COOs at accountancy practices are less intelligent than their counterparts in tech or retail. It exists because the organisational machinery that keeps a regulated firm safe - the committees, the sign-off chains, the deeply ingrained culture of "get it right first time" - also happens to be extraordinarily effective at killing anything that looks like change.
And that machinery is doing exactly what it was designed to do.
I've spent the better part of two decades working with firms like yours - law firms, financial services businesses, accountancy practices, consulting firms - and the pattern is so consistent I could set my watch by it. Someone senior recognises that the digital experience is falling behind. A programme gets scoped. It's ambitious, properly funded, thoughtfully designed. It goes to the partnership or the board. And then it enters the committee cycle. Compliance wants a review. Risk wants an assessment. Three partners who weren't consulted early enough raise concerns. The scope gets amended. The timeline slips. Six months later, the programme is either quietly shelved or limping forward with half its original ambition and none of its original energy.
We've tried to change things before. The organisation is too cautious, too committee-driven. Every proposal gets delayed, amended, or quietly shelved.
I hear that almost word for word in about a third of my initial conversations with managing partners. And I genuinely empathise with it. But I think the lesson most people draw from the experience is wrong. The lesson isn't that the organisation can't change. The initiative was shaped in a way that gave the organisation's immune system everything it needed to reject it.
There's a different approach. And it doesn't involve pushing harder.
Before we get to what works, it's worth sitting with why the standard approach keeps failing. Because this isn't about timidity.
Think about what gets rewarded in your firm. Thoroughness. Caution. Getting it right. Not making mistakes that end up in front of the regulator. The professional premium placed on accuracy and risk avoidance is what makes your firm trustworthy to clients and credible to the SRA, the FCA, or whoever's watching. That's not something to apologise for.
But that same culture - the committee approvals, the blame-avoidance instincts, the need for consensus before anything moves - doesn't distinguish between "this decision could expose us to regulatory risk" and "this decision might improve our website." Everything gets run through the same machinery. A proposal to redesign the client portal triggers roughly the same organisational response as a proposal to change how you handle client money. The friction is rational in its origins but wildly disproportionate in its application.
McKinsey's research tells us that 70% of transformation programmes fail across all sectors. In regulated industries, you're adding governance complexity on top of the usual execution challenges. So when your big, ambitious digital programme stalls, you're not an outlier. You're the norm.
Here's what I've watched happen, more times than I'd like to count. A firm commissions a significant digital programme - let's say a website rebuild with CRM integration and a new client portal. Budget is £300k-plus. Timeline is 12 months. It requires input from IT, marketing, compliance, and at least half the partnership.
What happens next is entirely predictable. The programme's size and ambition - which the sponsor sees as a signal of seriousness - is received by the cautious organisation as a signal of risk. Compliance wants to review every customer-facing element. IT raises concerns about integration with existing systems. Partners who remember the last failed project become vocal sceptics. The programme spends 60% of its energy fighting internal resistance and 40% actually delivering anything.
I was in a conversation last year with the COO of a mid-sized accountancy firm - about 400 people across six offices - who'd watched exactly this happen. Nine months. A fair chunk of budget. One deliverable: a strategy document that was already out of date by the time it was approved. She said something that stuck with me: "We didn't fail because the plan was wrong. We failed because the plan was so big that everyone could find a reason to slow it down."
That's the core of it. In a risk-averse organisation, the size of the initiative is directly proportional to the resistance it generates.
I should say: I've made this mistake myself. Early on, I thought the answer to organisational caution was a more compelling vision - a bigger, bolder case for change that would sweep the sceptics along. It doesn't work like that. I had a client in financial services, probably 2015 or so, where we'd built what I still think was a genuinely excellent digital strategy. Thorough, well-evidenced, properly costed. The partnership spent four months debating it and eventually approved a version so watered down it was essentially a website refresh. We got there in the end, but I wasted a year learning a lesson I should have understood sooner: the quality of the argument is almost irrelevant if the size of the ask triggers the immune response.
So what actually works? Starting smaller. And I want to be precise about what I mean, because "start small" sounds like settling for less. It isn't.
A well-designed pilot in a risk-averse environment is a strategically superior approach to building the evidence and internal confidence that make larger investment possible. Research into change management in regulated environments suggests that pilot programmes demonstrating measurable outcomes in low-risk contexts are five times more likely to receive full-programme approval in subsequent budget cycles. Five times. That's not marginal.
The pilot needs to be small enough that it doesn't require full committee approval. Specific enough that it produces measurable results quickly. Low-risk enough that a failure would be instructive rather than career-threatening. And - this is the bit most people miss - visible enough that a success is noticed by the people whose support you'll need for the next phase.
We worked with a professional services firm - around 300 people - where the CTO was under pressure to do something meaningful with AI. The instinct was to commission a comprehensive AI strategy: workshops, a governance framework, a roadmap covering every department. That would have taken six months and required sign-off from a dozen stakeholders who didn't agree on what AI was for.
Instead, we ran a 14-day AI readiness assessment, identified the highest-impact use case - automated proposal generation - and delivered a working tool in a 90-day sprint. The result was a 60% reduction in proposal turnaround time and roughly 12 hours of senior consultant time saved per week. The second and third use cases were commissioned immediately after. Not because we'd persuaded anyone with a PowerPoint. Because the evidence was sitting right there, undeniable, saving people time every single day.
That's what a good pilot does. It converts sceptics by making the abstract concrete.
Not all pilots are created equal. I've seen plenty that produced decent results and went absolutely nowhere - the findings land in an inbox, someone says "great, let's discuss in Q3," and Q3 never quite arrives.
The difference between a pilot that builds momentum and one that disappears into a drawer comes down to five design decisions.
Scope it for speed. Results within a quarter, not a year. If your pilot takes 12 months to show outcomes, you've lost the window. People forget. Priorities shift. Budget cycles move on. A 90-day sprint with a clear outcome is worth more organisationally than a 12-month programme with a better theoretical ROI.
Measure against something specific. Not "improve the user experience." Something like "reduce portal login failures by 40%" or "cut proposal turnaround from five days to two." If there's any room for debate about whether the pilot worked, the sceptics will fill that room.
Be honest about the risk. The pilot should be something where failure is instructive, not catastrophic. You're not betting the firm's reputation on this. You're testing an approach in a contained environment. If it doesn't work, you've spent £50k-£80k and learned something useful. That's a perfectly acceptable outcome - and saying so out loud, before you start, tends to make cautious stakeholders considerably more relaxed.
Staff it with people who actually want to be there. This sounds obvious, but it's where a lot of pilots quietly die. If you put people in the room who were assigned rather than committed, you'll get grudging compliance rather than genuine engagement. Find the people in your firm who are frustrated by the status quo - they exist, I promise - and give them something to run with.
Tell people it's happening before it starts. A pilot that nobody knew about produces results that nobody believes. The managing partner, the head of compliance, the sceptical senior partner who blocked the last initiative - they should all know this is happening. Not because you need their approval (the whole point is that you don't), but because you need them watching. When the results come in, you want them to already be paying attention.
This is the bit that genuinely winds me up, because I've watched successful pilots fail to convert into funded programmes simply because nobody told the right people what happened.
A law firm - top 50 in the UK, about 180 lawyers - where the marketing team ran a brilliant pilot. They restructured the enquiry paths on the website, built proper conversion points, and saw a 67% increase in qualified enquiries within six months. Phenomenal result. The managing partner didn't know it had happened until we mentioned it in a completely separate conversation three months later. Three months. The evidence was sitting there. Nobody had put it in front of the person who could approve the next phase.
Effective pilot communication isn't complicated. A monthly one-page update to the relevant leadership group - not a 20-slide deck, one page, what we did, what happened, what it means. A direct conversation, face to face rather than email, with whoever will approve the next phase of investment. And a clear articulation of what the pilot proved and what would need to be true for the next phase to be worthwhile.
That last bit matters. You're not asking for a blank cheque. You're saying: "Here's what we learned. Here's what we think we could do next. Here are the conditions under which that would make sense." You're making it easy for a cautious decision-maker to say yes - because you've already answered the questions they'd have asked.
I want to be clear about something, because I know how this might land in a firm where governance and compliance aren't optional. The small-wins approach is not a trick to sneak change past the risk committee. It's not a workaround. It's a genuinely better method for achieving meaningful progress in an environment where caution is both necessary and valuable.
68% of firms in regulated sectors cite legacy systems as the primary obstacle to AI adoption. That's not going to get fixed by a single pilot. The goal here is momentum toward more significant change - not the celebration of small improvements as an end in themselves. A successful pilot doesn't replace the need for a proper strategy, a funded programme, and proper governance. It creates the conditions under which those things can actually happen.
The organisations I've seen make the most progress aren't the ones that fought their own culture head-on. They're the ones that worked with it. They respected the caution, acknowledged the governance, and then found a way to produce evidence so clear that even the most sceptical committee couldn't argue with it.
Start small. Measure relentlessly. Tell people what you found. Then go again.
If you want to talk through how to scope a pilot for your firm - something designed to produce clear evidence quickly and build the case for the next phase - get in touch. It's usually a pretty short conversation.