Build a register of the risks attaching to low-code platform governance and keep it current.
Governing Low-Code Development Platforms and Controlling Their Security Quality
Turn low-code platform governance from a stated policy into a practice your organisation can evidence.
Course Overview
The constraint on low-code platform governance is rarely the model or the platform — it is the data and the operating discipline behind it. Technology choices around this aspect of digital and data-driven work are easy to reverse on paper and expensive to reverse in practice. The programme builds the judgement to know which parts of the wider digital and data-driven work agenda to standardise and which to leave flexible. The version of low-code platform governance described in the manual and the version practised on the floor tend to diverge over time. The teaching approach is deliberately practical: participants build a delivery roadmap for this part of digital and data-driven work as they go. Post-incident reviews keep identifying weaknesses in this strand of digital and data-driven work that were visible long before the incident. The material serves both public bodies and commercial organisations dealing with low-code platform governance. This programme builds the practice within digital and data-driven work from first principles, without padding and without omitting what matters. The programme ends where implementation begins, with this aspect of digital and data-driven work broken into steps someone can start on Monday.
Expected Learning Outcomes
Document decisions about low-code platform governance in a form that remains useful after the people change.
Assess whether low-code platform governance should be built in-house, bought, or delivered through a partner.
Define escalation and fallback for low-code platform governance when the automated path fails.
Design the integration points between low-code platform governance and the systems already in production.
Integrate low-code platform governance into existing management routines rather than running it separately.
Build a security and access model for low-code platform governance appropriate to the sensitivity of the data involved.
Who Should Attend
Vendor and contract managers overseeing suppliers involved in low-code platform governance.
Operations managers whose processes are changed by low-code platform governance.
Risk managers assessing the exposure created by low-code platform governance.
Chief information officers accountable for the investment in low-code platform governance.
Project and programme managers whose delivery depends on low-code platform governance.
Solution architects designing how low-code platform governance fits the existing estate.
Course Modules
Low-code platform governance: security, privacy and regulatory obligation
2 sessions · 8 pointsSession 1Escalation and decision rights in low-code platform governance
- Close out actions on low-code platform governance rather than leaving them open indefinitely.
- Define the service level low-code platform governance must meet and what happens when it is missed.
- Identify where judgement in low-code platform governance is legitimate and where it is not.
- List the data sources low-code platform governance consumes and confirm each has a named owner.
Session 2The data question everyone skips at the start of low-code platform governance
- Verify that low-code platform governance still performs when input volume doubles unexpectedly.
- Confirm that reporting on low-code platform governance reaches the people who can act.
- Prepare the response for the most likely failure in low-code platform governance.
- Record the reasoning behind each architectural choice in low-code platform governance.
Low-code platform governance: architecture, integration and the existing estate
2 sessions · 8 pointsSession 1The pilot that actually settles the argument about low-code platform governance
- Design the pilot for low-code platform governance so that a negative result is still useful.
- Reduce the variation in how low-code platform governance is carried out between teams.
- Identify every system low-code platform governance must read from or write to.
- Check that records of low-code platform governance answer the questions likely to be asked.
Session 2Testing low-code platform governance before relying on it
- Prepare the summary of low-code platform governance that senior management will read.
- Specify the fallback path when low-code platform governance is unavailable.
- Define acceptance criteria for low-code platform governance in advance.
- Set out the decisions in low-code platform governance that require sign-off and by whom.
Low-code platform governance: from pilot to production
2 sessions · 8 pointsSession 1Sizing low-code platform governance honestly before committing budget
- Test low-code platform governance against edge cases drawn from real historical records.
- Confirm that those complying with low-code platform governance understand why it exists.
- Name a single owner for each element of low-code platform governance.
- Decide which legacy process low-code platform governance retires, and set the date.
Session 2The decisions in low-code platform governance that cannot be delegated
- Remove steps in low-code platform governance that add effort without adding assurance.
- Build the user briefing that explains what low-code platform governance does and does not decide.
- Set the metrics that will show whether low-code platform governance is drifting from its intended behaviour.
- Decide what will be stopped to create capacity for low-code platform governance.
Low-code platform governance: monitoring, drift and operational ownership
2 sessions · 8 pointsSession 1Making low-code platform governance secure without making it unusable
- Draft the minimum viable delivery roadmap for low-code platform governance.
- Identify the skills the team lacks to operate low-code platform governance independently.
- Review whether low-code platform governance is aligned with the objectives of the transformation programme.
- Arrange the handover of low-code platform governance so capability survives staff changes.
Session 2The governance low-code platform governance needs and the governance it does not
- Confirm the retention and deletion rules applied to data inside low-code platform governance.
- Assess the regulatory obligations low-code platform governance triggers in each jurisdiction.
- Measure the current quality of the data feeding low-code platform governance before assuming it is usable.
- Classify the data in low-code platform governance and apply access controls that match the classification.
Choose the package that suits you
Silver Package
At least 3 people
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.