The Eisenhower Matrix: The 2 Axes, How to Prioritize with Multiple Jobs, and Integrations (Jira, Apps)

The Eisenhower Matrix sorts tasks into four quadrants using two axes: urgency (time sensitivity) and importance (long-term impact). The quadrants are: Do now (urgent and important), Schedule (important but not urgent), Delegate (urgent but not important), and Eliminate (neither). For multiple jobs, the matrix fails unless you adapt it to account for job-specific priorities. For example, an urgent task in a low-priority job (e.g., a minor client request) should never override an important task in a high-priority job (e.g., a deliverable for your main income source).

How to Adapt the Eisenhower Matrix for Multiple Jobs: 3 Exact Steps

1. Assign Strategic Priority to Each Job (Not Just Tasks)

Label each job as high, medium, or low priority based on revenue, deadlines, or strategic value. For example:

• High priority: Jobs generating 80% of income (e.g., Client A, a $10K/month retainer) or with legal deadlines (e.g., tax filings).
• Medium priority: Recurring but low-growth work (e.g., a $2K/month client) or maintenance tasks (e.g., website updates).
• Low priority: Experimental or low-return work (e.g., a side project with no revenue yet).

A task’s urgency is secondary to its job’s priority. Example: A high-priority job’s non-urgent task (e.g., drafting a proposal for Client A) trumps a low-priority job’s urgent task (e.g., fixing a typo for Client C).

2. Use Colors or Labels to Visualize Jobs in the Matrix

Assign a color to each job and tag tasks accordingly. Example for a freelancer with three jobs:

• Red (Client A, high priority): Urgent/important tasks (e.g., finalizing a $15K project due Friday).
• Blue (Personal project, medium priority): Important/not urgent (e.g., writing a blog post to attract leads).
• Green (Client B, low priority): Urgent/not important (e.g., approving a minor design tweak).

This reveals imbalances. If your "Do now" quadrant is 90% red, you’re neglecting medium-priority work. Tools like Foco let you filter tasks by job color and urgency, turning the matrix into a live dashboard.

3. Set Conflict Rules for Competing Tasks

When tasks from different jobs clash, use these tiebreakers:

• Deadline vs. impact: A task due in 3 days with high consequences (e.g., losing a $20K contract) beats a task due today with low stakes (e.g., a $500 invoice).
• Dependencies: If Task A blocks 3 other people’s work, prioritize it over a solo task with the same deadline.
• Energy match: Do deep-focus tasks (e.g., coding) when fresh; save mechanical tasks (e.g., data entry) for low-energy moments.

Real Example: Applying the Matrix to a Freelancer’s Day

You’re a developer with three jobs:

• Client A (high priority): Fix a critical bug in a live app (due today, $5K penalty if delayed).
• Client B (medium priority): Draft a proposal for a $10K project (due in 5 days).
• Personal project (low priority): Update your portfolio (no deadline).

Your to-do list:

• Debug Client A’s app (2 hours).
• Reply to Client B’s email about the proposal (10 minutes).
• Attend a networking call (1 hour, no immediate benefit).
• Select portfolio projects (30 minutes).

Matrix breakdown:

• Do now: Debug Client A’s app (high priority + urgent).
• Schedule: Draft the proposal for Client B (medium priority + important). Block 1 hour tomorrow.
• Delegate/eliminate: Reply to Client B’s email (urgent but not important—batch it at the end of the day). Skip the networking call (no value).
• Eliminate: Portfolio update (not urgent or important).

Pros and Cons of the Eisenhower Matrix

Pros

• Clarity: Forces you to distinguish between urgency and importance, reducing reactive work.
• Flexibility: Adapts to multiple jobs if you assign job-specific priorities.
• Integration: Works with tools like Jira (see below) or apps like Foco to automate quadrant sorting.

Cons

• Subjectivity: Importance is hard to quantify. A task’s impact may not be clear until later.
• Overhead: Requires weekly reviews to adjust priorities as jobs evolve.
• No energy accounting: Doesn’t factor in your mental state (e.g., a high-priority task may not be doable when exhausted).

How to Use the Eisenhower Matrix with Jira (or Other Tools)

Jira lacks a native Eisenhower Matrix view, but you can replicate it using:

• Custom fields: Add "Urgency" (High/Low) and "Importance" (High/Low) to issues. Use JQL to filter: project = "Client A" AND Urgency = High AND Importance = High.
• Labels: Tag issues with quadrants (e.g., #do-now, #schedule).
• Automation: Use scripts to auto-assign quadrants based on due dates and priority levels (e.g., issues due in <24 hours with "Blocker" priority go to "Do now").

For non-Jira users, apps like Foco sync tasks from tools like GitHub or Asana and let you assign quadrants via drag-and-drop in a kanban view. Example: A GitHub issue labeled "urgent" and assigned to your high-priority job appears in the "Do now" column.

Key Mistakes to Avoid

• Treating all deadlines as equal: A task due today in a low-priority job isn’t more important than a task due in 3 days in a high-priority job.
• Ignoring the "Schedule" quadrant: Without it, you’ll always be firefighting. Block time for important/not urgent tasks (e.g., 2 hours/week for Client B’s proposal).
• Not reviewing priorities weekly: A job’s priority can change. Example: A side project becomes high priority if it lands a $20K contract.

How to Apply This with Foco

Foco lets you manage multiple jobs in one place, with each job assigned a color. In Panorama mode, you see all tasks color-coded by job, making it easy to spot imbalances (e.g., too many red tasks in "Do now"). In Foco mode, filter to one job to focus. Use the kanban view to drag tasks into quadrants (e.g., "Do now" column for urgent/important tasks). For Jira users, Foco’s Plus plan syncs issues and auto-assigns them to jobs based on rules you set (e.g., all GitHub issues go to your "Development" job).

The Eisenhower Matrix isn’t about doing more—it’s about doing what moves the needle for your most important jobs.

FAQ

FAQ

What are the 2 axes in the Eisenhower box?

The two axes are urgency (time sensitivity, e.g., deadlines) and importance (long-term impact, e.g., revenue or strategic value). Tasks are plotted on these axes to determine which quadrant they belong to.

How do I use the Eisenhower Matrix with Jira?

Add custom fields for "Urgency" and "Importance" to Jira issues. Use JQL to filter tasks (e.g., Urgency = High AND Importance = High). Alternatively, tag issues with quadrant labels (e.g., #do-now) or use automation scripts to auto-assign quadrants based on due dates and priority levels.

What are the pros and cons of the Eisenhower Matrix?

Pros: Clarifies priorities, reduces reactive work, and adapts to multiple jobs. Cons: Subjective (importance is hard to quantify), requires regular reviews, and doesn’t account for energy levels or task dependencies.

How do I prioritize tasks from different jobs using the Eisenhower Matrix?

Assign each job a priority level (high/medium/low). A task’s urgency is secondary to its job’s priority. Example: A non-urgent task in a high-priority job (e.g., drafting a proposal for your main client) beats an urgent task in a low-priority job (e.g., fixing a typo for a side project). Use colors or labels to visualize jobs in the matrix.

Can I automate the Eisenhower Matrix in tools like Jira or Asana?

Yes. In Jira, use custom fields for urgency/importance and JQL to filter tasks. In Asana, use custom tags or sections to represent quadrants. Apps like Foco sync tasks from these tools and let you drag-and-drop them into quadrants in a kanban view.