wiki content export 2026-05-07

content/wiki/cooperative-foundations/peer-support-playbook/session-guides/session-4-decision-making-in-practice.md

@@ -16,7 +16,7 @@ Studios explore cooperative decision-making frameworks (consensus, consent, majo
 
 
 :::tip
-**Homework assigned:** practice one decision-making framework on a real decision, map current role distribution, complete the Informal Hierarchy Check-In as a studio, and notice where decisions happen this week.
+Solo reflection covers: picking a decision-making framework and a real decision to bring to the PS meeting, and initial reactions to the Informal Hierarchy Check-In.
 
 :::
 
@@ -42,15 +42,17 @@ Studios explore cooperative decision-making frameworks (consensus, consent, majo
 
 ### **👆 Before the session**
 
-* Know which decision-making framework the studio chose to practice
-* Have a small, real decision ready in case the studio can't think of one (e.g., "What should your next team social activity be?" or "How should you structure your next sprint?")
+* Check the studio channel for their framework and decision picks from the Session 4 solo reflection. If the studio has already settled on one of each, you're all set. If they posted different picks or haven't consolidated yet, you'll sort that out in the first few minutes of the meeting.
+* Have a small, real decision ready as a backup (e.g., "What should your next team social activity be?" or "How should you structure your next sprint?") in case they don't have one.
 * Review the 5 Informal Hierarchy Check-In questions so you can facilitate them smoothly
 
 ### **🌊 Session flow**
 
 #### **Check-in (5 min)**
 
-"What did you notice in the facilitation rotation? What was harder than expected – facilitating, participating, or observing?"
+**"What did you notice in the facilitation rotation? What was harder than expected - facilitating, participating, or observing?"**
+
+If the studio hasn't decided on a framework and decision yet, take a couple of minutes here to sort that out. Have each person share what they posted in the channel and pick one framework and one decision together. If they can't settle on a decision within, use your backup.
 
 #### **Practice a decision-making framework (20-25 min)**
 
@@ -95,13 +97,13 @@ Capture observations – they'll bring these to Session 5.
 #### **Close (5 min)**
 
 * "What's one pattern you noticed that you want to keep an eye on?"
-* Remind them to notice where decisions happen this week (in meetings? DMs? Slack? who's present?)
+* Remind them to notice where decisions happen this week (in meetings? DMs? Slack? who's present?) and to map their current role distribution before Session 5
 
 ### 👉 **Also this week**
 
 #### **Map your current role distribution**
 
-This can be done async or as part of the PS meeting if there's time. The question is simple: for each role/responsibility in the studio, where did it come from – explicit decision or implicit default?
+This is async work for the studio to do on their own this week, separate from the PS meeting. It feeds directly into Session 5's governance work.
 
 Prompts:
 

content/wiki/cooperative-foundations/session-content/session-4-decision-making-in-practice.md

@@ -24,9 +24,9 @@ This session is about noticing your *current* patterns and practicing alternativ
 
 ---
 
-## Check-in - 10 min
+## Check-in - ==5 min==
 
-Last session you practiced Layers of Effect on a decision. What did you notice when you tried to connect your values to a specific decision? Was it easier or harder than expected?
+==Last session you worked with Why/What/How, and you practiced Layers of Effect with your Peer Supports. What did you notice when you tried to connect your values to a specific decision? Was it easier or harder than expected?==
 
 
 ---
@@ -41,7 +41,7 @@ But before we look at different methods for decision-making, let's talk about **
 
 In traditional structures, only managers can put items on meeting agendas. Only certain people can say "we need to decide this." Everyone else has to hope someone with authority notices the problem.
 
-In a cooperative, **anyone affected by an issue** can bring it to the group. But we need systems so important things don't get los\*t and small things don't overwhelm us.
+In a cooperative, **anyone affected by an issue** can bring it to the group. But we need systems so important things don't get lost and small things don't overwhelm us.
 
 **Activity: Private journaling (3 min)**
 
@@ -350,22 +350,39 @@ Rotate roles every 3 minutes.
 
 ---
 
-## Closing - 2 min
+### ==Solo reflection - 10 min==
 
-You've practiced frameworks and started noticing patterns – who speaks, who defers, whose defaults became the group's. These patterns *are* your governance, whether you've named it or not.
+==Capture your own thoughts from today privately. One sentence per question is fine. You'll bring these notes to your Peer Support session this week and decide what to share.==
 
-Next session, we'll look at formal structures: How do you design governance that supports the decision-making practices you want and addresses the dynamics you noticed?
+==\[Back in the main huddle, mics off.\]==
+
+==Processing today's session:==
+
+* ==What did you notice about yourself during the facilitation rotation? Or what was harder than expected?==
+* ==Did any of the Informal Hierarchy Check-In questions hit close to home?==
+
+==Prep for your studio support meeting:==
+
+* ==Pick one decision-making framework you want to try with your PS this week. Write down why that one.==
+* ==What's a real decision your studio== 
 
 
 ---
 
-## Homework - 3 min
+### ==Closing - 3 min==
 
+==You've just done your Studio Support Meeting prep! Wahoo! Bring your solo notes to your PS session this week. You'll practice your chosen framework on a real decision and work through the full Informal Hierarchy Check-In together.==
 
-1. **Practice one decision-making framework on a real decision** – Try consent or consensus on something that actually matters, even if it's small.
-2. **Map your current role distribution** – Where did each role assignment come from: Explicit decision, or implicit default?
-3. **Complete the Informal Hierarchy Check-In as a studio** – Work through the 5 questions together. Bring your observations to Session 5.
-4. **Notice this week: where do decisions happen?** – In meetings? DMs? Who's present?
+==These patterns (who speaks, who defers, whose defaults became the group's) *are* your governance. Next session, we'll look at formal structures that support the decision-making practices you want and address the dynamics you noticed.==
+
+*==After this meeting, post your framework and decision picks in your studio channel. Your studio will need to choose one of each before your PS meeting.==*
 
 
 ---
+
+### ==Weekly exercises==
+
+
+1. ==Studio support meeting with your Peer Supports - you'll practice a decision-making framework on a real decision and work through the Informal Hierarchy Check-In together. Bring your solo reflection notes.==
+2. ==Map your current role distribution - for each role/responsibility in the studio, where did it come from: explicit decision, or implicit default? This can be async. It feeds directly into Session 5.==
+3. ==This week, pay attention to where decisions happen: In meetings? DMs? Who's present?==