How to Run 1:1s That Aren't Awkward

The short answer

One-on-ones feel awkward when they have no structure and no clear owner. Fix it by giving the meeting a loose, consistent shape — a brief check-in, the report's priorities and blockers, your feedback, and career or growth — and by preparing one or two specific things to discuss instead of improvising. The best 1:1s are owned mostly by the report, run on a consistent cadence, and prepared for rather than winged. Awkwardness is almost always a structure problem, not a chemistry problem.

Why 1:1s go awkward

Three patterns account for most awkward one-on-ones. The meeting has no agenda, so both people improvise and it stalls. The manager dominates it, so it becomes a broadcast rather than a conversation. Or it collapses into a status update — information the manager could have gotten from a project tool — and both people quietly wonder why they are meeting. None of these are about the two people not getting along. They are about the meeting having no design.

Give the meeting a shape

A 1:1 does not need a rigid agenda, but it needs a loose, repeatable shape. A reliable one: a short personal check-in, then the report's priorities and blockers (this should be most of the meeting), then your feedback and updates, then a periodic look at growth and career. Consistency matters more than perfection — the same shape every time means neither person has to wonder how to start.

Let the report own most of it

The single biggest upgrade is handing the agenda to the report. It is their meeting; you are there to unblock, coach, and connect the dots. Ask them to bring two or three things. When the report drives, the 1:1 stops being a performance and becomes useful — and the awkward silences disappear because the person with the most to say is the one steering.

Prepare for the specific person

Awkwardness also eases when you walk in with something real to discuss. Come with one specific piece of feedback, one question about their work, or one thing about their growth — and frame it the way this person best receives it. Someone who needs processing time should get the topic in advance; someone direct wants you to just say it.

That preparation is what PeoplePrints is built to support. Its Pre-Meeting Blueprint gives you a one-page read before a 1:1 — a suggested opening for this specific person, what they tend to need to hear and to feel, and where the conversation is most likely to stall — from one data point you already have on file, no test required. It does not script the meeting; it means you are not staring at a blank agenda.

Frequently asked questions

How often should you have 1:1s with direct reports?

Weekly works well for most teams; bi-weekly can be realistic for managers with many reports. The key is consistency — a 1:1 that gets cancelled often signals to the report that the time is not really theirs.

What should you talk about in a 1:1?

Let the report set most of the agenda — their priorities, blockers, and concerns. Add your feedback, relevant updates, and a periodic look at growth and career. Keep pure status reporting out of it; that belongs in a project tool.

Why do my 1:1s feel so awkward?

Almost always because the meeting has no shape or no clear owner. Give it a consistent loose structure, hand the agenda to the report, and come prepared with one specific thing to discuss. Awkwardness is a design problem, not a chemistry problem.

Should 1:1s be casual or structured?

Both — a consistent light structure with a relaxed tone. Structure removes the 'how do we start' friction; an informal tone keeps it human. You are aiming for a dependable rhythm, not a formal review.

PeoplePrints generates a tactical Blueprint for the hard conversations managers walk into — interviews, performance reviews, and conflict mediation — from one data point you already have on file. See a sample Blueprint.

Why 1:1s go awkward

Give the meeting a shape

Let the report own most of it

Prepare for the specific person

Frequently asked questions

Your next hard conversation is already on the calendar.