# One-on-One Meeting

A recurring private conversation between a manager and team member focused on context, support, feedback, growth, and the working relationship.

- Type: practice
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/one-on-one-meeting/>)

## What it means

A one-on-one meeting is protected time for a manager and an individual team member to exchange information that may not surface in group settings. The employee’s priorities should shape much of the agenda, while the manager ensures that expectations, wellbeing, development, and organizational context are not neglected. It is not simply a status report.

## Why it matters

Regular conversations help managers notice obstacles, unclear priorities, relationship strain, and development needs before they become expensive surprises. They also give employees predictable access to context and support. Consistency matters because trust is built through repeated attention and follow-through, not through an occasional intensive conversation after a problem emerges.

## When to use it

Hold one-on-ones on a reliable cadence suited to the role, experience, and pace of change. Increase frequency during onboarding, role transitions, difficult delivery periods, or significant organizational change. Use other channels for urgent issues rather than saving them for the next scheduled meeting.

## How it works

1. Maintain a shared agenda where both participants can add topics before the meeting.
2. Begin with the person’s most important concern, listening for context rather than rushing toward advice.
3. Discuss priorities, obstacles, relationships, workload, feedback, and growth at an appropriate rhythm.
4. Ask open questions, distinguish coaching from decisions, and state clearly when the manager must set direction.
5. Record commitments and sensitive notes carefully, respecting privacy and organizational record requirements.
6. Follow through promptly and periodically review whether the cadence and format remain useful.

## A practical example

A designer uses a weekly one-on-one to raise repeated late changes from a partner team. The manager asks for examples, helps separate a process issue from a relationship assumption, and agrees to clarify decision deadlines with the partner lead. At the next meeting, they review whether the intervention worked and discuss how the designer can lead future alignment directly.

## Where it breaks

A private meeting can reinforce manager dependence if every problem is solved upward. It is not confidential in an absolute sense; managers may need to act on safety, harassment, or legal concerns and should explain those boundaries. One-on-ones also cannot compensate for unfair systems, absent career paths, or chronically unmanageable workloads.

## Common mistakes

- Turning the entire conversation into project status that could be handled asynchronously.
- Frequently canceling or rescheduling, signaling that the employee’s concerns are optional.
- Collecting personal disclosures without clear purpose, privacy boundaries, or follow-through.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/one-on-one-meeting/#visualization-one-on-one-meeting>)

## Sources

1. [One-on-One Meetings: Best Practices Guide](<https://www.gvsu.edu/cms4/asset/8C0B809B-0726-4E3B-1EBA4A40A82D8597/1-1_meeting_guide.pdf>) — Grand Valley State University · University management guide
2. [One-to-One Meetings: Guidance for Managers](<https://www.gre.ac.uk/__data/assets/pdf_file/0027/132759/One-to-One-Meetings-Guidance-for-Managers.pdf>) — University of Greenwich · University management guidance

## Related topics

- [Feedback Culture](<https://wiki.soroush.uk/topic/feedback-culture/>)
- [Delegation](<https://wiki.soroush.uk/topic/delegation/>)
- [Competency Matrix](<https://wiki.soroush.uk/topic/competency-matrix/>)
