information flow, interconnectedness, interdependencies, relationality, interactions -> enabling context-sensitive/dependent constraints
cadence, rhythm, gait -> enabling temporal constraints
Also see definition in Complexity Space Framework
- actors
- capabilities
- relationships
- Containers
- Differences
- Exchanges
- Communicate your logic
- Make change your default
- Top-down interventions, bottom-up emergence
- The permeating centrality of relationships between people and systems
- 3 critical dimensions of Fit (Drive,Differentiation,Stretch), Power (Concentration, Strength) and Time (Speed)
- Drive,Differentiation,Stretch, Concentration, Strength and Speed are elements of structural coupling
- Differentiation - 3 degrees of similarity or difference with others - herd, edge, individual
- Drive - 3 differential between leading or following others, through time - an actor shape, react and co-evolve with others
- Stretch - 5 types of change as a result of coupling - incremental, radical, disruptive, paradigm shift, confound
- Time - 3 differential in the rate of change relative to others - fast, slow, synchronised
- Time Enablers - Foresight, Change Rate, Cycle Time
- Strength - 3 differential in relevant resource and capability - stronger, weaker, balanced
- Concentration - 3 degree of focus of capabilities and resources - single, multiple, diffuse
- Power Enablers - Critical Mass, Agility
- Differentials drive Dynamics
- Authority
- Crusader - value-driven
Approach - what do a framework looks like that listens and adapts to stakeholders stories?
- Ongoing meaningful inquiry.
- Iterative evaluative questions that matter: What’s being developed? What’s emerging? How is it being judged? How should it be judged? Who is the judge? Based on what’s happening so far, what’s next? This means asking stakeholders, or complex adaptive agents, from all their different perspectives: what’s going on? How can we make it better? And importantly using language and a framework that engages and includes stakeholders, using their everyday language.
- Context: What are the objectives? What is the operating environment?
- Stakeholders: Identify them using using participatory stakeholder mapping techniques. what does success looks like to them? What objectives do they want to achieve?
- Situational analysis: Drawing on all the data available to us, including the stakeholders, ask: what is happening now? What needs to change? And how can we make that change? What’s going on that might prevent that change? How would we know if we’ve achieved our objectives? How will we monitor change and find out about barriers and unintended consequences?
- Interventions: How can we unlock the system forces to allow co-evolution to take effects resulting in desirable changes?
- Monitoring Loops: Who to assign monitoring responsibilities to capture data about change? How do we develop a series of ongoing evaluative questions to measure progress, to keep asking periodically and feed back into our monitoring loops? This monitoring data keeps feeding back into our program adaptation.
- Communication: We keep communicating with our broader stakeholders about what we’re doing and how it’s all going. Through that we identify more stakeholders that we can now include. We get their feedback, and that informs our ongoing adaptation.
- Unintended consequences: As the broader stakeholders tell us about unintended consequences, and we learn and we adapt. And we can capture all this data and provide an evidence based argument to why the program has changed.
- Evaluation: On the basis of realistic, contextually evolved objectives, we ask our evaluative questions