Redesign the academy around this quarter
This quarter's priorities go first, built from what you already have.
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
Plan, build, deliver, and keep every program current.
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.
29 Journey Plays
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.
Signature play
Who learned it, who talked about it, and which accounts now use it, every week.
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.
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.