Rescue: a modernization program flagged red by the client
A two-workstream modernization program at a Fortune 100 financial services firm, flagged red by the client’s own domain review before I took it over. No delivery methodology, no governance plan, no documented commitments, and nobody on either side owning requirements — which were being reverse-engineered out of legacy code. Fourteen engineers, a hard seasonal freeze I could not move, and an executive sponsor who had already lost confidence.
Led as primary delivery owner, from delivery lead through executive sponsor. Had the client define milestones rather than inherit a date, and put one named owner on each. Narrowed three parallel batch jobs to one, and front-end scope from five transaction types to one proven end to end — a repeatable pattern beats five half-finished ones. Rejected: holding the original date and pushing harder. Closed volume against work in flight said it would not land, and a missed date after a death march costs more credibility than a renegotiated one.
Nine milestones defined where there were none; first two demoed sixteen days after I landed — the first working increment the engagement had produced. On the batch side, specification approved first pass, stories the same day, build four days later, and my engineer promoted to technical lead with the client’s backing. Both workstreams now target delivery ahead of the October freeze. In flight.
ReflectionI moved on governance before requirements ownership, and requirements was the more expensive gap by a wide margin. Where a client-side expert owned the specification, the work moved within days. Where nobody would take that seat, it did not.