Jams (flipped meetings)

TL;DR

Jams are the heart of Ripple’s flipped-meeting model. They let teams align asynchronously through short videos, written briefs, and AI-structured discussions so live meetings shrink—or disappear.

Overview

Each Jam acts as a mini workspace for a single topic or recurring series. You can define objectives, record 3-minute updates, gather sentiment, and let Ripple AI create summaries and tasks. Most teams discover that once a Jam is humming, the “live” follow-up becomes optional.

In depth

Creating a Jam

1. Click New Jam from the dashboard or inside a channel.
2. Add a title and objective (what you want to align on).
3. Choose visibility (public to the org or private).
4. Add topics—each represents a discussion point.
5. Record a ≤3-minute video or drop written updates, files, or links.
6. Invite participants and set a reply deadline.

Participating in a Jam

• Respond with video or text to keep everyone’s voice in the room.
• Use sentiment buttons (Happy, Unhappy, Let’s Meet) to signal alignment.
• Ripple AI builds a live summary thread as replies roll in.

After the Jam

• Review the auto-generated Summary & Next Steps.
• Tasks are auto-created and pushed to the relevant projects or channels.
• Decide whether you still need a live meeting—often the answer is “no.”

Jam workspace map (Version 25 §5)

Section 5 of the NZ guide is the canonical description of what lives inside every Jam. Use it when you need to verify copy, screenshots, or training steps:

• Video (Section 5.1): Play uploaded recordings inline, scrub to any timestamp, review the auto transcript, and read the AI-generated summary of key decisions.
• Uploaded Files (Section 5.2): Shows every artifact attached to the Jam; click to preview or download without leaving context.
• Discussion (Section 5.3): Time-stamped comment stream where participants drop updates, questions, and replies.
• Video Summary (Section 5.4): Ripple’s automatic digest of themes, outcomes, and next steps—ideal for sharing with stakeholders who skip the full recording.
• Topic Sentiment (Section 5.5): Capture the mood (positive, neutral, needs attention) so you can triage quickly.
• Related Tasks (Section 5.6): Lists all tasks spawned from the Jam and links back to their owners, due dates, and channels.

When documenting Jams elsewhere in this site, link back to those anchors so everyone consumes the same authoritative description.

Recurring Jams

• Toggle Recurring to roll topics and incomplete tasks into the next cycle.
• Ideal for weekly team check-ins, sales reviews, project updates, and 1:1 conversations.

Analytics within Jams

• Participation rate: % of invitees who contributed.
• Alignment score: Sentiment blend from Happy / Unhappy / Let’s Meet.
• Engagement depth: Number of comments per topic.
• Time saved: Estimated hours replaced by async updates.

Best practices

• Keep videos concise (<3 minutes) and topic-focused.
• Start with objectives, not agendas, to drive outcomes.
• Encourage async participation to finish 80% of the work before any live call.
• Turn recurring meetings into Jams to cement new habits.

Example use cases

• Leadership updates: Async recordings with AI summary routed to the board.
• Sprint reviews: Product demos posted ahead of the retro.
• Client syncs: Replace status calls with shareable Jam links.

See also

• The Flipped Meeting Model
• Calls
• Tasks & Projects