top of page

Scalable Governance: From 8 Team Safety Training to Portfolio Level Coordination

  • Writer: Ola Seweje
    Ola Seweje
  • 6 days ago
  • 3 min read

I've scaled safety training from 8 team members to 120+ contractors annually. That scaling process teaches you how to build governance that works at portfolio level. The first version of the contractor training programme was manual, labour-intensive, and only possible because I ran it personally for a small team. The current version runs across multiple concurrent projects with a modular structure that doesn't require my personal delivery on every session. That's what scalable governance looks like.

What Doesn't Scale: Heroic Effort

The first version of the contractor safety training programme relied on my personal delivery of every training session, my personal review of every certification assessment, and my personal follow-up with contractors who needed additional support. That model worked when the programme was small. It became a bottleneck as the programme grew.

Heroic effort doesn't scale because it's bounded by individual capacity. Any governance system that depends on one person doing everything in that system hits a ceiling when that person's capacity is exhausted. Identifying the heroic effort elements of any governance system and replacing them with process, tooling, or delegation is the fundamental task of scaling governance. The contractor training programme's scaling journey from 8 to 120+ required explicitly identifying every heroic effort element and replacing it with a scalable alternative.

What Does Scale: Frameworks and Process

The training curriculum itself is a scalable framework. Once the curriculum is designed, documented, and validated against the Red Book and HSG 47 standards, it can be delivered by any qualified trainer, not just the programme designer. The certification verification process, once it's designed as a structured assessment with defined pass criteria, can be administered by any assessor, not just the programme manager.

Process documentation is the mechanism that makes frameworks scalable. A training curriculum that exists in the trainer's head doesn't scale. A training curriculum that exists as documented modules with delivery guides, assessment criteria, and quality standards can be delivered at scale by multiple trainers simultaneously. The investment in documentation is the investment in scalability.

Governance That Scales

Portfolio-level programme governance faces the same scaling challenge as the training programme. The first version of governance on concurrent delivery programmes is often a system that works because the portfolio manager is involved in every decision at every level. That system produces good decisions but it doesn't scale.

The governance structures I've developed for concurrent delivery, the three-level risk register that separates site, programme, and portfolio risks, the weekly governance meeting structure with embedded stakeholder representation, the permit acceleration protocols that are pre-built for standard utility types, are all designed to function without heroic effort at the portfolio level. Site-level governance happens at the site level. Programme-level governance happens at the programme level. Portfolio-level governance focuses on strategic alignment and escalation management.

How Scalable Processes Become Competitive Advantage

The GLA's adoption of the contractor training programme as a model is the clearest evidence that scalable governance creates competitive advantage. A training programme that can only be delivered by one person is a proprietary capability that dies when that person leaves. A training programme that has been documented, standardised, and validated against regulatory standards is a transferable asset that organisations can adopt and adapt.

In customer success management, scalable governance is what allows a customer success manager to manage a larger book of accounts without proportionally increasing the time they spend on each account. The onboarding process, the health monitoring framework, the escalation protocols, and the expansion playbook all need to be designed to function without heroic effort. When they are, the customer success manager's leverage increases. When they aren't, account growth creates workload growth that quickly becomes unsustainable. The portfolio delivery case studies demonstrating scalable governance in action are at olamapped.com.

Recent Posts

See All
Portfolio Thinking in Infrastructure Delivery

Managing a £38M portfolio across multiple concurrent sites requires portfolio-level thinking that most project managers don't develop. Project management is a skill of managing a defined scope to a de

 
 
 

Comments


bottom of page