Use when a manager wants to run better 1-on-1s — moving from status-update check-ins to growth and feedback conversations that build real trust with direct reports. Triggers on: "improve my 1-on-1s", "1-on-1 feels like a status update", "how to have
Use when a manager wants to run better 1-on-1s — moving from status-update check-ins to growth and feedback conversations that build real trust with direct reports. Triggers on: "improve my 1-on-1s", "1-on-1 feels like a status update", "how to have
license
MIT
metadata
{"author":"wondelai","version":"1.0.0"}
scenarios
["My 1-on-1s feel like status updates — help me run them better","I need to have a growth conversation with a direct report who seems stuck","Help me prepare coaching questions for my 1-on-1 with an engineer who wants to go to Staff","1on1이 매번 프로젝트 상태 보고가 되고 있어 — 어떻게 개선해?","직원 성장 대화를 1on1에서 어떻게 이끌어야 해?"]
compatibility
{"recommended":["think-tool"],"optional":[],"remote_mcp_note":"think-tool이 있으면 특정 직원 상황에 맞는 코칭 질문 생성 품질이 높아집니다. Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요."}
Standing Mandates
ALWAYS start with what is on the direct report's mind before the manager's agenda.
ALWAYS separate performance feedback from growth coaching within the same conversation.
NEVER let 1-on-1s default to project status — redirect with open-ended questions.
NEVER give feedback without naming the specific behavior, the impact observed, and an alternative.
1-on-1 Manager Framework
When to Use / When Not to Use
Use when:
1-on-1s have become project status meetings
You want to run a specific growth, feedback, or career conversation
An employee is passive in meetings and you want to change the dynamic
Not for:
IC prep for their own 1-on-1 (use 1-on-1-ic)
Writing a promotion case (use leveling-manager)
Team-wide process or performance issues
Process
Set cadence — weekly, fixed time; never cancel, always reschedule
Create shared doc — employee adds topics; manager adds at the bottom; both review before the meeting
Start with employee's agenda — redirect project status to async channels
Coach, don't tell — lead with "What do you think?" before offering perspective
Track growth — document each employee's growth direction; revisit quarterly
Close the loop — review last meeting's action items at the start of every meeting
Solicit upward feedback — "What's one thing I could do differently?" at least monthly
Output Template
When asked to help with a specific meeting:
Suggested agenda for 1-on-1 with [name]:
1. Follow-through check: [commitments from last meeting]
2. Employee topics (their priority order)
3. Coaching questions for this situation:
- [Question 1 — open, employee-led]
- [Question 2 — growth-focused]
- [Question 3 — feedback invitation]
4. One manager item (if time allows): [topic]
Commitment to document: [specific follow-through item]
What Claude Does / What You Do
Claude
You
Generates coaching questions tailored to the employee's situation
Has the actual conversation; coaching requires human presence
Scores current 1-on-1 practice (0-10) with highest-leverage improvement
Makes judgment calls about what the employee actually needs
Suggests agenda structure for specific meeting types (growth, feedback, returning from leave)
Builds trust through consistency, follow-through, and honesty
Drafts SBI-model feedback statements
Delivers feedback in person with appropriate tone
Identifies if the "empty agenda" pattern is a signal worth investigating
Decides how to respond to what the employee actually brings
Related Skills
../1-on-1-ic/SKILL.md — understand what your ICs are trying to do in the meeting
../leveling-manager/SKILL.md — 1-on-1 growth tracking feeds the promotion evidence log
Core Principle
The 1-on-1 is the most important meeting in a manager's week — and it belongs to the employee, not the manager. A manager's primary job is to make their team successful. The 1-on-1 is the primary instrument for that work: surfacing what the employee actually thinks, removing blockers they won't raise in group settings, investing in their growth, and building the trust that enables honest feedback in both directions.
The foundation: The 1-on-1 has two failure modes. Mode 1: status update theater — the manager asks about projects, the employee reports status, nothing changes. Mode 2: sporadic and cancellation-prone — the signal sent is "your time and development are not my priority." The antidote is a consistent, employee-led meeting with a prepared agenda, focused on the person not the project, with documented follow-through.
Agent Output
When a manager describes their current practice, produce:
Score (0-10) — using the rubric below, rate their practice
Highest-leverage improvement — the single most impactful change they can make
2-3 concrete next actions — specific, with example language they can use in their next meeting
When a manager asks for help running a specific meeting, produce:
Suggested agenda items — tailored to what they've shared about the employee and situation
3-5 coaching questions — specific to the context (not generic GROW boilerplate)
One follow-through commitment to document in the shared doc
Scoring
Goal: 10/10. When evaluating a manager's 1-on-1 practice, rate 0-10. A 10/10 means meetings are weekly, employee-led, focused on growth and blockers, and followed up with action. Always provide the current score and specific improvements needed.
7-8: Regular cadence but manager-led; project status dominates; follow-through is inconsistent
5-6: Meetings happen but are unstructured; no agenda; employee is passive; growth rarely discussed
3-4: Meetings are irregular or frequently cancelled; primarily status updates; no follow-through system
1-2: 1-on-1s rarely happen; employee growth is not tracked; trust is low or unknown
The 1-on-1 Manager Framework
1. Cadence and Structure
Core concept: 1-on-1s should be weekly, 30-45 minutes, at a fixed time. They should never be cancelled by the manager — only rescheduled if truly unavoidable. The message sent by cancellation is "your development is optional." Frequency matters more than duration.
Why it works: Trust and psychological safety are built through consistent, reliable contact. An employee who knows their manager will show up every week, prepared and present, will bring harder problems and more honest feedback. An employee whose 1-on-1s are frequently cancelled learns to deprioritize their own development.
Key insights:
Weekly 30-45 minutes beats biweekly 60 minutes — frequency enables timelier support
Same time, same day — reduce scheduling friction; make it non-negotiable
Never cancel; always reschedule if necessary — model that this is a priority
The employee should arrive knowing the agenda; the manager should arrive having reviewed the last session's notes
Remote-first tip: video on, no multitasking, treat it as the most focused meeting of the week
First 1-on-1 with a new report: invest full time in getting-to-know-you, not tasks
Practice applications:
Context
Pattern
Example
Setting cadence
Weekly fixed time
"Let's block 30 minutes every Tuesday at 10am — this is your standing meeting"
Cancellation policy
Reschedule, never cancel
"I need to move Tuesday's 1-on-1 — can we do Thursday at 10am instead?"
New report
First meeting is relationship, not tasks
"Tell me about your best work experience. What made it great?"
Preparation
Review notes before meeting
"I noted you were concerned about the API timeline last week — how has that evolved?"
Remote cadence
Same presence standards
Video on, door closed, phone away — 30 minutes of full presence
2. Employee-Led Agendas
Core concept: The 1-on-1 agenda belongs to the employee. The manager may add items, but the employee's topics take precedence. A shared doc — updated by the employee before each meeting — is the standard tool. Topics accumulate throughout the week; the meeting works through them in order of the employee's priority.
Why it works: When managers control the agenda, 1-on-1s become another manager-driven meeting. When employees own the agenda, they're incentivized to think about what they need help with and to bring the real issues, not just safe ones. The act of writing topics down also gives employees agency: they're not waiting to be asked — they're preparing to direct.
Key insights:
Shared Google Doc or Notion page: employee adds topics; manager adds topics; both can see in advance
"I don't have anything" is not an acceptable agenda — coach the employee to think about: what's blocking you? what do you want to learn? what feedback do you want? what's on your mind?
If the employee comes with no agenda for several weeks, that is a signal worth investigating
Manager items should be added at the bottom — they get time if employee topics are covered
Status updates should be redirected: "You can update me on that in the project channel — what would you like to talk about?"
The agenda doc becomes the memory of the relationship — track decisions and follow-through items
Practice applications:
Context
Pattern
Example
Agenda setup
Shared running doc
"Here's our shared doc — add topics any time. I'll see them before we meet."
Empty agenda
Coach to generate topics
"What's been on your mind this week? What's felt harder than it should? What do you want to get better at?"
Status update redirect
Redirect to async
"Good to know — post that in #project-updates. What would you actually like to talk about?"
Manager topics
Add at bottom
"I have a question about the Q3 plan — I'll add it at the bottom; let's do your topics first"
Follow-through
Use the doc as memory
"We agreed you'd talk to the platform team by Friday — how did that go?"
3. Coaching Questions
Core concept: The manager's primary mode in a 1-on-1 is asking, not telling. Coaching questions help the employee develop their own thinking, surface what they actually believe, and arrive at their own solutions — which they are far more likely to act on than manager-prescribed solutions.
Why it works: Telling is fast and feels efficient. But employees who are told what to do don't develop judgment, don't build ownership, and don't grow. Coaching builds the employee's capacity to handle similar situations independently. The ROI of one good coaching question is months of compounding growth.
Key insights:
"What do you think?" is the most powerful sentence in a manager's vocabulary
Follow-up: "What have you tried?" → "What did you learn?" → "What would you do differently?"
Avoid leading questions: "Don't you think you should...?" is advice disguised as a question
Silence is a tool: after asking a question, wait. The employee will fill the silence with real thinking.
The GROW model: Goal (what do you want?) → Reality (what's happening now?) → Options (what could you do?) → Will (what will you do?)
When to shift from coaching to advising: "I have a perspective on this — would you like to hear it?" — then get consent
Practice applications:
Context
Pattern
Example
Opening question
Broad, employee-led
"What's on your mind?" or "What would make today's conversation most valuable?"
Problem exploration
Socratic sequence
"What have you tried? What happened? What did you learn from that?"
Growth conversation
Forward-looking
"Where do you want to be in a year? What's one thing that would most accelerate you?"
Feedback invitation
Create safety
"What's one thing I could do differently that would make it easier for you to do great work?"
GROW structure
Full coaching sequence
Goal: "What outcome are you looking for here?" → Reality: "What's the current situation?" → Options: "What are three ways you could approach this?" → Will: "Which will you try?"
4. Growth and Development
Core concept: Every employee should have a documented growth direction — not a formal PIP, but a shared understanding of what they're trying to get better at and why. The manager's role is to actively create growth opportunities: stretch assignments, feedback, sponsorship, and visibility.
Why it works: Employees who feel their manager is invested in their growth are dramatically more engaged and retained. Growth conversations that happen only in annual reviews are too infrequent to drive real development. Integrating growth into the weekly 1-on-1 makes development continuous, not episodic.
Key insights:
Ask in early 1-on-1s: "Where do you want to grow? What kind of work energizes you?"
Document the answer: a shared growth note or section in the 1-on-1 doc
Revisit quarterly: "Is this still where you want to grow? Has anything changed?"
Sponsorship > mentorship: don't just coach — create opportunities, make introductions, advocate in rooms the employee isn't in
Stretch assignments: "I want to give you the chance to lead the next architecture review — here's why I think you're ready, and here's how I'll support you"
Skill gaps should be specific: "You want to grow in technical leadership — the gap I see is structuring technical proposals. Here's how we'll work on that."
Practice applications:
Context
Pattern
Example
Initial growth conversation
Open, employee-led
"What kind of engineer do you want to be in three years? What's most important to you about your work?"
Growth note
Document and revisit
Shared section in 1-on-1 doc: "Growth focus: leading technical design. Next opportunity: own the Q3 API design."
Stretch assignment
Set up for success
"I'm giving you the Q3 planning lead — here's what I'll handle, here's what's yours, here's how we'll check in"
Sponsorship
Advocate externally
"I mentioned your API work to the VP — she wants to hear from you directly. I'll intro you."
Skill gap conversation
Specific and collaborative
"I want to share what I see as a growth edge — and I want to hear if it matches what you see"
5. Feedback and Trust
Core concept: The 1-on-1 is the primary channel for timely, specific feedback — both manager to employee and employee to manager. Feedback that waits for performance reviews is neither timely nor actionable. Trust is built when feedback is honest, specific, two-directional, and followed through on.
Why it works: Employees who receive frequent, specific feedback grow faster and feel more confident. Managers who actively solicit upward feedback build teams that tell them the truth — which is the most valuable intelligence a manager can have. Delayed feedback compounds: a small issue, unaddressed, grows into a large one.
Key insights:
Timely feedback: as close to the event as possible, ideally within 48 hours
Specific feedback: "The way you structured the incident post-mortem made the root cause clear and the action items actionable — that's the bar" not "Good job on the post-mortem"
Developmental feedback: "The area where I'd like to see you grow is..." not "You're bad at..."
Upward feedback: "I'm trying to get better at [X] — what's one thing I could do differently?"
Psychological safety: feedback requires safety — if the employee is afraid of the reaction, feedback won't flow
Trust is built by: doing what you say you'll do, being honest when you don't know, advocating for the employee's interests in rooms they're not in
Practice applications:
Context
Pattern
Example
Timely positive feedback
Specific + near-real-time
"The presentation to the stakeholders yesterday — the way you handled the pushback on the timeline was exactly right"
Developmental feedback
SBI model
Situation: "In yesterday's design review—" Behavior: "you dismissed Chen's concern before she finished" Impact: "it shut down discussion and she didn't contribute the rest of the meeting"
Upward feedback request
Regular, specific
"I want your honest take: is there something I do in our 1-on-1s that makes it harder for you to raise hard things?"
Trust repair
Name the gap directly
"I realize I cancelled our last two 1-on-1s — that sent a bad signal. I want to change that."
Safety check
Test psychological safety
"If something was really bothering you about how the team operates, would you feel comfortable bringing it to me?"
