Compassionate Systems Awareness Orchestrator

Orchestrate compassionate systems tools from issue or aspiration to wise action. Use when a class needs a complete inquiry workflow.

What it does

Sequences the compassionate systems awareness tools into a coherent teacher-usable workflow. The orchestrator makes pathway options visible before committing to a route, then helps the educator choose which tool to use first, what output should be passed forward, when to stop for evidence or safety, and how to move from systems understanding to wise action without collapsing into blame, vague empathy, or superficial projects.

Use this when the task is larger than one tool: a class wants to understand a recurring issue, design a desired culture, investigate a local system, or plan a regenerative/action project. The orchestrator should not duplicate the discrete skills. It coordinates them.

The evidence behind it

The workflow draws from the Center for Systems Awareness and Compassionate Systems Framework, combining the iceberg, mental models, reflective dialogue tools, and agency/action framing. It also uses systems-thinking principles from Senge and Meadows: behaviour emerges from structures and mental models, and effective action requires attention to leverage, feedback, and unintended consequences.

Sources

• Center for Systems Awareness (2022) — Compassionate Systems Framework and tools practitioner resources
• Senge (1990) — The Fifth Discipline (systems thinking and learning organisations)
• Meadows (2008) — Thinking in Systems (structures, feedback, leverage points)
• Argyris (1990) — Ladder of inference and defensive reasoning
• Covey (1989) — Circle of concern and influence as agency framing

How to use it in your lesson

For the best results with EvidenceLesson, give it:

• starting_point — The current issue, aspiration, place-based concern, project idea, or class culture focus
• context — Class, school, community, ecological, or curriculum context
• intended_use — Student lesson, teacher planning, project design, staff inquiry, or community action
• student_level (optional) — Age/year group
• available_time (optional) — Single lesson, sequence, project, staff meeting, or unit
• prior_evidence (optional) — Existing data, stories, observations, or student work
• safety_sensitivities (optional) — Conflict, trauma, identity, power, or safeguarding considerations

Known limitations

1. Cannot assess local conditions. This orchestrator coordinates tool selection but cannot replace teacher knowledge of specific students, classroom dynamics, community trauma history, or cultural protocols — pathway appropriateness depends entirely on local conditions the orchestrator cannot assess.
2. Not a feedback loop. The pathway is presented as a sequence, but classroom systems inquiry is recursive. In practice, a class may need to return to earlier tools as new evidence or conflict emerges. The orchestrator provides a starting map, not a dynamic workflow.
3. Degrades with vague starting points. "Improve classroom culture" is too broad to route effectively. The orchestrator works best when the starting point names a specific recurring issue or a clearly stated desired event.
4. Produces a plan, not the outputs. The orchestrator sequences the discrete tools but does not run them. Using this skill without then running each discrete tool produces only a pathway outline — not actual iceberg maps, mental model maps, or agency circles.

Before you deliver: a quick check

• [ ] The pathway begins with the right kind of iceberg or reflection tool.
• [ ] Each step has a handoff output.
• [ ] Stop/slow checks are explicit.
• [ ] Student agency is bounded and supported.
• [ ] Teacher/institutional responsibility is not hidden.
• [ ] The final output is practical enough for a real teacher to use.

Pairs well with