Eisenhower Matrix Template

What Is the Eisenhower Matrix?

The Eisenhower Matrix is named after Dwight D. Eisenhower, the 34th President of the United States, who was famously productive and attributed his effectiveness to a simple principle: "What is important is seldom urgent and what is urgent is seldom important."

The framework is a 2×2 grid that categorises every task by two dimensions: urgency (is there time pressure?) and importance (does it move you toward your goals?). By plotting your work across these two axes, you get four distinct quadrants - each with a clear action: do, schedule, delegate, or eliminate.

The power of the matrix lies in a single insight that most leaders struggle with: urgency and importance are not the same thing. A Slack message marked "urgent" may have zero strategic value. A career-development conversation with a direct report has enormous strategic value but no deadline forcing it to happen today. Without a system for separating the two, most managers default to working on whatever feels most pressing - and the important work quietly falls off the radar.

The Template

Below is the Eisenhower Matrix template. Each quadrant maps to a specific action and contains example tasks for engineering managers. Use this as a starting point - fill in your own tasks each week during your planning session.

The Four Quadrants Explained

Quadrant 1: Do (Urgent & Important)

These are crises and hard deadlines that demand immediate action. A production outage, a critical security vulnerability, or a key team member handing in their notice - these cannot wait. You handle them now, personally, and with full focus.

The trap with Q1 is that it feels productive. Firefighting gives you an adrenaline rush and a sense of accomplishment. But if you spend most of your time here, it means you are not investing in Q2 work that would prevent crises from occurring in the first place. A healthy Eisenhower Matrix has a relatively small Q1.

Quadrant 2: Schedule (Not Urgent & Important)

This is where high-impact leadership lives. Strategy, mentoring, process improvement, relationship building, career development conversations, architecture reviews - none of these have a deadline screaming at you today, but all of them compound over time. Q2 is where great engineering managers differentiate themselves from mediocre ones.

Because Q2 tasks have no built-in urgency, they are the first to be postponed when something "urgent" arrives. The solution is to schedule Q2 work in your calendar as immovable blocks. Treat a career conversation with a direct report with the same seriousness as a meeting with your VP. If it is not on the calendar, it will not happen.

Quadrant 3: Delegate (Urgent & Not Important)

Q3 tasks create the illusion of productivity. Someone needs a quick answer on Slack, a stakeholder wants a status update, a meeting invitation lands in your inbox marked "urgent." These tasks have time pressure but do not move you or your team toward meaningful goals. The right response is to delegate them - to a team lead, a senior engineer, or an automated system.

Delegation does not mean ignoring these tasks. It means building systems and empowering people so that you are not the bottleneck. Create a shared FAQ for common stakeholder questions. Empower your tech lead to approve routine code reviews. Set up automated status dashboards so people can self-serve instead of asking you.

Quadrant 4: Eliminate (Not Urgent & Not Important)

These are activities that deliver no value and have no deadline. They persist out of habit, obligation, or distraction. Attending a weekly meeting you contribute nothing to. Re-reading the same Slack channel for the third time today. Refactoring a module nobody uses because the code "bothers" you. These tasks should be ruthlessly eliminated.

Audit your calendar and your habits every quarter. If you cannot articulate why an activity exists and what value it delivers, stop doing it. The time you reclaim flows directly into Q2, which is where it creates the most leverage.

How to Use This Template

Follow these six steps to integrate the Eisenhower Matrix into your weekly workflow:

1. Brain-dump every task. At the start of your week (Monday morning works best), write down every task, commitment, and open loop on your plate. Do not filter or prioritise yet - just get everything out of your head and onto paper or a digital list.
2. Score each task on urgency and importance. For each item, ask two questions: "Does this have a real deadline or time pressure?" (urgency) and "Does this contribute to my long-term goals, team health, or strategic outcomes?" (importance). Be honest - most tasks that feel urgent are not truly important.
3. Place each task in the correct quadrant. Use the template above. If you are unsure where something belongs, default to Q3 (delegate) rather than Q1 (do). Most people over-classify tasks as urgent and important.
4. Act on Q1 immediately. Handle crises and hard deadlines first thing. Aim to complete or make significant progress on all Q1 items by midday.
5. Schedule Q2 into your calendar. Block dedicated time for important-but-not-urgent work. Protect these blocks as fiercely as you would a meeting with your CEO. This is where your highest-leverage work lives.
6. Delegate Q3 and eliminate Q4. For each Q3 task, identify who can handle it or what system can automate it. For Q4, simply stop. Remove yourself from the meeting, unsubscribe from the notification, or archive the task.

Eisenhower Matrix Examples for Engineering Managers

The abstract framework becomes clearer with concrete examples from engineering management. Here are four scenarios you will recognise:

Example 1: Production Incident (Q1 - Do)

Your on-call engineer pages you at 10 a.m. - a critical payment-processing service is returning 500 errors and customer transactions are failing. This is both urgent (every minute costs revenue) and important (it directly impacts your team's core metric). You drop everything, join the incident channel, coordinate the response, and communicate status to stakeholders. Classic Q1.

Example 2: Career Development Conversation (Q2 - Schedule)

A senior engineer on your team wants to grow into a staff role. The conversation about their development plan has no deadline - nobody is going to page you if it does not happen this week. But it is deeply important: it affects retention, team capability, and individual fulfilment. If you keep postponing it because "something urgent came up," that engineer will eventually leave. Schedule it. Protect the time. This is where great managers invest.

Example 3: Slack Notification Flood (Q3 - Delegate)

You are tagged in twelve Slack threads before lunch. Most are questions about deployment processes, access requests, or status checks. They feel urgent because someone is waiting, but they are not important - they do not require your specific expertise or authority. Create a team FAQ document, empower your tech lead to handle access requests, and set up a status dashboard. Delegate the pattern, not just the individual task.

Example 4: Refactoring a Stable Module (Q4 - Eliminate)

You spot a module written in an older style that "could be cleaner." The code works, has good test coverage, and nobody needs to modify it in the foreseeable future. Refactoring it would feel satisfying but delivers no user value, no performance improvement, and no reduction in maintenance burden. This is Q4. Resist the itch. Redirect that energy toward Q2 work that actually compounds.

Common Mistakes

• Putting everything in Q1. If every task is "urgent and important," the matrix loses its power. Be ruthlessly honest about what truly has both time pressure and strategic impact. Most of your tasks belong in Q2 or Q3.
• Neglecting Q2 consistently. Q2 is the most valuable quadrant, yet it is the easiest to skip because nothing forces you to do it today. If you find your Q2 list growing week after week without progress, your calendar is broken - fix it by blocking dedicated time.
• Not reviewing weekly. A one-time exercise is not enough. The matrix only works as a recurring habit. Rebuild it every Monday. Tasks shift quadrants as deadlines approach or priorities change, and new tasks arrive constantly.
• Confusing delegation with abdication. Delegating Q3 tasks does not mean ignoring them. You are still accountable for the outcome. Set clear expectations, provide context, and follow up. Delegation is a leadership skill, not an escape hatch.
• Using it alone instead of with your team. The Eisenhower Matrix is even more powerful when your entire team uses the same language. When everyone understands the difference between Q1 and Q3, conversations about priorities become faster and more precise. Share the framework in a team meeting and encourage people to use it in their own planning. For more prioritisation approaches, see the prioritisation matrix framework.