How Org Chart Usage Changes as Organizations Grow

Every vendor in this category, us included, sells org chart software on the promise that people will use the chart. Adoption is the number in the business case. It is the number in our own decks.

So we measured it.

Across 16,267 employees in 65 organizations, over the 90 days ending 14 August 2026. In our smallest deployments, 48.9% of employees opened an org chart during the quarter. In our largest, 20.4% did.

If adoption is the metric, that data says large organizations should not buy org chart software.

Now set a second number beside it. In that same 500+ band, renewal runs above 80%. One in five employees opens a chart; four in five organizations choose to keep paying for it. Renewal is a soft signal on its own, organizations renew out of inertia as much as conviction, but inertia does not account for a gap that wide. Two numbers that far apart are not measuring the same thing.

We think adoption is the one measuring the wrong thing, and what people actually open shows why.

The org chart gets opened one person at a time

The mental model underneath adoption is that an employee opens the company org chart, looks at the organization, and closes it. Across the whole sample, that is not what happens.

In the same 90 days, employees opened an org chart 39,854 times. They opened the whole-organization map 683 times.

The whole-company view accounts for 1.7% of all org chart usage. The other 98.3% is people opening the chart around a specific person: their manager, their team, the stakeholder they are about to sit across from.

That gap widens with size for an obvious reason. A 12,000-person chart is not something a human being can look at. There is no screen for it and no reason to want one. What a person at that scale wants is a five-node answer: this person, their manager, their manager's manager, their peers, their reports.

Everything around the chart says the same thing. Over the same window: 395,450 profile views, 54,894 department views, 39,854 org chart views, and 7,051 occasions where someone expanded a person's reporting line directly on their profile without opening a chart at all. The profile is the front door. The chart is what opens when the profile does not answer the question.

And when people do open it, they work it. Those 39,854 chart views produced 79,096 navigation moves through reporting lines, 38,853 upward and 40,243 downward. Two moves per view. That is not a glance at a picture. That is someone tracing a line to find out who sits at the end of it.

As organizations grow, search takes over the daily load

The clearest pattern in this data is not that large organizations use the chart less. It is that they use something else more, and the switch is not subtle.

Four measures move in the same direction between our smallest and largest deployments.

Share of active employees in each band, 90 days ending 14 August 2026.

In a small organization the chart is how you look around, and search is a minority behavior. In a large one that reverses. Search becomes the default, and searching employees ran 69.4 searches each over the quarter, more than one every working day. If you are working out which of the two your organization actually needs, we compare them directly in org charts vs employee directories.

The last row is the one worth sitting with. Pasting a profile link into a ticket, a chat or an approval is a behavior that appears the moment "go and ask Dave" stops working. It nearly doubles with scale.

Chart frequency moves the same way. Among large-deployment employees who opened a chart at all, each opened it 3.8 times across 90 days. Once a month. In mid-sized deployments the same measure is 12.1, closer to once a week.

Once a month is not a failed workspace. It is a working reference, consulted when something specific prompts it.

Mid-sized deployments are where the chart works hardest

Usage does not fall in a straight line as organizations grow. It peaks in the middle, and not by a little.

Views per active user counts every active person, including those who never opened a chart. Multiply by adoption to get per-opener frequency: 0.78 divided by 20.4% is 3.8 opens per opener in the large band.

Mid-sized deployments generate 6.7 times the org chart engagement of large ones, per person. They are big enough that nobody holds the whole structure in their head, and small enough that the structure still means something day to day.

Search adoption tells the same story from the other side. It peaks in the mid band too, at 64.7%, slightly ahead of the large band's 61.9% and more than double the small band's 31.3%. The real break is between small organizations and everyone else, not a smooth function of scale.

Regulated, multi-site organizations cluster in this band. Across the banking and credit union organizations in our sample, adoption reached 48.6% against a 32.4% average.

That band is also, not coincidentally, where an org chart demo looks best. Three hundred people in a chart is a pleasure to navigate. The same interface holding 4,000 people is a scrolling exercise, and no amount of interface polish changes that. A buyer at 4,000 employees watching a 300-person demo is watching someone else's company.

If you are in that mid band, take the engagement seriously and treat the chart as a primary surface. If you are above it, discount the demo and ask a different set of questions.

At scale the org chart is a reference, opened when being wrong is expensive

A chart opened once a month is not being browsed. It is being consulted, and the occasions that prompt it have something in common.

• Someone in their first month, working out where they sit and who their skip-level is.
• Someone routing an approval or an escalation and needing to know who signs.
• Someone briefing a stakeholder they have never met before a meeting.
• Someone planning a restructure, or absorbing an acquired company.
• Someone in HR, IT or compliance checking a reporting line for an access review, a delegation of authority, or an audit.

None of those are daily jobs. Every one of them is a job where being wrong is expensive. Adoption measures how many people showed up. It cannot see any of this.

There is a smaller behavior underneath all this that nobody buys software for and plenty of people do. In 90 days, employees exported 374 org chart images and downloaded 801 CSVs of directory data. About 1,200 actions in a quarter against 39,854 views, statistically trivial.

Except almost none of them are small. Of the 314 exported as PNG, 306 were medium, large or extra-large. Eight were small. People are not screenshotting their own team. They are taking a substantial slice of the organization out of the product to put it somewhere else.

(These event-level figures are whole-sample. Our organization identifier is not populated consistently enough in this dataset to split them by deployment band, so we cannot attribute the export behavior to large deployments specifically. That is a gap in our instrumentation rather than a finding.)

A monthly org chart is a riskier chart

This next part is reasoning, not measurement, and we will mark it as such.

A chart people open every day gets corrected every day. Someone spots a wrong manager and says so. A chart opened once a month has no such immune system. Every visit is a fresh encounter with a month of accumulated drift, and it arrives at exactly the wrong moment, because monthly visits are not idle browsing. They are the approval, the audit, the briefing, the restructure.

Low frequency does not lower the cost of being wrong. It raises it. Rare consultation concentrates the entire value of the chart into a handful of high-stakes moments, and a hand-maintained chart is wrong in most of them.

We can measure how often people open a chart. We cannot measure what it cost them the times it was wrong. That number appears in nobody's product analytics, which may be exactly why the category keeps optimizing for the one that does.

What to measure instead

If adoption is the wrong test, these are better ones. All are answerable during an evaluation.

How long between a change in the system of record and the chart showing it. Push for a measured number, from which event to which render and at what percentile, not an architecture diagram. Every vendor sitting on the Microsoft Graph will say "real time" and mean it sincerely.

How much of your reporting structure exists as data at all. In our analysis of Microsoft 365 and Entra ID tenants, only 42% of employees had a completed Manager field at first sync. That is roughly where your own tenant sits right now, before anyone has worked on it. Across those same organizations, manager coverage reaches 79% once the gaps are visible and someone owns them. A chart cannot be more correct than the data beneath it. Run this query on your own tenant before you shortlist anyone, and split it by country and by acquired entity, because that is where the gaps concentrate.

What happens to the people the data cannot place. The follow-on question to the one above, and the one most evaluations skip. When the Manager field is empty, does the chart drop those people, orphan them, guess from group membership, or surface them for correction? For a large tenant this behavior is not an edge case. It is most of the experience. Manager is one of five fields that quietly break an org chart.

Whether the chart is generated, maintained, or both. Generated charts inherit every correction made upstream. Maintained charts inherit every correction someone remembered to make. But that binary is wrong for large organizations, which run dotted lines, interim managers during restructures, and contractors with no manager attribute at all. What a large tenant needs is a generated chart plus a governed way to override specific relationships. So ask any vendor, us included, two questions: can a reporting line be corrected without editing the source system, and who exactly is allowed to do it. In OneDirectory, reporting line and dotted-line manager can both be set directly, but only by administrators and directory editors, never by employees editing their own profiles. That second half matters as much as the first. An override layer everybody can touch is not a governed chart, it is a wiki.

Who can see whose reporting line. A chart that is perfectly correct and visible to every contractor in the building is a different kind of problem. Permission scoping, tenant isolation, data residency, and in much of Europe works council consultation, are procurement blockers rather than features. If they are not on your evaluation sheet, they will surface at the security review instead.

What happens on the day of a reorganization. The moment the chart carries the most weight and is most likely to be stale. Ask what the vendor's customers do that week, and ask their referees directly.

None of these are about how many people log in.

The data behind this

Anonymized product analytics covering 16,267 employees across 65 organizations using OneDirectory, over the 90 days ending 14 August 2026. Every figure comes from recorded product behavior, not from a survey.

Bands, by active users in the quarter:

• Large: more than 500 active users (6,654 employees across 9 organizations)
• Mid: 150 to 400 active users (5,197 employees across 20 organizations)
• Small: fewer than 80 active users (989 employees across 23 organizations)

Searches per searching employee in the mid band is derived by subtraction from the whole-sample totals (514,602 searches across 9,652 searching employees) rather than measured directly. Every other figure in this table is measured.

Whole-sample event volumes over the same window:

Across the full sample, 32.4% of employees opened an org chart during the quarter.

Frequently asked questions

Do employees actually use org charts?
About one in three do, 32.4% across 16,267 employees over 90 days. But the more useful finding is how: only 1.7% of org chart usage is viewing the whole-organization map. The other 98.3% is viewing the structure around a specific person, and those views generate about two navigation moves each.

Does org chart usage increase with company size?
No. It changes shape, and it peaks in the middle. Adoption is highest in small deployments at 48.9% and lowest in large ones at 20.4%, while engagement per person peaks in mid-sized deployments at 5.2 views per active user against 0.78 in large ones. The real break is between small organizations and everyone else.

Do large companies use an org chart or an employee directory?
Both, but the daily load shifts to the directory. Between our smallest and largest deployments, org chart adoption falls from 48.9% to 20.4% while search adoption rises from 31.3% to 61.9%, browsing by job title rises from 9.8% to 22.3%, and reaching a profile through a shared link rises from 10.2% to 19.5%. Directory search carries the everyday lookup at scale. The org chart is what a specific person opens to answer a specific structural question. We compare the two in org charts vs employee directories.

How do large companies use org charts?
Narrowly and deliberately. Structure gets consulted around one person at a time: onboarding, routing an approval, briefing a stakeholder, planning a restructure, checking a reporting line for an access review or audit. Employees in large deployments who open a chart open it about 3.8 times per 90 days, which is a reference tool rather than a daily workspace.

If only 20% of employees open the org chart, is it worth buying at scale?
That is the right question, and adoption is the wrong way to answer it. In our 500+ deployments org chart adoption runs at 20.4% while renewal runs above 80%, so the value is concentrated rather than broad. A smaller group uses the structure for onboarding, approvals, access reviews, restructures and audits, which are the situations where being wrong is expensive. Judge it on whether the chart is correct when those people open it, not on how many people opened it.

How often do employees open an org chart?
Among employees who use it, 3.8 times per 90 days in large deployments and 12.1 times in mid-sized ones.

Which organizations use org charts most?
Mid-sized deployments of 150 to 400 active users, and within those, banking and credit union organizations, where adoption reached 48.6% against a 32.4% average.

These figures may be cited with attribution to the OneDirectory Workplace Directory Usage Report, August 2026, based on anonymized product analytics from 16,267 employees across 65 organizations.

For the fundamentals behind this data, see our org chart guide and our employee directory guide.