Chapter 06
The RDI maturity curve
The three stages of organisational maturity in RDI — visibility, control, and optimisation — and how to recognise the failure modes between them.
01
What this lesson is about
Most organisations adopting RDI move through three recognisable stages. Each stage has real value. Each stage has a ceiling. The failure modes between them are organisational rather than technical, which is why most attempts to advance through hardware upgrades stall. By the end of this lesson you should be able to place your own project on the curve, identify the failure mode that is keeping it at the current stage, and pick the one workflow whose closure would advance it. The lesson is diagnostic. Honesty matters more than ambition. A project that names its stage correctly will advance faster than one that overclaims.
02
Visibility, control, and optimisation as stages
Visibility is the entry stage. Cameras, walks, and drones produce a record people can look at. Owners feel closer to the project; site teams have something to show in the OAC pack; a few useful clips emerge during disputes. Control begins when named workflows close on top of the record. Progress meetings open with evidence rather than memory. Safety findings become observations with owners and clocks. Delivery disputes resolve in minutes rather than days. Optimisation is the portfolio stage. Patterns of recurrence surface across projects. The leadership team directs programmes of work in response: supplier reviews, capture-plan templates, training rotations. Each stage produces value. The mistake is to stop at visibility because it feels like progress and confuse it with control, or to stop at control because the project is calm and miss the portfolio learning that optimisation provides.
03
The failure mode between visibility and control
The most common failure between visibility and control is the absence of named owners. The capture is happening. The records exist. The platform has surfaced findings. Nobody owns them. Findings sit in a feed and decay. The site team rationalises the decay with a story about being too busy, which is true and irrelevant. The diagnosis is not technical. The cure is operational: pick one workflow, name a single owner, agree the closeout record, and run it for six weeks. Resist the temptation to advance every workflow at once. The teams that move from visibility to control fastest pick the workflow with the highest current pain and treat the others as next quarter’s work. They also resist the urge to add more cameras or another module before the first workflow is closing reliably.
04
The failure mode between control and optimisation
The failure between control and optimisation is the absence of a command view. Each project closes its own workflows. Each project produces its own closeout records. Nobody is comparing across the portfolio. Patterns of recurrence stay local. The same supplier underdelivers on three projects in three regions and nobody connects the dots. The same package phase produces non-conformances in the slab pour across the portfolio and the lesson is learned three times instead of once. A command view is not a dashboard. It is the operational habit of a leadership team reading exception summaries across projects each week and deciding which patterns belong at organisational level. Without that habit, optimisation does not happen even on a fully instrumented portfolio.
05
How to advance with discipline
Advancing on the curve is concrete work. Pick the workflow currently most painful and most informal. Name the owner. Agree the trigger, evidence, decision, action, and closeout record. Run it for six weeks. Report on closeout. Do nothing else for that period. Once the loop is closing reliably, pick the next workflow. The tempo matters: one closed loop per quarter on a single project is faster than three half-built loops, because half-built loops decay and have to be restarted. At portfolio level, the equivalent discipline is to pick one pattern of recurrence per quarter and treat it as a programme of work with its own owner, milestone, and closeout. The leadership teams that maintain this tempo pull ahead of the ones that try to do everything in the first six months.
Practice
01. Place your current project on the maturity curve and write one sentence on which failure mode is keeping it at that stage.
Look for: A strong response is honest about the stage, names the specific organisational gap rather than blaming the platform, and identifies the role responsible for closing it.
02. Pick the single workflow whose closure would move your project to the next stage. Write the trigger, the named owner, the closeout record, and the six-week milestone.
Look for: A strong response chooses one workflow rather than a list, sets a realistic milestone, and resists adding hardware before the loop is reliably closing.
Checkpoint
For your project, which stage are you on, and which workflow would you close first to advance?
Recommended reading