Build, Buy, Keep, Replace, or Stop Decisions
A council compares complete strategies for its benefits system, separates migration from future exit, and calculates when a higher-priced option pays off.
A council compares complete strategies for its benefits system, separates migration from future exit, and calculates when a higher-priced option pays off.
A supplier announces a feature removal fourteen months ahead. The buyer must check rights, recover business rules, and test an alternative before negotiating.
Trace a rising cloud bill through usage, commitments, unit costs, and service requirements, with clear owners and evidence for each spending decision.
A partial four-million estimate becomes nine million over the same three years. Reconcile the costs, then test the assumptions behind the next case.
Eleven projects reported green, yet the combined forecast missed a regulatory deadline. The recovery plan makes integration, decisions, and readiness visible.
Ninety-four projects were approved, forty-one were running, and the one the strategy depended on had been waiting for staff for eleven months.
The new claims system had been live for a year and a third of the branches used it. The business case had booked the savings in month one.
Row counts matched on both sides at cutover. Month-end totals disagreed by eleven thousand. The count had been the only check anyone wrote down.
Three years in, sixty percent of features had moved, twenty-three adapters kept the old system alive, and nobody could say which system owned a customer record.
The register mapped 203 systems to 299 hosts. Discovery found 340 hosts, including 41 unregistered ones; the initial migration plan had missed their dependencies.
The program moved three hundred servers to the cloud in fourteen months and called it transformation. Two years later billing still changed once a quarter.