Guides

Honest answers about prioritising a working day, grounded in named results from scheduling and queueing theory rather than productivity folklore.

• What to do with a task you keep postponing — A task that has survived a fortnight of being scheduled later is telling you something. Four specific things it might be, and what each one needs.
• Choosing between two important things — When both matter, importance has stopped being a useful tiebreak. Five questions that separate them, in the order that resolves it fastest.
• Coming back after time away — A gap in a record is a gap in a record. What to do on the first morning back, and why rebuilding the old plan is the wrong first move.
• When two people give you different priorities — You cannot resolve a conflict between other people's priorities by working harder. What you can do is make the conflict visible to the people who own it.
• Do productivity systems actually work? — Some of the mechanisms are sound and the claims made for them usually are not. How to tell which part of a system is doing work and which part is decoration.
• When everything feels urgent — Urgency is about when; importance is about consequence. They feel identical because urgency is louder. Two named failure modes explain the rest.
• How long should a task take? — Nobody can tell you the right number, and it is not the useful question. What an estimate is really for, why accuracy is not the point, and what to do after.
• How many tasks should a day hold? — There is real arithmetic behind limiting work in progress, and no research establishing a magic number. Here is where the line between them falls.
• How to decide what to drop — When the arithmetic does not work, something is not happening — the only question is whether you choose it or discover it. Six questions, in order.
• How to do a five-minute daily review — The review is where a plan becomes an estimate. Four questions, five minutes, and the one thing that must never be part of it.
• How to handle constant interruptions — An interruption costs more than the minutes it takes, and the extra is paid on the way back. What a scheduler does about it, and what transfers to a person.
• How to plan a week, not just a day — A week is where capacity becomes visible and a day is where it is decided. What belongs at each level, and the mistake that makes weekly plans collapse.
• How to prioritise a long backlog — A backlog and a day are different objects with different rules. Sorting the whole thing is the wrong move; here is what to do with it instead.
• How to prioritise your tasks — Three methods, and how to tell which one today is asking for. A method aimed at the wrong problem feels like a personal failing when it is not.
• How to prioritise work across a team — A team is not one worker multiplied. Adding people shortens some work and none of the rest, and there is a 1967 result that says exactly how much.
• How to say no to more work — Saying no is admission control, and every system that stays responsive has some. What to say instead, and why promising to try is the expensive answer.
• Is a long to-do list bad? — Not in itself, and the guilt about it is misplaced. What costs you is how many things are open at once, which is a different number entirely.
• Is multitasking real? — A processor with one core does not multitask; it switches fast enough to look like it. What that does and does not tell you about a person doing four things.
• Is there a best prioritisation method? — No, and that is a formal result rather than a hedge. The right ordering rule depends on what you are optimising for, which is why the question comes first.
• Ivy Lee vs Top 3: which one fits — Both limit what you take on, but answer different problems. One caps volume; the other enforces order. Choosing wrong is why a method stops working.
• Little's Law, applied to a working day — Limiting work in progress shortens completion time, and that is arithmetic rather than willpower. What the theorem says, and what it does not say.
• Should you plan your day the night before? — The 1918 method that made this famous put the planning at night for a specific reason, and it is not about discipline. What it buys, and what it costs.
• Prioritising life, not just work — Personal work has no deadlines and no one chasing it, which is exactly the condition under which a queue starves its most important items.
• Prioritising when you work for yourself — Without a manager, nothing arrives pre-ranked and nothing is ever due. The freedom is real and so is the failure mode it creates, which has a name.
• Should you batch similar tasks? — Usually yes, and the reason is mechanical rather than motivational. Where batching helps, where it quietly hurts, and how large a batch should be.
• Should you do the hardest thing first? — Two ordering rules answer this and they disagree, because they optimise for different things. Which one is right depends on what today is actually short of.
• Should you schedule every hour? — A fully booked day has no room to absorb anything, and queueing theory is unusually blunt about what happens to a system run at full utilisation.
• What switching tasks actually costs — A processor does not multitask either; it switches fast and pays for it. The overhead has a name, a mechanism, and a point where throughput collapses.
• What a good task looks like — Most tasks that never get done were badly written rather than badly prioritised. Four properties, and the test that takes five seconds.
• What to do when you can't start — Not starting is usually a decision problem rather than a motivation one. If the first action is unnamed, there is nothing to begin, and willpower cannot help.
• What to do when you have too much to do — First establish whether this is a prioritisation problem or a capacity problem, because the second one does not respond to any ordering rule at all.
• What to do with work that repeats — Recurring work has a scheduling literature of its own, and one useful result: fixed priority by frequency beats judging each occurrence on its merits.
• When the day goes wrong by ten o'clock — A plan that met reality and lost is not a failed day. Re-plan once, deliberately, against the hours that are actually left — not the ones you started with.
• When your day is all meetings — Fragmented time is not the same quantity as those hours in one block, and planning as though it were is why the gaps between meetings produce so little.
• When your work depends on other people — A significant task can be held up by a trivial one, and the size of the blocker says nothing about the size of what it blocks. This has a name and a fix.
• Why deadlines work, and what they cost — Ordering by deadline is provably optimal for one objective and quietly bad for another. Knowing which one you are buying is the whole of using them well.
• Why your important work never gets done — There is a name for work that waits forever because louder work keeps arriving. It is starvation, and the standard fix is not discipline.
• Why your priorities change by lunchtime — A plan that can be renegotiated at any moment will be. The fix is not more resolve but a rule about when the order is allowed to change at all.
• Why small tasks pile up — Small work is cheap to accept and cheap to defer, so it accumulates from both ends. Two ordering rules disagree about it, and both are right.
• Why to-do lists stop working — A plain list runs in arrival order, the one ordering known to be bad. The problem is not discipline — a list records decisions instead of making it.
• Why you can't finish anything you start — Starting is cheap and finishing is not, so a day fills with open work. The gap between them has a mechanism, and closing things beats starting fewer.