Prioritising when you work for yourself
The short answer
Working for yourself removes the thing that was quietly doing your ordering: other people's deadlines.
That sounds like pure gain and mostly is. The cost is specific. Client work has dates attached, so it is loud. The work that builds the business — the site, the positioning, the thing that would bring better clients next year — has no date, so it is silent. A queue with no correction always serves the loud item, so the silent work never runs.
This is starvation, and it is a property of the ordering rule rather than of you. The mechanism and the standard fix.
The three queues, which is the useful frame
Most self-employed work sorts into three, and they behave differently enough that mixing them is where the trouble starts.
Delivery. Client work with dates. Loud, and it will always get done — that is not the problem.
Sales. Finding the next piece of work. Has no date, and its consequence arrives two months later, which is exactly the shape of thing a deadline-driven day defers indefinitely. The specific failure is the feast-and-famine cycle: delivery fills the week, sales stops, and six weeks later there is no delivery to do.
Building. The website, the process, the offer. No date at all, and no consequence for a year — so it starves hardest.
The correction is not motivation. It is giving the two silent queues a standing claim before the loud one gets to bid.
What actually works
Give sales a fixed slot every week, when you are busiest. This is the whole thing, and the timing is the counterintuitive part. Sales feels unnecessary in a full week and urgent in an empty one — which is precisely backwards, because the pipeline you build today pays out in six weeks. Two hours on a Monday, held regardless.
Invent deadlines for undated work, and tell someone. A date with no consequence is a preference. Attaching another person to it — a client call booked, a post announced, a collaborator expecting a draft — converts it into something that will actually happen. This is borrowing the loudness that client work gets for free.
Separate the day's list from the business's list. They operate at different timescales and the long list will otherwise eat the day. Capture everything; commit to three things for today.
Price the time properly. An hour on the site is an hour not billed. That is a real cost and pretending otherwise is why building work gets abandoned at the first busy week — it should be planned as a cost, not squeezed into the gaps that a busy week does not have.
The failure that is not a prioritisation problem
Working at full capacity every week is not a sign the business is going well. It means there is no room for the work that would change anything — and a system with no slack has nowhere to put anything unexpected.
If every hour is billable, the business is a job with worse security. That is a structural observation rather than a scheduling one, and no method fixes it; the only levers are price, scope and who you work for.
A weekly shape that holds
- Monday, first two hours: sales. Before delivery has a chance to fill the day.
- One half-day a week: building. Same slot every week. Protected the way a client call would be, because it is the same kind of commitment.
- Everything else: delivery, ordered by real dates.
- Friday, fifteen minutes: what did I plan, what happened. Planned against actual is the only honest signal when there is no manager to give you one.
The specific hours matter far less than the fact that the silent queues have a claim which is made before the loud one arrives. Leftover time is where starvation happens, by definition.
The honest caveat
None of this helps if the arithmetic does not work. If delivery genuinely fills every hour and the money is still short, that is a pricing or a positioning problem wearing a productivity costume, and reorganising the week will not touch it.
The useful test: track planned against actual for a month, then look at what the business actually pays you per hour worked — including the unbilled hours. That number answers a different and more important question than any ordering rule can.
Where to go next
- Why your important work never gets done — starvation, and aging as the correction
- Why deadlines work, and what they cost — what you lose when nothing has a date
- How to prioritise your tasks — the three conditions
Using this in Decide One
Decide One bounds the day and keeps the long list separate, which is the distinction that matters most when nobody else is setting your scope. Durations on each line make the unbilled hours visible instead of invisible.
A line you did not finish is unfinished. It is not marked against you, and a day you did not open is not counted.
Open Decide One — free to use, with no account. Nothing you write leaves your device.
Decide One is a priority instrument. Bring the day into view, choose a method, give the first thing real time.