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.
The Lightning Product Audit
Works best for:
Product Management, Planning
The Lightning Product Audit template streamlines product evaluation processes with a comprehensive framework. By assessing key areas such as market fit, user experience, and feature performance, this template enables teams to identify strengths, weaknesses, and areas for improvement swiftly. With sections for conducting SWOT analysis, user feedback review, and competitive benchmarking, it facilitates data-driven decision-making and prioritization. This template serves as a catalyst for refining product strategies and driving continuous improvement.
A3 Report Template
Works best for:
Product, Strategy and Planning
The A3 report template is a carefully designed tool that provides teams with a structured and visual methodology to tackle challenges. It divides the problem-solving process into background, current context, data analysis, and implementation plans, ensuring a comprehensive approach to each issue. One of the major advantages of this template is its "Data Analysis" section, which enables teams to delve deeply into concrete insights and trends. This data-driven approach ensures that all recommendations and actions are based on real, tangible evidence rather than just intuition, leading to more effective and strategic decision-making.
Value Proposition Template
Works best for:
Strategy & Planning, Product Strategy
The Value Proposition Template is a framework that empowers businesses to articulate their offerings' core advantages. By breaking down an offering into its essential elements, this template ensures that stakeholders grasp the unique value a product or service brings to the market.
20/80 Process Diagram - EOS Compatible
Works best for:
Diagramming
The 20/80 Process Diagram - EOS® Compatible template is a visual tool for mapping out processes and workflows aligned with the Entrepreneurial Operating System (EOS®) methodology. It provides a structured framework for identifying core processes and key activities that drive business outcomes. This template enables organizations to streamline operations, clarify roles and responsibilities, and enhance accountability. By promoting alignment with EOS® principles, the 20/80 Process Diagram empowers teams to achieve organizational excellence and drive sustainable growth.
Inspired: Creating Products Customers Love
Works best for:
Product Management, Planning
Inspired: Creating Products Customers Love template guides product managers in developing innovative and customer-centric products. By emphasizing empathy, ideation, and validation, this template fosters a deep understanding of customer needs and preferences. With sections for brainstorming ideas, defining features, and validating concepts, it facilitates the creation of compelling products that resonate with target audiences. This template serves as a roadmap for delivering exceptional customer experiences and driving product success.
Entity–Relationship Diagram (ERD) HR Management System Template
Works best for:
ERD
The Entity–Relationship Diagram (ERD) HR Management System Template in Miro is designed to streamline the management of employee-related information and processes within an organization. This template allows for the visualization and organization of complex HR systems, making it easier to understand relationships and processes. It enables users to map out departments, positions, and employee details, including attendance records, payroll, and performance reviews.