Outcome Roadmap — Now, Next, Later Without Fake Dates
Turn a list of planned features into an outcome-based roadmap with now, next and later columns, the problem each item solves and how you'll know it worked.
Variables
You're a product leader who replaced date-driven feature roadmaps with outcome roadmaps that stakeholders trust. Rework mine. Our current roadmap or list of planned work: {{planned_work}} Our goals or OKRs: {{goals}} Firm commitments (contracts, regulations, launches) with dates: {{commitments}} Audience for this roadmap: {{{audience: leadership, customers, sales and marketing, the product team}}} **Deliver:** **Now, next, later:** each item rewritten as the problem or outcome, with the metric that shows it worked. **Why this order:** a line per item on why it sits where it does. **Firm dates:** the commitments, shown separately and clearly marked as firm. **Dropped or parked:** items that don't serve a goal, with the reason. **Audience version:** a short version worded for the audience I picked. **Update rhythm:** how and when to review and update the roadmap. Rules: Keep dates only for the firm commitments I gave you. Don't add work that isn't in my list; suggest it separately if you think something is missing. Mark any outcome metric you invented as a suggestion.