Start the Job That Has Been Sitting Since Tuesday
One quotation, one appraisal write-up, one difficult call keeps sliding to tomorrow, and three other people are waiting behind it. This session works out why that particular task is being avoided and gives people a practised way to make a start on it.
What One Postponed Task Costs Everybody Else
Procrastination is rarely laziness. It is usually a task that is unclear, unpleasant, or has no visible edge: the vendor call that will turn into an argument, the appraisal write-up with no format to follow, the report that could take an hour or a day. So it moves down the list, and it takes other people's work down with it. This session works on what participants are actually avoiding right now, names the reason for each item, and rehearses the first ten minutes of starting.
Program Focus: Beating Procrastination
Naming Why This One Is Stuck
Each participant lists what they have been putting off and sorts it by cause: not clear enough to begin, unpleasant to do, or with no defined end. The remedy is different for each, so the sorting comes first.
The First Ten Minutes
Cutting a stalled job down to a first piece that can be finished in one sitting — open the file and write the heading, draft the opening line of the mail — so beginning stops being a decision to be made again each morning.
Work With No Edge
A task that could take an hour or a week gets avoided longest. Setting a scope and a stop point before starting, so a policy draft or a costing has a version that counts as finished.
The Conversation Being Avoided
A large share of postponed work is not paperwork, it is a conversation: the vendor who is late, the employee whose output has dropped, the customer asking for a discount you cannot give. Participants rehearse the opening lines.
Deadlines You Set Yourself
Why a customer's date holds and a self-imposed one slips, and how to borrow the force of an external commitment — telling a colleague, booking the slot, sending the calendar hold before the intention fades.
When the Delay Is Not Yours
A file that has sat for a week waiting on the promoter's signature is not procrastination. Telling your own avoidance apart from a queue you do not control, and what to escalate instead of privately blaming yourself.
Checking In Without Nagging
Pair check-ins and a short weekly look at what stayed on the list untouched. Light enough that a supervisor keeps doing it in a busy week, rather than an accountability system that lasts a fortnight.
Benefits
Something Stalled Actually Gets Started
Participants make a start on a real postponed item during the session, so the method has been used once before it goes back to a desk with them.
Fewer People Waiting on One Desk
When the approval, the quotation or the write-up that everyone is waiting for finally moves, the delay stops multiplying down the line into other people's dates.
Avoidance Gets Named, Not Judged
People can say out loud what they are avoiding and why without it turning into a performance conversation. For many participants that is the first time the real reason is stated.
A Reason to Escalate Instead of Stall
Participants can separate their own delay from someone else's, and raise a genuinely blocked item with the person who can move it rather than letting it sit.
Why Choose GullyHR
Your Own Postponed List, Not a Case Study
The working material is what participants are avoiding this week, brought into the room. Nobody spends the session solving a fictional student's assignment problem.
We Say When It Is Not Procrastination
Where the pattern is an approval stuck with one signatory, a queue longer than the week, or priorities the owner resets every Monday, we say so. That is a process problem, and GullyHR would take it up as process consulting rather than sell you this session.
No Motivational Content
Short input, then applied work on real tasks, and an honest look at the items that will probably still be avoided next week. No pep talk, no quotations on slides.
Part of the Time and Productivity Programme
It runs on its own or alongside the prioritisation, planning and interruption modules, weighted to whatever the time-use diagnostic shows this cohort actually struggles with.
Start With the One That Has Been Sitting Longest
Tell us what your teams are postponing and who is waiting behind it. We will scope a session around those tasks — or say so if what you are describing is a queue problem rather than an avoidance one.
Frequently Asked Questions
Scoped with you rather than fixed. It runs as a short focused session or as one module inside the wider time and productivity programme, and the length is confirmed in the proposal once we know the cohort size and how much of the time goes to work on real tasks.
Only at the margins, and we would rather say that plainly. Training an individual to start faster does not fix a list that gets reordered from the top every Monday — that is a decision-making and process question, and we would look at it separately. The session still helps with the items that are genuinely being avoided, which in most teams is a real and separate share of the backlog.
Yes, with the examples changed. For a supervisor, postponed work looks like the incident report not written up, the operator conversation not had, the maintenance request not raised. The language of delivery is agreed in advance so people are working in the one they are comfortable arguing in.
No training can promise that, and we will not. What the session gives someone is a way to name why a specific task is stuck and a practised first step for it. Whether it holds depends on what their manager asks about in the weeks afterwards, which is why participants leave with an action plan their manager can see where you want that.