Three casinos. One night. Eleven specialists. Not a single shot fired. Danny Ocean's heist works for the same reasons a Business Central go-live does: the right crew, one job each, a rehearsal vault and a plan for when it goes wrong.
Three casinos. One night. Eleven specialists. Not a single shot fired.
Nobody remembers Ocean's Eleven for the robbery. They remember the crew, and the planning that made the night look easy. A Business Central go-live works the same way. The weekend is the easy part. The job is won in the weeks before it.
Danny doesn't start with the vault. He starts with the people: the pickpocket, the explosives expert, the tech, the acrobat, the con man, the inside man, the drivers, the money. One skill each. No passengers.
For your project: name the team before you sign anything. Sponsor, project manager, process owners, super users, data owner, and someone technical on your side who owes the partner nothing. "Available when they can" is not a role. (The right project team.)
Reuben puts up the money, but not before he's grilled Danny on the risks, the odds and the crew. He's not along for the ride.
For your project: that's your sponsor. They fund it, they chair the steering group, and they keep asking awkward questions until go-live. A sponsor who signs and vanishes is how projects drift.
Rusty walks the crew through a model of the casino. Every person knows what they do, when, and who they hand over to. Nobody improvises on the night.
For your project: that's the solution design and the cut-over plan. Every step has an owner and a time. If someone can't tell you what they're doing at 11am on go-live Saturday, the plan isn't done. (The go-live weekend, hour by hour.)
The crew builds a full-size copy of the Bellagio vault and rehearses until it's muscle memory.
For your project: that's your sandbox. Copy production, run the migration end to end, reconcile to the penny, time it, then do it again. Go-live should be the third performance, not the first. (Use a sandbox.)
Frank works the casino floor. He knows the routines nobody wrote down.
For your project: every business has a Frank, the person who knows every exception in the purchase ledger or which bins are actually used. They're your super users. Put them in the room from day one. (Super users.)
The fight, the power cut, the vault, the swap. In that order, to the minute.
For your project: close the old system, take control totals, load master data, load balances, reconcile, switch on integrations one at a time. "Saturday: migrate data" is not a plan. It's a hope.
Danny gets spotted. Benedict smells a rat. The crew adapts, because they'd already thought about what could go wrong.
For your project: agree go/no-go points and rollback criteria before the weekend, and give someone the authority to call it. Rolling back on Saturday is the professional call. A week's delay costs less than a quarter of untangling.
Everyone gets a share, because it only worked with all of them.
For your project: thank the super users, the data owner and the finance team in public, and recognise it in pay and appraisals. You'll need the same crew for the next job.
Unless someone plans well enough to beat it. In an ERP project, the house is business as usual: the day job, the old system, the workarounds. Left alone, it wins every time.
So pick the crew, give everyone one job, rehearse until it's boring, plan for the bit that goes wrong, and share the credit.
Then go and rob the place.
Planning a go-live and want an experienced hand on your side of the table? Book a 30-minute call.
