Three years ago, I sat in a conference room with twelve insurance brokers, watching them debate whether moving from paper filing to cloud storage would violate Financial Conduct Authority regulations. The conversation lasted two hours. Two hours for what most businesses would consider a basic operational decision.
At the time, I’ll admit, I was frustrated. Here was a clear efficiency gain, obvious cost savings, and reduced risk of human error. Yet we were stuck discussing regulatory compliance, staff training protocols, and client communication strategies. It felt like bureaucratic theatre.
I was completely wrong.
That painstaking process taught me more about successful digital transformation than any tech conference or case study ever has. The insurance industry—along with finance, healthcare, and other heavily regulated sectors—has cracked the code on something most businesses struggle with: how to implement lasting technological change without breaking what already works.
The Problem with Moving Fast and Breaking Things
Silicon Valley’s favourite mantra has infected business thinking across industries. The idea that you should implement first and sort out the consequences later might work for social media platforms, but it’s a disaster for businesses with real-world obligations.
I’ve seen too many digital transformation projects fail because leadership treated them like software deployments rather than organisational change. They focused on features and functionality whilst ignoring the humans who would actually use these systems daily. They prioritised speed over adoption, assuming that efficiency gains would automatically translate into business value.
But regulated industries can’t afford this approach. When you’re handling client money, personal data, or safety-critical processes, “move fast and break things” isn’t a strategy—it’s a path to regulatory sanctions and lost licences.
This constraint, which I initially viewed as a hindrance, actually forces a more thoughtful approach to digital transformation. It requires you to consider stakeholder impact from day one, to plan for compliance requirements, and to build consensus before implementation.
The Stakeholder-First Approach
Those insurance brokers didn’t spend two hours debating cloud storage because they were technophobic. They were methodically working through every stakeholder who would be affected by the change.
First, they considered their clients. How would this affect data access during claims? Would client communication need to change? What reassurances would clients need about data security?
Then, their staff. Who would need training? How would workflows change? What backup procedures were required? Which team members might resist the change, and why?
Finally, their regulators. Which compliance requirements applied? What documentation would be needed? How should they communicate the change to the FCA?
This systematic stakeholder analysis revealed potential issues that would have derailed the project later. The administrative assistant who processed claims had been with the company for fifteen years and knew every client file location by memory. The change would initially slow her down, potentially affecting claim processing times during her adjustment period.
By identifying this early, they could plan additional training, temporary support, and client communication about potential delays. What could have been a crisis became a managed transition.
Compliance as a Design Constraint
Most businesses view compliance as a box-ticking exercise—something to address after the fun work of building systems is complete. Regulated industries know better. They treat compliance requirements as design constraints from the beginning.
This changes everything about how you approach digital transformation. Instead of asking “What’s the coolest solution we could build?” you ask “What’s the best solution we can build within our constraints?”
These constraints often lead to better solutions. When privacy regulations require explicit consent tracking, you build more transparent customer relationships. When financial regulations require audit trails, you create systems with better accountability and error tracking. When safety regulations require redundancy, you build more reliable systems.
I’ve started applying this thinking to unregulated businesses. What if we treated customer trust like a regulatory requirement? What if we designed systems as if we had to justify every data collection practice to a regulator?
The results are remarkable. Solutions become more focused, more user-friendly, and more trustworthy. Teams spend less time retrofitting compliance and more time building value.
Building Consensus, Not Just Systems
The most striking difference between successful and failed digital transformation projects isn’t technical—it’s cultural. Regulated industries understand that lasting change requires consensus building, not executive mandate.
This doesn’t mean democratic decision-making about every technical choice. It means ensuring that everyone understands why change is necessary, how it will affect their work, and what support they’ll receive during the transition.
That insurance brokerage didn’t just announce the move to cloud storage. They ran workshops explaining the risks of paper filing, demonstrated the new system’s benefits, and addressed individual concerns. They created champions within each team who could support their colleagues during the transition.
By the time they implemented the change, it wasn’t something being done to the team—it was something the team had decided to do.
The Long Game Advantage
This approach takes longer upfront, but it creates more durable change. While other businesses cycle through digital transformation initiatives, regulated industries build systems and processes that last.
They also build organisational capability for future change. Teams that have been through thoughtful transformation processes become more adaptable, not less. They understand how to evaluate new tools, how to manage change processes, and how to maintain compliance during transitions.
This compounds over time. Businesses that master systematic change management become faster at subsequent transformations, not slower.
Beyond Regulation
These lessons apply far beyond regulated industries. Every business has stakeholders to consider, constraints to work within, and people who must adopt new ways of working.
Whether your constraints are regulatory, budgetary, or cultural, treating them as design parameters rather than obstacles leads to better outcomes. Whether your stakeholders are customers, employees, or shareholders, involving them in change processes increases adoption and reduces resistance.
The next time you’re planning a digital transformation project, try the regulated industry approach. Map your stakeholders systematically. Identify your constraints early. Build consensus before you build systems.
It might take longer than the “move fast and break things” alternative, but you’ll be far more likely to create change that actually sticks.
After all, what’s the point of transforming quickly if the transformation doesn’t last?