Thinking
Only an organization that understands itself can transform successfully.
Organizations today have more data, more knowledge and more technology at their disposal than ever before. And it is still getting harder to understand them as a whole.
Processes sit in systems. Knowledge sits in documents and in people's heads. Decisions change structures. Rules change workflows. Markets change requirements. And with every change, complexity grows further.
We therefore believe that organizations need a new capability:
the capability to understand themselves continuously.
The real news of the AI era is not that machines understand organizations. It is that an organization is, for the first time, in a position to understand itself - continuously, rather than as of the cut-off date of a project. The term for it is "Organizational Intelligence". It is older than any language model. What is new is that it can now be delivered on.
Why now
Every era had one layer everything else was built on. It was never replaced, only built over - and each next layer only became possible once the one below it was taken for granted. Process management is no mistake in that chain. It is the step before.
- Industrial Age
- MachinesProductivity comes from what stands on the shop floor. The organization itself is not an object of study.
- Process Age
- Business Process ManagementWorkflows become describable and therefore steerable. What gets described is the target state - and it holds until the next change, which the description never hears about.
- Digital Age
- Digital systemsThe workflows move into software. That produces data about the organization, spread across so many systems that nobody sees the whole any more.
- AI Age
- Artificial intelligenceMachines can read, for the first time, what only people could read before: contracts, minutes, standards, grown line-of-business applications. That is the precondition, not the result.
- Next Age
- Organizational IntelligenceWhat is read becomes a continuous picture of the organization - and out of the picture come decisions that can be justified. That is the layer still missing.
- Outcome
- Organizational ResilienceNot a further era, but what comes out at the end: an organization that survives migrations, regulation and outages because it knows itself.
The eras in full, with sources: chapter 2 of the book →
A new perspective on organizations
For decades we have broken organizations down into separate disciplines.
Each of those disciplines looks at an important part of the organization.
But organizations do not work in parts. Processes depend on people. People work with systems. Systems follow rules. Decisions change processes. Knowledge shapes decisions. And everything keeps changing.
The decisive question is therefore no longer: how do we manage these separate perspectives better?
It is: how does a shared understanding of the organization emerge from them?
- Process management
- describes workflowsWhat is described is the target state. It holds until the next change, which the description never hears about.
- Enterprise architecture
- describes systems and structuresThe landscape is captured, the work inside it is not. Two organizations with the same architecture work entirely differently.
- Knowledge management
- organizes knowledgeContent becomes accessible. Whether it fits together, and which version applies, no filing system answers.
- Process mining
- analyses operational dataWhat systems log becomes visible. What sits beside it - contracts, standards, minutes, experience - stays outside.
- Governance
- defines rules and responsibilitiesWhat should apply is set down. Whether anyone acts on it is in no policy.
From knowledge to understanding
More knowledge does not automatically lead to more understanding. An organization can document thousands of processes, store millions of records and have capable AI at its disposal – and still not know why certain things work the way they do.
Information only becomes valuable once the relationships within it become understandable. Data becomes information.
Information becomes knowledge. Connected knowledge becomes understanding.
And when an organization can apply that understanding to itself continuously, something new emerges: Organizational Self-Understanding.
The organization as a system in its own right.
An organization is more than the sum of the people working in it. It consists of processes, roles, rules, decisions, systems, relationships, experience and knowledge. People come and go. Technologies change. Processes develop further.
The organization remains.
Organizational knowledge therefore has to be more than the knowledge of individual people. It has to become a capability of the organization itself.
It can put knowledge to use in new contexts. And it can develop new capabilities out of that understanding.
That is the point at which organizational understanding becomes Organizational Intelligence. Organizational Intelligence does not mean that an organization “thinks” the way a person does. It denotes its capability to relate its own knowledge, its structures and its operational reality to one another continuously – and to develop understanding that can be acted on.
Semantic systems can establish the relationships between different sources of information. Agents can draw on organizational knowledge and act within defined rules. That changes the role of AI. The decisive question is no longer: what can AI do for individual tasks? It is: what becomes possible once AI understands the context of an organization?
Not only for people. Increasingly for machines and AI agents as well.
Knowledge becomes understanding.
Understanding becomes the ability to act.
The ability to act becomes development.
That is Organizational Intelligence.
Where these sentences are derived in the book - understanding, intelligence, capability: Chapter 8 →
The terms
These are the names as they stand in the long read, each with what it amounts to in plain terms. The order is not a ranking: every stage presupposes the one before it.
- Organizational Memory
- The memory of the organization.Knowledge, connections and decisions are preserved in a form someone can pick up again later. A filing system alone does not achieve that - it holds files, not connections.
- Organizational Self-Understanding
- The organization reads itself.Out of that memory, a picture of its own workflows, structures and decisions emerges continuously. Continuously is the decisive part: a picture of last quarter is no basis for a decision taken today.
- Organizational Intelligence
- The picture turns into decisions.Understanding becomes interpretation, interpretation becomes decisions that can be justified. Only at this point does it become visible whether the picture holds - in the quality of the decisions built on it.
- Organizational Capabilities
- Decisions turn into repeatable ability.A capability is what a company can still do on the twentieth occasion without the same people standing beside it. Only what reaches this form survives a change of staff.
- Organizational Self-Empowerment
- The organization develops its own capabilities further.The newest term in the series and the least settled. It replaces the earlier formulation “self-improving organization”, because that described a result and this one describes a capability. Provisional, and carried as such in the long read.
- Organizational Resilience
- The company withstands change.Not a building block of its own, but the consequence of the earlier ones: an organization that knows itself and keeps developing its capabilities comes through migrations, regulation and outages better. This is where the theory meets commercial questions.
The terms are derived chapter by chapter - from memory to resilience: chapters 6 to 9 →
Which stage delivers which term
The terms above are the theory, the tools are the offer. This is the bridge between them - and nothing more stands here. What the tools actually do is on the home page and on the product sites.
- Stage 1 · ProcessCollector
- Organizational MemoryKnowledge, connections and decisions are preserved in a form someone can pick up again later.
- Stage 2 · ProcessMagnet
- Organizational IntelligenceThe organization reads itself, and out of that picture come decisions that can be justified. Organizational Self-Understanding is the first half of that step, not a stage of its own.
- Stage 3 · ProcessForge
- Organizational CapabilitiesDecisions turn into repeatable ability - what an organization can still do on the twentieth occasion without the same people standing beside it.
- Outcome
- Organizational ResilienceNot a stage but the consequence of all of them: an organization that comes through migrations, regulation and outages because it knows itself.
The system is not the destination
The terms above describe a capability, and a capability needs a place to operate: one that connects an organization's reality, context, decisions and action into a single foundation instead of spreading them across twenty systems. That is what an Organizational Intelligence System is. It is not the destination. The destination is an organization that stays able to act under change - and whether that happens is decided not by the software but by whether somebody inside works with the result.
How it becomes a system - chapter 13 →Claims and limits
A theory that explains everything explains nothing. Beside every statement, therefore, stands what expressly does not follow from it.
Whose terms these are - and what in them is our own assembly: Chapter 3 →
Where the term comes from
Organizational Intelligence is not a word from the AI era. It has been in organizational research since the sixties, and the diagnosis behind it has been reformulated several times since. What was missing was never the idea. What was missing was the means to deliver on it.
- 1967Wilensky
The sociologist Harold L. Wilensky publishes a book with Basic Books under exactly this title: “Organizational Intelligence”. His subject is not technology but structure - why governments and corporations fail on information they already hold in-house. The diagnosis is close to sixty years old and has not become wrong.
- 1978Argyris and Schön
Chris Argyris and Donald Schön describe organizations as learning systems and separate what a company says about itself from what it actually acts on. That names the uncomfortable half of the problem: an organization follows rules it does not itself know.
- 1991Organizational memory
James Walsh and Gerardo Ungson set out in the Academy of Management Review where the things an organization “remembers” actually sit: in people, structures, workflows, systems and in its own history. Distributed, not in one place - and therefore never fully readable by any single system.
- 1995Knowledge management
Ikujiro Nonaka and Hirotaka Takeuchi distinguish tacit from explicit knowledge and turn it into a management discipline. What gets built from that over the following two decades is mostly storage: knowledge becomes accessible, understanding does not follow from it.
- 2007In our own house
With Quam, the same work begins in Magdeburg from the practical side: documenting processes so that they become auditable. Two decades of projects in industry and the public sector are the reason this theory was not written at a desk.
- TodayWhat is new
Not the term, but the technology. Language models, vector search and knowledge graphs read holdings that previously only people could read - contracts, minutes, standards, tickets, line-of-business applications grown over years. That turns a description of the problem into a capability for the first time.
Further reading
The full derivation stands as a document of its own, continuously extended. Anyone who only wanted to know what the tools rest on is finished at this point.
- Organizational Intelligence - the living documentEN/DE · Dr. Christian Graup and Jobst von Heintze · continuously extended
Why organizations need an Organizational Intelligence System: the problem of the missing layer, the OI ladder as a six-step model, plus the measurement catalogue, case studies, maturity model and reference architecture.
Open the documentPublic - The revision journalDE/EN · continuously updated
Which version changed what, when and why. The short form of the last few weeks is above on this page; the full record is here.
Open the journalPublic - The bibliographyDE/EN
Wilensky, Argyris and Schön, Nonaka and Takeuchi, Walsh and Ungson - the prior work the terms rest on, with full references. Anyone wanting to check whether an old term is being resold here starts here.
Open the bibliographyPublic
Who stands behind the theory, and for how long: to the company →
What was changed most recently
The text is not closed. Every version is recorded with its date and reason, and the changes of recent weeks concerned terms, not wording.
- 3 July 2026Version 0.10
Self-understanding is carried as a capability rather than a state: as something an organization establishes continuously, and therefore as a management task rather than the outcome of a project. Until then, knowledge had been at the centre.
- 8 July 2026Version 0.14
Theory and architecture are separated. Since then the statement about organizations stands independently of the question of which systems deliver on it - the previous version could be read as a product description.
- 10 July 2026Version 0.15
One sentence goes explicitly into the text: artificial intelligence can contribute to Organizational Intelligence, it is not that intelligence itself. Before, it stood between the lines. It is the reason no model takes over the role of understanding in this theory.
- 10 July 2026Version 1.0 RC
First complete version: observation separated from management history, decision quality carried as an observable consequence, chapters taken through to the reference architecture. From here the text can be examined as a whole rather than chapter by chapter.
- In progressNew edition
The coming version places the prior work the terms rest on, and answers the two objections that come up most often: that an old term is being sold again here - and that texts about AI and organizations mostly sound as though a machine wrote them. Both belong in the text, not in a footnote.
Let us talk.
For objections, a conversation is the better place than a form: twenty minutes about the thesis, not about the price list. Anyone who thinks the order is wrong is the more interesting person to talk to.