The flipped meeting model
TL;DR
Ripple applies the flipped-classroom idea to work: prepare asynchronously, meet briefly and purposefully, and let AI capture outcomes. The result is higher alignment with dramatically less live time lost.
Overview
Traditional meetings burn live time on updates that could have shipped beforehand. Flipped meetings reverse the flow:
- Prepare async: Participants record or write context in a Jam.
- Engage live: Discuss only decisions or blockers.
- Act fast: AI generates tasks, minutes, and summaries.
- Measure engagement: Track participation, alignment, and impact metrics.
Ripple operationalizes this cycle so it becomes a habit instead of a heroic effort.
In depth
The problem
- Knowledge workers spend 30-50% of their week in meetings.
- Up to 40% of those sessions add little or no value.
- Outcomes are rarely documented or actionable afterward.
The Ripple method
| Stage | Purpose | Tools |
|---|---|---|
| Prepare | Share briefs, data, and context asynchronously. | Jams |
| Align | Collect feedback and sentiment. | Jam summaries & reactions |
| Decide | Reserve live time for items needing debate. | Calls |
| Act | Convert decisions into tasks. | Jams & Tasks |
| Learn | Store insights & metrics. | Summaries and analytics |
Outcomes
- 60-70% fewer recurring meetings.
- Sharper, faster decisions.
- Transparent ownership via linked tasks.
- Preserved institutional memory with searchable transcripts and summaries.
Best practices
- Adopt a “no meeting without a Jam” rule; no agenda = no live time.
- Keep Jam videos under 3 minutes and topic-focused.
- Start every live Call from an existing Jam to keep context tight.
- Review participation metrics weekly to reinforce habits.
Tie it back to the UI (Version 25 §4)
When you operationalize the flipped model, reference the specific UI sections from Ripple Onboarding Guide — New Zealand Edition 2025:
- Create async context: Use the R dot (·) quick-create menu in Section 4.1.1 to launch Jams, Calls, Tasks, and Notes from anywhere.
- Guide teammates through the layout: Sections 4.1–4.3 map the left sidebar, middle panel, and right-hand panel so everyone knows where async prep happens and where live call artifacts land.
- Inspect Jam anatomy: Section 5 shows Video, Files, Discussion, Summary, Sentiment, and Related Tasks blocks exactly as they appear, making it easy to coach teams on what “done” looks like.
Linking back to those anchors keeps your enablement decks and SOPs perfectly aligned with Version 25.