Update curriculum source files to current versions
This commit is contained in:
parent
136ee2442b
commit
8549cb0252
20 changed files with 467 additions and 466 deletions
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
## Pre-session
|
||||
|
||||
If you are the presenting PS for this session, prep a **15–20 minute** case study from your studio covering:
|
||||
If you are the presenting PS for this session, prep a **15-20 minute** case study from your studio covering:
|
||||
|
||||
- How your studio makes decisions now
|
||||
- What you tried that didn't work
|
||||
|
|
@ -10,21 +10,19 @@ If you are the presenting PS for this session, prep a **15–20 minute** case st
|
|||
|
||||
## **What happens in session**
|
||||
|
||||
Studios learn about legal structures (sole prop, partnership, corporation, worker coop), governance models (collective governance, advice process, sociocratic circles, board + membership, DisCOs), and member management (adding, departing, removing members). A PS presenter shares a 15-20 minute case study on their studio's governance journey. The session introduces Community Rule as a tool for documenting governance in plain language. Key themes: making governance visible, designing structures from the patterns noticed in Session 4, and distinguishing between governance practice and legal incorporation.
|
||||
|
||||
|
||||
:::info
|
||||
If you are the presenting PS for this session, prepare a **15-20 minute case study** covering: how your studio makes decisions now, what you tried that didn't work, and one example of governance helping resolve a real issue. Be honest about the messy parts.
|
||||
|
||||
:::
|
||||
Studios learn about:
|
||||
- legal structures (sole prop, partnership, corporation, worker coop)
|
||||
- governance models (collective governance, advice process, sociocratic circles, board + membership, DisCOs)
|
||||
- member management (adding, departing, removing members)
|
||||
|
||||
A PS presenter shares a 15-20 minute case study on their studio's governance journey. We also introduce Community Rule as a tool for documenting governance in plain language. We focus on *making governance visible*, designing structures from the patterns noticed in Session 4, and distinguishing between governance practice and legal incorporation.
|
||||
|
||||
### :eyes: **Your role during session**
|
||||
|
||||
- If presenting: deliver your case study
|
||||
- Observe how your studio responds to the governance models — what resonates? What causes confusion or resistance?
|
||||
- Observe how your studio responds to the governance models – what resonates? What causes confusion or resistance?
|
||||
- Listen for whether they connect their Session 4 Informal Hierarchy Check-In observations to governance design choices
|
||||
- Note how they react to the member removal discussion — this is often where discomfort shows up
|
||||
- Note how they react to the member removal discussion. It's an uncomfortable topic.
|
||||
|
||||
|
||||
### 👆 **Your role after session**
|
||||
|
|
@ -38,14 +36,14 @@ If you are the presenting PS for this session, prepare a **15-20 minute case stu
|
|||
|
||||
### **📚 Materials**
|
||||
|
||||
- [Community Rule](https://communityrule.info/) tool (open in browser)
|
||||
- [Community Rule](https://communityrule.info/) tool
|
||||
- Studio's Informal Hierarchy Check-In observations from Session 4
|
||||
- Notes on which governance model(s) interested them
|
||||
|
||||
|
||||
### :world_map: **Context**
|
||||
|
||||
This is a working session. You're helping the studio start documenting their governance in plain language using Community Rule. They don't need to finish — the goal is to surface where they already have answers vs. where they need more conversation. This draft will evolve.
|
||||
This is a working session. You're helping the studio start documenting their governance in plain language using Community Rule. They don't need to finish – the goal is to surface where they already have answers vs. where they need more conversation. This will be a living document.
|
||||
|
||||
|
||||
### **👆 Before the session**
|
||||
|
|
@ -59,53 +57,39 @@ This is a working session. You're helping the studio start documenting their gov
|
|||
|
||||
#### **Check-in (5 min)**
|
||||
|
||||
"What governance model stuck with you from the session? Did anything click — or feel wrong?"
|
||||
"What governance model stuck with you from the session? Did anything click, or feel wrong?"
|
||||
|
||||
|
||||
#### **Community Rule walkthrough (10 min)**
|
||||
|
||||
Open the tool together. Walk through the fields it asks for:
|
||||
Open the tool together. Community Rule works as a modular builder – you assemble your governance from pre-made or custom building blocks.
|
||||
|
||||
- What is this community?
|
||||
- Who are the members? What qualifies someone for membership?
|
||||
- How are decisions made?
|
||||
- What roles exist?
|
||||
- How do you change these rules?
|
||||
Start with the basics: Name your studio and write a short summary of its structure.
|
||||
|
||||
Don't try to fill everything in right away. Start by identifying which fields the studio can answer easily vs. which ones need more discussion.
|
||||
Then explore the module library together. There are four categories:
|
||||
|
||||
- **Culture** – values, norms, purpose, solidarity, diversity
|
||||
- **Decision** – how decisions get made (lazy consensus, do-ocracy, vote, ranked choice, etc.)
|
||||
- **Process** – how policies are implemented and evolve (accountability process, delegation, transparency, dissolution, exclusion, etc.)
|
||||
- **Structure** – roles and internal entities (board, council, membership, ownership, roles, committee, etc.)
|
||||
|
||||
Drag in the modules that feel relevant. Each one can be configured with key-value pairs – for example, a "Membership" module might have configuration like "Eligibility: active worker-owners who have completed a 3-month trial period." You can also create custom modules for anything the library doesn't cover.
|
||||
|
||||
Don't try to build everything at once. Start by browsing the categories and noticing which modules the studio can configure easily vs. which ones lead to blank stares.
|
||||
|
||||
Prompts:
|
||||
|
||||
- "Where do you already have a clear answer?"
|
||||
- "Which of these are you already doing without naming it?"
|
||||
- "Where is there genuine disagreement or uncertainty?"
|
||||
- "Which of these have you been doing by default without naming it?"
|
||||
|
||||
- "What's missing from the library that's specific to how you work?"
|
||||
|
||||
#### **Draft together (20-25 min)**
|
||||
|
||||
Start filling in what you can. Focus on the fields where there's energy or alignment. When you hit a field where there's disagreement, note it and move on — don't try to resolve everything today.
|
||||
|
||||
**Key fields to prioritize:**
|
||||
|
||||
**Decision-making:** "Based on what you practiced in Session 4, what framework are you leaning toward for different types of decisions?"
|
||||
|
||||
- Major decisions (new members, large spending, creative direction shifts)
|
||||
- Day-to-day decisions (task assignment, meeting scheduling)
|
||||
- Emergency/time-sensitive decisions
|
||||
|
||||
**Roles:** "What roles do you actually need right now? Who's doing them? Was that decided or default?"
|
||||
|
||||
Connect back to their role distribution mapping from last week.
|
||||
|
||||
**Membership:** "This is the hard one. What happens when someone wants to join? When someone wants to leave? When someone needs to leave?"
|
||||
|
||||
- You don't need to resolve this today. Just surface where assumptions differ.
|
||||
- If they resist discussing removal: "I know this is uncomfortable. But having a process before you need it is a form of care."
|
||||
|
||||
Start filling in what you can. Focus on the modules where there's energy or alignment. When you hit a field where there's disagreement, note it and move on. Don't try to resolve everything today.
|
||||
|
||||
#### **Close and gaps list (5 min)**
|
||||
|
||||
- Make a list of fields that still need discussion
|
||||
- Make a list of areas that still need discussion
|
||||
- "What's the most important unresolved question?"
|
||||
- "Who's going to take a first pass at writing up what we decided today?"
|
||||
|
||||
|
|
@ -121,18 +105,18 @@ This is prep for Session 6 (Equitable Economics). Check in during the week:
|
|||
- "Has everyone spent some time thinking about the financial sustainability question?"
|
||||
- "And the personal reflection: what financial information have you never been allowed to see at work?"
|
||||
|
||||
These don't need to be discussed as a studio yet — just make sure individuals are reflecting.
|
||||
These don't need to be discussed as a studio yet – just make sure individuals are reflecting.
|
||||
|
||||
|
||||
### :star: **Tips**
|
||||
|
||||
If they want to pick a governance model immediately:
|
||||
|
||||
- "You don't have to commit today. Start with collective governance or advice process — you can add complexity as you learn what you actually need."
|
||||
- "You don't have to commit today. Start with collective governance or advice process – you can add complexity as you learn what you actually need."
|
||||
|
||||
If Community Rule feels bureaucratic:
|
||||
|
||||
- "Think of it as making the invisible visible. You're already doing governance — this just names it."
|
||||
- "You're already doing governance – this just helps you name it."
|
||||
|
||||
If they skip over membership/removal:
|
||||
|
||||
|
|
@ -142,23 +126,19 @@ If one person is doing all the talking about governance:
|
|||
|
||||
- "Governance designed by one person is just management with extra steps. Everyone needs to shape this."
|
||||
|
||||
If time runs short:
|
||||
|
||||
- Prioritize decision-making and roles. Membership can be returned to next week.
|
||||
|
||||
|
||||
### **🏁 After the session**
|
||||
|
||||
- Note where the studio has clear alignment vs. where they got stuck
|
||||
- Note any tension around membership/removal — these conversations will deepen
|
||||
- Note any tension around membership/removal – these conversations will deepen
|
||||
- Remind them about the financial sustainability reflection for Session 6 prep
|
||||
- Bring the draft status to your PS check-in
|
||||
|
||||
|
||||
## :triangular_flag_on_post: **Red flags to watch for**
|
||||
|
||||
- A studio that resists documenting anything — "we just know how we work" (that's exactly the problem)
|
||||
- A studio that resists documenting anything – "we just know how we work" (exactly the problem)
|
||||
- Governance designed around one person's strengths or preferences
|
||||
- Avoiding the membership/removal conversation entirely
|
||||
- Confusing governance with incorporation — "we're not a real coop yet so we don't need this"
|
||||
- Confusing governance with incorporation – "we're not a real coop yet so we don't need this"
|
||||
- A draft that looks perfect on paper but doesn't match how the studio actually operates
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue