"When will it be ready?" is the question every planned item attracts. The tempting answer is a date. Customers like dates. Sales teams love them. And almost every team that publishes them regrets it within a quarter.
Why dates go wrong in public
Estimates are wrong, routinely and in one direction. Inside the team, a slip of two weeks is a normal Tuesday. On a public roadmap, it's a broken promise, seen by everyone who was waiting, often screenshotted. Each slip costs a little trust, and slips compound.
Dates also change what people do. A customer who sees "March 14" may plan a launch around it, tell their boss, or delay buying something else. When it slips, you've cost them more than a wait.
When a date is right
There are cases where a date is the honest thing to share:
- The work is nearly done and you're confident. A date two weeks out is far safer than one two quarters out.
- The date isn't yours. A regulation takes effect, a partner retires an API. Customers need to know you'll be ready for it.
- A specific customer needs it for a contract. Share it with them directly, not on the public board.
Keep dates for your team
Internally, dates are useful. They help people plan and coordinate. You can keep a target date on a post for your team without showing it publicly.
When you've already published dates
If your roadmap has dates today, you don't need to remove them all at once. As each one comes up, either hit it or replace it with a quarter and a sentence. "Moving to next quarter: we found a better approach that takes a little longer." Most customers will take honesty about a slip far better than silence about one.