Agile Product Roadmap (Now, Next, Later)
This is a Themes-based Product Roadmap in a modified "Now, Next, Later" form made to assist teams who transform to a Product Operating Model to build Outcomes-based High integrity Product Roadmaps because it is so different from what those teams are used to see and use as Product Roadmaps.
This Roadmap has prefixes "probably", "maybe" in addition to "Never", "Next", "Later" to emphasize its agility nature: if something is on Agile Roadmap it doesn't mean that it will be eventually delivered to the customers. It's absolutely not!
How to use Agile Product Roadmap
Start with the "Now" section. Add some Themes (hard, real customers/users/company problems that your team is working this quarter/month) sticky notes to a "To Do" section of "Now." Themes must be based on (i.e., exist there because of, prioritized, and split among the existing teams) a Product Strategy created by Product Leaders. "Now, Next, Later" sections represent Product Strategy prioritization. The "Now" section split by Product Teams represents teams topology. Example of Theme: "Signup completion rate is about 20%, which is too low."
Move some of Themes from "Now" to "Next" and "Later" sections to init Product Roadmap prioritization (or simply create new Themes in those sections).
Change Themes in a "To Do" list of "Now" section to OKR's (Objectives & Key Results). Example of OKR: "Increase signup completion rate from 20% to 50%."
Move sticky notes from "To Do" to "Discovery / Delivery" and then to "Delivered" or to "Next" or to "Later" or even to "Never". Working in a Product Operating Model, we do Product Discovery and Product Delivery. It may happen that the team discovers that it is very expensive for a company to solve this problem. And that's why this problem (an OKR) will get to "Never" instead of "Delivered."
Use "Delivered" section to keep sticky notes there when you start a new quarter/month - so you can see what you've recently done. This helps to change and track the course of the Product Strategy.
Keep items in the "Never" section. Once a sticky note gets to a "Never" section we need some document that explains the story behind that sticky note: what was Discovered that lead to a conclusion that our company Product Leaders (along with the Product Teams) decided not to deliver a solution to that problem (at least for now).
This template was created by Aleksei Soskov.
Get started with this template right now.
Salesforce Implementation Plan
Works best for:
Roadmap, Planning, Mapping
The Salesforce Implementation Plan template offers a structured framework for planning and executing Salesforce deployment projects. By outlining key milestones, tasks, and dependencies, teams can ensure a smooth transition to the Salesforce platform. This template facilitates collaboration between IT and business teams, ensuring that implementation efforts are aligned with strategic objectives and deliver value to stakeholders.
Product Management - Product Flow
Works best for:
Product Management, Planning
Product Management - Product Flow template enables product managers to visualize and streamline product development processes. By mapping out key stages, tasks, and dependencies, this template enhances workflow transparency and coordination. With features for identifying bottlenecks and optimizing resource allocation, it empowers teams to improve efficiency and accelerate product delivery. This template serves as a valuable tool for ensuring smooth product development and launch processes, ultimately driving better outcomes.
Official 5-Day Design Sprint
Works best for:
Design, Desk Research, Sprint Planning
The goal of a Design Sprint is to build and test a prototype in just five days. You'll take a small team, clear the schedule for a week, and rapidly progress from problem to tested solution using a proven step-by-step checklist. Steph Cruchon of Design Sprint created this template for Miro in collaboration with design sprint gurus at Google. This Design Sprint template is designed specifically for remote sprints so you can run productive and efficient sprints with colleagues around the world.
Product Ownership Evolution Model (POEM)
Works best for:
Product Management, Planning
The Product Ownership Evolution Model (POEM) template guides product teams through the evolution of product ownership roles and responsibilities. By illustrating the transition from individual ownership to shared ownership, this template fosters collaboration and accountability. With sections for defining roles, establishing workflows, and setting expectations, it facilitates smooth transitions and enhances team effectiveness. This template serves as a roadmap for optimizing product ownership practices and driving continuous improvement.
5Gs Retrospective
Works best for:
Agile Methodology, Retrospectives, Meetings
The 5Gs Retrospective template offers a structured approach for teams to reflect on their projects or iterations, focusing on five key aspects: Goals, Gains, Gratitude, Gaps, and Growth. It provides elements for identifying achievements, expressing gratitude, and addressing areas for improvement. This template enables teams to conduct retrospectives systematically, fostering a culture of learning, appreciation, and continuous improvement. By emphasizing the five dimensions of reflection, the 5Gs Retrospective empowers teams to optimize their performance, enhance collaboration, and achieve their goals effectively.
The Product Storyboard
Works best for:
Product Management, Planning
The Product Storyboard template enables product managers to visualize product experiences and user journeys. By mapping out key touchpoints, interactions, and scenarios, this template helps teams understand user needs and pain points. With sections for defining user personas, storyboarding user flows, and capturing feedback, it supports iterative product design and validation. This template serves as a storytelling tool for communicating product visions and guiding product development efforts towards delivering exceptional user experiences.