A company remembers what it decided and forgets why. An AI can read the record.

Jesper E. Thomsen · 24 October 2026

Organisations remember decisions and lose the reasoning within a few years. By the time it matters, the people who could reconstruct it have moved on. An AI can read a decision record across functions and years in a way no person ever has. The record is the valuable part; the judgment stays yours.

Organisations remember what they decided and lose the reasoning behind it within a few years. By the time the reasoning matters, the people who could reconstruct it have moved on. A written record of why decisions were taken can hold that reasoning in view. Read by an AI, it can be held in view across functions and years in a way no person ever has. The record is the valuable part. The judgment on what it shows stays with the executive.

McKinsey calls an enterprise AI operating system the company's second brain. I have been running something with that name on my own material, and it is a different thing. McKinsey's version connects the company's data to its decisions on one platform. Mine is a decision record, a written account of why each decision was taken, with a system reading it. The difference matters because a platform without the reasoning optimises what it can see.

I started with principles, board notes, meeting recaps and decision records. The aim was a system that knows how I think and tells me when I am not acting on it. For the first weeks it was mostly noise. Then it told me that I was again spending too little time with the stakeholders who mattered most for what I was trying to do. It was right, and I changed my calendar. A good chief of staff would have said the same, but would have needed to be in every meeting for a year to say it. The system had been.

The organisation remembers the decision and loses the reasoning

A transformation programme is approved because the rationale is compelling, the benefits are attractive and management believes it can deliver. The people put in charge are capable, which is why they were chosen. Three years later it is struggling, and the account becomes poor management, unrealistic targets and the wrong people. Some of that may be true. What is rarely asked is who made the original assumptions, what was known at the time, what changed, and whether the organisation supplied the conditions it had promised.

There is a structural reason. Initiatives are approved on optimistic assumptions, because the proposers believe in them and because an ambitious case is approved more often than a cautious one. When the assumptions fail, accountability travels to the people executing. The business case usually still exists. What is missing is what was known at the time and who assumed what. Nobody has an incentive to reconstruct it. The people who approved would be the ones examined, and the people executing are the ones still in the building. The next initiative is then approved on similar assumptions. Outcomes are measured. The reasoning that produced them is not kept.

The drift nobody decided

The larger version of the same loss is drift. A company states an ambition to become customer-led. Over five years its decisions on hiring, incentives, technology, structure and cost each make sense on their own. Together they move it toward internal efficiency. Nobody intended it and nobody noticed, because nobody was present at all of the decisions. A CFO sees the investments, a CHRO the appointments, a COO the restructurings. The pattern lives in the sum, and the sum has no owner. The CEO owns the whole in theory, but nobody has the memory or the attention to hold five years of significant decisions in view at once.

A system holding the record can hold them all in view. It cannot decide better than the executive. It is, however, the one party with every decision, the assumptions behind it and the corrections since in front of it. It can be asked whether the sum has started to contradict the stated direction. The same applies to the long-horizon bets discussed in the piece on two clocks. A board can only review whether a thesis still holds if the thesis was written down when the money was committed.

Record first, challenge second

A system like this does two things that are usually sold together. It keeps the record, and it challenges decisions against it. The two do not perform alike.

The record is the dependable part. After an important meeting I write a short recap, or hand over the notes, covering what happened, what was decided, why, on which assumptions, and what remains open. It takes ten minutes. For a CEO the place to start is the executive committee, with its strategy papers, investment proposals and minutes. The recaps of the conversations where the decision was actually made belong there too, and those conversations are usually before the meeting. Mail and calendar can be added later, with explicit rules for access, privilege, retention and who may see what. The system gets things wrong at first. The corrections both improve the record and show it which things matter.

The challenge is the less dependable part, and I say that from my own corrections. In a live session the systems I run produce each step from the last one and drop premises stated earlier. An assumption already in the conversation goes unused. Asking for a challenge while the system is working produces little. Given a closed record afterwards and one question, it finds the inconsistencies well. So the challenge works as a separate pass over the record, best where the record is thickest. The judgment on what it finds stays with the person who owns the decision.

A useful side effect is that the record shows which kind of decision is in front of you. Most decisions deserve less analysis and faster correction. A few deserve far more than they get. A senior appointment shapes capability and culture for a decade and often receives less scrutiny than a mid-sized capital request. A record of past decisions and their consequences is the evidence for changing that.

Why this sits with the CEO

Strategic decisions play out over five to fifteen years, and the people who made them rarely stay that long. The record is what can outlast them, and only if someone owns it. The CEO is responsible for connecting strategy, allocation, execution and the development of the organisation, and for whether the executive team learns at all. That is the reason to start there rather than as a company-wide programme. The CEO owns the discipline. The organisation has to end up owning the memory, or the record leaves with the person who kept it.

Where this does not hold

The record is only as good as what gets captured, and the decisions that matter most are often made in conversations nobody writes down. A thin record produces confident drift reports about nothing. A good decision can produce a bad outcome and a bad one a good outcome. The system can separate reasoning from luck only if the reasoning was recorded in advance. Recorded afterwards it is a rationalisation. A complete record is also a concentrated map of strategy, disagreement and personal judgment. Weak access control makes it a liability, and knowing that every remark is retained may make executives less candid. The challenge function is, on my own evidence, unproven beyond one user who corrects it daily. An executive team that does not correct it will get a sophisticated confirmation machine.