People connected across an open building by flowing ink lines and blue branches, illustrating shared enterprise knowledge on cream paper.

Enterprise knowledge management could become a more direct source of business value as organisations connect their accumulated experience to AI agents capable of acting on it. Customer insights could inform more commercial decisions. Lessons from delivery could improve the next proposal. The reasoning behind a critical decision could remain available long after the people involved have changed roles.

The opportunity is to make expertise available across more of the enterprise, at the moment it can influence an outcome. That could support revenue growth, reduce operating effort and improve continuity. It could also change how companies develop new capabilities: each completed piece of work would contribute context that subsequent work could reuse and refine.

Enterprises would need to connect information across existing systems, distinguish authoritative decisions from tentative suggestions, and define where agents can act independently. Leaders would also need to decide how released capacity will create value and how employees will develop the judgment needed to direct increasingly automated work.

I think of an enterprise AI brain (for lack of a better term) as a permissioned memory of the organisation, connected to agents that prepare and execute work under human accountability. Its value would be measured in better business outcomes and the organisation’s ability to retain and apply what it learns.

Four ways connected enterprise knowledge could create value

Faster preparation may release capacity, but the larger opportunity could lie in applying existing expertise to more customers, decisions and products.

Enterprise knowledge management value pathways: growth, efficiency, accuracy and continuity, paired with measures including win rate, accepted-outcome cost, errors and time to independent work.

Support growth by extending the reach of expertise

A sales team preparing a proposal could draw on comparable projects, the commitments those teams made and what delivery subsequently learned. Making that experience easier to apply could allow the company to pursue more suitable opportunities without a proportionate increase in preparation effort. It could also improve qualification and help teams make commitments they can deliver profitably.

Across authorised customer records, recurring problems could suggest an opportunity for a new service or product. Experience that previously informed a single project could become an input to a broader commercial decision.

These mechanisms would need to be tested against customer demand and execution. Relevant measures include win rate, contribution margin and time to market. An increase in the number of proposals produced would be insufficient evidence of growth or improved economics.

Improve efficiency across the full workflow

Connected knowledge could reduce the effort required to find context, reconstruct earlier decisions and recreate existing work. Agents could then use that context to prepare the next task, carrying the relevant evidence and constraints with it.

The unit of measurement should be an accepted outcome. A faster draft that requires more correction may increase total effort. Conversely, an organisation could spend more time on deliberate review while reducing the effort required to complete the workflow. The financial benefit would depend on how the released capacity is used and what the system costs to operate.

Improve accuracy by making decisions easier to verify

A proposal linked to its sources, assumptions and approved requirements gives reviewers a clearer basis for judgment. An agent could identify a conflict between a customer commitment and a delivery constraint before it becomes an implementation problem. Changes to an underlying decision could trigger a review of the work that depends on it.

The system could also introduce errors or propagate a mistaken interpretation. Accuracy should therefore be assessed through material error rates and subsequent rework, including errors that automated checks initially accept. Traceability makes verification possible; it does not establish that a conclusion is correct.

Strengthen continuity by preserving institutional knowledge

A company’s experience includes exceptions, rejected alternatives and the reasons a particular approach succeeded or failed. Preserving that context could reduce dependence on individual employees for explanations that the organisation can reasonably record and share.

New colleagues could understand why a constraint exists as they encounter it in their work. Experts could spend less time repeating explanations and more time addressing unfamiliar problems. Measures such as time to independent work and the frequency of expert interruptions would help assess whether knowledge retention is improving continuity.

Some expertise remains tacit and develops through practice. Recorded decisions can support learning without reproducing the judgment of the person who made them. The objective should be to make that expertise easier to learn from and apply across the organisation.

Connecting organisational memory with execution

Delivering these benefits would require an operating model that connects shared context, agent execution and human judgment. Existing systems would continue to hold their authoritative records: code in Git, documents in SharePoint or Drive, and customer information in the CRM. A context layer would connect those records to the decisions and rationale that explain how they should be used.

This extends the coordination argument in Enterprise AI Strategy is Backwards. The opportunity grows when knowledge captured in one workflow becomes usable in the next, subject to the relevant permissions.

Enterprise AI operating model linking shared context, AI agents and human judgment. Authorised outcomes update memory; Git, documents, tickets, CRM and meetings remain systems of record.

Shared context would preserve sources, ownership, access rights and decision history. It would distinguish approved decisions from suggestions, retain unresolved conflicts and show when an earlier conclusion had been superseded. Knowledge owners would be responsible for correcting or retiring stale material, including the summaries derived from it.

Agent execution would translate that context into scoped work. Agents could prepare decision notes, propose changes to a backlog, draft a customer response or implement an approved task on a branch. Each assignment would have defined permissions, an accountable owner and a record of the evidence used. Models could change without the organisation losing the history around the work. The Jev model-routing project explores this separation at a smaller scale by selecting a model according to the task and available evidence.

Human judgment would establish objectives, allocate authority and resolve consequential uncertainty. Review should give people access to the proposed change and its supporting evidence. Disagreements between automated reviewers would help direct attention, while inspection of accepted outputs would help identify shared mistakes.

Consider a hypothetical design review. The team agrees to simplify an onboarding flow, postpone a feature and retain a customer exception. An agent prepares a decision note for confirmation. Once the relevant decisions are approved, another agent checks the backlog, proposes ticket updates and identifies an older instruction that conflicts with the new scope.

Work within existing permissions proceeds. Coding agents prepare changes and run tests; reviewers check them against the approved task. The conflicting instruction returns to the project lead. By the next morning, the team has proposed changes to inspect and a specific question to resolve, with a record linking both to the original decision.

The value comes from continuity across the workflow. A decision can inform subsequent work without requiring each participant to reconstruct its meaning. That places a corresponding responsibility on the context layer: a suggestion incorrectly recorded as an instruction could be propagated through several otherwise competent agents. Authority and uncertainty must travel with the information.

Converting released capacity into business impact

Leaders should make explicit how productivity improvements will contribute to growth or lower costs. Released time creates an opportunity; its value depends on the decisions that follow.

Consider an illustrative set of 100 comparable cases. Assume employees currently spend 35 hours reconstructing context, 35 preparing drafts, 20 reviewing them and ten correcting them. Now assume connected knowledge reduces reconstruction to ten hours and preparation to 15, while review rises to 25 and correction remains at ten. Total human effort falls from 100 to 60 hours.

Illustrative stacked bars compare 100 hours of fragmented work with 60 hours in a connected workflow per 100 comparable cases. Context reconstruction falls from 35 to 10 hours, drafting from 35 to 15, review rises from 20 to 25, and correction stays at 10. Forty hours are released before technology and operating costs.

These figures are assumptions, not measured results or a forecast. They hold case volume and required quality constant. They illustrate how a reduction in preparation could accommodate more review and still release 40 hours of capacity.

That capacity could support additional customer work, faster delivery or activities that improve future performance. It could reduce spending where it replaces overtime or an otherwise necessary external expense. If it is absorbed by additional low-value activity, the financial benefit may be negligible.

An investment case would also need to include technology, implementation and ongoing operating costs, which are excluded from this example. Maintaining context, reviewing exceptions and correcting agent errors all consume resources. Measuring total effort and business outcomes over time would establish whether the new workflow creates a sustainable advantage.

Establishing the conditions for dependable scale

Confidential client work, employee information and commercially sensitive plans cannot become universally accessible because they have been indexed. Permissions need to follow information into summaries and proposed actions as well as govern access to the original record.

Decision authority also needs to remain explicit. A recent message does not necessarily override an older approved requirement. An agent authorised to prepare a draft may have no authority to send it to a client. A team could expand autonomy for a well-understood class of work as evidence accumulates, while keeping that permission specific and revocable.

Review capacity is another design constraint. Agents that produce proposals continuously could create more work than people can assess. Priorities and limits on work in progress should therefore be part of the operating model. A low-cost proposal can still be expensive to evaluate, and the system should be able to defer work whose value does not justify that attention.

Automated review can support this process, but agreement is not independent verification. Two agents may reach the same conclusion because they relied on the same mistaken decision note. Human reviewers need access to underlying evidence and periodic samples of work that automated checks accepted.

Recovery should be defined according to the action. A document can often be restored from version history; a sent email cannot be recalled with the same certainty. Pausing an agent can stop its next action without reversing the consequences of its last one. Teams need to know which changes they can undo and which would require repair.

Employees build judgment partly by preparing analyses, implementing changes and seeing where their reasoning fails. As agents assume more of that preparation, organisations should create deliberate opportunities for people to form their own view, inspect failures and take responsibility. Shared decision histories could support that development by making alternatives and outcomes available for comparison.

A leadership agenda for enterprise knowledge management

A practical starting point is a recurring workflow with a measurable outcome, a named owner and a bounded body of knowledge. The objective should be to establish whether connected knowledge improves the work sufficiently to justify broader adoption.

Start with a business outcome. Identify whether the workflow should improve delivery speed, reduce rework, support commercial growth or strengthen continuity. Establish a baseline that includes preparation, review and correction. Select work where the result can be evaluated at a consistent quality standard.

Define the knowledge and authority the workflow needs. Identify the sources, decisions and exceptions that inform the work. Assign responsibility for maintaining them. Make access rights, approval requirements and unresolved conflicts explicit before allowing agents to execute against that context.

Test continuity as well as productivity. Assess whether someone unfamiliar with the project can understand the reasoning and carry the work forward. Change an underlying decision and check whether the system identifies affected tasks. These tests reveal whether the organisation is retaining usable knowledge or accumulating more records.

Expand through evidence. Compare accepted outcomes, cycle time, material errors and total operating effort before widening the scope. Connect successful workflows where permissions allow it, so delivery experience can inform sales and customer feedback can inform product decisions. Set the pace of expansion according to the organisation’s ability to maintain the knowledge and judge the resulting work.