How to prioritise a backlog when every task is marked urgent

TL;DR — If every backlog item is marked urgent, stop using the urgent label as the deciding factor. Put every item through the same short triage table: impact, deadline, effort, dependency, and risk of delay; then rank by a simple score and cut the list into "do now", "next", and "later".\n> Reading time: ~5 min\n\n## Goal\nWhen you finish, you will have one ranked backlog with the top items clearly selected for the next delivery window, each item will have an owner and target date, and stakeholders will be able to see why lower items are not being worked on yet.\n\n## Prerequisites\n- Access to your work tracker (the tool where your backlog lives), with permission to edit items, fields, and labels; examples include Jira, Azure DevOps, Trello, Linear, or a spreadsheet\n- A list of all current backlog items in one place; if your work is split across tools, export or copy them into one sheet first\n- 30-60 minutes with one decision-maker who can approve trade-offs; this is usually the product owner, project sponsor, or delivery lead\n- The following fields available on each item, either in your tracker or in a spreadsheet: Title, Owner, Deadline, Business impact, Effort, Dependency, Risk of delay, Status\n- A spreadsheet app if your tracker cannot sort by custom values; any current version of Excel, Google Sheets, or LibreOffice Calc is fine\n\n## Steps\n\n### Step 1: Freeze new "urgent" labels for one review session\nIn your tracker, stop re-labelling items during this exercise. If your tool supports comments, add this exact comment to the backlog board or sprint planning note:\n\ntext\nUrgent labels are paused for this review. We will prioritise all open items using impact, deadline, effort, dependency, and risk of delay, then publish a ranked list today.\n\n\nIf you use a spreadsheet instead of a tracker, put this exact text in cell A1 of a new sheet named Backlog Triage.\n\nWhat you should see when this succeeds: one visible note that tells everyone the ranking method has changed for this review.\n\n### Step 2: Put every open item into one table\nUse your provider's backlog export option if available; in many tools this is under something like Backlog/Issues → Export. If not, create a sheet with these exact column headers in row 1:\n\ntext\nID | Title | Current Urgent Label | Owner | Deadline | Business Impact | Effort | Dependency | Risk of Delay | Score | Decision\n\n\nIf you are in Google Sheets or Excel, paste those headers into row 1 starting at cell A1. Then copy every open backlog item into one row.\n\nWhat you should see when this succeeds: every open item appears once in a single table, even if it came from different lists before.\n\n### Step 3: Replace vague urgency with fixed values\nFor each item, enter only these allowed values in the five scoring columns:\n\ntext\nBusiness Impact: 3 = revenue/compliance/customer outage, 2 = important user or internal efficiency gain, 1 = nice-to-have\nDeadline: 3 = fixed within 7 days, 2 = fixed within 30 days, 1 = no real date\nEffort: 3 = 1 day or less, 2 = 2-5 days, 1 = more than 5 days\nDependency: 3 = blocks other work, 2 = related but not blocking, 1 = standalone\nRisk of Delay: 3 = cost, breach, or customer loss likely, 2 = noticeable pain, 1 = little consequence\n\n\nIf your tracker supports custom fields, create these exact field names and use the values above. If not, enter the numbers directly in the spreadsheet.\n\nWhat you should see when this succeeds: each item has five numbers and no one is debating what "urgent" means.\n\n### Step 4: Calculate a score for every item\nIn the Score column, use this exact formula:\n\ntext\nScore = Business Impact + Deadline + Effort + Dependency + Risk of Delay\n\n\nIn Google Sheets or Excel, if Business Impact is column F and Risk of Delay is column J, enter this in cell K2 and fill down:\n\nexcel\n=F2+G2+H2+I2+J2\n\n\nThen sort the table by Score from highest to lowest. If two items have the same score, put the earlier deadline first.\n\nWhat you should see when this succeeds: the list is ordered, with the highest-value and most time-sensitive items at the top.\n\n### Step 5: Cut the ranked list into "Now", "Next", and "Later"\nTake the top of the sorted list and assign only as much work as your team can actually finish in the next delivery window. Use this exact decision rule:\n\ntext\nNow = only the top items that fit the team's next 1-2 weeks of capacity\nNext = the next 5-10 items after Now\nLater = everything else\n\n\nIn the Decision column, enter only one of these exact values:\n\ntext\nNow\nNext\nLater\n\n\nIf you do not know team capacity, use this temporary rule: count only items with Effort = 3 as 1 day, Effort = 2 as 3 days, and Effort = 1 as 7 days; stop adding items to Now when you reach the number of team-days available in the next 2 weeks.\n\nWhat you should see when this succeeds: a short, realistic Now list instead of a long list of impossible promises.\n\n### Step 6: Add an owner and target date to every "Now" item\nFor each row marked Now, fill in Owner and Deadline with literal values, for example:\n\ntext\nOwner: Sam Patel\nDeadline: 2026-08-21\n\n\nIf your tracker supports assignees and due dates, update the item directly there. If not, keep the values in the spreadsheet and send the list to the team.\n\nWhat you should see when this succeeds: every item in Now has one named owner and one date.\n\n### Step 7: Publish the ranked list and the rule used\nPost this exact summary in your project channel, ticket, or status update:\n\ntext\nBacklog triage complete. We ranked all open items by Business Impact, Deadline, Effort, Dependency, and Risk of Delay. Only items marked Now will be worked in the next delivery window. Items marked Next and Later remain visible but are not committed yet.\n\n\nAttach the spreadsheet or share the tracker view sorted by Score descending and filtered by Decision.\n\nWhat you should see when this succeeds: stakeholders can see both the order and the reason for the order without asking for a separate explanation.\n\n## Verify it works\nUse these checks to confirm the process is complete end to end:\n\n1. Open your backlog view or spreadsheet and confirm these columns exist and are filled for all open items:\n\ntext\nBusiness Impact | Deadline | Effort | Dependency | Risk of Delay | Score | Decision\n\n\n2. Confirm the list is sorted by Score highest to lowest. The first 3-5 items should all have visible numeric scores.\n\n3. Filter Decision = Now. You should see only a small set of items, not the whole backlog.\n\n4. In the Now view, confirm every item has these fields filled:\n\ntext\nOwner\nDeadline\n\n\n5. Ask one stakeholder to review the top 10 items. If they disagree, they should be able to point to one of the five scoring fields, not just say "this feels urgent". That is the sign the method is working.\n\n## Common pitfalls\n\n### Using "urgent" as both a label and a decision rule\nMistake: keeping the old urgent label and still using it to jump items to the top.\n\nSymptom: items with low impact but loud requests keep displacing higher-value work.\n\nFix: stop sorting by the urgent label and sort only by Score, then by earliest real deadline.\n\n### Letting every stakeholder score their own item\nMistake: asking requesters to assign the final numbers without review.\n\nSymptom: most items end up with all 3s, so the list is tied again.\n\nFix: have one decision-maker approve the five scores in a single review session.\n\n### Filling the "Now" bucket with more work than the team can finish\nMistake: treating Now as "important" instead of "can actually be delivered next".\n\nSymptom: deadlines slip, work starts but does not finish, and the backlog gets noisier next week.\n\nFix: cap Now to the next 1-2 weeks of team capacity and move the rest to Next.\n\n### Leaving owners or dates blank on top items\nMistake: ranking items but not assigning who will do them and by when.\n\nSymptom: the top of the backlog is agreed in theory but no work starts.\n\nFix: add one owner and one target date to every Now item before publishing the list.\n\n### Mixing bugs, features, and chores without a common scoring rule\nMistake: scoring different work types with different hidden rules.\n\nSymptom: people argue that a bug is always more urgent than a feature, or vice versa, without evidence.\n\nFix: score all work types with the same five fields, then use the same sort order for all of them.

---

This article was written by an AI system and published pending human review. Verify anything you intend to act on.