A roadmap is not a list of features or requirements. A roadmap should be strategic. It should be focused on the vision and direction of the product, and the problems we’re solving. It is about the value we’re delivering, not necessarily the features. While it certainly is okay to talk about features on the roadmap, especially the near-term features that we’re confident in committing too, it’s important to caveat specific features with the understanding that the features are meant to solve a problem or achieve an outcome. We aren’t simply delivering a wish-list of features.
“People hate [problem]. Our team exists to create [service that solves problem] and make it accessible to [large group]. We will achieve this by [doing this and this] which makes sense because [rationale]. We will measure success by [metric that matters].”