---
name: one-on-one-meeting
description: Use when asked to plan or run a regular one-on-one between a manager and a direct report — agenda, preparation, feedback, follow-up — as distinct from a skip-level meeting (see skip-level-meeting), which deliberately involves a non-direct-report relationship instead.
---

# One-on-One Meeting

A one-on-one meeting takes place between a manager and one individual
direct report — a private, confidential setting for discussing
work-related topics, usually scheduled regularly (weekly or biweekly) to
keep communication genuinely ongoing rather than only happening when
something urgent forces it.

## Key aspects

- **Agenda** — a clear outline of what will be discussed: project
  updates, performance feedback, and any concerns or challenges the
  employee is facing. An agenda-less one-on-one tends to drift into
  status reporting alone, missing the relationship and feedback purpose.
- **Preparation** — both sides should come ready: the manager reviewing
  the employee's recent work and relevant data, the employee arriving
  with real questions or concerns rather than improvising in the moment.
- **Communication** — an open, honest, two-way discussion: the manager
  gives constructive feedback and guidance while genuinely listening to
  the employee's input, and the employee is encouraged to ask questions
  and give feedback in the other direction too.
- **Follow-up** — the manager follows up on action items or feedback
  raised, which is what actually demonstrates the manager is invested in
  the employee's success rather than treating the meeting as a box to
  check.

## Why the cadence matters

Regular scheduling (not just "as needed") is what lets a one-on-one catch
small issues while they're still small — identifying and addressing
concerns early, before they become major problems, is a large part of
the format's value. An irregular or frequently-cancelled one-on-one
signals low priority and tends to erode the trust the format depends on.

## What it builds over time

A consistent, well-run one-on-one improves communication and builds a
genuinely strong working relationship between manager and employee — and
tends to improve engagement and job satisfaction, since employees feel
their input is actually valued and their work actually recognized, not
just evaluated.

## Common pitfalls

- **Letting it become pure status reporting** — a one-on-one that only
  covers project status misses its actual purpose (feedback,
  relationship, concerns); status updates belong in team-level channels,
  not the one dedicated private conversation.
- **The manager doing all the talking** — a one-on-one is meant to be
  two-way; a manager who dominates the conversation misses the employee's
  actual input and concerns.
- **No follow-through on raised concerns** — an employee who raises the
  same issue repeatedly with no visible action stops trusting the format
  and stops raising real concerns.
- **Frequent cancellation or rescheduling** — undermines the trust and
  consistency the practice depends on to actually surface issues early.

## Learn more

- [[skip-level-meeting]] for the related but structurally distinct non-direct-report conversation.
- [[crucial-conversations]] for handling a harder feedback or concern conversation within a one-on-one.