The Ridgeline Learning Cycle: How learning moves into practice in complex systems
In many professional settings, learning is treated as an event.
A training is delivered.
A workshop is held.
Information is shared.
Sometimes these experiences are engaging and well designed. But even when participants leave energized, the impact often fades quickly once they return to their daily work.
This is not because people are resistant to learning. It is because complex systems rarely change through information alone.
In fields like public health, emergency management, and other coordination-heavy environments, the challenge is not simply understanding a concept. The challenge is translating that concept into judgment, coordination, and action within real-world constraints.
Meaningful learning in these contexts tends to follow a different rhythm.
At The Ridgeline Collective, we think of this rhythm as the Ridgeline Learning Cycle.
Rather than beginning with theory and moving toward application, the cycle begins with the reality of the work itself.
1-Situate: Begin in the reality of the work
Learning starts by situating participants in the context of their own practice.
Sometimes this means drawing directly from the experience of the room, asking professionals to describe how work actually unfolds in their setting. In other cases, it means presenting a realistic, localized scenario that reflects the complexity of their environment.
The goal is to surface the work as it is actually done, not just the way it is described in policies or manuals.
Starting here anchors the learning in lived experience rather than abstract instruction.
2-Inquire: Engage in shared sense-making
Once the reality of the work is on the table, the next step is inquiry.
Participants explore what happened, what assumptions were present, what emotions surfaced, and how different roles shaped the situation. One useful frame in this stage is the distinction between work as imagined—the way procedures or policies describe work—and work as done, the way it unfolds in practice.
Through structured dialogue and reflection, participants begin making sense of the situation together.
This stage is less about solving the problem immediately and more about developing a clearer shared understanding of it.
3-Reconcile: Compare context with concept
At this point, external concepts enter the conversation.
These might include formal policies, technical guidance, textbook approaches, or established frameworks. Rather than presenting these ideas as authoritative answers, they are used as a point of comparison.
Participants examine the relationship between the concept and their own context. Through structured discussion, they identify what elements of the external concept might be:
- Adopted directly
- Adapted to fit the local context
- Augmented with additional local tools, knowledge, or agreements
- Averted, where alternatives are more appropriate
This process allows teams to move beyond either blindly following external guidance or dismissing it entirely. Instead, they integrate it thoughtfully with their own experience.
4-Prototype: Test ideas in practice
Insights alone rarely change systems.
For that reason, the next step is prototyping.
Participants select one element from the reconciliation stage and place it into an experimental phase. This might involve a tabletop exercise, a simulation, a drill, or another structured practice environment.
The key is that the test is intentional. The group defines signals in advance—what they will look for to determine whether the idea is working or where it might need adjustment.
Prototyping turns conceptual agreement into practical experimentation.
5-Integrate: Embed learning in systems and identity
The final stage focuses on integration.
If the prototype reveals useful improvements, those insights must be embedded into the system. This may involve updates to governance structures, standard operating procedures, role descriptions, interagency agreements, or operational tools.
Integration also occurs at the level of professional identity. Individuals may pursue new credentials, coaching relationships, or reflective practices that reinforce the learning.
When both system structures and professional identities evolve together, the learning becomes durable.
A cycle, not a sequence
The Ridgeline Learning Cycle is not meant to occur once.
As professionals continue to work, new experiences emerge, new questions arise, and the cycle begins again: situating, inquiring, reconciling, prototyping, and integrating.
Over time, this rhythm strengthens the ability of individuals and institutions to learn directly from their own practice while remaining open to external knowledge.
In complex systems, this kind of learning is less about delivering answers and more about developing the capacity to navigate uncertainty with clarity and sound judgment.
That capacity is what ultimately allows systems to improve.
In our work with public health systems, emergency response teams, and multisector partnerships, we have seen this rhythm emerge repeatedly. The Ridgeline Learning Cycle simply names it.
When teams learn in this way—starting from experience, questioning assumptions, testing ideas, and embedding what works—learning becomes part of how the system evolves.