Eisenhower week prioritization
2×2 Eisenhower table grouping a week's tasks into Do First / Schedule / Delegate / Delete — the canonical text-in-cell layout, not a scatter chart.
For the engineering manager
Scenario
An engineering manager triages her week at Monday planning. The point of an Eisenhower matrix in real use isn't a scatter plot — it's a four-cell list: tasks dropped into the quadrant that matches their urgency × importance. The table tells her at a glance where her attention should go this week (Do First + Schedule), what to push down (Delegate), and what to drop (Delete).
Annotation key
matrix eisenhower— preset axes (urgency × importance) and four quadrant titlesstyle: table— text-in-cell layout: hides axes/arrows/grid, renders quadrant titles as cell headers, lists each item as a bulletQ1:…Q4:— shorthand forcell (col, row) label: …. Q1=top-right (Schedule), Q2=top-left (Do First), Q3=bottom-left (Delete), Q4=bottom-right (Delegate)- Repeating
Q2:stacks multiple tasks in the same cell as a bullet list
How to read
The "Do First" cell (top-left in eisenhower's convention with urgent on the left axis) is the urgent + important pile — work the morning sprint. "Schedule" is the trap quadrant: important but not yet urgent (Q3 OKRs, refactor) — it silently slips until it becomes urgent and badly done. "Delegate" is the busy-work the AI generates — urgent on someone's calendar but not actually load-bearing for the org. "Delete" is the candidate for "no": neither urgent nor important.
Why a table, not a chart
The classic Eisenhower output is a 2×2 grid with task lists, not a scatter of dots. If you want to encode a third dimension (time cost, owner) on top of the cell layout, drop style: table and use "Label" at (x, y) size: N instead — that switches to bubble mode.