CoP= KAYS + COLLIN

On By konstapelIn Uncategorized

go to the summary.

The article argues that modern organizations fail not because of missing tools or data, but because of a lack of coherence.

Real knowledge work happens in cycles and rhythms, while management systems treat it as linear.

The frameworks COLLIN (work cycles) and KAYS (thinking dimensions) explain this mismatch.

Gripler is presented as a coherence infrastructure that learns an organization’s natural rhythms and preserves knowledge.

In an AI-driven world, coherent action—not speed—is the true competitive advantage.

J.Konstapel, Leiden, 22-12-2025.

This blog is about the merge of KAys and Collin.into a Community of Practice (CoP).

What Organizational Coherence Means to the Market

Why Organizations Can’t Coordinate (Even When They Try)

It’s 2025. A biotech company has invested in real-time dashboards, AI-driven task management, and wellness initiatives. Every metric suggests the organization should be firing on all cylinders.

But something is broken. Not visibly broken—the numbers don’t show it. But the people know it. The research team operates in four-week deep cycles. The commercial team moves in one-week sprints. The leadership team demands daily updates. Nobody is working at the same frequency, yet everyone is convinced their rhythm is the right one.

When a breakthrough happens, it’s chaos to scale. When someone exceptional leaves, nobody can articulate what made them exceptional—their rhythm dies with them. The organization hires to replace them, brings in someone with equal credentials, but the team’s coherence collapses. It takes six months to rebuild.

This isn’t a management problem. It isn’t a tools problem. It’s a coherence problem.

Most organizations have never asked the question: At what frequencies do our different teams naturally operate, and are those frequencies compatible? They measure output, efficiency, engagement. They don’t measure coherence—the alignment of oscillatory patterns across the organization.

Until now, there was no way to.

The Problem with Linear Thinking in Non-Linear Work

The dominant management paradigm since the Industrial Revolution has been linear: input → process → output. Gantt charts. Waterfall. Sprints. Roadmaps. These frameworks assume that work is sequential, predictable, and decomposable into independent tasks.

They work fine for assembly lines. They fail catastrophically for knowledge work, research, innovation, or anything that requires genuine coordination across diverse teams.

The reason is simple: Knowledge work doesn’t flow linearly. It oscillates. A researcher alternates between hypothesis and experiment, pattern and deviation, focus and reflection. A designer cycles through constraint recognition, ideation, iteration, and validation. A team of researchers doesn’t move in lockstep through phases—different researchers are in different phases simultaneously, creating an overall oscillatory system that produces breakthroughs when the oscillations are in phase.

But traditional project management software treats all work as a series of tasks with start dates and end dates. It flattens the oscillation into a line. And in doing so, it destroys the very thing that makes knowledge work productive: the natural rhythm of the work itself.

This creates what we might call the “Coherence Gap”—the distance between how work actually happens (oscillatory, rhythmic, multi-phased) and how organizations try to manage it (linear, task-based, milestone-driven). Close the gap, and teams become dramatically more productive. Leave it open, and you get burnout, knowledge loss, and the perpetual sense that despite all your tools and metrics, something fundamental is broken.

What COLLIN + KAYS Actually Are

COLLIN and KAYS are not software. They’re frameworks for understanding organizational coherence. They’re ways of thinking about how teams and organizations actually work.

COLLIN describes the learning cycle that all complex work goes through: Context observation, Operation execution, Learning reflection, Learning integration, and then back to New context. It’s not linear—it’s continuous. You observe, you act, you learn, you integrate, and immediately you’re back in a new context with more information. The cycle keeps turning.

Importantly, COLLIN doesn’t prescribe a pace. Different work requires different speeds. Research might cycle through these phases in four-week intervals. Responsive operations might cycle weekly. The point is recognizing that the cycle exists and that different work has different natural frequencies.

KAYS describes the multi-dimensional nature of how people and organizations actually think and move. It’s a framework built on decades of work by researchers like David Kolb (how people learn), Will McWhinney (how people perceive reality), and others who recognized that organizations don’t think in one way—they think in four or five fundamentally different ways simultaneously.

KAYS maps these dimensions: the structures we build (how organizations stabilize), the goals we pursue (what we’re trying to become), the operations we execute (what we actually do), the functions we perform (the role we play in larger systems), and the domains we inhabit (the context we’re embedded in).

The power of KAYS is that it provides a common language. When a structural thinker and a visionary thinker are trying to coordinate, they’re not speaking the same language. One sees constraints and rules; the other sees possibilities and potential. KAYS makes that translation explicit. It says: Here are the five ways we need to think about this problem, and they’re all valid. The coherence comes from moving through all five simultaneously, not from everyone agreeing on one.

Together, COLLIN + KAYS create a framework for organizational coherence. COLLIN says: Work happens in cycles. KAYS says: Organizations think in multiple dimensions simultaneously. The combination means: Coherent organizations are ones where cycles align across dimensions, where different ways of thinking are held in productive tension, and where the organization can move through its learning cycles without losing people, knowledge, or direction in the process.

How Gripler Makes COLLIN + KAYS Actionable

This is where infrastructure matters. COLLIN + KAYS are conceptually powerful, but diagnosing coherence in a live organization requires measurement, learning, and continuous adjustment. That’s what Gripler does.

Gripler implements COLLIN as a continuous cycle in software. Its COMM framework (Context, Operation, Measurement, Memory) mirrors the learning cycle: observe context, execute operations, measure results, extract patterns for the next cycle. But unlike a static framework, Gripler’s cycle runs continuously, in real-time, across all the data flowing through an organization.

Every interaction, every task completion, every decision creates data. Gripler doesn’t just log it—it asks: What pattern is this? How does it relate to patterns we’ve seen before? What can we predict about what comes next? The E-Memory system extracts patterns, predicts outcomes, and feeds those insights back into the next cycle.

The result is infrastructure that gets smarter the more it’s used. After three months, it understands your team’s natural rhythm. After six months, it can predict which combinations of team composition, task type, and phase state lead to breakthrough. After a year, it has captured “coherence templates”—replicable patterns of how high-performing teams actually work.

More importantly, these templates are specific to your organization. Your biotech team’s breakthrough rhythm is different from another biotech team’s. Gripler learns your rhythm, not a generic one. And when someone new joins, they learn not from a handbook, but from the actual pattern that made your team successful.

That last point is crucial: Gripler solves the knowledge transfer problem. When a great researcher leaves, their rhythm—the thing that actually made them great—dies with them. Gripler captures it. The next researcher can’t become them, but they can work with the rhythm that worked, and the team’s coherence survives the transition.

Why This Matters to the Market Now

The market is saturated with tools that optimize throughput. More dashboards. Faster sprints. Better automation. The assumption is always the same: If we just move faster and measure more precisely, we’ll win.

But this assumption is failing. Organizations are burning out. Knowledge is leaking. Teams that should be brilliant are mediocre. The problem isn’t the pace—it’s that the pace is incoherent. Everyone is accelerating independently, and the overall system becomes chaotic.

Three forces are converging to make coherence suddenly valuable:

First: The Burnout Crisis. Organizations finally understand that burnout isn’t a personal weakness; it’s a structural problem. It happens when people are forced to work at rhythms that aren’t sustainable for their type of work. A knowledge worker on constant on-call burns out differently than someone in a four-week research cycle. The solution isn’t generic wellness—it’s aligning rhythms. Organizations that can do this will retain talent; those that can’t will hemorrhage it.

Second: AI Saturation. AI makes thinking cheap. Everyone can generate content, make predictions, optimize processes. What becomes rare is coherence—the ability to move together toward something meaningful. In a world where content is abundant, the organizations that win are the ones where diverse teams actually stay synchronized. This requires coherence infrastructure.

Third: The Shift to Regenerative Models. The extractive model—maximize throughput, externalize costs, optimize shareholder return—is running out of social license. Organizations are starting to ask: What would it look like to optimize for sustainability? For deep work? For human flourishing? COLLIN + KAYS are built on exactly these principles. They’re not compatibility patches on an extractive model; they’re the architecture of a sustainable one.

What Changes When Coherence Becomes Measurable

Once you can measure and manage organizational coherence, several things shift:

Knowledge becomes transferable. Instead of losing institutional knowledge when people leave, you capture the patterns that made those people valuable. New hires don’t learn from manuals; they learn by joining a system that encodes successful patterns. This compounds over time—your oldest teams have the richest coherence templates.

Burnout becomes predictable and preventable. You can see which teams are oscillating sustainably and which are approaching collapse. And because you understand the rhythms, you can often fix it by changing the context, not by asking people to work harder.

Teams become composable. If you understand the coherence patterns of different teams, you can deliberately create new team combinations that maintain coherence across disciplines. The breakthrough happens at the boundary between fields, not within them. COLLIN + KAYS make those boundary coherences visible and designable.

Organizational learning accelerates exponentially. Most organizations learn once. A team figures something out, documents it (usually poorly), and then five other teams figure out the same thing independently. With coherence infrastructure, the pattern is captured the first time and available to all teams immediately. Each cycle through the COLLIN loop makes the whole system smarter.

Mergers and acquisitions stop failing. The hidden problem in most M&A is that the two organizations have different oscillatory patterns. They’re literally operating at different frequencies. Coherence infrastructure makes those incompatibilities visible and, more importantly, provides a framework for harmonizing them.

The Market Opportunity

The market opportunity here is not in replacing project management tools. It’s in becoming the infrastructure layer that makes organizational coherence visible, measurable, and manageable.

Current market players in this space—Workday, Lattice, Planview, Brightidea—optimize within their category. They’re better dashboards, better data, better automation. But they all operate on the same fundamental assumption: that work is linear and decomposable. They make that assumption more efficient, but they don’t question it.

An organization that builds coherence infrastructure doesn’t compete in those categories. It sits underneath them. It feeds them data that wasn’t visible before. It makes them more valuable by giving them context they didn’t have.

The addressable market is large. Every organization with more than fifty people has a coherence problem. But the early market is smaller and more valuable: deep tech companies, research organizations, healthcare systems, any place where knowledge work is central and the loss of institutional knowledge is catastrophic. These organizations will pay premium prices for coherence infrastructure because coherence directly impacts their core value creation.

The deeper value, though, is lock-in through intelligence. After two years of continuous learning, a coherence system understands your organization in ways no consultant, no external hire, no competitor can replicate. Your coherence templates are unique. Your learning curves are specific to your domain. The system that knows all of this is indispensable.

Why Now

The convergence of three technology trends makes this possible now in ways it wasn’t before:

Machine learning has matured enough to run continuous pattern extraction without human intervention. You don’t need a PhD in statistics to see what the data is telling you.

Event-driven architecture (message queues, real-time data flows) means you can observe organizations continuously without disrupting them. You don’t need to build a new system; you can sit on top of existing infrastructure.

LLMs have created a translation layer between domain-specific language and general reasoning. A coherence system can understand your organization’s language—your terminology, your processes, your implicit knowledge—and reason about it without requiring everything to be formalized first.

Put these together with 50+ years of systems theory (from Wiener to Beer to McWhinney to Hamilton), and you have something that’s actually possible to build. The theory was always there. The technology finally caught up.

What Makes COLLIN + KAYS Different

There are frameworks everywhere. What makes COLLIN + KAYS different is that they’re not imposed from outside. They’re not “Best Practice #47 from McKinsey.” They emerged from people who spent decades actually working in complex organizations, learning what patterns repeat, what assumptions fail, what actually creates coherence.

And importantly, they’re not deterministic. They don’t say “Do this and you’ll win.” They say “Here are the dimensions along which organizations move. Here are the cycles that all work goes through. Now, what’s your rhythm? What does coherence look like for you?”

This humility—refusing to impose a single model—is exactly what makes them scalable across wildly different domains. Biotech teams and school systems operate very differently, but both move through COLLIN cycles and both think in the KAYS dimensions. The framework holds. The specifics change.

Conclusion: The Coherence Economy

We’re not yet in a world where organizational coherence is a central concern. Most conversations are still about efficiency, speed, productivity. But that’s changing. Organizations are discovering that the best people don’t want to work in chaotic systems, that burnout has a structural cause, that knowledge loss is expensive, and that most of their investment in tools and processes doesn’t actually improve the things that matter.

When they make that discovery, they’re looking for something they don’t yet have a name for. They’re looking for coherence infrastructure.

COLLIN + KAYS provide the conceptual framework. Gripler provides one concrete implementation. But the opportunity is much larger: It’s to become the operating system for organizations that have decided to optimize for coherence rather than extraction.

That shift—from “How do we squeeze more out?” to “How do we create conditions where excellence can be sustained?”—is coming. The organizations that build the infrastructure for it first will own the coherence economy.

Everything else is just moving faster on a broken path.

.

Beyond Efficiency: Coherence Infrastructure and the Viable Organizational Form

Introduction: The Coherence Gap and Its Structural Cause

The contemporary organizational landscape presents a peculiar paradox. Despite unprecedented investment in productivity technology and management frameworks, collective intelligence remains fundamentally elusive. The problem, however, is not one of implementation or effort. It is structural.

This essay argues three connected claims:

First, that organizational dysfunction stems not from individual failure or poor strategy, but from the breakdown of synchronized learning cycles (COLLIN) and multi-dimensional coherence (KAYS) across organizational scales.

Second, that the formal hierarchical organization is structurally incapable of maintaining these cycles intact—it necessarily breaks them.

Third, and most radically, that Communities of Practice are not peripheral to organizations but the viable organizational form itself—the only structure capable of maintaining coherence in knowledge work. The formal organization should not be improved; it should be replaced.

What follows is an exploration of why this is theoretically sound and what it means for support infrastructure.

Part 1: Why Linear Systems Fail at Knowledge Work

The Three Knowledge Types and Formal Decomposition

All knowledge work requires the simultaneous alignment of three distinct knowledge types.[1]

Why-knowledge concerns purpose, intention, and significance. Why are we doing this work? What difference does it make? What do we care about?

What-knowledge concerns reality, pattern, and structure. What patterns exist? What constraints must we work with? What do we actually see?

How-knowledge concerns action, method, and execution. What moves can we make? What produces change?

In healthy knowledge work, these three remain in continuous dialogue. Purpose guides observation. Observation corrects purpose. Method connects them both.

The formal hierarchical organization systematically decouples these knowledge types.

Strategic planning departments monopolize Why-knowledge: they set vision, define goals, establish direction. Operations departments are confined to How-knowledge: they execute, manage resources, implement tasks. The observation of actual What-knowledge—the patterns emerging from lived practice—is lost in the noise, fragmented across departments, never permitted to inform strategy.

The result is strategic hallucination: leadership believes something about the organization that doesn’t match operational reality. Operations execute tasks misaligned with actual purpose. Critical feedback that could correct both is suppressed.

This is not a communication problem. It is architectural. Hierarchy necessarily creates this separation. The higher you go, the more abstracted you become from actual practice. The deeper you go into practice, the harder it is to see larger patterns. The formal organization makes this separation structural.

The COLLIN Cycle and Its Destruction by Hierarchy

The COLLIN framework describes learning as a natural, continuous cycle:[2]

  • Context: Understanding the situation, observing patterns
  • Operation: Acting, experimenting, doing work
  • Learning: Reflecting on results
  • Learning Integration: Extracting patterns, building understanding
  • New Context: Equipped with new understanding, return to observation

This is not a process to be completed; it is a continuous spiral. Each cycle should feed into the next. Each iteration should make the system smarter.

But formal organizations break this cycle systematically.

Strategic decisions come from the top, handed down without context observation (Context is skipped). Operations execute without the strategy makers seeing results (Operation happens, but Measurement is blocked). Lessons from the field never reach strategy (Integration is prevented). The next cycle repeats the same mistakes (New Context never informs Context at the top).

This is the fate of all matrix-organized, hierarchically-divided, functionally-separated organizations. No individual is at fault. The structure itself makes it impossible for the full COLLIN cycle to complete.

What happens instead is that organizations segment the cycle. Strategy has its own cycle (Context from market data, Operation as planning, Learning as post-mortems, Integration as new strategy). Operations has its own cycle (Context from tasks, Operation as execution, Learning as standups, Integration as process improvement). These cycles never sync. The organization learns two separate things that don’t connect.

Knowledge workers experience this as the constant frustration that “strategy doesn’t understand operations” and “operations doesn’t get what strategy is trying to do.” This is not individual misalignment. This is the inevitable consequence of structural separation.

Part 2: The Multi-Dimensional Coherence Problem (KAYS)

How Organizations Actually Think

If the COLLIN cycle shows the problem of linear decomposition, KAYS reveals why that decomposition is structurally inevitable in formal organizations.

Organizations do not think in one way. They simultaneously engage multiple modes of meaning-making. Will McWhinney documented four fundamental pathways:[3]

Structural thinking (rule-based, order-focused): “What are the rules? What constraints exist? How do we maintain stability?”

Sensory thinking (empirical, data-driven): “What do we observe? What patterns do we see? What does the data show?”

Mythic thinking (visionary, meaning-driven): “What is possible? What could we become? What do we care about?”

Social thinking (relational, consensus-based): “What do others think? How do we align? What creates belonging?”

A healthy organization engages all four simultaneously. Structural thinking provides stability; mythic thinking provides direction; sensory thinking grounds both in reality; social thinking creates coherence.

But formal organizations institutionalize these divisions. They create departments:

  • Finance and Compliance departments monopolize structural thinking (rules, constraints, risk management)
  • Data and Analytics departments monopolize sensory thinking (measurement, empirical observation, reporting)
  • Strategy and Product departments monopolize mythic thinking (vision, possibility, meaning)
  • HR and Culture departments monopolize social thinking (relationships, belonging, consensus)

These departments then speak past each other because they are literally thinking in different languages.

Finance says “that’s too risky” (structural). Strategy says “but it creates the future we want” (mythic). Data says “here’s what the market shows” (sensory). HR worries “will people embrace this?” (social). None of them are wrong. They are just operating in different dimensions.

A healthy organization would hold all four simultaneously: “Yes, we need the stability (structural), but we’re also reaching for what’s possible (mythic), grounded in what we observe (sensory), in a way that people can align around (social).”

But formal organizations can’t do this. The structure forces choice. You end up with organizations that are either rule-bound (structure dominates) or chaotic (mythic dominates), either data-obsessed (sensory dominates) or politically fractured (social dominates).

David Kolb’s research on learning cycles adds another dimension: people don’t just think in different modes; they also move through different learning phases (concrete experience, reflective observation, abstract conceptualization, active experimentation).[4] And different roles in the organization get trapped in different phases:

  • Operators are stuck in Concrete Experience (doing the work)
  • Analysts are stuck in Reflective Observation (measuring results)
  • Strategists are stuck in Abstract Conceptualization (conceptualizing principles)
  • Nobody is allowed back to Active Experimentation at the strategic level

The full learning cycle never completes. Each function cycles internally. They never sync.

The Coherence Cost

The cost of this dimensional separation is severe.

Organizations trying to innovate with strategy separated from operations discover that “the strategy never works” because it wasn’t built with knowledge of what’s actually possible. The gap between strategic vision and operational reality becomes a canyon.

Organizations trying to move fast with data separated from meaning discover that “people resist change” because the change was optimized for efficiency but nobody explained why it matters. People comply or leave; they don’t commit.

Organizations trying to be stable with structure separated from social dynamics discover that policies work for 80% of the population and create pathological resentment in 20%. The 20% are often the people most needed (edge cases, misfits, divergent thinkers) because the policy was designed without understanding social complexity.

The formal organization cannot maintain KAYS coherence because it is architecturally structured around isolation of these dimensions.

Part 3: Communities of Practice as the Viable Organizational Form

What Communities of Practice Actually Are

Communities of Practice (CoPs) are not teams. They are not departments. They are not committees. They are groups of people who care deeply about something, who learn how to do it well together, and whose shared understanding creates meaning.[5]

Wenger’s foundational insight was recognizing that the real work of organizations happens in CoPs, not in the formal structure. A formal department of “customer service” might be dysfunctional, but within it, the best agents form a CoP—an informal group that has developed actual expertise about how to handle difficult customers. That CoP is where the real learning and excellence lives. The formal structure is administrative overhead.

Lave’s research on apprenticeship showed that expertise doesn’t develop through instruction but through participation in authentic practice. A master weaver doesn’t teach apprentices through explanation; the apprentice learns by participating in weaving, gradually moving from peripheral participation toward full membership.[6] The learning is inseparable from the practice. The practice is the community.

What Brown & Duguid added was radical: Communities of Practice are not peripheral to organizations; they ARE the organization. The formal hierarchy is the illusion.[7]

The implications are stark. If the real work happens in CoPs and the real learning happens in CoPs, then the formal organization—with its separation of strategy from operations, structure from meaning, data from purpose—is not just inefficient. It is anti-learning. It systematically prevents the very thing the organization claims to want: coherence, innovation, collective intelligence.

How CoPs Maintain COLLIN Cycles Intact

A Community of Practice is built around shared practice—a domain of activity that members care about and engage in together.

A practice creates context automatically. If you’re part of a community of epidemiologists, you’re constantly observing disease patterns (Context). You’re running studies and interventions (Operation). You’re seeing what works and what doesn’t (Measurement). You’re integrating new understanding into how you approach the next case (Learning Integration). You’re immediately back in a new context with more sophistication (New Context). The cycle is intrinsic to the practice itself.

Critically, all members of the community cycle through all these phases simultaneously. The senior researcher and the novice are both in the same COLLIN spiral, just at different levels of expertise. The research results immediately inform how the next research question is framed. There is no gap between knowing and doing.

This is radically different from a formal organization, where the cycle is broken:

  • Strategy teams Context-and-Conceptualize, handing off to Operations
  • Operations teams Operate, handing off to Analytics
  • Analytics teams Measure-and-Report, handing off back to Strategy with a lag of months or quarters
  • Nothing feeds back in real time
  • The newest learning never reaches the original Context-observation

In a CoP, by contrast, the cycle is continuous, unbroken, and immediate. Every member is simultaneously learning and practicing. The learning informs the next iteration of practice within days or hours.

This is why CoPs are radically more adaptive than formal organizations. They are learning systems by structure, not by intention.

How CoPs Maintain KAYS Coherence

A Community of Practice naturally engages all four modes of thinking simultaneously because the community is composed of diverse people, all focused on the same practice.

The structural thinkers in an epidemiology CoP ask: “What protocols, what safeguards, what regulations must we maintain?” This is essential.

The sensory thinkers ask: “What does the disease surveillance data show? What patterns do we see?” This is essential.

The mythic thinkers ask: “What could we become? What would it mean to actually eliminate this disease?” This is essential.

The social thinkers ask: “How do we get communities to trust public health? How do we build together?” This is essential.

Critically, all of this happens in one conversation. The structural person isn’t in compliance; the sensory person isn’t in data analytics. They are in the same room because they are part of the same community committed to the same practice.

This is why CoPs are capable of holding genuine paradox. They can be both principled (structural) and pragmatic (sensory), both ambitious (mythic) and consensual (social), because the same people embody all these dimensions. There is no department that monopolizes one.

The diversity of the CoP isn’t a management problem; it’s a cognitive resource. The diversity maintains coherence because it prevents any single dimension from dominating.

Lave and Wenger documented this in studies of communities from tailoring shops to naval navigation: the communities that thrived were those with genuine diversity of thought and background, because that diversity maintained the tension that keeps learning alive.[8]

Oscillatory Coherence in Communities of Practice

At the deepest level, CoPs maintain what we might call oscillatory coherence—the phase-locking of coupled oscillators that Wiener and Ashby identified as fundamental to all self-regulating systems.[9]

In a formal organization, different departments oscillate at different frequencies and phases:

  • Strategy cycles quarterly or annually
  • Operations cycles weekly
  • Finance cycles monthly
  • HR cycles continuously
  • These cycles are decoupled. No phase-locking occurs.

In a Community of Practice, members oscillate at compatible, mutually-reinforcing frequencies.

Why? Because they are all engaged in the same practice. The pace of practice sets the rhythm. A research community’s pace is set by the pace of experiments. A clinical community’s pace is set by patient encounters. A creative community’s pace is set by iteration cycles. All members, regardless of formal role, move at the pace of the practice.

This creates automatic phase-locking. Senior and novice, theorist and practitioner, thinker and executor all oscillate together because they are participants in the same activity. There is no need to “synchronize” them; they self-synchronize through engagement in shared practice.

This is the mechanism by which CoPs avoid burnout. People are working at unsustainable intensity not because they are weak, but because they are forced to oscillate at frequencies incompatible with their nature. A 24/7 on-call emergency room creates unsustainable oscillation. A research community with natural cycles (intense periods, integration periods, planning periods) maintains sustainable rhythm.

The formal organization disrupts these natural rhythms. CoPs preserve them.

Part 4: Why Formal Organizations Are Structurally Inviable for Knowledge Work

The Impossibility Theorem

If the above analysis is correct, then formal hierarchical organizations face an internal contradiction for knowledge work:

They attempt to manage knowledge work through task decomposition and functional separation. But knowledge work requires:

  1. Continuous COLLIN cycles (which requires all three knowledge types coupled)
  2. Multi-dimensional KAYS thinking (which requires all four modes engaged simultaneously)
  3. Oscillatory coherence (which requires phase-locking across scales)

Task decomposition and functional separation necessarily prevent all three.

Therefore, formal organizations are structurally incapable of managing knowledge work effectively. The problem is not implementation; it’s the form itself.

This is not new. It has been documented repeatedly:

  • Lave and Wenger showed that real learning happens in CoPs, not in formal training
  • Brown & Duguid showed that real innovation happens in CoPs, not in R&D departments
  • Nonaka and Takeuchi showed that knowledge creation happens in dynamic teams, not in silos
  • Pentland showed that the strongest predictor of team performance is interaction patterns, not individual intelligence or formal structure

The evidence is overwhelming. Yet organizations continue to optimize within the formal structure, adding layers of communication, adding more meetings, hiring “cultural change consultants,” all while maintaining the fundamental separation that prevents COLLIN cycles, KAYS coherence, and oscillatory phase-locking.

The Historical Accident of Formal Organization

The hierarchical organization was not designed for knowledge work. It was designed for industrial production.

Frederick Taylor’s Scientific Management (1911) and Max Weber’s Bureaucracy (1922) created the formal organization to optimize routine work with standard outputs.[10] Manufacturing, logistics, administration. In these domains, decomposition and hierarchical control work remarkably well. You break down the task into steps, assign each step to a specialist, measure output, optimize speed.

This worked so well for industrial production that the form was extended to everything: universities, hospitals, governments, banks, technology companies. We tried to apply industrial organization to domains where it is fundamentally incoherent.

The tragedy is not that we use the wrong form. It’s that we don’t recognize it’s the wrong form. We keep optimizing it—better project management, flatter hierarchies, more cross-functional teams—while leaving the fundamental structure intact.

Knowledge work requires a completely different organizational form. Not a variation on hierarchy. A different category.

The Viable Alternative: Communities of Practice at Scale

Communities of Practice are not small informal groups. They can scale.

Wenger documented how organizations can be designed around CoPs rather than functions. A hospital can organize around clinical communities (different disease specialties) rather than departments (surgery, medicine, emergency). The community structure naturally maintains coherence because all members—surgeons, nurses, residents, researchers, administrators—are part of the same community focused on the same practice.

The advantage is immediate: a surgical innovation moves through the community in days (all members speak the same language, share the same context, see the same results). In a functionally-organized hospital, the same innovation takes months (it has to jump from surgery to administration to finance to compliance, each time translated into different language, context is lost).

Open source software communities demonstrate this at massive scale. Apache, Linux, Mozilla—these are organizations of thousands of people with no hierarchical authority, no formal managers, no headquarters. Yet they produce sophisticated software. How? Because they are built as collections of nested Communities of Practice, each focused on a specific technical domain. The organization emerges from the practice, not imposed on it.

DAOs (Decentralized Autonomous Organizations) are attempting to formalize this at scale: communities with no central authority, organized around shared values and practices, coordinating through contribution recognition and reputation rather than hierarchy.

These are not fringe experiments. They demonstrate that knowledge work can be organized without formal hierarchy, without functional separation, without the structures that break COLLIN cycles and KAYS coherence.

The question is not whether CoPs can work. The question is why we continue to use formal hierarchy when we have examples of alternatives that work better.

Part 5: Support Infrastructure for Communities of Practice

What Current Systems Miss

Enterprise software—ERP, CRM, project management, business intelligence—is built on the assumption of formal hierarchy. It assumes someone has authority to break down work, assign tasks, measure completion, enforce standards.

This architecture is fundamentally misaligned with Communities of Practice.

A CoP doesn’t need a task management system that assumes a manager assigning work. It needs a practice support system that makes the shared knowledge and practice visible, that helps new members participate in the community, that captures and preserves learning.

Current systems fail at this because they are built to optimize formal processes, not to support practice.

What Coherence Infrastructure for CoPs Would Do

A support system built for CoPs rather than hierarchies would:

1. Make Practice Visible Not as tasks (formal structure) but as actual activity. What is the community actually doing? What patterns are they creating? What is the rhythm of the practice?

This requires capturing not task completion but knowledge in action. How does an expert solve a problem? What sequence of observations and decisions leads to insight? This is what CoPs naturally preserve (through apprenticeship, through shared practice), but it evaporates when the expert leaves.

Infrastructure that captures this—the actual patterns of reasoning and action in authentic practice—preserves the knowledge that formal documentation cannot.

2. Support Legitimate Peripheral Participation Lave and Wenger’s term for how learning happens in CoPs: novices start at the periphery, gradually moving toward full participation as they develop competence and identity in the community.[11]

This is radically different from formal training. Formal training says “Here are the rules and procedures.” CoP learning says “Come participate. You’ll learn by doing, gradually. Your role will expand as you develop competence.”

Infrastructure that supports this would show newcomers how to participate, would match them with mentors, would make it easy to increase their role as they develop capability. Not by formal advancement (promotion), but by natural evolution of participation.

3. Maintain Oscillatory Coherence COLLIN cycles happen at the rhythm of practice. Some practices have fast cycles (daily), some have slow cycles (multi-month projects). The system should recognize these rhythms and protect them.

This means detecting when someone is being pulled out of rhythm (forced to sprint when the practice requires integration) and surfacing that. Not to judge them, but to make visible where coherence is breaking down.

4. Preserve Learning Across Participation Changes In formal organizations, knowledge walks out the door when someone leaves. In CoPs, knowledge is preserved in the community itself—in stories, in procedures, in the collective understanding.

But as communities grow and change, this knowledge can evaporate. Infrastructure that explicitly captures what the community is learning—not as codified procedures (which are dead knowledge), but as narrative and pattern—preserves what makes the community viable.

5. Enable Communities to Remain Nested and Autonomous CoPs need to scale, but not through hierarchy. Rather through nesting: a large practice (say, software engineering) contains communities around sub-practices (distributed systems, frontend engineering, database optimization).

Each community should be autonomous—it makes its own decisions about practice, standards, membership. But information needs to flow between them. Someone working on distributed systems may discover something relevant to database optimization.

Support infrastructure that enables this flow—without either dictating from above or creating pure chaos—is what enables CoPs to scale.

Part 6: Market and Social Implications

The Market Opportunity

Current organizational software is built for formal hierarchy. It’s a mature market with entrenched players (Salesforce, SAP, Oracle) optimizing incremental improvements to the same basic model.

Support infrastructure built for Communities of Practice would be fundamentally different. It would not try to enforce hierarchy or control through formal authority. It would:

  • Make practice and learning visible
  • Support natural participation and growth
  • Preserve knowledge
  • Enable coherence across scales
  • Foster emergent coordination rather than impose formal structure

This is not a “better project management tool.” It’s a different category.

The early adopters would be:

  • Open source communities (currently underserved by enterprise software, using ad-hoc solutions)
  • Research communities (universities, labs, institutes)
  • Creative communities (design, film, music, architecture)
  • Professional communities (medicine, law, engineering)
  • Any organization attempting to do genuine knowledge work

As these communities demonstrate the viability of CoP-based organization, the competitive pressure on formal hierarchy increases. Organizations will either transform toward CoP structures or lose talent to organizations that have.

The Social Transformation

If formal hierarchy is not viable for knowledge work, then the implication is radical: the organization itself—as currently understood—is anachronistic for 21st century work.

This does not mean work disappears. It means the form changes from hierarchy to networks of practice.

Instead of:

  • Employees in formal roles → Communities of practitioners
  • Managers directing work → Facilitators enabling practice
  • Career progression through hierarchy → Deepening expertise and recognition within communities
  • Knowledge archived in systems → Knowledge preserved in practice and community

This is not a utopian vision. It’s what already happens in open source, in startup ecosystems, in professional guilds, in research communities. These exist and thrive without formal organization.

The opportunity is to make this viability explicit, to build infrastructure that supports it at scale, and to demonstrate that knowledge work is actually more productive, more coherent, more sustainable in CoP structures than in formal hierarchy.

Part 7: Coherence Infrastructure as Commons

Why This Cannot Be Proprietary

If support infrastructure for Communities of Practice is genuinely different from formal organizational software, it has a different ownership model.

Salesforce is proprietary because it enforces formal structure on behalf of companies. It is a tool of control. Companies will pay to control their employees.

Support infrastructure for CoPs, by contrast, is enabling infrastructure. It makes the community itself smarter and more capable. It would be built by and for communities, not imposed on them.

This suggests a different model: open infrastructure for communities, not proprietary software for companies.

Some possibilities:

  • Open source platforms (similar to how Apache or Linux are maintained)
  • Community-owned infrastructure (governed by the communities it serves)
  • Public goods (funded as infrastructure, similar to universities or libraries)

The first organizations to recognize this—that the market opportunity is not in capturing communities but in enabling them—will likely be the ones that dominate this space.

Implications for Policy and Society

If knowledge work is better organized as communities than as formal hierarchy, then policy implications follow:

Education becomes apprenticeship in communities of practice, not credentialing in formal institutions. Training becomes participation in authentic practice, not classroom instruction. Expertise becomes reputation and participation in communities, not degrees and certifications.

Labor becomes contribution to communities, not employment in companies. Compensation could be based on contribution recognized by the community, not on role in a hierarchy.

Ownership and governance become questions for communities, not companies. If a community creates value, who owns it? The community itself? Its participants?

These are not questions with obvious answers. But they become urgent if formal hierarchy is revealed as fundamentally inviable for knowledge work.

Conclusion: The Coherence Economy Built on Practice

We are at the early stages of recognizing that coherence is an infrastructure problem, not a management problem. For the past four decades, the assumption has been that better information, clearer goals, and more sophisticated control would produce coordination.

The evidence suggests a more radical conclusion: coherence is achievable only when organizational form is aligned with how knowledge actually develops—in Communities of Practice.

Formal hierarchy breaks COLLIN cycles. It fragments KAYS coherence. It prevents oscillatory phase-locking. These are not bugs that better management can fix. They are consequences of the form itself.

Communities of Practice maintain all three naturally, because they are built around shared practice, not imposed structure.

The next wave of organizational infrastructure will not optimize formal hierarchy. It will enable communities. It will support the oscillatory rhythm of practice. It will preserve learning in narrative and pattern. It will facilitate participation from periphery toward mastery.

The organizations that recognize this—that stop trying to optimize an obsolete form and start enabling the form that actually works—will lead the coherence economy.

The rest will face a choice: transform or lose talent to organizations that have.

References and Annotations

[1] Lohman, T. & Rozie, H. The COLLIN framework emerges from decades of consultation on how organizational learning actually occurs. The three knowledge types (Why/What/How) are not theoretical abstractions but empirical observations of what must be held together for knowledge work to be coherent. Their decoupling is the root cause of organizational dysfunction.

[2] Kolb, D. A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Englewood Cliffs, NJ: Prentice Hall. Kolb’s cycle (Concrete Experience → Reflective Observation → Abstract Conceptualization → Active Experimentation) is the most empirically validated model of how adults learn. The critical insight: the full cycle must complete. Truncating it at any point halts genuine learning.

[3] McWhinney, W. H. (1992). Paths of Change: Strategic Choices for Organizations and Society. Thousand Oaks, CA: Sage Publications. McWhinney documents that organizations do not change through a single mechanism but through simultaneous engagement of four fundamentally different meaning-making pathways. The organization that loses access to any one becomes brittle.

[4] Kolb, D. A. (1984). op. cit. Kolb’s learning styles (Converger, Diverger, Assimilator, Accommodator) show different people naturally enter the learning cycle at different points. Formal organizations often trap people in one phase, preventing the full cycle.

[5] Wenger, E. (1998). Communities of Practice: Learning, Meaning, and Identity. Cambridge: Cambridge University Press. The foundational text. Wenger defines a community of practice through three dimensions: a shared domain of interest, mutual engagement in practice, and shared repertoire (language, tools, stories, ways of doing things). CoPs are not formed through organizational mandate; they emerge around authentic practice.

[6] Lave, J., & Wenger, E. (1991). Situated Learning: Legitimate Peripheral Participation. Cambridge: Cambridge University Press. Lave’s apprenticeship studies showed that expertise develops not through instruction but through participation in authentic practice, gradually moving from the periphery (watching, helping with small tasks) toward full participation. This is how a child learns to weave, how a surgeon develops skill, how expertise actually develops.

[7] Brown, J. S., & Duguid, P. (1991). “Organizational Learning and Communities-of-Practice: Toward a Unified View of Working, Learning, and Innovation.” Organization Science, 2(1), 40-57. The crucial insight: formal organization charts show hierarchy; the actual organization is CoPs. Innovation, learning, and real problem-solving happen in CoPs, not in formal roles. The organization “on paper” is different from the organization “in fact.”

[8] Lave, J., & Wenger, E. (1991). op. cit. Studies of apprenticeship in tailoring, navigation, butchering, and other crafts show that communities with genuine diversity maintain the strongest learning. Homogeneous groups (all experts, or all at the same level) stagnate. Diversity creates the tension that sustains learning.

[9] Wiener, N. (1948). Cybernetics: Or Control and Communication in the Animal and the Machine. New York: Wiley. Wiener established that all self-regulating systems operate through feedback loops. Ashby extended this to show that systems require internal variety matching environmental variety. In terms of oscillation: systems maintain coherence through phase-locking of coupled oscillators operating at compatible frequencies.

[10] Taylor, F. W. (1911). The Principles of Scientific Management. New York: Harper & Brothers. Taylor’s approach (break work into components, optimize each, control execution) was revolutionary for routine manufacturing. It remains the implicit model for almost all organizational design. Weber, M. (1922). Economy and Society. The bureaucratic form emerges as the “most efficient” way to organize large-scale routine work. Stability, predictability, control. Exactly wrong for knowledge work.

[11] Lave, J., & Wenger, E. (1991). op. cit. “Legitimate peripheral participation” describes the natural trajectory by which newcomers become expert members. It is not advancement through a hierarchy but deepening participation in a community. The novice’s role expands as competence grows, naturally, without formal promotion. The community recognizes and enables this evolution.

COLLIN & KAYS- Bridging Knowledge Structuring and Coherence DetectionDownload

Summary

Modern organizations do not fail because they lack data, tools, or intelligence. They fail because they lack coherence.

Most management systems assume that work progresses in a linear way: tasks are defined, executed, completed, and reported. In reality, especially in knowledge-intensive environments, work unfolds in cycles. People observe context, act, learn from the results, integrate that learning, and then re-enter a changed context. This process repeats continuously. When organizations try to force cyclical work into linear systems, misalignment becomes inevitable.

This gap between how work actually happens and how it is managed is the root cause of many familiar problems: burnout, slow learning, poor coordination, and the loss of critical organizational knowledge when people leave.

The article introduces two complementary frameworks that together explain how coherence can be restored.

The first is COLLIN, which describes the natural cycle of knowledge work. Work does not move forward in straight lines but in repeating loops of observation, execution, reflection, and integration. Importantly, different types of work operate at different rhythms. Research, operations, strategy, and innovation each have their own pace. Coherence requires recognizing and respecting these rhythms rather than flattening them into a single planning cadence.

The second framework is KAYS, which explains how people think and act across multiple organizational dimensions. Some focus primarily on structure and rules, others on goals and vision, others on operational execution or contextual constraints. None of these perspectives are wrong, but when they are not made explicit, people talk past each other. KAYS provides a shared language that makes these different modes of thinking visible and comparable.

Together, COLLIN and KAYS form a model of organizational coherence. COLLIN explains how work moves over time; KAYS explains how work is interpreted and coordinated across perspectives. When both are aligned, teams can act coherently without excessive control or bureaucracy.

This is where Gripler comes in. Gripler is not another task management or reporting tool. It is a coherence infrastructure. Instead of enforcing predefined workflows, it learns from real organizational activity: decisions, interactions, and patterns of work. Over time, it identifies the natural rhythms of teams and builds “coherence templates” that capture how effective work actually happens in that specific context.

These templates make previously invisible knowledge transferable. New team members can learn not just what to do, but how and when to do it. Burnout becomes predictable because rhythm mismatches are detectable early. Teams can be formed based on compatible working cycles rather than job titles alone. Organizational learning accelerates because insights are continuously integrated instead of lost.

The article argues that traditional hierarchical structures struggle with this kind of coherence because they fragment cycles and perspectives. In contrast, Communities of Practice—groups organized around shared work rather than authority—naturally maintain cyclical learning and multidimensional alignment. They are better suited to modern knowledge work.

The broader claim is strategic. In a world where AI makes execution faster and data abundant, competitive advantage no longer comes from speed or optimization alone. It comes from the ability to act coherently over time, across people, and across contexts.

Organizations that invest in coherence will outperform those that merely optimize throughput.