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.
About Agile Product Roadmap (Now, Next, Later) template
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).
Get started with this template right now.
Product Reflection
Works best for:
Product Management, Planning
The Product Reflection template encourages teams to reflect on past experiences and lessons learned in product development journeys. By facilitating retrospective sessions, capturing insights, and identifying improvement opportunities, this template fosters a culture of continuous learning and improvement. With sections for evaluating successes, challenges, and areas for growth, it enables teams to iterate on their processes and enhance future product development efforts. This template serves as a tool for fostering team collaboration and driving iterative product innovation.
Product Discovery Kick Off Workshop
Works best for:
Product Managament, Planning
The Product Discovery Kick Off Workshop template accelerates the start of product discovery initiatives. By facilitating collaborative workshops, defining objectives, and establishing timelines, this template ensures that product discovery efforts are structured and focused. With sections for defining user personas, articulating problem statements, and setting success criteria, it guides teams through the initial stages of product discovery, laying the foundation for successful product development. This template serves as a catalyst for aligning teams and kick-starting product innovation journeys.
Product Strategy Canvas
Works best for:
Product Management, Planning
The Product Strategy Canvas template aids product managers in defining strategic direction and priorities. By outlining key components, such as target markets, value propositions, and differentiation strategies, this template clarifies product vision and positioning. With sections for analyzing market trends and competitive landscapes, it facilitates informed decision-making in product strategy development. This template serves as a strategic blueprint for driving product success and achieving business objectives.
Technology Roadmap Template
Works best for:
Agile Methodology, Roadmaps, Agile Workflows
A technology roadmap helps teams document the rationale of when, why, how, and what tech-related solutions can help the company move forward. Also known as IT roadmaps, technology roadmaps show teams what technology is available to them, focusing on to-be-scheduled improvements. They allow you to identify gaps or overlap between phased-out tech tools, as well as software or programs soon to be installed. From a practical point of view, the roadmap should also outline what kinds of tools are best to spend money on, and the most effective way to introduce new systems and processes.
IASA - Product Roadmap Canvas
Works best for:
Roadmap, Mapping, Planning
The IASA - Product Roadmap Canvas template offers a holistic view of product development by integrating key elements such as customer needs, business goals, and technology requirements. By utilizing this canvas, teams can align their product strategy with market demands and ensure that development efforts are focused on delivering maximum value to customers.
The Product HQ— your product's source of truth.
Works best for:
Product Management, Planning
An HQ for all your product thinking. A central place for you and your team to articulate and cultivate your point of view with regard to the concept at hand (be it a product, a service or something in between).