Onboarding Ends at Access. The Institutional Context That Would Have Prevented the Mistake Lives Somewhere Else.

I move fast. It is a core operating pattern: when the structural problem is visible, the instinct is to act on it immediately. In my current position I had to hold that instinct back, deliberately, for longer than felt right. Not because the business is fundamentally different from others I have led. Because the context I needed to move correctly was not in any document I had been given. It was in Jira comment chains from years before I arrived: the reasoning behind decisions already in place, the approaches that had been tried and quietly abandoned, the constraints that had shaped what the system became. The context was not inaccessible. It was buried. You would need to already know what you were looking for before you could find it.

The standard onboarding prescription comes in two forms. The first is “ask questions and figure it out,” which treats leadership knowledge as information transfer: proximity to the right people produces the right answers, and the new leader absorbs what they need through access and conversation. The second is formal training. As a Career Manager for Avanade, I was sent to Accenture’s training facility in Chicago. The curriculum was focused on customer management: the external interface, the visible business need. The discipline of managing people directly, organizational dynamics, team psychology, coaching, the judgment that directing reports actually requires, was not the curriculum. It was not what the training was built to transfer.

Leadership is a discipline with specific components. Organizational dynamics, team psychology, coaching, decision architecture: the judgment that comes from understanding how people and systems behave under pressure. None of that transfers through informal question-asking, because the people being asked often do not know what they know. Frequently, the people who know it best have already left.

What needs to transfer, and almost never does, is two things. The Why: the reasoning behind decisions already in place. Why the system was built this way. Why that approach was abandoned. Why that constraint exists. Without the Why, a new leader makes decisions that look reasonable in isolation but contradict the organizational logic established before they arrived. The second is what was tried and did not work: the negative space. The approaches that seemed sound, were attempted, and failed for reasons now invisible. Without it, the new leader rediscovers the same dead ends and pays a trust cost for appearing to not understand the situation, even when their logic was correct.

That trust cost is the mechanism. When a new leader moves without the Why, the team reads it as not understanding what they have been through: dismissiveness or incompetence, even when the decision was technically sound. The leader incurs a deficit they did not earn and may not know they have incurred. Recovering it takes longer than acquiring the context would have.

The organization that cycles through this pattern (new leader, early friction, trust cost, extended recovery) almost always attributes the problem to the leader. Wrong fit. Moved too fast. Did not read the room. In some cases that is accurate. The more precise diagnostic is available from a simpler question: was the decision that produced the friction reasonable given what the leader knew on day one?

If the answer is yes, and the decision made sense with the information that was available, the problem was not the leader’s judgment. It was the context that was never designed to transfer. Good judgment applied to incomplete inputs produces recoverable mistakes. The leader who makes bad decisions with full context is a fit problem. The leader who makes good decisions with wrong inputs is a Continuity design problem.

Onboarding is not a training problem. It is a Continuity design problem: context, decisions, and reasoning that live in someone’s memory rather than a designed transfer structure disappear at departure and reappear as costly reconstruction work for the next person. The organizations that stop cycling through early-leader friction are not the ones with better onboarding programs. They are the ones that decided which Why and which what-was-tried the new leader needed in the first 90 days and built a structure to move it rather than assuming it would travel through conversations, calendar access, and a Jira account.

I write about structural leadership for technical leaders in high-stakes operating environments. If this way of thinking resonates, it runs deeper in LeadershipOS: http://TheLeadershipOSBook.com

---

I write about structural leadership for technical leaders in high-stakes operating environments. If you're reading this outside the daily email, subscribe free: https://technicalleader.coach/daily-email