8 Different Ways to Organize Your Backlog
Often we don’t question our product backlogs, they’re a list of stuff we hope, might and would like to do, but do they always have to be represented as a list?
The 8 Different Ways to Organize Your Backlog
1. User Story Map
Backlog as a User Story MapUser Story Maps are a great way to quickly build out your backlog for the first time, it’s also a powerful tool for release planning.
For more mature products I’ve often split my user story map by customer archetype, JTBD, objectives and even problem spaces, depending on what makes the most sense.
2. Idea Funnel Backlog
Idea Funnel Backlog feeding into a Kanban board.
Literally a funnel! A great way to visualise your backlog and to actually physically restrict the number of product backlog items that are at the “top” (well “right”) of the backlog.
This form of backlog is great to help with prioritisation and focus whilst also keeping things fluid without too much overhead or formal structure.
3. Opportunity Backlog
Splitting your backlog into two — Opportunity backlog for discovery and Development for delivery.
All the ideas, problem spaces, and opportunities are thrown in here, if validated as a good idea they graduate to the delivery backlog.
And eventually the learning will lead to more opportunities and thus making its way back into the Opportunity backlog and that’s the circle of Product Development!
4. Classes of Work Backlog
Divide your backlog into multiple smaller backlogs based on different classes of work.
What often happens is that in order to keep track of everything product managers go labeling-crazy. When you think about it what they are actually doing is dividing their backlog into multiple smaller backlogs based on different classes of work.
One simple thing to do is to literally separate them. Most tools will allow you to achieve this using different views and filters whilst keeping the integrity of a single view for things like your sprints.
5. Tree Backlog
Tree backlogs are great for complex products with many different feature sets.
Technology Trees are great for complex products with many different types of features. Representing your backlog in this manner is a great way to visually show how different features inter-relate and how certain functionality can start out simple and incrementally be enhanced.
6. Impact Map Backlog
Impact maps are great for ideating many alternative paths towards a particular outcome.
Impact mapping works in a similar way to the Tree Backlog in the sense that it branches out. However, unlike the Tree each stage in the branch is not another backlog item rather it represents a stage in the impact map moving from the WHY > WHO > WHAT > HOW.
Representing your backlog this way is great for keeping everything outcome orientated. However impact mapping backlogs aren’t great at representing other classes of work such as technical debt, bug fixes, etc.
7. Circle Backlog
Circle backlogs are perfect for creating ‘slices’ to categorise your work whilst still maintaining a holistic view in one place.
There’s just something about breaking the mould — or perhaps it has to do with the lack of corners — that brings the creativity out in people.
You can even get creative and have different slice sizes, a great way to physically restrict WIP!And much like the Funnel Backlog they also can act as a roadmap + backlog in one.
8. Conversion Funnel Backlog
Conversion Funnel backlogs are great for early and growth stage products with clear conversions.
It brings two important pieces of information together, the quantitative data around drop-offs/potential pain-points in your funnel but also the backlog items/opportunity areas.
If there is a clear drop off at a particular point then everything within that section of the backlog is now your top priority. You get laser-focus, and you keep focusing on that section of the backlog until the numbers improve or if you get another compelling reason to focus on something else.
This template was created by Ant Murphy.
Get started with this template right now.
SAFe Roam Board
Works best for:
Agile Methodology, Operations, Agile Workflows
A SAFe ROAM Board is a framework for making risks visible. It gives you and your team a shared space to notice and highlight risks, so they don’t get ignored. The ROAM Board helps everyone consider the likelihood and impact of risks, and decide which risks are low priority versus high priority. The underlying principles of SAFe (Scaled Agile Framework) are: drive cost-effective solutions, apply systems thinking, assume that things will change, build incrementally, base milestones on evaluating working systems, and visualize and limit works in progress.
B2B – Product Journey Map & User Network
Works best for:
Planning, Product Management
The B2B Product Journey Map & User Network template helps product teams visualize and understand the complex journey of B2B customers. By mapping user interactions, pain points, and touchpoints across the buyer's journey, this template provides insights into user behavior and preferences. With sections for analyzing user needs, identifying opportunities, and optimizing user experiences, it enables teams to design tailored solutions and drive customer satisfaction. This template serves as a strategic tool for enhancing B2B product offerings and maximizing customer value.
Roadmap Planning Template
Works best for:
Roadmap, Agile
The Roadmap Planning Template in Miro is a dynamic tool designed to streamline the process of planning and tracking project milestones. This template is part of Miro's Intelligent Templates offering, which integrates AI, interactive widgets, and automation to enhance productivity. One key feature of this template is its real-time collaboration capability, allowing team members to work together seamlessly, regardless of their location. This feature ensures that everyone is on the same page, making it easier to assign tasks, set deadlines, and track progress effectively.
Scrum Puzzle Iteration Game
Works best for:
Agile, Games, Icebreaker
The Scrum Puzzle Iteration Game is a hands-on activity that reinforces Scrum principles and practices. By simulating iterative development cycles through puzzle-solving, teams learn the importance of collaboration, adaptability, and continuous improvement. This template provides a fun and engaging way to internalize Scrum concepts and enhance teamwork, empowering Agile practitioners to deliver value more effectively.
Opportunity Canvas Template
Works best for:
Leadership, Decision Making, Strategic Planning
Features and capabilities — they make or break a product, which is why companies spend so much time and effort focusing on them. Sound like you? Try it with an Opportunity Canvas. This streamlined one-pager gives you and your team the power to improve your product by exploring the use cases, potential setbacks, strategies, challenges, and metrics. An Opportunity Canvas is ideal if you’ve already built a product, because you don’t need to consider the operational or revenue model.
Timeline Design
Works best for:
Timeline, Planning
The Timeline Design template is perfect for creating visually engaging timelines. It helps you showcase project milestones, deadlines, and important events in a clear and attractive format. Ideal for presentations and reports, this template ensures your timeline is both informative and visually appealing.