Important Tasks

This document explores time management in IT through the Eisenhower Decision Matrix, categorizing work by urgency and importance to optimize resource allocation. It examines handling immediate incidents versus investing in long-term infrastructure, managing technical debt accumulation, dealing with interruptions effectively through team rotation and focus time blocks, and ensuring dedicated periods for complex problem-solving that drives sustainable improvements.

The Most Valuable Resource: Time

Beyond Computer Resources

While previous discussions covered making better use of computer resources like CPU, memory, disk, and network, another resource is even more valuable in day-to-day operations: time.

Resource value comparison:

Human Time Optimization Goals

As humans, ensuring that time is spent on meaningful activities is essential, including work that is enjoyed and earning the satisfaction of a job well done. When working, optimizing the time spent to bring the most value to the company is necessary.

Time optimization dimensions:

Finding the right balance is challenging. From updated calendars to social media detoxes, many different ways exist to optimize time.

The Eisenhower Decision Matrix

Framework Overview

One method that’s super effective when working in IT is the Eisenhower Decision Matrix. When using this method, tasks are split into two different categories: urgent and important.

Eisenhower Matrix structure:

The following interactive visualization shows the Eisenhower Decision Matrix with color-coded quadrants representing different priority levels. Hover over each quadrant to see detailed examples and recommended time allocation.

Note

The Eisenhower Matrix uses color coding to indicate priority: red (Quadrant 1) for urgent and important tasks requiring immediate action, green (Quadrant 2) for important but not urgent strategic work where most time should be invested, yellow (Quadrant 3) for urgent but not important interruptions to manage strategically, and gray (Quadrant 4) for neither urgent nor important tasks to eliminate.

Matrix definitions:

Quadrant 1: Important and Urgent

Critical Immediate Tasks

Tasks that are important and urgent need to be done right away. Draw alarm bells around them because these require immediate attention.

Quadrant 1 examples:

Quadrant 1 characteristics:

For example, if the company’s Internet connection is down, it’s both urgent and important to get it back up as soon as possible.

Warning

When Quadrant 1 tasks dominate work schedules, it indicates insufficient Quadrant 2 investment in planning and prevention, creating a crisis-driven culture that exhausts teams and prevents strategic improvements.

Quadrant 2: Important but Not Urgent

Strategic Long-Term Work

Some tasks are important but not urgent, so they need to get done at some point even if it takes a while to complete them.

Quadrant 2 examples:

For example, as a follow-up to the network being down, it would be important to make sure that there’s a backup network connection so that if the existing one is ever down again, the company can stay connected using the backup.

Infrastructure Investment

Setting up infrastructure so that changes can be easily rolled back or new servers deployed when needed takes a large chunk of time. But investing in the future can save even more time and user frustration when responding to a problem.

Infrastructure investment ROI:

Technology Research

Researching new technologies is another task in this category. IT is always evolving and it’s important to have time set aside to stay up to date.

Technology research areas:

Research task characteristics:

Quadrant 3: Urgent but Not Important

Managing Interruptions

Other tasks might seem urgent but aren’t really important. A lot of the interruptions that need to be dealt with are in this category.

Quadrant 3 examples:

Answering email, phone calls, texts, or instant messages feel like something that needs to be done right away. But most of the time are not really the best use of time.

Communication channel prioritization:

Interrupt Handling Strategies

If working in IT support, being interrupted is part of the role, so planning to deal with those interruptions effectively is necessary.

Team-based rotation strategies:

If working on a team, the person dealing with interruptions can be rotated. Maybe someone takes care of them in the morning and a different person in the afternoon, or alternating days.

Independent work strategies:

If working independently, establishing a set of hours when users can expect availability for normal requests is possible, with the rest of the time being available only for emergencies.

Important

The key is having a window of time reserved when interruptions won’t occur. That’s the time when the most important tasks can be completed, when full concentration on complex issues and finding solutions for tricky problems is possible.

Quadrant 4: Neither Important nor Urgent

Eliminating Time Wasters

Finally, there’s a whole category of tasks that are neither important nor urgent. These are distractions and time wasters that shouldn’t be done at all.

Quadrant 4 examples:

These include meetings where nothing useful is being discussed, email threads that lead to nowhere, office gossip, and any other tasks that eat up time without giving anything valuable in return.

Time waster identification:

Polite elimination strategies:

Time Allocation Strategy

Focus on Important Tasks

In general, to make the most of time, ensuring that the majority is spent on tasks that are important is necessary.

Ideal time allocation:

Typical vs. optimal allocation:

Urgent vs. Long-Term Balance

Of course getting to urgent tasks as soon as possible is desired, but blocking some time for long-term planning and execution is needed.

Balancing considerations:

Spending time on long-term tasks might not bear fruit right away, but it can be critical when dealing with a large incident.

Note

Quadrant 2 work is the most important investment for IT professionals. It prevents Quadrant 1 crises, builds capabilities that make work more efficient, and creates the infrastructure that enables rapid response when problems do occur.

Technical Debt

Understanding Technical Debt

Another important task that might not necessarily be urgent is solving technical debt.

Technical debt definition:

Technical debt is the pending work that accumulates when choosing a quick-and-easy solution instead of applying a sustainable long-term one.

Creating Technical Debt

When applying a short-term remediation to fix a problem right away, and then planning for a long-term solution to prevent it from happening in the future is a pattern seen several times. Until the fix is complete, the workaround created is technical debt because time must be spent keeping it in place even if it’s not the best solution.

Technical debt creation scenarios:

Whenever going for short-term solutions and leaving the long-term solution for later, technical debt is being created. This might be the right decision in the moment to get out of a crisis and let users get back to work, but time must be scheduled to apply the long-term solution that will make future lives easier.

Technical debt decision framework:

External Technical Debt

Technical debt can also be generated by external parties. For example, when a new version of software being used is released, time must be scheduled to upgrade it. Until that happens, the pending upgrade is technical debt.

External technical debt sources:

Technical debt tracking:

Protecting Focus Time

The Importance of Uninterrupted Work

Depending on the role and how the company works, getting work done in a different location to avoid people walking up to a desk might be necessary, or actively silencing any notifications to avoid getting interrupted and distracted by unimportant conversations.

Focus time protection strategies:

Notification management:

Making Focus Time Effective

Assuming that some time has been set aside to work on important but not urgent tasks, ensuring work on the right things with the right priorities is the next consideration.

Focus time optimization:

Complex problem-solving environment:

Conclusion

Time represents the most valuable and irreplaceable resource in IT work, surpassing even critical computer resources like CPU, memory, and network because it cannot be scaled through hardware purchases or recovered once lost, requiring optimization through strategic task prioritization and effective management frameworks. The Eisenhower Decision Matrix provides a powerful categorization system splitting tasks into four quadrants based on urgency and importance, with Quadrant 1 containing critical incidents requiring immediate response like network outages, Quadrant 2 holding strategic work like infrastructure investment and technology research that prevents future crises, Quadrant 3 capturing interruptions that feel urgent but deliver low value like most emails and messages, and Quadrant 4 containing time wasters like unproductive meetings that should be eliminated entirely. Optimal time allocation targets 50-60% in Quadrant 2 strategic work because this investment in long-term solutions like automated deployment, backup systems, and monitoring infrastructure saves exponentially more time during future incidents while preventing many problems from escalating to crises, contrasting with crisis-driven environments spending 60% in Quadrant 1 firefighting that leaves no time for improvements. Technical debt accumulates when choosing quick-and-easy temporary fixes over sustainable long-term solutions, creating ongoing maintenance burden from workarounds that must be maintained, pending software upgrades that increase security risk, and deferred infrastructure improvements that compound over time, requiring scheduled time in Quadrant 2 to systematically reduce this debt through proper long-term implementations. Managing Quadrant 3 interruptions in IT support roles requires strategies like team rotation where different people handle requests in morning versus afternoon shifts, establishing office hours when users can expect availability for normal requests while reserving other time for emergencies only, and working in different locations or silencing notifications to protect focus time windows. Protected focus time enables the deep concentration necessary for complex problem-solving and strategic work, requiring 2-4 hour uninterrupted blocks during peak energy periods with notifications completely silenced and either physical separation from interruption sources or explicit team agreements about do-not-disturb periods, ultimately allowing completion of the important-but-not-urgent Quadrant 2 work that transforms reactive firefighting into proactive system improvement.

FAQ