Access changes agency

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.

Informal networks are information infrastructure

Every organization has an unofficial map. Ask Priya about billing. Marcus remembers why that integration works that way. Do not trust the dashboard until Elena checks it.

Relationships are one of the ways organizations think. But informal networks distribute information unevenly. People with tenure, confidence, proximity to leadership, or strong internal relationships can navigate them. New employees and people outside those networks encounter a different organization.

What becomes data is a decision

A number fits neatly into a field. A customer’s hesitation during a conversation does not. A closed-won opportunity is easy to count. Months of relationship-building are harder to represent. A support ticket can be categorized. A pattern someone notices across ten conversations may remain intuition until someone with enough authority decides it deserves investigation.

When an organization says it is data-driven, I want to know what became data and what disappeared on the way there.

The people with the richest context are not always the people making the decision. Support understands the problem. Sales understands the relationship. Finance understands the contract. Product understands the technical tradeoff. An executive may have authority to accept the risk.

Every handoff introduces interpretation. Details are summarized. Language changes. The person with authority eventually receives a representation of the problem rather than the problem itself.

Follow the information

When I am trying to understand an organization, I often follow information rather than the org 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?

That path reveals another architecture made of access, trust, relationships, and authority.

Information architecture does more than determine what an organization knows. It helps determine who inside the organization is able to know enough to matter.

Information is only as useful as its proximity to action.

Where it makes sense for engineers to consume data may not be the same place as Finance or Marketing. The question is not whether everyone can technically access the same repository. It is where information is shared, who receives it, how they interpret and use it, and how their activity feeds equally useful information back into the organizational system.

That makes information architecture inseparable from power: who can see, who can interpret, who can decide, and who has to ask someone else before knowledge becomes action.

Agency needs more than permission

Organizations often say they want people to have more agency. Usually they mean initiative: notice the problem, make a recommendation, move without waiting to be told.

But agency and authority are different things. Agency is a person’s capacity to perceive, choose, and act. Authority is the system’s permission for that action to carry consequence.

A person can have enormous agency and very little authority. They can see the pattern, understand the tradeoff, and know what should change while still needing approval from someone with less context.

Empowerment does not erase architecture

This is why exhortations to ‘be empowered’ can become frustrating. If decision rights, information access, budgets, incentives, or consequences have not changed, the architecture has not changed either.

The person may be invited to act while still being punished for crossing a boundary the organization never made explicit. Or they may be asked to own an outcome without control over the conditions that produce it.

Repeated escalation is a clue

When the same category of decision repeatedly moves upward, I become curious. Sometimes escalation is appropriate. Some decisions carry enterprise risk and should be made centrally.

But repeated escalation can also mean authority lives too far from the information required to use it well. Senior leaders become routing layers, while the people closest to the work learn to wait.

The goal is not maximum autonomy. It is alignment between agency, information, authority, and consequence.

Distributed authority requires trust, but trust is not simply a feeling leaders either have or do not have. Systems can make trustworthy action easier.

Clear principles, visible constraints, accessible information, feedback loops, and explicit decision rights allow people to act without guessing what will later be considered acceptable.

If you want more agency, do not only ask people to behave differently. Look at what the organization allows them to know, decide, spend, change, and learn from.

People can see what needs to change long before they have permission to change it. The architecture determines whether that seeing becomes useful.

Agency depends on legibility

When people do not understand the process, the expectations, or the rules, they cannot meaningfully influence the outcome. Ambiguity can be useful in exploration, but hidden rules are not the same thing as freedom.

I am interested in systems where people can see enough of the architecture to locate themselves inside it: what is fixed, what is negotiable, what they own, what someone else owns, and where a decision can actually be changed.

Agency requires more than permission to act. It requires enough legibility to act intentionally.