What a headless migration taught me about saying no

This is a sample note so you can see how the blog works. To write a real one, duplicate this file, change the frontmatter at the top, and write markdown below it.

Re-platforming a storefront while the shop keeps selling is like renovating a restaurant during dinner service. Everything is urgent, everyone has a request, and the only way through is a brutally honest definition of “must have.”

The stakeholder map came first

Before a single user story was written, we mapped who would feel the migration: merchandising, CRM, customer service, the warehouse. The features they fought for were rarely the features customers noticed — and the discovery work saved us from shipping three of them.

”No” is a product decision

Every “yes” during a migration is borrowed time. The most valuable artifact we produced was not the roadmap — it was the list of things we explicitly agreed not to rebuild. Half of them were never missed.

If you are heading into a re-platforming project: write the not-doing list first, get it signed, and revisit it monthly. It will be the calmest document in the room.