Eisenhower Priority Matrix

A senior manager or director describes their workweek as almost entirely reactive - they move from meeting to meeting, respond to requests, handle escalations, and by Friday have done nothing that advances their own priorities. They know this is a problem but cannot identify a way in.

The diagnostic framing is critical here: 'Before we try to fix the calendar, let's see what's actually in it.' Have the client bring a real task list from the past week, not a hypothetical one. Placing actual tasks in the matrix rather than representative examples is what makes the pattern visible. The common pattern will be: top-right quadrant (Important + Not Urgent) nearly empty, bottom-left quadrant (Not Important + Urgent) overloaded. Name what you expect to find before the exercise so the client sees it as a system problem, not a personal failure.

The bottom-left quadrant is where the most important diagnostic work happens. If tasks land there but no one is named in the Delegate column, the client is accepting other people's urgent priorities without a delegation decision. Also watch whether everything in the top-left quadrant is genuinely both important and urgent, or whether urgency has been assigned by organizational pressure rather than actual consequence. The distinction matters for whether the response is execution or negotiation.

Start with the quadrant distribution count - how many items in each quadrant? The distribution itself is more informative than any individual item. Then move to the bottom-left column: read each item and ask 'whose urgent is this?' If it's someone else's, name who should own it. Then focus on the top-right column: what is in there, and when was the last time the client protected calendar time for it? The debrief ends with one concrete calendar change for next week - not a system change, one change.

A founder or owner with a small team handles the majority of their work themselves - including tasks that could be delegated - because it feels faster, more reliable, or more comfortable to do things personally. The business is growing and the model is no longer sustainable, but delegation feels risky.

Position the Delegate quadrant as the primary output of this exercise, not just one of four categories. 'We're going to use this matrix specifically to identify what you're doing that you shouldn't be.' The resistance to delegation in founders is usually not laziness but a legitimate history of delegation going wrong. Name that: 'The goal isn't to hand things off blindly. The goal is to identify what's specifically in your way and make a real delegation decision about it.' The Delegate column must name a person or it doesn't count.

Watch whether tasks in the bottom-left quadrant (Not Important + Urgent) get moved to Delegate with a specific name, or whether the client writes 'team' or 'someone else.' Abstract delegation is not delegation. Also watch whether any tasks in the top-right quadrant (Important + Not Urgent) are things the client has been meaning to address for months - those are the highest-value items in the exercise and often get overlooked because they don't press.

Start with the Delegate column: read each item and ask when specifically the client will have the delegation conversation. Not 'soon' but a day and a format. Then move to the Delete column: ask whether those items actually got deleted from previous versions of the list or have been reappearing. The pattern of recurring Delete items is important data about what the client is not willing to actually remove. End with the top-right quadrant: pick one item and schedule it.

A recently promoted manager is still doing a significant portion of individual contributor work because it feels familiar, they're good at it, and they don't trust that it will be done properly otherwise. Their leadership responsibilities are being crowded out by execution-level tasks that now belong to their team.

Frame the matrix as a way to surface the transition that hasn't fully happened yet. 'Your old job and your new job are both in your task list. Let's sort them.' The Important + Urgent and Important + Not Urgent quadrants will likely contain a mix of leadership tasks (strategy, team development, stakeholder management) and individual contributor tasks (execution, quality review, deliverable production). Making that mix visible is more useful than immediately discussing what to do about it.

Watch whether the IC tasks that land in the bottom-left quadrant (Delegate) get realistic names assigned, or whether the client immediately says 'the team isn't ready.' That may be true, but it's also the justification that prevents the transition from ever happening. Ask: 'Ready enough to start, with you reviewing? Or ready to own it completely?' The first condition is usually already met. Also notice whether any of the top-right items are team development activities - those are the first things new managers drop and the last things they should.

Start with the ratio of leadership tasks to IC tasks in the top-left quadrant. If IC tasks outnumber leadership tasks 2:1 or more, the transition has not happened even if the title has. Name that specifically. Then move to the delegation decisions: for each item with a name, ask what the handoff plan actually is - not whether the team member exists, but whether there is a specific plan to transfer ownership. End with what the top-right leadership tasks are and when they will be scheduled.