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.
Corrective Action Plan Template
Works best for:
Project Management, Operations, Strategic Planning
For a manager or HR leader, it’s the least fun part of the job: Documenting an employee’s performance issues and talking about them directly to that employee. A corrective action plan makes that tough task a little easier by putting issues into a professional, written framework. That way the process, next steps, and details of the conversations are all clearly documented. This template will enable you to eliminate murky communication, align on expectations, and provide step-by-step instructions for your employee.
Timelining
Works best for:
Planning, Timeline
Timelining is a versatile template designed for creating detailed project timelines. It allows you to outline tasks, milestones, and deadlines, helping you manage projects efficiently. Whether for business or personal use, this template ensures you stay organized and on schedule.
Features Audit Template
Works best for:
Desk Research, Product Management, User Experience
Add new features or improve existing features—those are the two paths toward improving a product. But which should you take? A features audit will help you decide. This easy, powerful product management tool will give you a way to examine all of your features, then gather research and have detailed discussions about the ones that simply aren’t working. Then you can decide if you should increase those features’ visibility or the frequency with which it’s used—or if you should remove it altogether.
5W1H Template
Works best for:
Strategy & Planning
The 5W1H Template is a strategic framework that clarifies complex situations or projects into six foundational questions: What, Who, Where, When, How, and Why. This methodological approach ensures a comprehensive understanding, encouraging teams to dissect and explore every aspect of a given challenge or project.
PDCA Template
Works best for:
Planning
The PDCA template provides a visually compelling representation of the Plan-Do-Check-Act cycle, a foundational management methodology. Structured around four primary segments, this template helps teams systematically address challenges, test solutions, assess outcomes, and make necessary refinements. Using the PDCA template fosters continuous improvement. By cycling through each phase repeatedly, organizations can perpetually refine their strategies, ensuring they always move towards optimal solutions and processes.
Product Vision
Works best for:
Product Management, Planning
The Product Vision template helps articulate a clear and compelling vision for product development. By defining goals, target markets, and success metrics, this template aligns teams around a shared vision. With sections for outlining product features, benefits, and competitive advantages, it communicates the value proposition effectively. This template serves as a guiding light for product teams, inspiring creativity and focus as they work towards bringing the product vision to life and achieving business objectives.