Breaking the "Launch Date" Curse
A U.S. B2B SaaS company, nine months into a website rebuild. Engineering and Marketing were barely speaking. Every week the C-suite asked for a date. Every week nobody could give one.
Before
No single person was willing to say no to a VP's feature request. Every new idea reopened the release boundaries. The team had stopped trusting the roadmap because the roadmap had never held.
What we fixed
Ran a "Keep vs. Kill" session where every open request had to survive a single question: does this need to be in V1.0, or can it wait? The list of things that could wait was longer than anyone wanted to admit. Shifted to V1.0 + V1.1 and enforced a 24-hour decision rule, unresolved trade-offs were called the next morning based on pre-agreed goals, not whoever was loudest.
After
- Site shipped six weeks after engagement started
- No release-plan changes in the final four weeks of build
- First time Engineering and Marketing agreed on a launch date, and held it
“For the first time in a year, the project actually felt calm.”