Features, the Backlog & Prioritisation

Once you can write user stories, you quickly drown in them. Everyone has an idea, every customer has a complaint, and your list of “things we should build” grows faster than any team could ever deliver. This lesson is about the three tools that keep that list from becoming chaos: the feature, the backlog, and prioritisation. Together they answer the only question that really matters — not “what could we build?” but “what should we build next?”

This is the heart of product work: customers have endless needs, and you have limited time. Choosing well, and being able to explain why, is most of the job.

Where work waits and how it gets chosen

A feature is a chunk of capability a customer can point at — “saved payment cards” or “order tracking.” A feature is usually bigger than one story; it’s a small cluster of related stories that together deliver something whole. The backlog is simply the ordered list of everything you might build, with the most important work at the top. Prioritisation is the act of putting things in that order — and re-ordering as you learn.

A feature is a customer-shaped thing

The useful test for a feature is: can a customer name it and care about it? “Order tracking” passes — a shopper would happily tell you they want it. “Refactor the payments service” fails; that’s internal plumbing, valuable but invisible. A feature usually bundles several user stories. Order tracking might include “see where my parcel is,” “get a delivery estimate,” and “be notified when it ships.” Grouping stories into features keeps conversations at a level customers and executives can follow, while the stories underneath stay small enough to build.

The backlog is a queue, not a graveyard

A backlog is the single, ordered list of work the team hasn’t done yet. Two things make a backlog healthy. First, it’s ordered — top items are clear and ready, and the further down you go the fuzzier things can be. Second, it’s honest: ideas that will never realistically be built should be removed, not buried. A backlog where nothing is ever deleted stops being a plan and becomes a place where ideas go to die quietly while still cluttering the view.

A backlog is a list of bets about the future, not a list of promises. Re-ordering it as you learn is the work, not a sign you got it wrong.

Prioritisation: value against effort

Prioritisation is deciding the order, and the most useful starting lens is value versus effort. Value is how much a feature helps customers or the business; effort is how much it costs to build. Plot the two and four groups appear. Quick wins (high value, low effort) should usually go first — they build momentum cheaply. Big bets (high value, high effort) deserve real planning. Time sinks (low value, high effort) are the ones to resist, however shiny. And low-value, low-effort “maybes” can wait until a slow week.

The grid is a conversation tool, not a calculator. Its real power is forcing two honest questions about every idea: how much does this actually help someone, and how big is it really? Most disagreements about priority dissolve once people are arguing about value and effort specifically, rather than about whose idea is best.

Spot it: where does it sit

Read each idea and decide: quick win, big bet, maybe, or time sink? Tap a card to check.

Sort the features

Drag each feature into the quadrant where it belongs on the value-versus-effort grid.

How to use it

When your list of ideas feels overwhelming, group the stories into a handful of features so you’re comparing customer-shaped things, not scattered tasks. Put them all in one backlog so there’s a single source of truth instead of five competing wish-lists in five inboxes. Then prioritise out loud: “This one’s high value and small — quick win, let’s do it. This one’s huge and we’re not sure it pays off — let’s prove the value before we commit.” When a senior stakeholder demands their pet feature jump the queue, you don’t have to say no flatly; you can ask, “Where does it sit on value versus effort against what’s already at the top?” That keeps the decision about the work, not about the loudest voice in the room.