The competitor you copied into irrelevance
Every product meeting opened with what the leader shipped. Two years later you were a cheaper version of them, and buyers said so out loud.
Roadmap-by-competitor is the most confident way to build a second-place product. It starts small. Every product meeting opens with the same agenda item: what did the leader ship this week? Their changelog sits open on a second monitor. At one company, within 2 quarters, every release the team shipped was a slightly late, slightly different version of a release the leader shipped first. The team calls this staying competitive.
By the third year, the company was a worse version of the leader, and buyers said so out loud. Deal after deal, they described it the same way: like the leader, but cheaper, or smaller, or not quite as polished. Positioning had collapsed into a comparison. Every win needed a discount. Every loss was a loss to the leader. Two years had gone into becoming the second-best version of someone else.
Roadmap-by-competitor is one of the most destructive product strategies a company can run, and it's the default response to a faster-moving rival. The changelog is visible and concrete. You can point at it in a meeting. If we don't ship this, we'll lose deals. The argument is internally coherent and almost always wrong. The deals aren't lost on the missing feature. They're lost on positioning. By chasing the roadmap, the company signals that the leader is the real product and it's the budget alternative. Once that signal sets, no amount of feature-matching reverses it.
The deeper problem: a competitor's changelog is the worst product research input available. The features they ship are the features they've already sold their buyers on. Those buyers aren't yours, by definition. Your buyers are the ones who didn't buy the leader, for reasons the changelog can't show. Building against the changelog means building for people who already have a vendor, and ignoring the people who don't.
The differentiation that wins isn't in the feature set. It's in the wedge. Five customers who tried the leader and left, or never picked it, will tell you exactly what's missing. Sometimes what they wanted wasn't a feature at all. Their reasons are a buyer pattern the leader can't serve without alienating its own base. Build toward those reasons and you get a product that's recognizably different in ways a specific segment cares about. That segment becomes your home market, and it's yours because you're competing on something other than price.
This is harder than copying. Copying hands you a clear roadmap the team can execute today. Wedge-building needs customer research, hypothesis-testing, and the nerve to ship features the competitor doesn't have and may never validate. The team feels less certain. The board asks harder questions. That discomfort is exactly why copying seduces. It produces an immediate roadmap nobody questions in the moment.
The cost of that comfort is irrelevance. Two years of copying produces a company the market files under the other one, and the other one is the last slot any company wants. So stop opening the competitor's changelog in product meetings. Start opening the interview transcripts from buyers who chose someone else. The changelog tells you what the leader already won. The transcripts tell you what's still open. Only one of those is your strategy.