Every company has a roadmap. The question is whether it's written down. Founders carry one in their heads — the next product they want to ship, the hire they want to make in Q3, the partnership they're hoping closes by year-end — and that mental roadmap drives the decisions that actually happen day to day. The trouble is that nobody else can see it. So the team executes against guesses, vendors quote based on a snapshot, and three months in everyone is doing slightly different work for slightly different goals, and no one can quite say when the trajectory started bending.
Writing the roadmap down has a strange property: it almost always shrinks. The moment you list everything you said you'd do this year, on one page, in priority order, the impossible-ness of it becomes obvious. Things drop off. Things get re-sequenced. Honest trade-offs replace optimistic parallelism. This is the entire point. The written roadmap isn't a contract — it's a forcing function that surfaces the trade-offs you were already making implicitly, and lets you make them out loud.
What we'd push back on is the idea that a roadmap needs to be a Gantt chart or a polished PDF. The most useful roadmap we've ever seen at a 25-person company was a Google Doc with bullet points under three headings: this quarter, next quarter, sometime. It got reviewed every other Friday. It changed often. It was honest. People could plan against it because everyone was looking at the same document, including the founder.
The cost of the unwritten roadmap shows up as small, repeated friction: a sales hire who doesn't know which product to lead with, an engineer building the third pivot of a feature that keeps getting reprioritized, a marketing campaign that ships two weeks after the thing it was promoting got cut. None of those moments looks like a strategy failure in isolation. Added up across a year, they are the strategy failure.