An Intranet Needs Three Lenses

An intranet can be full of documents and still leave people unable to see what their colleagues are doing or discuss what they find. The repository may be working exactly as designed, which is useful, but the organization does not necessarily learn merely because the filing cabinet has excellent uptime.

The three-lens audit separates those functions. An intranet serves information through storage, awareness through activity, and communication through conversation, so the exercise asks a person to spend ten minutes visiting the intranet and assess each lens: can I find documents and data, can I see my colleagues’ work, and can I discuss and interpret what I find? Each lens receives a simple rating of strong, adequate, or missing.

I think the audit is useful because it turns one woolly judgment about “the intranet” into three observable questions. A team can have a strong repository while awareness and conversation have quietly atrophied, and a single engagement score will usually conceal which part went missing.

Storage is necessary and incomplete

The information lens asks whether documents and data can be found easily. This is a real requirement. A system that cannot return the needed record does not support the work that depends on it.

Storage alone does not reveal current activity. A person may retrieve a document without knowing whether another group is using, revising, questioning, or applying it. The repository can preserve information while leaving the living context of the work invisible.

Awareness and conversation complete the picture

The awareness lens asks whether people can see what colleagues are working on. The communication lens asks whether people can discuss and interpret what they find. These functions make a record part of shared practice rather than a static object in a collection.

Organizations often overinvest in information storage while awareness and communication atrophy. The audit does not assume that this imbalance exists in every system. It gives a person a way to see whether it exists in theirs.

Awareness is not the same as a stream of announcements. The useful question is whether the intranet lets someone notice relevant work early enough to connect with it. Communication is not the same as an empty comment field. The useful question is whether a person can ask what a record means, add context, or locate someone who can interpret it.

Those distinctions prevent a feature inventory from passing the audit on behalf of the experience. A system may contain an activity feed that nobody can relate to their work, or discussion controls without a visible practice of response; the ten-minute visit asks what a person can actually do through each lens, which is a less flattering question but a better one.

Audit one journey, not the whole platform

The short exercise becomes clearer when it follows one ordinary need. Look for a document connected to current work. Observe whether the search route makes sense. See whether the system reveals who created, revised, or is presently using the material. Then try to ask a question or inspect an existing interpretation.

One journey cannot certify the whole intranet. It can show where a real passage breaks. Repeating the audit with different needs and several colleagues creates a small body of evidence without requiring a grand platform review. The ratings remain useful because they name the kind of failure: missing information, missing awareness, or missing conversation.

The weakest rating also keeps the response specific. A storage failure may need better description or retrieval. An awareness failure may need a clearer view of active work. A communication failure may need a visible route to interpretation and response. Calling all three problems “engagement” would make the diagnosis smaller by making the word larger.

Repeat the observation and compare it

The suggested frequency is monthly for three months. Repeating the short visit builds a pattern instead of relying on one impression. The participant is auditing their own experience, not criticizing IT. If stakeholders dismiss the result, three colleagues can conduct the same informal assessment. When several people identify the same weak lens, the pattern becomes harder to ignore.

After three visits, the ratings become a basis for balanced intranet development rather than another opinion about whether the platform feels “engaging.” The weakest lens tells us where to look next: at finding information, noticing active work, or having the conversation that turns a stored document back into shared practice.