
A new-hire channel for one role
Week 1 to day 90 in topics, with a short lesson for every gap.
- For
- HR
- Routine
- Every new role
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Example dataBackNorthstar

Account Executive ramp
25%complete
Steps: 1 of 4Due: Jan 6, 2027
Steps
Welcome from the Lisbon teamVideo · 4 minReview
PaperworkTodo / Checklist · 5 itemsContinue
Your first-week planArticle · 6 minGo to article
How we work hereCourse · 5 sections
Meetings
Wed14Walk through the CRMJan 14 · 11:00Tomás Reis · Buddy
Fri161:1 on FridayJan 16 · 15:00Rui Cardoso · Manager
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
Works in Claude, ChatGPT, Copilot
I want a new-hire channel in Juno Journey for one role, so a new person knows exactly what to learn and when. 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 2. What they should be able to do by day 30, 60 and 90 3. Whether we keep onboarding docs outside Juno, and where (or I’ll upload them) 4. When the next hires start Ask these in one message, then wait for my answers. In that same first message, also ask me my role and the team I support, and which docs or knowledge base we use. Then check each one is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. If the docs live in another tool, check it’s connected in this chat; if not, I’ll connect it or upload the files. Don’t make up our processes. Search Juno first for onboarding courses and journeys we already have for this or similar roles. Then propose topics like Week 1, Month 1, Tools and People, filled with existing content, with short draft lessons only where there’s a gap. Show me the outline, then 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, assign or notify anyone until I approve. Routine: after the first run, offer to repeat this for every new role. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run.
Your AI asks you
- Q1The role
- Q2What they should be able to do by day 30, 60 and 90
- Q3Whether we keep onboarding docs outside Juno, and where (or I’ll upload them)
- Q4When the next hires start
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: Every new role. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
- Google Drivevia your AI assistant
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

A 30-60-90 ramp for every new role
Three phases, a checkpoint each, your existing courses reused where they fit.
Every new role
Plan every onboarding wave from one calendar
Sessions, hosts and attendance for a whole cohort, on one calendar.
GCBETAEvery wave
Keep the company orientation current
The foundation everyone gets, checked against your policies every month.
Every month























