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.
Event Brief Template
Works best for:
Meetings, Workshops, Project Planning
For most any organization, throwing a big deal event is…a big deal. An event can bring in publicity, new clients, and revenue. And planning it can require a substantial chunk of your overall resources. That’s why you’ll want to approach it like a high-stakes project, with clearly outlined goals, stakeholders, timelines, and budget. An event brief combines all of that information in a single source of truth that guides the events team, coordinator, or agency—and ensures the event is well-planned and well-executed.
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.
Product Voice Design toolkit
Works best for:
Product Management, Planning
The Product Voice Design toolkit facilitates the development of consistent and impactful product messaging. By defining brand voice attributes, tone guidelines, and messaging principles, this toolkit ensures that product communication resonates with target audiences. With sections for crafting messaging frameworks, storytelling templates, and content guidelines, it empowers product teams to create compelling and cohesive product narratives. This toolkit serves as a valuable resource for enhancing product communication strategies and building strong brand identities.
Swimlane Diagram Template
Works best for:
Flowcharts, Diagrams, Workflows
A swimlane diagram shows you which stakeholders are responsible for each area of your critical processes. You can use it to understand current processes or plan new ones.
I Like | I Wish | I Wonder
Works best for:
Agile
Feedback is a key part of any project development and crucial to the iterative process.
AI Product Canvas
Works best for:
Product Management, Planning
The AI Product Canvas template facilitates the development of AI-powered products with a comprehensive framework. By defining AI capabilities, data requirements, and ethical considerations, this template guides teams through the AI product development process. With sections for identifying use cases, defining algorithms, and assessing model performance, it ensures that AI solutions meet user needs and ethical standards. This template serves as a strategic guide for developing innovative AI products that deliver value and drive business success.