How would you explain your product roadmap to an engineer who thinks all roadmaps are a waste of time?

Model answerI wouldn't argue for roadmaps — I'd ask what problem they've had with them before. Usually the complaint is that roadmaps are treated as commitments that don't change. I'd reframe: this roadmap is a set of bets, not a promise. Each item represents a hypothesis about what will drive user value. Engineers shape those bets too — their input on effort changes prioritization. The roadmap isn't done to engineers; it's built with them.