What Happens When Complexity Exceeds Organizational Processing Capacity™?
- Jun 6
- 35 min read
Every Person, Team & Organization Has a Ceiling.
Why Organizations Hit Complexity Ceilings—and How Sustainable Growth Depends on Capacity, Not Effort
ABSTRACT
Organizational Processing Capacity™
Organizations do not primarily fail because people cannot handle complexity. They struggle because complexity grows faster than the system's ability to process it. |
Most organizations misread friction as a performance problem. They add more training, more oversight, more meetings, more tools — and the friction grows. Not because people are weak, but because the system is saturated.
This paper introduces Organizational Processing Capacity™ (OPC™): a framework that redefines how leaders understand growth, friction, burnout, and organizational design. At its center is the Complexity Ceiling™ — the point at which the complexity a system carries exceeds its capacity to process it sustainably.
Every person, team, and organization operates within a finite capacity to process information, coordinate activity, make decisions, and adapt to change. When the demands placed upon a system exceed that capacity, performance begins to deteriorate. This threshold can be understood as the Complexity Ceiling™.
The Complexity Ceiling™ represents the point at which additional complexity creates diminishing returns and eventually triggers systemic breakdown.
Understanding this principle can fundamentally change how leaders approach growth, innovation, and organizational design.
What Is a Complexity Ceiling?
A complexity ceiling is the maximum amount of complexity a system can effectively manage at a given point in time.
Complexity does not only refer to workload. It includes:
Number of projects
Number of meetings
Number of tools and platforms
Decision-making demands
Reporting requirements
Communication pathways
Stakeholder involvement
Organizational change initiatives
Interdependencies between teams
Each additional layer consumes cognitive, emotional, and operational resources.
Initially, organizations often absorb these additions without obvious consequences. Performance remains stable. Employees compensate. Managers work longer hours. Teams stretch their capacity.
Eventually, however, a tipping point emerges.
One additional project.
One additional meeting.
One additional system.
Suddenly, the system begins to struggle.
Mistakes increase.
Recovery time lengthens.
Important details are missed.
Decision quality declines.
Execution slows.
What appears to be a people problem is often a complexity problem.
How the Complexity Ceiling™ Differs
Although inspired by Meadows, Senge, and Goldratt, the Complexity Ceiling™ introduces several distinctions.
It Is Capacity-Centered
Traditional systems models focus primarily on structures.
The Complexity Ceiling™ focuses on the relationship between:
Complexity
and
Processing Capacity
Complexity only becomes problematic when it exceeds available capacity.
It Works Across Multiple Levels
Most models focus on organizations.
The Complexity Ceiling™ applies equally to:
individuals
leaders
teams
departments
organizations
The same pattern appears repeatedly:
Growth → Complexity → Friction → Ceiling → Redesign → New Capacity
It Integrates Neurocognitive Variability
This is where the model becomes particularly relevant for neuroinclusive leadership.
Traditional organizational models often assume a relatively uniform ability to process complexity.
Reality is considerably more nuanced.
People differ in:
sensory processing
executive functioning
social energy
working memory
temporal regulation
recovery requirements
uncertainty tolerance
The same environment may feel manageable for one person and overwhelming for another.
The Complexity Ceiling™ therefore incorporates neurocognitive variability as a design consideration rather than treating it as an individual deficit.
The question shifts from:
"Why can't this person keep up?"
to:
"Has the complexity of the environment exceeded the processing capacity available to this individual, team, or system?"
This reframing often reveals opportunities for better design rather than increased pressure.
Why Growth Changes the System
One of the most common misconceptions in leadership is the assumption that growth is linear.
In reality, growth changes the nature of the system itself.
A team of five people does not simply become a larger version of itself when it grows to twenty.
Communication pathways multiply.
Coordination requirements increase.
Decision-making becomes more complex.
Information must travel through additional channels.
The system becomes qualitatively different.
This principle is well established within systems thinking and organizational theory. As organizations scale, coordination costs often increase faster than productive output.
Growth therefore creates two simultaneous realities:
Increased opportunity.
Increased complexity.
Organizations frequently focus on the first while underestimating the second.
Signs You Have Reached the Ceiling
Complexity ceilings rarely announce themselves directly.
Instead, they appear through secondary symptoms.
Common indicators include:
Quality Degradation
Work that was previously straightforward suddenly contains more errors, omissions, and rework.
Meeting Proliferation
More communication is required to coordinate the growing complexity, creating even less time for execution.
Decision Fatigue
Leaders and teams become slower, more hesitant, and increasingly reactive.
Burnout and Exhaustion
Employees spend more energy coordinating work than completing it.
Reduced Innovation
Cognitive resources become consumed by maintenance and administration rather than creativity and problem-solving.
Longer Recovery Times
Periods of intense activity require increasingly long recovery periods before performance returns to baseline.
When several of these signs appear simultaneously, the organization may be operating near or beyond its current complexity ceiling.
The Trap of Addition
When performance declines, leaders often respond by adding something.
Another process.
Another dashboard.
Another policy.
Another meeting.
Another software platform.
Another layer of approval.
Each intervention is usually well-intentioned.
Yet every addition consumes capacity.
This creates a paradox:
The very solutions intended to improve performance may increase the complexity causing the problem.
As organizations mature, the ability to remove complexity often becomes more valuable than the ability to add it.
The Principle of Subtraction Before Addition
One of the most effective questions a leader can ask is:
"What must be removed before something new is added?"
Before implementing a new initiative, consider:
Which process can be simplified?
Which meeting can be eliminated?
Which tool can be retired?
Which reporting requirement can be reduced?
Which approval layer can be removed?
This approach shifts leadership from accumulation to intentional design.
Rather than endlessly expanding systems, leaders actively manage organizational complexity.
The result is greater sustainability, clarity, and execution quality.
Complexity Ceilings and Neuroinclusive Leadership
The Complexity Ceiling™ becomes particularly relevant in neuroinclusive workplaces.
People vary significantly in how they process information, manage competing demands, recover from cognitive effort, and navigate ambiguity.
Some individuals thrive in highly dynamic environments.
Others perform best when complexity is structured, predictable, and transparent.
Neither approach is inherently superior.
They represent different cognitive operating styles.
When organizational complexity increases unchecked, these differences often become more visible.
Employees may appear less productive, less engaged, or less resilient when the real challenge is that the environment has exceeded their processing capacity.
Neuroinclusive leadership therefore involves designing systems that reduce unnecessary complexity while preserving meaningful challenge and autonomy.
The objective is not simplification for its own sake.
The objective is sustainable performance.
Lowering the Ceiling During High-Stress Periods
An important characteristic of complexity ceilings is that they are dynamic.
Capacity fluctuates.
A team navigating organizational restructuring, rapid growth, staff turnover, economic uncertainty, or personal stress may temporarily operate with a lower complexity ceiling.
During these periods, successful leaders intentionally reduce demands.
They pause nonessential projects.
They simplify priorities.
They clarify decision ownership.
They remove unnecessary work.
Rather than pushing harder, they create the conditions for stability.
This allows the system to regain capacity before new complexity is introduced.
Complexity Ceilings as Catalysts for Breakthroughs
Reaching a complexity ceiling is often interpreted as failure.
In reality, it may be one of the most valuable signals a system can produce.
Many organizational breakthroughs emerge precisely because existing structures can no longer absorb additional complexity. The ceiling forces a choice: continue compensating through greater effort, or redesign the system itself.
Historically, many innovations emerged from such constraints. Organizations introduced new operating models because old ones no longer scaled. Leaders delegated authority because centralized decision-making became a bottleneck. Teams adopted new communication structures because information flow had become unmanageable.
The ceiling therefore represents more than a limit.
It represents feedback.
A signal that the current design has reached the end of its useful range.
From a systems perspective, complexity ceilings frequently precede transformation. They reveal hidden constraints, expose inefficient assumptions, and create the conditions for redesign.
The breakthrough rarely comes from pushing harder against the ceiling.
It emerges from changing the structure beneath it.
The question is therefore not:
"How do we force more through the system?"
The more useful question becomes:
"What must change for the system to operate differently?"
In this sense, the complexity ceiling is less a barrier than a doorway.
OPC™ integrates insights from Organizational Information Processing Theory (Galbraith, 1974), Cognitive Load Theory (Sweller, 1988), the Job Demands–Resources Model (Bakker & Demerouti, 2007), Systems Thinking (Meadows, 2008), Learning Organizations (Senge, 1990), Theory of Constraints (Goldratt, 1984), Dunbar's research on social complexity (1992), Ashby's Law of Requisite Variety (1956), and neuroinclusive design principles — into one unified, actionable model.
The result is a framework that works at three levels simultaneously: individual, team, and organization. It is applicable to scaling startups, corporate restructuring, merger integration, burnout prevention, and the specific challenges of neuroinclusive workplaces. It provides both a diagnostic lens and a practical protocol.
What makes OPC™ distinct is not that any one of its sources is new. What is new is the integration — and the reframe it enables:
Friction is not failure. Friction is feedback. The Complexity Ceiling™ is not a problem. It is often the invitation to the breakthrough the system needed. |
OPC™ matters when an organization is scaling — and things that used to work suddenly don't. Not because the people got worse. Because the system became qualitatively different, and nobody designed for the complexity that growth created. Every new hire, every new project, every new tool multiplies coordination costs faster than intuition suggests. OPC™ makes that visible before it becomes a crisis.
OPC™ matters during mergers and acquisitions — two organizations, both near their Complexity Ceiling, suddenly face the combined load of two systems plus the overhead of integration itself. The OPC™ demand is multiplicative. Most integration timelines are built on efficiency assumptions, not capacity reality. OPC™ provides the framework for sequencing complexity in a way that doesn't collapse the people doing the work.
OPC™ matters when retention starts slipping — organizations often assume turnover is primarily a compensation, culture, or engagement problem.
Sometimes it is. But often, retention declines when complexity silently exceeds the organization's processing capacity. People become exhausted by excessive coordination, unclear priorities, fragmented systems, constant context switching, and decision bottlenecks. The work itself may still be meaningful. The experience of doing the work becomes unsustainable. OPC™ helps distinguish between employees leaving the mission and employees leaving the friction.
Because people rarely leave solely because the work is hard. They leave when the complexity of getting the work done becomes overwhelming.
OPC™ matters when burnout won't go away — when coaching, wellness programs, and time off don't produce lasting change. That's usually not an individual resilience problem. It's a coordination complexity problem. The exhaustion isn't coming from workload volume. It's coming from overhead: unclear decision ownership, meeting proliferation, tool fragmentation, the constant friction of poorly designed processes. OPC™ locates the actual source.
OPC™ matters when quality declines despite capable people — when errors increase in work that used to be clean, when reliable performers start dropping things. That is the clearest Complexity Ceiling signal available. The system is saturated. The people are fine. The architecture is the problem.
OPC™ matters when transformation projects stall — change saturation is real and extensively documented. Too many simultaneous initiatives overwhelm OPC™ regardless of how well each one is designed individually. OPC™ gives change management a capacity logic: not just what to change, but when the system can actually absorb it.
OPC™ matters when neurodivergent employees are disproportionately struggling — when the same environment works for some people and breaks down for others, that's almost never about attitude or effort. It's about different baseline processing costs meeting the same environmental complexity load. OPC™ gives organizations a non-pathologizing language for that dynamic — and a design solution rather than an accommodation workaround.
OPC™ matters as a standing leadership instrument — for any leader facing the recurring decision: new project, new initiative, new priority. The right question before every addition is not simply "is this a good idea?" It's "do we have the processing capacity for this right now — or are we already at the ceiling?"
OPC™ matters when innovation slows despite investment — organizations often respond to slowing innovation by adding more initiatives, more brainstorming sessions, more tools, or more cross-functional collaboration.
Yet innovation depends on available processing capacity. When OPC™ is consumed by coordination overhead, reporting demands, excessive meetings, and change fatigue, there is little capacity left for exploration, experimentation, and creative problem-solving. Innovation rarely dies from a lack of ideas.
It dies when complexity consumes the capacity required to develop them.
OPC™ matters when leaders become the bottleneck — many organizations eventually discover that growth has outpaced leadership bandwidth.Decisions accumulate. Approvals queue up. Teams wait. Executives become increasingly overloaded. What appears to be a leadership problem is often an OPC™ problem.
The organization has centralized more complexity than its leadership system can process. OPC™ helps identify when decision architecture—not leadership quality—is limiting performance.
The bottom line is this.
OPC™ is relevant whenever an organization has friction it cannot explain — and the default responses (more training, more accountability, more process) are making it worse instead of better.
That covers more organizations than most leaders want to admit.
Expected Outcomes — after applying the OPC™ Assessment:
From blame to design. Stop misreading system saturation as individual underperformance. Leaders and teams get a shared, evidence-based language for what is actually happening — and where to intervene.
Burnout located, not just labeled. Identify exactly where extraneous OPC™ load is generated — meeting overhead, tool proliferation, change saturation, coordination friction — and address the source instead of the symptom.
Transformation unstuck. Know which initiatives are competing for the same limited OPC™. Sequence change deliberately. Stop launching what the system cannot yet absorb.
Neurodivergent talent retained. Make visible the gap between individual processing capacity and organizational complexity load. Replace accommodation conversations with design conversations — and keep the people you cannot afford to lose.
Scaling without breaking. Give executives a concrete diagnostic before the next growth threshold. Anticipate the complexity the system cannot yet hold — before it shows up as errors, delays, and exhausted teams.
Innovation restored. Cognitive capacity freed from coordination overhead goes somewhere. When the system stops consuming people with unnecessary complexity, creativity and problem-solving return — not as a culture initiative, but as a structural consequence.
High-performing teams, by design. High performance is not a function of pressure. It is a function of sustainable capacity. OPC™ creates the conditions — clarity, recovery, reduced friction — in which teams actually deliver at their best.
Psychological safety that holds. When people see that the environment is being designed around their actual cognitive needs — not just their output — they feel seen. That is the foundation of belonging. Belonging drives engagement. Engagement drives retention.
Retention as a result, not a program. Organizations that manage OPC™ intentionally do not need to convince people to stay. They build the conditions in which people want to.
01
The Great Organizational Misdiagnosis
Why we keep looking at people when we should be looking at systems
There is a moment most leaders recognize, usually in hindsight.
Things were working. The team was sharp. The output was solid. Then something shifted — not dramatically, not all at once — but a kind of slowness entered the room. Decisions took longer. Emails multiplied. Someone missed a critical detail. The same meeting happened twice under different names. Burnout showed up in people you never expected to lose.
The instinct, almost universal, is to look at the people.
Who dropped the ball? Who needs coaching? Who isn't pulling their weight?
The interventions follow predictably: more accountability structures, more check-ins, more training, more process to ensure quality doesn't slip again. And here is what happens next: the friction doesn't go away. It gets bigger. Because you just added more.
This is the misdiagnosis that quietly guts organizations. And it happens not because leaders are incompetent — but because the default framework for understanding organizational problems is built around individuals, not systems.
The Default Framework — and Why It Fails
Most organizational theory developed in an era when work was relatively linear. A person had a role. The role had clear inputs and outputs. If output was poor, you looked at the person. This framework made sense for factory floors and bureaucratic hierarchies.
It does not make sense for modern organizations.
Modern work is characterized by interdependence, ambiguity, rapid change, information overload, constant context-switching, and increasing demands on coordination and communication. In this environment, performance is rarely a function of individual capability alone. It is a function of the relationship between complexity and capacity.
When that relationship falls out of balance, the entire system degrades — not just the weakest link.
What the Research Has Long Established
Jay Galbraith wrote in 1974 that organizations exist primarily to process information. When information-processing requirements exceed an organization's capacity, coordination problems emerge, quality declines, and performance deteriorates. That insight is fifty years old. It is still not operationalized in most leadership practice.
Herbert Simon's Nobel Prize-winning work on bounded rationality established that decision-makers don't fail because they lack intelligence. They fail because they face more information and complexity than any human cognitive system can optimally process. The constraint is architectural, not personal.
John Sweller's Cognitive Load Theory demonstrated at the individual level what Galbraith had shown at the organizational level: when processing demands exceed available capacity, performance degrades systematically. Working memory has limits. When those limits are exceeded, even expert performers make errors.
These three bodies of work, from organizational science, economics, and cognitive psychology, all point to the same underlying reality:
Finite processing capacity is not a personal failing. It is a structural feature of all information-processing systems — human or organizational. |
OPC™ builds on this foundation and extends it into a practical framework leaders can actually use.
02
Organizational Processing Capacity™ (OPC™)
Defining the framework and its three levels
Organizational Processing Capacity™ (OPC™) refers to the total ability of an individual, team, or organization to effectively absorb, coordinate, process, communicate, adapt to, and recover from complexity within a given operational context.
The key word is total. OPC™ is not just about cognitive bandwidth. It encompasses every dimension of organizational functioning that consumes capacity — and every dimension that replenishes it.
Three Levels of OPC™
OPC™ operates simultaneously across three levels. Each level has its own processing demands, its own capacity constraints, and its own failure signatures when those constraints are exceeded.
INDIVIDUAL OPC™ Cognitive bandwidth Attention regulation Decision-making capacity Sensory processing load Executive functioning Working memory capacity Recovery capacity Emotional regulation bandwidth Tolerance for ambiguity Temporal regulation | TEAM OPC™ Communication efficiency Coordination overhead Psychological safety Trust infrastructure Shared mental models Decision velocity Collective sensemaking Social processing load Meeting overhead Conflict processing costs | ORGANIZATIONAL OPC™ Process architecture clarity Information flow design Leadership bandwidth Change absorption capacity Decision system architecture Structural clarity Resource allocation efficiency Tool and platform coherence Reporting load Stakeholder coordination costs |
Complexity Is Not the Enemy
This is a critical nuance. OPC™ is not an argument against complexity. Complexity is inherent in meaningful work. Growing organizations are complex. Important decisions are complex. Serving diverse clients and markets is complex.
Complexity becomes a problem only when it grows faster than the available capacity to process it.
A high-OPC™ organization can absorb significant complexity and still function at high performance. The same complexity load applied to a low-OPC™ organization — or to the same organization during a period of reduced capacity — produces friction, errors, and breakdown.
The strategic question is never simply: how do we reduce complexity? It is always: what is the relationship between our current complexity load and our current processing capacity?
OPC™ is the ratio that matters. Not complexity alone. Not capacity alone. The relationship between them. |
What Consumes OPC™
OPC™ is consumed by demands on the system. Understanding what consumes it is the first step toward managing it intentionally.
OPC™ CONSUMERS — ORGANIZATIONAL • Active projects and initiatives • Meeting volume and duration • Number of tools and platforms • Reporting requirements • Approval and escalation layers • Communication channel proliferation • Stakeholder coordination demands • Change initiatives in flight • Organizational ambiguity and uncertainty • Misaligned roles and ownership | OPC™ CONSUMERS — HUMAN • Cognitive load from task complexity • Sensory processing demands • Social and relational energy expenditure • Emotional regulation under pressure • Context-switching between tasks • Processing ambiguous or contradictory information • Suppressing natural working styles (masking) • Recovery deficits from sustained effort • Decision fatigue from accumulated choices • Uncertainty and unpredictability exposure |
What Replenishes OPC™
Capacity is not fixed. It fluctuates based on what replenishes the system. Leaders who understand OPC™ actively manage both sides of the equation — not just the complexity inputs, but the capacity restoration mechanisms.
OPC™ REPLENISHERS — ORGANIZATIONAL • Clear decision ownership and authority • Simplified process architecture • Consolidated tools and platforms • Protected deep work time • Reduced meeting overhead • Structural clarity about priorities • Elimination of low-value reporting • Trust and psychological safety • Predictable rhythms and routines • Strategic pauses between initiatives | OPC™ REPLENISHERS — HUMAN • Genuine recovery and rest • Autonomy and self-directed work • Interest-aligned tasks • Sensory and environmental comfort • Predictability and reduced ambiguity • Co-regulation and relational safety • Meaningful contribution and progress • Clear expectations and feedback • Reduced masking demands • Physical movement and somatic reset |
03
The Complexity Ceiling™
What happens when complexity exceeds OPC™
The Complexity Ceiling™ is the point at which the complexity a system is carrying exceeds its Organizational Processing Capacity.
It is not a crisis. It doesn't arrive with a memo. It arrives sideways.
Decisions that used to take an hour now take a week. Work that used to be clean now contains errors that nobody can quite explain. The team seems capable — because they are — but something keeps slipping. Innovation has quietly left the building. People are tired in a way that sleep doesn't fix.
These are not performance symptoms. They are capacity symptoms. The system is saturated.
The Signature of a Complexity Ceiling
Most Complexity Ceiling events share a recognizable signature. The challenge is that individual symptoms are easily misattributed. When you see all of them simultaneously, you are at the ceiling.
COMPLEXITY CEILING™ — DIAGNOSTIC SIGNALS ↑ Errors increasing in work that was previously clean ↓ Decision quality declining despite capable decision-makers ↑ Time required for decisions increasing disproportionately ↑ Meeting volume increasing as coordination costs rise ↓ Innovation and creative output declining or disappearing ↑ Recovery time after intense periods growing longer ↑ Conflict and communication breakdowns increasing ↓ Employee engagement declining despite no obvious cause ↑ Burnout appearing in high performers and reliable people ↓ Execution quality declining despite sustained effort |
Why the Ceiling Is Dynamic
One of the most important properties of the Complexity Ceiling is that it moves. It is not a fixed characteristic of a person, team, or organization.
It is context-dependent and fluctuates based on:
Available resources and staffing levels
Leadership bandwidth and stability
Ambient uncertainty and change in the environment
Recovery opportunities and rest quality
Team morale and psychological safety levels
External stressors and personal circumstances of team members
Neurocognitive variability within the team
A team navigating a merger, a restructuring, rapid growth, or significant external pressure has a lower Complexity Ceiling than the same team in stable conditions. This is not weakness. It is how systems work. Effective leaders treat it as design information, not as a performance judgment.
During high-stress periods, the Complexity Ceiling drops. The right response is not to push harder. It is to temporarily reduce complexity demands — and buy the system the space to regain capacity. |
The Ceiling Is Not the Problem
Most leaders experience the Complexity Ceiling as a barrier. The framework reframes it as feedback.
Complexity Ceilings frequently emerge immediately before significant transformation. When the existing structure can no longer absorb additional complexity, organizations are forced to redesign. They simplify. They automate. They clarify. They delegate. They eliminate what isn't serving the mission.
The breakthrough rarely emerges from pushing harder. It emerges from changing the structure beneath the ceiling. The ceiling is often not the problem. It is the invitation.
The Complexity Ceiling™ is inspired by systems thinking, organizational design, and capacity management principles, while providing a practical framework for identifying when complexity exceeds the processing capacity of individuals, teams, or organizations.
04
The Scientific Foundations of OPC™
How six bodies of research converge on one framework
OPC™ is an integrative model. It does not claim to have invented any of its component insights. What it does is connect them — and in connecting them, reveal a unified picture that none of the individual traditions made fully visible.
Here is how the foundational bodies of work relate to OPC™ — and where each tradition ends and OPC™ extends.
Organizational Information Processing Theory — Galbraith (1974)
Jay Galbraith's foundational insight is arguably the most important single source for OPC™: organizations exist primarily to process information. Their entire architecture — their structures, roles, hierarchies, communication systems — is in service of processing the information required to coordinate activity and make decisions.
Galbraith argued that as uncertainty and complexity increase, organizations require greater information-processing capacity. When requirements exceed capacity, coordination problems emerge. The organization's response options are limited: either reduce the need for information processing (clarify, standardize, simplify) or increase the capacity to process it (invest in systems, people, structures).
OPC™ extends this by recognizing that modern organizations process far more than information. They process emotion, social complexity, sensory demands, change, uncertainty, and interdependence. The Galbraithian model is the skeleton of OPC™. OPC™ adds the flesh.
Galbraith: Organizations are information-processing systems. OPC™: Organizations are information-processing systems with finite, variable, and designable processing capacity. |
Cognitive Load Theory — Sweller (1988)
John Sweller demonstrated at the individual cognitive level what OPC™ proposes at the organizational level. Working memory is finite. When the demands placed on it exceed its capacity, performance deteriorates — not because the person becomes less intelligent, but because the architecture has reached its limit.
Sweller identified three types of cognitive load: intrinsic (the inherent complexity of the task), extraneous (unnecessary complexity introduced by poor design), and germane (cognitive effort that builds capability). Poor design creates extraneous load that consumes capacity without adding value.
OPC™ applies this directly to organizational design. Unnecessary meetings, redundant reporting requirements, unclear ownership, proliferating tools, and ambiguous priorities are organizational extraneous load. They consume OPC™ without producing output. Reducing them is not simplification for its own sake — it is precision design.
Job Demands–Resources Model — Bakker & Demerouti (2007)
The JD-R Model established that burnout emerges when job demands chronically exceed available resources. The model has been extensively validated across industries and cultures. When demands are high and resources are low, engagement declines, health deteriorates, and performance collapses.
OPC™ extends this logic from individuals to teams and organizations. Complexity is the organizational demand. Processing capacity is the organizational resource.
When complexity chronically exceeds OPC™, the result is organizational burnout — which manifests as the exact constellation of symptoms the Complexity Ceiling produces: errors, slowness, exhaustion, disengagement.
The JD-R research also established something critical for OPC™ practice: resources don't just protect against burnout — they actively buffer its effects even when demands are high. This is why OPC™ focuses as much on replenishing capacity as on reducing complexity.
Systems Thinking — Meadows (2008)
Donella Meadows demonstrated that organizational problems are rarely caused by bad people. They are caused by system structures that produce predictable outcomes regardless of the people within them. Friction is information. When the same problems recur despite different people, different interventions, and different attempts at improvement — the system is telling you something about its own design.
Meadows's concept of feedback loops is central to OPC™. When complexity exceeds OPC™ and leaders respond by adding more process, more oversight, more meetings — they increase complexity without increasing capacity. This is a reinforcing feedback loop that drives the system further above the Complexity Ceiling. The appropriate leverage points — in Meadows's framework — are the structural interventions that actually change the underlying relationship: subtraction, redesign, simplification.
Learning Organizations — Senge (1990)
Peter Senge's most enduring contribution to OPC™ is his observation that today's problems are frequently caused by yesterday's solutions. Organizations respond to coordination problems by adding meetings. They respond to quality problems by adding approval layers. They respond to communication breakdown by adding reporting requirements. Each intervention may solve a local problem. Collectively, they accumulate into organizational debt.
This is how organizations reach the Complexity Ceiling without realizing they are approaching it. Each addition seemed reasonable. Nobody saw the aggregate. OPC™ makes the aggregate visible and provides the framework for managing it proactively rather than reacting to its consequences.
Theory of Constraints — Goldratt (1984)
Eliyahu Goldratt established that every system has a constraint — a limiting factor that determines the throughput of the entire system. Most improvement efforts fail because organizations try to optimize everything simultaneously rather than identifying and addressing the actual constraint.
OPC™ draws on this principle but extends it in an important direction. Modern complex organizations rarely have a single constraint. They experience multiple interacting constraints: decision bottlenecks, communication bottlenecks, recovery bottlenecks, leadership bandwidth constraints, coordination overhead. The Complexity Ceiling is not a single bottleneck — it is the cumulative effect of multiple constraints overwhelming available OPC™.
This is why conventional productivity approaches often fail at scale: they optimize individual components while the interaction between components continues to generate friction. OPC™ addresses the system-level constraint.
Dunbar's Research on Social Complexity — Dunbar (1992)
Robin Dunbar's research demonstrated that humans have cognitive limits on the number of stable social relationships they can maintain — not because of any individual deficiency, but because managing social relationships requires sustained cognitive investment. As organizations grow, communication pathways don't increase linearly — they multiply exponentially. A team of twenty doesn't communicate like two teams of ten. It generates a fundamentally different, and far more complex, communication network.
This is why scaling so reliably produces friction. Leaders add people expecting more output. What they get, simultaneously, is dramatically more coordination complexity. OPC™ makes this dynamic explicit and gives leaders a framework for anticipating and designing for it — rather than being surprised by the friction that growth reliably generates past certain thresholds.
Ashby's Law of Requisite Variety — Ashby (1956)
Cybernetician W. Ross Ashby proposed one of the most powerful principles in systems science: only variety can absorb variety. A system can effectively regulate complexity only when it possesses sufficient internal variety — sufficient adaptive capacity — to match the complexity of its environment.
Applied to organizations: as environmental complexity increases — more markets, more customers, more products, more uncertainty, more regulatory demands — organizational processing capacity must increase to match. When it doesn't, the organization loses its ability to regulate effectively. Decisions become reactive. Coordination breaks down. The system loses its adaptive coherence.
Ashby's Law gives OPC™ its theoretical spine. The Complexity Ceiling is precisely the point where environmental complexity has outpaced internal OPC™ — where variety can no longer absorb variety.
A system can only effectively regulate complexity if it possesses sufficient internal capacity to match that complexity.
Why the Complexity Ceiling™ Is Different
This is where your model becomes distinct.
Theory | Core Question |
Meadows | How does the system create its own outcomes? |
Senge | What patterns are we failing to see? |
Goldratt | What is the primary constraint? |
Dunbar | How much relational complexity can humans manage? |
Ashby | Does the system have enough variety to handle complexity? |
Complexity Ceiling™ | Has complexity exceeded the available processing capacity of this person, team, or organization? |
The practical advantage is that leaders do not need to understand systems dynamics, cybernetics, organizational learning, or network theory.
They simply need to ask:
Are we approaching the ceiling?
05
OPC™ and Neuroinclusive Organizations
Why cognitive diversity changes everything about capacity design
Traditional organizational models assume relatively uniform processing capacity across people. The standard assumption, embedded in most process design, meeting architecture, and performance management, is that a well-designed system works roughly the same way for everyone.
This assumption is wrong. And the consequences of that wrongness are significant.
Human Processing Capacity Is Not Uniform
People differ substantially in how they process information, regulate sensory input, manage working memory, navigate social demands, recover from effort, and tolerate ambiguity. These differences are not deficits in most cases. They are legitimate variations in cognitive architecture — variations that have persisted in human populations for good reason.
People with ADHD carry persistent executive function demands that neurotypical systems were not designed to accommodate. Autistic people may process sensory information at a higher baseline intensity — which means that a noisy open-plan office, three back-to-back meetings, and ambiguous Slack messages aren't just annoying; they are computationally expensive in ways that leave less OPC™ for everything else. Highly sensitive people (HSP) process environmental and emotional information more deeply, which is an asset in the right context and a significant capacity drain in the wrong one. Dyslexic people may expend considerably more effort on tasks that neurotypical colleagues handle automatically.
This is not weakness. This is variability. And it has direct implications for how OPC™ is experienced and distributed across a team.
When organizational complexity increases unchecked, neurocognitive variability becomes visible in ways that get systematically misread as performance problems. |
The Misread
The pattern is depressingly predictable. An organization scales. Complexity increases. The Complexity Ceiling drops for the whole team — but it drops further and faster for people whose baseline processing demands are already higher. A neurodivergent team member who was managing well at lower complexity starts struggling. The interpretation: performance problem. The intervention: more pressure, more monitoring, more accountability.
The actual problem is that the environment has exceeded their available OPC™. The same environment may be right at — but not yet above — the ceiling for neurotypical colleagues. The apparent performance gap is an architecture gap.
Neuroinclusion as Capacity Design
This reframe is at the heart of what makes OPC™ powerful for neuroinclusive organizations. The question shifts entirely.
OLD QUESTION • Why can't this person keep up? • What does this person need to do differently? • How do we accommodate this individual? • Is this a capability problem? • What training does this person need? • How do we manage this person's performance? | OPC™ QUESTION • Has the environment exceeded available OPC™? • What does the system need to change? • How do we design for the full range of cognitive variability? • Is this a design problem? • What in the system is consuming unnecessary OPC™? • How do we redesign the environment for sustainable performance? |
This is not about lowering standards. It is about understanding that the system generating friction may be producing the same friction for everyone — but with more severe consequences for people with higher baseline processing demands. Reducing unnecessary complexity benefits the whole team. It just makes the neuroinclusive team function.
What OPC™ Design Looks Like in Practice for Neuroinclusive Teams
Reduce ambient complexity before addressing individual accommodation — quiet environments, clear communication channels, predictable rhythms
Design meetings for cognitive efficiency: clear agenda, defined decision points, written summaries, asynchronous options where possible
Build structural predictability — clear ownership, clear timelines, explicit expectations — to reduce the OPC™ cost of ambiguity
Audit and reduce extraneous tool proliferation; context-switching between platforms has a disproportionate OPC™ cost for people with executive function differences
Protect recovery capacity explicitly — not as a wellness initiative but as a structural design decision
Create explicit permission to flag when OPC™ is being exceeded — without pathologizing the person raising it
Neuroinclusive design and OPC™ management are the same work. Building systems that respect the finite, variable, and context-dependent nature of human processing capacity produces organizations that are sustainable for everyone — and functional for people whose capacity is most sensitive to environmental complexity.
06
The OPC™ Cycle
Growth: New opportunities emerge.
↓
Complexity Accumulation: Projects, processes, stakeholders, and demands increase.
↓
Friction: Delays, errors, overwhelm, and inefficiencies appear.
↓
Complexity Ceiling: The system reaches its current processing limit.
↓
Simplification / Redesign: Complexity is reduced or capacity is expanded.
↓
Breakthrough: Performance improves and new opportunities emerge.
↓
New Capacity: The system can now support greater complexity.
↓
Growth
Friction is often diagnostic. The ceiling is not necessarily the problem. The ceiling is often the signal that the next version of the system is ready to emerge.
How growth, friction, and breakthrough follow a predictable pattern
One of the most valuable things OPC™ provides is not just a diagnosis — it's a map. Once you see the pattern, you can locate yourself within it, anticipate what comes next, and intervene at the right moment rather than reacting to consequences.
The OPC™ Cycle describes how virtually every scaling organization, and every individual navigating significant growth, moves through a predictable sequence.
01 · GROWTH | New opportunity emerges. A project launches, a team expands, a market opens, a product scales. Energy is high. Output increases. The system is working. |
02 · COMPLEXITY ACCUMULATES | Each addition brings coordination costs. More stakeholders means more communication pathways. More projects means more context-switching. More tools means more fragmentation. Individually, each addition seems reasonable. Collectively, they compound faster than intuition suggests. |
03 · OPC™ MISMATCH | Complexity has now grown faster than processing capacity. The system is carrying more than it can sustainably absorb. This is often invisible at first — people compensate through extra effort, longer hours, heroic individual performance. |
04 · FRICTION | The compensation stops working. Errors increase. Decisions slow. Meetings proliferate as coordination costs rise. Burnout appears. Innovation declines. The Complexity Ceiling™ is reached. |
05 · REDESIGN | The system can no longer absorb complexity without structural change. Leaders who understand OPC™ use this moment to redesign rather than push harder. They simplify, clarify, automate, delegate, and eliminate what isn't serving the mission. |
06 · BREAKTHROUGH | The redesign creates the conditions for performance that the previous structure couldn't hold. Often the breakthrough that follows a Complexity Ceiling is more significant than any gain made through effort alone — because it comes from structural improvement rather than compensation. |
07 · NEW CAPACITY | The system now has greater OPC™ than before. It can absorb more complexity sustainably. New growth becomes possible — and the cycle begins again. |
Why Most Organizations Miss the Redesign Moment
The OPC™ Cycle is predictable. But most organizations skip Step 5. They experience friction, correctly identify that more is needed — and add more complexity. More process to fix quality problems. More meetings to fix coordination. More reporting to fix visibility. This drives the system further above the Complexity Ceiling rather than below it.
The organizations that scale sustainably are the ones that learn to recognize the friction of Step 4 as the signal for Step 5 — and make the structural intervention before the system breaks.
The breakthrough rarely comes from pushing harder. It comes from changing the structure beneath the ceiling. Friction is not the enemy. Friction is the invitation. |
07
OPC™ Assessment
How to diagnose your current position and identify the right intervention
The OPC™ Assessment is designed to give leaders a clear, evidence-based picture of the relationship between their current complexity load and their current processing capacity — and to identify where the highest-leverage interventions lie.
Complete both parts before interpreting results. OPC™ is a ratio, not a single score. Complexity and capacity must always be assessed together.
Part 1: Complexity Inventory
Rate each area from 1 (very low) to 5 (very high) based on the current state of your team or organization.
COMPLEXITY DIMENSION | 1 | 2 | 3 | 4 | 5 |
Volume of active projects and initiatives | ○ | ○ | ○ | ○ | ○ |
Number and duration of regular meetings | ○ | ○ | ○ | ○ | ○ |
Number of software tools and platforms in active use | ○ | ○ | ○ | ○ | ○ |
Stakeholder coordination demands | ○ | ○ | ○ | ○ | ○ |
Reporting, documentation, and approval requirements | ○ | ○ | ○ | ○ | ○ |
Number of simultaneous change initiatives | ○ | ○ | ○ | ○ | ○ |
Communication channel proliferation | ○ | ○ | ○ | ○ | ○ |
Organizational ambiguity (unclear roles, ownership, priorities) | ○ | ○ | ○ | ○ | ○ |
Rate of new complexity being added (past 6 months) | ○ | ○ | ○ | ○ | ○ |
Coordination overhead between teams or functions | ○ | ○ | ○ | ○ | ○ |
Complexity Score: _____ / 50
Part 2: Capacity Inventory
Rate each area from 1 (very low / insufficient) to 5 (very high / strong) based on the current state.
CAPACITY DIMENSION | 1 | 2 | 3 | 4 | 5 |
Leadership bandwidth and availability | ○ | ○ | ○ | ○ | ○ |
Decision-making speed and clarity | ○ | ○ | ○ | ○ | ○ |
Team coordination efficiency | ○ | ○ | ○ | ○ | ○ |
Communication quality and clarity | ○ | ○ | ○ | ○ | ○ |
Process architecture clarity and simplicity | ○ | ○ | ○ | ○ | ○ |
Psychological safety and trust levels | ○ | ○ | ○ | ○ | ○ |
Recovery opportunities between intensive periods | ○ | ○ | ○ | ○ | ○ |
Change absorption capacity | ○ | ○ | ○ | ○ | ○ |
Clarity of priorities and decision ownership | ○ | ○ | ○ | ○ | ○ |
Ability to remove complexity (not just add) | ○ | ○ | ○ | ○ | ○ |
Capacity Score: _____ / 50
Interpreting Your OPC™ Score
POSITION | Complexity relative to Capacity | Primary Signal |
Capacity > Complexity | Score gap: Capacity higher by 10+ | Growth can be absorbed. Monitor as complexity increases. |
Complexity ≈ Capacity | Scores within 5–9 points of each other | Approaching the ceiling. Friction signals are early warnings. Simplify before adding. |
Complexity > Capacity | Complexity score higher by 10+ | At or above the ceiling. Redesign required before any new complexity is added. |
Complexity >> Capacity | Complexity score higher by 20+ | Well above ceiling. Active breakdown likely. Immediate structural intervention needed. |
Note: These thresholds are indicative, not diagnostic. Use them as orientation points, not verdicts. Context matters enormously — a team in rapid growth may score high on complexity and still be managing well if capacity is also high and recovery is built in.
08
The OPC™ Protocol- How Do You Actually Use the Complexity Ceiling™?
The model becomes most useful when applied proactively rather than reactively.
What to do — exactly — at each stage of the cycle
Assessment without action is analysis paralysis. The OPC™ Protocol provides the specific interventions for each position in the OPC™ Cycle. The protocol is built on one central principle:
Subtraction Before Addition™ — Before introducing any new complexity, remove something first. Every addition must earn its place. |
Step 1: Map What Has Been Added (identify Complexity Inputs)
Pull up the last six to twelve months. What has been introduced to the system? Not what was planned — what actually landed.
New projects and initiatives — including those that haven't formally launched but are consuming mental space
New meetings — including standing meetings that were added and never removed
New tools and platforms — including trials that became permanent defaults
New stakeholders — including external partners, new hires in cross-functional roles, and new reporting lines
New reporting requirements — both internal and external
New change initiatives — including cultural initiatives, restructuring processes, and strategy pivots
Growth often arrives with fanfare. Complexity arrives quietly, attached to the bottom of a project plan. Most leaders can identify the visible growth additions easily. The OPC™ load is usually hidden in the second category.
Step 2: Read the Friction Signals
Before deciding on any intervention, read the signal accurately. The Complexity Ceiling produces a recognizable signature — and misreading it as a performance problem leads to the wrong intervention.
COMPLEXITY CEILING SIGNAL • Errors in previously reliable work • Decision slowdown without obvious cause • Meeting proliferation as coordination rises • Burnout in high performers • Innovation declining or disappearing • Recovery time increasing after intense periods • Communication quality declining • Conflict rising without clear precipitating cause | PERFORMANCE PROBLEM SIGNAL • Errors in new or unfamiliar work only • Decision slowdown with clear skill or information gaps • Meetings productive but too infrequent • Burnout in people with known overload • Innovation declining with identifiable cause • Normal recovery time; fatigue is proportionate • Communication declining with specific people or contexts • Conflict with identifiable source and pattern |
If multiple Complexity Ceiling signals are present simultaneously — particularly across different teams, functions, or levels of the organization — the diagnosis is likely an OPC™ mismatch rather than an individual performance issue.
Step 3: Assess Current Capacity
Complexity alone tells only half the story.
The same complexity load may be manageable in one context and overwhelming in another.
Assess the system's current capacity by considering:
• Workload and competing priorities
• Staffing levels and capability distribution
• Recovery opportunities between intensive periods
• Leadership bandwidth and decision availability
• Cognitive and coordination demands
• Organizational uncertainty and change in flight
• Psychological safety and trust
• Overall change absorption capacity
The critical question is:
Can the system realistically absorb the complexity it is currently carrying?
Capacity matters just as much as complexity.
Step 4: Simplify Before Adding- Apply Subtraction Before Addition™
Before anything new is introduced — a project, a meeting, a tool, an initiative, a process improvement — identify what comes out.
The practical question is not simply 'what can we remove' (which often produces defensive responses).
The more useful framing is:
If we could only keep the things that are generating real value right now, what would we keep — and what would quietly disappear? |
Practical subtraction actions, in roughly increasing order of structural impact:
Cancel, combine, or shorten one standing meeting per week
Retire one reporting requirement that produces data no one acts on
Consolidate two tools into one wherever overlap exists
Pause one low-priority initiative for sixty days and evaluate its status at the end
Clarify ownership for three decisions that currently require escalation or group alignment
Remove one approval layer from a routine decision-making process
Establish and protect one no-meeting half-day per week for the team
Subtraction often creates more capacity than addition.
Step 5: Redesign Before Breakdown
When friction is persistent and the OPC™ assessment confirms a significant mismatch, individual subtractions are not sufficient. The system needs structural redesign.
Complexity grows by default. Capacity grows by design.
Redesign interventions, in order of scope:
REDESIGN INTERVENTION LEVELS LEVEL 1 — PROCESS ARCHITECTURE Simplify workflows. Clarify ownership. Reduce decision bottlenecks. Eliminate approval layers that add delay without adding value. Map the end-to-end process for your highest-complexity work and identify where the extraneous load is generated. LEVEL 2 — MEETING AND COMMUNICATION ARCHITECTURE Redesign the meeting ecosystem. Every standing meeting should have a clear decision it produces or a coordination need it serves. If it doesn't, it is consuming OPC™ without generating value. Establish communication protocols that reduce ambient noise. LEVEL 3 — PRIORITY ARCHITECTURE Most teams have too many active priorities. The research consistently shows that three well-executed priorities outperform six poorly-executed ones. Identify the critical three. Explicitly pause the rest. LEVEL 4 — STRUCTURAL REDESIGN At this level, the intervention addresses the organizational architecture itself: role clarity, team structure, reporting lines, decision authority. This is the deepest redesign and requires the most time — but it is also where the most durable capacity increase is achieved. |
Step 6: Lower the Ceiling Deliberately During High-Stress Periods
The Complexity Ceiling is dynamic. During high-stress periods — restructuring, rapid growth, merger integration, significant external uncertainty, team transitions — the ceiling drops. Attempting to maintain the same complexity load during these periods is not resilience. It is miscalibration.
Effective leaders deliberately reduce complexity demands during high-stress periods. They pause non-essential initiatives. They simplify priorities. They reduce reporting overhead. They protect recovery capacity explicitly.
This is not lowering the bar. It is intelligent capacity management — buying the system the space to regain OPC™ before the next cycle of growth.
Modern organizations rarely suffer from a lack of ambition.
More often, they suffer from accumulated complexity.
The Complexity Ceiling™ offers a practical framework for recognizing when growth has outpaced capacity and when redesign has become necessary.
Inspired by systems thinking, informed by organizational science, and expanded through a neuroinclusive lens, the model provides a simple yet powerful insight:
Every system has a complexity ceiling.
The goal is not to avoid reaching it.
The goal is to recognize it early enough that it becomes a catalyst for redesign rather than a precursor to burnout.
Because the most significant breakthroughs often begin at the point where the current system can no longer continue as it is.
Subtraction before addition.
09
The OPC™ Premortem
How to prevent complexity overload before it begins
One of the most effective ways to prevent complexity overload is to assess complexity before it arrives.
Before launching a major initiative, ask:
Imagine this project failed completely twelve months from now.
The OPC™ Premortem is a structured exercise for identifying complexity risks before they materialize — before the project launches, before the restructuring is announced, before the new system goes live.
Imagine it's twelve months from now. The initiative failed. Not spectacularly — quietly. Teams are exhausted, quality has declined, the original goal has been quietly de-prioritized. What happened? |
Work backwards from that failure to map the complexity accumulation that created it. The premortem format:
1. Where did complexity accumulate? | Which teams, functions, or processes became overloaded as the initiative scaled? Where did coordination costs multiply unexpectedly? |
2. Which dependencies became bottlenecks? | Which approval steps, decision points, or cross-functional handoffs slowed or broke under increased load? |
3. Which meetings multiplied? | What coordination needs emerged that weren't anticipated? Where did standing meetings get added to compensate for unclear ownership or communication breakdowns? |
4. Which teams became overloaded? | Which functions carried disproportionate complexity burden? Who was asked to absorb more than their OPC™ could sustain? |
5. What did we underestimate? | Where did our assumptions about coordination costs prove wrong? What complexity arrived quietly that we didn't anticipate from the project plan? |
6. What did we fail to remove? | What pre-existing complexity could have been cleared before the new initiative landed — but wasn't? |
The OPC™ Premortem works because it bypasses the optimism bias that makes complexity invisible at project launch. Most people can imagine failure when asked to think backward from it. The structured format ensures the analysis focuses specifically on OPC™ dynamics — not just on execution quality or strategy.
10
OPC™ in Specific Contexts
Applications across organizational scenarios
Scaling Organizations
OPC™ is most immediately applicable in scaling organizations. The pattern is predictable: 10 people works beautifully. 25 people works well. 50 people produces friction. 100 people produces meeting explosion and process proliferation. 150 people produces the demand for 'more structure' — which often means more complexity added on top of the existing complexity.
This is Dunbar's research plus OPC™ made concrete. Each growth threshold creates a qualitatively different coordination system, not just a larger version of the previous one. Leaders who understand OPC™ anticipate the complexity load each threshold creates — and proactively redesign before the friction of the Complexity Ceiling forces a reactive response.
Mergers and Acquisitions
Many mergers and acquisitions fail not because of strategic misalignment but because of OPC™ collapse during integration. Two organizations, each near their complexity ceiling, suddenly face the combined complexity of two systems plus the coordination overhead of integration itself. The OPC™ demand is multiplicative. The available capacity is frequently lower than before the merger, because both organizations are simultaneously dealing with uncertainty, leadership changes, and cultural adjustment.
OPC™ assessment before and during integration provides a framework for sequencing complexity carefully — combining what must be combined, leaving separate what can remain separate, and managing the integration timeline against actual OPC™ capacity rather than aspirational efficiency targets.
Burnout Prevention
Most burnout models focus on individual demands, individual resources, and individual resilience. OPC™ adds a dimension that is rarely assessed: coordination complexity as a burnout driver.
A significant proportion of organizational burnout is not caused by the volume of work. It is caused by the coordination overhead required to do the work. The meetings to align on a decision that could have been made by one person with clear authority. The reporting to satisfy oversight structures that produce data nobody acts on. The tool-switching between platforms that don't integrate. The ambiguity that requires constant re-checking and re-clarifying.
This is extraneous OPC™ load — the organizational equivalent of cognitive extraneous load in Sweller's model. It consumes processing capacity without producing output. Reducing it is one of the highest-leverage interventions for burnout prevention available to leaders.
Change Management and Transformation
Change saturation research (Prosci, Gartner, McKinsey) has consistently shown that organizations have limited capacity to absorb change. Too many simultaneous change initiatives produce resistance, exhaustion, and failed transformation — not because the individual changes are poorly designed, but because the aggregate OPC™ demand exceeds available capacity.
OPC™ provides the framework for sequencing change intentionally — spacing initiatives to allow each one to land and stabilize before the next is introduced. The core principle: organizational change is itself a complexity input. It consumes OPC™ even when it is ultimately in service of reducing complexity. Design accordingly.
11
Final Reflection
The question that changes organizational leadership
Organizations rarely fail because they lack ambition, talent, or effort. They struggle because complexity grows faster than the system's ability to process it — and nobody stops to ask whether the structure can hold what is being loaded onto it.
For decades, organizational thinking has defaulted to the individual as the unit of failure. Someone wasn't resilient enough. A team didn't communicate well enough. A leader didn't execute effectively enough. The interventions follow: more training, more accountability, more resilience coaching, more performance management.
OPC™ offers a different question — and a different level of intervention.
Is this a people problem — or a system design problem? |
When you have talented people producing friction-laden output in environments loaded beyond their processing capacity, the answer is almost always: design problem. The people are fine. The architecture is the issue.
Galbraith showed us in 1974 that organizations exist to process information. Sweller showed us that processing systems have capacity limits. Meadows showed us that friction is feedback from the system about its own design. Senge showed us that today's problems are yesterday's solutions accumulated without subtraction. Goldratt showed us that constraints limit the whole system. Dunbar showed us that complexity scales faster than headcount. Ashby showed us that only variety can absorb variety.
OPC™ integrates all of this — and adds the neuroinclusive dimension that most organizational models ignore: that processing capacity is not uniform across people, and that designing for cognitive diversity is not accommodation. It is precision engineering for sustainable performance.
The Core Principle
ORGANIZATIONAL PROCESSING CAPACITY™ — THE CORE PRINCIPLE Growth creates complexity. Complexity creates friction. Friction reveals the ceiling. The ceiling invites redesign. Redesign creates breakthrough. Breakthrough creates new capacity. New capacity enables sustainable growth. Subtraction Before Addition™ — every time. Sustainable growth is not determined by how much complexity an organization can accumulate. It is determined by how much it can meaningfully process. |
SELECTED REFERENCES
Ashby, W. R. (1956). An introduction to cybernetics. Chapman & Hall.
Bakker, A. B., & Demerouti, E. (2007). The Job Demands–Resources model: State of the art. Journal of Managerial Psychology, 22(3), 309–328. https://doi.org/10.1108/02683940710733115
Dunbar, R. I. M. (1992). Neocortex size as a constraint on group size in primates. Journal of Human Evolution, 22(6), 469–493. https://doi.org/10.1016/0047-2484(92)90081-J
Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28–36. https://doi.org/10.1287/inte.4.3.28
Goldratt, E. M., & Cox, J. (1984). The goal: A process of ongoing improvement. North River Press.
Kahneman, D. (2011). Thinking, fast and slow. Farrar, Straus and Giroux.
Maslach, C., & Leiter, M. P. (2016). Understanding the burnout experience: Recent research and its implications for psychiatry. World Psychiatry, 15(2), 103–111. https://doi.org/10.1002/wps.20311
Meadows, D. H. (2008). Thinking in systems: A primer. Chelsea Green Publishing.
Robuste, A. (2025). Gentle leading & neurodivergence-inclusive leadership. Routledge.
Salas, E., Cooke, N. J., & Rosen, M. A. (2008). On teams, teamwork, and team performance: Discoveries and developments. Human Factors, 50(3), 540–547. https://doi.org/10.1518/001872008X288457
Senge, P. M. (1990). The fifth discipline: The art and practice of the learning organization. Doubleday.
Simon, H. A. (1955). A behavioral model of rational choice. The Quarterly Journal of Economics, 69(1), 99–118. https://doi.org/10.2307/1884852
Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2), 257–285. https://doi.org/10.1207/s15516709cog1202_4
Weick, K. E., & Sutcliffe, K. M. (2007). Managing the unexpected: Resilient performance in an age of uncertainty (2nd ed.). Jossey-Bass.
Alexandra Robuste Leadership Academy
© Alexandra Robuste. All rights reserved. OPC™, Complexity Ceiling, Subtraction Before Addition™, and all frameworks marked ™ are proprietary to Alexandra Robuste.
Comments