Every large organisation runs an induction, and every induction teaches the same things: the systems, the policies, the expenses process, the fire exits. A fortnight later the new starter can submit a timesheet perfectly and still has no idea who to ask about the question that actually matters today.
Ask anyone who has joined a big company what took the time, and you rarely hear about the software. You hear about the people. Who really owns the integration that keeps failing? Which person in compliance can actually say yes? Why does every request to that team take a week, and who is covering them while they are on leave? This is the layer of knowledge that makes an organisation legible, and it is the layer inductions teach worst.
Why inductions skip the important part
The gap is not carelessness. It is that process knowledge is easy to teach and people knowledge is hard.
Processes are written down. There is a wiki page for expenses and a module for security training, so the induction covers them. People knowledge lives in heads: in the programme manager who knows which approver is on compressed hours, in the tech lead who remembers why you never deploy on a Thursday. None of that is on a wiki page, because writing it down is awkward. Describing what Dave really controls, as opposed to what his job title says, feels like gossip even when it is simply the truth.
Acas's guidance on inductions makes the planning point well: a good induction is planned around what the new person needs to become effective, not just around what is easy to present. For most roles in complex organisations, effectiveness means knowing who does what long before you know every process. The induction that ignores the people map is training someone to navigate with the wrong chart.
The cost of learning it by accident
Left to chance, people knowledge takes months to accumulate, and the learning method is expensive: trial and error.
The new starter emails the wrong team and waits three days. They book a meeting with the person whose title sounds right, and learn the real decision-maker is two levels sideways. They ask a question in a channel of two hundred people because they do not yet know the four people who would have answered in a minute. Each of these costs is small. Multiplied across every new starter, every contractor, every person moving teams, they are a standing tax on the whole organisation.
Contractors feel it hardest. A permanent employee has years to absorb the map. A contractor on a three-month engagement needs it in the first week, and every day spent learning who to ask is a day of the day rate spent on navigation instead of delivery.
What a people-first fortnight looks like
None of this requires new software or a new programme. It requires treating the people map as a first-class part of onboarding.
In week one, give the new starter the map explicitly. Not the org chart, which shows reporting lines and little else, but the working map: these are the teams you will deal with, these are the people in them, this is what each one actually owns, this is who to ask when the obvious person is away. A good manager can sketch this in an hour over coffee. Almost nobody does.
Then structure the introductions around ownership, not hierarchy. The standard induction walkabout introduces the new starter to whoever is at their desk. A better version books short conversations with the people whose work touches theirs: the person who approves their requests, the person who maintains the system they will use daily, the person who has been there longest and knows where the bodies are buried. Fifteen minutes each, and the question to ask is always the same: what do you own, and when should I come to you?
And keep the map alive. The single most useful artefact a team can hand a new joiner is a living list of who owns what, including working patterns and leave, updated when things change. Stale people knowledge is worse than none, because it sends the new starter confidently to the wrong door.
The organisation gains more than the starter
Here is the part that surprises teams who build this habit: the map helps everyone, not just the newcomer.
Writing down who owns what surfaces the gaps and the single points of failure. The process that only one person understands stops being invisible. The team that cannot cover its own absence stops being a quiet risk. The contractor finishing next month starts handing over a map instead of a memory.
New starters are simply the forcing function. They arrive needing the organisation to explain itself, and in explaining itself to them, the organisation finally explains itself to itself. The first fortnight is the best opportunity you will ever get to build that map. The process training can wait a week. The people cannot.