Making Organizations Intelligent

1.0 Once Upon a Time, There Was Hierarchy

Picture a Roman general for a moment.

He commanded a legion. Five thousand men.

He didn't know all of them, of course. How could he.

But he spoke with his six tribunes, each of whom led a cohort of roughly eight hundred soldiers.

The tribunes didn't talk to all their men. They did, however, align periodically with the centurions, each of whom led a century of eighty soldiers.

The centurions didn't manage eighty people directly. They managed ten decans.

And each decan led eight soldiers: the same men he shared a tent with, ate with, marched with.

Five thousand men. Four levels.

Nobody, in the entire structure, ever managed more than eight people at once.

What might look like a refined and well-orchestrated organizational choice is actually a biological constraint.

A human being can effectively keep track of only between three and eight people. Beyond that threshold, they lose the thread.

This is how hierarchy was born, more than 2,000 years ago. Not as a form of power, but as a solution to an information problem.

Hierarchy serves three purposes:

- Allocating decision rights: who decides what, with what authority, within what limits, generally in organizations where people are asked to specialize in executing very well-defined tasks.

- Distributing accountability: who answers for what, and to whom.

- And finally, in large part, collecting context from below, synthesizing it, and transmitting it upward. And vice versa.

This last point is the most relevant one for understanding how hierarchy works, both that of an army and, to draw a parallel closer to our times, that of a company.

Because a certain group of managers have always been, above all, this: signal repeaters and information gatekeepers.

On one hand, they move information, downward, sideways, and upward.

On the other, they concentrate knowledge and information, using it to their own advantage and becoming nodes of power.

On these constraints, the organizations and companies of the last two thousand years have been built.

---

2.0 The Collective Brain

The intelligence of the organization. Or, for the nerds among you, the company brain.

In a hierarchical structure, like the one you probably work in if you're reading this essay in 2026, information cannot flow freely. It has to pass through layers of management that act as intermediaries.

The general doesn't know what's happening in the decan's tent, except through a chain of people who synthesize, filter, and interpret.

Every step introduces latency. Every step introduces distortion. This generates resistance and time dilation.

For two millennia, organizations have worked this way because there was no alternative.

There was no way to build a functional collective brain: information lived only in people's heads, in conversations, in meetings.

Information wasn't only the knowledge held within the hierarchical scaffolding. It was the culture of the organization itself. It was fragmented, invisible, impossible to aggregate.

You could breathe it but you couldn't query it. You could sense it but it wasn't distributed.

It was the individual memory of that manager who had been with the company for twenty years. It was the founder's ways of doing things. It was how people behaved when he (or she) wasn't in the room.

When someone left the organization, they took with them years of context that no document had ever captured.

The collective brain was missing. Or rather, the only collective brain that existed, a dysfunctional one, was the hierarchy itself.

So what exactly is this functional collective brain that organizations have never had?

2.1 The Functional Collective Brain

Let's start with what it isn't.

The company brain is not a document archive. It's not a dashboard. It's not a chatbot trained on company files. It's not even the hierarchical organization I described before, that gatekeeper of knowledge.

The company brain has two dimensions that cannot exist without each other.

One is technological: the explicit memory of the organization. Documented decisions, mapped processes, knowledge made queryable. A system that knows why a decision was made six months ago. That knows what is blocked today, where resources are going, who is working on what and with what priorities.

The other is human: the implicit memory of the organization. The shared behaviors, the way people reason together, the culture that determines how decisions are made, how conflicts are handled, how trust is built over time.

The two dimensions feed each other and neither is functional without the other.

A technological company brain fed by people with dysfunctional behaviors produces structured noise.

A human company brain made of brilliant people, without a system that captures their knowledge and transforms it into organizational culture and functional behaviors, produces an intelligence that vanishes when those people leave.

Only when the two levels integrate does the organization truly become intelligent. This creates an organization that learns as a system, not as a sum of individuals.

To sum it up: the company brain is an organization's capacity to remember, reason, and act in a coherent and functional way over time, into the future, through its people and its systems, without depending on anyone's individual memory in particular.

It is exactly what hierarchy was also trying to do, but with only human tools, and dysfunctional ones at that.

The mid-level manager spent most of their time collecting information from those below and transmitting it to those above. Their main value wasn't judgment or the ability to lead a team as a leader: it was their position in the chain. They were the node through which information passed.

The functional company brain does the same thing. Without the human node.

People are not at the center of the information chain, the way traditional managers were, but at the edges of the system, where technology can't reach and human judgment and relational skills make the difference.

But a brain without governance is a brain in a coma: technically present, functionally absent. The company brain doesn't switch itself on and doesn't maintain itself. It requires an owner, explicit governance, continuous maintenance. It requires effort.

Without someone taking care of it, the technological component becomes an archive that nobody consults and nobody updates.

Without someone taking care of it, the human component becomes a mass of individuals subject to cultural entropy and the loss of collective identity.

2.2 The Company Brain Is Not an AI Invention

Here it's worth pausing on a widespread misconception.

If any of you live in the world of X (Twitter, for nostalgics) or the San Francisco bubble, you may have gotten the impression that artificial intelligence and the company brain are closely correlated.

Let's dispel the myth right away: the company brain did not become possible thanks to AI.

Well-organized companies have always tried to build both its dimensions.

The technological dimension: knowledge bases, documented processes, operational manuals, internal wikis. McKinsey has been accumulating institutional knowledge for decades. The Japanese kaizen model is grounded in continuous process documentation as a daily practice.

The human dimension: strong company cultures, shared values, ways of working passed down through experience, mentorship systems, organizational rituals that lead people to reason coherently over time.

So why has it never really worked?

For the technological dimension, the answer is simple. Documenting costs time. Sharing context requires discipline. And above all: in most organizations, nobody has an interest in doing it. The manager who accumulates information in their own head or on their local computer is structurally more powerful than one who shares it.

Think about it for a moment. Knowledge is power. And hierarchy creates a perverse incentive not to build the collective brain that would make the hierarchy itself less necessary.

For the human dimension, the problem is different but equally structural. Building functional human behaviors requires method. What is generally not considered in organizations, which don't ask themselves what truly drives people to change behavior, don't align incentives, and don't factor in the neuroscience of learning and change management.

Organizations have always known that culture matters. But they have never had a systematic method to build it intentionally and measurably. They relied on selecting the "right" people, on the example of a few leaders, and on osmosis between colleagues. All slow, uncertain processes, difficult to scale.

And so, despite the fact that the dysfunctional culture, which you end up building in the absence of method, persists even without the individual, the tacit knowledge of that individual, never written down, disappears. A part of the company's collective memory is lost. No document had ever captured it. And nobody was scandalized, because the system was designed to work exactly that way.

2.3 The Company Brain in the Age of AI (and the Digital)

AI didn't invent anything new. It did something simpler, and more decisive. On both dimensions.

On the technological dimension, it did three things.

It brought the cost of documentation down to nearly zero. Transcribing a call, summarizing a meeting, categorizing decisions: operations that used to require hours of human work now take seconds.

It made the mass of previously inaccessible, unstructured information queryable. Having a thousand internal documents is useless if you can't find the right one at the right moment.

And above all: it created a new incentive. An AI system is only as useful as it is well-fed. Building the technological dimension of the company brain stops being a cost with no return and becomes the condition for getting something concrete. For the first time in history, documenting pays off.

On the human dimension, technology changed something more subtle but equally important.

It made visible what was previously invisible. People's behaviors, how they collaborate, how they make decisions, where they lose time, where they generate value: all of this now leaves digital traces. Those traces can be read, analyzed, and returned to organizations and their people as a mirror of themselves.

An organization that understands how its people actually work, not how they think they work, can intervene on behaviors in a much more precise way than before. It can identify where behaviors are functional and where they aren't. It can build collective awareness around dynamics that previously remained implicit.

And above all: it can make explicit the tacit knowledge that used to disappear with people. It can capture the reasoning behind decisions, not just the decisions themselves. It can transform implicit memory into shared memory.

The two dimensions have come closer than ever before. Technological memory and human memory can finally feed each other in real time.

---

3.0 Why AI Fails When It Enters Organizations

A recent MIT study argues that 95% of AI initiatives in companies produce no results.

A note on this, right away. This is not a technology problem. The technology works, and how.

The problem is that nobody has worked on the necessary conditions for it to work. And those conditions are two, one for each dimension of the company brain.

The first is technological. An AI system is precise. It requires precise inputs. If processes aren't documented, AI can't reason over them. If decisions leave no traces, AI can't learn. If context exists only in people's heads, AI works in a vacuum. It becomes useless.

The second is human. Even when the technological system is well-built, AI fails if people haven't developed the functional behaviors needed to inhabit it. They don't know how to structure a request in a way that the machine can process. They're not in the habit of making their reasoning explicit. They don't trust the system and they route around it. They don't collaborate in ways that leave useful traces instead of noise.

The two failures feed each other. A technological system without functional behaviors remains empty. People with functional behaviors but without a technological system produce intelligence that vanishes.

I smile when I talk to people who say AI produces mediocre results.

In most cases, we are the ones responsible for the mediocrity. Not because the result is the product of a probabilistic calculation that traces the average of the information on which AI was trained, as I often hear people say. But because we haven't worked on any of the two necessary conditions for it to function properly.

To build and feed the company brain, then, people must change the way they work. They must activate smarter behaviors, ones suited to the new opportunities.

For instance, they must change how they structure a decision. How they distribute the authority to make that decision. How they document it. How they pass context to colleagues. How they interact with AI. How they allocate the time AI has freed up. How they make their own work readable by the machine without losing the depth that only a human being can bring.

---

4.0 The Org Chart of the Future Is Made of Intelligences. Period.

Some are human, others are artificial.

Five years ago, that sentence would have sounded like science fiction. Today it's becoming reality in some organizations. At Wibo, the company I co-founded a few years ago, we decided to embrace the AI industrial revolution by working first on ourselves to become an AI-native team, a role model for what I'm writing about.

But we're not alone in this decision.

Block, Jack Dorsey's company, is dismantling its hierarchical structure and building a system where coordination is handled by the intelligence of the system itself. People operate at the edges, where human judgment truly matters.

Moderna merged the roles of Chief HR Officer and Chief Digital Technology Officer into a single figure. This hybrid role is there to govern a hybrid workforce, made of human beings and AI agents together. This transition requires a unified vision that two separate HR and IT departments, confined in separate silos, cannot have.

The question that has guided organizations for two thousand years was: "How many people can a single manager handle?"

The question of the next twenty years will be: "Which tasks should people do, and which can machines do?"

Not all tasks are the same.

Some are eliminable: these are the operational tasks that AI performs better, faster, and without distraction errors.

Some are augmentable: the combination of human and AI produces something that neither produces alone, in the same time and with the same quality.

Some are irreducibly human: they require judgment in ambiguous situations, reading of relational context, building trust, the ability to be in a room and understand what isn't being said.

Others, finally, are human activities by choice: activities that a machine could technically perform, but that we choose to keep human for identity, ethical, or formative reasons.

Stripping a professional of what defines them is not optimization: it's demolition.

And depriving a junior of the experience of doing something because the machine does it better means producing a generation that doesn't know where things come from. The right question isn't just "who does it better." It's "who do we want to do it, and why."

This is a cultural, social, political question before it's a technological one.

There's something deeper that this classification brings with it. When operational tasks are delegated to the machine, the noise that was covering the human signal disappears. People stop spending their time filling in reports, summarizing data, managing repetitive processes. And that freed-up time is space where they can finally do what only a human being can truly do: build trust, read the relational context, look at the entire value chain, pass on experience, make tacit knowledge explicit.

Everything that feeds the human dimension of the company brain.

Without this dimension, the hybrid org chart is just a new elegant way to distribute tasks. The organization has a new structure, but it hasn't become more intelligent.

An org chart becomes truly intelligent when the people who inhabit it have developed the functional behaviors to feed the system, and the system has the technological memory to learn from them.

The paradox is this: AI enters organizations as technology. And paradoxically, it makes us more human.

Redesigning the organization from these distinctions is the strategic work that almost no company has yet done seriously.

---

5.0 Change Falls in the Gap Between HR, IT, and Business Owners

There is a fracture inside most companies that remains unresolved.

Sometimes from a lack of mutual respect. Sometimes from differences in background. Most often from an obsolete organizational design.

I'm talking about HR and IT. Human Resources and Information Technology. People and Tech.

Let's say it plainly: HR and IT speak different languages, measure different things, and often pull in opposite directions.

IT implements the technologies. HR takes care of the people. So it often falls on HR to handle change management, to drive adoption of the tools that IT has bought. Sometimes without having understood them yet. Sometimes forced by IT to implement tools that people weren't ready to adopt.

But this fracture isn't just organizational. It is exactly the fracture between the two dimensions of the company brain.

IT owns the technological dimension: the systems, the data, the documented processes.

HR owns the human dimension: the behaviors, the culture, the skills of the people.

When the two departments don't talk to each other, the two dimensions of the company brain don't talk to each other. And a company brain with its two dimensions disconnected doesn't work.

We know the result. Sophisticated tools used superficially. People trained on skills that the processes don't let them apply. The two dimensions move out of sync, and change doesn't happen.

The biggest problem arises today when the technology to be purchased is AI. Generative AI, to be more precise. The kind you talk to using natural language. The language of humans.

So IT departments buy a technology so human that anyone can talk to it without having to write a single line of code. While the HR team prepares to welcome AI workers into the organization, that is, technology that makes decisions, acts, and achieves objectives without depending strictly on human colleagues.

The boundary between HR and IT is becoming increasingly blurred in the age of AI.

And the third vertex is still missing.

The business owner, understood as the leadership team in its highest form, the one who owns the meaning of work and the responsibility for output. The business owner is not the operational manager of the company brain. They don't manage the technological or human dimension in detail. But they are the strategic owner.

They decide what the organization needs to be intelligent about. Which problems it must know how to solve. Which decisions it must support.

Without this third vertex, HR optimizes people and IT optimizes systems. But nobody optimizes the intelligence of the organization.

The arrangement that works is triangular: HR on the human dimension of the company brain, IT on the technological dimension, and the business owner on the strategic vision of both. Three vertices and a table where none of the three stakeholders can be absent.

This brings us to Wibo, the point of convergence between HR, IT, and the Business Owner.

---

6.0 Wibo Is Not a Training Company. Nor Is It a System Integrator.

Wibo is the point of convergence between HR, IT, and the Business Owner. It's the solution to an intelligence problem that none of the three, alone, is able to solve.

What we do is work simultaneously on both dimensions of the company brain, with HR, IT, and the business owner sitting at the same table, because it's the only way change holds over time. Transforming organizations is, in fact, a permanent condition.

Our work is structured across three levels.

Each of the levels you'll read about in a moment is what we consider a productized service: built to scale, flexible enough to adapt to the needs of each of our clients. And while this isn't the place to go deep into the specifics of each of our products, we'll explore their foundations together, starting with the first.

1. Mapping the Organization's Intelligence (or Company Brain)

The starting point is diagnosis. That moment when we see how deep the rabbit hole goes.

Before touching any process or training any person, we need to understand the state of that organization's collective intelligence. We do this across both dimensions of the company brain.

On the human dimension, we identify functional and dysfunctional behaviors: how people collaborate, decide, communicate, handle conflict, and build trust. We measure the organization's sentiment: how people experience their work, where there's energy and where there's resistance, where change finds fertile ground and where it doesn't. We assess the expressed levels of organizational culture, values, and principles: not the ones declared in company documents, but the ones that actually emerge in everyday behaviors, in decisions, in how people treat each other.

On the technological dimension, we analyze actual tasks: what people really do, classified into eliminable with AI, augmentable with a human-plus-AI combination, irreducibly human, or retained by choice for identity, ethical, or formative reasons. We look at how work is documented, where information is lost, which processes support collective intelligence and which obstruct it.

This mapping has a precise output: a measure of the intelligence level of that organization's company brain. From that snapshot, the real hybrid org chart emerges: the organization made of abundant intelligence, both human and technological.

It is from that snapshot that the two subsequent interventions arise: on the human dimension and on the technological one. This mapping is the compass. Without it, any subsequent intervention is blind, or significantly weakened.

2. Building the Human Dimension of the Company Brain

The second level is about behaviors, built through the transversal skills we teach.

Not technical skills. Hard skills age quickly, now.

We focus instead on the skills that make people capable of working better, both as individuals and as a group: communicating clearly in conditions of uncertainty, making decisions in ambiguous situations, collaborating effectively with colleagues and with AI agents, giving and receiving feedback that produces real change, leading teams through transitions that nobody has been through before.

These skills are not soft in the sense of secondary. They are the hardest to develop and the least replicable by a machine.

And they are exactly the ones that build the human dimension of the company brain: without them, people don't document, don't share context, don't develop the behaviors that allow the organization to learn collectively. They don't feed the culture.

The question now is: who needs these skills, and how are they built.

Who Will Need These Skills?

On the first question, the answer is simple. Everyone.

- Individual contributors, both in collaboration with a team of humans and in managing their own team of AI agents, a condition that, among other things, will make every IC a manager as well. Everyone, in some way, even those of you reading this who are not yet formally managers, will be managers.

- The managers of human teams, those who will remain after AI has eroded that part of management that was, in truth, nothing more than signal repetition.

The real managerial work will be what's left: giving feedback that produces change, making decisions in ambiguous situations, building trust through transitions that nobody has been through before. That work is not done by any machine. And it will become even more important at the moment the machine has taken care of everything else.

How Are These Skills Built?

Behaviors don't change through traditional training, where someone explains a concept, maybe uses a nice metaphor, and then everyone goes back to work.

The skills Wibo trains are functional human behaviors. They are built through practice, iteration cycles, and trial and error in safe environments where you can make mistakes without real consequences. You learn by doing, correcting, and doing again.

It's the only model that produces lasting behavioral change over time. This is why we work with top executives who don't transmit theories but bring real experience, concrete cases, the kind of context that triggers something in people because it's recognizable and lived.

A skill gets fixed when you meet someone who has already applied it under real conditions and can tell you how it actually went, including the mistakes.

But the executive alone isn't enough. Without a facilitator who transforms the story into an exercise, the account stays quality entertainment. Ten minutes of an executive describing a real mistake are worth ten hours of theory, but only if there's someone alongside who converts that account into something the participant can actually do on Monday morning.

This is how Wibo transforms human behaviors into functional human behaviors. Through a well-harmonized tandem of Executive Teacher and trainer, together.

This applies both to human-to-human skills, the way people work together, decide, coordinate, and trust each other, and to human-to-machine skills, the way people learn to collaborate with AI agents, to interrogate them, to evaluate their outputs, to know when to trust them and when not to.

3. Building the Technological Dimension of the Company Brain

The third level is integration.

Starting from the mapping, we build the technological dimension of the company brain: the explicit memory of the organization, the systems that allow it to update itself, the context, the full set of relationships between entities that make up the organization.

Then we identify the workflows where AI agents can operate, we configure them, and we introduce them into the processes. Not as a separate technological layer. As something that people, having already developed the functional behaviors of the second level, know how to feed, query, and correct.

The technological dimension of the company brain doesn't emerge from technology. It emerges from the way people inhabit it.

The three levels don't work separately. And here lies the point that the industry keeps failing to understand.

Companies that invest only in training see their people return to the same obsolete behaviors and processes as before. Individual change disperses into a system that hasn't changed.

Companies that invest only in technological integration change the processes, but people don't adopt them. They haven't developed the functional behaviors to inhabit them. The new system gets routed around, ignored, misused.

In both cases, the functional company brain is never built. Because one of its two dimensions is always missing.

A technological revolution is, first of all, a cultural one.

Companies that introduce AI without working on this level end up with sophisticated systems used superficially, new processes inhabited by people with old mindsets, and a widespread frustration that ultimately produces the wrong conclusion.

AI doesn't work.

The organization doesn't work.

The team doesn't work.

The manager doesn't work.

AI does work.

The manager who develops functional human behaviors works.

The team that organizes itself around more functional processes works.

The organization that responds better and more functionally to the needs of its clients works.

The problem is that nobody has worked on the necessary condition for all of this to function. That condition has two faces.

The first is people: smarter, better at collaborating, better at learning from mistakes, better at making their own work readable by the system. People who feed the company brain instead of draining it.

The second is the system: a technological memory that learns from those people, that coordinates without the need for excessive layers of management, that makes the organization capable of acting coherently over time.

Intelligence is not in the machine. And it's not only in the people either. It's in the way people and the machine learn to work together.

This is why at Wibo, we design how people and AI work together. In a functional way.

---

Let's finish with the concept of intelligence itself.

You've read this far. You've spent time understanding how we make organizations intelligent. But have you asked yourself what intelligence actually means?

It's worth pausing on its original meaning.

Intelligence comes from the Latin intelligere: inter, between, and legere, to read, to choose, to gather. Intelligere literally means to read between things.

Not to know many things. But to see the relationships that are not immediately evident. To grasp the connections that others don't see.

For the first time in history, we are entering an age where knowledge has become abundant. That knowledge that used to be paid for because of its scarcity, in the age of the internet and artificial intelligence, has now become a commodity. Anyone, with the same tools, has access to the same information.

Competitive advantage, then, can no longer come from knowing more than others. It comes from connecting better.

From reading the relationships between your processes and the market, between people's behaviors and the results they produce, between the decisions of yesterday and the challenges of tomorrow. Between the human dimension and the technological dimension of the company brain.

Building intelligent organizations does not mean building organizations that know more. It means building organizations that know how to read better.

This is what we build at Wibo. Through functional behaviors, work mapping, and AI technological integration.

This is why at Wibo, we make organizations intelligent.