You've seen the product, the methodology, and the market. This last lesson is about how the team actually works — because the practice behind the product is as important as the product itself. And it ends with concrete next steps if you want to go further.
The Meta Analysis loop
Every week, the team analyzes a recorded call through the lens of developmental psychology. Not summarizes — analyzes. The output is a ~2,000-word read in three sections, deliberately timed to the reader's moment:
- Immediate Post-Meeting Insights — read right after the call. Participant intents, speaking dynamics, emotional trajectory, core narrative.
- Preparation for Next Meeting — read before the next call. What was missed, action items, prep, process adjustments.
- Theoretical Framework (optional depth) — a single school of thought applied as a lens. 2–3 concepts from the framework, how they illuminate this call, what they predict.
Over ~26 analyzed calls, patterns emerge:
- Three developmental stages operating simultaneously in a single hour-long product call. Identity (what we're building), Intimacy (how we collaborated), Generativity (our dominant drive). The tension between them explained why a "simple marketing discussion" felt difficult.
- The AoD vs MCC distinction emerged from analyzing a single session. Naming the difference gave the team a durable vocabulary.
- Tempo drift. A recurring failure mode: start in presence, drift into analysis too early. The countermeasure, synthesized across several calls: protect the first third of the session as pure AoD, bring AI in only as a mirror after 20–30 minutes — never as agenda-setter.
The practice is the feedback loop. The team improves not because someone writes a better handbook, but because last week's call becomes next week's method.
What the practice produced in April
The previous lesson — on go-to-market — was rewritten because of one specific session. On April 16, 2026, a strategic review ran through the Meta Analysis loop alongside two working prototypes. The output of that single session:
- The compliance product direction was parked. Commodity territory, wrong fit for the team.
- The thesis was reframed from "training tool for defined workflows" to "AI on real conversations in defined systems." Zurich stopped being the whole bet and became a template.
- Two live motions were named and separated — Live Companion (real-time) and Agent-based modeling — with their respective pulls made explicit: investor validation on one side, near-term revenue on the other.
- The tension between them was left unresolved on purpose. The practice prefers naming a live tension over collapsing it prematurely.
None of that was on a roadmap before the session. It fell out of running real conversations through the loop and being honest about what they revealed. The lesson you just read is the artifact.
The workflows database
Alongside Meta Analysis is the Workflows database — 60+ lightweight cards tracking everything from a single sales call to a multi-quarter research initiative. Each card is small on purpose (a person, a stage, a tag, sometimes a checklist) and most link to a Google Drive or a full sub-page where the real content lives.
The cards are grouped loosely by theme: Sales & Pilots (Zurich, CoachHub, Konvekta), Product R&D (MVP 0.4 matchmaking, Career Chat 0.4, AI facilitator), Research (CoachHub AIMY, Public Sector Recruiting, Jung's archetype expert), Events (AI Spark Meetup, webinars), the Ukraine track (Bureviy, Diaspora Youth, Volo4Ukraine), and Operations.
The database isn't trying to be a project management system. It's a shared pointer layer that answers who owns this, what stage, what's next — for everything else, follow the link.
Principles that shaped the practice
Three commitments are explicit — worth naming because they're often implicit in other teams:
Portable, defensible documents over tactical memory. The Meta Analysis outputs are designed to be circulated — which means memoryless AI, no persistent state about participants. Memory would give more tactical power (better interventions inside a session) but less circulation (harder to share without privacy questions). The team chose portability.
Protect emergence before structure. The first third of a session is reserved for presence and co-seeing. Frameworks and lists come after the relational field has formed. This is a direct AoD principle, and it shapes everything from team meetings to user sessions in the product.
Name live tensions; don't collapse them. The April 16 session produced a clear thesis and a clear unresolved decision (Live Companion vs. modeling). The practice resisted manufacturing a fake answer. A named tension is a better artifact than a premature decision, because it keeps the next session useful.
What to do next
Depending on who you are, a different door opens here:
- Investor or partner? Start with the Strategy summary and the go-to-market lesson you just finished. Then the Exec Summary for Investors for the full pitch. The two motions (Live Companion, Agent-based modeling) both have working prototypes — ask to see either.
- HR leader evaluating RAIner? The HR Customer Journey walks through a week in HR with and without the product. The HR Lean Canvas covers pricing and implementation shape. Then reach out for a pilot conversation.
- Coach evaluating the tool? Start with The Future of Coaching, then the Coaching Lean Canvas.
- Lobbyist, strategist, or consultant curious about agent-based modeling? Ask for a walkthrough — this motion is actively taking pilots (EU directive lobbying, leadership cross-assessment, difficult-conversation rehearsal).
- Running meetings and wondering about Live Companion? The Live Companion product card is the quickest read; a demo is available on request.
- Collaborator or new team member? The Methodology summary and Meta Analysis summary are the substrate. Then browse the Workflows index to see what's currently in motion.
- Just curious? The full raw archive is the Internal Wiki — ~185 pages, messy, alive. Start anywhere; follow what catches your attention.
Finishing the course
You've now seen:
- Why we bet on real conversations over scripted ones.
- How RAIner turns a 20-minute dialogue into a growth trajectory.
- The developmental lens (Kegan, AoD) behind it.
- The thesis — AI on real conversations in defined systems — and the two live product motions competing for focus inside it.
- The weekly practice that keeps the method honest, and that produced the April reframing you just read.
When you complete the reflection below, you'll have spent ~30 minutes on this course. If even one idea in these six lessons sharpens how you think about your own work, we'll consider the trade fair.
Welcome to the Lab.