Prioritisation SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as prioritisation/SKILL.md.

---
name: prioritisation
description: "Choose what matters now: goals first, then the right method (top three, Eisenhower matrix, impact and effort, MoSCoW, weighted scoring, 1-3-5), hard constraints, a capacity check against real free hours, a not-now list with draft messages and short lists for today and this week. Use whenever someone has too much to do, conflicting priorities, needs to explain trade-offs to a manager, wants to cut a backlog, or asks what to work on today or this week."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/prioritisation/
  category: productivity
  subcategory: planning-tasks
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-12"
---

# Prioritisation

A long to-do list does not tell anyone what to do next. Without a clear way to choose, people default to whatever is loudest: the latest message, the easiest task, or the person who asked most recently. Important work that is never urgent, such as planning, learning or building, waits for a quiet week that never comes.

This skill helps a person or team choose what matters now. It clarifies goals and constraints, applies a method that fits the decision (Eisenhower matrix, impact and effort, MoSCoW, a weighted score or a simple top-three rule), protects important but not urgent work, says what will not be done, and turns choices into a short list for today and this week.

## Operating principles
1. **Priorities come from goals.** Without knowing what success looks like this week or quarter, ranking is guesswork.
2. **Few priorities.** Three for a day and three to five for a week; more than that means none.
3. **Choose what not to do.** Every yes needs a no, a later or a delegate.
4. **Make trade-offs visible.** Show why something ranks above something else.
5. **Revisit, do not reshuffle.** Re-rank at set times, not every time a message arrives.

## Methods and when to use them
| Method | Use for | How |
|---|---|---|
| Top three | Daily focus | Pick the three tasks that would make the day a success |
| Eisenhower matrix | Sorting a mixed list | Urgent and important: do; important not urgent: schedule; urgent not important: delegate or batch; neither: drop |
| Impact and effort | Projects and ideas | Score impact and effort 1 to 5; do high-impact, low-effort first; plan high-impact, high-effort |
| MoSCoW | Scope for a deadline | Must, should, could, won't |
| Weighted scoring | Comparing options with several criteria | Score each option against weighted criteria such as goal fit, impact, effort, risk |
| 1-3-5 rule | A realistic day | One big task, three medium, five small |

## When to use, and when not to
Use it when there is too much to do, priorities conflict, a manager asks for a rationale, a new quarter or week starts, or a backlog needs cutting.

Don't use it to capture tasks (`task-capture-clarify`) or schedule them (`time-blocking`). For product roadmap prioritisation, use the Product Management category.

## Inputs
- The task or project list.
- Goals for the week, quarter or role.
- Deadlines, dependencies and commitments to others.
- Available time this week (after meetings) and energy constraints.
- Who else can do which tasks.

## Workflow

### Step 1. Confirm the goals
The two or three outcomes that matter most this period. If missing, ask, or draft them for confirmation.

### Step 2. Clean the list
Merge duplicates, rewrite vague items as next actions and remove anything already done.

### Step 3. Mark hard constraints
Real deadlines, commitments to others, legal or financial obligations and dependencies blocking other people.

### Step 4. Apply the right method
Eisenhower for a mixed list, impact and effort for projects, MoSCoW for a deadline, weighted scoring for big choices.

### Step 5. Check capacity
Compare the chosen work with the hours actually free after meetings, with buffer for interruptions. If it does not fit, cut or move items.

### Step 6. Decide what not to do
List items to delegate, defer with a date, or drop, and draft messages to anyone affected.

### Step 7. Produce the short list
Today's top three and this week's three to five priorities, each linked to a goal.

## Weighted scoring template
```
| Option | Goal fit (40%) | Impact (30%) | Effort, inverted (20%) | Risk, inverted (10%) | Total |
| Launch email series | 5 | 4 | 3 | 4 | 4.2 |
| Redesign dashboard | 3 | 3 | 2 | 3 | 2.8 |
```

## Capacity check
```
Available hours this week: 40
Meetings: -14 | Admin and email: -6 | Buffer (20%): -4
Hours for priorities: 16
Planned priority work: 22 -> cut or move 6 hours
```

## Saying no or later
| Situation | Message idea |
|---|---|
| Manager adds work | "Happy to take this on. To fit it in, X moves to next week. Does that work, or should Y wait instead?" |
| Colleague request | "I can't get to this before Thursday. If it's urgent, Sam may be able to help sooner." |
| Meeting invite with no agenda | "Could you share the goal? If it's an update, I can read the notes instead." |
| Nice-to-have idea | "Good idea. I've added it to the list for next month's planning." |
The agent drafts these so declining takes seconds rather than turning into a long thread.

## Urgent versus important
Urgent work demands attention now; important work moves goals forward. Most stress comes from urgent but unimportant tasks crowding out important ones. Protect important, non-urgent work by scheduling it first, then fit urgent requests around it, and batch small urgent items together.

## Priorities for teams
For a small team, agree the week's top three outcomes on Monday, show each person's capacity, and name one owner per outcome. Requests that arrive mid-week are compared against the three; if they win, something visible moves out, and everyone sees the trade-off.

## Estimating effort
Use rough sizes such as small (under an hour), medium (half a day) and large (several days) rather than precise hours. Add a buffer of around 20 to 30% to allow for interruptions and the common habit of underestimating. Break any large item into smaller next actions before ranking it, because large vague items are easy to postpone.

## When priorities change
New information, such as a client escalation or a changed deadline, can reorder the week. When it does, re-run the capacity check, move one item out explicitly, and tell anyone affected. Change by decision, not by drift.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Everything is "urgent" | Ask what happens if each waits a week; real urgency survives the question |
| Two managers with conflicting asks | Show both priorities and the capacity gap; ask them to decide together |
| Important work never gets done | Schedule it first, as a fixed block, before urgent requests |
| Too many small tasks | Batch them into one daily or weekly slot |
| Low energy or unwell | Pick one essential task; move the rest |

## Handoffs to related skills
- Clean list first: `task-capture-clarify`
- Scheduling the choices: `time-blocking`, `daily-planning`
- Goals that drive priorities: `goal-setting-okrs`
- Breaking big priorities into steps: `project-breakdown`
- Weekly re-ranking: `weekly-review`

## Worked example
A product marketer has 34 open tasks, a launch in three weeks and two managers asking for different reports. After confirming the quarter's goal (launch on time with sales trained), the agent cleans the list to 26 actions, applies the Eisenhower matrix, checks capacity (16 free hours against 25 planned) and recommends three weekly priorities: finish the launch messaging, run sales training, and deliver one of the two reports. It drafts a note to both managers showing the trade-off and asking them to pick which report can wait a week. Six small tasks are batched into Friday afternoon.

## Output format
```
1. Goals this period
2. Method used and why
3. Ranked list with reasons
4. Capacity check
5. Today's top three and this week's priorities
6. Not now: delegate, defer (with dates) or drop, plus draft messages
```

## Common mistakes
- Ranking without goals.
- Ten priorities a day.
- Ignoring meetings when estimating capacity.
- Never saying no or later.
- Re-ranking every hour.

## Self-check before you answer
- Is each priority linked to a goal?
- Does the plan fit the real hours available?
- Is there a clear not-now list?
- Are trade-offs explained?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/prioritisation/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.