Playbooks
Workflows, not features
Cross-track playbooks that chain academy lessons into one working system in your own workspace: close the feedback loop, launch a feature everywhere, fix activation, run Slack-first support.
- 10
- Playbooks
- 4
- Roles
- The Loop
- One framework
For product managers
Product managers
Close the feedback loop end-to-end
The flagship Userorbit story: collect feedback, triage it, put it on a public roadmap, announce the ship, and notify every voter automatically.
The feature launch playbook: demo → video → announcement → tour → adoption
Record a demo, generate the video, write the announcement, attach a tour, and measure adoption. One launch, every surface.
The activation improvement loop: measure → find drop-off → fix with a tour → verify
Build the activation funnel, find where new users stall, fix it with a checklist, and verify the lift in the same chart.
Retention rescue: cohorts → replays → churn survey → win-back announcement
Find the cohorts that slip away, watch why in session replay, ask with a churn survey, and win them back with a targeted announcement.
For growth
Growth
The PLG onboarding stack: checklist + tour + segmentation survey, measured
Assemble the onboarding stack that activates self-serve signups, then measure whether it actually moved the number.
Segment-driven communication: right message, right users, every surface
Stop announcing to everyone. Build segments once and reuse them across announcements, tours, and surveys.
For support & CX
Support & CX
The deflection stack: docs + AI agent + widget, honestly measured
Build self-serve support that actually deflects (help center, AI agent, widget chat) and measure it with a methodology you can defend.
Slack-first support ops
Run B2B support where your customers already are: Slack channels, keyboard-first triage, and automations behind them.
For founders
Founders
One-person product ops: let AI and workflows run the busywork
Nova drafts, workflows route, and the GitHub pipeline turns feature requests into PRs. Product ops for a team of one.
Instrument your product properly from day one
The events to track for a PLG SaaS, naming conventions that survive scale, and a clean catalog from the first commit.