one_on_one_meetings v1.0.0

---

name: one_on_one_meetings description: Run recurring one-on-one meetings between a manager and a direct report that build trust and get blockers cleared early: set a protected cadence, let the report own a shared running agenda, keep one continuity note across meetings, track every commitment to done, rotate in career and feedback topics, and handle first 1:1s, quiet reports, venting, and cancellation spirals. Use when setting up, running, preparing for, or fixing 1:1s with a direct report, a manager, a mentor, or a skip-level partner.

---

One-on-One Meetings

Purpose

Make the recurring 1:1 the most reliable hour in a working relationship. The report leaves feeling heard, with blockers named, help committed, and nothing important left to memory. The manager leaves knowing what is actually going on, weeks before it shows up in results.

This skill covers one recurring pair. For designing a whole organization's meeting system use a meeting system skill. For running a group meeting use a facilitation skill. For a one-off prep brief use a meeting prep skill.

Workflow

1. Set the contract at the first meeting

• Say plainly whose meeting it is: the report's. The manager facilitates, listens, and removes obstacles. The report drives the agenda.

• Agree the cadence and protect it. Weekly 30 minutes is the default that research and practice keep landing on. Biweekly 45 to 60 minutes works when the pair already talk daily. Monthly is too sparse: recent weeks crowd out everything earlier, and small problems age into big ones.

• Agree the cancellation rule up front: reschedule, do not cancel. If a week truly breaks, hold a 15 minute version rather than skipping. Every cancellation teaches the report where they rank.

• Agree where the shared note lives (step 3) and who can see it. Default: visible to the two of you only. Say so out loud, because candor dies if the report suspects the note is a performance file.

• Use the first meeting to learn how the person works, not to review their work. Question set: references/first-one-on-one.md.

2. Let the report own a shared running agenda

• Keep one running agenda document per pair, not a fresh doc per meeting. Both people drop items into it during the week as things occur to them. An item written down on Tuesday does not need a Slack ping on Tuesday.

• The report orders their items. The manager adds theirs last and keeps them few: a blocker they can clear, context from above, one piece of recognition with a specific example.

• If the agenda is empty, that is data, not a free pass to cancel. Fall back to the standing prompts in references/question-bank.md and find out why nothing felt safe or worth raising.

• Ban the status recital. Work status belongs in the project tracker, the standup, or an async update. If status keeps taking over the 1:1, name it and move it out. Time in this meeting goes to what status tools cannot carry: judgment calls, friction, priorities that conflict, and how the person is doing.

3. Run the meeting in five beats

For a 30 minute meeting (scale the beats, keep the order, for 45 or 60):

1. Check-in (about 5 min). Start with what is going well, then a real temperature check: workload, energy, anything outside work affecting focus, if they want to share it. Start here and the rest of the meeting gets more honest.

1. Their agenda (about 15 min). Work the report's items in their order. Listen more than you talk. A useful self-check: if the manager spoke more than the report, the meeting probably failed its main job. Ask, then stay quiet long enough for the full answer.

1. Blockers (about 5 min). For each stuck item, classify it before solving: missing decision, missing resource, missing information, or conflict with another person or team. Each class has a different fix, and managers waste weeks applying the wrong one. Spot blockers early with the signals in step 6.

1. Manager items (about 3 min). Context, recognition, admin with dates. Keep it short. Anything long becomes a separate meeting or a written update.

1. Close (about 2 min). Read back every commitment made in the room, with owner and date, and write it into the note before you stand up. End by asking what has not been discussed that should have been. That last question is where the real item often appears.

4. Keep one continuity note, and open with it

• One document per pair, newest meeting on top, same sections every time. Template: references/continuity-note-template.md.

• Open every meeting by closing the loop on the last one: read the open commitments from the previous note and mark each done, moved with a new date, or dropped with a reason. Two minutes. This single habit is what separates a 1:1 series from a string of unrelated chats.

• Write notes during or immediately after the meeting, in the shared doc, in plain language the report would agree with. No secret second set of notes about the same conversation. If something must be recorded privately for a formal process, that belongs in that process, not hidden inside the 1:1 note.

• Keep a running section at the bottom of the note for slow-moving threads: career goals, skills being built, recurring frustrations, personal context the report chose to share (a new baby, a house move, a course they are taking). Review it before each meeting. Remembering the thread is how trust compounds.

5. Track commitments like debts

• A commitment has four parts: what, one owner, a date, and where completion will be visible. "I will look into it" has none of the four. Rewrite it in the room.

• Track both directions. Manager commitments (unblock this, ask that director, review this doc by Thursday) matter more than report commitments, because the report is watching whether the manager's word holds. A manager who misses twice without comment should expect the agenda to go quiet.

• Use scripts/track_commitments.py to keep a ledger per pair and flag overdue items before the next meeting:

bash
python3 scripts/track_commitments.py --file ledger.json add --owner manager --what "Ask director about contractor renewal" --due 2026-10-20
python3 scripts/track_commitments.py --file ledger.json add --owner report --what "Draft migration plan outline" --due 2026-10-22
python3 scripts/track_commitments.py --file ledger.json list --overdue --today 2026-10-21
python3 scripts/track_commitments.py --file ledger.json done --id 1

• When a commitment slips, the owner raises it before the other person has to. Renegotiating a date early is normal. Going silent is the failure.

6. Spot blockers and trouble early

Treat these as agenda items even when the report does not:

• Language shift. "Fine" and "busy" replacing specific answers, two meetings in a row. Ask what changed, and accept a partial answer without pushing.

• Shrinking agenda. Items get shorter and safer over a month. Usually means something raised earlier was dismissed, mocked, or acted on without credit. Repair that moment directly.

• Surprise risk. You hear about a delay, a conflict, or a resignation risk from someone else first. The 1:1 is not carrying real news. Ask what would make it easier to bring bad news early, then prove the answer with your reaction to the next piece of bad news.

• Repeat blocker. The same obstacle three meetings running means the fix was wrong or nobody with the authority to fix it has been engaged. Escalate it yourself, with a date, and report back.

• Energy drop with no work cause. Raise workload and sustainability directly. Agree one concrete reduction or deferral, owned by the manager, rather than offering sympathy and the same workload.

7. Rotate the long-horizon topics

Weekly meetings drift toward the urgent. Counter it with a rotation: roughly one meeting in four gives most of its time to one long-horizon topic, cycling through:

• Career. Where they want to be in one to two years, and what work this quarter builds toward it. For a structured version use the GROW sequence: goal, current reality, options, what they will do next.

• Growth and feedback for the report. Specific recent work, what it shows about their strengths, one skill to build next and how the manager will create chances to build it.

• Feedback for the manager. Ask directly and reward the answer, especially when it stings. Suggested wording: "What is one thing I do that makes your work harder?" Then do not argue. Report back next meeting on what you changed or why you did not.

• Working relationship reset. Cadence, format, agenda habits: what is working about these meetings, what to change. Ask at least twice a year, and after any change of role, team, or manager.

Note which rotation topic ran and when, in the continuity note, so the rotation actually happens.

8. Handle the hard patterns

• The quiet report. Silence is rarely emptiness. Offer items in writing ahead of time, ask one question and tolerate the pause, and try a walking or chat-based meeting if face to face shuts them down. Never fill their silence with your own status update and call it a 1:1.

• The vent that eats the meeting. Let it run once, fully. Then ask which of these they want: just to be heard, advice, or action from you. If venting becomes the standing format, name the pattern kindly and agree one action per vent topic before the meeting ends.

• The performance problem. Do not ambush: a 1:1 that suddenly becomes a warning destroys trust in every future 1:1. Give day-to-day feedback close to the event, not stockpiled for the 1:1. If a formal performance process starts, say so plainly, explain how it differs from the 1:1, and keep the two separate.

• The cry, the conflict, the disclosure. Stay. Listen. Do not try to fix feelings or play therapist. Agree what, if anything, you will do next, and follow through exactly. If someone discloses something involving safety or harassment, follow your organization's process and tell them what you must pass on before you pass it on, where the rules allow.

• You are the report, not the manager. You still own half this system: bring a written agenda, bring solutions with your blockers, state what you need in one sentence, track your manager's commitments politely in the shared note, and use the rotation topics yourself. A report who runs their side well gets more out of a mediocre manager than a passive report gets from a good one.

• Skip-level 1:1s. Same system, one rule added: support, do not decide. Carry themes upward without names unless the person agrees, and never let a skip-level meeting become an end run around their manager.

Output Contract

When setting up or repairing a 1:1 series, produce:

1. The contract: cadence, length, cancellation rule, note location and privacy, agreed in the first meeting.
2. The shared running agenda and continuity note, one per pair, using references/continuity-note-template.md, with the slow-threads section started.
3. A commitment ledger with every open commitment carrying an owner and a date, checkable with scripts/track_commitments.py.
4. A rotation plan: which long-horizon topic runs in which week for the next four meetings.
5. For a repair job: the diagnosis (which of the failure signals in step 6 or 8 is present), one change to make first, and the meeting at which you will check whether it worked.

Operating Rules

1. Reschedule, never silently cancel. A skipped 1:1 is a message, and the report reads it correctly.
2. The report owns the agenda and speaks most of the time. The manager's main tools are questions, silence, and removing obstacles.
3. No status recitals. If it can be read in a tracker, it does not get meeting time.
4. Every meeting opens by closing the last meeting's commitments. No exceptions, even when the answer is "not done": that is when it matters most.
5. One shared note, written in language the report would sign. No secret parallel notes on the same conversation.
6. Feedback about specific work goes close to the event. The 1:1 is for patterns, growth, and feedback flowing toward the manager.
7. What is said in the 1:1 stays there, except what the pair agrees to carry out, and except safety or legal duties, which you disclose before acting on where you can.
8. Gallup reports that employees whose managers meet with them regularly are almost three times as likely to be engaged as those whose managers do not. Treat that as a reported association, not a promise: the meeting earns its effect by how it runs, not by existing on a calendar.
9. Judge the series monthly with three checks: are commitments closing, is the agenda still bringing real items, and has a long-horizon topic run in the last four meetings. Two failing checks means repair the system, not try harder inside it.