Why the chart is worth drawing
Drawing the structure exposes things that are invisible in a directory. Managers with eleven direct reports, layers that exist for one person, teams whose work is entangled but who report through entirely separate branches, contractors doing core work at the edge of the diagram. None of that is visible in a list of names, and all of it shows up the moment the boxes are stacked.
For newcomers, the chart is orientation: it tells them who owns a decision and who to escalate to. For anyone planning a change, it is the map the plan gets drawn on — and comparing the current chart against the one you would design from scratch is a fast, uncomfortable, useful exercise.
What a chart does not show
The reporting line is a claim about accountability, not about how the work moves. In most organizations the real flow of decisions crosses the chart constantly: the person everyone consults before shipping may be three branches away and two levels down. Read a chart as who is accountable for whom, and do not mistake it for who talks to whom.
It also says nothing about capability, load or influence. Two peers on the same line can have completely different scope. And it goes stale faster than almost any other document in a company — an org chart that has not been touched since the last reorganization is actively misleading, which is a good argument for keeping it somewhere easy to edit rather than in a slide deck someone has to find and unlock.
Building one that stays readable
Use roles rather than titles where they differ. 'Runs onboarding' orients a newcomer; 'Manager II' does not. Keep each box to a name and one short line — charts fail through width, and a box carrying three lines of responsibilities forces the whole tree wider than a page.
If the tree is getting unmanageably wide, that is usually information rather than a formatting problem: either a manager has too many direct reports, or you are trying to fit the whole company on one page when you should be drawing one department at a time. Splitting by department and linking the charts together generally beats one enormous diagram nobody can read.
Where someone genuinely reports to two people, pick the primary line for the chart and record the second relationship in the role text. Charts that try to draw matrix reporting as crossing lines become unreadable at about the fourth line.
Nothing leaves your browser
Staff names, roles and reporting lines are ordinary internal information right up until they are being used to plan a restructure, at which point they are among the most confidential things you will type all year. This tool makes no network request with your content: the chart is held in your browser's local storage and nowhere else, and deleting it removes it.
That is also why there is no share link. If you want the chart on a canvas you can reach from another device, the save button hands it to your OmniCanvas account explicitly; until you press it, nothing has been transmitted.