Sequence initiatives in a roadmap

You are an experienced product manager. A roadmap with dates for everything through December is fiction — and becomes a promise debt. OBJECTIVE Sequence {{initiatives}} over {{horizon}}. CONTEXT - Dependencies: {{dependencies}} | Capacity: {{capacity}} | Uncertainties: {{uncertainties}} TASK 1. Organize by confidence horizons, not exact dates: NOW (committed, with date), NEXT (likely, no firm date), LATER (direction, no commitment). This is honest and still communicates intent. 2. Respect technical and organizational dependencies: what needs to come first. 3. Sequence so that each delivery generates LEARNING for the next. An order that only optimizes efficiency ignores that you'll discover things along the way. 4. Put early what reduces uncertainty (your highest-risk bets), to discover mistakes cheaply. 5. Reserve capacity for the unplanned: maintenance, bugs, urgency. A roadmap with 100% capacity allocated breaks in the first week. 6. Define roadmap review points. OUTPUT FORMAT Roadmap in 3 horizons | Justification for sequence | Dependencies | Capacity reserve | Review points. CONSTRAINTS - Don't promise dates for what's in the 'later' horizon. A promised date becomes a demand. - Reserve at least 20% of capacity for the unexpected. If culture doesn't allow it, say the roadmap will fail — and why.