How to Run 1-on-1s
That Actually Build Trust

Most 1-on-1s are status updates dressed as connection. The manager asks what’s on the person’s plate, the employee reports, and both leave feeling like the meeting was mostly a formality. Here’s how to run 1-on-1s that surface what’s actually going on — before it becomes a problem.

What a Good 1-on-1 Is Actually For

A 1-on-1 is not a status update meeting. If the main content of your 1-on-1s is “here’s what I’m working on this week,” you have a well-intentioned meeting that isn’t delivering its real value. Status updates belong in written async formats — Slack, a weekly update doc, a shared task system. The 1-on-1 is for the things that don’t fit there.

What 1-on-1s are actually for: understanding how the person is doing — not just what they’re doing. Surfacing blockers, frustrations, and concerns before they become disengagement or departure. Building the kind of trust that makes honest feedback flow in both directions. And giving the person your full attention in a way that’s impossible in a group setting.

The most valuable output of a great 1-on-1 is often something you didn’t know you needed to know. The team member who’s quietly considering leaving. The process that’s been broken for three months but nobody raised because it wasn’t worth a Slack message. The early signal on a customer relationship that’s at risk. These only surface in a context where the person feels safe and heard.

The Setup That Makes People Feel Safe to Be Honest

Psychological safety in a 1-on-1 is built over time through consistent behaviour, not declared in a single conversation. The behaviours that build it: following up on things the person raised in a previous 1-on-1 (shows you were listening), acting on feedback when it’s actionable (shows honesty produces results), and being willing to share your own challenges and uncertainties (reciprocal vulnerability).

The behaviours that erode it: making the 1-on-1 feel like a performance review, using what someone shares against them later, cancelling or rescheduling frequently (signals their time isn’t important), and filling the entire meeting with your own agenda.

A practical setup principle: the 1-on-1 belongs to the employee, not the manager. Their agenda first, always. The things you want to cover go at the end, after you’ve given them space to say what’s on their mind. This shift alone — from manager-led to employee-led — changes the quality of what surfaces.

The Questions That Get Beneath the Surface

The questions that produce honest, useful answers are open-ended, forward-looking, and focused on the person’s experience rather than their task list.

“What’s on your mind?” — the simplest and most effective opener. Not “how are things going?” (which invites “fine”) but a genuine invitation to share whatever is actually present for them.

“What’s been the hardest part of your work in the last two weeks?” — normalises difficulty and creates space for honest reporting without feeling like a complaint.

“Is there anything slowing you down that I could help remove?” — specific ask for blockers that frames you as a resource, not an evaluator.

“What would make your work feel more meaningful?” — surfaces motivation and alignment issues before they become disengagement.

“What’s something I could be doing differently as a manager?” — the question most managers never ask. Ask it genuinely and act on the answer, and the trust it builds is disproportionate to the discomfort of asking it. See our feedback playbook for how to create the conditions where this kind of exchange is possible.

How to Give Feedback in 1-on-1s Without Derailing Them

Small, real-time feedback belongs in 1-on-1s. Major corrective feedback or performance discussions do not — those require their own dedicated conversation with preparation on both sides. Mixing them creates a dynamic where the employee starts dreading 1-on-1s as potential ambush sessions, which kills the psychological safety the meeting depends on.

When giving feedback in a 1-on-1: be specific (behaviour, not character), be direct (don’t bury the point in cushioning), and make it actionable (what would better look like?). And always ask for their read before giving yours — “I wanted to share some thoughts on X, but first I’m curious how you felt it went?” often reveals that they already know, which makes the conversation collaborative rather than corrective.

What to Do With What You Hear

The fastest way to kill the value of 1-on-1s: hearing what someone shares and doing nothing with it. If someone raises a process frustration and three weeks later it’s unchanged, the implicit message is “your input doesn’t change things.” That person stops sharing the things that matter.

Keep a simple running note for each direct report — a shared doc or even a personal note — that tracks what they raised, what you said you’d do, and what actually happened. Review it before each 1-on-1. Following up on the previous conversation (“last time you mentioned X — have things improved?”) signals attentiveness and closes the feedback loop that makes honesty worth the risk.

Cadence and Format

For most early-stage teams: weekly 30-minute 1-on-1s with direct reports, biweekly for more senior people who operate more independently. Monthly is usually not enough frequency to catch emerging issues before they compound. The format: no formal agenda required, but a shared doc where either party can add items before the meeting helps avoid the “so, anything on your mind?” cold start.

Walking 1-on-1s (literally walking while talking) consistently produce more candid conversations than desk-to-desk meetings. The absence of eye contact reduces social pressure and the movement itself reduces defensiveness. For remote teams, video-off audio calls produce a similar effect.

---

Get 50 more prompts for people ops, team management, and culture — free.