Employee directory and org chart: ending the "who do I ask?" question

The most frequently asked question in a company isn't technical: "who do I ask about this?" For a new joiner it fills the first week; for everyone else it costs a few minutes each week. That is exactly why a corporate directory exists — and why a spreadsheet doesn't replace one.

Why a spreadsheet isn't enough

A shared staff list breaks in three places. It goes out of date — updating the file when someone leaves is nobody's job. It carries no context — it doesn't know what a person does, who they report to, or whether they are available right now. It isn't searchable — someone typing "accounting" won't find the person whose title is "chartered accountant".

An intranet directory solves all three, but the first is the critical one: staying current must not depend on manual upkeep.

Directory synchronisation

The sustainable answer is for the directory to connect to your identity directory (Entra ID, LDAP) instead of keeping its own list. A title change is made in the HR system and the directory follows. Someone disabled in the directory drops out here too.

The critical decision is how far the sync goes. Our approach: matching profiles are updated, and people present in the directory but not in the system are only reported — no accounts are created automatically. In a directory of 4,000 people, "turn on the sync" would otherwise mean creating 4,000 accounts, and that is hard to undo.

The org chart: more than hierarchy

An org chart is usually treated as an HR document; in daily work it answers two concrete questions: whose approval does this need, and who runs this team? Being able to see the management chain also makes it easier to understand where an approval request is stuck.

Keeping the chart current again depends on the directory connection. A hand-drawn org chart is correct on the day it is drawn and wrong three months later.

Availability status

The most used and least discussed feature of a directory is the status indicator: in the office, on leave, in a meeting, working remotely. It looks trivial; in practice it shortens the "I called, couldn't reach them" loop.

There is a privacy balance here. Status should be the employee's own declaration — a system that infers status from location or calendar feels like surveillance and damages trust.

Skills and profile text

What really makes a directory powerful is the record of what a person knows. Skill tags and a short bio make "who do I ask" answerable independently of job titles. Not everyone in the finance department knows about export invoicing; the way to find the person who does is expertise, not title.

There is one step built on top of that: matching a plain-language question against people's profile text by meaning. We built the expert finder for exactly that need.

Department pages

The natural extension of the directory is a micro page for each team: who works there, what the team does, which documents and announcements belong to it. For a new joiner this page is a faster orientation tool than the org chart.

A department page is also the natural ground for content targeting: routing an announcement to "Finance" makes it appear on that team's page too, so information sits both in the feed and permanently in the right place.

What to watch for under data protection law

A directory is a component that processes personal data. Three practical rules:

1. Data minimisation. Don't collect personal mobile numbers while a company line exists.
2. Birthdays. Day and month are enough for celebrations; the year isn't needed.
3. Export permissions. A permission that allows downloading the entire employee list is in practice a leak risk and should be open only to the roles that need it.

We cover the whole topic in our compliance article.

Measurement

The fastest way to tell whether the directory works is to look at search logs: which names and which skills were searched, and which searches returned nothing? Unsuccessful searches point directly at what's missing — usually skill tags or department naming.

A second useful number is profile completeness: a profile with an empty skills field makes the directory's most valuable feature unusable.

We recommend switching the directory on as one of the first three modules; the reasoning is in the 90-day plan.