Every Era Requires a New Foundation. What Does This Era Require?

David

Jun 26

9 min read

A lot of commentary on AI sounds more certain than it should.

We do not know exactly how AI will reshape work, roles, teams, or organisations. We do not know which operating models will endure, which skills will matter most, or how quickly different types of work will be reshaped.

But we do know this: when the nature of work changes, organisations need new foundations.

The question is not whether we can predict every effect of AI. The question is whether we are building the foundation that allows us to make sense of change, preserve what we learn, govern what we rely on, and adapt without fragmenting.

Every major shift in work has required organisations to build a new foundation, because each shift exposes the gaps in the previous one. When work changes, the constraint changes. When the constraint changes, organisations need a new foundational capability.

History shows a recurring pattern through definable Era's.

The industrial age required management systems because work had to be coordinated at scale. The digital era required process and systems architecture because work, customers, transactions, and operations became connected. The data era required data architecture because organisations had more numbers than they could trust.

The era we find ourselves in now exposes a different constraint: whether the organisation can continue to make sense of itself as the work changes.

AI matters, but AI is not the protagonist of this story. The protagonist is the pace of change.

AI accelerates that pace. It exposes the informal workarounds that used to hide the gaps. It makes fragmentation more visible, more repeatable, and more consequential. But the foundation is justified by change itself, not by an AI forecast.

The better question is not, “What will AI do to work?”

The better question is, “What foundation does an organisation need when work keeps changing, knowledge keeps moving, and both people and machines increasingly depend on the same underlying understanding?”

The pattern across eras

Era	What changed	New organisational constraint	Foundation that had to be built
Industrial age	Work scaled through factories, machinery, labour coordination, distribution, and standardised production	Coordinating people, time, materials, cost, quality, and supervision at scale	Management systems, hierarchy, administration, standard methods, reporting, accounting, and process control
Digital / dot-com era	Customers, transactions, operations, and communication moved into connected digital systems	Connecting demand, fulfilment, customer records, finance, workflows, and internal operations	Process and systems architecture, ERP, CRM, workflow redesign, system integration, and digital operating models
Data era	Digital systems produced more records, reports, dashboards, and metrics than organisations could confidently interpret	Knowing which numbers to trust, how they were defined, and how they should be used	Data architecture, data models, pipelines, warehouses, governance, standard definitions, and data quality
Current era	Work is faster, more distributed, more knowledge-dependent, and increasingly mediated by AI	Knowing what the organisation knows, what is current, what is authoritative, what context matters, and how learning is preserved	Knowledge architecture: structured, governed, maintained knowledge that people and AI can reliably use

The industrial foundation helped organisations coordinate work.
The digital foundation helped organisations connect work.
The data foundation helped organisations measure work.

The knowledge foundation described above helps organisations understand and adapt work. That is the shift now taking place.

The industrial age: scale required management

In the industrial age, the central problem was not simply that organisations needed more workers. It was that work itself changed shape.

Production moved from smaller workshops and craft-based environments into larger systems of labour, machinery, materials, cost, output, and quality. Work could no longer be coordinated through proximity, habit, or the judgement of a few individuals close to the action. As organisations grew, the informal methods that had worked at a smaller scale became insufficient.

Industrial work created scale. Scale created coordination problems. Coordination problems created the need for management systems.

More people had to be coordinated. More materials had to arrive at the right time. Machines had to be used consistently. Costs had to be tracked. Quality had to be controlled. Output had to become more predictable. Work had to move through repeatable methods rather than personal habit alone.

Hierarchy, roles, supervision, planning, administration, accounting, reporting, timekeeping, standard methods, and quality control were not merely bureaucratic additions. They became the foundation that allowed industrial organisations to operate beyond the limits of direct personal oversight.

At first, these systems may have looked like extra structure. Later, they became the condition for scale. That is often how new foundations appear. They are first experienced as overhead. Then, once the nature of work has changed enough, they become obvious.

The digital era: connection required process and systems architecture

The digital era created a different kind of organisational problem.

It is easy to remember the dot-com era as the moment businesses needed websites, but that is too shallow. The more important shift was that customers, transactions, suppliers, internal teams, finance, fulfilment, support, and communication started becoming digitally connected.

Work was no longer only happening inside departments. It was moving across systems.

A customer action could trigger a sales process, a stock movement, an invoice, a support ticket, a delivery workflow, a marketing record, and a financial entry. The organisation needed to connect front-office demand with back-office execution.

The value was not simply in “being online”; it was in whether the organisation could actually operate through connected systems. Digital work created connection. Connection created integration problems. Integration problems created the need for process and systems architecture.

Functional silos, manual handoffs, local spreadsheets, and disconnected records could not support the speed and complexity of digitally connected work. Organisations needed to redesign how work moved across functions, systems, and teams.

ERP systems, CRM platforms, e-commerce systems, workflow tools, integration layers, and process redesign were not just technology choices. They became part of the organisational foundation. They helped businesses connect work across functions, reduce duplication, create more consistent handoffs, and operate through shared systems rather than isolated departments.

The digital era was therefore not only about technology adoption. It was about building the systems and processes that allowed connected work to function. The foundation shifted from coordinating work at scale to connecting work across the organisation.

The data era: abundance required trust

Once organisations had digital systems everywhere, another problem emerged.

They had more data than ever before, but not necessarily more confidence.

Different teams had different reports. Dashboards told different stories. KPIs were defined differently across departments. Numbers could not always be reconciled. Leaders spent time debating whose figures were correct rather than what action should be taken.

The problem was no longer simply access to data. The problem was trust.

More records did not automatically create better decisions. In some cases, more records created more confusion. Data was duplicated, incomplete, inconsistently defined, poorly governed, or trapped in systems that did not speak clearly to each other.

Digital systems created data abundance. Data abundance created trust problems. Trust problems created the need for data architecture.

Data architecture gave organisations a more reliable numerical backbone. It brought structure to data models, pipelines, warehouses, definitions, governance, quality standards, and reporting logic. It helped organisations move from “we have numbers everywhere” to “we know which numbers we can rely on.”

That foundation mattered because measurement had become central to how organisations made decisions. If the numbers could not be trusted, the decisions built on them became weaker too.

But data architecture also revealed its own boundary.

It helped organisations manage structured data. It helped them measure what had happened. It helped them reconcile numbers and build more consistent reporting.

But organisations do not run on numbers alone.They run on judgement, context, decisions, exceptions, customer nuance, operating principles, lessons learned, informal know-how, and the reasoning that explains not only what happened, but why it happened and what should be done next.

That is where the next constraint begins.

The collaboration wave: access without coherence

Before AI arrived in daily work, organisations had already changed again.

Cloud tools, SaaS platforms, shared drives, Slack, Teams, Google Drive, SharePoint, Notion, Confluence, project tools, meeting recordings, transcripts, and collaborative documents made it easier than ever for people to create and share information.

This was useful. It enabled distributed teams. It helped people work across geographies. It reduced some of the friction of access. It made collaboration faster and more flexible.

But access is not the same as coherence.

The collaboration wave made information easier to create, share, and access across teams and geographies. But it did not solve the deeper problem of shared understanding. In many organisations, it multiplied the number of places where knowledge could live without clarifying what should be trusted.

A decision might sit in a meeting recording. The rationale might be in a Slack thread. The latest version of a process might be in someone’s drive. The customer nuance might live in a senior person’s head. A workaround might be known by one team but not another. An outdated SOP might still be findable. A newer version might exist, but only because someone happens to know where to look.

The collaboration wave gave organisations speed. It did not necessarily give them shared understanding.

That distinction matters because the informal ways knowledge used to move around organisations have weakened. In stable, co-located teams, people could rely more heavily on proximity. They could ask the person next to them, overhear what mattered, or learn through repeated exposure to the same people and situations.

As teams became more distributed, more fluid, and more tool-heavy, those informal mechanisms became less reliable. Knowledge still moved, but often through personal memory, private notes, direct messages, old documents, recurring questions, and local workarounds.

The organisation could still function, but only because people compensated.

They asked the person who usually knew. They searched old messages. They copied a previous document. They kept their own version. They used judgement to decide what looked current. They worked around the system.

These behaviours are human and understandable. They often work in the moment.

But they hide a deeper gap: the organisation may have information everywhere, while still lacking shared, trusted knowledge.

The current era: change requires knowledge architecture

This is the environment into which AI has arrived.

Again, AI is not the whole story. The deeper story is that work is becoming faster, more distributed, more knowledge-dependent, and more fluid. Roles change. Teams change. Tools change. Markets change. Customer expectations change. Methods change. Best practice changes. New information arrives constantly.

AI accelerates this. It gives people new ways to generate, retrieve, summarise, compare, and act on information. It also increases the pressure on organisations to make their knowledge usable, because more work can now be performed against whatever knowledge environment already exists.

And that is where the weakness becomes visible.

If the organisation’s knowledge is fragmented, AI exposes fragmentation. If authority is unclear, AI exposes unclear authority. If processes are outdated, AI may surface outdated processes. If decisions were made but never captured, AI cannot recover the reasoning. If lessons were learned but never integrated, AI cannot make them available.

The issue is not that AI suddenly creates the problem. The problem was already there. AI makes it harder to ignore.

This is why the current era requires a different foundation.

Not because anyone can fully predict where AI is going. Not because every organisation needs to chase every new tool. Not because automation will solve the problem.

The foundation is needed because organisations now have to keep learning, adapting, and aligning under conditions of continuous change. That is a knowledge problem.

Organisations are not linear production lines

Much of the AI conversation is still framed as a search for the next bottleneck.

Where is the constraint now? What task can be automated? Which function will shrink? Which step can AI speed up? Where does the bottleneck move next?

There is some usefulness in that framing. Some work does move through sequences. Some constraints are real. Some tasks can be accelerated.

But organisations are not linear production lines. They are complex knowledge systems. Work moves through relationships, context, judgement, memory, interpretation, authority, and coordination.

A change in one part of the organisation affects how people decide, what they trust, who they ask, what gets repeated, what gets forgotten, and how work is understood elsewhere.

The real question is not where the bottleneck moved, but whether the organisation can keep sensing, learning, deciding, and aligning as the work changes.

Can the organisation continue to make sense of itself as the process changes?

Can it preserve what it learns?

Can it govern what it relies on?

Can it adapt without fragmenting?

These are not questions of automation alone. They are questions of organisational knowledge.

The new foundation

This is where knowledge architecture matters.

Not as a new label for documentation. Not as a better filing system. Not as a wiki clean-up. And not as an AI prediction.

Knowledge architecture is the foundation that allows an organisation to structure, govern, maintain, and use what it knows, so that people and AI can work from shared, trusted understanding.

That is enough for this argument. The point here is not the full method. It is the shift in foundation.

Every era asks organisations to build what the previous era did not require.

The industrial age asked organisations to coordinate work at scale.
The digital era asked organisations to connect work across systems.
The data era asked organisations to measure work with greater trust.

This era asks organisations to understand and adapt work as it changes. That requires knowledge architecture.

No one can fully know how AI will reshape roles, teams, workflows, operating models, or competitive advantage. But organisations still need a way to make sense of what is changing, preserve what they learn, govern what they rely on, and adapt without fragmenting.

That is the real foundation now required.

This era requires knowledge architecture because AI is not entering a linear process.

It is entering a complex organisational knowledge system.

And the organisations best prepared for what comes next will not be the ones that guessed the future perfectly. They will be the ones that built the foundation to keep making sense of it.