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.
4Ps Retrospective
The 4Ps Retrospective template offers a structured framework for teams to reflect on past iterations or projects using the 4Ps model (Praise, Problems, Possibilities, and Plans). It provides elements for sharing positive feedback, identifying challenges, exploring opportunities, and setting action plans. This template enables teams to conduct retrospectives systematically, generate actionable insights, and drive continuous improvement. By promoting a balanced and comprehensive approach, the 4Ps Retrospective empowers teams to enhance collaboration, boost morale, and achieve their objectives effectively.
Value Chain Analysis Template
Works best for:
Leadership, Strategic Planning, Workflows
First coined by Harvard Business School professor Michael Porter, the value chain analysis helps your team evaluate your business activities so you can find ways to improve your competitive advantage. A value chain is a set of activities that a company performs in order to deliver a valuable product from start to finish. The analysis itself allows your team to visualize all the business activities involved in creating the product—and helps you identify inefficiencies, bottlenecks, and miscommunication within the process.
Competitor Product Research
Works best for:
Product Management, Planning
The Competitor Product Research template assists product teams in analyzing competitor offerings and market landscapes effectively. By identifying competitor strengths, weaknesses, and market trends, this template enables teams to uncover insights and opportunities for differentiation. With sections for conducting feature comparisons, SWOT analysis, and market positioning assessments, it facilitates informed decision-making and strategic planning. This template serves as a valuable resource for gaining competitive intelligence and driving product innovation and differentiation.
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.
Brand Guidelines Template
Works best for:
Design, Marketing, Documentation
What makes a strong brand? It’s having a well-defined personality, expressed with consistency at every touchpoint, and brand guidelines can help you do it. Brand guidelines are a clear list of rules—all the dos and don’ts—that cover details like colors, fonts, logo usage, photography, and brand voice. They help ensure that employees across a whole company or organization know how to display or speak about the brand. Miro’s whiteboard tool is the perfect canvas for creating brand guidelines, sharing them, and updating them.
OODA Loop Template
Works best for:
Strategic Planning, Strategy
The OODA Loop template helps optimize decision-making processes by using four key stages- Observe, Orient, Decide, and Act. Its well-structured layout allows teams to systematically break down complex decisions, leading to a shared understanding of the decision-making workflow. One of the key benefits of the template is its ability to enhance collaboration. Teams can seamlessly contribute to and iterate upon the decision-making cycle in real time, resulting in more informed decisions and a more efficient process. The template provides a clear and visual representation of each stage, accelerating the decision-making process and fostering a collaborative environment where teams can work together to navigate challenges and make well-informed decisions.