// For transformation leaders
Real plays from real transformations — sent to IT directors and CTOs who are done rebuilding the plane mid-flight.
Join 3,400+ leaders shipping real change.
Step-by-step sequencing for moving off legacy platforms — data mapping, cutover windows, rollback triggers — pulled from transformations that actually shipped.
How to sunset the system nobody wants to touch: dependency mapping, stakeholder sequencing, and the decommission checklist most teams write after it's too late.
The adoption plays that get a skeptical department off Excel and into the new stack — without a mandate from the top forcing it.
Scorecards and bake-off structures for the buy decision, built from RFPs that avoided a second failed rollout.
issue-44 — migration-timeline.log
Fourteen weeks, not the six the vendor quoted. The actual week-by-week breakdown, including the three-week stall nobody put in the retro deck.
issue-45 — buy-vs-build.log
A scoring framework for the decision that kills more transformation budgets than any other, revised after two more years of AI-vendor sprawl.
issue-46 — root-cause.log
Post-mortems from six stalled programs, traced back to the same root cause in five of them — and it's never the platform.
“This is the only newsletter I've kept in my Wednesday routine for two years. The Lotus Notes issue got forwarded to our whole steering committee.”
“The vendor evaluation frameworks alone paid for the time I spend reading this. We used the buy-vs-build tree on our ERP decision and it held up under board scrutiny.”
One email, thirty seconds. No sales call, no gated content behind a demo request.
One transformation broken down in full — timeline, budget, the decision that almost sank it.
Every issue ends with a single action sized for your next two weeks, not your next fiscal year.
inbox — [email protected]
FirstNex Playbooks <[email protected]>
7:14 AMWe Migrated 400 Users Off Lotus Notes — Here’s the Real Timeline
Morning — fourteen weeks. That's how long it actually took to move 400 users off Lotus Notes, against the six the vendor quoted us in the SOW.
“The delay wasn't the migration tooling. It was three weeks lost waiting on a calendar-sync edge case nobody scoped.”
Full timeline and budget variance below.
— Daniel Okafor, Editor
IT directors, digital transformation leads, and CTOs at traditional companies running a real modernization program — not vendors pitching a platform.
Vendor-neutral. We don't take placement fees from the vendors we evaluate, and when a playbook names a tool, it's because a subscriber's team shipped with it — not because someone paid for the mention.
Every playbook includes the actual timeline, the vendor shortlist that got cut, the budget variance, and the step that almost killed the project — the details a polished case study leaves out.
No. Most subscribers join mid-program, looking for the specific decision in front of them — a legacy exit, a vendor bake-off, a rollout that's stalled. Search the archive by that decision, not by issue number.
Every Wednesday morning, five minutes to read, one tactic you can apply to this sprint. Built to survive being read between two standups.
Join 3,400+ IT leaders reading FirstNex before their next steering committee meeting.