8 DIFFERENT WAYS

TO ORGANIZE YOUR
PRODUCT BACKLOG
with templates

antmurphy.me
 #1 User Story Map

User 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.
antmurphy.me
#2 Idea Funnel Backlog

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.

antmurphy.me
#3 Opportunity Backlog

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!
antmurphy.me
 #4 Classes of Work

Divide your backlog into multiple smaller backlogs based on

different classes of work.

Often, in order to keep track of everything product managers

go labeling-crazy. When you think about it what you're
actually doing is dividing your backlog into multiple smaller
backlogs based on different classes of work.

One simple thing to do is to literally separate them. This helps

remove the noise and make things more manageable.
antmurphy.me
 #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.
antmurphy.me
 #6 Impact Map

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.
antmurphy.me
 #7 Circle Backlog

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.
antmurphy.me
 #8 Funnel Backlog

Conversion Funnel backlogs are great for early and growth

stage products with clear conversions.

Funnel backlogs bring 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 point then everything within that

section of the backlog is likely a top priority.

antmurphy.me
p.s. You can find templates for all these
backlogs in the miroverse!
 Subscribe to my
newsletter for more
content like this:
antmurphy.me/newsletter

and if video’s are more your thing, subscribe on Youtube:

youtube.com/@productpathways

antmurphy.me