An effective one-on-one belongs to both participants. Keep a shared agenda, invite the employee's topics first, ask about work and support rather than reciting tasks, and leave with clear follow-up. The meeting is useful when it creates context that ordinary project updates miss, not when the manager fills every minute.
Who this is for: People managers holding recurring private meetings with direct reports in office, remote, or hybrid teams.
- Use a shared running agenda so concerns and decisions are captured when they arise, not reconstructed at meeting time.
- Let the employee shape the conversation while the manager listens, tests understanding, and addresses obstacles within their control.
- Record only practical commitments, protect appropriate privacy, and revisit promised actions at the next conversation.
Give the meeting a clear job
A one-on-one is a regular space for matters that need attention, context, or candor. Project dashboards can carry routine status. The conversation can then cover priorities, unclear decisions, working relationships, workload signals, feedback, and development. Explain this purpose when starting the rhythm so the employee knows what belongs there.
Consistency matters more than a polished script. Choose a cadence that fits the work and keep the appointment unless a real conflict intervenes. Repeated cancellation communicates that the conversation is optional. When rescheduling is necessary, offer a new time promptly rather than leaving the employee to request access again.
Prepare without controlling
Maintain a shared agenda that either person can update. Before the meeting, review previous commitments and add questions that require discussion. Do not arrive with a hidden list of criticisms. If a serious performance issue needs a formal process, handle it directly under the organization's policy rather than surprising someone inside a routine conversation.
Open by asking what would make the time useful. An employee may need a decision, a sounding board, context about a change, or simply room to explain an obstacle. Follow the most consequential topic instead of forcing every prepared prompt. A manager can still reserve time for an important issue and say why it matters.
Listen for meaning and action
Ask open questions, then allow enough silence for a considered answer. Reflect back the substance before offering advice: what you heard, why it matters, and what remains uncertain. This reduces avoidable misunderstanding. It also helps distinguish a request for coaching from a request for a concrete managerial decision or resource.
Avoid treating every concern as a problem the manager must instantly solve. Ask what the employee has tried, what options they see, and what support would help. Where the manager owns the obstacle, accept the action plainly. Where the request cannot be met, explain the constraint and discuss realistic alternatives without pretending the concern disappeared.
Close the loop
End by naming decisions, owners, and follow-up. Notes should be proportionate and respectful: capture commitments and work context, not speculative judgments about personality. Follow organizational requirements for records and confidentiality. The employee should not have to guess whether a sensitive point will be shared or what happens next.
At later meetings, begin by checking prior promises. A simple acknowledgement that an action is delayed is better than silence. Periodically ask whether the format, cadence, and topics remain useful. Adjust from the team's experience rather than assuming one manager's preferred template suits every role, career stage, or communication style.
Refocus a status-heavy conversation
A designer's recurring meeting has become a spoken task list, while a dependency problem keeps appearing after decisions are made.
- Move routine task updates to the project board and explain that the private conversation will focus on context, obstacles, feedback, and support.
- Invite the designer to lead with the dependency issue, ask what decision is missing, and reflect the concern before suggesting a response.
- Agree that the manager will clarify ownership with the partner team while the designer documents the affected decision and desired deadline.
- Put both commitments on the shared agenda and review them at the next meeting before opening new topics.
Shared one-on-one agenda
Keep this lightweight record available to both participants and carry unfinished items into the next conversation.
- Employee topics: questions, obstacles, decisions, feedback, development, or context needed.
- Manager topics: information to share, support to offer, and issues requiring direct discussion.
- Conversation notes: key facts, options considered, and decisions made without unnecessary personal speculation.
- Follow-up: action, owner, expected timing, and the point at which progress will be checked.
Common mistakes
- Using the entire meeting for project status that is already visible elsewhere.
- Canceling repeatedly and expecting the employee to keep finding replacement time.
- Offering solutions before confirming whether the employee wants advice, context, advocacy, or a decision.
Try one
A direct report says, 'It feels pointless to raise this because the decision is already made.' How should the manager respond?
A strong response does not defend the process immediately. It asks which decision and experience led to that conclusion, reflects the concern accurately, and distinguishes what can still change from what cannot. The manager should explain the decision boundary, own any missed consultation, agree on a useful follow-up, and avoid promising influence that the employee does not actually have.
Sources
- Atlassian one-on-one playA practical format for recurring conversations between managers and team members.
- CIPD line management factsheetProfessional guidance on the people-management responsibilities and support needs of line managers.