The Real AI Bottleneck in Organisations Is Memory

Part of Expertise Encoding. This essay sets out the problem that method is designed to solve: organisations that store plenty of information but cannot remember their own work in a form AI can use.

A team leaves a meeting with a clear decision. Three weeks later that decision has gone soft. One person remembers the direction it was heading, someone else remembers the exception that got carved out, the document has moved folders twice, and the colleague who understood the trade-off has rolled onto a different project. When the question comes back round, the organisation does the only thing it knows how to do. It asks a few people to rebuild the context from memory.

That is usually the point where AI gets invited in. Someone opens a chat window and asks for help. But the assistant can’t do anything useful until a person has explained the project, dug out the document, recapped the decision, named the people involved, flagged the deadline and spelled out why any of it matters. By the time you have finished that briefing, you could very nearly have answered the question yourself.

None of this is an intelligence problem. The model would handle the question fine. What it can’t do is reach into an organisation whose memory was never kept in a usable state. In my experience that, far more than model choice or prompt skill, is why so much workplace AI stays impressive in demos and oddly weak inside real work.

AI sits beside the work, not inside it

Most of the teams I work with are experimenting with AI. People are trying ChatGPT, Copilot, meeting summarisers, document assistants and a handful of internal pilots. Some of it genuinely helps. A lot of it sits to one side of the actual work: useful in the moment and forgotten by the next meeting.

I used to think the gap was about better tools or better prompts. I have stopped believing that. The tools are already good, and they keep getting better. The problem is that they do not know enough about the work to be trusted with it.

What people need, most days, is not a sharper answer to a prompt. They need to know what was agreed in the last meeting, which version of the document is current, what the client is actually expecting, which deadlines are live this week, which decision is still open, and what needs their attention today. That is not a prompting problem. It is a context problem.

This is also why so many AI pilots stall after the demo. The demo impresses because it shows a model doing something clever in isolation. The pilot disappoints because the cleverness never connects to the surrounding work. The model answered the prompt, but it did not know the project, the history, the people or the stakes.

Storage is not memory

Here is a distinction a lot of organisations have quietly stepped over. Storage is where information ends up. Memory is the part you can pull back out, make sense of and act on at the moment it counts.

Almost everyone already has plenty of storage: SharePoint, Google Drive, Teams, Slack, email, Notion, the CRM, shared project folders, and now a fast-growing heap of meeting transcripts. None of these is short of files. What they are short of is memory.

Storage will happily hold ten versions of a document. It won’t tell you which one is current, what moved between version six and version nine, or why anyone bothered. It keeps the recording of the meeting and quietly loses the decision that came out of it. The information is technically there and practically out of reach.

So when the questions that actually move work forward come up, storage has nothing to offer:

• What matters now?
• Which decision is the current one, and why did we go that way?
• What has changed since the last version?
• Who owns the next step?
• What should be back on someone’s desk today?

People answer these by remembering, by messaging a colleague, or by scrolling back through a channel until they give up and guess. That informal human memory carries far more of the load than most leaders realise. It is also brittle. It walks out of the door when someone resigns, goes dark when they are on leave, and frays a little every week even when nobody leaves.

Why memory is the bottleneck

AI becomes genuinely useful the moment it can reach context that is structured, current and trusted. Take that away and you are back with the workarounds we already lean on: the long prompt, the manual context dump at the start of every session, one person’s recollection standing in for the whole organisation’s.

That is why so much prompt engineering is really compensation. A long prompt is usually a symptom of a weak layer underneath it. We paste the background in because the system doesn’t already know the work. Every time someone rebuilds a project history from scratch to get one useful answer, the missing memory becomes visible. The effort hasn’t gone anywhere. It has been shifted back onto a person, every single time. I made a related argument about moving from prompt engineering to context engineering; this is the organisational version of the same point.

Prompting won’t fix it. You can write the most elegant instruction imaginable, but if the system has no idea which version of the proposal is live, who signed off the change of scope, or why the timeline slipped in March, you will get a confident answer resting on nothing. A confident answer resting on nothing is worse than no answer, because somebody downstream will act on it.

The wider evidence points the same way, with sensible caveats. Ofsted’s June 2025 study of early AI adopters in English schools and further education colleges, The biggest risk is doing nothing, interviewed leaders from 21 schools and colleges. The ones getting value had moved beyond one-off experiments into practice with clear leadership, approved tools, time for staff to learn and human oversight. That is an education finding, not a universal business rule, but the pattern travels. AI pays off where the surrounding work is organised enough to trust it. Where context is scattered, the cleverness has nowhere to land.

There is a parallel on the engineering side. A May 2026 survey by Xuying Ning and colleagues, Code as Agent Harness, frames durable agent value as coming from executable, verifiable and stateful systems, with planning, memory and tool use treated as core infrastructure rather than add-ons. In plain terms: systems that hold state, remember and can act reliably over time. Same instinct, approached from the other direction. The chat box is the interface. The layer underneath is where the value compounds.

Organisational working memory

The thing that is missing deserves a name. I call it organisational working memory: the live layer of context that helps people, and AI, keep hold of what is current, what has been decided, what needs attention and what has just changed.

In practice it draws on parts of the work that already exist but rarely talk to each other: live projects, the handful of documents that genuinely matter, the trail of decisions, meeting outcomes, open questions, deadlines, owners, dependencies and the obligations that come round every quarter. The aim is not to hoard all of it. It is to keep the parts that matter within reach at the moment they are needed.

This is where a knowledge base and working memory part ways. A knowledge base is somewhere you go and search, on the days you remember it exists. Working memory surfaces what needs attention today, before you have thought to ask. Think of it less as a bigger archive and more as something that puts the right context in front of the right person.

The missing operating layer

If you accept that framing, the priority shifts. The useful question is no longer “which AI tool should we buy?” It becomes “what does the AI need to know to be useful here?”

The honest answer is mostly the boring, structural material that organisations already half track in scattered places: which projects are live, who is responsible, what has been decided and why, which documents matter, what the deadlines are, and what needs attention next. Put together, that is an operating layer.

Here is the idea in one line. An AI operating layer is the persistent context and workflow infrastructure that sits between AI tools and the real work, so that the AI understands what is happening, what matters and what to do next.

It is less glamorous than a new model release and far more useful. It means your assistant can answer “what did we decide about the delivery timeline?” because the decision was captured when it was made. It means “what is overdue this week?” returns a real list, because tasks and deadlines live somewhere the system can read. It means a document doesn’t vanish into a folder, because the system knows what it is, which project it belongs to and when it was last reviewed.

This is not automation in the old sense of replacing a task. It is closer to giving the organisation a working memory and then letting AI operate against that memory, under human judgement. The tools answer questions. The operating layer makes sure they are answering them about the right things. On the Expertise Encoding page I describe this as four layers: the work as it exists, a knowledge layer that structures it, an operating layer of skills, retrieval and quality gates, and only then reusable AI capability.

What I am testing in NiallOS

I test this on my own work first, through NiallOS, which I treat as a working laboratory rather than a product. There is nothing to buy, and I am not claiming everyone needs my setup. It holds projects, tasks, decisions and contacts in a structured database, takes documents in and turns them into extracts that can be checked against the source, and surfaces what needs attention each day. AI agents work as bounded helpers in the background rather than as a single chat box I have to remember to open.

One lesson has held up as the system has changed. The structural work, retrieval, scoring and checking, increasingly runs as plain deterministic code, and a model is called only where a task genuinely needs judgement or language. That keeps the memory dependable and makes the model the replaceable part, which is the argument of Own the Memory, Rent the Intelligence. The origin story is in Why I Built an AI Twin to Run My Life.

Plenty of it is rough, and some parts I have rebuilt more than once. But the narrow claim holds: better organisational memory makes AI both more useful and more trustworthy, and its absence explains a good number of the pilots that quietly stall.

Building it has also been a lesson in fluency. Rick Dakan and Joseph Feller’s 4D Framework for AI Fluency (Delegation, Description, Discernment and Diligence) puts judgement and responsible practice ahead of the tool list. A working memory layer is where those habits become routine: what to hand to AI, what context to give it, how to check the result, and who stays accountable.

Questions for leaders

If you want to find your own memory problem before you sign off on another tool, these questions tend to expose it quickly:

• Where does the organisation actually remember decisions, as opposed to storing files?
• What context do people keep having to explain from scratch?
• Which documents, meetings and decisions should be wired into live work, and currently aren’t?
• Could an AI answer a question about a current project without someone rebuilding the background first?
• If a key person left tomorrow, which decisions would leave with them?

The honest answers are usually uncomfortable, which is rather the point. They tell you what an AI would need to know before you could trust it to help.

Where this goes next

The practical takeaway is not “go and build a personal operating system”. It is to find out where your institutional memory is kept and whether an AI could reach it if you asked. For most organisations the answer is that memory is scattered across inboxes, drives, chat threads and individual heads. That is the real constraint, and it is fixable.

Connecting AI to project context, decision trails, meeting notes, documents and actions is unglamorous work. It is also where durable value sits, well ahead of another tool licence. If the first wave of workplace AI was about access to intelligence, the next will be about access to context. The organisations that benefit most won’t be the ones with the most tools. They will be the ones that make their memory usable, so that people and AI are finally working from the same version of the work.

If you are working through this in an education organisation or a professional team, Expertise Encoding sets out the method I use, and you can work with me on putting it in place.