Part 1 of 7 · 6 min

What you own on Monday

The cutover weekend ends and the migration tool's job ends with it. Part 1 of the Change Series: the machine that remains, and why the second initiative costs a fraction of the first.

It is Monday morning at Danubia, our invented manufacturer from the last series, and the migration is in stabilization. The new system holds the supplier master. The seal from the cutover still verifies. The war room is a regular meeting again, and people took Friday off for the first time in months.

The first request arrives before ten. The legacy system is still running. It costs license money, it needs a patching team, and its disks hold the archived legal-hold rows from part 4 of the last series. Somebody should switch it off. Everyone agrees, the way everyone agrees about exercise.

Watch what happens to that request in most estates. It becomes a slide, then a project, then a plan owned by whoever spoke last. The discipline that carried the migration, the gates, the signatures, the tie-outs, stays behind in the migration, because it was bought as a migration. The next change starts from zero, with a fresh spreadsheet.

This series is about the other path, and the claim is simple to state. The migration you just finished was one instance of a general thing: a governed unit of change. The machine that ran it does not know it was built for a migration, and on Monday it is still yours.

The request becomes an initiative

At Danubia, the switch-off request does not become a slide. It becomes an initiative of type decommissioning, on the same platform that ran the migration.

The type matters, because a decommissioning is not a small migration. It has its own ladder of phases: scope definition, dependency migration, graceful shutdown, physical retirement, and a post-decommission audit at the end. The audit closes the ladder because a system that went dark quietly is a system nobody can answer for. Each phase has entry conditions and exit gates, and the initiative cannot skip down the ladder because a quarter is ending.

Nobody at Danubia designed that ladder in a workshop. It came with the type, the way the migration's ladder of discovery, design, build, cutover and stabilization came with its type. A team can adjust within the frame. What it cannot do is invent process from scratch at the moment it is least equipped to, which is the start.

Six shapes of change, one machine

Decommissioning is one of six. The platform ships typed ladders for the changes an estate actually undergoes. The six: migration, onboarding, the integration of an acquisition, a compliance program, a capability buildout, and the retirement of a system.

The ladders differ because the work differs. The acquisition type runs from pre-close through day one, the first hundred days, operational integration, and on to synergy realization. The compliance type runs from gap analysis through remediation design, implementation and validation. Its last phase is attestation, which readers of our first series will recognize as the point of the whole exercise.

One boundary belongs in the same breath, because this is where category vendors overpromise. Synergy realization is a phase with entry and exit conditions, never a measured business outcome. Our platform does not gate a phase on a revenue number, and part 6 of our first series explains why we refuse to pretend otherwise.

What the six types share is everything below the ladder. The same server recomputes every gate, and nobody advances a phase by asserting readiness in a status meeting. The same sole writers record every decision, with the same receipts. The same rule holds that human judgment survives re-runs, and the same seals refuse to form over guesses. Learn the machine once, on any type, and you know it for all six.

Why the second initiative is cheap

Here is the economics, because Monday's argument is an economic one.

Danubia's migration was expensive the way first times are expensive. People learned what a confirmed pair is, what a gate demands, what a countersign means, and why the platform sometimes says no. That learning cost real weeks, and on most projects it evaporates when the consultants leave.

The decommissioning inherits all of it. The reviewer who confirmed field mappings reviews shutdown dependencies with the same moves. The delivery lead who learned that gates read the record, never the meeting, plans the shutdown against gates from day one. The charters fold the same way, the exceptions get named the same way, and the audit trail accumulates in the same place. What changed is only the ladder on top.

There is a second inheritance, quieter and worth more. The decommissioning does not start by discovering the estate, because the estate is already modeled. The two downstream reports that still read the legacy tables are edges in the graph, not surprises in week six. The legal-hold obligation from the migration is a recorded decision with a named home. The new initiative starts from what the last one proved.

What this is not

Three boundaries, stated before a buyer finds them.

We do not execute the change. The shutdown scripts, the patching, the license cancellation: your teams and your integrator, on your side of the line. The platform governs the decisions and holds the proof, which is the same division of labor the migration had.

The phase ladders are not project management. There is no Gantt chart underneath, no resource leveling, no timesheet. Tools for that exist and yours can stay. What they do not have is gates that recompute from evidence, and that is the part we sell.

And the machine does not make change fast. It makes change answerable, which sometimes means slower, in the specific places where fast is how estates get hurt. Our first series called this the cost of honesty, and it did not apologize for it.

Where this goes

The next five parts open the machine. Part 2 takes the unit itself: what an initiative is, how a phase advances, and why the advance cannot be talked forward. Part 3 takes the charter, which nobody writes and everybody signs.

Part 4 takes the single door through which work arrives. Part 5 takes the exceptions, because a governed system that cannot bend breaks in ungoverned ways. Part 6 governs the weekend itself. Part 7 returns to the buyer, a year later, to count what accumulated.

The claim to hold until then fits in one sentence. A migration ends, change does not, and what you own on Monday is the machine.

Part 2: A unit of change with a spine. Typed initiatives, phase machines, and the advance that cannot be talked forward.

part 2 →A unit of change with a spine

Model your first domain today.

You send five documents, we model them, and the first cut comes back in days.