Signature play
Trace a launch from training to customer usage
Who learned it, who talked about it, and which accounts now use it, every week.
Journey Plays for every team.
Journey Plays for HR
Journey Plays for L&D
Journey Plays for Revenue Enablement
Journey Plays for Customer Education
Journey Plays for CX & Support
Journey Plays for Legal / IT
Ready-made prompts that build training in Juno, from ChatGPT, Claude, GitHub Copilot, or Cursor.
Ready-made prompts that build training in Juno, from ChatGPT, Claude, GitHub Copilot, or Cursor.
The whole employee lifecycle, from the offer letter to the next role.
Before day one: paperwork, a welcome, and a manager who is ready.
The first 90 days, for every role and every wave.
What each role needs, and where the gaps are.
Mandatory training, new policies, and proof of completion.
Objectives turned into plans people follow.
From first promotion to senior leader.
Show people where they can grow here.
Plan, build, deliver, and keep every program current.
Priorities first, from what the business needs.
Courses, lessons, and videos from your own sources.
Your existing library brought over, and editable from day one.
The right learning in front of the right people.
Nothing stale, nothing duplicated.
Did it change anything?
Sales and partners current on every release, and it shows in the deals.
Every release reaches your sales team in days.
The new story, rehearsed before it meets a customer.
Proof that the team can deliver it.
Teach what winning deals have in common.
Partners certified on the product you sell today.
Learned it, using it, winning with it.
Customers onboarded, current, and certified.
A branded academy your customers actually use.
Every account onboarded like your biggest one.
The accounts that use what changed, notified in the tools they already use.
Proof that trained accounts adopt.
Agents current on every change, from their first ticket.
The first weeks of a support agent.
Agents briefed on every release before the first ticket about it arrives.
What customers keep asking becomes training.
Better answers, coached from real conversations.
Policies rolled out, tools adopted, and proof ready.
Every change, acknowledged by the right people.
Always on, always current.
A new tool, adopted in weeks.
The right people enrolled, and the proof ready to export.
Signature play
Who learned it, who talked about it, and which accounts now use it, every week.
A draft course with a quiz, built from the documents you already have.
Each release note becomes a click-through lesson for the teams it affects.
Once the record is created: paperwork, a welcome video, and the first week.
Three phases with a checkpoint each, reusing your existing courses where they fit.
Each new hire's progress at day 30, with one suggested nudge for each manager.
A draft course with a quiz, built from the documents you already have.
Everything that drifted from the source, with a draft fix for each.
Imported once, edited in plain words; links, assignments, and versions stay.
Signature play
Who learned it, who talked about it, and which accounts now use it, every week.
Each release note becomes a click-through lesson for the teams it affects.
Reps study it, practice it, and write it, scored against your rubric.
Each person scored 1 to 5 from their own calls, with quotes, and coaching only for the gap.
People matched from the CRM: a path for the admin, the champion, and users.
The lesson is updated in place, and the affected accounts are notified.
Usage side by side, clearly labeled as correlation.
The most frequent questions, answered plainly, with sources linked.
The key facts, checked before the tickets arrive.
Three phases with a checkpoint each, reusing your support courses.
Each agent scored 1 to 5 from their own tickets and emails, with excerpts, and coaching only for the gap.
A short course, a 5-question check, and an acknowledgment, with who's done.
Overdue training first, sorted by team and topic, ready for the audit.
A short path for each role, built from the vendor's docs, assigned on go-live.
Each person scored 1 to 5 from their own calls, with quotes, and coaching only for the gap.
Each agent scored 1 to 5 from their own tickets and emails, with excerpts, and coaching only for the gap.
85 Journey Plays
Once the record is created: paperwork, a welcome video, and the first week.
The hiring manager gets the checklist, the buddy intro, and the first 1:1s, all prepared.
The handbook and key policies, acknowledged before the first login.
Three phases with a checkpoint each, reusing your existing courses where they fit.
Week 1 to day 90, organized by topic, with a short lesson for each gap.
Sessions, hosts, and attendance for a whole cohort, in one place.
The orientation everyone takes, checked against your policies every month.
Each new hire's progress at day 30, with one suggested nudge for each manager.
Each role's competencies and level, drafted for you to approve.
People rate their level, managers confirm, and you see the gaps by team.
Teams and skills on one grid, with the three weakest spots first.
A short course, a 5-question check, and an acknowledgment, with who's done.
A reminder drafted for each overdue person, sent only when you say so.
Overdue training first, sorted by team and topic, ready for the audit.
Each person gets the version for their location and role, from your HRIS.
A plan for each person the objective affects, which their manager commits to.
Internal options first, one external option, and the request drafted.
The best current courses and videos, each with one line on why it is there.
It starts when someone is promoted: the standard, the team and the first 1:1s.
Who finished, who is overdue, and one suggested nudge.
Where each person stands, what has stalled, and one thing to suggest.
What you decided in the review becomes steps, dates, and a check.
The path, how far each person is from it, and a plan agreed with their manager.
One mentor, one goal, and nothing for you to administer.
Who is closing in on one career path, ready for the talent review.
This quarter's priorities go first, built from what you already have.
This quarter's objectives, turned into the programs each team needs.
A draft course with a quiz, built from the documents you already have.
It starts with a storyboard for you to check, then renders the video once you approve it.
A click-through lesson with hotspots and a check, tracked in Juno.
The old package is edited in place: same link, same assignments, every version kept.
Topics filled from your library, with drafts for anything missing.
A shortlist of current courses and videos. You choose what goes in.
An audience built from roles and attributes, assigned when you approve.
Your academy homepage, with a preview to check before it goes live.
Everything that drifted from the source, with a draft fix for each.
A short list of what to update, merge, or retire.
Every new course checked against what already exists.
One snapshot of progress, by team.
The trend after a launch, and what changed.
See the gaps before the deadline.
Each release note becomes a click-through lesson for the teams it affects.
Everything you shipped in one short course, plus a video on the biggest change.
Each release becomes a short lesson, filed by product area.
A quick check on the key facts after a launch, with a reminder drafted.
Pitch, product, and competitive material in one place your reps open.
A branching scenario: the customer asks, the rep picks an answer, the story branches.
Reps study it, practice it, and write it, scored against your rubric.
What your won deals have in common, turned into lessons and questions.
The questions buyers actually ask, answered before the next call.
Tiers, exams, and the gates between them, drafted as journeys for you to approve.
Only the partners who hold the certification, and only the part that changed.
Completions matched against calls, with a next step for each rep.
Signature play
Who learned it, who talked about it, and which accounts now use it, every week.
A branded public homepage with your real courses, for you to preview first.
People matched from the CRM: a path for the admin, the champion, and users.
At day 30, the evidence your CSM needs: is this account onboarded?
The lesson is updated in place, and the affected accounts are notified.
Questions from calls and tickets, answered in a lesson.
Usage side by side, clearly labeled as correlation.
Three phases with a checkpoint each, reusing your support courses.
Week 1 to day 90, with a short lesson for each gap.
The key facts, checked before the tickets arrive.
The handbook checked against the product docs every month.
The most frequent questions, answered plainly, with sources linked.
What your best answers have in common, turned into short lessons.
One short lesson on this month's threat, with a check.
A short path for each role, built from the vendor's docs, assigned on go-live.
New hires are provisioned through SCIM and get their mandatory training on day one.
Who completed what, which version, and when.
Each new hire is paired with a certified buddy, added to their onboarding path.
Your academy page in every language, each reviewed before it goes live.
Your catalog page, with rows for you, popular, by role, free, and your own.
Spend by provider and by team, the top spenders, and the requests still waiting.
Who started and stopped, on what, for how long, with a nudge drafted.
Pass rates, falling scores, and reset spikes show which content needs fixing.
No-shows found and sent the recording or a short lesson, with a deadline set.
Your saved dashboard in five lines: what moved, why, and who is behind it.
Narration for every section, for frontline teams and anyone who learns better by ear.
Imported once, edited in plain words; links, assignments, and versions stay.
A rename, logo, or rule change, fixed across your library with one approval.
The content of a locked package, rebuilt as a native Juno course with its quiz.
Decide what to keep, merge, rebuild, or retire before the migration.
Each person scored 1 to 5 from their own calls, with quotes, and coaching only for the gap.
Each agent scored 1 to 5 from their own tickets and emails, with excerpts, and coaching only for the gap.
I want to coach our team from recent wins and losses: what winning deals had in common, where lost ones went wrong, and training that fixes the pattern.
Happy to. One question before I build anything:
Where do you keep deals and call notes?
Salesforce and Gong
Compared last quarter's won and lost deals
Used Salesforce, Gong and Juno
Nothing is published, assigned, or sent until you say so.