How to Make an Org Chart Diagram (Step by Step)

Published October 31, 2026 · Updated October 31, 2026 · 8 min read · by the Sakura5 team

To make an org chart diagram, list every person or role in a simple table with one column for who they report to, find the single person at the top, group everyone else by manager, then draw it top-down: one box per role, one line from each box up to its manager, and every box at the same management level on the same row. Build the list first and the drawing second, and the chart almost draws itself.

An org chart answers two questions at a glance: who does what, and who answers to whom. When it’s wrong or cramped, people stop trusting it and go back to asking around.

This guide covers why most first attempts turn messy, a six-step method that works in any tool, a full worked example for a 24-person company, the awkward cases (dotted lines, shared roles, vacancies) and a short FAQ.

Why org charts get messy on the first try

The usual approach is to open a diagram tool, drop the CEO box at the top and start adding people from memory. That works for about ten boxes. After that, three problems show up.

• The reporting lines are guessed. You draw who you think reports to whom. Then someone points out that the office manager reports to finance, not operations, and half a branch has to move.
• One team swallows the page. A manager with nine direct reports stretches a row so wide that the rest of the chart shrinks to fit.
• Names and roles get mixed up. Some boxes say “Sarah”, some say “Head of Sales”, some say both. When a person leaves, nobody knows whether to delete the box or just the name.

All three come from the same mistake: treating the org chart as a drawing problem when it’s really a data problem. The structure is a hierarchy, and a hierarchy is easy to get right as a list before it becomes a picture.

How to make an org chart diagram, step by step

These steps work whether you finish in PowerPoint, Visio, a whiteboard or a slide deck.

1. Decide what the chart is for

A chart for new starters needs names, photos and maybe a line of responsibility. A chart for a reorganisation needs roles and headcount, not names. A board pack usually wants only the top two or three levels. Pick one purpose; it decides how deep to go and what goes in each box.

2. Build a two-column list: role and manager

Write every role on its own line with the role it reports to next to it. A spreadsheet is fine. Use role titles as the primary label and the person’s name second, so the chart survives the next hire. Have each team lead confirm their rows.

3. Find the root and group by manager

Exactly one role should have no manager. Everyone else sorts into groups under their manager. If you find two roles with no manager, you either have co-founders or a gap in the data; decide which before drawing.

4. Count levels and the widest row

Count how many layers sit between the top and the most junior role, and which manager has the most direct reports. Those two numbers decide whether the chart fits on one landscape page or needs splitting into a top-level chart plus one chart per department.

5. Draft the hierarchy as a tree

Draft the structure somewhere that lets you move whole teams without redrawing lines. A mind map works well for this because a reporting structure is already a tree: the top role in the center, each direct report as a branch, their teams as sub-branches. In Mindmap AI you can type the roles in as nodes, drag a whole branch to a new manager when the list turns out to be wrong, and switch to the outline view to read the hierarchy as an indented list. You type the structure yourself — the app doesn’t know your company — but moving a department takes a second.

6. Draw the final top-down chart and check it

Copy the structure into your final tool as a top-down chart. Keep every box the same size, put peers on the same row, and use straight elbow connectors from each manager down to a horizontal bar above their team. Then tick every role on your list against the chart. Any role without a tick is missing.

A worked example: a 24-person software company

Say Amara is the operations lead at Lumen Labs, a 24-person software company. The founders want an org chart for the new-starter handbook, with role, name and team on each box.

The list. Amara exports names from the payroll system and asks each lead to confirm reporting lines. She ends up with 24 rows. The CEO has four direct reports: CTO, Head of Product, Head of Sales and Amara as Operations Lead. Under the CTO sit two engineering managers, each with five engineers, plus a solo designer who reports straight to the CTO. Head of Product has one product manager. Head of Sales has three account executives. Amara has one finance and admin coordinator.

The check. Counting gives 1 + 4 + 2 + 10 + 1 + 1 + 3 + 1 = 23. One person is missing. The confirmation round finds it: a customer support specialist who was on payroll but whom nobody had listed, because she was hired in the gap between two managers. She reports to Head of Product. Now the count is 24.

The shape. Four levels deep. The widest row is the engineers: ten boxes. On one landscape page that makes the bottom row cramped, so Amara draws the main chart down to the engineering managers only and labels each with “+5 engineers”. A second page shows the full engineering team. Every other team fits on page one.

The draft. In the mind map, the CEO goes in the center with four branches. When the designer turns out to be shared between product and engineering, Amara drags the node from the Head of Product branch to the CTO branch — where payroll says the role sits — and notes the product work as a dotted-line relationship for later. The outline view gives her the indented list she pastes into the handbook draft for the founders to approve.

The final chart. She rebuilds it top-down in the company’s slide template: two pages, 24 boxes, role in bold, name underneath.

Awkward cases: dotted lines, shared roles and gaps

Real organisations rarely look like the textbook pyramid. The chart’s job is to stay readable anyway.

Dotted-line reporting

When someone reports to one manager but takes day-to-day direction from another, draw the formal line solid and the second one dashed, and add a one-line key. Keep dotted lines to a handful; if half the chart needs them, a matrix structure is a better fit for a table than a tree.

Vacancies and interim roles

Keep the box and write “Vacant” or “Interim: name” in it. Deleting the box hides the gap, and the people under that role suddenly appear to report to nobody.

Assistants and advisers

Executive assistants and advisory roles usually hang off the side of their manager’s connector rather than sitting in the row below, which signals support rather than a layer of management.

Charts that are too big

Past roughly 30 to 40 boxes, split the chart: one page for the top levels, then one page per department with the department head at the top. The same idea works for project scope — see our guide to creating a work breakdown structure mind map, which uses the same split-by-branch approach.

Which tool to use for the final chart

For a small team, a slide tool’s built-in hierarchy layout is enough. PowerPoint and Word both have SmartArt organization chart layouts, and Microsoft documents them in its guide to creating an organization chart with SmartArt. For hundreds of roles, a dedicated diagram tool that can import a spreadsheet will save hours, because the role-and-manager list from step 2 is exactly the format those imports expect.

Whatever you finish in, the drafting step is where most mistakes get caught. A tree you can rearrange freely is the fastest way to argue about structure before anyone polishes boxes. If you’re mapping something more personal than a company, the same method applies to making a family tree diagram, with generations in place of management levels. And Mindmap AI with Pro can export the outline as a PDF, which makes a handy one-page reference of every role to send round for sign-off.

FAQ

What is the easiest way to make an org chart?

Start with a list, not a drawing. Write every role with the role it reports to, confirm it with team leads, then use a hierarchy layout in PowerPoint, Word or a diagram tool to draw it top-down. Building the list first means the chart is right before you spend time making it look tidy.

Should an org chart show names or job titles?

Show job titles first and names second. Titles describe the structure, which changes slowly; names change every time someone joins or leaves. Putting the role in bold and the name underneath keeps the chart useful for longer, and makes vacancies obvious because the role box stays even when the name is gone.

How do you show dotted-line reporting on an org chart?

Draw the formal reporting line as a solid connector and the secondary relationship as a dashed one, then add a short key explaining the difference. Use dotted lines sparingly. If many roles have two managers, the organisation is closer to a matrix, and a table usually explains it better than a tree diagram.

Can I use a mind map to make an org chart?

Yes, as the drafting step. A reporting structure is a tree, so a mind map with the top role in the center and each team as a branch captures it accurately and lets you move teams around easily. For the final version, most people redraw it top-down, because that is the layout readers expect from an org chart.

← All articles