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 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 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.
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.
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.
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 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.
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 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.