Quickstart
Prove value in under 20 minutes by following the same flow outlined in the New Zealand onboarding guide. This runbook turns that long-form narrative into a punchy pilot you can reuse for workshops or dry runs.
Objective
Spin up your first Ripple workspace objects — Jam, Call, Task, and Note — directly from R dot (·), validate that the left/middle/right panels display the right context, and confirm Metrics is ingesting activity so stakeholders can see immediate progress.
Checklist
- Accept your invite and sign in — Follow the steps in sections 2 and 3. Capture a screenshot of the confirmation banner and note who owns ongoing access requests.
- Tour the left sidebar — Starting at 4.1, hover over each icon (Rppl, Metrics, Collab, Tasks, Jams, Notes, Notifications, User status) and record any items you still need to configure. This ensures everyone can navigate before you create artifacts.
- Use R dot quick-create to launch a Jam — Re-create the flow in 4.1.1.1: rename the Jam, set the objective, assign an owner, and tag it to the channel you plan to pilot. Treat this as your anchor workspace.
- Add supporting Call, Task, and Note — Still within the quick-create menu, follow sections 4.1.1.2, 4.1.1.3, and 4.1.1.4 so every action item stays context-linked to the Jam.
- Verify the middle and right panels — Use 4.2 to check Recent Jams, Channels, Shared Jams, and Direct Chats, then confirm the right-hand panel shows the correct participants, files, and activity feed for the Jam you just created.
- Review Metrics and status — Jump to 4.1.2 to confirm productivity tiles populate, then set your status dot and custom status per 4.1.8 so teammates know the pilot window is live.
R dot quick-create cheat sheet
| Item | Where it appears | When to use it | Key controls |
|---|---|---|---|
| New Jam | Collab page | Stand up the shared space for a project or topic. | Rename the Jam, add an objective, set deadline/owner, share or open the ⋯ menu for extra options. |
| New Call | Linked to the current Jam/Collab view | Keep async and live work connected without leaving context. | Name the call, choose Public vs Private, pick participants, and select Instant or Scheduled (Smart Schedule). |
| New Task | Inbox (until reassigned) | Track actions that fall out of your Jam. | Add description, attachments, and discussion; set status (Backlog/In Progress/Done), assignee, tags, priority, and due date. |
| New Note | Notes middle panel | Capture briefs, decisions, or follow-ups. | Title the note, write free-form content, save, share with Viewer/Editor/Owner roles, and use ⋯ for history or delete. |
Verification tips
- Middle panel pulse: Recent Jams, Calls, and Summaries should all reference the Jam you just created. If not, refresh or confirm you published the Jam instead of abandoning the draft.
- Metrics tiles: Total Jams and Topics should increment after you create artifacts. Use the date filters (Last 3 Months / Current Quarter / Last Quarter) to ensure you are viewing the right window.
- Notifications: Creating or editing from R dot should generate at least one notification. Open the bell icon to confirm you can mark it read/unread.
- Right-hand panel context: Owners, tags, and due dates adjusted in the Jam should instantly reflect here. If fields stay blank, verify your changes were saved via the ⋯ menu.
Troubleshooting links
- R dot quick-create details
- Tasks workspace overview
- Notes workspace workflow
- Metrics diagnostics
- Status & notifications reference
Pilot reminders
⚠️
Warning
- Label every Jam, Call, Task, and Note created during the pilot with a “Quickstart” tag so you can archive or delete the artifacts afterward.
- If you are mirroring the New Zealand guide for another region, clone this page and tailor the links to the localized onboarding runbook.