The biggest delay isn't implementation. It's understanding.

One assumption still appears in many regulatory change programmes: that implementation is the longest part of the process. In practice, it often isn't. By the time implementation begins, most organisations have already decided what needs to change. The difficult part is getting to that point.

Anyone who's worked on a significant regulatory programme will recognise the pattern. A new regulation, supervisory letter or consultation paper is published. The compliance team reads it. Legal provides an initial view. Business leaders ask what it means for their area.

Then the discussions begin. Not about whether the regulation applies, but about what it actually requires the organisation to do. That is where momentum often slows. The regulation itself rarely answers those questions.

• Should existing controls be redesigned?
• Is this a clarification of existing expectations, or a change in supervisory approach?
• Does it affect one business line or several?
• Will Internal Audit need to adjust its assurance programme?
• Should work begin immediately, or is further regulatory guidance likely to follow?

None of those questions has an obvious answer. They require judgement.

One thing that's become increasingly noticeable is that organisations are spending less time trying to find regulatory information and much more time understanding its operational impact. That's a subtle change. But it's an important one.

The challenge has shifted from collecting information to interpreting it.

The Financial Conduct Authority (FCA) illustrates this well. Anyone involved in UK financial services will know that Dear CEO letters, thematic reviews, supervisory statements and speeches often influence how firms interpret regulatory expectations long before formal rule changes arrive.

Waiting for legislation alone rarely provides the complete picture. Understanding where supervisory expectations are heading has become just as important. This is why two organisations can receive exactly the same regulatory publication and respond very differently. One identifies the implications quickly and begins planning. The other spends weeks debating what, if anything, actually needs to change.

Perhaps that's because understanding regulatory change has become less about reading regulations and more about understanding context. Each part of the organisation brings a different lens to the same publication.

None of those perspectives is wrong. The challenge is bringing them together quickly enough to support confident decision-making. Implementation still matters. It always will.

But implementation rarely creates the biggest delay.
Reaching agreement on what needs to change usually does.

As regulatory expectations continue to evolve, organisations that develop that understanding more quickly will be better placed to respond with confidence. Increasingly, that's becoming one of the defining capabilities of modern compliance functions.