Seniority is not knowledge

The outcome of any meeting is determined by the knowledge distribution in the room, not the seniority distribution.

This is the fact that most meeting cultures ignore. Organisations structure meetings around hierarchy. The most senior person leads. The agenda reflects their priorities. The conclusions reflect their understanding. But seniority and knowledge are not the same thing. In operational environments they are often inversely related. The people closest to the work know the most about it. The people furthest from it carry the title.

When the knowledge distribution and the seniority distribution are misaligned, meetings produce conclusions that the people with the most knowledge know are wrong. They may say so. They may not. It depends on whether the culture of the meeting permits challenge from below. In many organisations it does not. The senior person's conclusion stands. The knowledge in the room that contradicted it is noted privately and forgotten officially.

The cost of this is not visible in the meeting. It is visible in the implementation. The process that was approved without understanding takes longer than planned. The solution that was escalated without context produces pushback from the teams who have to execute it. The decision that was made at the top reaches the bottom and meets the knowledge that should have informed it in the first place.

Knowledge in the room is not about who is smartest. It is about who knows the current state of the specific thing being discussed. That person is not always the most senior. They are not always the most confident. But they are always the most important person in the room for that specific conversation.

Key Takeaway: The outcome of a meeting is determined by how well the knowledge in the room is accessed, not by how well the seniority in the room is managed. The person who knows the most about the specific topic is the most important person in that conversation, regardless of their title.

Seniority determines who leads the meeting. Knowledge determines whether the meeting leads anywhere useful.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · Section: Seniority is not knowledge

MarvinPro | November 2025

marvinpro.com

The manager who did not know

There is a specific and damaging pattern that appears in organisations when a manager receives responsibility for work they do not understand.

The manager knows they do not understand it. This creates discomfort. The discomfort creates a response. In a confident, self-aware leader the response is to learn, to ask questions, to connect directly with the people who do understand it and to build the context needed to lead effectively. In a leader whose authority depends on appearing to know, the response is different. They escalate what they cannot explain. They push back on timelines they cannot evaluate. They manage the inputs and outputs of the work without understanding the work itself.

This produces a specific kind of friction. The teams doing the work know the manager does not understand it. They can see the gap between the questions being asked and the reality of what the work requires. When the manager escalates a concern upward, the escalation does not carry the full picture, because the manager does not have the full picture. The response from above is shaped by an incomplete description of the problem. The solution that comes back down does not fit the actual situation.

The knowledge gap at the management layer is a translation problem. Every time information passes through a manager who does not understand it, something is lost. The detail that would have changed the decision. The context that explained why the timeline was what it was. The nuance that separated a genuine problem from a normal operational phase that requires patience rather than intervention.

The manager who escalates without understanding does not make the problem visible. They make a version of the problem visible. And the version they make visible is shaped by their own discomfort, not by the operational reality.

Key Takeaway: A knowledge gap at the management layer is a translation problem. Every escalation that passes through a manager who does not understand the work loses something. What arrives at leadership is a version of the problem shaped by the manager's discomfort, not the operational reality.

The escalation that passes through a knowledge gap does not carry the full picture. It carries the manager's version of it.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · Section: The manager who did not know

MarvinPro | November 2025

marvinpro.com

The blockage

The most damaging consequence of a knowledge gap at the management layer is not the bad escalation. It is the blockage.

When a manager does not understand the work, they often compensate by controlling access to information. They position themselves between the team and the people the team needs to speak to. Every question the team has about the process, the requirements, the current status of a decision must pass through the manager. Every communication with an owner, a partner, another department must be approved or conducted by the manager.

This feels like management. It is not. It is a manager protecting their position by controlling a flow they do not understand.

The team that is blocked from direct communication with the people who have the knowledge they need cannot function at the speed the work requires. They wait for the manager to relay questions they could have asked directly. They receive answers that have been translated by someone who did not fully understand the question. They implement instructions that have been filtered through a layer of misunderstanding and then discover, when the work does not produce the expected result, that something was lost in the translation.

The blockage is invisible to leadership. The manager appears to be managing. The team appears to be working. The friction, the delays, the rework and the frustration are internal to the team and expressed, when they are expressed at all, as performance problems or attitude problems rather than as the structural communication failure they actually are.

The team that revolts is not a difficult team. It is a team that has been blocked from the information it needs to do its job and has run out of patience with the blockage.

Key Takeaway: A manager who controls access to knowledge they do not have does not protect their authority. They create a blockage that the team pays for in delays, rework and frustration. The revolt that follows is not a people problem. It is a structural communication failure.

The team that revolts is not a difficult team. It is a team that has been blocked from the knowledge it needs to do its job.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · Section: The blockage

MarvinPro | November 2025

marvinpro.com

Knowing less than your team

There is a version of this situation that produces the opposite outcome.

A manager who knows they do not know everything, who is comfortable with that reality and who builds their management approach around it, creates something the controlling manager never achieves. A self-regulating knowledge flow.

The principle is simple. The manager signals clearly, through behaviour rather than announcement, that they do not need to be the knowledge bottleneck. The team is trusted to communicate directly with owners, partners and other departments. The manager does not need to know everything because the team can access what they need without waiting for the manager to relay it.

What happens next is the interesting part. When the team knows the manager does not want to hold all the knowledge, they stop bringing knowledge questions. They bring advice questions instead.

The advice question is fundamentally different from the knowledge question. The knowledge question asks the manager to know something. The advice question asks the manager to think about something. And the advice question always arrives with the current context attached. The team member who asks for advice brings the relevant article, the current status, the specific situation. The manager receives the context they need to advise, without having to maintain an independent knowledge base they could never keep current.

This is a self-regulating system. The manager set the expectation once. The team adapted permanently. The knowledge stayed where it was most current, in the team and in the direct relationships with owners and partners. The manager stayed relevant through judgment and advice rather than through knowledge maintenance.

No friction. Always appreciated. The team felt trusted. The manager stayed current. The work moved at the speed it needed to move.

Key Takeaway: The manager who signals they do not need to hold all the knowledge creates a self-regulating flow. The team stops bringing knowledge questions and starts bringing advice questions. The advice question always carries the current context. The manager advises without maintaining a knowledge base they could never keep current. No friction. Always effective.

They did not come with questions. They came with advice requests. And the advice request always brought the answer with it.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · Section: Knowing less than your team

MarvinPro | November 2025

marvinpro.com

A real example

In a large organisation, a specific operational area was transferred to a new team as part of a structural change. The new team's manager had no background in the area. Some members of the team did, because they had come from the group that handled it previously. The knowledge in the room was distributed unevenly. The team knew more than the manager about the specific work they were being asked to do.

The manager's response was to tighten control. Every communication with the process owner had to go through the manager. Every question about the current state of the process, the temporary workarounds in place during the review period, the articles being updated, the partner sign-offs still pending, had to be relayed through someone who did not fully understand what was being relayed.

The owner was operating in a post-implementation period. Temporary workarounds had been provided while the formal process documentation was being reviewed and updated. This is normal. It requires the team executing the work to stay in direct contact with the owner so that the workarounds are applied correctly and updated promptly when the formal documentation is ready.

The blockage prevented this. The workarounds were misapplied because the relay lost the detail. The escalations that reached leadership described a process that was not working, without the context that explained why the temporary state was temporary and what was being done to resolve it. Leadership escalated further. The owner, who had been managing the situation correctly, was now managing an escalation that did not reflect the actual status of the work.

In a parallel situation in the same organisation, a different manager had received a similarly complex area with team members who knew the work better than the manager did. This manager made a different choice. They told the team directly that they did not need to know everything. The team could communicate with owners and partners without routing through the manager. When they needed advice, they should bring the current context with them.

The team adapted immediately. They stopped asking the manager questions about the process and started asking for advice on decisions. Every advice conversation came with the current article, the current status and the specific scenario. The manager stayed current without maintaining anything independently. The work moved without friction. The escalations that did reach leadership were accurate because they had not been filtered through a knowledge gap.

Same organisation. Same type of work. Two different management approaches. Two completely different outcomes.

The knowledge did not change. The distance between the knowledge and the decision maker did.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · A real example

MarvinPro | November 2025

marvinpro.com

Knowledge in the room

Before any significant meeting, any escalation, any decision, ask one question. Who in this room knows the most about the specific thing being discussed?

That person is the most important person in the conversation. Not the most senior. Not the most confident. The most informed about this specific topic at this specific moment.

Give that person space to speak. Give their knowledge the weight it deserves. Do not let the seniority distribution in the room override the knowledge distribution.

As a manager, know what you do not know. Signal it clearly. Let your team access the knowledge they need directly. Trust them to bring you the advice questions rather than the knowledge questions. The advice question will always carry the context you need. You will stay current without maintaining anything. Your team will move without friction.

Sometimes it is good to know. Sometimes it is good to know that you do not know. The leader who understands the difference between these two states will always build a better functioning team than the leader who tries to know everything and ends up knowing nothing current.

Know what you know. Know what you do not know. And know which one is more useful right now.

Think Simple · Leadership · Here is How to Think · Vol 2: The Leader · Philosophy 6: Knowledge in the Room · Chapter Outcome

MarvinPro | November 2025

marvinpro.com