From Motion to Meaning

Part I: The Crisis of Coordination

The Great Detachment and the Failure of Motion

The modern organization stands at a precipice, characterized not by a lack of effort, but by a profound lack of coherence. Across the spectrum of the economy, from the high-velocity environments of venture-backed startups to the rigid hierarchies of public sector administration, leadership teams report a consistent and unsettling phenomenon: despite overflowing calendars, relentless responsiveness, and well groomed backlogs, the organization does not feel like it is improving. There is motion, undeniable and exhausting, but there is little progress or satisfaction.

This disconnect has now become what many are calling the Great Detachment. The numbers are blunt: around 62 % of the global workforce is not engaged, and roughly 82 % are showing signs of burnout.¹² That's not a vibe or a mood, it's a structural response to the friction baked into modern work. The tools meant to help us coordinate now seek to dominate our attention, scatter our focus, and strip meaning out of the day-to-day. People aren't checking out because they're lazy. They're checking out because the system is wearing them down.

For the past thirty years, we've modeled knowledge work on the factory floor, adopting the ticketization of labor. This breaks complex, human narratives into isolated units called "tickets." While it digitisized the artifacts of work, it stripped away their meaning. By removing context, we turn high-agency employees into custodians of fragmented records. The modern knowledge worker spends more time acting as a digital janitor than a contributor, cleaning up after the tools themselves instead of moving the work forward. They begin to feel increasingly helpless and alienated from any form of impact or connection.

The core tension lies in the distinction between Motion and Meaning. Modern work culture has developed a dangerous bias toward motion. We reward the visible activity of checking boxes, moving cards, and replying to messages. However, motion without meaning is ineffective and ultimately discouraging. When people are disconnected from the larger narrative, it erodes their motivation and engagement. The task of holding the context or meaning also then tends to fall to a few key staff, leading to brittle dependencies.

Conversely, meaning without execution is mere theatre; it lives in strategy decks and vision statements but never touches the ground of daily operations. Most software chooses a side, optimizing either for the granular tracking of task execution or the static storage of meaning in policy documents. Because the tools do not bridge this gap, humans are forced to bridge it themselves, engaging in "articulation work" to sync context between incompatible silos.

The Legitimacy Gap and the Rise of Shadow IT

This architectural failure has created a profound "legitimacy gap" within the organization. Organizational theory defines a legitimacy gap as the discrepancy between an organization's stated procedures (regulatory legitimacy) and its actual social norms (pragmatic legitimacy).³ In the context of software, this manifests as the difference between the "official process" → "All requests must go through our ticket management system" and the "actual process" → "Just DM me the file".

When an organization's "system of record"⁴ becomes too cumbersome, optimizing for data storage rather than investing in a system of engagement, it loses its pragmatic legitimacy. Employees, driven by a rational desire to be efficient and get real work done, increasingly resort to tools and workflows outside official systems. This is not a failure of compliance; it is a vote of no confidence in the organization's coordination infrastructure. Research shows that around 41 % of employees acquire, modify, or create technology that their IT departments are unaware of, a trend projected to rise unless organizations address underlying usability and workflow frictions.⁵

This widespread use of "Shadow IT" isn't just about security risk; it signals that the cognitive and coordination load imposed by traditional organization tools diverts attention from meaningful work toward managing and reconciling fractured contexts. When the tools themselves demand attention rather than enable flow, people rationally choose alternatives that feel more efficient, even if they compromise transparency, consistency and control.

The workforce is increasingly signaling that the system of record model no longer meets their needs. These tools require employees to act as data entry clerks, filling in forms that provide no immediate value in return. This creates the Data Entry Fallacy: assuming that value lies in capturing data rather than supporting the flow of work. The predictable outcome is low-quality data ("garbage in, garbage out"), which degrades the reliability of the organizational intelligence these systems aim to produce.

Incremental improvements to project management tools or documentation platforms cannot resolve this crisis; they simply reproduce the same underlying ontological error. What is required is a foundational re-design of the organization's operating system. We must move from software that models things (nouns) to systems that orchestrate processes (verbs), from platforms that track motion to architectures that enable meaning to emerge.

Part II: The Diagnosis – The Ontological Flaw

Substance vs. Process: The Metaphysical Error

The root of today's coordination problems is ontological. Modern software is built on an underlying ontology that treats the world as a set of static things to be stored and managed; users, records, documents and assets. This reflects a model of that reality that privileges "stable" objects rather than unfolding processes.⁶

That's why organization tools center on Users, Documents, Records and Assets, static nouns in tidy tables. Time becomes an afterthought: just another timestamp on another row. This works fine for inventory management, but for human collaboration, it's a disaster.

• Work isn't a thing (noun)
• Work is a process (verb), a flow of agreements, handovers, decisions, and changes over time.⁷

When tools are designed around static objects, the process becomes invisible. It slips into the white space between the rows, the unspoken negotiations, the subtle handovers, the rhythm of a team. And because the software can't see the flow, it can't support it. Humans end up carrying the mental model of "where we are" and "what comes next," doing orchestration the tools should be doing for them.

The Language/Action Perspective (LAP)

A helpful way to understand this gap is through the Language/Action Perspective.⁸ Developed by Terry Winograd and Fernando Flores in the 1980s, LAP challenges the old "information processing" model of software, rather it treats them as networks of commitments made through language.

In LAP, the core unit of work isn't the task or the ticket, it's the "conversation for action", the loop through which a commitment is created and completed:

1. Preparation — context is set
2. Request/Offer — someone asks for something or offers to do it
3. Negotiation — accept, decline, or counter-offer
4. Performance — the action is carried out
5. Completion — "I'm done"
6. Satisfaction — "This meets the standard"

Most tools capture only the Performance step. They record that something happened, but not how the commitment was formed. The earlier steps where ownership, expectations, and standards are actually set are invisible. That's how tasks drift: not because people don't care, but because the promise behind the work was never clearly made, negotiated, or agreed.

Process Philosophy and Structural Memory

To bring LAP into modern software, we draw on the process philosophy of Alfred North Whitehead. Whitehead argued that reality is made of events unfolding over time, not static substances.⁹ In this view, a project isn't a container of tasks, it's a stream of activity: commits, conversations, decisions, designs, and meetings. These moments are the real "entities" of work.

This shift underpins the idea of process media. Unlike a traditional database, which treats work as static records, process media treats the flow of digital activity as the organization's primary material. When the system captures events as they happen, it produces structural memory. Documentation describes work; structural memory records it.

• Documentation relies on people summarising events after the fact.
• Structural memory emerges directly from the events themselves, as they happen.

Structural Memory is what actually happened. Because each interaction is captured as a structured event, the record forms automatically as a byproduct of doing the work. There's no separate "reporting" step. The data is the work.

This enables "Immediation", making the real state of a process visible in real time, the system infers progress from the user activity stream. When the flow slows, the status reflects it automatically. The system represents work as it is becoming, not as it was last remembered.

Part III: Process & Organizational Intelligence

Process media is the technical foundation of organizational intelligence. By capturing work as a stream of structured events rather than scattered documents and status updates, it generates structural memory or history, a reliable record of what actually happened, not what people remember. This creates the conditions for feedback loops, real-time visibility, simulation, and learning. In other words, process media is a powerful form of data that, with the right analysis, can produce organizational intelligence.

The solution to the crisis of coordination isn't a feature but an architecture. The loop (Map → Execute → Store → Analyze) is a simple improvement cycle that will look familiar, as many continuous-improvement frameworks follow a similar pattern. Eddy makes this practical by implementing each phase as a specialised digital tool, using an integrated process-based approach. This turns the organization from individuals doing their best into a group that can act with shared clarity and collective purpose.

3.1 Map: The Constitution of Work

The first phase in organizational Intelligence is the externalisation of tacit knowledge. In most organizations, the "how" of work is tribal: Ask Sarah, she knows how we do the safety audit or It depends on which department you ask. This reliance on implicit knowledge makes the organization fragile; when Sarah leaves, the process leaves with her.

In this architecture, the map editor acts like a constitutional convention. It forces the organization to define the map of the process. This map isn't a diagram for a slide deck, it's a runnable, enforceable graph that turns vague policies into executable code.

The Map defines the "Game Board".⁴ It specifies:

• Roles — abstract participants (e.g., "Safety Rep,")
• Stages — the distinct states of the conversation
• Transitions — the allowed moves in the map, defined by conditional logic
• Blocks — the specific media and data inputs required to progress

Externalising the work turns previously shapeless admin into something concrete. It forces the organization to confront the reality of its own bureaucracy. Often, mapping the process reveals gaps in understanding. Eddy forces the organization to be specific, and that clarity exposes ambiguity that was previously invisible.

3.2 Execute: The Performance of Agency

The second phase is execution, and it is not about ticking boxes; it's about taking your turn in a defined process. The Session is the runtime version of the Map; the process unfolding in time.

The One-Link Invitation

Eddy uses a simple invitation. A single email arrives that looks like any standard request; familiar, lightweight, easy to open. When the user clicks "Start," they accept the invitation and step into the process.

From that moment, the Session environment takes over. The user is guided along the paths in a clear, structured way, and each step is anchored to the definitions encoded in the Map. Once inside, the process provides the boundaries and expectations. There is no ambiguity, because the map itself holds everyone to the same standard.

This approach uses the reach of email without inheriting its noise. It offers a low-friction way to invite people into a coordinated, multiplayer experience, without asking them to navigate dashboards, manage accounts, or learn a new tool before they begin.

Structured Agency & Game Semantics

Under the hood, a Session works as a structured dialogue between the user and the system. At each step, the Map defines the valid moves, and the user exercises agency by choosing one of them.

• User: selects a valid move from the options available at their stage
• System: checks that choice against the rules encoded in the Map

If the choice is valid, the process advances. Each step becomes a verified speech act tied to the definitions of the map.

The user doesn't need to understand the full process, only the options available on their turn. This removes the mental load of figuring out what comes next and lets them focus on the substance of the work.

The Manager as Game Master

In this model, the manager shifts from bureaucratic policeman to Game Master:

• The bureaucratic policeman chases people for updates and enforces compliance through reminders, a low-value, high-friction role nobody wants to play.
• The Game Master designs the workflow: shaping the narrative, setting the constraints, and defining how the process should unfold. Staff move through this structure as players in a shared system, and the invisible work of coordination, handovers, timing, expectations, becomes explicit and tangible. A well-designed map is appreciated because it makes everyone's work easier and clearer, reducing ambiguity and freeing people to focus on the real work.

This replaces policing with transparency. When the process map is visible to everyone, accountability emerges naturally. If work is stuck, it shows up on the board, the system surfaces the signal, not the manager.

3.3 Store: Structural Memory

The third phase solves the Data Entry Fallacy. In most systems, data entry happens after the real work is done. It's painful admin work, people dislike it, and the quality suffers. In Eddy, process media flips this: the data is created as a side-effect of doing the work itself.

Every input block in a Session is linked directly to a structured column in a Data Table, so the act of completing a stage is the act of creating the record. There's no separate reporting phase. This produces structural memory, a precise record that reflects what actually happened, not what someone remembered or intended to update later.

This level of detail becomes the foundation for a "live" (real-time) model of an organization's processes, which reflects the actual, current state of affairs. It shows how the work actually flows. Instead of static documents or postmortem reports, the organization gains a real-time reflection of its own operations. It shifts the organization from a system of remembrance (relying on human recall) to a true system of record grounded in reality.

3.4 Analyze: Closing and Starting the Cybernetic Loop

The final phase is improvement. Most organizations struggle here because they don't have clear feedback loops; problems only surface when someone heroic notices an issue and pushes against the system to fix it.

In Eddy, improvement is built in. Because the process is digital and the data is structured, the organization can see how its own workflows behave. It becomes possible to analyze performance through a Process Intelligence hub:

• Bottlenecks — Where does the flow stall?
• Cycle time — How long does the whole process take end to end?
• Handoff latency — How long does work sit idle between roles?

This gives the organization a kind of second-order awareness, the ability to observe and adjust itself. What's learned in the "Analyze" phase feeds the next "Map" phase, allowing structures to evolve rather than decay.

This is the essence of organizational intelligence: the capacity to learn as a system, not just as individuals.

Part IV: A Complement and Counterpoint in the Age of the LLM or Generative AI

We have been drowning in the hyperbole, uncertainty and fear of LLMs. Software engineering, a field recently beset by huge, high-profile layoffs,¹⁰ has been declared "dead" what feels like multiple times in the past few months.¹¹ Creative industry professionals like artists, writers and designers are bracing themselves in a time when people are struggling to distinguish AI content from the "real" thing. New Zealand's top book awards committee ruled that books with covers made with LLM assistance would be disqualified from consideration.¹² And those are just a few examples of controversy from recent memory. We stand at the edge of an ocean of ethical, existential and informational risk, whose scale seems beyond fathom.

We can't pretend to know what's going to happen in this unfolding era of the LLM. But AI is flooding into our lives and organizations faster than most can make sense or keep track of. One thing seems clear; it's here to stay. Yet, all this hype and fear both obfuscates and shores up the question: What is work? Is work simply the production of content or information or commodities?

Eddy embodies our proposal that the answer is a resounding, "no." The idea that work is equivalent to production depends on the ontology or worldview articulated earlier, that the world is merely a collection of things. But the world is not just a bunch of discrete entities. It is a network of dynamic, interconnected processes. For us, work is also the problem of organizing, coordinating, tracking and auditing these processes.

So while much of the tech industry rushes to capitalise on LLMs and their productive power, Eddy is here to say two things to them. One, you're wrong; and, two, you're going to need help with that. Our tool has the potential to accommodate and leverage the use of LLMs while also providing an auditable, transparent record and visualization of it. Legislative and regulatory bodies will be seeking to govern, restrict and guide its use. We are in a prime position to facilitate that.

AI use could be dangerous and inefficient if left unchecked in the realms of "Shadow IT." When AI is dropped into an unstructured environment of loose documents, scattered messages, and unclear processes, it doesn't make things clearer. It just amplifies the noise. AI only becomes useful when the organization itself has structure. Models need rules, boundaries, and shared, explicit context to act safely. This is where process media changes what's possible. When the workflow is defined (the Map) and the data is clean (structural memory), AI can take part in a way that's transparent, auditable and accountable. It works within the process rather than floating above it.

Without structure, AI is just noise, and risk. With the right constraints, it has a chance to become part of the organization's formalised processes and intelligence.

Part VII: Conclusion – The Invitation to Meaning and the Future of Work

We didn't set out to build another productivity tool. The world already has plenty of apps that speed things up — faster chats, more communication, easier tasks, prettier documents. We set out to answer a quieter, harder question: What kind of technology would make work feel more coherent, more transparent, more connected, and ultimately, more human?

We believe the answer is Process & Organizational Intelligence.

By shifting the foundation of our tools from things to processes, from tickets to commitments, and from messy archives to real-time modeling, we can unlock organizational intelligence. We can build organizations where the friction of meta-work is lifted, where managers act as facilitators and domain experts rather than bureaucratic enforcers, and where the rhythm of work is shaped by meaning and reflection rather than pressure. We are invested in an entirely new horizon of work, a degree of coordination and collaboration that can be easy to theorise but is impractical without the right tool.

We're building Eddy with and for people who care about clarity, continuity and learning from how work actually unfolds. Organizational Intelligence isn't a doctrine for us; it's a practical frame for exploring better ways of working together.

If this way of thinking is interesting to you, please get in touch. We'd love to hear from you!

The current way of working is unsustainable. It is time to stop managing the artifacts of work and start designing the intelligence of the organization.