Guide
Eisenhower matrix: from tasks to project arbitration
Two axes — urgent and important — and four quadrants that tell you what to do, schedule, delegate or drop. The same logic scales to a portfolio.
The Eisenhower matrix sorts work along two independent axes: importance, which measures the contribution to a goal, and urgency, which measures how soon the deadline is. Crossing them gives four quadrants and four different decisions. Its power lies in separating two things that daily pressure constantly confuses.
The four quadrants
Important and urgent: handle it now — crises, hard deadlines. Important but not urgent: schedule it, because this is where preparation, design and prevention live. Urgent but not important: delegate it, or handle it in a batch. Neither important nor urgent: drop it, and stop feeling guilty about it.
The quadrant that decides everything
The second quadrant — important, not urgent — is the one that gets sacrificed, and the one that produces the next quarter’s crises. Every hour not spent on specification, testing or risk anticipation comes back as an urgent item later. A team that permanently lives in quadrant one has usually starved quadrant two for months.
When everything is urgent
If most items land in the urgent column, the problem is upstream: too many commitments, or an unarbitrated demand. Urgency is a symptom of an overloaded portfolio far more often than a personal organization issue — which is exactly why the matrix cannot stop at the individual level.
From the task to the portfolio
The same two axes apply to projects: strategic contribution instead of importance, deadline or window of opportunity instead of urgency. The portfolio version usually adds a third dimension — effort or cost — because arbitrating projects means comparing value against the capacity they consume. Prioritizing without looking at workload just moves the queue.
Prioritizing in FoxPlan
Tasks and Kanban cards carry a priority level, and portfolio views let you rank projects, compare them against available capacity and record the resulting arbitrations. The workload histogram can be read by project priority, so you can see which projects are actually consuming your teams — and whether that matches the ranking you defended in the last steering committee.
