---
title: How to Make an Eisenhower Matrix Slide in PowerPoint
description: Build an Eisenhower Matrix slide in PowerPoint with quadrants that resize themselves as task cards get added, moved, or deleted.
image: https://www.advis-io.com/hubfs/blog-key-visuals/136-eisenhower-matrix-powerpoint.en.kv.png
---

[![logo\_transparent-Apr-12-2025-09-23-39-9623-AM-1](https://www.advis-io.com/hubfs/logo_transparent-Apr-12-2025-09-23-39-9623-AM-1.svg)](https://www.advis-io.com/en/?hsLang=en)

- [BLOG](https://www.advis-io.com/blog?hsLang=en)
- [ABOUT](https://www.advis-io.com/about?hsLang=en)

[CREATE SLIDES](https://marketplace.microsoft.com/en-us/product/advisioinc1760912844242.advisio-202604?tab=Overview)

Consulting Slides

# How to Make an Eisenhower Matrix Slide in PowerPoint

Build an Eisenhower Matrix slide in PowerPoint with quadrants that resize themselves as task cards get added, moved, or deleted.

[Advisio Editorial](https://www.advis-io.com/en/blog/author/advisio-editorial)

 Oct 14, 2026

---

It's Tuesday morning, fifteen minutes before a priority-setting review, and someone is dragging twenty-three sticky-note-style task cards into a four-quadrant grid in PowerPoint. The grid itself takes thirty seconds — four rectangles, two axis labels, done. The twenty minutes that follow are spent nudging cards so the "Do First" quadrant's nine cards don't overlap, shrinking font size in "Delegate" to make its six cards fit a box sized for three, and re-centering everything after someone says quadrant three should really be "Decide," not "Delegate." An Eisenhower Matrix slide is two intersecting lines and four labeled boxes. What breaks it is that the box sizes get fixed before anyone knows how many tasks are going into each one — and that number changes every time the slide gets used, because that's the whole point of a prioritization matrix.

## The Matrix That Works Until the Real Task List Arrives

Here's the version that shows up in most working sessions: four equal squares arranged in a 2x2 grid, axis labels for Urgency (horizontal) and Importance (vertical), and a plan to drop sticky-note-style cards into each quadrant once the task list is final. It looks clean in the template state, with two or three placeholder cards per box. Then the actual prioritization exercise happens — a product team sorting this sprint's backlog, say — and "Do First" (urgent and important) ends up with nine cards: a production bug, three client escalations, a compliance deadline, two blocked teammates waiting on a decision, a board-deck slide due that afternoon, and a vendor contract expiring at midnight. "Delete" (neither urgent nor important) gets one card: a recurring status meeting nobody remembers the purpose of.

Nine cards in a box sized for three means overlapping edges, cards that no longer fit inside the quadrant border, and a font size that's been shrunk twice already. The one-card "Delete" quadrant, meanwhile, sits mostly empty next to it — exactly as tall as the overcrowded quadrant beside it, because quadrant height was set once, for all four boxes, before the task list existed.

## Why Fixed Quadrants Break on the First Real Sort

Three assumptions get baked into the slide before the content exists, and none of them hold once real tasks start landing.

**Quadrant size assumes an even split that almost never happens.** A 2x2 grid divides the slide into four equal regions because that's the only assumption a template can make with no task list in hand. Real prioritization exercises are lopsided by design — the whole reason to run one is that most of what's on a to-do list turns out to be urgent-but-not-important noise, or a crowded "Do First" quadrant that needs to get triaged down. An even split is the one outcome a working session is actually trying to avoid.

**Card count changes mid-meeting, and the layout doesn't know that.** Someone reclassifies a card from "Decide" to "Do First" twenty minutes into the review because a deadline turns out to be closer than the card's author thought. If quadrant height is fixed, that one move can push a quadrant that was already tight over the edge, and nobody notices until the cards are physically colliding.

**Quadrant 2 and Quadrant 3 get mislabeled more often than the other two.** "Important, not urgent" (Decide / Schedule — strategic work with no immediate deadline) and "Urgent, not important" (Delegate — other people's priorities landing on your desk) sound similar enough that a card sorted under time pressure lands in the wrong one roughly as often as the right one. A slide that doesn't visually distinguish the two quadrants' purpose beyond a one-word label makes that mis-sort easy to miss until someone reads the quadrant out loud in the meeting.

## Step 1 — Build the Grid as Four Independent Containers, Not One Fixed Table

Skip the SmartArt Basic Matrix and the 3x3 table approach — both default to four cells of identical, linked size, which is exactly the assumption that breaks here. Instead, draw four separate rectangles (Insert \> Shapes \> Rectangle), one per quadrant, positioned with a shared center gap of about 0.15 inches for the crosshair, and give each one its own name in the Selection Pane ("Quad\_DoFirst," "Quad\_Decide," "Quad\_Delegate," "Quad\_Delete"). Because they're four independent shapes rather than cells in one table object, each one's height and width can change without PowerPoint trying to keep all four in lockstep.

**Common mistake:** building the matrix as a single 2x2 table and then trying to resize one cell. PowerPoint tables resize rows and columns across the whole table, so widening one cell's row to fit more cards widens every other cell in that row too — which is how "Do First" needing more height turns into "Decide" getting taller for no reason. Four separate rectangles don't have that constraint.

## Step 2 — Size Each Quadrant to Its Own Card Count

Don't fix quadrant dimensions until the cards exist. Once a quadrant's card count is final, the sizing is mechanical: at a typical card size of 1.8 inches wide by 0.6 inches tall with 0.1-inch gaps, a quadrant needs roughly (cards per row × 1.9) inches of width and (rows needed × 0.7) inches of height, where rows needed = ceiling(card count ÷ cards per row). A nine-card "Do First" quadrant at three cards per row needs three rows — about 2.1 inches of height. A one-card "Delete" quadrant needs exactly one row — about 0.7 inches.

That leaves two quadrants of very different height sitting side by side in the same grid. Resist the urge to force them back to equal size by shrinking the crowded quadrant's card font, which is the same failure mode as cramming six competitor bullets into a box sized for three on a [3C analysis slide](https://www.advis-io.com/en/blog/3c-analysis-slide-powerpoint?hsLang=en) — a reader clocks shrunken type as "this didn't fit" even without being able to say why. Instead, let the grid itself be asymmetric: the two columns can differ in width, and the two rows can differ in height, as long as the crosshair lines connecting them still meet at a clean intersection and every quadrant's top-left label sits at the same offset from its own corner. Consistent corner-label placement is what tells a viewer these are still four co-equal quadrants, not a hierarchy by accident of size.

## Step 3 — Group Each Quadrant With Its Own Cards, Then Lock the Crosshair Separately

Select each quadrant's rectangle plus every card currently inside it and group them with Ctrl+G. This is the step that makes a mid-meeting reclassification tolerable: moving a card from "Decide" to "Do First" means dragging it out of one group into another and letting that group's height recalculate — not re-measuring every card in both quadrants by hand. Keep the crosshair (the two lines separating the quadrants) and the axis labels ("Urgency," "Importance") as a separate background object, ungrouped from any quadrant, since resizing one quadrant means the crosshair position needs to shift but the quadrant contents don't need to move relative to each other.

**A note from experience:** at a Big Four firm, I sat through a quarterly priority review where the Eisenhower Matrix slide got rebuilt live, three times, because every reclassification meant re-measuring two quadrants by hand. The actual prioritization conversation — should this really be urgent, or does it just feel that way because the person raising it is anxious about it — kept getting interrupted by someone saying "hold on, let me fix the layout first." The matrix is a sorting tool. A layout that fights every sort defeats the point of running the exercise live instead of just emailing people a static list.

![Comparison diagram: a 2x2 Eisenhower Matrix built as one linked table with four equal-size quadrants causing a nine-card Do First quadrant to overflow while a one-card Delete quadrant sits empty, versus the same matrix built as four independently grouped quadrants sized to their own card counts.](https://www.advis-io.com/hubfs/blog-figures/136-eisenhower-matrix-powerpoint-fig1.en.png)

Figure: a linked 2x2 table with equal quadrant sizes overflowing under a lopsided task sort (top), versus four independently sized and grouped quadrants (bottom).

![Comparison diagram: an Eisenhower Matrix with four equal-height quadrants causing a nine-card Do First quadrant to overflow its box while a one-card Delete quadrant sits mostly empty, versus the same matrix with each quadrant sized to its own card count.](https://www.advis-io.com/hubfs/blog-figures/136-eisenhower-matrix-powerpoint-fig1.en.png)

Figure: four equal-height quadrants with Do First overflowing (left) versus quadrants sized to their own card counts (right).

## Making Quadrant 2 and Quadrant 3 Impossible to Mix Up

"Important, not urgent" and "urgent, not important" are easy to confuse under time pressure, because both get shortened to a single word — "Decide" and "Delegate" — that doesn't carry the reasoning behind the label. The fix isn't a better word; it's a second line of text under the quadrant title that states who the task actually serves. Under "Decide / Schedule," add a small subtitle in 11-point gray type: "Moves your own goals forward — no deadline forcing it." Under "Delegate," add: "Someone else's deadline, not your priority — hand it off." A card sorter reads the subtitle, not just the label, and the two quadrants stop looking like synonyms.

This matters more than it sounds like it should, because the two quadrants also tend to swap crowding depending on who's running the exercise. An individual contributor's task list usually has a thin "Delegate" quadrant — there's often nobody to delegate to — and a dangerously thin "Decide" quadrant, because strategic, no-deadline work is exactly what gets crowded out by everything else. A manager's task list flips this: "Delegate" fills up fast with requests that technically landed on their desk but belong to someone on their team, while "Do First" should be thinner than it usually is if delegation is actually happening. Neither pattern is wrong on its face, but a slide that can't show the difference — because both quadrants are the same size regardless of content — hides the exact signal a manager running this exercise is looking for: is my "Do First" quadrant crowded because the work is genuinely urgent, or because I'm not delegating enough to keep "Delegate" where it belongs?

Color can reinforce the same distinction without replacing the subtitle. A light green fill for "Do First," pale blue for "Decide," pale amber for "Delegate," and light gray for "Delete" gives a reader a pre-verbal cue before they've read a single card — but keep the fills pale enough that a 12-point black card label stays legible on top, and never let color alone carry a distinction a subtitle can state in words. Color is the second signal, not the first one.

## Three Mistakes That Show Up Even After the Grid Is Fixed

**Treating "urgent" as a synonym for "important."** The entire point of the matrix collapses if a task lands in "Do First" because it feels pressing rather than because it's actually both urgent and important. A ringing phone is urgent by definition — that's what makes a phone ring — but most calls aren't important, which is the classic example Eisenhower's framework was built to separate out. Sort by feeling and the matrix just reproduces whatever was already loudest, which defeats the reason to run the exercise.

**Leaving "Delete" nearly empty and treating that as a sign the exercise worked.** An empty "Delete" quadrant usually means tasks that belong there were never written down as cards in the first place — recurring meetings nobody questioned, reports nobody reads, "quick syncs" that exist out of habit. A task list with zero genuinely deletable items is rarer than a task list where nobody looked hard enough for them. Treat a thin "Delete" quadrant as a prompt to look again, not a result to be proud of.

**Re-running the sort from scratch instead of re-sorting what changed.** Once a quadrant's card count and positions exist, the next review should move individual cards that changed status, not rebuild all four quadrants from an empty grid. Rebuilding from scratch is slower, and it throws away the one thing a recurring prioritization exercise is supposed to build over time: a visible record of which quadrant a given task actually tends to land in, review after review.

## Four Principles That Hold for Any Prioritization Matrix

- **Build the grid as independent containers, not a linked table.** A SmartArt matrix or table object resizes cells in lockstep; four separate grouped shapes don't.
- **Quadrant size follows card count, decided after the sort, not before it.** An even 2x2 split is the one outcome a real prioritization exercise is least likely to produce.
- **Trim before you shrink.** A genuinely overloaded quadrant should get its lowest-priority cards moved to a parking-lot list, not a smaller font to force a fit.
- **Group by quadrant, not by card type, so reclassification is a drag between groups.** That's the difference between a mid-meeting reclassification taking five seconds or five minutes of re-measuring.

## Applying the Same Grid to a RICE or MoSCoW Prioritization Slide

The same four-step build carries over directly to other 2x2 or categorical prioritization frameworks that consulting and product teams run the same live-sorting exercise with. A MoSCoW slide (Must have / Should have / Could have / Won't have) is structurally the same problem as the Eisenhower Matrix — four buckets, wildly uneven counts, built from a backlog that gets reclassified in the room — and the fix is identical: independent grouped containers sized to their own item count, not a fixed table. A RICE-scored backlog sorted into "build now" versus "build later" tiers instead of four quadrants only changes the number of containers, not the construction logic.

What changes between frameworks is which bucket tends to be the crowded one. On a product backlog, "Could have" is usually the overloaded quadrant, not "Do First" — everything nice-to-have accumulates there because nobody wants to formally kill a feature idea. The same asymmetry that showed up in the task-sort example shows up again, just in a different corner of the grid, which is exactly why quadrant size has to be decided from the actual sort each time rather than copied from the last time the template got used.

None of this changes whether the prioritization itself is sound — a matrix built this way still lets a team sort a genuinely important task into "Delete" by mistake, same as a fixed grid would. What the construction above fixes is narrower: once the sort is done, the slide should show it without a quadrant overflowing or a font shrinking to hide the overflow. [Advisio](https://www.advis-io.com/?hsLang=en), listed on [Microsoft AppSource](https://marketplace.microsoft.com/en-us/product/advisioinc1760912844242.advisio-202604?tab=Overview), builds the quadrant grid from the actual task list as native, editable PowerPoint shapes — sizing each quadrant to its own card count and keeping the crosshair clean, so a card moved between quadrants mid-review is a drag-and-drop, not a rebuild.

[Consulting Slides](https://www.advis-io.com/en/blog/tag/consulting-slides) [Slide Design](https://www.advis-io.com/en/blog/tag/slide-design)

## Similar posts

![logo\_white-1](https://www.advis-io.com/hubfs/logo_white-1.svg)

Transform your business data into actionable insights with AI-powered analytics. Get consultancy-grade presentations in minutes, not weeks.

N&E Building, 6th Floor  
1-12-4 Ginza, Chuo-ku  
Tokyo 104-0061  
Japan

[contact@advis-io.com](mailto:contact@advisio.com)

 

<https://x.com/advis_io><https://www.linkedin.com/company/advisio1/><https://www.facebook.com/people/Advisio/61573197194211/>

- [Blog](https://www.advis-io.com/en/blog)
- [About Us](https://www.advis-io.com/en/about?hsLang=en)
- [問い合わせ](https://www.advis-io.com/contact?hsLang=en)
- [特定商取引法に基づく表記](https://www.advis-io.com/jacommercialtransaction?hsLang=en)
- [利用規約](https://www.advis-io.com/terms?hsLang=en)
- [プライバシーポリシー](https://www.advis-io.com/privacy-policy?hsLang=en)

© 2026 Advisio Inc. All rights reserved.

[Powered by Atlas - a B2B SaaS HubSpot theme](https://www.kalungi.com/atlas-hubspot-theme-for-b2b-saas-software)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Advisio Editorial",
    "url" : "https://www.advis-io.com/en/blog/author/advisio-editorial"
  },
  "dateModified" : "2026-10-14T23:24:49.966Z",
  "datePublished" : "2026-10-14T23:24:49.000Z",
  "headline" : "How to Make an Eisenhower Matrix Slide in PowerPoint",
  "image" : [ "https://www.advis-io.com/hubfs/blog-key-visuals/136-eisenhower-matrix-powerpoint.en.kv.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://www.advis-io.com/en/blog/eisenhower-matrix-powerpoint",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.advis-io.com/hubfs/logo.svg"
    },
    "name" : "Advisio株式会社"
  }
}
```