A quarterly roadmap lays a team's planned work across the four quarters of a year, so everyone can see what ships when and why. This template is a Q1 to Q4 grid with team swimlanes, strategic theme rows, and initiative cards you can link to briefs and wireframes. Product and ops teams use it to align on priorities and report timing to stakeholders, without rebuilding a slide deck every quarter.
A quarterly roadmap places initiatives in calendar time, Q1 through Q4, so teams commit to timing and coordinate across squads. A now-next-later roadmap leaves dates off and sorts work into three horizons by priority, which keeps plans flexible when timelines are genuinely uncertain. Choose a quarterly roadmap when leadership needs confidence on when things ship and multiple teams have to sync. Choose now-next-later when scope is still moving.
Lead with themes, then hang initiatives under them. Themes like Growth, Retention, and Platform connect the work to company goals and stay stable even when individual features change. Listing only features turns the roadmap into a backlog in disguise, and it ages fast. A good quarterly roadmap shows a few themes per quarter, each with the initiatives that serve it.
Move the card. A quarterly roadmap is meant to flex: when a priority shifts, drag the initiative to a new quarter or swimlane and note why. Treat the board as a living plan, not a contract. Re-share it so stakeholders see the change, and capture the reasoning so the team remembers the trade-off later.
A quarterly roadmap sets direction for the next few months; sprint planning turns the current slice of it into two-week chunks. The roadmap says 'this quarter we focus on onboarding'; sprint planning breaks that into specific stories. The roadmap feeds the sprints, and what the team learns each sprint feeds back into the next quarter's plan.
A quarterly roadmap places initiatives in calendar time, Q1 through Q4, so teams commit to timing and coordinate. A now-next-later roadmap drops dates and sorts work into three horizons by priority, which keeps things flexible when timelines are uncertain. Pick quarterly when several teams must sync on dates; pick now-next-later when scope is still moving.
Keep it to a few per team, per quarter, usually three to five. A quarterly roadmap is a planning and communication tool, not an exhaustive task list, so it should fit on one screen and stay readable. If a quarter is crammed with a dozen initiatives, that's a sign to cut scope or push some work to a later quarter.