This Eisenhower matrix template keeps urgency and importance as separate judgments, with a reason for each. The makerspace example places five tasks, explains the proposed next actions, and keeps an unassessed request outside the four quadrants.
Name the goal before sorting the list
The original fictional planning snapshot is Friday morning. The goal is to prepare clear arrival instructions and a workable facilitator plan for Saturday's makerspace induction. The example includes a longer-term improvement to that recurring induction process. It supplies no actual event, staff agreement, or completed action.
Urgency concerns timing and the consequence of delay. Importance concerns contribution to the stated goal or responsibility. A task can matter to someone else's work while falling outside this particular planning goal.
Asana's Eisenhower matrix explanation separates the two dimensions and connects the quadrants with doing, scheduling, delegating, or removing work. Use those as prompts for a decision. A proposed handoff still needs the right owner and agreement; a low-priority label does not automatically cancel an obligation.
Read the reasons beside the placements
| Task | Urgency basis | Importance basis | Proposed placement and action |
|---|---|---|---|
| T1 · Correct the arrival reminder | The reminder is due Friday noon and currently names the wrong entrance. Delay would leave incorrect instructions in the planned message. | Clear arrival instructions directly support Saturday's induction. | Urgent / Important: correct the instruction and use the actual review/send process before noon. |
| T2 · Prepare a reusable welcome checklist | Intended for next month's induction; no immediate deadline is supplied. | A reusable preparation aid supports the recurring induction process. | Not urgent / Important: agree a preparation slot and reviewer. |
| T3 · Format the separate club newsletter | Its requester asks for formatting today. | The supplied work concerns a separate club newsletter, outside this induction goal. | Urgent / Not important to this goal: discuss routing with the newsletter owner and confirm who can take it. |
| T4 · Browse unused banner styles | No deadline or dependency is supplied. | No use for the banner styles is identified in the induction plan. | Not urgent / Not important to this goal: reconsider spending time on it. |
| T5 · Update a supply order | Deadline and consequence of delay are not supplied. | The request does not state its connection to the induction. | Unassessed: ask what must change, by when, and which work depends on it. |
T1 and T3 both have near-term timing. Only T1 has a supplied direct connection to this goal. T2 has a useful longer-term contribution without an immediate deadline. The matrix makes those differences visible rather than treating the newest request as the most important one.
Choose T2 · Welcome checklist in the example to inspect the longer-term work beside its proposed action. Scheduling it means agreeing actual time and a reviewer, not merely putting the task in the important quadrant.
Protect important work without ignoring obligations
Work in the urgent-and-important area needs attention in the current plan. For T1, the meaningful next step is a corrected reminder that goes through the real review and sending process. Moving a card does not perform that work.
For T2, ask when the preparation can happen before the next induction and who will check that the checklist fits the actual process. Otherwise, it may remain visibly Important while never becoming part of the working plan.
T3 needs a conversation about ownership and capacity. Its position means the task is outside the chosen induction goal; it does not make the newsletter worthless or give the induction lead authority to assign another person's work. Confirm the route with the owner rather than assuming a Delegate label completes the handoff.
For T4, consider whether there is a reason to retain it in another plan. If there is none, you can decide to stop spending time on it. The example keeps the record visible and does not delete anything for you.
Revisit the reason when an assessment changes
Select a task and change its proposed urgency or importance. The example moves that task to the corresponding area. If either dimension is Unknown, the task stays Unassessed instead of being treated as low priority.
Changing T2 to Urgent may be reasonable if a real deadline or dependency changes. The original “next month's induction” note alone does not explain that new judgment. The example retains the supplied reasons and prompts you to review them after an assessment change; it does not invent a new deadline to make the placement look consistent.
Review priorities when the goal, commitments, or available time change. If several urgent-and-important tasks compete, discuss the actual consequences, constraints, and responsibilities. The four areas do not compute an exact order within a quadrant or prove that the workload fits the day.
Copy a prompt for your tasks and goal
Create one complete HTML Eisenhower task-priority review page.
Planning goal, responsibilities and review time: [PASTE]
Tasks with stable IDs and relevant context: [PASTE]
Actual deadlines/dependencies and consequences of delay: [PASTE]
Each task's contribution to the goal: [PASTE]
Proposed next actions, owners and authority limits: [PASTE]
Assess urgency and importance separately from supplied information.
Show a reason for each dimension. Unknown is not No. Do not invent
deadlines, goal contribution, delegation authority or completed work.
Keep urgent/important, not urgent/important, urgent/not important,
and neither as named areas, plus Unassessed for either Unknown.
Include this original fictional Friday-morning makerspace example:
Goal: clear arrival instructions and workable facilitator plan for
Saturday's induction, plus preparation for the recurring process.
T1 Correct arrival reminder. Due Friday noon; wrong entrance now
listed. Important to clear arrival instructions. Urgent Yes,
Important Yes. Proposed action: correct then use real review/send.
T2 Reusable welcome checklist. For next month's induction; no
immediate deadline. Supports recurring preparation. Urgent No,
Important Yes. Proposed action: agree preparation slot and reviewer.
T3 Separate club newsletter formatting. Requester asks for today;
outside supplied induction goal. Urgent Yes, Important No for this
goal. Proposed action: discuss route/available owner, confirm handoff.
T4 Browse unused banner styles. No deadline/dependency and no
identified use in induction. Urgent No, Important No. Reconsider
spending time; do not delete or cancel it automatically.
T5 Update supply order. Deadline, delay consequence and connection
to induction absent. Urgent Unknown, Important Unknown. Ask what
changes, by when, and which work depends on it.
No actual event, staff agreement, delegation, sending or completion.
Show all five tasks and full reasons/actions, not only task names.
Provide task selection and proposed urgency/importance controls
with Yes/No/Unknown. Changes move the same task to the matching
area and retain its supplied reason, flagging that the reason needs
review after an assessment changes. Do not invent a new rationale.
Restore example restores all five assessments and clears stale
review prompts. A selected task shows its reason and proposed next
action; no Do/Delegate/Delete buttons that imply actual execution.
Add a blank goal/task scaffold and temporary review-notes area.
Preserve typing on task/assessment changes and confirm reset.
No overall priority score, automatic ordering inside quadrants,
calendar booking, assignment, cancellation or completion tracking.
Use at least 16px text, native labeled controls, visible focus and
named stacked areas at 360px without overflow. Inline CSS/JavaScript,
no external assets, network or storage. Return the complete HTML.
Check that the generated page keeps T5 unassessed and gives T2 a real planning question. Read every “not important” label in relation to the stated goal; the page should not turn that local assessment into a judgment about everyone else's priorities.
Review the commitments behind the quadrants
Put the HTML in your NOS workspace when a colleague needs to read the task reasons and proposed next actions together. Ask whether the plan protects the welcome-checklist work while still dealing with the noon reminder.
If “Not important” is being read as “unimportant to the organization,” clarify the static area description to “Not important to this induction goal” in visual editing mode. Save it so colleagues can reopen the existing link and read the narrower meaning. Check any separately maintained task plans too; editing the explanation does not route the newsletter or book preparation time.
Agree the next actions through the team's working process. Revisit the matrix when a deadline or goal changes, keeping the reasons visible beside the new placement.