Time Management and Process Management

Most time-management advice starts and ends with prioritization matrices. Those are genuinely useful — but they quietly assume all your time is yours to allocate in the first place. It isn't. The bigger unlock for most managers is realizing how much of their calendar belongs to other people by default, and doing something deliberate about that.

Prioritizing what's actually in front of you

The classic tool here is a 2x2 of urgency and importance:

• Urgent and important — do these now, but keep them short. This is also the "urgency trap": because these feel critical in the moment, people over-invest time here even though the long-term value is usually low.
• Not urgent, important — this is where the real value lives, and where most people under-invest. Strategic planning, skill-building, relationship maintenance — none of it screams for attention today, which is exactly why it needs to be scheduled rather than left to compete with things that do.
• Urgent, not important — delegate these. They demand speed but don't demand you specifically.
• Not urgent, not important — cut them. These are the tasks that feel productive in the moment and add up to nothing.

A useful companion lens, especially for planning projects rather than daily tasks, swaps urgency for effort: quick wins (high impact, low effort) get prioritized first; major projects (high impact, high effort) get properly resourced rather than squeezed in; fill-ins (low impact, low effort) happen only when there's genuine slack; and thankless tasks (low impact, high effort) get avoided or renegotiated wherever possible. The two matrices ask different questions — one about timing, one about return — and it's worth running both before committing real time to something.

Whose time is it, actually?

Not all of your time is self-directed, and pretending otherwise is where a lot of time-management advice quietly fails leaders. Three categories:

• Boss-imposed time — the time you spend because your boss wants something. The pragmatic rule here, however unglamorous: satisfying your manager takes time, but failing to do so costs more of it later. If you disagree with a direction, make your case — but once you've made it and lost, commit fully rather than dragging your feet, which just burns time on both sides.
• System-imposed time — organizational demands that aren't from your boss or your team, but from the machinery of the company itself. Knowing people across departments makes this time cheaper to spend, because you're navigating the system with allies instead of alone.
• Self-imposed time — the time you actually control, and where your individual contribution to the organization shows up. This splits further into discretionary time (genuinely yours) and subordinate-imposed time — the time your own team hands back to you.

That last category is the one worth watching closest. The classic image is a "monkey" — a problem — jumping from a subordinate's back onto yours because they asked "what should I do about X?" and you answered instead of coaching them to the answer. Every monkey you accept is time you no longer control, and subordinates cannot impose one on you without your cooperation. The discipline isn't refusing to help — it's refusing to take the task back, the same principle covered under reverse delegation.

Procrastination deserves a specific mention here too, because it's often confused with laziness and it isn't the same thing. Procrastination is choosing an easier, more enjoyable task over an important one that's due — an active choice, not a passive failure to act. Naming it accurately is the first step to catching it in yourself before it costs you something real.

Building the structure that protects your time

A few concrete habits do more than any philosophy here:

• Delegate deliberately. Time management and delegation are the same skill pointed in different directions — every task you competently hand off is time returned to the quadrant that actually matters.
• Plan before you execute. Clear goals, broken into smaller steps with real deadlines, beat a long undifferentiated to-do list every time.
• Use your calendar as a commitment device, not a record. Block time for deep work before the week fills in around it, not after. Blocking personal time and breaks the same way you block meetings keeps them from quietly disappearing.

Borrowing structure from software teams

Two ideas from software delivery generalize well beyond engineering. Kanban visualizes work as it moves through stages (to do, in progress, done) and caps how much can be "in progress" at once — a work-in-progress limit — which forces finishing over starting. The metric that matters is lead time: how long something takes from the moment it's committed to until it's actually delivered, and the goal is shrinking that number over time, not just moving more cards.

The underlying principle transfers directly to personal time management: limit how many things you're actively juggling, finish before you start the next thing, and track how long things actually take from commitment to completion — not just whether they eventually got done.