The Eisenhower Matrix is a simple prioritization method that divides tasks into four quadrants based on urgency and importance. It helps teams and individuals categorize work, decide what to do, delegate, or defer, and maintain focus on strategically valuable activities. Useful for backlog and time management.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
The Eisenhower Matrix is a prioritization method that sorts tasks by urgency and importance. It helps separate immediate action, scheduling, delegation, and elimination.
The method is attributed to Dwight D. Eisenhower. In a 1954 speech, he highlighted the contrast between what is urgent and what is important. The familiar four-quadrant version was later popularized, especially by Stephen Covey in The 7 Habits of Highly Effective People (1989), as a practical tool for task prioritization. It responds to the problem of limited attention being pulled toward urgent work that is not always the most valuable.
Think of it as a two-axis sorting grid: urgency on one axis, importance on the other. Each task is placed by answering two questions: does it need action now, and does it contribute to a meaningful goal? That produces four actions: do now, schedule, delegate, or drop. The matrix works best when tasks are re-evaluated regularly rather than fixed by first impressions.
A task appears time-sensitive and demands prompt attention.
A task contributes to goals, impact, or long-term value.
The combination of important/unimportant and urgent/not urgent yields four distinct response patterns.
Tasks with lower personal priority can be handed off when responsibilities allow it.
Important but non-urgent tasks need a reserved slot in the calendar or they will be displaced.
People tend to favor urgent tasks even when other tasks create more value.
The matrix is useful for daily planning, backlog grooming, and team alignment when many tasks compete for attention. It separates reactive pressure from strategic work and makes delegation visible. Its limits show up when delegation is unavailable, dependencies are complex, or urgency keeps crowding out everything else; then it needs support from context, capacity, and clear goals.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.