
Redesign the academy around this quarter's priorities
What matters now goes first, built from what you already have.
Pick your team or an app you use. Each Journey Play runs from Claude, ChatGPT or Copilot, and nothing goes live until you approve.
Plan, build, deliver and keep every program current. Written for: I lead Learning & Development and I'm responsible for what our people learn and for keeping it current.

What matters now goes first, built from what you already have.

From the quarter's objectives to the programs each team needs.

A draft course with a quiz, from the documents you already have.

Storyboard first; it renders only after you approve it.

A click-through lesson with hotspots and a check, tracked in Juno.

The old package edited in place: same link, same assignments, every version kept.

Narration for every section, for frontline teams and anyone who learns better by ear.

Imported once, then edited in plain words: same link, same assignments, every version kept.

A rename, a new logo, a changed rule: found and fixed across your library, one approval.

The content of a locked package, rebuilt as a native Juno course with its quiz.

Keep, merge, rebuild or retire: decided before the migration, not after.

The old package edited in place: same link, same assignments, every version kept.

A channel with topics, filed from your library, gaps drafted.

A shortlist of current courses and videos; you pick what goes in.

The audience built from roles and attributes, assigned when you approve.

Your academy homepage, previewed before it goes live.

One academy page, translated into every language you need, each one reviewed before it goes live.

Your catalog page with the rails your people need: for you, popular, by role, free, and your own.

No-shows found, the recording or a short lesson sent, a deadline set.

What drifted from the source, with a draft fix for each.

A short list of what to update, merge or retire.

New content checked against what already exists.

Pass rates, falling scores and reset spikes: the content that needs fixing, not the people.

From who learned it, to who talked about it, to the accounts now using it. Every week.

One snapshot of progress, by team.

The trend after a launch, with what moved.

Gaps visible before the deadline.

Spend by provider and by team, the top spenders, and the requests still waiting.

Started, then stopped: who, on what, for how long, with a nudge drafted.

Your saved dashboard in five lines: what moved, why, and who is behind it.
Your team's next plays
Northstar · Revenue Enablement
Northstar Sales12 repsFour colleagues around a laptop in a bright office
Coach the team from recent wins and lossesEvery month
Turn what customers ask on calls into trainingEvery month
Turn a review into a plan with datesBETAEvery review cycleExample data