Decide What Goes First, and Who Gets Told
Everything on the list is marked urgent, so the loudest requester wins and the important work waits. This session gives a team one way of sorting competing demands that survives a bad Monday, and the wording to tell a requester their item is not first.
Sorting Is the Easy Half
Most people can already point to the two things on their list that matter most. What stops them is the next part: telling the third requester their item moves to next week, when that requester is a senior colleague, a paying customer, or the owner. So the list quietly gets reordered by whoever asked last. This session covers a sorting method simple enough to use under pressure, then spends real time on the conversation that has to follow it.
Program Focus: Task Prioritisation Techniques
Urgent and Important, Kept Apart
A four-quadrant sort applied to the participant's actual list, including an honest look at how much of a normal week goes to work that was only ever urgent.
One Method the Whole Team Uses
A sorting rule shared across a team beats a better rule that one person applies alone, because priorities have to be comparable between people before a handover argument can be settled.
Whose Decision Is It
Some priority calls belong to the manager or the promoter, not to the person holding the task. Recognising which ones, and putting them up with options attached rather than as a complaint.
Telling a Requester They Are Not First
Wording for the call or the mail: what will happen, when, and what would have to move to bring it forward. Practised until it sounds like the participant rather than like a script.
The Cost of the Reshuffle
What reordering a list mid-week actually costs — the setup repeated, the half-finished item, the handover redone — so a reprioritisation gets made with its price visible to whoever is asking for it.
Breaking Down What Cannot Be Ranked
A large piece of work sits on the list unranked because it is a block rather than a task. Splitting it into items that can be compared against everything else competing for the same day.
Making It Survive Monday
A short weekly reordering slot and a shared record, so the sort gets repeated in the business rather than done once in a workshop and abandoned by the second week.
Benefits
The Loudest Requester Stops Winning by Default
A stated sorting rule lets somebody hold a position with a reason behind it, instead of conceding because the other person asked more forcefully.
Priority Decisions Reach the Right Desk
Calls that belong to the owner get escalated with options attached, rather than absorbed silently by a team lead who then carries the consequences.
Requesters Know Where They Stand
A clear not this week, here is when beats silence, and it usually cuts the chasing more than working faster would have.
Two People Can Compare Their Lists
When a team sorts the same way, a dependency or a handover can be discussed on the facts rather than with both sides insisting everything they hold is critical.
Why Choose GullyHR
Sorted on a Live Task List
Participants sort their own real work during the session. Nobody spends the afternoon ranking the tasks of a fictional manager in a case study.
The Conversation Gets as Much Time as the Matrix
Most prioritisation training stops at the framework and hands out a template. Roughly half of this one is practice at communicating a decision that somebody will not like.
Run for the Whole Team Where It Matters
A shared rule is worth more than an individual one, so where you want it to stick we run it with the group that shares the queue rather than with one nominated person from each department.
Clear About What Sorting Cannot Do
Ranking a list does not shorten it. Where the volume genuinely exceeds the people available, we say so and treat it as a resourcing question rather than a technique to be taught better.
Bring the List Everyone Says Is Urgent
Tell us which team is being reordered by whoever asks last, and who the requesters are. We will scope a session around that queue and the conversations attached to it.
Frequently Asked Questions
Yes, along with a couple of simpler alternatives. The method is chosen for being usable on a bad Monday rather than for being clever, and we do not spend the day comparing frameworks. Whichever one the team can actually repeat is the one worth adopting.
Scoped with you rather than fixed. It runs as a focused workshop for one team or as a module inside the wider time and productivity programme, and the length is confirmed in the proposal once the cohort and format are known.
Yes, and that is the version we would suggest. A shared sorting rule only settles arguments if everybody in the argument uses it, and the escalation practice works better when the person who normally receives the escalation is in the room to react to it.
No. Duplicate approval paths are a process design problem, and sorting a list faster does not remove a signature from the route. That is work GullyHR would take up as process consulting rather than as a training session, and we would say so before proposing this one.