The 4Cs
A simple way to control change and risk in delivery.
Core. Configuration. Customisation. Context.
Not new ideas — just a practical way to use them when things need to land cleanly.
This is the lens I use to control change and risk in real programmes — particularly in migration, integration, and cutover.
Most delivery issues don’t come from the platform itself. They come from how change is introduced around it.
The 4Cs makes that visible: Core, Configuration, Customisation, and Context.
The Four Cs. Twice. Please.
A practical framing for delivery — alongside the common 4Cs
The 4Cs fits alongside a simple delivery pattern:
DEFINE → MOVE → PROVE
Understand the Core and Context properly. Use Configuration where possible. Control Customisation. Then prove the outcome end to end.