Every large organisation has two structures. The first is the official one: reporting lines in the HR system, neat boxes and arrows, job titles that sound decisive. The second is the real one: who actually approves a firewall change, who the only person is that understands the legacy feed, who never answers email but walks the floor on Thursdays.
If you have ever joined a big company as a contractor or a new starter, you already know which of the two determines whether your first month goes well.
Why the official map fails
Org charts are built for HR, not for work. They answer "who do I report to?" — a question that matters exactly once. The questions that matter every day are different:
- Who owns this? The service owner on paper left eight months ago. Someone inherited it. Good luck finding out who from the intranet.
- Who can unblock this? Your project is stuck on an InfoSec review. Which of the 14 people in the security team actually signs off network changes?
- Are they even in? The approver works Tuesday to Thursday. Your deadline is Friday.
None of that lives in the org chart. It lives in tribal knowledge — and tribal knowledge walks out the door every time a contractor rolls off.
The cost of not knowing
Delivery teams quietly budget for this. The first two weeks of a contractor's engagement are largely spent interviewing people to reconstruct a map that has been built dozens of times before. It is the single most repeated, most wasted effort in corporate life — and it is entirely avoidable.
The bottom-up alternative
The fix is not a better org chart. It is a different kind of map — built by the people doing the work, for the people doing the work:
- People with real remits. "Sarah Chen — approves production releases for payments" beats "Sarah Chen — Senior Manager II".
- Departments with SLAs. What they control and how much notice they need, in plain language.
- Working patterns and leave. So "who do I ask?" always comes with "and are they in this week?".
- Blockers linked to resolvers. So the answer to a stuck project is a name, not a meeting.
One person can map their immediate ecosystem in about ten minutes. A squad that shares the map gets something rarer: organisational memory that survives the next leaver.
That is the bet behind OrgBearings — a live map of who does what, who's in, and who covers them. Free to start, no IT sign-off required.