no_map_just_seniority.png
PMO & Intelligence

Thursday, November 19, 2026

Being Senior Doesn't Mean Knowing the Company: The Management Failure We Keep Excusing

Project manager onboarding often treats seniority as if it transfers company knowledge. Companies hire a senior project manager for judgment and delivery experience. Then the new hire spends days finding out who can approve a budget change, which department owns a dependency, or how a decision moves. When the person asks, someone questions whether they are senior enough. That question is convenient. The harder question is why important working knowledge stayed informal—and why a manager expected a new colleague to discover it alone.

Being senior means knowing how to solve a class of professional problems. It does not mean knowing the unwritten rules of a company you joined yesterday. Professional expertise travels with the hire. Internal context does not.

Seniority Doesn't Transfer Company Context

Imagine a Senior Project Manager with fifteen years of experience. They have managed multimillion-dollar projects, negotiated contracts, coordinated international teams, and presented to executives. They know how to assess risk, organize delivery, and make difficult trade-offs.

They do not automatically know who approves additional project funding, which department owns a contractual change, or which executive can resolve a critical dependency in this company. Those answers were learned through local relationships and experience. Someone has to make them accessible.

A senior professional can be expected to exercise judgment once the role, authority, and relevant context are clear. They cannot be expected to infer an invisible approval chain. Calling that expectation autonomy does not make it good management. It makes the new hire pay to discover what the company already knows.

When the Team Becomes the Company's Directory

When a newcomer needs information, they often turn to the colleague who has been there longest. That person explains whom to contact, how to request the information, which approvals apply, and which process is likely to cause a delay. The problem gets solved, so the manager may never hear about it.

Colleagues helping each other is healthy. Repeatedly relying on a few people to explain undocumented routes is a management and organizational problem. The helpful employee becomes an unofficial onboarding specialist and internal directory, with no planned capacity and little recognition for the work.

Managers can assign experienced employees to mentor newcomers, but the responsibility must be explicit. The manager remains accountable for making the team's work navigable: sharing the relationships and decision paths they know, and ensuring critical knowledge does not stay in one person's head. The organization is accountable for clear decision rights, accessible processes, and functioning information systems. If a manager cannot fix a company-wide barrier, they should expose it—not disguise it with another private workaround.

Information Friction Has a Price

APQC's 2021 survey of 982 full-time knowledge workers found that respondents estimated spending an average of 2.8 hours per week looking for or requesting needed information. APQC also reported that mentoring can strengthen employees' networks and reduce time spent seeking experts. The figures describe broad information friction; they do not show how much is caused by managers or how much could be avoided.

To put a hypothetical value on the problem, imagine a 12-person team where each person loses two avoidable hours a week searching for contacts or clarifying approval routes. At an assumed fully loaded labor cost of $60 an hour over 48 working weeks, that is 1,152 hours, or $69,120 worth of capacity.

The two hours and the hourly cost are assumptions, not APQC findings. The calculation is not a forecast of cash savings or a measurement of management failure. It shows the scale of capacity a company could examine in its own operations. The actual cost may also appear as delayed decisions, repeated work, slower customer responses, or projects waiting for an answer. Those consequences need to be measured in the organization where they occur.

A Manager Should Reduce Repeat Dependencies

A Senior Marketing Specialist needs financial data to prepare a campaign budget. The manager knows who in Finance owns it, so they request the numbers and forward them. The task is complete. Next month, the specialist needs similar information and has to ask again.

The manager could introduce the specialist to the Finance contact, explain the process, and clarify which decisions the specialist can make independently. One approach gets the task done. The other makes the next task easier to do without the same intervention.

A manager does not need to know every company process. They should share the routes they know, make introductions, clarify authority, and raise gaps they cannot resolve. When a process has no clear owner or the decision rights are contradictory, the answer is organizational repair—not blaming an employee for failing to guess.

That extends a point I made in an earlier article about what managers do: managers organize people, priorities, information, and decisions so work can move toward an outcome. A practical test is whether the team can use what the manager knows without needing the manager to find the same contact or explain the same route again.

Project Manager Onboarding Is a Start, Not the Finish

Gallup's January 2019 article reports that employees were 3.4 times as likely to feel their onboarding had been successful when their manager took an active role. That finding concerns employees' assessment of onboarding; it does not prove the effect of ongoing knowledge transfer. It does make one point clear: managers belong in the process when a new employee joins.

And the organization keeps changing after onboarding. Responsibilities shift, people leave, approval paths change, and employees take on work that requires new relationships. Managers should keep the team current when those changes affect how work gets done.

Companies can measure whether that is happening: how quickly a new employee can identify the people and information needed for the role; how often the same process has to be explained; how many routine questions still require a manager to find a contact; and whether work continues when that manager is unavailable. The measure is not a team that never asks for help. It is a team that does not have to guess its way through routine work.

Companies often praise managers everyone depends on. But when routine work stops because only one person knows how to navigate the organization, the company has a fragile operating model—not proof of exceptional leadership.

Being senior does not mean knowing the company. A manager who does know how it works should make the team's routes visible and raise the barriers they cannot remove. When a senior hire is blamed for not knowing a rule nobody explained, who else should be answering for it?

Erik Scaranello