메뉴
Plan and run effective 1:1 meetings between a manager and a direct report (or peer). Use when preparing for a one-on-one, building a recurring 1:1 agenda, or coaching on how to make 1:1s valuable.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | meeting-one-on-one |
| description | Plan and run effective 1:1 meetings between a manager and a direct report (or peer). Use when preparing for a one-on-one, building a recurring 1:1 agenda, or coaching on how to make 1:1s valuable. |
A 1:1 is a relationship and growth conversation, not a status update. The manager's job is to listen, unblock, and develop — not to receive project reports (those belong in team syncs).
The 1:1 belongs to the direct report. They set the agenda. The manager shows up prepared to support.
| Relationship | Recommended Cadence | Duration |
|---|---|---|
| New employee (first 90 days) | Weekly | 45-60 min |
| Ongoing direct report | Bi-weekly | 30-45 min |
| Senior/experienced IC | Monthly | 45-60 min |
| Skip-level 1:1 | Quarterly | 30-45 min |
| Peer 1:1 | Monthly or as needed | 30 min |
Never skip more than two weeks in a row — trust erodes fast.
Maintain a rolling Google Doc or Notion page. Both parties add items before the meeting.
Template:
1:1 — [Name] + [Manager] | [Date]
Employee Topics:
-
Manager Topics:
-
Action Items from Last 1:1:
- [ ]
Notes:
Review action items from last session at the start of every 1:1.
| Anti-Pattern | Why It's Harmful | Fix |
|---|---|---|
| Running a status update | Employee can't raise real concerns | Ban project updates; redirect to async |
| Canceling frequently | Signals they're not a priority | Protect the calendar; reschedule don't cancel |
| Manager dominates | Employee doesn't get heard | Set a timer; manager talks < 40% |
| No agenda | Meeting wanders; wastes time | Shared doc, both add before meeting |
| No follow-through | Erodes trust fast | Track action items; review them first |
| Always surface-level | Misses real issues | Ask "What's really going on?" |
Reserve at least one 1:1 per quarter for a focused career conversation:
Build a growth plan together: specific skills + concrete opportunities to practice them.
Use SBI (Situation → Behavior → Impact):
Then: "I wanted to raise this directly. What's your read on what happened?"
Recognition feedback follows the same format — be specific, not generic:
Plan and run a company or department all-hands meeting. Use when preparing for a quarterly all-hands, town hall, or company-wide meeting where leadership addresses the full organization.
Plan and run a customer meeting — discovery call, demo, business review, or renewal conversation. Use when preparing for any external meeting with a customer, prospect, or client.
Plan and run a daily standup (daily scrum). Use when structuring a daily standup ritual for an engineering team, product team, or any group that runs daily check-ins.
Plan and run a recurring team sync (weekly or bi-weekly team meeting). Use when structuring a team standup, weekly sync, or sprint review meeting for an ongoing team.
Plan podcast episodes — structure, talking points, guest prep, show notes, and distribution strategy. Use when the user wants to create a new podcast episode, prepare for a guest interview, or launch a podcast series.
Plan and deliver high-impact presentations to senior executives and decision-makers — C-suite, VPs, boards, steering committees, and investment committees. Use when a user is preparing to present a strategy, project status, budget ask, proposal, or decision brief to people who are time-pressured and focused on business outcomes.