Updated 2026-09-09

How to Run Effective 1 on 1 Meetings

Most 1:1 advice ends when the meeting does. Yours shouldn't.

If you're working out how to run effective 1 on 1 meetings, start with the next one. Can you open it without making your direct report repeat the problem? Do you remember what you promised? A good 1:1 leaves both of you with enough of a record to pick up where you stopped.

Start with last time

Before you think of a clever question, read the notes from your last 1:1. Check what you said you'd do, what they were going to do, and what neither of you had resolved yet.

That sounds obvious. Managers still skip it. The result is a friendly conversation with a small insult tucked inside: your direct report has to remind you about the introduction, decision, or difficult subject they already handed you.

Keep one shared page for each person. Google Docs, OneNote, Notion, or whatever your company already uses is fine. It only needs four parts:

SectionWhat goes there
From last timeDecisions and promises that need an update
Their topicsWhat your direct report wants to use the time for
Your topicsContext, feedback, or questions you need to bring
Next timeOwners, dates, and anything you agreed to reopen

Read the page before the meeting and add your topics. Leave room for theirs. If the information is already in Jira or the team channel, don't make them read it back to you. A 1:1 is expensive time to spend on status reporting.

Keep the meeting recurring. Weekly and every other week can both work. If an every-other-Thursday meeting gets canceled, though, four weeks pass before you talk again. Move it instead of quietly dropping it.

Let them go first

Open by closing the old loop: "Last time I said I'd check the staffing plan. I did, and here's what I learned." If you didn't do it, say so. Don't wait for them to ask.

Then try, "Where should we start?"

When you get a thin answer, skip the giant list of 1:1 questions. Ask about something you noticed:

  • "You said the handoff was rough last time. Is it any better?"
  • "You seemed unsure about the new role. What still feels unclear?"
  • "What are you waiting on from me?"

Give them a few seconds. Silence often means they're deciding whether to give you the safe answer or the useful one.

Your topics come next unless something cannot wait. Bring context they can't get from a ticket, including a change in priorities or feedback that is easier to understand in conversation. Ask how you're doing as their manager too.

Don't push for personal detail. If they mention family or health because it affects the week, let them choose how far that conversation goes. You have more power in the room, even when the chat feels casual.

Say the promises out loud

Save the last few minutes for the boring part. It is usually the part that keeps the meeting from disappearing.

Read back what you heard:

  • "I'll get you an answer on access before our next 1:1."
  • "You'll draft the proposal we discussed."
  • "We'll come back to the workload question next time."

Include your own promises. A record containing only the employee's tasks is a manager's checklist for somebody else. Don't make them chase you.

Ask, "Is that how you heard it?" If a date matters, write it down. If nobody named a date, don't add one later because it makes the recap look neater.

Write down less

The shared note doesn't need to be minutes. Keep the decisions, promises, and open questions you just confirmed. Leave out the transcript, the personal asides, and your private reading of someone's mood.

"Wants a decision on the rotation" can go on the shared page. "Seems disengaged and may be planning to leave" is your interpretation. Turning that guess into durable employee data changes the relationship, especially if nobody knows you're doing it.

Use the AI summary as a draft. Read it once, then move only the agreed items into the shared page. If the conversation needs formal documentation, use the HR process your company has approved.

Short notes are easier to use. Before the next 1:1, you should be able to scan one screen and remember where you left off. That's enough.

Use Pastok without making it weird

Ask before you record. Say what the recording is for and what you'll share afterward. A quiet device is still a recorder.

You could say:

I use Pastok to draft the decisions and follow-ups so I don't have to type while we're talking. I'll check the result and put only what we agree on in our shared page. Are you okay with that? If not, I'll take light notes.

If they say no, put the watch away. Check your company's policy too. Both of you should know what will end up in the shared page.

Once they agree, the Pastok workflow is short:

  1. Tap the Pastok complication on your Apple Watch to start. The laptop can stay closed.
  2. After the meeting, run a Custom Skill that drafts the handoff.
  3. Review the draft while the meeting is still fresh, then copy the agreed decisions and promises into the shared page.
  4. Before the next 1:1, ask Chat what you still owe this person or which subject you agreed to revisit.

Use a narrow prompt for the Skill:

Draft a follow-up for this 1:1. Include decisions, commitments I made, commitments the other person made, dates we stated, and subjects to reopen next time. Leave out empty sections. Do not infer mood, personality, performance, or intent.

Pastok does the first pass because rebuilding an hour from memory is lousy work. You still decide what belongs in the shared page. This works especially well in person, on a walk, or anywhere opening a laptop would make the conversation worse.

Use Pastok to draft the follow-up

Start capture after the person agrees. Review the Skill output, then put only the decisions and promises you both recognize into the shared page.

Try Pastok

Related

Use Pastok to draft the follow-up

Start capture after the person agrees. Review the Skill output, then put only the decisions and promises you both recognize into the shared page.

Try Pastok