Process-Led System Design at Regulatory Organisation
In just 10-weeks, a clear picture of the business was created and used as a platform for designing a custom system. To-Be models, requirements/ user stories and RFQ packs were built, enabling Vendors to be evaluated and selected. The design shaped development, ensuring an efficient, effective and compliant process, whilst engaging the broader business to increase engagement, visibility and control.
Head of Digital Services at the UK Oil & Gas Authority
Challenge & Opportunity
Their existing processes were outdated and made limited use of modern tools / automation. Extensive manual effort was required in creating, responding to and maintaining data records, few of which were digitised effectively. This resulted in duplication of data entry, non-real time status tracking and output data which was not integrated with downstream operations.
The initial step was to collect all existing process collateral to prepare draft frameworks. Key stakeholders were brought together in a workshop to be briefed on the project, trained in the basics of process management and used to define a high-level end-to-end view of the process.
Interviews were then held with the Process Owners and Subject Matter Experts (SMEs) to fully define the in-scope, As-Is landscape through detailed BPMN 2.0 models. In parallel, an issue register was maintained, documenting current problems and improvement / innovation opportunities.
Once this had been signed-off by senior leadership, three analysis approaches were deployed:
- Value-add – maximising value from critical activities, streamlining non-critical activates.
- Problem-based – addressing stakeholder concerns and improvement suggestions; and
- Automation redesign – where can the business be restructured to maximise automation opportunities.
Based on this analysis, To-Be process models were drafted describing the system user profiles and the associated responsibilities. The models were reviewed with both SMEs and IT to ensure alignment. Prioritised system requirements / user stories were prepared to support the post transformation process, with the Minimum Viable Product (MVP) clearly defined.
To generate a view of the data recorded throughout the in-scope processes, an As-Is Bus Matrix (Data Dictionary) was created. This described all data fields currently captured, the format of the data and who was responsible for entering it. With this as the baseline, a To Be Bus Matrix (Data Dictionary) was defined. This was streamlined and the timelines/ responsibilities for entering the data aligned with the To-Be processes.
All the collateral was extracted into a System Design Report and reviewed with a preferred software vendor to ensure coherence, completeness and feasibility. Updates were made after this session and, with this done, it was ready for submission to vendors through an RFQ.
A compelling, fully costed business case that yielded the following benefits: