In a previous blog here, I looked at why there is a business case for using Regulatory Architects to manage Regulatory Architecture.
If you have ever been involved in a regulatory change project, you will likely have experienced the many ‘pains’ that are encountered when trying to understand, let alone implement, complex regulations.
The role of the Regulatory Architect is to alleviate these pains by bridging the gap between the regulatory process and project delivery.
So what are some of the tools that the Regulatory Architect might use to ‘bridge the gap’ and enable greater implementation efficiencies?
- Deploying structured ‘knowledge management’ for processing 100’s of pages of regulation and consultation and turning them into structured, usable process that we can work with
- Decomposing the regulations and mapping the ‘regulatory impact’ across the project workstreams
- Processing the regulations and converting them into requirements and deliverables that can be implemented
- Mapping the constant changes and updates that evolve in real-time into the project
- Ensuring top-to-bottom coverage that spans scope and business case right through to implementation and ‘getting your hands dirty at the coal face’
In my next blog here, I want to look at the efficiencies that Regulatory Architecture will bring to the Programme.
Pingback: Regulatory Architecture: A New Stategy for Managing Regulatory Change | johnphilpott.com