juno journey
Book a demo

A course ends.A journey doesn't.

In the LMS, a journey is the blended path your team already builds. The same object also runs the process around it, and its proof starts the next run.

Book a demo

It is the journey your team already builds in Juno.

Every change starts one. Every result starts the next.

A release, a policy, a new hire or a renewal: the journey is what Juno runs each time, from the change to the proof that people are ready.

How it works

Business decision

1Trigger & Signal

  • GitHubProduct updates and changes
  • Jira
  • Workday

Judgment

2Knowledge Design

Your LLM + Juno MCP

  • Analyzes and prioritizes
  • Mission-critical
  • Important, not urgent
  • Nice to know
Human approval

Strategy

3Delivery & Adoption

  • EmployeesLearning that fits them, delivered
  • PartnersLearning that fits them, delivered
  • CustomersLearning that fits them, delivered
  • Assignments to the right people at the right time
  • Channels by role and team
  • Curated updates by audience

4Measure

Close the loop: measure impact, and the next change starts it again

One release, walked through the four phases

  1. 1

    Trigger & Signal

    The journey starts itself, manually, or from your own tools.

    The business decides what changed matters

  2. 2

    Knowledge Design

    Who, what, format, language, decided from context Juno keeps current.

    Your LLM proposes who it concerns and how urgent, you approve

  3. 3

    Delivery & Adoption

    Enrollment, reminders, escalations and re-assignment run without anyone chasing them.

    Juno delivers by audience

  4. 4

    Measure

    What changed is read, and it becomes the next trigger.

    You read who is ready, and the next release starts again

The same release, in one conversation

This release is in GitHub. Brief CS, our customers and our partners by Friday.

Claude

The journey your team already builds

Steps in order: courses, quizzes, videos, articles, SCORM, with live sessions on the Meetings tab, steps that wait for a validator, and a certificate at the end.

  • Steps in order

    Lock the sequence where it matters, or leave it open.

  • The Meetings tab

    A workshop belongs to the run, not to a calendar beside it.

  • Pending review

    Open answers, uploads and recordings are looked at before anything moves on.

  • The certificate

    Issued when someone finishes, and it carries the date it lapses.

  • Assignments

    What a person is given, and the day it is due.

  • Channels

    Where the content sits for the people it is for.

  • Updates

    What goes out when something inside it changes.

Your checkpoints, wherever you want them

Approve a build, sign off a send, arbitrate an exception. Who that is changes with the journey: a manager, a CSM, a compliance officer. You set the level.

Every journey comes with its recipe

On each journey page: how it runs, the tools it connects, the prompts to start it, and the view that tells you it worked.

  • 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 a 30-60-90 day onboarding journey

    Three phases for one role, a checkpoint quiz per phase, and the courses you already have reused where they fit.

    Your AI asks you

    The role, what "ramped" looks like at 30/60/90, any existing material, who signs off

    New to Juno? See it in a demo
    The prompt

    I want a 30-60-90 day onboarding journey in Juno Journey for one role, so new hires ramp on a clear path instead of a pile of links. 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 role and the team 2. What “ramped” looks like at day 30, 60 and 90 3. What material we have outside Juno, if any, and where 4. Who signs off at each milestone Ask these in one message, then wait for my answers. For material outside Juno, check that source is connected in this chat; if not, I’ll connect it or upload files. Don’t invent our processes. Search Juno first and reuse existing courses and quizzes wherever they fit. Then propose the journey: three phases, the courses in each, a checkpoint quiz per phase, and the gaps you’d fill with short new courses. After I approve the outline, build the new pieces and the journey as drafts. Don’t publish, assign or notify anyone until I say so.

  • Roll out a new policy with proof of completion

    A short course, a 5-question check and an acknowledgment, with a clear list of who's done.

    Your AI asks you

    The policy document, who must complete it, the deadline, acknowledgment or quiz

    New to Juno? See it in a demo
    The prompt

    I want to roll out a new policy in Juno Journey with proof that everyone who needs to has read and understood it. 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 policy document (upload it, or tell me where it lives) 2. Who must complete it (departments, locations, roles) 3. The deadline 4. Acknowledgment, a quiz, or both Ask these in one message, then wait for my answers. If the document lives in a tool outside Juno, check it’s connected in this chat; if not, I’ll upload it. Stick to what the policy says; don’t add rules. Search Juno for older versions of this policy training and update rather than duplicate. Then plan a short course (what changed, what it means for you, examples), a 5-question check with a pass mark, and an acknowledgment step. Show me that outline, the audience and the due date first, then build as drafts. Don’t publish, assign or notify anyone until I explicitly approve.

Every prompt

Two customers, on the object itself

One builds them and keeps them current. One ran an onboarding wave on it.

“Speaking from my experience, Juno is the perfect combination of functionality and flexibility. Juno is really intuitive to use, and allows me to quickly build courses, create high-quality journeys, and maintain them all easily in one place.”
Meagan D., Director of Sales Enablement at Hunters.Meagan D.Director of Sales Enablement, Hunters
“We had to onboard 100 new hires remotely and connect them directly with their teams' objectives and workflows. Using Juno's onboarding path, we decreased the time and manpower involved by 20% and were able to finalize the process within a month.”
Hili B., HR & OD Expert at Kaltura.Hili B.HR & OD Expert, Kaltura

How is a journey different from a course?

A course is content someone completes. A journey is the whole run: the content in order, the live sessions, the checkpoints, the people it applies to, and what changed by the end. A course ends at completed. A journey ends by producing the trigger for its next run.

A learning path, what your LMS probably calls it, is the sequencing half of that. It orders content and tracks progress. It has nothing in front of it and nothing after it: no trigger, no audience rule, no delivery that runs itself, no reading of what changed.

Three neighboring objects, kept apart on purpose. A group is a segment of people. A channel is a space that holds content. A journey is an ordered run of learning that tracks completion. One scheduled run of a journey, for one set of people, is a cohort.

How do you know it changed anything?

A journey does not end at completed. Its last phase reads what changed in the work: the validated step where someone had to do the thing, the quiz that comes back weeks later, the manager who confirms a person can work independently, the officer who signs off, the same question asked before and after.

That reading is the Behavioral Change Signal. It is composed, never fixed: you choose which signals count for this journey and at which altitude, per release, per team, per population, per account, and the view is built from those. It is not one number and nothing is graded.

In-platform and human-loop signals run today. Business signals, what your CRM, your product analytics or your support queue show, are the direction the same reading extends into. And whatever it reads becomes the next trigger. That is the sentence that makes a journey different from a course.

learnedtalked about itused itthe outcome you pickcorrelation, never causation

What changed

Composed from the signals you chose

  • Can execute independently

    manager confirms, at each checkpoint

  • Population current

    by role, geography and risk profile

  • Certificates expiring

    flagged per person before they lapse

  • Evidence pack

    who, what, when, exportable per policy

  • Validated in practice

    scenarios and pitches, checked not clicked

  • Before and after

    the same question, two moments

One journey, three audiences

Every journey names the audience it was built for and runs for the other two. Same loop, different last mile, its own signals per audience.

The people you employ

A hiring wave, a new manager, a plan for the next role. It arrives as an assignment.

The people who buy from you

It reaches an account inside the academy they already open, as the update they needed.

The people who sell for you

It lands on a partner as a certification they have to keep current to keep selling.

Six families, one object each time

Every one of them is this page, run for a different reason.

Questions people ask.

Is a journey a course?

No. A course is one piece of content that ends when someone completes it. A journey is the run around it: what starts it, who it applies to, the content and live sessions in order, the checkpoints you approve, and the reading of what changed afterwards. That reading starts the next run.

What is the difference between a journey and a learning path?

A learning path sequences content and tracks progress. A journey does that too, and adds the parts a path has no place for: a trigger that starts it, an audience rule that decides who is in it, delivery that reminds and escalates on its own, human checkpoints, and a reading of what changed.

Do I need the whole loop to use a journey?

No. Build a journey the way your team builds one today, in Juno's own interface, and add the automatic parts when you want them. Checkpoints are several, one, or none. You set the autonomy level. Operating from ChatGPT, Claude or Copilot is a mode you switch on when you are ready.

Where does a human approve anything?

Anywhere you decide. A checkpoint is not a phase: it plugs into any of the four. Approve a build before it publishes, sign off a send before it reaches anyone, arbitrate an exception. Who the person is changes with the journey: a manager, a CSM, a compliance officer, a team lead.

What starts a journey?

You do, or one of your own systems does. Juno syncs people natively from your HRIS or HCM over SCIM, and from Okta, Microsoft Entra, Google or CyberArk. For everything else, your LLM reads the change, in Jira, Confluence, Notion, GitHub or Google Drive, and drives Juno.

Can the same journey run for customers and partners?

Yes, and that is the point. A journey names the audience it was built for and runs for the other two, with the same four phases and a different last mile. Employees get an assignment, customers get an academy update, partners get a certification refresh. Each audience keeps its own signals.

Is a journey the same as a cohort?

No. The journey is the object you design once. A cohort is one scheduled run of it, for one set of people, with its own dates, its own checkpoints and its own reading of what changed. Design the journey once, then run as many cohorts from it as you need.