A one on one meeting is a scheduled private conversation between a manager and a direct report. It focuses on priorities, development, feedback, and removing roadblocks before they become bigger problems. Done well, it is not a status update squeezed into a calendar slot. It is a regular working conversation that protects attention, trust, and follow-through.
Think of it as a recurring tune-up for the working relationship and the workload. The manager gets a clearer view of what is blocking progress. The employee gets space to raise issues, ask for support, discuss development, and give feedback upward. When managers treat this time like just another meeting, the things that matter are usually the first things to disappear.
What is a one on one meeting?
A one on one meeting is a recurring private meeting where the agenda is centred on the employee and the working relationship, not only on the manager’s task list. It gives both people a predictable place to discuss current work, blockers, feedback, career goals, workload, and any concerns that are easier to raise in private than in a team setting.
The meeting is usually between a manager and a direct report, but the format can also be used between peers, mentors, project leads, or skip-level leaders. The core idea stays the same: two people protect time for a focused conversation that would otherwise get lost in chat messages, team stand-ups, or formal review cycles.
A good one on one creates fewer surprises later. Performance reviews become more accurate because feedback has not been saved up for months. Development conversations become more practical because they are connected to live work. Blockers become easier to resolve because they are raised while there is still time to act.
What should a one on one meeting cover?
The content should reflect the person and the moment, but most useful one on ones cover four broad areas. They start with how the person is doing, move into current work and blockers, leave room for feedback or development, and end with clear next steps. The shape is simple, but the value comes from making it consistent.
A personal check-in helps the manager understand whether anything is affecting focus, energy, or workload. It does not need to become deeply personal. A short question about how the week is going can be enough if the manager listens properly. Current work and blockers then give the conversation a practical anchor. This is where unclear ownership, missing decisions, or dependency issues surface.
Development and feedback should appear regularly, not only during review season. That might mean discussing a skill the employee wants to build, a stretch opportunity, feedback from a recent project, or a pattern the manager has noticed. The meeting should end with actions that both people understand. If nobody owns the next step, the conversation has not finished.
How does a one on one meeting work in practice?
In practice, the meeting works best when both people can add to the agenda before it starts. The employee should usually lead with what matters to them, because the meeting is one of the few recurring spaces designed around their perspective. The manager can add context, ask questions, remove blockers, and raise feedback that should not wait.
For example, a designer might bring a blocker about delayed research results. The manager can help identify the right stakeholder, agree who will follow up, and record the action. A problem that was floating around as frustration becomes a visible task with an owner. That is the practical value of the meeting: it turns vague friction into something that can be resolved.
An engineer might raise an API dependency that is slowing deployment. The manager may not solve the technical issue directly, but they can escalate the vendor conversation, align priorities with another team, or create space for the engineer to focus. The meeting works when the spoken problem becomes a clear next step rather than a repeated complaint.
How often should one on one meetings happen?
Weekly meetings are common because they keep alignment tight and make it easier to catch problems early. They work especially well for new hires, fast-moving projects, managers with new teams, or employees who need more coaching. A weekly rhythm also makes the meeting feel normal rather than exceptional.
Fortnightly meetings can work for experienced employees who have stable responsibilities and fewer dependencies. They give more room for development and reflection, but they can also allow blockers to sit for too long if the work is changing quickly. Monthly meetings are usually too infrequent for a direct manager relationship unless there are other strong communication routines in place.
The cadence should change when the work changes. During onboarding, a manager may meet more often. During a performance improvement period, the meeting may become more structured and frequent. When a senior employee is operating independently, the meeting may become less frequent but deeper. The important point is to make the change explicit rather than quietly cancelling until the habit disappears.
How is a one on one meeting different from other meetings?
A one on one meeting is different because it is private, recurring, and relationship-based. It is not a team meeting, where the focus is group coordination. It is not a performance review, where the focus is formal assessment. It is not a project stand-up, where the focus is immediate task status. It can touch all of those areas, but it should not collapse into any one of them.
| Meeting type | Main purpose | Risk if confused with a one on one |
|---|---|---|
| One on one meeting | Private alignment, development, feedback, blockers, and working relationship health. | The meeting becomes too broad if it has no owner, agenda, or follow-up. |
| Performance review | Formal assessment, rating, compensation input, and documented performance decisions. | Employees may feel every one on one is evaluative and stop speaking candidly. |
| Team meeting | Shared updates, coordination, planning, and group decisions. | Private concerns, feedback, and individual development topics get missed. |
| Skip-level meeting | Upward visibility, broader organisational patterns, and feedback beyond the direct manager. | It can bypass the direct coaching relationship if used as a substitute. |
The boundaries matter because employees need to know what kind of conversation they are in. A one on one can include feedback, but it should not feel like a hidden performance review. It can include project updates, but it should not become a private stand-up. It can surface wider issues, but it should not replace formal HR routes when a case needs escalation.
What variants of one on one meetings exist?
Not every one on one needs the same shape. A coaching-focused meeting spends more time on skill growth, feedback, experiments, and career planning. This is useful when an employee is building capability or preparing for a larger role. The manager may ask more reflective questions and agree a small practice task before the next meeting.
Onboarding one on ones are usually more frequent and more structured. A new hire needs help understanding systems, norms, priorities, stakeholders, and expectations. These meetings are less about broad career reflection and more about reducing confusion quickly. The manager should expect more practical questions and should use the meetings to check whether the new employee knows where to find information.
Performance-focused one on ones are narrower and more documented. They may be needed when expectations are not being met or when a formal improvement plan is in place. These meetings require clearer records, specific goals, and appropriate HR involvement. Peer one on ones are different again. They are lateral conversations used for alignment, informal mentoring, and mutual problem solving rather than line management.
When should managers start, stop, or change one on ones?
Managers should start regular one on ones when a new employee joins, when the manager changes, when work becomes more complex, or when the team is moving through change. They are especially useful when responsibilities are unclear, blockers are rising, or engagement seems to be dropping.
Meetings should change when they become stale. If every conversation is a status update, the agenda is probably too manager-led. If action items never close, the follow-up process is weak. If one person keeps cancelling, the meeting may no longer be protected as real work. A short experiment can help: change the cadence, shift the agenda owner, or focus the next few meetings on one theme.
Stopping one on ones entirely is rarely the right first move in a manager-direct report relationship. Reducing frequency may make sense for a very independent employee, but a complete stop removes a regular channel for feedback and escalation. If the meeting feels unnecessary, first ask what it is failing to do.
How should one on one notes be handled?
Notes should be useful without becoming a surveillance record. The best notes are short, factual, and focused on actions, decisions, blockers, and agreed follow-up. They should not become a diary of every personal detail shared in the conversation.
Managers and employees should agree where notes live, who can edit them, and who can see them. Some teams use a shared document. Others use a manager-owned note with employee access. Either can work if the rules are clear. Sensitive topics such as medical issues, legal concerns, disciplinary matters, or compensation issues should follow formal HR channels rather than being buried in ordinary meeting notes.
For sensitive records, teams should follow the organisation’s Security and Data Protection guidance. If notes connect to project work or people processes, system access and retention rules should be intentional, not accidental.
How do one on ones connect with HR and payroll processes?
Most one on one conversations should stay informal and practical. Sometimes, though, a conversation triggers a formal process. A compensation concern, contract question, leave issue, performance problem, or workplace conduct matter may need HR involvement. The manager should recognise when the conversation has moved beyond coaching and into case handling.
When that happens, the issue should move through the right route. A compensation concern should not sit indefinitely in a shared one on one note. A leave or payroll issue should not be promised informally if it requires payroll review. Managers should use established HR and payroll paths so the right approvals, records, and privacy controls are applied.
What common problems should managers avoid?
The most common problem is letting one on ones become status updates. Status matters, but if the whole meeting is a task report, employees stop bringing development, feedback, or concerns. Managers can reset this by asking better questions and letting the employee set the first agenda items.
Frequent cancellation is another warning sign. Cancelling once is normal. Cancelling repeatedly tells the employee that the conversation is optional. If time is tight, a short consistent meeting is usually better than a long meeting that keeps disappearing.
Inconsistent notes also create problems. If actions are agreed but never written down, the same blockers return. If notes are too detailed or too personal, trust can suffer. A lightweight note style works best: what was discussed, what was decided, who owns the next step, and when it will be reviewed.
What should a new manager do in the first 30 days?
A new manager should schedule recurring one on ones with every direct report early. The first conversation should cover working preferences, current priorities, role expectations, communication habits, and what the employee wants from the meeting. This is also the moment to agree cadence, note location, confidentiality boundaries, and how agenda items will be added.
The first month should not be over-engineered. The manager is trying to build a stable rhythm and understand the work. Useful early questions include what is going well, what is harder than it should be, what decisions are blocked, and what the employee wants to develop next. The answers give the manager a map of where support is needed.
By the end of the first month, the manager should be able to see whether meetings are happening consistently, whether actions are being closed, and whether the employee is bringing substantive topics. These signals are not a policing tool. They simply show whether the meeting is useful enough to earn its place on the calendar.
How should teams measure whether one on ones are working?
Measurement should stay light. A one on one is a human conversation, not a compliance form. Still, a few signals can show whether the habit is healthy. Rising cancellation rates, repeated unresolved actions, and empty notes suggest the meeting is not working as intended.
Qualitative signals matter more than perfect metrics. Healthy one on ones produce candid conversations, clearer ownership, fewer surprise escalations, and visible development steps. If an employee starts raising problems earlier, asking for feedback more directly, or taking on new responsibilities with better support, the meeting is probably doing useful work.
Managers should periodically ask whether the meeting is still useful and what should change. A short reset every few months prevents the ritual from going stale. The answer may be a new cadence, a different agenda structure, or a stronger focus on development for a while.
What should teams focus on now?
Start by checking whether one on one meetings are clearly defined in your organisation. Managers should know the purpose, expected cadence, note rules, and escalation route. Employees should know what they can bring to the meeting and how actions will be followed up.
Then look for one weak point. It may be repeated cancellations, unclear notes, status-only conversations, or sensitive issues being handled in the wrong place. Fixing one of those problems will usually improve the whole practice faster than rolling out a new template.
A practical next step is to choose one Fhreteam and review the last month of one on ones. Check whether meetings happened, whether actions were recorded, and whether any issue should have been escalated to HR, payroll, or another formal process. Use that review to simplify the meeting habit, not to make it heavier.