Every deployment has two endings. The one on the plan is go-live: the cutover weekend, the first payroll, the champagne email. The second ending gets no slide and no email. It is the Friday when hypercare closes, the SI's badges stop working, and the program stops being a program.
I have watched the Monday after that Friday enough times that I can walk it by the clock. The hours below are a composite, but nothing in them is invented. Every one of these moments comes from real programs, and if your deployment ended with a calendar date instead of an exit gate, most of them are already on your schedule.
Go-live ends the project. It starts the product. Whether the product compounds or decays comes down to three things that all cost money before Monday: a funded run team, one intake queue, and a named owner per area.
The day, by the clock
Badge in. The war room is dark.
The whiteboards are wiped. The chairs are pushed in for the first time in fourteen months. For a year, this room was where problems went to die: you walked in with a broken business process and walked out with a named person and a date. As of this morning, problems have nowhere to go.
Nobody notices this at 7:55. The system is up. Payroll ran Friday. The dashboards are green. The absence in this room is invisible until the first thing breaks, which will take about 95 minutes.
The access requests start stacking.
A new manager cannot see her team. A cost center moved and the approver chain broke. A terminated contractor still has a live account, which is the one that should scare you. During hypercare these were fixed inside an hour because a consultant with security access sat in the room. Today the same requests go to a help desk that does not yet have a Workday queue, gets triaged as "software issue," and waits.
Access is always the first thing to pile up, because access changes every single day. People are hired, moved, promoted, and terminated whether or not anyone owns the security model. By Friday this queue will be the longest one you have.
An integration fails. The alert goes to a folder.
The benefits file to the carrier errors out on three records. The integration did exactly what it was configured to do: it fired an alert. The alert went to a shared mailbox that was created for the project team, and the project team no longer exists. Nobody is in the folder.
This is the quietest failure mode in ERP and the most expensive per incident. An unwatched integration does not fail loudly on day one. It fails silently for days, and you find out from the far end: the carrier, the bank, the state agency. The fix costs nothing at signature: every integration alerts a person, not a folder. On the first Monday, that clause is worth more than most of the testing budget.
The tickets queue. Everyone is back at their day job.
The functional leads who carried the design are payroll managers, accountants, and HR business partners. The plan always said they would return to their day jobs after go-live, and their calendars agree. What the plan never said is who inherits the 40 hours a week of Workday work they were doing, because the honest answer was nobody, and writing that down would have forced a hiring conversation the budget did not want.
So the tickets queue. Not dramatically. Three today, five tomorrow. The backlog that eventually gets labeled "adoption problems" starts here, in week one, as simple unowned capacity.
Report request 14. Nothing gets retired.
A director asks for a report that does not exist. Someone builds it fast, saves it next to the other 400, and moves on. The catalog grew again. No owner, no naming standard, no retirement rule. Run this pattern for two years and you get the report estate every rescue engagement finds: hundreds of near-duplicates, a handful that matter, and nobody who can say which is which.
The rule that prevents it fits in one line: every report has an owner or it goes, and you retire more than you build.
Someone asks the question.
It happens in a hallway or on a Teams thread, and it is always phrased the same way: "who owns this now?" Security thinks the help desk does. The help desk thinks HRIS does. HRIS is one analyst who was hired for the old system. Finance assumes HR has it because the project sat under the CHRO.
The question defines the next two years, because a system nobody owns does not stay still. It decays: two feature releases a year ship whether you test them or not, access drifts, integrations rot, and the report catalog compounds. The organizations that answer the question before Monday run a product. The ones that answer it in a rescue engagement run an archaeology dig.
Nothing failed on Monday
Read the timeline again and notice what is missing: a failure. The software worked all day. Every one of those six moments traces to a decision made months earlier, usually in a budget review, usually framed as discipline. The run team was a line item, and it got cut. Hypercare got a calendar date instead of an exit gate. The knowledge transfer plan became a SharePoint folder of recordings nobody will watch.
The industry data says the average program delivers 56% less value than the business case promised. In my experience the gap does not open at go-live. It opens in the first year of running, at the rate of one unowned Monday at a time, and it opens slowly enough that nobody notices for about nine months.
The run-ready check
Five conditions, all checkable before your hypercare end date. Tick what is true today.
Will your first Monday hold?
If your Monday is already behind you
Most teams read this after the fact, not before. The recovery sequence is the same at month two or month nine, just slower: name the owners first, stand up the single intake queue second, then walk the integration alert routing in one afternoon, because that is where the silent damage is accruing. Fund the run team from the value the business case already promised; you are not asking for new money, you are asking to stop losing the money already spent.
I run day-one readiness reviews in the last month of hypercare, and run-team rescues after the fact: owners, intake, release governance, and the report estate. The full first-year playbook is free in The Complete Workday Run Guide, and the hypercare exit conditions are in Hypercare that stabilizes the business.