EcoHubs

Layer 5 · Operations

Meeting Template: Reflection & Learning

  • Layer: 5 — Operations & Coordination
  • Status: Stub — not yet adopted
  • RCOS reference: §7.2, §7.6
Why a quarterly retrospective?
Communities that don’t pause to learn repeat their failures with new vocabulary. Reflection & Learning is the structured pause — a cadence where experience becomes pattern, pattern becomes Learning Log entry, and learning becomes future proposal. Without it, the Learning Log (Layer 6) stays empty and the framework stops evolving.

Meeting Type: Reflection & Learning

RCOS definition7.2.1, 7.2.2, 7.2.3, 7.6.4
  • 7.2.1 The community MUST define explicit meeting types sufficient to support:
  • 7.2.2 Each meeting type MUST define, at minimum:
  • 7.2.3 Meetings MUST NOT exceed their declared decision scope or bypass authority boundaries defined in Layer 2.
  • 7.6.4 Meeting Templates MUST define, at minimum:

Read 7.2 Meeting System in the RCOS spec ↗

Why give reflection its own meeting type?
Reflection that happens only when time allows never happens. A named meeting type with a quarterly cadence makes space for looking back — and keeps retrospection from getting squeezed out by operational urgency.
  • Purpose: Review recent experience, surface patterns, capture learnings, and feed insights back into the RCOS framework and community practice
  • Decision scope: May produce proposals for change; no direct decision authority unless specified in the Decision Matrix
  • Required participants: All Full Members invited
  • Optional participants: —
  • Cadence: Quarterly
  • Duration limit: 90 minutes maximum
  • Facilitation: Facilitator role holder

Agenda Structure

Why separate what worked from what didn't?
If both are discussed together, failures dominate and successes get underweighted — or the reverse, if the group is conflict-averse. Separating the two ensures both patterns get named, and that the Learning Log captures a full picture rather than just grievances.
  1. Check-in (10 min) — one word or sentence from each participant; how are you arriving?
  2. Review period highlights (15 min) — what has the community done and experienced since the last reflection meeting?
  3. What worked well (15 min) — patterns of success worth reinforcing or documenting
  4. What didn’t work / what we’d do differently (15 min) — failures, friction, near-misses; no blame, focus on patterns and systems
  5. Learnings to carry forward (15 min) — insights to capture in the Learning Log (Layer 6); Blueprint Steward notes items for framework consideration
  6. Updates to learning log and future proposals (15 min) — Blueprint Steward records learning log entries; any items that should become a future proposal are added to resources/future-proposals.md
  7. Check-out (5 min) — one word or sentence from each participant

Notes and Records

  • Date:
  • Facilitator:
  • Attendees:
  • Notes: [Summary posted to Discord after the meeting]
  • Learning Log entries triggered: [List or “none” — Blueprint Steward updates layers/6-evolution/03-learning-log.md]
  • Future proposals added: [Links or titles, or “none”]

← Back to Operations