Main idea

In Jira or any equivalent tool, the separation looks like a filing convenience. In reality it produces two queues driven by different forces: features by the roadmap, defects by urgency, support, customer pressure or a prioritization committee.

Between the two, nobody looks at the whole through the lens of pain and value. Both queues are ranked, neither is compared with the other.

The alternative holds in a single kind of card: a work card, carrying a problem to solve. That problem can come from a software defect, a missing capability, poor design, technical debt — the trade-off stays the same: what pain, what value, what impact, what decision.

Why it matters

The morning daily then serves to decide what matters now, instead of debating for twenty minutes whether the item is a defect, a feature, an improvement or a rework.

More generally: the structure of the tool decides what is comparable. Two queues, two logics, no shared trade-off — and this appears nowhere as a decision, since nobody took it.

The separation by nature of work doesn't stop at defects, moreover: product backlog, technical backlog, bug backlog, support backlog, discovery backlog produce the same effect, multiplied. Yet you don't prioritize categories, you prioritize pains, risks and value — and the subject coming out of support that mobilizes support, data and development fits none of the boxes. The right reasoning isn't "which backlog does this subject go in?" but "which problem are we addressing, and which people do we need?".

Layer added by "The Backlog Is Not a Dumping Ground: It's a Tool for Action" (2026-06-03).

Nuances and limits

The relevant unit is the prioritization space, not the organization: several teams working on distinct scopes can hold several queues or several views without breaking anything. What doesn't hold is fragmentation inside a single space of trade-off.

Some organizations need quality reporting, sometimes contractual. Tags and metrics suffice for that, provided they don't structure the queue itself.

Open questions

• Which constraints — certification, contractual commitment, audit — make a separate queue non-negotiable?