Information Management as an Organizational Capability

Information management is usually treated as a back-office function — the domain of records, archives and compliance. That is an underestimate. Information is how an organization knows itself. Every decision is only as good as the information it runs on, and most organizational friction is, at bottom, an information problem wearing the costume of a process problem.

The capability, in practice

• Capture: information is recorded where it is created, in a form the organization can use.
• Classification: records are categorized by what they are and how long they must be kept.
• Ownership: every class of information has a named owner who answers for its quality.
• Access: the right people can find the right information, under rules that hold under audit.
• Retention: records are kept where they must be kept, and released where they must be released.
• Visibility: management can see the state of the organization without assembling it by hand.

Notice that none of this is software. A document management system is a carrier for these disciplines, not a substitute for them. Organizations that buy records software without classification rules and ownership simply create a very organized place to lose things.

Why leadership should care

Information is the substrate of accountability. When a decision cannot be traced to its inputs, responsibility diffuses. When records are found in personal folders, institutional memory depends on tenure. When reports are assembled by hand, leadership sees the organization a week late. The fix is not more data. It is information treated as a managed organizational asset — with architecture, governance and workflows — not as a by-product of work.

You can tell a lot about an organization by what it can find in the time it takes to make a decision.