You join a company.
HR gives you an organization chart.
Your manager explains who reports to whom.
You receive policies, procedures, job descriptions, and perhaps an employee handbook. Everything appears reasonably clear.
Then you start working. And gradually, you discover another "workplace."
The workplace behind the workplace is the informal human system that develops alongside an organization's formal structure.
It includes relationships, trust, reputation, informal influence, institutional knowledge, communication patterns, unwritten expectations, and the ways people actually cooperate to get things done. This isn’t merely anecdotal workplace wisdom.
Researchers David Krackhardt and Jeffrey Hanson wrote about what they called the “company behind the chart” in the Harvard Business Review in 1993.
They distinguished informal advice, trust, and communication networks that can operate across formal organizational boundaries. Their central observation was that an organization chart can show formal reporting relationships, but not necessarily the relationships through which advice, trust, and communication flow.
Later research has similarly examined organizations as combinations of formal structures and informal networks, rather than assuming the organization chart tells the whole story. That distinction matters.
Because understanding your job is not necessarily the same thing as understanding how to operate effectively within your workplace.
This is perhaps the most useful way to think about it.
Most of us assume we work in one organization. In practice, we may be navigating two overlapping systems. Neither system automatically replaces the other. And neither is necessarily more legitimate.
The formal structure is essential. Organizations need accountability, governance, responsibilities, and clear decision rights.
But human beings don’t suddenly stop being human because they enter an office. Relationships develop. Trust accumulates. Reputations form. People discover who knows what. They learn who responds quickly. They discover who gives sensible advice. They learn who remains calm when things go wrong. And gradually, an informal human infrastructure develops alongside the formal organization.
This distinction is important. Mention informal influence, and some people immediately think, "Office politics."
Gossip, cliques, favoritism, backroom deals, and manipulation. Those things can certainly exist. But reducing the informal workplace to politics misses something important.
Imagine your company has a difficult customer problem. The organization chart says the issue belongs to Operations. But everyone knows:
“Ask Ravi.”
Ravi may not be the most senior person. He may not own the process. But he has worked there for 15 years. He remembers what happened the last three times something similar occurred. People trust his judgement. So they consult him. That isn’t necessarily politics. It is institutional knowledge combined with earned credibility.
Now imagine marketing needs something unusual from IT. The formal process says: Submit a ticket. But experienced employees have learned that discussing unusual requirements with IT early prevents misunderstandings later. So they speak before submitting the formal request. Again, that isn’t necessarily political maneuvering. It may simply be sensible collaboration.
The workplace behind the workplace often exists because people need ways to coordinate things that formal structures cannot anticipate perfectly. Research on informal organizational networks has long recognized that information and work can move through personal contacts and relationships as well as traditional hierarchy.
The workplace behind the workplace isn’t necessarily where the politics happens. Sometimes it is where the work happens.
Suppose you are preparing for an important internal presentation. You look at the attendee list. There are eight people. You naturally focus on the two most senior executives. Understandable.
But what if the person most influential on this particular decision is not one of them?
Perhaps the finance manager has been analyzing the proposal for three months.
Perhaps a technical specialist has the confidence of the CEO.
Perhaps the operations manager will ultimately have to implement your recommendation.
Perhaps the executive you are presenting to routinely asks a trusted colleague:
“What do you think?”
The organization chart cannot easily tell you this. This is because authority and influence are related, but they are not identical. This explains something many professionals eventually discover: The most senior person in the room is not necessarily the only person you need to understand. That does not mean bypassing authority or playing political games. It means recognizing the broader stakeholder environment surrounding a decision.
Position tells you who has authority. Observation helps reveal whose judgement others value.
Every organization seems to have a few people like this. They may not be senior executives. But when something unusual happens, people seek them out.
Ask Mei. She’ll know.”
“Speak to Arjun before you send that.”
“Check with Sarah. She handled the previous project.”
These people often function as informal knowledge nodes.
Research into organizational networks has examined exactly this phenomenon. Krackhardt and Hanson, for example, described an advice network consisting of the people colleagues depend upon for solving problems and obtaining technical information, alongside trust and communication networks.
This creates an important lesson for anyone navigating an organization. Don’t evaluate people’s organizational importance solely through hierarchy. Pay attention to behavior.
Who gets consulted?
Who gets copied?
Whose opinion changes the direction of a conversation?
Who seems to know the history?
Who connects departments that otherwise rarely interact?
Who can explain why something is done a certain way?
The answers may tell you something the organization chart cannot.
Some workplace expectations are explicit—submit expenses by Friday, get approval before purchasing, and do not disclose confidential information.
Others are rarely written down.
How quickly should you reply to the CEO?
How much disagreement is acceptable during meetings?
When should your manager be copied?
Who should be consulted before a major proposal?
How much autonomy are employees expected to exercise?
Is it acceptable to contact senior leadership directly?
How are mistakes normally communicated?
How much bad news should you bring before you also have a proposed solution?
The frustrating thing about unwritten rules is that newcomers sometimes discover them only after violating one. You send an email. Someone quietly tells you:
“Next time, you might want to speak to your manager first.”
Nobody told you. But apparently everybody else knew.
This is one reason experienced employees can appear unusually adept at navigating an organization. They may not necessarily be more intelligent. They simply possess more history and experience. They have accumulated hundreds of small pieces of information about how the organization operates.
The newcomer has not.
There is a temptation at this point to turn workplace navigation into a formula.
Don’t.
Human organizations are too contextual for that, but a few questions can sharpen your observation.
When something unusual happens, who gets consulted?
Not once but repeatedly.
Patterns matter more than anecdotes.
Ask:
“Is this a workaround because the formal process is poor—or is there context I haven’t understood?”
Those are very different situations.
When someone says:
“We tried that before,”
Don’t immediately accept it as proof that the idea cannot work. But don’t dismiss it either.
Dig deeper and ask what happened.
One person may possess all three.
Often they are distributed among different people.
Identify who wields them.
Someone who appears “political” may simply be well connected.
Someone who appears “difficult” may be protecting an important constraint.
Someone who seems resistant to change may know something you don’t.
Or your initial interpretation may be correct.
The point is to gather enough information before becoming too certain. These principles help you notice more. They do not tell you exactly what to do in every situation. And that distinction matters.
Once you recognize the workplace behind the workplace, you may start seeing it everywhere.
You notice who people consult.
You notice how information travels.
You notice the gap between stated values and actual behavior.
You notice which relationships make work easier.
You notice the histories behind certain decisions.
That awareness is valuable. But awareness creates another challenge.
What should you do with what you notice?
This is where reading an article can only take you so far.
Knowing that you should validate an assumption is different from recognizing an assumption while you are under pressure.
Understanding that influence exists is different from knowing how to engage an influential stakeholder appropriately. Knowing that context matters is different from knowing when you have enough context to act.
Understanding that you should think beyond the immediate moment is different from doing so during a difficult conversation.
Consistent application requires something more than information. It benefits from structured frameworks, realistic scenarios, practice, reflection, and feedback. That is the territory explored more deeply in Savvy Academy’s workplace programs and workshops, where judgement can be exercised, examined, and developed.