Prioritisation
Choosing what gets your attention, and accepting what will not.
The behaviour, in one line: I know each day which task matters most and protect time for it instead of just reacting.
Fill a jar with sand and the big rocks will not fit afterwards, no matter how you shake it. Put the rocks in first and the sand runs round them. Nothing about the volume changed — only the order.
There is always more to do than there is time, and the tasks are not equal — a few produce most of the value and the rest arrive dressed as urgency. Prioritisation is deciding what gets your energy and, much harder, what does not. The difficult part is rarely identifying the important thing. It is saying no to a genuinely good thing in order to protect it. Digital work removes the natural limit. Every channel delivers straight to you, everything arrives with a badge on it, and a tool that can generate ten options in a minute also generates ten things to do about them. The inbox is not a priority list. It is a list of what other people wanted.
| What it is | What it isn’t |
|---|---|
| One task named before the day | A list sorted as things arrive |
| Important | Urgent |
| A clear yes | A maybe kept alive |
| A block booked in advance | Whatever time was left over |
What it looks like. Someone asks for something reasonable first thing. It is genuinely useful and it is not your one thing. You say you will look at it after lunch, and then you do.
- More demands than hours. Which is every job now. Not choosing is still choosing, and it hands the sorting to whoever is loudest.
- When everything is technically urgent. Every notification arrives wearing the same badge. If nothing can be dropped then nothing is being prioritised — you are working a queue in arrival order.
- Leading anyone. A team that has not been told what matters most will each pick something different, all of it reasonable.
- Name the one task that would make the rest matter less, and do it before anything reactive.
- Sort urgent from important. Most urgent things are someone else’s important thing arriving on your desk.
- Use a hard filter: anything short of a clear yes is a no. Maybes accumulate, and nothing else does.
- Book the block before the day fills. An unbooked hour is not protected; it is just unclaimed.
- Break it into parts
Four parts: naming the one task that matters, splitting urgent from important, applying a hard yes-or-no filter, and protecting a block for the work.
- The part that carries it
Naming the single task that would make the rest matter less, and doing it first — before the day starts negotiating with you.
- The order to learn it in
- Name the one task each morning, before email, and do it first.
- Then sort incoming demands by urgent against important, rather than by who asked.
- Then apply the hard filter: anything short of a clear yes is a no.
- Put something at stake
Tell your manager each Monday what your one thing is for the week, and report on Friday whether it moved.
- Compress it
One task named before the day starts. Urgent is not important. Anything short of a clear yes is a no.
- The smallest useful dose
Sixty protected minutes on the one thing, every working day, before anything reactive.
- Anchor it to something you know
A jar, some sand and some big rocks. Put the sand in first and the rocks will not fit, however hard you shake it. Put the rocks in first and the sand runs round them.
“The key is not to prioritise what’s on your schedule, but to schedule your priorities.”
— Stephen R. Covey
The interactive version is in the course. The diagram, the simulation and the four-question check for Prioritisation run in the free course, where your progress across all 24 skills is kept.
Open Prioritisation in the course →
Not sure where you stand? Take the twelve-minute self-assessment, or see the 30-day course that turns these skills into a roadmap.