The priority problem is rarely that nobody knows what matters. It is that several things appear important at the same time, each backed by a loud stakeholder. A useful framework goes beyond “urgent” and “high.” It forces a comparison of impact, timing, cost of delay, and actual capacity.
Four questions before assigning priority
- What outcome changes if we complete this task?
- Is there a real external deadline or only an internal sense of urgency?
- What is the cost of delaying it by one week?
- Is the task ready, or is it waiting for a decision or input?
A task can have high impact but still be unready, while a smaller task may unlock it. Priority is therefore not a permanent property. It is a decision shaped by context and time.
A lightweight model: impact × time sensitivity ÷ effort
Score impact, time sensitivity, and effort from 1 to 3. Divide impact multiplied by time sensitivity by effort. Do not treat the result as precise mathematics. Use it to expose differences in assumptions. If one person scores impact as 3 and another scores it as 1, that disagreement is the conversation worth having.
| Task | Impact | Time | Effort | Decision |
|---|---|---|---|---|
| Fix a defect blocking delivery | 3 | 3 | 1 | Do now |
| Prepare a recurring report | 2 | 2 | 2 | Schedule clearly |
| Reformat an internal file | 1 | 1 | 2 | Delay or remove |
Use only four priority levels
- Urgent: blocks work or is tied to an immovable commitment.
- High: materially advances an important outcome this week.
- Medium: necessary, but timing is flexible.
- Low: a useful improvement or an idea whose value is not yet proven.
Treat an urgent request as a trade-off
Do not ask only whether to do it. Ask what will stop in return. When urgent work enters the active queue, remove something else or change its date visibly. Fast response then becomes an explicit choice rather than silent accumulation and broken trust.
Review priorities on a stable cadence
Priority should change when information changes, but not with every message. Reserve a short daily window for genuine urgency and a weekly review for everything else. This protects focus and prevents the latest message from becoming the team’s strategy.
Real priority is visible in what you stop, not what you call important.
Representing the decision in your tool
Set the priority level on the task, but explain the reason in its description or discussion. Use due dates for real commitments—not as a way to paint every item red. Taskelo keeps priority, date, owner, and stage visible together, making work easier to compare than a disconnected list of task names.
A decision example: the biggest client or the nearest deadline?
A services team has three requests: a cosmetic change from a large client, a file another team needs to deliver tomorrow, and an experiment that might attract future customers. Client size alone makes the first request look most important. Asking about the cost of delay reveals that the second blocks an existing commitment, while the cosmetic change may be scheduled by agreement. This is an illustrative scenario; the decision changes if the change is contractual or fixes something preventing use.
Do not manufacture scores to justify a decision already made. State an assumption for each request: what is lost if it waits one day, who is blocked, and whether the date is genuinely fixed. Choose an order and check the assumptions with the people who have the information. When a critical fact is missing, the next action may be a clarification call rather than implementation.
Separate priority from execution order
The highest-impact task may not be ready because an essential input is missing. It remains important, but pretending to work on it adds no value. Create an action to remove the blocker, then select ready work that will not prevent returning to the main commitment. Do not let easy tasks become a permanent escape from difficult work: specify when the blocker will be reviewed and who decides if it persists.
| Request | Unhelpful response | Decision-oriented response |
|---|---|---|
| I need it today | We will try | Is there an external commitment today? What changes if it arrives tomorrow? |
| Everything matters | We will do it all | We can finish one outcome now; which delay causes less harm? |
| Add this change | It should be quick | Does this replace scope or change the delivery date? |
Agree how priorities can change
Name the person who resolves conflicts, decide when to review the queue, and define the situations that justify interrupting active work. Record the reason for an escalation on the task. During the weekly review, look at requests that became urgent and then quietly disappeared. Expectations may be unclear, or urgency may have become a way to secure attention rather than a description of consequence.
Turn the resulting order into realistic commitments with the weekly planning system.
Turn clarity into a way of working.
Start with one project, bring the team’s tasks together, and see progress on a clear board.
