
Ship on Monday, train on Tuesday
A release note becomes a click-through lesson for the teams it changes.
- For
- Revenue Enablement
- Routine
- Every release
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Channel · for salesSales Win Room3 new this week
Objection Handling
by Northstar
Updated September 28, 2026
Competitive Positioning
by Northstar
Updated September 24, 2026

Pricing and packaging
by Northstar
Updated September 9, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want to turn a product release into a click-through lesson in Juno Journey: people practice the new flow, answer a quick check, and the score reports back to Juno. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. Where the release note lives (or I’ll paste it) 2. Screenshots of the new screens (I’ll attach them) 3. Who the lesson is for 4. The pass mark Ask these in one message, then wait for my answers. In that same first message, also ask me my role and the team I support, and which product tracker or release notes we use. Then check each one is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. If the release note lives in another tool, check it’s connected in this chat; if not, I’ll paste it. Rebuild each screen in HTML to match my screenshots; never invent UI. Search Juno first for training on this feature, and update it if it exists. Then outline 4-6 steps that mirror the real clicks, with hotspots and short coaching, plus a knowledge check. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it. Routine: after the first run, offer to repeat this after every release. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run.
Your AI asks you
- Q1Where the release note lives (or I’ll paste it)
- Q2Screenshots of the new screens (I’ll attach them)
- Q3Who the lesson is for
- Q4The pass mark
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: Every release. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- Jiravia your AI assistant
- JunoRequired
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

This month's “What's new” digest and video
Everything you shipped in one short course, plus a video on the biggest change.
Every month
A Product Hub channel from your release notes
Your releases as short lessons, filed by product area.
Every release
A 5-question drill with a deadline
The key facts after a launch, checked, with a nudge drafted.
Every launch






















