Prioritising life, not just work

Updated 2026-09-12

The short answer

Personal work loses to work work for a structural reason, not a moral one: the office has deadlines, meetings and people waiting, and your own life has almost none of that.

Urgency is what gets work selected, and personal items are almost never urgent until they suddenly are — the passport, the appointment, the conversation. A queue with no correction serves the loud item every time, so the quiet queue starves. The mechanism, and the standard fix.

The correction is the same one operating systems use: give the quiet work a standing claim, before the loud work gets to bid.

Urgency is about when; importance is about consequence. Sorting on both axes keeps them apart IMPORTANT · URGENT do it now, and it is loud enough that you will IMPORTANT · NOT URGENT the quadrant that starves, because nothing here ever asks NOT IMPORTANT · URGENT the loudest work on most days, and the reason above is empty NEITHER cheap to drop once it is written down where you can see it MORE URGENT LESS URGENT MORE IMPORTANT LESS IMPORTANT
Urgency is about when; importance is about consequence. Sorting on both axes keeps them apart

The two kinds, which behave differently

Life admin. The renewals, the forms, the appointment nobody will book for you. Individually trivial, collectively substantial, and it decays into something worse when deferred — a renewal becomes an expiry becomes a problem.

The fix is batching. One bounded block a week, same slot, everything in it. These tasks are nearly all short and nearly all require the same state: a laptop, the account details, half an hour. Doing them one at a time as they surface is the expensive version.

The things that actually matter. The relationship, the health thing, the person you have been meaning to call. These have no deadline at all, ever — which is precisely why they starve hardest. Nothing will ever make them urgent until something does, and by then the window has usually closed.

These do not respond to batching. They need a fixed, protected slot, defended exactly as a meeting would be, because a calendar defends what is on it and defends nothing that is not.

Applying the two axes properly

The urgent/important matrix is more useful here than at work, because personal life produces the clearest possible example of its central quadrant.

Almost everything that genuinely matters in a life is important and not urgent. Exercise, savings, the difficult conversation, seeing people. It has no deadline, makes no noise, and is invisible to any system that orders by what is asking now.

That quadrant is the one the matrix exists to protect, and personal life is where the cost of not protecting it is highest — because work will eventually generate a consequence that forces the issue, and a life mostly will not.

What works

One slot, protected like a meeting. Not a list, a slot. The specific hour matters less than that it is fixed and that it is defended the way a work commitment would be.

Batch the admin, once a week, bounded by time. An hour of life admin ends. "All the life admin" does not.

Give undated things a date and tell someone. A date with another person attached is the only reliable way to convert a silent item into one that happens. Booking the thing is the task.

Do the blocking ones first. Some personal admin is holding up someone else in your life. Same rule as work, same reason.

Keep one list, not two. Work and life compete for the same hours in the same day whether or not they are written in the same place. Two lists hide the competition; they do not remove it.

The honest limit

Nothing here helps if the underlying arithmetic does not work. If the job takes sixty hours a week, the correct response is not a better personal ordering rule — it is a conversation about the job, and reorganising a list will not touch it.

Scheduling technique has a ceiling, and pretending it does not is how people end up feeling that a structural problem is a personal failing.

And a note on how this should feel

An unfinished personal task is unfinished. It is not a verdict on your life, and a week where none of it moved is a week, not a pattern.

The test worth applying to any system you use for this: could this make someone feel bad on a day they had a bad day? If it could, it will — and the days it does that are the days you most needed it to work.

Where to go next

Using this in Decide One

Decide One does not separate work from life, because a day does not. Three things, whatever they are, with real times against the hours actually available.

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.

Open it — free, nothing to sign up for