A Migration Deadline and the Corner the Team Gave Up

A Migration Deadline and the Corner the Team Gave Up

Deep inside a regional freight business, the infrastructure team was handed a deadline that did not care about anyone’s preferences. The lease on their old hosting arrangement ended in ten weeks, and the reporting service that dispatchers relied on every morning still ran there. The brief from management was familiar: move it soon, keep the cost down, and make sure nothing breaks. This case study, a fictional composite of the kind of story many delivery teams will recognise, follows how the team handled the fast, cheap or good trade-off in a DevOps migration.

The setting

The reporting service was not glamorous. It pulled data from several internal systems, produced summaries overnight, and served them through a web interface that dispatchers opened at the start of each shift. Its deployment process was a mixture of scripts and manual steps passed down by people who had since moved on. The new environment would run on managed cloud infrastructure, with an automated pipeline replacing the manual steps.

The team lead gathered the group and drew a triangle on the whiteboard with the three words at its corners. Everyone had heard the idea before. What was new was the instruction that followed: before any ticket was written, each person would say which corner they believed the project should protect.

Three answers, three projects

The answers split. One engineer wanted to protect cheap, pointing out that the migration budget was already tight. Another wanted to protect good, since a failed morning report would hit dispatchers directly. A third wanted to protect fast, because the lease date could not move. Each view was reasonable, and each described a different project.

  • Protect cheap and good: the move would take longer, probably past the lease date, which meant paying for an extension on the old arrangement.
  • Protect fast and cheap: the team would copy the service across as it was, manual steps included, and accept a fragile result.
  • Protect fast and good: the team would spend more, buying temporary capacity, extra test environments and a short engagement with outside help.

The lead observed that the date was fixed by a contract, and that a morning report failing was costly in ways the finance team could measure. Those two facts decided it. The team would protect fast and good, and give up cheap, openly and on purpose.

Writing the choice down

A paragraph went into the project document: “The lease date and the morning report are protected. Cost is relaxed. The programme may exceed the original budget by an agreed margin, and requests to trim spending will be weighed against the date and reliability.” The sponsor signed it, which mattered more than the wording. From then on, when someone asked whether a parallel test environment was really necessary, the answer was already on paper.

The team also agreed on a ceiling. Giving up cheap did not mean a blank cheque. The sponsor approved a stated overspend, and any request beyond it would go back to the sponsor for a decision. That kept the sacrificed corner from growing quietly.

What the team spent the money on

With cost relaxed, the spending went where it protected the other two goals. The team ran the old and new environments side by side for three weeks, so every morning they could compare outputs. They paid for a short burst of contract help to rewrite the most fragile scripts as pipeline stages. And they bought extra capacity for a load rehearsal, so the first busy morning would not be the first time the system met real traffic. For background on why surges deserve rehearsal, see this article about coping with enormous visitor spikes using cloud capacity.

Not every dollar was well spent. One expensive tool trial produced little, and the team admitted it in their weekly review. The difference was that the overspend was visible and discussed, not discovered at the end.

Where the old habits showed up

Midway through, a manager asked whether the team could skip the side-by-side comparison to save a few days. The lead replied with a single question: which corner are we now willing to relax? Skipping the comparison would give up good, which had been protected. Nobody wanted to reopen that choice, and the comparison stayed.

A different request arrived from the dispatch office, asking for a new filter on the report. It was reasonable, and it was sent to a later release. The trigger rule from the project document made that an easy answer, not a standoff.

There was also a quieter benefit. The dispatchers, who had been nervous about the move, were invited to look at the old and new outputs next to each other during the parallel weeks. Two of them spotted a rounding difference in a weekly total before the engineers did. Letting the people who depend on a system see the evidence made the final switch feel like a shared step, not a surprise handed down from the technology group.

The engineers also kept a short daily note of what the overlap was costing. By the second week the number was larger than anyone had liked, and the sponsor asked whether to stop early. Because the group could point to the signed paragraph and to the comparison results gathered so far, the conversation took ten minutes and ended with the plan intact.

The cutover week

The cutover happened over a quiet weekend. The team had rehearsed it twice, and the pipeline handled the deployment without the old manual steps. On Monday morning the reports appeared on time. A minor formatting difference in one summary table turned up, which the team fixed by lunchtime. Because the comparison data was available, they could prove that the figures themselves matched.

The final bill was above the original number and inside the agreed margin. The team and sponsor both treated that as the plan working, not failing, because the extra spend had bought exactly the two outcomes they had decided to protect.

What other teams can take from it

Three habits stand out. First, the choice was made at the very beginning, before the plan hardened. Second, it was written in plain words and signed by the person with authority over the budget. Third, each later request was judged against it, so the trade stayed visible. The same approach works whether the project is an infrastructure move, a paper-to-digital transition like the one described in this practical guide to leaving paper records behind, or a smaller automation task.

Teams who want to see the triangle described outside their own field sometimes browse a blog about cloud operations whose pages are short and written in plain language. It is a reminder that the vocabulary of a trade-off is shared across many kinds of work, even when the tools differ.

A note on the fictional frame

The team, company and numbers in this story are invented to illustrate a pattern. The pattern itself is common. Delivery work frequently meets a fixed date, a limited budget and a demand for reliability, and the teams that do well are those that decide which of the three to relax before the pressure starts.

Had the lead chosen differently, the story would have been different but not worse. A cheap and good migration with a paid lease extension would have been a legitimate plan too, as would a fast and cheap copy with its fragility accepted and monitored. What made the project calm was the decision itself, taken early, recorded clearly and respected under pressure.