Org Chart Slide: A Clean Hierarchy in PowerPoint

When an org chart slide is right, and when it isn't

An org chart earns its place when the audience needs to understand who owns what and who reports to whom. Use one for:

Executive org charts deserve extra discipline because they are both high-stakes and long-lived. A board or diligence audience will notice an ambiguous reporting line immediately, while the slide itself may be revised for months as titles and ownership change. Build it so a single role can be updated without reworking the full hierarchy.

For a financial bridge, see how to build a waterfall chart slide; for a four-quadrant assessment like SWOT, see our field guide to consulting frameworks.

Key takeaways

• Match the shape to how decisions actually get made: a functional chart if authority runs up one line, a matrix chart the moment a meaningful share of roles report into two.
• Show only the depth your audience needs, then group the rest into a single counted box. A chosen level of detail reads better than full depth under one leader and a single box under another.
• Reserve dotted lines for genuine matrixed or advisory relationships, always paired with a small legend. Solid lines mean formal reporting and nothing else.
• Keep the chart's shape stable across revisions. A board or diligence audience keeps this slide on file for months, and one redrawn every quarter starts to look unreliable regardless of accuracy.
• Build the chart as native, editable boxes and connectors, not a flat image, so the next reorg is a five-minute edit rather than a redraw from scratch.

The four org chart variants, compared

Every org chart is one of four underlying shapes. Match the columns below to your own reporting lines before you open PowerPoint; getting this choice right is what the rest of this guide's build steps assume.

Functional org chart: who is it built for?

A functional, or line, org chart is the default for a single-business company where authority runs in one direction: the CEO down to function leads such as finance, sales, product, and operations, then their teams beneath them. It is the shape most people picture the moment they hear the words org chart, and it is the right choice whenever a role has exactly one boss and one clear place in the hierarchy. Reach for it for onboarding decks, annual planning kickoffs, or any slide whose only job is to show who leads what, without the added noise of secondary reporting lines.

It earns its keep because it maps cleanly onto how a straightforward company runs day to day. If your organization has grown mainly through hiring rather than a merger or a geographic expansion, a functional chart will hold its shape for a long time; the boxes rarely need to move, only rename, which keeps a board or diligence audience confident the version in front of them is current.

Where it breaks down is scale and dual reporting. The moment a shared-services lead answers to both a division head and a central function, a purely functional layout hides that second relationship unless you add a dotted line, and once a chart needs more than one or two of those, it has effectively become a matrix chart wearing a functional skin.

The trade-off: a functional chart is the easiest of the four to build and the easiest to read, but it goes quiet exactly where the more interesting decisions in a modern company happen, in dual and shared reporting.

Matrix org chart: who is it built for?

A matrix chart is for an organization where a meaningful share of roles report to two managers at once, typically a functional manager and a project, product, or regional manager. That is closer to the norm than the exception: a 2013 to 2018 survey of more than 750 respondents across 500-plus companies, Vantage Partners' Organizational Effectiveness Study, found 90 percent of respondents worked in an organization that was at least somewhat matrixed, and the pattern held even at small companies, with 67 percent of respondents at firms under 100 employees reporting the same.

Build a matrix chart by keeping the primary, solid-line relationship as the backbone of the hierarchy, then adding a dashed connector for every secondary relationship, each one labeled through a small legend rather than left for the reader to guess at. Cap the depth earlier than you would on a functional chart; a leadership row plus one level below is usually the ceiling before the crossing lines stop explaining the structure and start requiring their own explanation.

Use it for a governance page mapping a steering committee against workstream leads, a post-merger structure during an integration, or any operating model where a shared function genuinely serves more than one part of the business.

The trade-off: a matrix chart tells the truth about how the organization actually decides, but it is the hardest of the four to keep legible; every dotted line is a line the reader has to interpret, and past a handful, the chart stops explaining the structure and starts requiring one.

Flat org chart: who is it built for?

A flat chart fits an early-stage company or a small team where most people report directly to one or two leaders, with little or no middle-management layer in between. It is the fastest of the four to build, since there is rarely more than one level to align, and the fastest to keep current, since a chart with few boxes barely needs a legend or a depth rule to stay readable.

The shape gets tested first as a team scales. Gallup's most recent workplace analysis puts the average US manager's span of control at 12.1 direct reports in 2025, up from 10.9 the year before and nearly 50 percent higher than in 2013, though the median manager still holds five to six. Gallup's Jim Harter, the firm's chief scientist for workplace management, has made the point that the count alone is not the risk factor: "poorly managed teams struggle, even when small." A flat chart that has quietly grown to fifteen or twenty direct reports under one box is usually a sign the structure needs a middle layer before the slide does.

Use a flat chart for a startup, a single department, or any team where introducing a management layer purely to make the org chart look conventional would misrepresent how the team actually runs.

The trade-off: a flat chart is trivial to build and keep current, but stretched past roughly a dozen direct reports per box, it stops describing real spans of control and starts hiding them.

Divisional org chart: who is it built for?

A divisional chart fits a company organized around product lines, regions, or markets, where each division runs semi-independently with its own leadership and, often, its own functional boxes underneath. It is the right shape once a single functional chart would have to repeat the same finance, sales, and operations boxes three or four times over, once per division, a sign the business has outgrown a single-hierarchy view.

Build it as a set of small functional charts hung off one executive row: the CEO, then a division lead for each market or product line, then each division's own function heads below. Growth in scope at the top is common as companies add divisions: a widely cited Harvard Business Review analysis of large-company reporting structures found that the average CEO's span of control roughly doubled between the mid-1980s and the mid-2000s, from about five direct reports to almost ten, much of it from folding what used to be separate divisional layers directly under the CEO.

Keep any shared, central function, such as legal or finance, on a dotted line into each division rather than duplicating it as a separate box, and group smaller divisions into a single counted box rather than drawing every one at full depth.

The trade-off: a divisional chart scales to a large, multi-market company far better than the other three shapes, but every division drawn at full depth adds boxes fast, and it is the quickest of the four to turn into the forty-box grid this guide warns against.

How to actually build an org chart slide

What you need before you open PowerPoint

Gather three things before you place a single box. First, the reporting list itself, ideally exported from your HRIS or a simple spreadsheet of name, role, and manager, rather than reconstructed from memory. Second, a decision on depth: which level of the organization the audience needs to see, and where you will stop and group the rest into a counted box. Third, a short list of any matrixed or advisory relationships that need a dotted line, written out as plain sentences, for example "the data lead has a dotted line to the CFO," so the legend describes exactly what is on the slide, not a general policy.

The build sequence

Work top down and level by level, not box by box. Place the single top box first, centered. Add the row of function or division boxes beneath it, evenly spaced and identically sized, joined to the top box by solid reporting lines. Align every box in that row on a shared top edge and vertical center before you add anything below it; misaligned boxes are the fastest way to make a finished chart look unfinished. Add the next row, team boxes under each function, holding the same size rule within that row. Only after the hierarchy is aligned do you add dotted lines for matrixed relationships, plus the small legend that explains them. Last, apply your template's fonts and colors, and condense any branch that has grown past your chosen depth into a single box carrying a headcount.

SmartArt, manual, or one prompt

PowerPoint ships with SmartArt's Organization Chart layout, which is quick for a handful of boxes and worth knowing. It turns rigid the moment a real structure arrives: SmartArt resists a dotted line, resists custom box sizing, and reflows unpredictably as you add roles. Building manually in PowerPoint's own shapes gives full control but costs time on alignment and spacing at any real size. A prompt-driven route through Oria sits between the two: describe the structure in one line of plain text, from the PowerPoint task pane or from Claude and ChatGPT over MCP, and it returns a clean, editable hierarchy of native boxes and connectors, on your template, with dotted lines and a legend handled from the same prompt.

The numbers that have to tie

Any box that reads as a count, such as "240 colleagues across operations," has to reconcile with the real headcount, and a diligence or board audience will check it. Add up every named box plus every counted box within a branch and confirm the total matches the actual team size before the slide goes out; a mismatch of even a handful of people is the fastest way to lose credibility on a slide whose entire job is to be trusted at a glance. The same discipline applies to spans of control: if a single box claims to hold twenty or thirty reports, decide deliberately whether that reflects a real flat team or whether a middle layer has quietly been grouped out of sight.

Mistakes that read as amateur

Prompts to drive the build in Oria

Paste a block, replace the bracketed parts, and run it in Oria's Text to Slide or in Claude when you want the structure written out first.

If your situation is different, build this instead

An org chart is not always the right exhibit, and PowerPoint is not always the right tool. Route yourself honestly before you spend an hour on the wrong one:

Frequently asked questions