Consulting · Legacy modernization
The PROVEN Migration Methodology™
“Earn the cut-over.”
-
P
Pin the programme
-
R
Register what applies
-
O
Observe the witness
-
V
Verify within budgets
-
E
Earn the cut-over
-
N
Notarize the handoff
Your migration, proven — within declared populations, budgets, and dates. Never 'proven, full stop.'
Three Records, One System
Every system your organization runs carries three separate records of what it does, and the three rarely agree with each other. The witness is what the system actually did — the logs, the state transitions, the artifacts it left behind. The business record is what the organization intended the system to do — the requirements, the sign-offs, the story told to the steering committee. The legal record is what the law and the regulator require the system to do, whether or not the code comments mention it.
Your test suite covers one of these circles. Your regulator reads all three.
A dashboard can be green by omission — passing every test it was written to run, silent about every population it was never asked to cover. A claim made without its population attached is not evidence.
The Four Gates
A gate that can't say no is a doorway.
-
Diagnose
6
instruments
Can refuse: a programme with no bounded population.
-
Design
9
instruments
Can refuse: a control design with no evidence plan behind it.
-
Demonstrate
13
instruments
Can refuse: a pilot whose evidence doesn't clear budget.
-
Deliver
21
instruments
Can refuse: a cut-over resting on a stale claim.
Funded exit, after Diagnose. The population doesn't bound. Nothing downstream has been scheduled to walk back.
Funded exit, after Design. The control design doesn't hold. Pre-authorized, no penalty for taking it.
Funded exit, after Demonstrate. The pilot's evidence doesn't clear budget. The programme stops — not the cut-over, because there isn't one yet.
Deliver ends at the cut-over — the one gate on this path that is not a funded exit. Every gate before it is.
- questions, answered in order
- 3
- gates
- 5
- measurements
- 6
- instruments across all four phases
- 49
The committee's demand list fits on a card. If a vendor can't fill in 3·5·6, you've learned what you needed to know.
A Method, Not A Template Pack
- Source-bounded
- Every claim traces to the public, versioned paper — never to a private slide deck that can say anything a room wants to hear.
- Evidence-bounded
- Missing stays UNEVIDENCED. Aged evidence goes STALE. Neither one quietly becomes a pass.
- Interlocking outputs
- Each gate's output is the next gate's input. An instrument in isolation proves nothing — the chain is the proof.
- Built for governance use
- Committee artifacts, not team dashboards — what a CRO or head of audit can put in a board pack.
The Claim Grid
Plot your vendor's equivalence promise on this grid — including ours.
| Evidence current | Evidence stale | |
|---|---|---|
| Claim bounded |
Decision-grade Bounded, dated, current. This one can carry a committee decision. |
Refresh before deciding The claim still holds its shape. Its evidence has aged out of budget. |
| Claim unbounded |
Narrow it Fresh evidence, no declared population. Name the denominator and it moves up. |
Marketing No population, no date. Reads as a promise; survives no cross-examination. |
What A Completed Instrument Proves
A completed form is a record, not a result.
This is the line most methods blur, so it is stated here in the two columns it actually has. Everything on the left is what the artifact can carry into a committee room. Everything on the right is what someone will still have to judge.
It shows
What was recorded, and by whom
- Which fields were completed — and which were left open
- The named owner who completed them
- The date it was true
- The evidence state: current, STALE, or UNEVIDENCED
It does not show
Anything a human still has to decide
- That the control was effective
- That the system conforms
- That the organization is compliant
- That the cut-over will succeed
Who This Is For
For you if
- You are the CIO or CTO sponsoring a core-system modernization and need to show your committee more than a vendor deck.
- You are the CRO or head of audit who must be able to veto the cut-over — and needs gates that can actually say no.
- You are the head of engineering who has to live with what ships, long after the consultants are gone.
Not for you if
- You want a fixed-price, off-the-shelf migration tool with no governance layer — this is a governed programme, not a subscription.
- You need the full instrument catalog before you will engage — the operative detail is scoped and licensed after Diagnose, never published.
- Nobody with veto authority over the cut-over is in the room yet — bring them in before the first gate, not after.
The Proof Behind The Method
This method is the delivery discipline behind The Oracle You Already Own — the public paper on the evidence your organization's systems already carry, and why most modernization programmes never go looking for it.
Pricing Posture
Pricing follows the engagement shape and its gates. Funding is bounded to the next gate — Diagnose is scoped and costed on its own, and nothing past it is committed until that gate clears. See the four engagement shapes on /consulting/.
Frequently Asked
Proven by whom?
Is this a conformity assessment or legal advice?
Can the pilot actually stop?
What do we receive?
Bring the modernization programme your committee can actually approve.
Start a conversation through the "Legacy modernization programme" option on the consulting inquiry form.