1. Describe your customer-facing product roadmap. Your description should include: a) How customers can access it (e.g., under NDA, public portal); b) The typical time horizon it covers (e.g., 6, 12, 24 months); and c) How you distinguish between different commitment levels (e.g., 'committed,' 'planned,' 'exploratory').
Why it matters. A roadmap with defined commitment levels shows the buyer what the vendor plans to build and how firmly it has committed to each item. Blurring committed deliverables with aspirational ideas, or hiding the roadmap entirely, exposes the buyer to risk from surprise strategic shifts or features that never ship.
- Roadmap is accessible to customers under NDA via a portal or document.
- Clearly defines the time horizon (e.g., 12 months).
- Uses an explicit taxonomy for commitment levels (e.g., 'committed', 'planned', 'exploring').
- No roadmap is shared with customers, even under NDA.
- Roadmap is purely verbal or exists only in marketing materials.
- Refusal to commit to any timeframes.