
Turn this quarter's objectives into plans
BETADevelopment plans are not in the MCP yetA plan for everyone the objective touches, committed by their managers.
- For
- HR
- Routine
- Every quarter
- Setup
- Juno only
- You approve
- every draft
What you get
Example dataMy Goals

Run my first quarterly business review
Learn withJonas WeberDue dateDecember 12th, 2026
Completed 2 / 6 Steps
Leading business reviewsCoursePending PurchaseHow a quarterly review is structuredArticle · LEARN
List the three numbers your team ownsAction Item · PREPARE
Draft the review with your mentorAction Item · EXECUTE
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
Works in Claude, ChatGPT, CopilotAsk for beta access
I want to turn this quarter's objectives into a development plan for each person they touch, ready for their manager to commit. 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. My role and the team I support 2. The objectives (paste them, or tell me where they live) 3. Which teams or people each one touches 4. How plans should be structured (steps, dates, a check at the end) Ask these in one message, then wait for my answers. For the place our objectives live, check it is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Search Juno first for courses, journeys and content that already support each objective. Draft one plan per person: 3 steps (learn, prepare, execute), content from our library first, dates to the end of the quarter. Show me three examples, then prepare the rest as drafts for managers. Routine: after the first run, offer to repeat this at the start of every quarter, with a mid-quarter check of which plans moved. 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. Plans stay drafts until each manager commits. Don't assign or notify anyone.
Your AI asks you
- Q1My role and the team I support
- Q2The objectives (paste them, or tell me where they live)
- Q3Which teams or people each one touches
- Q4How plans should be structured (steps, dates, a check at the end)
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 quarter. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Close a skill gap the week it appears
Internal first, one external option, the request drafted for the approver.
When it happens
A channel for one target skill
The best current courses and videos, one line on why for each.
When needed
Where the learning budget went this quarter
Spend by provider and by team, the top spenders, and the requests still waiting.
Live viewEvery quarter





















