Lesson 1: Village case study template

Use this as a copy/paste report format inside the Space (and optionally as a Notion template).

A) Case Study Title

Village Case Study | VillageName | PilotStartDate–PilotEndDate

---

B) Snapshot (readable in 30 seconds)

Village / Node name: People count: (active participants / total community) Launch phase: Pilot / Days 15–45 / Days 46–90 / Mature Domains active: (list) Steward roles staffed: Circle Steward / Exchange Steward / Care Steward / Admin Coordinator / Tools Steward / Domain Stewards VT360 status: Installed / Partially installed / Stable / Needs repair Biggest win (one sentence): Biggest friction (one sentence):

---

C) What you actually did (no fluff)

Onboarding path used: (Orientation only / Full course / Custom) Request intake method: (VT360 form/page/button used?) Matching method: (centralized Exchange Steward / Domain Steward matching) Closure method: (daily sweep / weekly sweep / mixed) PulseChecks used: Yes / No (frequency) Contribution logging used: Yes / No (how)

---

D) Metrics (Week 1 and Week 2 minimum)

Week 1

• Requests submitted:
• Requests triaged within 24h:
• Matches confirmed:
• Matches completed:
• Closure rate: (Completed + Closed / Total)
• NeedsInfo rate: (NeedsInfo / Total)
• Overload signals:

Week 2

• Requests submitted:
• Matches completed:
• Closure rate:
• Overload signals:

Optional (Day 30 / Day 90)

• Active participants weekly:
• Domains paused events:
• Repeat overgiver pattern detected: Yes / No

---

E) What worked (be specific)

List 3–7 bullets. Examples:

• “Micro-asks (≤30 min) doubled completion rate.”
• “Posting a VT360 shortcut link reduced feed requests by 80%.”
• “Daily closure sweep prevented resentment.”

---

F) What broke (and what you changed)

Break #1:

• Symptom:
• Root cause (your best guess):
• Fix applied:
• Result:

Repeat 2–3 times.

---

G) Week 3–6 risk status (the danger window)

Check the ones that showed up:

• Feed drift (operations happening in Mighty)
• Scope creep
• Overgivers taking over
• Emotional requests hijacking ops
• Steward burnout
• Fairness stories
• Tools drama

Early catch actions taken: What you’d do earlier next time:

---

H) Policy changes (if any)

List any policy cards you adopted or edited:

• No Scope Creep
• Closure Required
• Privacy Boundaries
• Domain pausing rules
• High emotional load routing rules

---

I) Upgrades requested (what you want next)

Choose up to 3:

• Better onboarding
• Better steward scripts
• Better dashboard views
• Better automations
• Better domain capacity design
• Inter-village learning support
• Regional corridor exploration (later)

---

J) One recommendation to new villages (one paragraph)

Write it like a human talking to a human.