openskills.info

Time Management

Deciding what not to do, and leaving enough slack that the plan survives contact with a Tuesday.

Time management is mostly a decision problem wearing a scheduling costume. You will not get through everything; the only real question is what gets dropped and whether you choose it or it chooses itself. Which means the useful moves are unglamorous — ranking things against each other rather than all being important, leaving gaps so that one overrun doesn't take the week with it, and finding out where the hours actually go rather than where you assume they go. Most productivity systems fail not because the system is wrong but because they're applied to a workload that was never going to fit, and no amount of arrangement fixes an arithmetic problem.

Mostly Harmless

The Urgent-Always-Wins

Works strictly in order of arrival, with volume as a tiebreaker. Whatever landed most recently and most loudly gets attention now, which means the work is always genuinely, verifiably necessary and never once chosen. The important thing with no deadline — the documentation, the hiring, the architecture problem everyone agrees about — has been on the list for fourteen months in a state of permanent near-eligibility, and will still be there when it finally becomes urgent, at which point it will be handled immediately.

The Priority Flattener

Has fourteen top priorities. Marks each of them urgent, in good faith, because each genuinely matters and downgrading any one feels like a judgment on the person who asked for it. Has thereby communicated precisely nothing about what should happen first, and transferred the entire ranking problem to whoever picks up the list, who will resolve it by doing the easiest one. Would describe the team as aligned on priorities, which is true in the sense that everyone has the same fourteen.

The Buffer-Free Planner

Schedules to the minute, wall to wall, with a precision that looks like competence and functions as a fault line. The nine o'clock runs eight minutes over and every subsequent commitment of the day inherits the debt, arriving late, ending early, and generating two follow-ups that must be scheduled into a week with no remaining space. Regards this as an unusually chaotic week. It has been an unusually chaotic week for three years.

The Time Blindness Case

Has no idea where the hours go and a confident theory about it that has never been checked. Believes the mornings are productive and the meetings are the problem, and has never once written down what actually happened to a Tuesday. Operates a mental model of their own week assembled from impressions, mostly from the memorable bits, and so optimizes energetically against a version of the problem that may not be the one they have.

Scenarios

You have fourteen things and your manager asks what's most important. What would you do — say all of them are, which is true, or force a ranking and tell them what will slip as a result?

Your calendar is booked solid all week and something urgent arrives. What would you do — fit it into the evening, or find the thing already scheduled that it should displace and say so?

You feel like meetings are destroying your week but haven't measured. What would you do — start declining meetings, or track two weeks first and find out whether meetings are actually the largest block?

Takeaway

  • Rank against each other, not against a standard. If everything is a priority, you've made no decision and someone else will.
  • Leave gaps on purpose. A plan with no slack fails on the first eight-minute overrun.
  • Say what will slip when you accept something new. Silent absorption just moves the failure later and makes it yours.
  • Measure a couple of weeks before redesigning your system. Your impression of where the time goes is assembled from the memorable parts.
  • Accept that things will be dropped. Choosing which ones is the whole job.

Go deeper

Awesome Links