juno journey
Book a demo

The release ships Thursday. Every team was ready Wednesday.

Your LLM reads what shipped in GitHub or Jira, decides who it matters to and how urgent it is, and drives Juno to brief each team before launch. You approve before anyone is told.

Book a demo

4.7 / 5G2

Example data

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, and two sprints later the feature is still explained wrong.

How it works

Business decision

1Trigger & Signal

  • GitHubProduct updates and changes
  • Jira

Judgment

2Knowledge Design

Your LLM + Juno MCP

  • Analyses and prioritises
  • Mission-critical
  • Important, not urgent
  • Nice to know
Human approval

Strategy

3Delivery & Adoption

  • Sales
  • CS
  • Support
  • Customers
  • Partners
  • Assignments to the right people at the right time
  • Channels by role and team
  • Curated updates by audience

4Measure

Who is ready on Wednesday, and what the next release changes

One release, one conversation

From the ticket to four teams briefed, before launch

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

Claude

Example data

Release 2026.37

Closed Thursday. Ready 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

    Dana M. · 9:40

  5. WedSep 16

    Ready before release day

    • Support
    • Sales
    • CS
    • Partners

  6. ThuSep 17· Ships

Example data

Ship Monday, train Tuesday

Interactive lesson · SCORMWhat's new: Notification settings · 3 minStep 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 beginSCORM · tracking

Example data

Every score reports back to Juno.

Revise the course you already have, from the change that broke it

Example data

  • Only what changed

    The sections the release touches are rewritten. The rest stays word for word.

  • Cited to the release

    Each proposed edit points to the passage of the release note it came from.

  • Earlier versions kept

    Each publish keeps the version before it, so nothing the field learned is lost.

  • A library they trust

    The course your reps open on Thursday already says 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

Example data

  • Three priorities

    Mission-critical, Important, not urgent, Nice to know. Every change lands in one.

  • Your LLM reads

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

  • Juno's tools act

    Juno's tools are built and documented for your LLM to drive and chain.

  • Your call stands

    You approve the triage before a course, a post or an assignment moves.

Juno acts within your existing Juno permissions, over OAuth, with no API keys.

When the release is a vendor's, not yours: Tool & Vendor Enablement

See securitySee Juno in your LLM

Each team has it a day before launch

Example data

  • Chosen by who

    Role, position, department, location, group or employee type decide who gets which brief.

  • Due before launch

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

  • In their language

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

  • Posted into Slack

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

Ready is something you can see on Wednesday

“Don't tell me who completed training. Tell me what changed.”
In scope 84 peopleExample data
  • Learnedvia Juno78 / 84
  • Talked about itvia call recordings61 / 84
  • Used itvia product usage29 / 84
ImpactThe outcome you pick

the biggest drop comes after the call, not the course

correlation, never causation

  • Per release, per team

    Readiness is read for each team on each release, before the date.

  • The lead confirms

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

  • Checked after launch

    Post-release quizzes per team, each with its own pass bar and deadline.

  • What changed in the work

    The Behavioral Change Signal follows the feature from the course to its use.

Try it

  • Build a Product Hub channel from our release notes

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

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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 your screenshots, with hotspots, a quick check and SCORM tracking.

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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

    Everything you shipped this month in one short course, plus an explainer video on the biggest change.

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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 the key facts after a launch, with a due date and a nudge drafted for you to send.

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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.

Every prompt

Our support agents need to be kept up to date on a daily basis on all product changes and updates, Juno makes it really easy to create the content, automate its assignment and track the completion.

“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 at Moon ActiveSalome M.Customer Experience Training & AI Enablement Manager, Moon ActiveG2
CustomersWhat they receiveAcademy update, in-app, 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

Questions people ask.

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

Let the release start the update. Your LLM reads what shipped in GitHub or Jira and drives Juno, which finds the course the change affects and rewrites only the sections it touches. The rest stays word for word, each publish keeps the earlier version, and nothing goes live until you approve it.

How do I know which releases actually need training?

Every change is triaged before anyone opens a course, into the three priorities Mission-critical, Important, not urgent, and Nice to know. Your LLM reads the change and proposes the priority; Juno's tools act on it. The priority decides whether a change becomes training, an announcement or a log entry, and you approve the triage before anything moves.

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

Each team gets its own brief from the same release: Sales the pitch, CS what changes for the customer, Support the new flow. Juno assigns each brief by role, department, location, group or employee type, with a due date the day before launch, and posts it into the team's Slack channel.

How do you measure product-launch readiness?

Per release and per team, before the date. Each team lead confirms their team is ready, and post-release quizzes check each team on its own content. After launch, the Behavioral Change Signal follows the feature from the course to the call to product usage, and reads what changed in the work.

Can ChatGPT or Claude update our training when we ship?

Yes. ChatGPT, Claude and Copilot connect to Juno through the Juno MCP, over OAuth, with no API keys. Your LLM reads the change where it already lives and drives Juno to update the course, draft the lesson and prepare the assignments. Everything stays within your Juno permissions, and nothing is published, assigned or notified before your OK.

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

The same journey runs for all three audiences, and only the last mile changes. Employees get a release brief per team. Customers get an academy update and a curated update, measured on adoption of the shipped feature. Partners get a certification refresh, measured on certified partner capacity. See Push Product Updates to Customers and Certify Your 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. The release starts the work, your LLM drives Juno, and readiness is measured on what changed in the work. Everyday enablement between releases, from new pitches to process changes, lives on 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 drives Juno through the Juno MCP. Juno's side is scoped to your existing permissions, over OAuth 2.1 with no API keys, and publishing, assigning and notifying wait for your review. Details: Security and the AI Policy.