The Eisner Matrix
A four-quadrant way to decide what deserves attention now, what deserves a plan, what can be handed off, and what should stop.
Human truth
Most teams call everything urgent because urgency is easy to feel. Important work is quieter, slower, and often the first thing pushed aside.
The parts
Urgent + important
The work with a real consequence if it waits. Handle it now, then ask what made it an emergency so the same fire does not return.
Important, not urgent
The work that changes the future: customer learning, planning, prevention, and the systems that make the next quarter less chaotic. Put it on the calendar before urgency fills it.
Urgent, not important
The interruption that needs movement but not necessarily your movement. Delegate it, simplify it, or make the decision once so it stops coming back.
Neither
The work that creates motion without consequence. Name it clearly, then stop doing it.
The review
Return to the matrix regularly. If the same work keeps landing in urgent and important, the system needs attention. The goal is not to process emergencies better. It is to create fewer of them.
The matrix is not a way to be busy more efficiently. It is a way to protect the work that matters from the work that merely arrives first.
When to reach for it
Your backlog is full, every request says urgent, and the team cannot explain what will be different if it gets done. Use it when deciding what you will not do, not just what comes next.
The essay
U
rgent is loud. Important is usually quiet.
That is why most teams mistake activity for progress. An urgent request lands in Slack. A customer escalates. Someone senior wants an answer. Those things may matter. But the speed of the request is not proof that it deserves the next hour of your team’s life.
The Eisner Matrix gives the conversation four places to go. Urgent and important work gets handled. Important work that is not urgent gets planned. Urgent work that is not important gets delegated or simplified. The rest gets removed.
The second quadrant is the one teams lose first. Nobody has to interrupt you to ask for customer research, better onboarding, cleaner handoffs, or the process that keeps a known problem from happening again. So those things wait. Then, a few weeks later, they come back as an emergency.
That is the useful part of the matrix for go-to-market work. It makes the cost of postponing prevention visible. If a customer-facing gap keeps producing urgent tickets, the answer is not to get faster at the tickets. It is to reserve time for the important work that closes the gap.
Use it in planning, but use it in the moment too. When a new request shows up, ask two plain questions: What happens if this waits? And what changes if we do it? The answers tell you more than the volume of the request ever will.
The point is not to create a perfect list. It is to make the trade visible. Once you can see it, you can decide what gets your attention and what gets out of the way. ■
Where it came from
The Eisner Matrix is adapted from the classic urgent-versus-important prioritization model. Jason uses it as a practical operating tool for go-to-market teams: a way to separate real customer consequence from internal noise, and to make room for the work that prevents the next emergency.