Teams ready a day before launch.

Your LLM reads what shipped. Juno briefs each team, once you approve.

Thursday's release closed in Jira last night.

By Friday, you have rebuilt one course, rewritten four team briefs, and answered the same question ten times. Two sprints later, the feature is still explained wrong.

From a closed ticket to four teams briefed before launch

Release 4.2 closed in Jira. Find what needs training and brief Sales, CS, and Support by Wednesday.

Claude

Closed on Thursday, ready by Wednesday

  1. ThuSep 10

    Release 2026.37Closed
  2. FriSep 11

    Triaged

    1Mission-critical2Important, not urgent2Nice to know
  3. MonSep 14

    Four briefs, one per team

    SupportSalesCSPartners
  4. TueSep 15

    Approved

    Maeve M. · 9:40

  5. WedSep 16

    Ready before release day

    • Support
    • Sales
    • CS
    • Partners
  6. ThuSep 17· Ships

Interactive lesson · SCORMWhat's new: Notification settings · 3 min
Step 1 of 6

What's new · Beta

Notification settings

Choose Email, Slack, or in-app for each notification type, and know where learners still see reminders.

3 min4 steps1 checkPass 80%

Press Start to begin
SCORM · tracking

Every score is reported back to Juno.

Revise the course you already have

  • Rewrite only what changed

    Only the sections affected by the release are rewritten. Everything else stays word for word.

  • Every edit cites the release

    Each proposed edit links to the part of the release note it came from.

  • Keep earlier versions

    Each time you publish, the previous version is kept, so nothing your teams learned is lost.

  • A library your teams can trust

    The course your reps open on Thursday already covers what shipped.

Decide which changes need training at all

Release 4.2

12 changes

2Mission-critical
  • Roles per workspaceTraining
  • Admins can invite membersTraining
4Important, not urgent
  • Bulk export of reportsAnnounce
  • New filter on the people tableAnnounce
  • Due-date picker redesignAnnounce
  • SSO sign-in pageAnnounce
6Nice to know
  • Faster searchLog only
  • Refreshed iconsLog only
  • Editor shortcutsLog only
  • Smaller PDF exportsLog only
  • Email typo fixesLog only
  • Updated help linksLog only
  • Sort every change into three priorities

    Every change is sorted into one of three priorities: Mission-critical; Important, not urgent; or Nice to know.

  • Your LLM proposes a priority

    Your LLM reads the release and proposes a priority for each change.

  • Juno's tools do the work

    Juno's tools are built and documented so your LLM can run them and chain them together.

  • You make the final call

    You approve the triage before any course, post, or assignment goes out.

Juno acts within your existing Juno permissions.

When the release comes from a vendor, not from you: Tool & Vendor Enablement

See securitySee Juno in your LLM

Each team gets its own brief

  • Choose who gets each brief

    Role, department, location, or group decides who gets which brief.

  • Due before launch

    Each assignment carries a due date the day before the release date.

  • In each team's language

    Each team's brief goes out in the languages that team works in.

  • Posted to Slack

    Each team's Juno channel posts the brief to its linked Slack channel.

See who is ready, team by team

“Don't tell me who completed training. Tell me what changed.”
In scope 84 people
  • Learned the featurevia Juno78 / 84
  • Mentioned the featurevia call recordings61 / 84
  • Used the featurevia product usage29 / 84
ImpactThe outcome you pick

the biggest drop comes after the call, not the course

correlation, never causation

  • Readiness by release and by team

    Readiness is measured for each team on every release, before launch day.

  • Team leads confirm readiness

    Each team lead confirms their team is ready before release day.

  • Check knowledge after launch

    Each team takes a post-release quiz with its own passing score and deadline.

  • See what changed in the work

    The Behavioral Change Signal tracks the feature from the course to how people use it.

Try it

  • Build a Product Hub channel from our release notes

    Your releases become short lessons and videos, filed by product area.

    The prompt

    Your AI asks you

    Where your release notes live, who it's for, your product areas, how far back

    I want a Product Hub channel in Juno Journey: one place where people learn what we ship, easy to refresh from our release notes whenever I ask. 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 our release notes live (a tool, a docs site, or I paste them) 2. Who the channel is for (customers, our own staff, both) 3. Our product areas, to use as topics 4. How far back to go Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste/upload the notes. Never invent a release. Search Juno first for lessons on these features and any existing product channel, and reuse what fits. Then propose the channel: a topic per product area, existing content filed in, and a draft lesson for each gap. Build it as a new private channel and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish or notify anyone until I approve.

  • Turn a release into a click-through lesson

    Your new screens, rebuilt from screenshots and tracked as SCORM.

    The prompt

    Your AI asks you

    Where the release note lives, screenshots of the new screens, who it's for, the pass mark

    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. 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.

  • Build this month's "What's new" digest + explainer video

    This month's releases in one short course, plus a video on the biggest one.

    The prompt

    Your AI asks you

    The date range, where your updates live, who it's for, your brand colors

    I want this month’s “What’s new” digest in Juno Journey: one short course on what we shipped, plus a 60-second explainer video for the biggest change. 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. The date range 2. Where our updates live (release notes, a changelog, or I paste them) 3. Who it’s for (customers, sellers, support, everyone) 4. Our brand colors Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste the updates. Never include a change I can’t trace to the source. Look in Juno first for courses that already cover these features, and update them instead of repeating. Then list the changes by product area and propose which one gets the video. Build the digest as a draft course with a short quiz. For the video, show me the storyboard and render only after I approve it, then add it to the draft course. Don’t publish, assign or notify anyone until I say so.

  • Add a 5-question drill with a deadline

    A quick check on a launch's key facts, with a due date and a drafted nudge.

    The prompt

    Your AI asks you

    The topic or course, who takes it, the deadline, the pass mark and attempts

    I want a quick 5-question drill in Juno Journey that locks in the key facts after a launch, with a due date so it actually gets done. 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. The topic, or the course it should reinforce 2. Who should take it 3. The deadline 4. The pass mark and how many attempts Ask these in one message, then wait for my answers. Find that course or lesson in Juno first and base every question on it. If the material lives outside Juno, check it’s connected here; if not, I’ll paste it. No questions you can’t trace to the source. Show me the 5 questions with answers and one-line explanations. After I approve, build the quiz as a draft and prepare the assignment with the deadline as its due date. Tell me plainly what Juno reminds people about on its own; you can’t schedule repeats or reminders from this chat. Draft a nudge I can send later. Show me who would get the assignment and the nudge, but don’t assign or send anything until I explicitly say go.

All promptsNew to Juno? See it in a demo

“The journeys with automations really helped me make sure my support agents were being kept up to date on our product on a daily basis.”
Salome M.Customer Experience Training & AI Enablement Manager, Moon ActiveG2
CustomersWhat they receiveAcademy update, in-app training, and curated updateMeasured onAdoption of the shipped feature · ticket deflection · renewal
PartnersWhat they receivePartner academy and certification refreshMeasured onCertified partner capacity · partner-sourced pipeline
EmployeesThis pageWhat they receiveRelease brief per teamMeasured onTeams certified before release day

Frequently asked questions

How do we keep training current when the product ships every two weeks?

Let each release trigger the update: your LLM reads what shipped and Juno rewrites only the sections it touches, keeping the previous version.

How do I know which releases actually need training?

Each change is sorted into a priority first, and the priority decides whether it becomes training, an announcement, or a log entry.

How do we get sales, CS, and support ready before launch day?

Each team gets its own brief from the same release, assigned by role with a due date the day before launch.

How do you measure product-launch readiness?

By release and by team, before launch day. Each team lead confirms their team is ready, and post-release quizzes test each team on its own content. After launch, the Behavioral Change Signal tracks the feature from the course to calls and product usage, and shows what changed in the work.

Can ChatGPT or Claude update our training when we ship?

Yes. ChatGPT, Claude, GitHub Copilot, and Cursor connect to Juno through the Juno MCP. Your LLM reads the change where it already lives and directs Juno to update the course, draft the lesson, and prepare the assignments. Everything stays within your Juno permissions, and nothing is published or assigned, and no one is notified, until you approve.

How do we train customers and partners on the same release?

The same journey runs for all three audiences; only the final delivery changes: a brief for employees, an academy update for customers, a certification refresh for partners.

Is Juno a sales enablement platform or an LMS?

Juno is an LLM-native People Readiness Platform with an LMS as its delivery layer. Each release starts the work, your LLM directs Juno, and readiness is measured by what changed in the work. For everyday enablement between releases, from new pitches to process changes, see CS, Sales & Support.

Does your AI read our Jira, and is it secure?

Juno does not read Jira itself. Your LLM reads the change through Jira's own MCP and directs Juno through the Juno MCP. On Juno's side, access is limited to your existing permissions, over OAuth 2.1 with no API keys. For details, see Security and the AI Policy.