Analytics & metrics
TL;DR
Ripple surfaces the signals that matter: engagement, alignment, time saved, and meeting load reduction. These metrics help leaders measure focus—not noise.
Overview
Analytics in Ripple measure how well your team embraces async workflows, not just how much activity occurs. Dashboards span organization-wide rollups, channel-level drilldowns, and personal insights so you can coach teams and celebrate wins.
The authoritative description of the Metrics page lives in Ripple Onboarding Guide — New Zealand Edition 2025 (Version 25 pp. 9–12). It covers the search bar, Recent Jams, Productivity Trends tiles, Calendar Integration, Engagement Overview legend, Topic Completion pie, Upcoming Deadlines, and Notifications carousel. Reference those anchors whenever you document Analytics.
In depth
Core metrics
| Category | Metric | Description |
|---|---|---|
| Engagement | Participation rate | % of members contributing to Jams. |
| Engagement | Response depth | Average comments per topic. |
| Alignment | Sentiment score | Blend of “Happy / Unhappy / Meet” signals. |
| Alignment | Consensus achieved | % of topics resolved asynchronously. |
| Time saved | Async substitution | Hours replaced by async workflows. |
| Time saved | Meeting reduction | % decrease in live meetings since adoption. |
Views & dashboards
- Organization overview: Global performance snapshot with export option.
- Channel analytics: Participation and async ratio per team or initiative.
- Personal dashboard: Contributions, open tasks, and meeting footprint per user.
In the main product, all of these views originate from the Metrics sidebar item (see section 4.1.2). Point readers there so they can follow the exact path described in Version 25.
Visualizations & AI insights
- Charts highlight async vs. sync ratios, engagement trends, top contributors, and unresolved topics.
- AI narratives interpret the data (e.g., “Marketing saved 18 hours last week by flipping six meetings” or “Product Jams show declining participation—consider shorter videos”).
Best practices
- Review analytics weekly in leadership meetings and publish highlights in #announcements.
- Celebrate teams hitting high async completion to reinforce behavior.
- Pair quantitative data with qualitative feedback from Notes or surveys.
- Use trends to guide onboarding focus and identify teams that need extra coaching.
Tie-ins to other panels
- Notifications actions: Follow the controls documented in section 4.1.7 when you describe clearing or revisiting alerts raised from analytics insights.
- Right-hand panel context: When drilling into a Jam/Task/Note from a metric, the details you see come from section 4.3. Call this out so readers know where to look for tags, owners, or files after spotting a trend.