Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.

Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step.

Reference revision: b3d65291c1706b36ca91929d5018c7e24f5803f4e6a2c3ca522a904e5a32a181

# Solution Tree

Subgroups analyze a central issue by mapping its root causes to roots, consequences to branches, and viable solutions to fruit on a tree diagram. They then prioritize practical next steps.

**Time:** 45 minutes. UWT suggested duration; the source record omits an explicit time band.
**People:** 4 to 24. Subgroups of 3 to 6 people at separate tree posters or digital canvases (a single group of 4 to 6 when total attendance is small).

## Choose this exercise

**Purpose:** Map root causes and visible effects of a core problem to identify targeted, viable solutions.
**Use it when:** Use when a team faces a persistent issue and needs to separate root causes from symptoms before selecting corrective actions.
**Skip it when:** Skip when the core issue is undefined, when the group lacks mandate to address root causes, or during brief administrative check-ins.

## Materials and tools

- 1 large flipchart sheet or whiteboard per subgroup
- 1 marker pen per person
- Sticky notes in 3 colors (1 pad each of yellow, pink, green per subgroup)
- Masking tape for mounting posters

## Before participants arrive

1. Draft a clear, neutral problem statement before starting.
2. Draw a bare tree outline (roots, trunk, branches) on each poster sheet.
3. Distribute one set of colored sticky notes and markers to each subgroup table.

## Say this to open

Today we will map a problem as a tree. The trunk is the problem itself. The roots below are the causes feeding it. The branches above are the effects it creates. Finally, we will place solutions as fruit on the tree. Let's work in small groups to map each section step by step.

## How to run it

### 1. Define trunk and post roots (10 minutes)

Introduce the session using the opening script. Subgroups write the central problem on the trunk. Each person writes causes on yellow sticky notes, addressing: 'What causes this problem?' Members may post their notes along the roots or keep private notes. The subgroup groups related root causes.

### 2. Map branch effects (10 minutes)

Subgroups consider: 'What consequences does this problem create?' Willing participants write observed effects on pink sticky notes and place them along the branches above the trunk.

### 3. Attach solution fruit (15 minutes)

Subgroups address the mapped causes and effects: 'What actions can mitigate or resolve this problem?' Participants write concrete actions on green sticky notes and place them on the branches as fruit.

### 4. Prioritize and debrief (10 minutes)

Each subgroup identifies up to two viable solutions from their poster. Invite one spokesperson per subgroup to share one solution with the whole room, up to four total contributions.


## Debrief questions

- Which root cause generated the most practical solution?
- Did any proposed solutions address symptoms in the branches rather than roots below?
- What is one concrete first action the team can start this week?

**Finished output:** Subgroup visual tree posters displaying grouped causes, observable effects, and prioritized green solution notes.

## Remote

Set up a digital whiteboard with a pre-drawn tree template for each breakout room. Subgroups work in breakout rooms of 3 to 6. Use distinct sticky note colors for causes, effects, and solution fruits. Return to the main call room to share screens during debrief.

## Hybrid

In-person subgroups work on their own physical posters while remote members join a video breakout group using a shared digital canvas. In the debrief, display the remote canvas on the room screen and direct a room camera toward physical posters.

## Access and participation choices

- Provide sticky notes in distinct shapes or textual labels in addition to colors to support color vision differences.
- Participants may choose to write notes, speak ideas to a peer scribe, or observe without speaking or posting notes. Individual contributions are optional, and participants may keep their personal notes private.

## If the session gets stuck

**Participants propose solutions that only address branch symptoms rather than roots.**

Ask the group which root cause their solution changes. If none, ask what action would reduce the cause lower down.

**Groups spend excessive time arguing over the problem definition.**

Provide a pre-approved, concrete problem statement during setup so the group focuses immediately on causes and actions.


## Terms used here

- Root cause: An underlying condition or factor that directly produces the central problem.

## Sources and adaptation

Observed in Participatory Methods library documentation.

Retained the defining mechanic of mapping causes to roots, central problem to trunk, effects to branches, and solutions to fruit. UWT supplied the 45-minute pacing, color-coded sticky note allocation, small-group structure, access choices, and debrief sequence, as the source text lacked timing and grouping specifics.

[Participatory Methods](https://participatorymethods.com/activities/solution-tree/)

Current run sheet: https://unitedwetransform.com/exercises/solution-tree/