philosophy Archives - Menschgeist

Most organizations I meet are not short on feedback. They have engagement surveys, NPS scores, customer complaints, ticket tags, retrospective notes and escalation emails. They lack feedback loops. These are places where signals reliably lead to small adjustments in how the system works. Here, people can actually see that connection. When feedback disappears into a void, people eventually stop offering it. They may offer it with a shrug, assuming nothing will change.

From an AO and systems‑thinking perspective, feedback loops are not an HR topic or a nice‑to‑have. They are crucial for a living organization to learn and adapt. The process involves regularly comparing intentions with actual outcomes. Then, adjustment of structure, flow, and behavior is done in small steps. In this issue, I share a story of a team. They improved their work by moving from tired rituals to a simple, tight loop. I also provide a concrete AO move you can try. This move is helpful if you sense feedback in your system is getting stuck rather than closing the loop.

From the field: from tired retros to a living loop

A cross‑functional product team told me they were “doing retros” but not really learning. Every two weeks, they spent an hour filling a digital board with sticky notes. They noted what went well, what didn’t, and ideas for improvement. At the end, they picked a couple of actions. By the time the next sprint ended, nobody remembered what those actions were, or whether anything had changed. The ritual was there; the loop was not.

When we looked closer, two patterns stood out. First, the scope of their retros was too broad. They tried to talk about everything at once: coding practices, stakeholder communication, deployment issues, team dynamics, long‑term strategy. Second, nothing outside the team room changed. Many of their frustrations were about upstream and downstream parts of the system. They dealt with unclear priorities, last‑minute requests, and release policies. However, their “actions” stayed within their own bubble.

Rather than abandoning retros, we narrowed and repurposed them. For a month, we focused the team on one specific flow for learning. This was the journey of one particular type of change, from idea to live usage. We also invited one person from customer success. Another was invited from operations. They joined for a short part of the session. This way, the loop included those who saw the impact outside the team.

We introduced a simple visual that became the backbone of their new loop. It was a board with three columns labeled “Signals”, “Experiments”, and “Effects”. Each week, rather than listing generic “went well/didn’t go well” items, they identified 2–3 specific signals about that flow. These signals could include a recurring support ticket pattern, a delay hotspot, or a positive surprise in customer behavior. For each important signal, they designed one small experiment. It could be a tweak in how they coordinated. They might also adjust how they sequenced work. Another option was tweaking how they checked quality. Alternatively, they could change how they communicated changes.

Crucially, the board stayed visible in their team space and in their digital workspace. The following week, they didn’t start from a blank slate. They returned to the same board and asked: “What did we actually do? What did we see? Do we keep this change, adjust it, or drop it?” Over time, some experiments became the new normal, others were retired, and new ones appeared.

Within a few iterations, their energy shifted. The team started noticing patterns earlier. They could see that a change in how they handled handoffs reduced a certain kind of support ticket. They also noticed that a change in release timing created new issues elsewhere. Customer success felt heard because their signals were now explicitly part of the loop, not an afterthought. One team member summed it up neatly: “We used to collect feedback about the past. Now we have a place where feedback changes what we do next.”

Try this AO move this week – design one tight loop

You don’t need to redesign all your feedback processes to start tightening your loops. You can begin by creating one simple, explicit loop around one important flow, and running it for a few weeks.

Pick one flow that really matters.
Choose a concrete slice of work where better learning would help. It could be Onboarding a certain type of customer. It might involve handling a particular class of incidents or claims. Consider delivering a type of feature or running a recurring service. Make it narrow enough that everyone can picture real examples.
Define 2–3 signals you will look at every week.
Ask: “If this flow were getting healthier or sicker, what simple signs would we see?” These signs could be things like repetition in support tickets. You might also notice a specific delay point. A satisfaction indicator may appear. There could be a handoffs that often goes wrong. Alternatively, you might hear a frontline story from customers or staff. Keep the list short and easy to see at a glance.
Install a small, regular loop into an existing meeting.
Instead of adding a new ceremony, use a meeting you already have. Reserve 15–20 minutes in that meeting. For example, use the end of a weekly team meeting, service review, or leadership huddle. Use that slot only for this flow and these signals. Every time, follow the same pattern:
- look at the signals;
- choose at most one small adjustment you will try before the next loop;
- write it down where everyone can see it.
Keep a tiny “signals → adjustments → effects” log.
On a physical board or a shared document, track three things. First, note which signal you reacted to. Next, record what adjustment you decided to make. Lastly, write down what you noticed by the next meeting. You don’t need perfect data; you need enough observation to see whether your system responds.
Review the loop itself after 3–4 cycles.
After a few weeks, step back: Is this loop giving us useful learning? Are the signals still the right ones? Are our adjustments too big or too vague? Do we need to involve someone else (e.g. another team, a function) to make the loop complete? Adjust the design of the loop as well as what you do inside it.

If you repeat this pattern across a few important flows, you’ll discover that your AO work doesn’t rely on big initiatives anymore. It starts to feel like part of how you move. Signals come in, small experiments go out, and everyone can see the connection between the two.

You want more?

If you’d like help designing feedback loops and lightweight review practices tailored to your AO work, you can book a short conversation with me.

Book a conversation

AO E-books

AO METHOD

A Systems Dynamics Perspective

Executive Summary

Linear and non-linear work approaches serve different organizational purposes. However, in VUCA (volatile, uncertain, complex, ambiguous) environments, linear methods have critical limitations. This document examines the fundamental differences between linear and non-linear work. It analyzes when each approach is appropriate. The document explores practical failure patterns of linear methods in VUCA contexts. It presents agile alternatives through the lens of Agile Systems Dynamics. Organizations operating in VUCA environments must consciously design their work systems as portfolios. They should maintain linear processes where stability exists. Additionally, they need to build non-linear, adaptive capabilities where complexity and uncertainty dominate.

Introduction

The distinction between linear and non-linear work is not merely methodological. It reflects fundamentally different assumptions about how the world behaves. It also affects how organizations should respond[1][2]. Business environments are becoming more volatile and complex. This makes the choice of work approach a strategic question rather than a tactical one.

This document synthesizes research on VUCA management, agile methodologies, systems dynamics, and organizational learning. It offers practitioners a comprehensive framework for choosing and designing appropriate work approaches. We examine both the theoretical foundations and practical implications through real-world examples and an Agile Systems Dynamics lens.

Definitions: Linear vs Non-Linear Work

Linear Work

Linear work operates on several core assumptions[3][4][5]:

Sequential phases with clear start and end points (A → B → C)
Predictable cause-and-effect relationships that remain stable during execution
Proportionality: inputs produce proportional outputs with minimal variation
Context stability: the environment changes slowly relative to execution cycles
Decomposability: complex problems can be broken into independent sub-tasks

Linear work thrives on optimization, efficiency, and variance reduction. It assumes that if you execute each step correctly according to plan, the cumulative result will match expectations.

Example: Building a standard highway bridge follows linear work patterns. Requirements are known. Engineering principles are established. Regulations are stable. The sequence of foundation → structure → surface → handover is predictable.

Non-Linear Work

Non-linear work recognizes different system characteristics[3][6][7][8]:

Progress occurs through feedback loops, iteration, and branching paths
Small changes can produce disproportionate effects (non-proportionality)
Outcomes emerge from interactions among many autonomous agents
Context co-evolves: the environment and the work influence each other continuously
Systems cannot be meaningfully decomposed without losing essential dynamics

Non-linear work optimizes for learning speed, resilience, and adaptability. It assumes that uncertainty and emergence are inherent, requiring continuous sensing and adjustment.

Example: Building a digital platform ecosystem involves understanding evolving customer behavior. Emerging technologies and shifting competitive dynamics must also be considered. This requires non-linear work. You release, observe, learn, adapt, pivot, and co-evolve with users and the market.

Where Each Approach Excels

When Linear Work is Appropriate

Linear work remains superior in specific contexts[3][4][5]:

Complicated but Stable Domains

Problems with many interdependent parts, but predictable behavior
Examples: standard ERP implementations, regulatory compliance reporting, established manufacturing processes
Expertise and best practices provide reliable guidance

Repeatable Operations

Low variance in inputs and environment
Focus on throughput optimization, cost reduction, and quality consistency
Value comes from execution excellence, not discovery

Slow-Changing Environments

Environmental change occurs more slowly than delivery cycles
Long-term infrastructure programs, routine operations, safety-critical systems
Deviation carries higher risk than delay

Benefits of Linear Work:

High resource utilization and efficiency
Accurate forecasting of time, cost, and capacity needs
Clear accountability through defined handoffs
Lower coordination overhead for routine tasks

When Non-Linear Work is Superior

Non-linear work becomes essential in different conditions[6][7][8][9]:

VUCA Environments

Volatility: rapid, unpredictable changes in key variables
Uncertainty: limited predictability of events and outcomes
Complexity: many interconnected, interacting factors
Ambiguity: unclear cause-effect relationships, multiple interpretations

Complex Adaptive Systems

Multiple autonomous agents with local goals and decision rules
Emergent patterns arise from agent interactions
Examples: markets, ecosystems, organizational cultures, innovation

High Novelty and Learning Requirements

Past solutions are weak predictors of future success
Problem definition itself evolves through exploration
New business models, transformations, breakthrough innovations

Benefits of Non-Linear Work:

Higher adaptability and resilience to unexpected change
Better fit to emergent opportunities and threats
Continuous learning and course correction
Encourages experimentation and diversity of approaches
Enables distributed decision-making closer to information sources

Comparative Overview

Aspect	Linear Work	Non-Linear Work
World assumption	Mostly stable, predictable	Volatile, emergent, interconnected
Planning style	Upfront, detailed, phase-gated	Rolling, adaptive, scenario-based
Control logic	Command-control, variance reduction	Distributed control, feedback loops
Optimization focus	Efficiency, cost, utilization	Learning speed, resilience, adaptability
Typical methods	Waterfall, stage-gate, linear KPIs	Agile/lean, experiments, probe-sense-respond
Best domain	Complicated, repeatable work	Complex, novel, strategic work
Feedback timing	Late, end-loaded	Early, frequent, structured
Scope management	Fixed upfront scope	Evolving scope via backlog

Table 1: Comparison of linear and non-linear work characteristics

Can We Use Linear Work in a VUCA World?

The answer is nuanced: yes, but within boundaries and as part of a conscious portfolio design[7][9][10][11].

The Dual Reality

Research on VUCA management emphasizes that the overall environment may be increasingly complex and volatile. However, not every organizational subsystem operates in that regime. The overall environment may be more complex and volatile, but individual subsystems may not necessarily follow that pattern[9][10][11]. Organizations that thrive in VUCA view themselves as complex adaptive systems. Some components remain highly standardized. Others are deliberately exploratory.

Appropriate Use of Linear Work in VUCA

Linear work remains valid for:

Core regulated processes: Finance closing, payroll, compliance, safety-critical operations where deviation is risky and learning cycles are long
Validated implementations: Once a new process has been validated through experiments and pilots, its broader rollout may follow a linear playbook
Infrastructure and support: Stable technology infrastructure, routine maintenance, established service delivery

When Linear Planning Becomes Dangerous

Linear approaches create risk when applied to[7][9][11][12]:

High-uncertainty strategic domains (new product strategy, digital ecosystem plays, major organizational redesign)
Contexts where problem definition itself is evolving
Initiatives spanning multiple years in rapidly changing markets
Cross-functional transformations involving cultural and power dynamics

The Ambidextrous Organization Pattern

A pragmatic organizational design is the dual-system or ambidextrous approach[1][7][9][11]:

One subsystem optimized for efficiency and execution (linear processes)
Another subsystem optimized for exploration and adaptation (non-linear processes)
Explicit interfaces, governance, and resource allocation between the two
Dynamic rebalancing based on environmental scanning

Research on strategic agility and VUCA management consistently supports this ambidexterity. Organizations maintain “structural separation with senior team integration.” This approach balances exploitation and exploration[1][9][11].

Agile Systems Dynamics Lens

Agile Systems Dynamics (ASD) explicitly models organizations as non-linear social systems. In these systems, “agile” emerges as a pattern of evolving behavior. It is not a fixed framework or methodology[13][14].

Core ASD Perspectives on Linear vs Non-Linear Work

1. Agents and Objectives vs Tasks and Phases

Traditional linear work assumes agents (teams, leaders, departments) will execute a predefined chain of tasks. ASD recognizes that:

Agents have partially aligned or conflicting objectives[13][14]
Their interactions, power relations, and local decisions alter the trajectory
Work design must account for agent autonomy and goal diversity

Non-linear work explicitly acknowledges agent dynamics. It builds coordination mechanisms that allow local adaptation within boundaries. These mechanisms avoid enforcing rigid task sequences.

2. Feedback Loops as the Real Engine

Agile practices (sprints, reviews, retrospectives, continuous discovery) are mechanisms to generate and process feedback faster than the environment changes[13][14].

From an ASD perspective:

Non-linear work is designed around fast learning loops that update local rules, structures, and strategies continuously
Linear work tends to suppress or delay feedback through long phases and late integration, which increases risk in complex domains

The quality and speed of feedback loops determine system agility more than any particular methodology or tool.

3. Structural Coupling with Environment

A system demonstrates agility in ASD when its internal structures co-evolve with environmental signals. These structures include roles, policies, cadences, and decision rights. This evolution occurs rather than resisting these signals[13][14].

Linear work assumes weak coupling: the environment can be treated as constant during execution
Non-linear work assumes strong coupling and builds mechanisms to adapt structure as the system learns

Agile transformations that succeed change not just process but also governance, incentives, and power distribution to enable structural adaptation.

4. Portfolio of Dynamics, Not One Best Practice

ASD reframes the linear vs non-linear question as a dynamics design question:

Where do we want stabilizing dynamics? (standardization, low variance, linear throughput)
Where do we want exploratory dynamics? (experiments, branching paths, non-linear scaling effects)
How do we design coherent interaction rules between these dynamics?

The art of organizational design in VUCA involves creating systems. These systems do not oscillate between chaos and rigidity. Instead, they maintain dynamic balance.

ASD-Style Diagnostic Questions

For any work stream, ASD would guide leaders to ask:

Information decay rate: How quickly does external information (customers, regulators, competitors, technology) invalidate our current plan?
Agent coordination complexity: How many autonomous agents must coordinate, and how aligned are their objectives?
Cost asymmetry: What is the cost of being wrong vs the cost of being slow?
Feedback availability: How quickly can we generate reliable feedback about our decisions?

Decision heuristic:

Plans invalidate slowly + few agents + aligned objectives + high cost of delay → Bias toward linear work with light feedback
Plans invalidate quickly + many agents + conflicting objectives + high cost of error → Design non-linear work with explicit agile feedback loops and adaptive structures

Practical Examples of Linear Work Failing in VUCA

Understanding failure patterns helps organizations recognize when they are applying linear methods inappropriately[12][15][16][17].

Typical Failure Patterns

Plans Become Obsolete on Contact with Reality

Traditional strategy and annual planning often assume environmental stability. In VUCA contexts, markets, technologies, or regulations shift before execution completes, rendering detailed plans irrelevant[12][18][19].

Strategy research shows that rigid plan-and-execute approaches lead to “implementation crises.” In these situations, employees no longer see connections between daily decisions and the original strategy[12][18]. Organizations experience:

95% of employees not understanding how to act on strategy[12]
Repeated re-planning while competitors adapt faster[12][18]
Strategy documents becoming “implementation theater” rather than decision guides[12]

Rigid Phase-Gates Delay Feedback

Waterfall and heavy linear methods lock requirements and design early, with testing and user feedback only at the end. In unstable contexts, this means validating solutions only after environments and needs have changed[15][16][20].

Empirical research on projects in adverse (VUCA) environments shows method misfit to the level of change. This misfit significantly increases failure rates in time. It also affects budget and goal achievement[15].

Example 1: Public-Sector IT (Waterfall Failure)

Context: A large police IT system in Scotland (i6) ran as a classic waterfall project. It assumed an existing solution could be linearly adapted. This adaptation aimed to replace approximately 130 processes and systems[16].

What happened:

As complexity and interdependencies emerged (bespoke needs, cross-system standards, data integration issues), the original linear plan could not absorb the learning
Rework exploded, delays accumulated, coding flaws multiplied
The contract was eventually terminated despite stakeholders “doing everything by the book”[16]

Why this is a VUCA/linear mismatch:

High uncertainty about integration with many legacy systems
Multiple stakeholders with evolving requirements
Governance optimized for documentation and pre-contract certainty instead of iterative discovery and incremental integration[16][20]

Example 2: Strategy Implementation Crisis

Context: In volatile markets, traditional multi-year top-down strategy rollouts frequently fail because plans cannot guide decisions once conditions change[12][18][19].

Failure mechanisms:

Strategy documents define targets and initiatives but lack simple decision rules for teams facing local surprises (e.g., sudden competitor entry, supply disruption)[12][18]
Linear cascades through annual cycles prevent rapid adjustment
By the time budgets and objectives are updated, markets have moved again[12][18][19]

Impact: Research and practice reports show that strategies framed as fixed plans become disconnected from daily operations. Executives endlessly re-plan while implementation stalls[12][18].

Example 3: COVID-19 and Just-In-Time Supply Chains

Context: Global supply chains were optimized linearly for cost and efficiency—just-in-time inventory, minimal buffers, long single-source chains—assuming smooth, predictable flows[21][22][23].

What failed:

When borders closed or suppliers stopped during COVID-19, companies had little visibility beyond tier-1 suppliers and almost no slack
Cascading shortages and long recovery times resulted
Planning models treated demand and supply as stable and independent, not as coupled non-linear systems with correlated shocks[21][22][23]

Linear work vulnerability:

Response plans were not designed for rapid scenario updates and local decision-making
Companies that stuck to original sourcing and inventory assumptions suffered deeper and longer disruptions than those that adjusted quickly[21][22][23]

Example 4: Digital Transformation as Linear Rollout

Context: Many digital transformations are organized as linear programs. They begin by defining the target state. Next, they involve selecting technology and implementing in phases. Finally, these programs roll out to all units[17][20].

Failure statistics: Studies show 70-90% of such initiatives fail or stall[17].

Key patterns:

Inflexible culture and process suffocate experimentation, so pilots do not reveal real adoption dynamics and scaling issues until too late[17]
Bureaucratic waterfall phases (heavy documentation, long approvals) slow learning and prevent teams from adapting when they discover new needs or constraints[17][20]
Rigid, top-down approaches collide with evolving technologies, unclear use cases, and changing organizational power dynamics[17]

Systemic Structure of These Failures (ASD Interpretation)

From an Agile Systems Dynamics perspective, each failure shares the same underlying structure. There is strong non-linearity in the environment and organization. However, work is designed as if the system were linear.

Hidden feedback loops and delays:

In IT and transformation cases, feedback (real user needs, integration issues, cultural blockers) appears late and is filtered through governance layers
Corrective action arrives when the cost of change is maximal[16][17][20]

Misaligned agent goals:

In strategy and transformation, executives optimize for plan certainty and budget approval while local teams need decision flexibility
Linear design amplifies goal conflicts instead of exposing and renegotiating them early[12][17][18]

Over-optimization for single objectives:

Just-in-time supply chains optimized for efficiency at the expense of resilience, ignoring non-linear risk amplification when shocks hit tightly coupled networks[21][22][23]

ASD would model these as systems where reinforcing loops (commitment to original plan, sunk-cost bias, local optimization) overpower balancing loops. These balancing loops include experimentation, early feedback, and design for resilience. This leads to brittle behavior when VUCA factors spike.

Agile Alternatives That Succeed in VUCA

Agile alternatives succeed where linear methods fail. They treat work as iterative and feedback-driven. The process is emergent rather than as fixed linear plans. They optimize for learning speed, resilience, and adaptability instead of upfront certainty[1][18][24][25][26][27].

Core Agile Patterns for VUCA

Short Feedback Cycles and Incremental Delivery

Frameworks like Scrum, Kanban, and related agile practices rely on small batches. They emphasize frequent inspection and adaptation through sprints, reviews, and retrospectives. This approach allows teams to update plans as volatility unfolds[24][25][26].

Contrast with linear delivery:

Linear “big-bang” delivery delays learning until the end
In high uncertainty, shorter cycles significantly improve fit to changing customer and stakeholder needs[24][25]

Emergent and Adaptive Strategy

Emergent strategy approaches deliberately treat complex contexts as spaces. In these spaces, problem definition and solution co-evolve. They use principles and decision rules instead of detailed long-range plans[18][28][29].

Strategy work in VUCA:

Uses iterative scenario planning, continuous sensing, and “act-sense-respond” logics
Aligned with Cynefin’s complex/chaotic domains
Replaces linear “analyze-plan-execute” with adaptive frameworks[18][28]

Concrete Agile Alternatives by Domain

Product Development and Transformation

Scrum, Kanban, and Hybrid Agile

Systematic reviews illustrate that customizing agile frameworks to context increases responsiveness. Such customization also reduces time-to-market and improves customer satisfaction in volatile environments[24][25][26].

Why they succeed:

Replace fixed scope and long upfront design with prioritized backlogs
Enable incremental releases and continuous refinement
Succeed where waterfall frequently fails in digital and transformation initiatives[17][24][25]

Continuous Discovery and Dual-Track Agile

Successful organizations separate discovery from delivery. Discovery means learning what to build. Delivery is the process of building it. They run experiments, prototypes, and user tests in parallel with incremental implementation[25][26].

Advantage:

Avoids the linear trap of freezing requirements too early
Tests assumptions quickly, reducing risk of late, expensive surprises[17][25]

Strategy and Portfolio in VUCA

Agile and Emergent Strategy Frameworks

Emergent strategy methods explicitly framed for VUCA treat strategy as a living framework. This framework consists of constraints, options, and hypotheses. It is refined through iterative tests and feedback[1][18][28][29].

Characteristics:

Use design principles, option portfolios, and regular strategy reviews
Replace infrequent rigid planning cycles
Enable faster strategic pivots when conditions shift[1][18][28][29]

Agile Portfolio Management

Agile portfolio approaches use shorter funding cycles. They rely on lean business cases and frequent reprioritization. These methods help to shift investment across initiatives as new information emerges[25][26].

Benefit: Overcomes the linear “lock-in” of multi-year fixed business cases that become misaligned in volatile markets.

Supply Chains and Operations

Agile and Resilient Supply Chains

Post-COVID-19 analyses show that companies with more agile supply chains recovered faster. These agile supply chains include multi-sourcing, regionalization, flexible capacity, and digital control towers. They captured market share compared with linear just-in-time models optimized only for cost[21][22][23][27][30].

Key features:

Continuous monitoring and scenario planning
Cross-functional collaboration
Near real-time reconfiguration of flows and suppliers[22][27][30]

Network Agility and Modular Operations

Leaders build modular operations and flexible supplier networks. They segment supply chains to enable different responses for different product segments. This approach is preferred over one monolithic plan[21][22][27][30].

Leadership, Learning, and Organization Design

Agile Leadership Practices

Agile leadership in VUCA emphasizes clear intent with flexible paths, frequent delivery, open communication, experimentation, and empowerment over command-and-control[26][31][32].

Focus areas:

Framing problems and setting boundaries
Enabling local decisions
Makes organizations more responsive than purely top-down linear decision chains[26][31][32]

Agile Learning and Continuous Improvement

Agile learning focuses on rapid learning loops, cross-functional collaboration, and application of new knowledge to new situations. This approach is strongly associated with higher agility and better outcomes in VUCA contexts[1][25][26].

Systematic reviews of agile transformations highlight adaptive leadership, continuous improvement, and contextual tailoring of methods as key success drivers[1][25].

Comparison: Linear vs Agile in VUCA

Dimension	Linear Method in VUCA	Agile Alternative That Succeeds
Planning horizon	Long, fixed plans	Short cycles, rolling planning
Scope	Fixed upfront scope	Evolving scope via backlog
Feedback	Late, end-loaded	Early, frequent, structured
Strategy	Plan-then-execute	Emergent, iterative strategy
Supply chain	Cost-optimized just-in-time	Resilient, multi-sourced, digital
Leadership	Command-control, predict-control	Empowering, adaptive leadership
Learning	End-of-phase reviews	Continuous improvement loops
Risk management	Upfront risk assessment	Iterative risk discovery
Decision-making	Centralized, hierarchical	Distributed, context-driven

Table 2: Linear methods vs agile alternatives in VUCA contexts

Practical Implications and Recommendations

For Leaders and Practitioners

Conduct honest context assessment: Use ASD diagnostic questions to determine where linear vs non-linear work is appropriate in your organization
Design dual systems explicitly: Do not treat the entire organization as either linear or agile—consciously architect ambidextrous portfolios
Invest in feedback infrastructure: The quality of your feedback loops determines agility more than any methodology label
Build adaptive capacity: Train leaders and teams in sensing, interpreting, and responding to weak signals rather than just executing plans
Challenge linear defaults: Question assumptions of stability, predictability, and proportionality in strategy, transformation, and innovation work
Create safe-to-fail experiments: In uncertain domains, design small, reversible experiments rather than betting everything on a single linear plan

When to Keep Linear Approaches

Linear work remains valuable when:

Operating in Cynefin’s “obvious” or “complicated” domains
Executing validated solutions at scale
Managing regulated, safety-critical, or compliance-driven processes
Optimizing stable, repeatable operations

When to Shift to Non-Linear Approaches

Non-linear work becomes essential when:

Operating in Cynefin’s “complex” or “chaotic” domains
Facing high uncertainty about problem definition or solution
Navigating rapid environmental change
Managing multi-stakeholder systems with emergent dynamics
Leading innovation, transformation, or strategic change

Conclusion

The choice between linear and non-linear work is not ideological but contextual and strategic. In a VUCA world, organizations must develop the capability to consciously design portfolios of work dynamics. They should maintain efficiency where stability exists. They must also build adaptability where complexity and uncertainty dominate.

Agile Systems Dynamics provides a powerful lens for understanding this design challenge. It emphasizes that agility emerges from the interplay of agents, feedback loops, and structural coupling with the environment. Agility stems from conscious dynamics design rather than from adopting any single methodology.

The evidence is clear. Linear methods optimized for predictability and efficiency fail systematically in VUCA contexts. These contexts are characterized by volatility, uncertainty, complexity, and ambiguity. Thriving organizations do not abandon structure. They build adaptive structures using short feedback cycles and emergent strategy. They employ modular operations and empowering leadership. This helps them sense and respond faster than their environments change.

The imperative for leaders is not to choose between linear and non-linear work universally. Instead, they must develop the sophistication to diagnose context. They need to design appropriate dynamics and build organizational capabilities for both exploitation and exploration. This ambidexterity—maintaining stability where needed while fostering agility where required—represents the essence of organizational fitness in VUCA environments.

References

[1] ScienceDirect. (2024). Managing the VUCA environment: The dynamic role of organizational learning and strategic agility. https://www.sciencedirect.com/science/article/pii/S0019850124002062

[2] World Scientific. (2025). From VUCA and BANI to a PUMO World: Why Agile Innovation Is Not Enough. https://www.worldscientific.com/doi/10.1142/S0219877025500129

[3] Neis, P. E. (2025, October 16). Linear vs. Non-Linear Systems. LinkedIn. https://www.linkedin.com/pulse/linear-vs-non-linear-systems-pierre-e-neis-0mt2e

[4] Lepaya. (2021, March 10). Linear vs Non-linear Learning and the Future of Work. https://www.lepaya.com/blog/linear-and-non-linear-learning

[5] Pinckley, C. (2020, May 4). What’s Working and What’s Not Right Now? Linear Vs. Nonlinear Thinking. LinkedIn. https://www.linkedin.com/pulse/whats-working-right-now-linear-vs-nonlinear-thinking-chris-pinckley

[6] Chuck’s LAMP. (2009, April 10). What kind of thinker am I? Linear vs. Non-linear thinking. https://chuckslamp.com/index.php/2009/04/11/non-linearthinking/

[7] Digital Leadership. (2024, April 23). VUCA World – Meaning, Examples And Management Steps. https://digitalleadership.com/blog/vuca-world/

[8] Agile Organization. (2026, January 14). The Dynamics of Agile Systems: Key Insights. https://agile-organization.com/2026/01/15/the-dynamics-of-agile-systems-key-insights/

[9] University of Western Ontario. (2021, August 1). Initiating Leadership Development In a VUCA Environment. https://ir.lib.uwo.ca/cgi/viewcontent.cgi?article=1233&context=oip

[10] Cadmus Journal. (2024, July 30). A Scale Development for VUCA World Management. https://www.cadmusjournal.org/article/volume-5-issue-3-p2/vuca-world-management

[11] Arkaro. (2025, August 3). Strategy Implementation Crisis: When Plans Fail in VUCA. https://arkaro.com/strategy-implementation-crisis/

[12] Neis, P. (2026, February 17). Agile Systems Dynamics: A New Approach to Organizational Behavior. LinkedIn. https://www.linkedin.com/posts/pierreneis_agile-systems-dynamics-field-guide-activity-7429837448886530049-aX23

[13] Agile Organization. (2026, January 14). The Dynamics of Agile Systems: Key Insights. https://agile-organization.com/2026/01/15/the-dynamics-of-agile-systems-key-insights/

[14] Neis, P. (2026, February 17). Agile Systems Dynamics: A New Approach to Organizational Behavior. LinkedIn. https://www.linkedin.com/posts/pierreneis_agile-systems-dynamics-field-guide-activity-7429837448886530049-aX23

[15] SciELO. (2023, June 4). VUCA environment on project success: The effect of agility and resilience. https://www.scielo.br/j/bbr/a/mK4tMzsYMRhKLJbxPCL4c7w/

[16] UK Campaign for Change. (2017, March 8). A classic “waterfall” IT project disaster – yet officials went by the book. https://ukcampaign4change.com/2017/03/09/a-classic-waterfall-it-project-disaster-yet-officials-went-by-the-book/

[17] Veremark. (2025, May 2). Why Digital Transformations Fail and What Lessons Can Be Learned. https://www.veremark.com/blog/why-digital-transformations-fail-and-what-lessons-can-be-learned

[18] Arkaro. (2025, July 19). Strategy in a VUCA World: Emergent Approach Guide. https://arkaro.com/strategy-in-a-vuca-world/

[19] IMD. (2015, March 17). Is VUCA the end of strategy and leadership? https://www.imd.org/research-knowledge/leadership/articles/is-vuca-the-end-of-strategy-and-leadership/

[20] SCIRP. (2025, April 24). A Case Study on Adaptation of Waterfall Methodology. https://www.scirp.org/journal/paperinformation?paperid=142222

[21] McKinsey. (2020, October 8). COVID-19 and supply-chain recovery: Planning for the future. https://www.mckinsey.com/capabilities/operations/our-insights/covid-19-and-supply-chain-recovery-planning-for-the-future

[22] Bain & Company. (2020, April 9). Covid-19: Protect, Recover and Retool. https://www.bain.com/insights/covid-19-protect-recover-and-retool/

[23] PMC. (2021, May 19). Bend or break? Small business survival and strategies during COVID. https://pmc.ncbi.nlm.nih.gov/articles/PMC9764849/

[24] Adesso. (2023, February 22). Using agile working methods to navigate the VUCA world. https://www.adesso.de/en/news/blog/10-agile-software-development-using-agile-working-methods-to-navigate-the-vuca-world-2.jsp

[25] IntechOpen. (2024, November 6). Business Strategies and Best Practices for VUCA and BANI World. https://www.intechopen.com/chapters/1205762

[26] Gemrain. (2024, July 22). Thriving in Uncertainty: Agile Leadership for the VUCA Environment. https://www.gemrain.net/post/thriving-in-uncertainty-agile-leadership-for-the-vuca-environment

[27] Bain & Company. (2020, April 26). Supply Chain Lessons from Covid-19: Time to Refocus. https://www.bain.com/insights/supply-chain-lessons-from-covid-19/

[28] Hult. (2018, March 11). Managing strategy in a VUCA world. https://www.hult.edu/blog/managing-strategy-in-a-a-vuca-world/

[29] Haas Consulting. (2024, March 14). Agile strategy development in the VUCA world. https://haas-consulting.tech/en/neuer-ansatz-agile-strategie-entwicklung-in-der-vuca-welt/

[30] Knowledge Ridge. (2025, October 21). 3 COVID-19 Lessons for Agile Supply Chain Software. https://www.knowledgeridge.com/expert-views/3-covid-19-lessons-for-agile-supply-chain-software/

[31] Kaizenko. (2023, December 11). Leadership Agility in a VUCA World: Strategies for Success. https://www.kaizenko.com/leadership-agility-in-a-vuca-world/

[32] Harvard Business. (2025, February 10). Thriving in the Most VUCA of VUCA Environments. https://www.harvardbusiness.org/insight/february-2025-the-leaders-agenda-navigating-uncertainty-thriving-in-the-most-vuca-of-vuca-environments/

Get the ASD Book

An Analysis of #play14 Through the Agile Organization Method Framework

Abstract

This paper examines #play14. It is a recurring international unconference focused on serious games. The paper studies it through the lens of the Agile Organization (AO) Method. We demonstrate that #play14 functions as a “micro-organization.” It manifests core AO patterns—platform, plexus, swarms, coherence, and simple rules—in concentrated form. We analyzed #play14’s structure, governance, and operational dynamics systematically. Our analysis shows that minimal organizational infrastructure combined with a clear purpose can generate high-quality collaboration. Well-designed interaction rules help achieve learning and innovation without traditional hierarchical control. The paper contributes to organizational agility theory. It provides empirical grounding for lightweight organizational designs. It also offers practitioners a concrete exemplar for implementing AO principles. Our findings suggest that the #play14 model represents a viable alternative to conventional organizational structures. This is especially true for knowledge work contexts requiring high adaptability. It also requires participant engagement.

Keywords: organizational agility, unconference, serious games, platform organizations, self-organization, Agile Organization Method, Open Space Technology

1. Introduction

Contemporary organizations face mounting pressure to achieve agility. They need the capacity to sense and respond rapidly to environmental changes. They must also maintain coherence and effectiveness[40][42][46][47]. Significant research has examined agile software development practices and their organizational implications[40][42][46]. However, less attention has been given to organizational forms that embody agility as an intrinsic property. These forms see agility as a natural characteristic rather than an adopted methodology. This paper addresses this gap by analyzing #play14, an international unconference network, as a naturally agile organizational system.

#play14 is a worldwide gathering of practitioners. They believe that “playing is the best way to learn, share and be creative”[1][16]. Since its inception, #play14 has operated across multiple countries and continents using an unconference format based on Open Space Technology[16][17][35]. Participants create the event’s content in real-time through a daily marketplace. In this marketplace, anyone can propose game-based sessions. Topics include facilitation and team dynamics. They also cover change management and leadership[16][17][22].

We analyze #play14 through the Agile Organization (AO) Method. It is a systemic framework for organizational design that emphasizes platforms and plexus (minimal coordinating structure). The framework also highlights swarms (temporary self-organizing teams), coherence (shared purpose), and simple rules over complex processes[20][26][29]. The AO Method uses systems thinking, complexity science, and the Viable System Model (VSM). It provides design principles for adaptive organizations[20][29][51][54][58].

Our central research question is: How does #play14 manifest AO principles? What can this reveal about designing minimal yet effective organizational structures?

This inquiry is significant for three reasons.

First, #play14 provides a rare empirical case of an organization that exhibits high agility without deliberate agile transformation. It is “born agile” rather than “made agile.”

Second, the unconference operates at scales between 50 to 200 participants per event. It handles complexities typical of organizational units within larger enterprises. This makes it directly relevant to practitioners.

Third, #play14’s global replication across diverse cultural contexts suggests robust underlying design principles worth extracting and formalizing.

The paper is structured in the following way. Section 2 reviews relevant literature on organizational agility. It also covers serious games as organizational learning tools, Open Space Technology, and the AO Method. Section 3 describes our analytical approach. Section 4 presents a systematic mapping of #play14 elements to AO patterns. Section 5 discusses theoretical and practical implications. Section 6 concludes with limitations and future research directions.

2. Literature Review

2.1 Organizational Agility and Design

Organizational agility has emerged as a critical capability for sustained performance in volatile environments[42][44][47][53]. Worley and Lawler define organizational agility as “the capacity of an organization to efficiently and effectively redeploy its resources.” It involves redirecting resources to value creating and value protecting activities. These are higher-yield activities as warranted by internal and external circumstances[44]. This definition emphasizes dynamic resource allocation rather than static structural efficiency.

Recent research has identified key organizational design features that enable agility. These include “maximum surface area” structures that place employees in direct contact with customers and markets. They also involve transparent information flows, flexible talent systems, and decentralized decision-making[42][44][50]. Shafiee et al.’s case study identified eighteen organizational practices. These are grouped into four categories: structure and governance, culture and people, IT tools and data infrastructure, and processes. Collectively, these practices support agile product development[40][42][50].

Most agility research focuses on transforming existing bureaucratic organizations toward greater agility. It rarely examines organizations designed from inception to be agile[46]. This transformation perspective creates a bias toward incremental change and hybrid organizational forms that blend traditional hierarchy with agile elements. Our study of #play14 offers a contrasting perspective: an organization intentionally designed around agility principles without legacy constraints.

2.2 Serious Games and Organizational Learning

Serious games—games designed for purposes beyond entertainment—have gained recognition as effective tools for organizational learning and capability development[17][41][43][45]. Research demonstrates that serious games enhance employee engagement, knowledge retention, and skill development. They create safe-to-fail environments where participants can experiment with new behaviors and mental models[17][25][41][43].

Giannarakis et al. found that serious games enable managers to understand and develop knowledge about complex innovations more effectively than traditional training methods[41]. The experiential, embodied nature of game-based learning creates stronger cognitive and emotional engagement than passive information transfer[43][45]. Games compress time. They allow participants to experience consequences of decisions. Participants can also see system dynamics that would unfold slowly in real organizational contexts[17][41].

The #play14 community explicitly leverages this learning mechanism. They use games not merely as training tools but as sense-making devices. These games help explore organizational phenomena such as collaboration, complexity, communication, and change[17][22][25]. This positions serious games as legitimate research and development infrastructure for organizational design, not merely pedagogical supplements.

2.3 Open Space Technology

Open Space Technology (OST), developed by Harrison Owen, is a facilitation methodology for participant-driven meetings. It is built around four principles and one “law”[16][52][55][57][59]. The principles include: “whoever comes are the right people.” Another principle is “whatever happens is the only thing that could have.” “Whenever it starts is the right time.” Finally, “when it’s over, it’s over.” The “law of two feet” (or mobility) states that participants should move. They should go to where they can contribute or learn most effectively[16][17][55].

Academic research on OST has documented its effectiveness for enabling self-directed learning. It fosters autonomy and motivation. It also creates conditions for emergent agenda-setting in educational and organizational contexts[52][55][57][59]. Dixon’s master’s thesis identified OST as an effective approach to whole-system change. Norris’s grounded theory study examined the value associated with OST. It concluded that the methodology generates significant participant engagement and actionable outcomes[55][59].

OST is critical to our analysis. It creates what Owen calls “self-organizing systems”—social systems that spontaneously develop order and purpose. They do this without central coordination[55]. This emergent order aligns conceptually with complex adaptive systems theory and provides a practical mechanism for implementing organizational agility principles[16][17][55].

2.4 The Agile Organization Method and Viable System Model

The Agile Organization (AO) Method is a systemic framework. It designs adaptive organizations based on patterns observed in high-performing agile systems[20][26][29]. The method integrates concepts from the Viable System Model (VSM). It also draws from complexity science and agile software development. These are combined into a coherent design language[29][51][54].

Central to the AO Method are three structural elements[20][29]:

Platform: The stable container providing infrastructure, standards, and enabling services that allow operational units to function effectively.
Plexus: A minimal coordinating structure. It maintains system coherence and stewards culture and values. This structure manages inter-unit dependencies. It provides strategic direction without detailed operational control.
Swarms: Temporary, self-organizing teams that form around specific problems or opportunities, collaborate intensively, then dissolve when their purpose is fulfilled.

These structural elements are governed by design principles[29]:

Coherence: Alignment through shared purpose, values, and simple rules rather than detailed policies and procedures.
Cohesion: Integration mechanisms that maintain system integrity while preserving autonomy of operational units.
Simple Rules: Minimal constraints that guide behavior without prescribing actions, enabling emergence and adaptation.
Avoidance: Deliberate elimination of unnecessary structure, process, and work that does not create value.
Separation: Bounded spaces where different dynamics can operate at different speeds, protecting innovation from operational pressures.
Assimilation: Selective adoption of successful practices from experiments into standard operations, allowing the organization to evolve based on evidence.

The VSM, developed by Stafford Beer, provides theoretical grounding for these patterns[51][54][56][58]. VSM describes any viable organization as composed of five interacting systems. These are operational units (System 1), coordination (System 2), and optimization and resource allocation (System 3). They also include strategic intelligence and adaptation (System 4), and identity and policy (System 5)[51][54][56][58]. The AO Method translates VSM’s cybernetic language into practical design patterns accessible to practitioners[20][29].

VSM has been applied to organizational diagnosis and design across diverse contexts[51][54][56][58][60]. However, few studies have examined naturally occurring organizations that instantiate VSM principles without explicit design intervention. Our analysis of #play14 provides such an instance.

3. Methodology

This study employs qualitative case analysis using the AO Method as an analytical framework. Case study methodology is appropriate for examining complex organizational phenomena in real-world contexts. It is also suitable for theory elaboration where existing frameworks need empirical grounding[40][42]. Our approach follows Yin’s guidelines for rigorous case analysis. We also acknowledge our dual role as observers. Additionally, we are participants in the #play14 community.

3.1 Data Sources

Our analysis draws on multiple data sources to ensure construct validity:

Primary documentation: Official #play14 website content describing format, values, principles, and history[1][16][21].
Participant accounts: Published blog posts, LinkedIn articles, and reflective essays by #play14 attendees across multiple events and locations[17][22][25][33][35].
Organizational artifacts: Event schedules, marketplace boards (photographs), session documentation, and community guidelines[16][21][30].
Academic literature: Published research on unconferences, OST, and organizational agility providing comparative context[38][39][52][55][57][59].
Participant observation: Author’s direct experience attending and organizing #play14 events, providing insider perspective on operational dynamics.

3.2 Analytical Approach

We conducted systematic pattern matching between observed #play14 characteristics and AO Method constructs. For each AO element (platform, plexus, swarms, coherence, simple rules, avoidance, separation, assimilation), we:

Identified concrete manifestations in #play14 structure and operations.
Gathered supporting evidence from multiple data sources.
Assessed the strength and consistency of pattern correspondence.
Examined negative cases or contradictions.
Synthesized findings into a coherent organizational description.

This approach combines deductive analysis (applying the AO framework) with inductive discovery (identifying emergent patterns not anticipated by the framework). We employ thick description to provide sufficient detail for readers to assess transferability to their own contexts.

3.3 Limitations

Several limitations should be noted. First, as participants in the #play14 community, we bring insider perspective that enables rich understanding but may introduce confirmation bias. We mitigate this through systematic use of external documentation and published accounts. Second, #play14 events vary across locations and organizing teams; our analysis synthesizes common patterns but may not capture all variation. Third, the study is descriptive and analytical rather than interventionist; we observe naturally occurring patterns rather than testing causal hypotheses.

4. Analysis: #play14 Through the AO Lens

4.1 Platform: The Unconference Infrastructure

In AO terms, a platform is the stable infrastructure that enables operational activity without dictating its content[20][29]. The #play14 platform consists of:

Physical and temporal container: Each event occupies a defined venue for 2–3 days. This typically happens from Friday evening through Sunday afternoon. This creates a bounded space-time container[1][16][30][31]. This separation from daily work environments enables experimental behaviors and psychological safety[17][21][35].

Shared infrastructure: Registration systems, venue logistics, and food and accommodation arrangements are essential. Visual materials such as flip charts, markers, and post-its are also provided. Game libraries offer common resources available to all participants[16][30][31]. Importantly, the platform provides infrastructure without prescribing how it will be used.

Communication channels: Digital platforms including websites, Slack workspaces, and social media channels extend the platform beyond physical events. They enable pre-event coordination and post-event knowledge sharing[1][16][31][33].

Global branding and identity: The #play14 name, visual identity, and core narrative create a recognizable brand. The phrase “play is the best way to learn, share and be creative” is central to this identity. This helps facilitate replication across contexts[1][16][21][28]. This common identity reduces coordination costs while allowing local adaptation.

Non-profit economic model: Events operate on a break-even basis with any surplus reinvested in future events or donated to charity[16][17][21]. This economic design removes profit motives that might distort content toward commercial interests. It maintains alignment with the core purpose of learning and sharing.

The #play14 platform exhibits the AO principle of minimalism: it provides just enough structure to enable self-organization without constraining it. Unlike traditional conferences that specify detailed agendas, speaker lineups, and tracks, the #play14 platform is intentionally incomplete. It creates conditions for emergence rather than programming content.

4.2 Plexus: Minimal Coordination Structure

The plexus in AO represents the minimal coordinating infrastructure that maintains system coherence without centralized control[20][29]. In #play14, the plexus appears as:

Organizing crew: Each event has a small organizing team of typically 3–8 people. They handle venue selection, logistics, registration, and event facilitation[16][17][21][30]. Critically, organizers do not control content—they hold space rather than fill it[16][17].

Format stewardship: Organizers introduce and maintain the Open Space format. They explain principles and rules at the event opening. They also facilitate the marketplace session where participants propose and select activities. Additionally, they guide opening and closing circles[16][17][22][35]. This facilitation role preserves the unconference structure without dictating content.

Values guardianship: The plexus maintains explicit values including playfulness, psychological safety, non-commercialism, and inclusivity[21]. When conflicts arise or behavior violates community norms, organizers intervene to restore alignment with values[21].

Inter-event coordination: A loosely coupled network of organizers across different cities and countries shares practices, maintains the play14.org website, and coordinates the calendar of events to avoid conflicts[1][16]. This distributed governance model allows local autonomy while maintaining global coherence.

Boundary management: Organizers define what #play14 is and is not—for example, explicitly excluding digital games, slideshows, and “Rockstar” keynote formats[1][16][19][22]. These boundaries protect the unconference’s distinctive character while still allowing wide variation within those boundaries.

The #play14 plexus demonstrates the AO principle of governance without management: it shapes conditions and boundaries but does not direct operational activity. This aligns with Beer’s VSM System 5 (identity and policy) and System 4 (strategic intelligence) without heavy System 3 (operational optimization) interventions[51][54][56].

4.3 Swarms: Self-Organizing Game Sessions

Swarms in the AO Method are temporary teams that form around specific problems or opportunities, collaborate intensively, then dissolve[20][29][32]. Each #play14 game session is a prototypical swarm:

Marketplace formation: Each morning, participants gather for a “marketplace.” Anyone can propose a game or activity. They do this by writing it on a card and briefly describing it to the group[16][17][22][35]. Participants then sign up for sessions that interest them, creating just-in-time teams.

Voluntary participation: The “law of two feet” ensures participation is entirely voluntary. People join sessions where they can contribute or learn. They leave when this is no longer true[16][17][22][55]. This mobility prevents dead sessions and ensures energy flows to valuable activities.

Time-boxed execution: Sessions are typically 60–90 minutes, creating clear boundaries and urgency[16][17][22]. This time constraint forces focus and prevents endless discussion.

Facilitated by initiator: The person proposing a session serves as a facilitator. They are not a traditional “presenter.” Their role is to guide the activity, not to lecture[16][17][25][35]. Expertise is distributed among participants rather than concentrated in one authority figure.

Cross-pollination: “Bumblebees” who move between sessions carry insights from one context to another, creating unexpected connections and idea recombination[16][17][22]. “Butterflies” who hover at the edges without deep engagement provide reflective distance and alternative perspectives[16][17].

Dissolution and recombination: After each session, swarms dissolve. Participants then form new swarms for the next time slot, creating fluid social structures that maximize learning and connection[16][17][22][35].

The swarm pattern in #play14 illustrates several AO principles. First, autonomy: teams self-select and self-organize without central assignment. Second, alignment: despite autonomy, swarms align with the overall purpose (learning through play) through shared values rather than hierarchical control. Third, rapid formation and dissolution: the low transaction cost of forming and dissolving teams allows for rapid adaptation. This enables a quick response to emerging interests and needs[16][17][29].

4.4 Coherence: Shared Purpose and Values

Coherence in the AO Method refers to alignment through shared purpose, values, and meaning. This alignment is achieved not through detailed rules and hierarchical control[20][29]. #play14 exhibits strong coherence mechanisms:

Explicit purpose: The statement “playing is the best way to learn, share and be creative” appears consistently. It is found across all #play14 materials and events[1][16][21][28]. This simple purpose statement provides a decision filter. Activities that support learning, sharing, and creativity through play are coherent with the purpose. Those that do not are incoherent.

Values articulation: The #play14 values page explicitly states principles including openness, participation, non-commercialism, face-to-face interaction, and psychological safety[21]. These values are not abstract aspirations but operational guidelines that shape behavior.

Ritual reinforcement: Opening and closing circles create shared experiences that reinforce collective identity and purpose[17][22][35]. These rituals transform a collection of individuals into a temporary community with shared meaning.

Stories and culture: Blog posts, articles, and social media content by participants shape a narrative culture. This culture reinforces what #play14 is about. It also conveys how it feels to participate[17][22][25][33][35]. These stories serve as cultural transmission mechanisms, educating newcomers about norms and expectations.

Self-selection: The fact that people choose to attend #play14 (rather than being assigned) creates high baseline alignment. Participants self-select based on resonance with the purpose, reducing the coordination burden required to maintain coherence.

The coherence mechanisms in #play14 demonstrate what AO calls alignment without enforcement. Participants behave coherently not because they are monitored and controlled, but because they share purpose and values[20][29]. This distributed coherence is more resilient than hierarchical alignment because it does not depend on central authority.

4.5 Simple Rules and Avoidance

The AO Method emphasizes simple rules that guide behavior without prescribing it, and deliberate avoidance of unnecessary structure[20][29]. #play14 embodies both principles strikingly:

Four principles and one law: Open Space Technology’s entire governance structure for each event is based on four principles. The right people are whoever comes. The only thing that could have happened is whatever happens. The right time is whenever it starts. It’s over when it’s over. It also relies on one law: the law of two feet[16][17][22][55]. These five simple rules replace detailed schedules, role descriptions, and process documentation.

No fixed agenda: By eliminating pre-programmed agendas, #play14 avoids the coordination overhead of speaker recruitment. It also avoids schedule conflicts and room assignments. Attendee commitment decisions made months in advance are also eliminated[16][17][19][22]. The marketplace creates the agenda just-in-time based on current participant interests.

No hierarchical presentations: #play14 excludes keynotes, slideshows, and “Rockstar” talks. This approach avoids the status dynamics common in traditional conferences. It also prevents passive learning modes[1][16][19][22]. Everyone is a peer contributor.

No digital games: The explicit exclusion of digital games forces face-to-face interaction and embodied engagement[16][19][22][25]. This constraint actually expands creative possibilities by directing attention toward interpersonal dynamics rather than screen-mediated experiences.

Minimal documentation: Unlike academic conferences with proceedings and published papers, #play14 produces minimal formal documentation[1][16]. Knowledge transfer happens through direct participation and subsequent informal sharing rather than through codified artifacts. This reduces administrative overhead while emphasizing experiential learning.

The avoidance principle is particularly visible: #play14 systematically avoids the complexity that conferences typically accumulate. These complexities include detailed programs, abstract review processes, and multiple submission formats. They also involve sponsorship management, commercial exhibition spaces, and hierarchical social structures. By eliminating these elements, #play14 reduces coordination costs and focuses energy on direct learning and relationship building.

This pattern aligns with the AO principle that complexity should be in the interaction patterns, not in the structural rules[29]. Simple rules enable complex, emergent behavior; complex rules constrain behavior to simpler, more predictable patterns.

4.6 Separation and Experimentation

Separation in the AO Method means creating bounded spaces. Different dynamics can operate without interfering with each other. This separation particularly protects experimental activities from operational pressures[20][29]. #play14 functions as a separated experimental space:

Temporal separation: The weekend or multi-day format creates clear boundaries between #play14 time and regular work time[1][16][30][31]. This separation provides psychological permission to experiment with behaviors and perspectives that might feel risky in work contexts.

Physical separation: Events occur in dedicated venues (conference centers, universities, retreat spaces) away from participants’ workplaces[16][30][31][33]. This physical separation reinforces the cognitive separation from daily routines and constraints.

Safe-to-fail environment: The game-based format explicitly frames activities as experiments where failure is learning rather than career risk[17][21][25][35]. This psychological safety enables experimentation with new facilitation techniques, leadership behaviors, communication patterns, and collaborative approaches.

Economic separation: The non-profit model and minimal ticket prices reduce financial pressures. This allows for more freedom in experimentation. It avoids pushing toward commercially popular but less experimental formats[16][17][21]. Organizers can optimize for learning rather than revenue.

Cultural separation: The playful, informal culture of #play14 contrasts deliberately with formal corporate or academic cultures[17][21][25][35]. This cultural difference provides freedom to try behaviors, such as physical games, improvisation, and vulnerability. These behaviors might be judged inappropriate in more formal contexts.

The separated nature of #play14 creates what organizational learning theory calls “practice fields.” These are safe spaces where people can develop skills. They can also build mental models before applying them in high-stakes contexts[17][41]. Participants report taking games, facilitation techniques, and insights back to their organizations. These innovations are selectively assimilated into standard practice[17][22][25][28].

4.7 Assimilation: From Experiment to Practice

Assimilation in the AO Method refers to the selective adoption of successful experimental practices into standard operations[20][29]. While #play14 itself is an experiment relative to traditional conferences, it serves as an innovation source for participants’ home organizations:

Game transfer: Participants learn specific serious games at #play14. They subsequently use them in retrospectives, team-building sessions, leadership workshops, and change initiatives in their organizations[3][17][22][25][28]. The games collection website (play14.org/games) facilitates this knowledge transfer[3].

Facilitation pattern transfer: Beyond specific games. Participants absorb facilitation patterns such as marketplace formats, law of two feet, opening/closing circles, and participatory agenda-setting[17][22][35]. These patterns are adapted to local contexts, creating hybrid formats that blend unconference and conventional meeting structures.

Cultural pattern transfer: The #play14 culture of playfulness, psychological safety, and peer learning influences how participants approach their professional practice[17][21][25][35]. Multiple blog posts describe shifts in mindset and behavior that participants attribute to #play14 experiences.

Network effects: Connections formed at #play14 create ongoing communities of practice that continue learning and experimentation beyond individual events[1][16][33]. These networks accelerate diffusion of innovations across organizations and geographies.

The assimilation dynamic demonstrates how #play14 functions not merely as an end in itself. It also serves as a catalyst for broader organizational change. It is a “change laboratory” that generates innovations. These innovations are subsequently adopted by organizations. These organizations would never implement a full unconference internally. However, they can incorporate specific elements[17][22][28].

5. Discussion

5.1 Theoretical Implications

Our analysis reveals several insights relevant to organizational agility theory and organizational design.

Agility as emergent property, not installed capability: Unlike most agility research. These studies examine transformation from traditional to agile structures[40][42][46]. #play14 shows agility as an emergent property of organizational design choices. The combination of clear purpose, minimal structure, simple rules, and voluntary participation creates inherent adaptability. This suggests that designing for agility from inception may be more effective than transforming existing bureaucracies.

Minimal viable organization: #play14 represents an extreme point on the spectrum of organizational minimalism. It challenges assumptions about how much structure is necessary for coordination at scale. A platform, a plexus, and simple rules work together. Voluntary participation also helps to coordinate hundreds of people across multiple days and diverse activities. This empirically grounds theoretical claims about self-organization and distributed coordination[44][47][51][54].

Structure versus organization: Our case illustrates Beer’s distinction. Organizational structure is the designed container. Organization is the emergent pattern of interactions [51][54][56]. #play14’s structure is extremely light, yet its organization—the patterns of collaboration, learning, and innovation—is rich and complex. This inversion of the traditional relationship (heavy structure producing constrained organization) suggests alternative design strategies.

Coherence mechanisms at scale: The case demonstrates how coherence without hierarchy can operate at substantial scale. #play14 maintains coherence across dozens of independent events worldwide. It achieves this with clear purpose, explicit values, self-selection, and simple rules. This challenges assumptions that coordination at scale requires hierarchical management[44][47][51][54].

Play as organizational R&D: The analysis presents serious games differently. They are not just training tools. Instead, they serve as research and development infrastructure for organizational design. Games compress experience, make system dynamics visible, and enable safe experimentation with social patterns. This repositions play from a pedagogical tool to a strategic organizational capability.

5.2 Practical Implications

The #play14 case offers several lessons for organizational designers and change practitioners.

Pattern library for agile transformation: Each element of #play14 can be extracted as a design pattern applicable in other contexts. The marketplace format, law of two feet, plexus role definition, and simple rules can be adapted to product development. They can also be used in strategic planning, community building, and problem-solving initiatives[29][32]. Practitioners need not implement entire unconferences to benefit from these patterns.

Diagnostic framework: The AO mapping provides a diagnostic lens for assessing existing organizational structures. Practitioners can identify where their organizations are over-structured by comparing current designs to the #play14 exemplar. They can also find areas that are under-purposeful or burdened with unnecessary complexity. The contrast makes hidden design assumptions visible.

Minimum viable transformation: For organizations attempting agile transformation, #play14 demonstrates a minimalist approach. Organizations might achieve more agility through purposeful subtraction. This involves removing constraints, simplifying rules, and trusting emergence rather than comprehensive process redesigns and role redefinition. The avoidance principle becomes a transformation strategy.

Experimental infrastructure: Organizations can establish #play14-inspired internal unconferences as bounded experimental spaces. These separated environments enable safe exploration of new collaboration patterns, leadership behaviors, and decision-making processes. Successful patterns can then be selectively assimilated into standard operations[29].

Alternative to training: The serious games approach offers an alternative to traditional training programs. Games integrate learning and action. They compress time to consequence. This creates embodied understanding instead of classroom instruction followed by workplace application. This has implications for leadership development, team building, and change management interventions[41][43][45].

5.3 Connections to Broader Agility Literature

Our findings connect to several streams in the organizational agility literature.

Dynamic capabilities: Teece et al.’s dynamic capabilities framework emphasizes sensing, seizing, and transforming as core capabilities for sustained competitive advantage[53]. #play14’s structure enables all three. The marketplace and law of two feet create continuous sensing of participant interests and energy. The simple rules enable rapid seizing of opportunities through swarm formation. The experimental nature enables continuous transformation through assimilation of successful patterns.

Surface area maximization: Worley and Lawler describe agile organizations as maximizing “surface area.” This is the extent to which employees have direct contact with relevant environments[44]. In #play14, every participant is simultaneously on the surface. They propose sessions, facilitate games, and make decisions. They are not insulated by hierarchical layers. This total surface area exposure creates maximal information flow and rapid adaptation.

Ambidexterity: Organizational ambidexterity theory examines how organizations balance exploitation of existing capabilities with exploration of new possibilities[53]. #play14 is almost entirely oriented toward exploration, making it an extreme case that illuminates exploration dynamics. The assimilation pattern reveals a connection between exploration in #play14 and exploitation in participants’ home organizations. This suggests that ambidexterity can be achieved through separation and selective integration. It is a different approach compared to simultaneous within-organization balancing.

Complexity leadership: Uhl-Bien and Arena’s complexity leadership theory distinguishes between two types of leadership. Administrative leadership maintains stability and efficiency. Adaptive leadership enables emergence and innovation[47]. The #play14 plexus performs minimal administrative leadership while creating maximal conditions for adaptive leadership to emerge from any participant. This demonstrates that organizations can be designed to elevate adaptive over administrative leadership.

5.4 Limitations and Boundary Conditions

Several factors limit the generalizability of our findings.

Voluntary participation: #play14 depends entirely on voluntary participation. Participants choose to attend and can leave at any time. This self-selection creates high baseline motivation and alignment that cannot be assumed in employment contexts where participation is not optional. Organizations cannot simply mandate unconference attendance and expect equivalent outcomes.

Temporal boundedness: #play14 events are 2–3 days. This limited duration creates intensity and focus that may be difficult to sustain in ongoing operations. The patterns may work precisely because they are temporary. Permanent organizations face different coordination challenges. These include resource allocation, career development, performance management, and longer-term strategy. These are areas that #play14 does not address.

Task nature: The learning and networking tasks central to #play14 may be particularly amenable to unconference formats. Production tasks requiring sustained coordination, specialized equipment, or tight interdependencies might not fit the model as well. The generalizability of #play14 patterns likely varies with task characteristics.

Scale limits: #play14 operates at a substantial scale. It involves 50–200 participants per event. However, it has not been tested at much larger scales. Network effects and coordination complexity may increase non-linearly beyond certain size thresholds, potentially requiring additional structure.

Cultural context: #play14 attracts participants already oriented toward agile values, serious games, and experiential learning. The model may not work with populations skeptical of play or preferring more structured formats. Cultural fit is likely a significant moderating variable.

These limitations suggest that #play14 represents a particular organizational form suitable for specific contexts rather than a universal model. Its value lies less in direct replication than in revealing design possibilities and challenging assumptions about necessary organizational complexity.

6. Conclusion

#play14 is a global unconference network focused on serious games. This paper has shown that it instantiates core patterns of the Agile Organization Method. These patterns include platform, plexus, and swarms. Additionally, coherence through purpose and simple rules is established. There is a deliberate avoidance of unnecessary structure. Separation for experimentation is practiced. Successful patterns are assimilated into practice. The case provides detailed empirical grounding for these abstract patterns. It contributes to organizational agility theory. Also, it offers practitioners concrete exemplars for implementing lightweight organizational designs.

Three primary contributions emerge from this analysis. First, we show that agility can be an intrinsic design property rather than an acquired transformation outcome. #play14 was not made agile through change programs; it is agile by design. This challenges the transformation-oriented framing dominant in agility literature and points toward alternative design-oriented approaches.

Second, we empirically demonstrate that minimal structure combined with clear purpose can coordinate complex collective activity at scale. Well-designed interaction rules also contribute to this coordination. #play14 achieves what many complex organizations struggle to achieve. It fosters high engagement, rapid adaptation, and continuous innovation. It also builds a strong community with a fraction of the structural apparatus. This suggests that many organizations are over-structured and under-purposed.

Third, we illustrate the value of serious games as organizational research and development infrastructure rather than merely training tools. Games enable compressed experience, system visibility, and safe experimentation that accelerate organizational learning and evolution.

Future research could usefully pursue several directions. Comparative analysis of multiple unconference formats would reveal which patterns are specific to #play14 versus general to unconference structures. Longitudinal studies would track how participants transfer #play14 patterns into their organizations. Such studies would illuminate assimilation dynamics. They would also identify enabling conditions and barriers. Experimental studies manipulating specific design elements (e.g., presence/absence of the law of two feet, marketplace frequency, session duration) would test causal relationships between design choices and outcomes. Finally, extension of the AO analytical framework to other organizational forms would build a broader pattern language for agility-oriented design.

Organizations face increasing pressure to achieve agility in turbulent environments. Examples like #play14 become valuable not as templates to copy. Instead, they serve as existence proofs of alternative organizational possibilities. #play14 shows that minimal structure, clear purpose, simple rules, and trust in emergence can generate effective collective action. It challenges prevailing assumptions. It also expands the design space available to organizational practitioners.

Acknowledgments

The author thanks the #play14 organizing teams across multiple countries. Their dedicated stewardship has maintained and evolved the unconference over many years. The author also appreciates the thousands of participants who contributed their games, insights, and energy. They have helped create the living laboratory analyzed in this paper.

References

[1] #play14. (2024). #play14 – play is the way. https://play14.org

[3] #play14. (2013). Games. https://play14.org/games

[16] #play14. (2023). About | Our format. https://play14.org/about/format

[17] Agile Reloaded. (2023). #PLAY14. The Serious Gaming Unconference. https://agilereloaded.com/play14-serious-gaming-unconference/

[19] ITnation. (2024). #play14 Luxembourg, are you ready to play? https://itnation.lu/news/play14-luxembourg-are-you-ready-to-play/

[20] Neis, P. E. (2019). Designing an agile Digital Enterprise. Agile Organization. https://agile-organization.com/2019/12/13/designing-an-agile-digital-enterprise/

[21] #play14. (2024). About | Our values. https://play14.org/about/values

[22] Marmelab. (2018). #play14 Luxembourg 2018: The Serious Games Conference. https://marmelab.com/blog/2018/04/12/play14.html

[25] Marmelab. (2017). Play14: Practicing Serious Games with Talented People Is Awesome. https://marmelab.com/blog/2017/03/27/play-14.html

[26] Agile Alliance. (2022). The New Normal – AO Concepts and Patterns of 21st Century Agile Organizations. https://agilealliance.org/resources/books/the-new-normal-ao-concepts-and-patterns-of-21-st-century-agile-organizations/

[28] Agile Reloaded. (2023). #Play14. L’unconference sul Serious Gaming. https://agilereloaded.it/play14-la-unconference-sul-seriour-gaming/

[29] Neis, P. E. (2026). Principles of the AO method. Agile Organization. https://agile-organization.com/2026/01/12/principles-of-the-ao-method/

[30] Sponsor My Event. (2014). #play14 – The first Serious Games gathering in Luxembourg. https://www.sponsormyevent.com/play14-the-first-serious-games-gathering-in-luxembourg-esch-sur-alzette

[31] Agile Gatherings. (2024). Play14 Singapore. https://agilegatherings.com/event/play14-singapore-2024/

[32] Neis, P. E. (2024). AO Swarm-4 A Practitioner’s Manual for Hypothesis-Driven Initiatives. Payhip. https://payhip.com/b/3adJC

[33] Helmerich, N. (2023). Dr. Nicole Helmerich’s Post [LinkedIn]. https://www.linkedin.com/posts/dr-nicole-helmerich_play14-play14-play14-activity-7080082102750203905-Dgx_

[35] Rached, E. (2018). PLAY14 … Learning can’t be more fun! [LinkedIn]. https://www.linkedin.com/pulse/play14-learning-cant-more-fun-elie-rached

[38] Roets, L., et al. (2024). Shifting mindsets from conference to (un)conference: A collaborative reflective perspective on conceptual disruption. Cristal, 12(SI1). https://journals.co.za/doi/pdf/10.14426/cristal.v12iSI1.2095

[39] Roets, L., et al. (2024). A collaborative reflective perspective on conceptual disruption. Cristal, 12(SI1). https://epubs.ac.za/index.php/cristal/article/download/2095/1573/4740

[40] Shafiee, S., et al. (2021). Organization Design in Motion: Designing an Organization for Agility. Design Conference Proceedings. https://orbit.dtu.dk/en/publications/organization-design-in-motion-designing-an-organization-for-agili

[41] Giannarakis, G., et al. (2023). Serious Games as an Organizational Learning Tool for Sustainable Innovations. Academy of Management Proceedings, 2023(1). https://doi.org/10.5465/AMPROC.2023.17088abstract

[42] Shafiee, S., et al. (2021). Organization Design in Motion: Designing an Organization for Agility [PDF]. https://backend.orbit.dtu.dk/ws/files/255813412/organization_design_in_motion_designing_an_organization_for_agility.pdf

[43] Dias, M. (2025). Serious Games in Online Corporate Training: Value Creation and Employee Engagement. International Journal of Management, Technology And Engineering, 15(12). https://www.murillodias.com/publicacoes/artigos/1765365322.pdf

[44] Worley, C. G., & Lawler, E. E. (2018). Agility and Organization Design: A Diagnostic Framework. USC Center for Effective Organizations. https://ceo.usc.edu/wp-content/uploads/2018/03/10_Agility_and_Org_Design.pdf

[45] Program-Ace. (2024). Play with Purpose: Exploring the Impact of Serious Games on Learning and Training [Whitepaper]. https://program-ace.com/whitepapers/impact-of-serious-games-on-learning-and-training.pdf

[46] Dikert, K., et al. (2021). Design of transformation initiatives implementing organisational agility. BMC Health Services Research, 21(408). https://doi.org/10.1186/s12913-021-06396-5

[47] Holbeche, L. (2025). A Framework for Organizational Agility and Performance. Journal of Applied Behavioral Science. https://doi.org/10.1177/00218863251329522

[48] Schuh, G., et al. (2020). A Systemic Framework for Organizational Agility [PDF]. IPMA World Congress. https://www.worldcongress-ipma.com/fileadmin/user_upload/Dokumente/Folien/vortrag4-paper107-practitioner-a-systemic-framework-fo

[49] Holsapple, C., & Li, X. (2008). Understanding Organizational Agility: A Work-Design Perspective [PDF]. NPS. https://nps.edu/documents/110704361/110754042/HolsappleLiICCRTS2008.pdf

[50] Shafiee, S., et al. (2021). Designing an Organization for Agility [PDF]. Cambridge Core. https://www.cambridge.org/core/services/aop-cambridge-core/content/view/28199BB46CE37CD0AFD2FAAC203B985C/S2732527X2100496Xa.pdf

[51] Witwam. (2022). Utilising the Viable System Model (VSM) for Organisation Design. https://www.witwam.com/utilising-the-viable-system-model-vsm-for-organisation-design

[52] Academia.edu. (2025). Open Space Technology Research Papers. https://www.academia.edu/Documents/in/Open_Space_Technology

[53] Worley, C. G., & Lawler, E. E. (2024). How Organization Agility Produces Sustained Performance [PDF]. USC Center for Effective Organizations. https://ceo.usc.edu/wp-content/uploads/2024/04/G24-01702.pdf

[54] Espinosa, A. (2023). Viable System Model: A theory for designing more responsive organizations. i2Insights. https://i2insights.org/2023/01/24/viable-system-model/

[55] Norris, R. D. (2000). A Grounded Theory Study On The Value Associated With Using Open Space Technology. Webster University. https://www.openspaceworld.org/files/tmnfiles/OSTResearch2000.htm

[56] Fractal Consulting. (n.d.). Modelling Organisations using The Viable System Model [PDF]. https://www.fractal-consulting.com/wp-content/uploads/Modelling-Organisations-using-the-Viable-System-Model.pdf

[57] Tierney, A., & Lanigan, J. (2015). Open Space Technology: An effective tool for consultation. SETU Research. https://research.setu.ie/en/publications/open-space-technology-an-effective-tool-for-consultation

[58] Wikipedia. (2005). Viable system model. https://en.wikipedia.org/wiki/Viable_system_model

[59] Open Space World. (n.d.). Academic Research on Open Space. https://openspaceworld.org/wp2/explore/open-space-research/

[60] Public Sector Network. (2024). Using the Viable System Model to Improve Government Operations. https://publicsectornetwork.com/insight/using-the-viable-system-model-to-improve-government-operations

Download PDF