Meta Analysis is the team's practice of turning its own recorded calls into structured, developmental feedback. It runs weekly, and the corpus is now 26+ calls deep, covering team meetings, R&D sessions, client calls, and strategic reviews.
The format
Every analyzed call produces a ~2,000–2,200 word read (9–10 minutes) in three sections. The structure is deliberately timed to the reader's moment:
Section 1 — Immediate Post-Meeting Insights. Read right after the call, while memory is fresh. Covers: core narrative (3–4 sentences), each participant's intent, topics with time allocation, speaking dynamics (who dominated, turn-taking quality), and emotional trajectory.
Section 2 — Preparation for Next Meeting. Read before the next call. Covers: what was missed, concrete action items with owners, prep items, next agenda, and process improvements.
Section 3 — Theoretical Framework (optional depth). A single school of thought — psychological, sociological, philosophical, or art-theoretical — applied as a lens. 2–3 key concepts, their application to this specific call, and a predictive insight.
Full prompt: Meta Analysis prompt
Why three sections
The sections separate by reading context, not by priority. Section 1 is for the participant who just hung up. Section 2 is for the organizer sitting down to plan. Section 3 is for anyone willing to go deeper — and it's where the corpus builds pattern recognition over time.
The Theoretical Framework section is what makes the corpus more than a meeting log. A call becomes not just "here's what we discussed" but "here's what was happening developmentally."
What the corpus has surfaced
Across the 26+ analyzed calls, a few durable patterns:
Three developmental stages operating simultaneously in a single hour-long product call — Stage 5 (Identity) in what we were building, Stage 6 (Intimacy) in how we collaborated, Stage 7 (Generativity) in our dominant drive. The tension between them explained why a "simple marketing discussion" felt difficult. See: Understanding Team Dynamics Through Erikson's Developmental Stages.
The AoD vs MCC distinction emerged from analyzing a single session. What looked like a "good coaching call" turned out to be methodologically different from classical MCC — and naming the difference gave the team a durable vocabulary. See: The Art of Dialogue vs classical MCC coaching.
Tempo drift. A recurring failure mode: the team starts in AoD (presence, humor, co-seeing) and drifts into analysis/structure before the field has fully formed. The countermeasure synthesized across several calls: protect the first third of the session as pure AoD, bring AI in only after 20–30 minutes as a mirror for what already happened — never as an agenda-setter.
Synthesized guidance: Recommendations to Maha from AI — cross-referenced to the specific calls each recommendation came from.
Open questions the team is working through
From the Meta Analysis root page:
- Personalization: each participant should get "their own" summary, filtered through the roles and values relevant to them — not one shared summary.
- Portability vs. memory: a memoryless document is defensible and shareable; a persistent memory is a tactical instrument, better for intervention, worse for circulation. The team is choosing deliberately.
- Measurement: how many minutes in a reflective journal is the right dose? Which signal captures usefulness — accuracy, utility, supportive-ness?
Structure
Root page: Meta Analysis. Core deliverables: Prompt, 3-sessions analysis, Recommendations, Erikson stages essay, Art of Dialogue comparison. The Calls sub-database holds the individual call analyses (A Session Only For You, Being WITH AI, Strategic Identity & Process Validation, Vortex Pill of Presence, Practicing the Value of Not-Knowing, and ~20 more).