Creating an org chart takes an afternoon. Creating an org chart that is accurate takes considerably longer - and maintaining one that stays accurate is something almost nobody manages. This guide shows you what a good org chart delivers, which tools suit which purpose, and how to proceed step by step. It also names the point most tool comparisons keep quiet about: the maintenance problem that sinks nearly every org chart.
What a good org chart shows - and what it doesn't
An org chart answers three questions at a glance: Who belongs to which department? Who reports to whom? And where does responsibility for a topic sit?
That sounds trivial, but it isn't. In a machine-building company with 80 people, the management team usually still knows who belongs where. The new head of sales doesn't. Neither does the bank that wants to see an organizational overview as part of a financing deal. And the auditor in an ISO 9001 audit will ask for it specifically.
Just as important is what an org chart does not show:
- How work actually flows. The fact that Ms. Weber formally sits in accounting but in practice handles half of order processing doesn't appear in any box.
- Who carries which knowledge. The org chart shows positions, not the single points of knowledge behind them - which knowledge depends on one individual person doesn't appear in any box.
- Informal decision paths. In many family businesses, the real decision-making runs right past the formal lines - the senior owner still has a say, even though he no longer appears in any box.
An org chart, then, is a map of the formal structure. Anyone who mistakes it for lived reality is planning past their own company. We'll come back to that.
The classic approaches compared
PowerPoint and Canva: quick to build, instantly outdated
The most common route in mid-sized companies: someone on the admin team builds the org chart in PowerPoint. Insert a SmartArt hierarchy, type in the names, done. Canva works similarly and, with ready-made org chart templates, even produces prettier results.
Strengths: No new tool, no cost, anyone can use it. For a one-off presentation - a bank meeting, a trade show, a company introduction - entirely sufficient.
Weaknesses: The file lives on a shared drive and has to be touched by hand with every personnel change. In practice, that doesn't happen. After the second departmental move and the first resignation, the slide shows a state of affairs that no longer exists. And because nobody knows which of the four file versions ("OrgChart_final_NEW_v3.pptx") is the current one, in the end nobody trusts any of them.
Diagramming tools like Lucidchart and draw.io: prettier, same problem
If you want something cleaner, you reach for specialized diagramming tools. draw.io (diagrams.net) is free, runs in the browser, and exports clean PDFs and PNGs. Lucidchart does more: data import from spreadsheets, automatic layout, real-time collaboration. Miro and Visio fall into this category too.
Strengths: Professional look, automatic arrangement of the boxes, and with Lucidchart even the option to generate the org chart from an employee list. For organizations of about 50 people and up, considerably more pleasant than PowerPoint.
Weaknesses: The maintenance problem stays exactly the same. The data import is a snapshot - when the organization changes, someone has to repeat the import or update things by hand. The tool is better, but the process behind it is identical: a human has to remember to do it, and that is precisely the breaking point.
HR software: up to date, but without context
Personio, HRworks, Factorial, and similar HR systems generate the org chart automatically from master data. When someone is hired or changes departments, the picture updates itself.
Strengths: The freshness problem is solved - as long as the master data is maintained, the hierarchy is correct. For companies that plan to introduce HR software anyway, the org chart is a sensible byproduct.
Weaknesses: First, the price: introducing an entire HR suite just for the org chart isn't worth it. Second, and this weighs heavier: HR software shows the formal hierarchy and nothing else. Who reports to whom - yes. Who actually owns which processes, who carries which knowledge in their head, which role is effectively filled twice and which not at all - on that, the system is silent. It reflects what's in the master data, and master data knows only positions, not reality.
Step by step: an org chart that matches reality
Whichever tool you choose - the real value is created during the fact-finding, not the drawing. Here's how to proceed:
Step 1: Define the purpose
An org chart for a bank meeting needs departments and leadership positions, nothing more. An org chart for succession planning or a QM audit needs every role down to team level. Decide up front what the picture is for - that determines the altitude.
Step 2: Capture roles, not just positions
First, collect the roles that exist in the company - regardless of who holds them. "Quote preparation," "incoming goods inspection," "IT administration." In a 60-person company, that quickly adds up to 40 to 80 roles, considerably more than positions. That difference is exactly what's interesting: a person carrying six roles is a risk. A role that nobody carries is one too.
Step 3: Ask the people, not the job descriptions
This is where the wishful picture parts ways with reality. Job descriptions say what someone should do. Instead, ask the employees themselves: "What do you do in a normal week? Who do you hand results to? Who comes to you for advice?" You will find discrepancies - the warehouse manager who also runs the vehicle fleet on the side; the clerk who de facto does the vacation planning for the whole department. These discrepancies are not errors in the org chart. They are the most valuable part of it.
Step 4: Clarify reporting lines - including the uncomfortable ones
Draw the formal line (who has managerial authority) and note separately where the actual functional control deviates from it. If three people say "really, Mr. Krause decides that," but Mr. Krause holds no leadership position, you've learned something no template will tell you.
Step 5: Make gaps and pile-ups visible
Now the role list pays off: mark roles with nobody in them (open flanks), roles with exactly one knowledgeable person (bus factor of 1), and people with a conspicuously high number of roles (overload and absence risk). An org chart that shows these three things is a management instrument. One that only shows boxes is decoration.
Step 6: Draw it - and put an expiration date on it
Only now does the tool come in. And write the date on it: "As of: March 2026." Not out of tidiness, but out of sober realism - which brings us to the catch.
The honest catch: every org chart starts going stale the day it's finished
Here is the point tool comparisons like to skip over: an org chart is a snapshot of something that is constantly moving. The day you finish it, it starts to go stale. Someone resigns. A team gets restructured. A role quietly migrates from one person to the next because it happened to be convenient. Six months later, your carefully crafted picture shows a company that no longer exists - and the knowledge from the conversations in step 3 has gone stale along with it.
The problem isn't the tool. The problem is that maintenance remains a manual task that always lands behind day-to-day business on the priority list. HR software solves this only for the formal hierarchy - the interesting layer, who really does what and knows what, goes unmaintained there too.
The only real way out: a source that updates itself, because the update falls out as a byproduct of something that happens anyway.
That is exactly how wissa.ai works: an AI conducts 15-to-20-minute chat interviews with your employees - no workshops, no questionnaires - and works its way from one knowledge holder to the next, snowball-style. From these conversations, the org chart emerges automatically: who does what, who reports to whom, which roles are unfilled. Because the interviews keep running, the picture keeps itself current with every conversation - including contradiction detection when two people describe a responsibility differently, and every statement remains traceable to its source. The org chart is then no longer a document someone has to maintain. It's a live reflection that keeps pace.
Conclusion
For a one-off presentation, an org chart template in PowerPoint or Canva is enough. If you want it permanently nicer, take draw.io or Lucidchart - and accept that someone has to own the maintenance. HR software keeps the hierarchy current but knows only positions, not reality. The real value is created not in the drawing anyway, but in the asking: who really does what? And if you want those questions answered not once but continuously, you need a source that updates itself.
If you'd like to try that: wissa.ai is available as an early beta for €149 per month (12 interview credits, free for interviewees, GDPR-compliant with EU hosting). Join the beta waitlist - the first org chart emerges from the first interviews.
FAQ
Which tool is best for creating an org chart?
It depends on the purpose. For a one-off presentation: PowerPoint or Canva with a ready-made template. For larger org charts in regular use: Lucidchart (with data import) or the free draw.io. For permanently current hierarchies: HR software like Personio, provided it's in use anyway. None of these tools, however, shows who actually carries which tasks and which knowledge - that requires asking the employees themselves.
Are there free org chart templates?
Yes. PowerPoint ships with built-in hierarchy layouts via SmartArt, and Canva and draw.io offer free org chart templates to customize. For small companies up to about 30 people, that's entirely sufficient. Just keep in mind: the template solves the drawing problem, not the maintenance problem.
How often should an org chart be updated?
With every personnel or structural change - in practice, that means continuously. Realistically, most companies manage one update per year, often triggered by an upcoming audit or bank meeting. That's why it pays to either assign the maintenance firmly to one person or switch to a source that updates itself automatically.
What is the difference between an org chart and a role overview?
The org chart shows the formal structure: departments, positions, reporting lines. A role overview shows which packages of work exist and who actually carries them - independent of position. In mid-sized companies, one person often carries many roles, and some roles are carried by nobody. Only both views together reveal where absence risks and overload sit.
Does the works council need to be involved in creating an org chart?
A plain org chart is generally not subject to codetermination. But as soon as you systematically survey employees or use software that processes personal data, it is wise - and depending on the setup, legally required - to involve the works council early. Transparency about purpose and data use takes the edge off the project - tools with GDPR compliance, EU hosting, and traceable sources make that conversation easier.