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

Pricing and packaging
by Drumlin
Updated Sep 9
The prompt
Paste it into Claude or ChatGPT. It asks its questions in one message, then starts from what you already have in Juno.
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.
What your assistant will ask 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
How it runs
- 01
Connect
Juno and the tools below
- 02
Answer
its questions in one message
- 03
Check
the draft or the report it builds
- 04
Approve it
Nothing is published, assigned, or sent before that.
Routine: Every release. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JiraConnected in your assistant
- JunoRequired
Your assistant reads these tools and does the work in Juno.
Teams that use it
Journey Plays that go with it
Send this month's “What's new” digest and video
Everything you shipped in one short course, plus a video on the biggest change.
Every monthBuild a Product Hub from release notes
Each release becomes a short lesson, filed by product area.
Every releaseRun a 5-question drill with a deadline
A quick check on the key facts after a launch, with a reminder drafted.
Every launch



























