Skip to content
Framework System Integrity REEF

REEF Framework

System integrity for transformation work. REEF checks whether a changed system has held — and rebuilds it on solid ground when it has drifted.

The Framework

Where DIVE moves a workflow forward, REEF checks whether the structure underneath is sound. Use REEF when something that used to work has started to drift, or before you scale a model you are not yet sure about.

R

Renew

Restore ownership and accountability clarity. Who is actually responsible for each part of the work now — not who was, not who should be on paper, but who owns it today?

Output: Refreshed ownership map, accountability reset, decision rights clarity
E

Examine

Compare the actual workflow against the intended one. Find where practice has quietly diverged from design — the informal workarounds, the skipped steps, the unstated conventions.

Output: Actual-vs-intended gap analysis, divergence inventory, undocumented workarounds
E

Evaluate

Test governance and quality gates. Are the checkpoints still doing their job, or have they become theatre? Is oversight catching real problems, or just adding delay?

Output: Governance gap report, gate effectiveness assessment, checkpoint retirement list
F

Foundation

Rebuild on proven structure. Keep what works, retire what does not, and re-anchor the system on solid ground. Document what was hardened so the next team knows why.

Output: Hardened operating foundation, retirement decisions, structural documentation

When to Use REEF

REEF is a diagnostic tool, not a failure signal. Applying REEF means you are being deliberate about system health — not that something has gone wrong.

After a major transformation

A DIVE sprint changed the workflow. Three months later, check whether the new model is holding or whether teams have reverted to informal patterns.

"I think people have stopped using the new intake process."

Before scaling

You're about to roll a working pilot to the whole organisation. Run REEF first to make sure the model is solid enough to scale without importing its cracks.

"We want to roll this out to all teams by Q3."

When governance feels like theatre

Meetings happen, sign-offs are collected, but nothing actually changes. The checkpoint exists but the gate isn't catching anything real.

"We go through the motions but everyone already knows the answer."

When ownership is fuzzy

Multiple people think they own the same thing, or nobody thinks they own something that needs to be owned. Both are accountability gaps.

"I thought X was handling that — weren't they?"

When workarounds have become standard practice

The official process exists, but everyone uses a version that bypasses it. The workaround is now the process — which means the documented process is fiction.

"We all just message Sarah directly."

When performance has plateaued after initial improvement

A transformation drove early gains, then improvement stalled. REEF often finds structural drift — the model partially reverted without anyone noticing.

"We made great progress early but now we seem stuck."

Running a REEF Assessment

R — Renew Ownership

Map current accountability against the intended model. For each key function, name the actual owner today — not the role, the person. Identify gaps, overlaps, and inherited ownership that was never formally transferred.

Prompt: For each part of this workflow, who is actually responsible today? Is that the same person who was responsible six months ago? If not, when did ownership change and was it deliberate?

E — Examine the Gap

Walk the real path of the work as it happens today. Compare against the intended design. Document every divergence — whether it is a workaround, a shortcut, an informal channel, or a step that has quietly disappeared.

Prompt: Show me how this work actually moves from start to finish right now. Where does it differ from the documented process? What steps are skipped? What steps have been added that aren't in the design?

E — Evaluate Governance

Test each checkpoint. Is it catching real problems? Is it adding signal or just adding delay? Are approvals meaningful, or are they rubber-stamped? Is the oversight proportionate to the risk?

Prompt: When this checkpoint catches a problem, what happens? When was the last time it actually stopped something that should have been stopped? Could we remove this gate without increasing real risk?

F — Rebuild the Foundation

Make deliberate decisions: what gets hardened, what gets retired, and what gets redesigned. Document the reasoning so future changes are made against a known baseline, not a guess.

Prompt: Given what we now know about how the system is actually working, what do we keep, what do we remove, and what do we redesign? What needs to be documented so the next person understands why the structure is this way?

REEF in the Framework Family

REEF works alongside DIVE and MURK as part of a complete transformation vocabulary. Each addresses a different job.

The Three Frameworks

DIVE
Forward movement — diagnose the workflow, redesign it, validate it, enable it with AI
REEF
System health — renew ownership, examine drift, evaluate governance, rebuild on solid ground
MURK
Resistance naming — give friction a name before it can be addressed

Use MURK to name what is slowing things down, DIVE to design and ship the forward move, and REEF to keep the result healthy after it scales. DIVE is the engine; REEF is the maintenance; MURK is the diagnostic lens.

See DIVE Framework