Most 1:1s collapse into status update. A good prompt forces topics that no other meeting handles: growth, friction, escalations, blockers, the team gossip.
Who this is for
Managers running weekly 1:1s, ICs prepping their manager 1:1, leaders running skip-levels, mentors structuring sessions.
When not to use these prompts
Don’t use these as a script — 1:1s need flexibility. Don’t use them to surface negative feedback for the first time (use a separate ad-hoc).
Prompt anatomy / structure formula
Every prompt should carry six elements:
- Role: who AI plays — chief of staff / manager / analyst.
- Context: team / org / scope / data.
- Goal: one deliverable — plan, memo, talking points, doc.
- Constraints: word count, must-include fields, audience seniority.
- Tone: confident, neutral, factual.
- Examples: 1-2 prior samples to anchor format.
Best for
- Direct report 1:1 prep
- My-1:1-with-manager prep
- Skip-level prep
- Mentor session prep
- Quarterly career conversation
12 copy-ready prompt templates
1. Direct report agenda
For my weekly 1:1 with `{name}` (role: `{role}`), build an agenda: (1) Status (5 min max), (2) Friction or blockers, (3) One growth topic, (4) One signal from elsewhere I should share, (5) Their questions. Cap at 30 min.Variables to swap: name, role
2. Manager 1:1 prep (as IC)
I report to `{manager}`. Prep for our 1:1: (1) Top 1-2 wins to surface, (2) One blocker I need help with, (3) One ambiguity I want clarified, (4) One feedback I want to give, (5) Career topic to nudge.Variables to swap: manager
3. Skip-level prep
Skip-level with `{skipManager}`. Prep: (1) State of my team in 3 bullets, (2) One concern I'd like their input on, (3) One thing they should know happening on the ground, (4) One question about org direction.Variables to swap: skipManager
4. Growth topic per direct
For each direct report, suggest one growth topic for this month's 1:1: based on their level / recent work / aspirations. Skip generic "career growth".5. Hard conversation prep
I need to give `{name}` direct feedback on `{topic}` in our 1:1. Prep: (1) Observation (specific behaviour), (2) Impact, (3) Ask (what to change), (4) Support I'll offer. Tone: care + candor, not soft.Variables to swap: name, topic
6. Friction-surfacing questions
Build a short list of 1:1 questions that surface friction (not status): "What's the most frustrating thing this week?", "What would you change if you could?", "Where do you feel stuck?". Pick 3 to rotate.7. Recent-work coaching
My direct shipped `{project}` last week. Prep a 1:1 segment: (1) Acknowledge specifically, (2) Ask reflection question (what they'd do differently), (3) One coaching point tied to next project.Variables to swap: project
8. Quarterly career conversation
It's the quarterly career 1:1. Build agenda: (1) Last quarter's growth signals, (2) Current trajectory + name level / scope, (3) Next-quarter focus + 1-2 specific skills, (4) What support / opportunities they need.9. Distributed-team 1:1
My direct is in `{timezone}`, async-first. Adapt the 1:1: shorter, more written prep, asynchronous follow-ups for topics that don't need live discussion.Variables to swap: timezone
10. New-hire first 30/60/90 1:1
New hire on day 7 / 30 / 90. Build 1:1 agenda per milestone: (1) what they should be doing by now, (2) signals to watch, (3) calibration question. Don't reuse same agenda.11. 1:1 follow-through tracker
List my last 4 weeks of 1:1 notes. Extract: action items I committed to, action items they committed to. Flag anything unresolved > 2 weeks. Drag it to today's agenda.12. 1:1 hygiene audit
Audit my 1:1s for: (1) Always running status-only? (2) Same topic every week? (3) I talk > 60% of the time? (4) No growth conversation in 6 weeks? Output a fix list.Common mistakes
- No specific context — output is generic.
- Skipping fact-check — AI invents numbers.
- Vague audience — over/undershoots seniority.
- No word limit — readers won’t finish.
- Same template every situation — readers tune out.
- No “decision needed” framing.
- Forgetting to attach source data.
How to push results further
- Specify audience level.
- Cap length: 1-page tactical, 3-bullet executive.
- Lead with the ask / decision needed.
- Attach source data link.
- Read aloud before sending.
- AI drafts; humans review.
- Save best examples; reuse format, refresh content.
Practical depth notes
Use these prompts as starting points, not final answers. For One-on-One Preparation Prompts: 12 Templates Beyond “Anything on Your Mind?”, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How long should this doc be?: Tactical: 1 page. Executive: 3 bullets + link.
- Can AI replace the analyst / manager?: Drafts and templates yes; judgment no.
- How often refresh?: Cadence-driven; adjust when audience signals fatigue.
- Should risks be included?: Always. Pretending no risk exists erodes trust.
- How to fact-check?: Attach sources; peer review numbers.
- Can AI generate data?: No — AI invents plausible numbers. Connect real data.
Related
- Meeting agenda prompts
- Action item extraction prompts
- Weekly report prompts
- Decision summary prompts
- Productivity & Office Prompts hub
Tags: #Prompt #Productivity #One-on-one