All essays

Technology leadership

Why technology and compliance need one accountable executive

Cloud, AI and a wave of operational-resilience regulation have made every architecture decision a compliance decision. Running them under separate executives now costs more than it saves.

Roy Biakpara, , 8 minute read

For years the standard model was simple: a technology leader to build and run things, and a compliance or risk leader to check them. It worked when regulation moved slowly and technology changed in annual releases. Neither is true any more.

NIS2, DORA, the EU AI Act and the UK's own resilience agenda don't regulate paperwork; they regulate how systems are designed, operated, monitored and recovered. Meanwhile cloud and AI mean architecture decisions are made weekly, by teams, in code. The compliance consequences of those decisions arrive whether or not anyone with compliance accountability was in the room.

When technology and compliance report to different people, risk ends up owned by nobody.

What goes wrong with two owners

I've seen the pattern in critical infrastructure, financial services and technology businesses alike. Delivery teams treat compliance as a late-stage gate. Compliance teams discover design decisions after go-live, when remediation is expensive. Risk acceptances bounce between two executives, each reasonably assuming the other owns it. The Board hears two narratives and has to reconcile them itself.

What a single accountable executive changes

A Chief Technology and Compliance Officer owns the roadmap and the obligations together. Regulatory requirements become design inputs rather than audit findings. Risk appetite is expressed as engineering tolerances teams can build to. Evidence is generated by the platforms themselves, so assurance is continuous rather than an annual scramble. And the Board gets one account of whether technology is delivering safely.

On a recent multi-cloud transformation, embedding risk ownership directly in delivery meant 92% of high-severity issues were closed before go-live. Not because anyone worked harder at the end, but because the decisions were made by people accountable for both outcomes.

It isn't a merger of two jobs

The role only works if it's built on genuine depth in both: enough engineering literacy to challenge architecture, and enough regulatory judgement to know which risks are acceptable. Done well, it removes a layer of friction that most organisations have simply learned to live with. That's the seat I believe more organisations will need over the next five years.

Next essayThe trust gap: the missing architecture of AI innovation