FIELD NOTE |
April 3, 2026
Who Gets to Know What the Organization Knows?
Information architecture is also an architecture of power: what people can know shapes what they can decide, challenge, and change.
Two people can be asked to make the same decision while operating with completely different amounts of context.
One can see the customer history, contract, product usage, previous exceptions, and the people involved.
The other sees a ticket containing five fields.
They may have identical judgment and motivation. They do not have identical agency.
One can reason from context. The other has to reconstruct it.
Every organization has an unofficial information network. Ask Priya about billing. Marcus remembers why that integration works that way. Don't trust the dashboard until Elena checks it.
Those relationships are valuable. They're part of how organizations remember, interpret, and make sense of what happens.
But they also distribute information unevenly.
People with tenure, confidence, proximity to leadership, or strong internal relationships can navigate those networks. New employees and people outside them encounter a different organization.
The information may exist. That doesn't mean it's equally available.
And even when information is technically accessible, that doesn't mean it's available in a form someone can use.
A support representative may understand the customer's problem. Sales understands the relationship. Finance understands the contract. Product understands the technical constraints. An executive has the authority to accept the risk.
Each has a legitimate piece of the picture.
But as information moves between them, it changes. Details are summarized. Context is compressed. Language shifts to fit the next audience.
Eventually, the person making the decision may receive a representation of the problem that no longer contains what made the original situation difficult.
This is why I often follow information rather than the organizational chart.
Where does knowledge originate? Where does it travel? Where does it change meaning? Where does it stop? Who has to recreate it? Who is allowed to act on it?
The answers reveal another kind of architecture, made of access, trust, relationships, and authority.
I've become less interested in whether an organization has a single place to store information and more interested in whether the people who need information can actually use it when it matters.
Engineers, Finance, Marketing, and Customer Success don't necessarily need identical views of the same data. They need enough shared context to understand how their decisions affect one another, and ways for what they learn to become available to the rest of the organization.
Information needs to travel in more than one direction.
Otherwise, the organization can become remarkably good at collecting information without becoming any better at learning from it.
Organizations often ask people to show more initiative, take ownership, and make better decisions.
But what can someone reasonably decide when they cannot see the conditions surrounding the decision?
What does ownership mean when the relevant information lives in someone else's system, inbox, memory, or relationships?
And what happens when the people with the richest context are not the people authorized to act?
These aren't simply communication problems.
They're design choices about who gets to know enough to participate meaningfully.
I don't think everyone needs access to everything. Privacy, confidentiality, security, and legitimate differences in responsibility matter.
But I do think restrictions, interfaces, and information flows deserve the same deliberate attention we give formal reporting structures.
Because access to information doesn't just affect how efficiently someone works.
It affects which possibilities they can recognize, which risks they can understand, and which decisions they can meaningfully influence.
Information architecture doesn't only determine what an organization knows. It helps determine who inside the organization is able to know enough to matter.