Export script pulls all Outline documents via API and writes them as flat markdown files to content/wiki/ with frontmatter metadata. Cron wrapper auto-commits changes daily.
113 lines
3.4 KiB
Markdown
113 lines
3.4 KiB
Markdown
---
|
|
title: Values Mapping
|
|
collection: Cooperative Foundations
|
|
path: Cooperative Foundations/Peer Support Playbook/Values Mapping
|
|
parentDocument: Peer Support Playbook
|
|
outlineId: fcba1d09-2356-4d69-9995-f512847ac552
|
|
updatedAt: '2026-03-03T12:42:15.702Z'
|
|
createdBy: Jennie R.F.
|
|
---
|
|
When: Between Session 1 and Session 2
|
|
|
|
Duration: 45-60 minutes
|
|
|
|
Materials: Shared Miro board (template provided), 7 Principles reference
|
|
|
|
\nThis session helps the studio identify individual values and see where they align or diverge as a team. The goal is to notice rather than try to align everything.
|
|
|
|
If tension emerges, that's okay. Name it and move on.
|
|
|
|
## Before the session
|
|
|
|
* Confirm everyone completed their individual journaling (Session 1 homework)
|
|
* Ensure their studio Miro board has the template
|
|
* Have the 7 Principles visible (on the board or screen-shared)
|
|
|
|
|
|
---
|
|
|
|
### 1. Check-in
|
|
|
|
### 2. Individual sharing (15-20 min)
|
|
|
|
Each person shares 3-5 values from their individual reflection.
|
|
|
|
prompts:
|
|
|
|
* "What values came up when you did the journaling?"
|
|
* "You don't need to explain or justify"
|
|
|
|
As they share:
|
|
|
|
* Each person adds their values to the Miro board (stickies in their colour/section)
|
|
* No discussion yet - just capture
|
|
|
|
Watch for:
|
|
|
|
* Someone dominating or going first every time
|
|
* Someone staying quiet - invite them in gently
|
|
* Values that sound the same but might mean different things
|
|
|
|
### 3. Noticing patterns (10-15 min)
|
|
|
|
Now look at the board together.
|
|
|
|
Prompts:
|
|
|
|
* "What do you notice?"
|
|
* "Where do you see overlap?"
|
|
* "Any surprises?"
|
|
* "Are there values that seem similar but might mean different things to different people?"
|
|
|
|
Example to offer: "Transparency" - does it mean open documents? Open conversations? Both? Neither? What exactly is meant?
|
|
|
|
Let them discuss and keep it moving
|
|
|
|
### 4. Connecting to the 7 Principles (10 min)
|
|
|
|
Look at the ICA 7 Principles together. Also see [ICA Values Connections](/doc/91342338-8257-4550-be63-59f78d88dd75)
|
|
|
|
prompt:
|
|
|
|
* "do you see connections between your values and these principles?"
|
|
* "draw lines or group things if it helps."
|
|
|
|
This can be loosey goosey and don't let them fixate on making a beautiful diagram. the point is to see that their values connect to *a larger cooperative tradition*.
|
|
|
|
### 5. To bring back to Session 2 (5 min)
|
|
|
|
prom
|
|
|
|
* "what's one thing you learned about where your team aligns or diverges?"
|
|
* "you'll share this in session 2 - doesn't need to be polished."
|
|
|
|
Have someone write it down or capture it on the board.
|
|
|
|
### 6. Community agreements contribution (5 min)
|
|
|
|
"Based on this conversation, are there 1-2 values you'd propose adding to the cohort community agreements?"
|
|
|
|
Capture these to bring back to the full group.
|
|
|
|
|
|
---
|
|
|
|
## Tips
|
|
|
|
If someone dominates: "Let's hear from someone who hasn't shared yet."
|
|
|
|
If no one talks: "Take a minute to look at the board silently. What stands out?"
|
|
|
|
If tension emerges: "I'm hearing some different perspectives here. That's useful but we don't need to resolve it today."
|
|
|
|
If they want to debate definitions: "It's okay to mean different things. The goal is simply to notice where you might need to clarify later."
|
|
|
|
If time runs short: Prioritize steps 2-3 (sharing and noticing). The principles connection and agreements contribution can be done async if needed.
|
|
|
|
|
|
---
|
|
|
|
## After the session
|
|
|
|
* Note any tensions / surprises to mention in your Peer Support check-in
|
|
* Remind the team to bring their learnings to Session 2
|