Business Insights

How to conduct one-on-one meetings with employees: structure, frequency, and common mistakes

A one-on-one is a regular individual meeting between a manager and an employee. Its purpose is not to check a list of completed tasks or hold a mini-meeting about current projects. This conversation is meant to help understand how the employee is coping with their work, what is getting in their way, what support they need, and how they would like to develop.

When structured properly, one-on-one meetings help identify overload, misunderstandings, declining motivation, and process-related problems earlier. At the same time, the employee gets a space where they can discuss issues that may be difficult to raise during a team meeting.

For these conversations to be genuinely useful, three things matter: regularity, a clear structure, and the manager’s ability not to turn the meeting into one-sided control.

Why one-on-one meetings are important

In day-to-day work, a manager most often sees the result: whether a task was completed, whether a deadline was met, or whether a target was achieved. But very different reasons may lie behind that result.

An employee may:

not understand the priorities;
feel overloaded;
lack the necessary resources;
face conflicts between tasks;
receive insufficient feedback;
want more responsibility;
notice a problem in a process that the manager has not yet seen.

If such issues are discussed only when the problem becomes serious, they are much harder to manage.

Regular individual meetings help managers get this information earlier. This is especially important for managers who oversee several employees and simply cannot constantly follow every detail of each person’s work.

One-on-one meetings also complement the feedback system well. If a specific behavior or work situation needs to be discussed, the conversation can be structured using the SBI model. You can read more about it in the FlagMAN-D article “Feedback without conflict: the SBI model or the ‘sandwich’ method”.

How often should one-on-one meetings be held?

For most teams, a practical guideline is one meeting every one to two weeks. This rhythm helps maintain regular communication without allowing questions and problems to accumulate for months.

However, there is no universal frequency.

A new employee or someone who has recently changed roles may need meetings more often — for example, once a week. For an experienced employee whose work is stable, one meeting every two weeks may be enough.

The main point is not to turn one-on-one meetings into something that happens only “when necessary.” If the meeting is scheduled only after a mistake or conflict, the employee will quickly begin to see the invitation as a warning sign.

The optimal duration is usually 30–45 minutes. This is enough for a meaningful conversation without turning the meeting into another long discussion.

One-on-one meeting structure: what to discuss

It is useful to follow a consistent structure.

1. Start with the employee

The first questions should focus on how the employee is doing and on their current situation:

how work has been going over the past few weeks;
what is going well;
where difficulties have appeared;
whether they have enough resources;
whether there are tasks that create constant pressure.

It is important not to ask all these questions one after another like a questionnaire. They should serve more as directions for the conversation.

2. Discuss tasks and priorities

The next part is the work context.

It is worth clarifying:

which tasks are currently the most important;
whether priorities are clear;
what is slowing down progress;
whether there are conflicting deadlines;
whether support from the manager is needed.

Here, the manager’s task is to identify obstacles.

3. Give and ask for feedback

A one-on-one should work both ways.

The manager can discuss what the employee is doing well and what could be changed. But it is equally important to ask:

what can I do better as a manager;
where do you lack information or support;
which processes make your work more difficult;
which team decisions seem unclear.

Sometimes this is exactly where problems emerge that the manager would not have discovered otherwise.

4. Discuss development

Not every meeting needs to become a career consultation, but development topics are useful to raise regularly.

For example:

which tasks are more interesting to the employee;
which skills they want to develop;
whether they want to take on more responsibility;
whether there is an area they would like to try;
what kind of experience would be especially useful to them now.

This helps not only with the employee’s development, but also with planning within the team.

5. Record the agreements

A good one-on-one ends with clear next steps.

It should be clear:

what the employee will do;
what the manager will do;
by what deadline;
what should be reviewed at the next meeting.

Otherwise, even a useful conversation can quickly be forgotten.

What should not be discussed during a one-on-one

One-on-one meetings should have clear boundaries.

They should not be used instead of a full project meeting. If half the meeting is spent discussing the status of current tasks, it is better to move operational matters into a separate format.

Likewise, there is no need to wait for the next one-on-one to address a serious mistake. Important feedback should be given in a timely manner while the situation is still relevant.

At the same time, an individual meeting should not consist only of criticism. If the employee hears only about problems from the manager, the format will quickly start to feel like a regular inspection.

One-on-one meetings do not replace HR processes

Regular meetings help improve communication, but they do not replace clear job responsibilities, work rules, proper documentation of changes to employment conditions, and other elements of an HR system.

If one-on-one meetings repeatedly reveal that employees understand their roles, responsibilities, or internal procedures differently, the problem should not be addressed through conversations alone.

We help companies build HR documentation management and HR processes: from formalizing employment relationships to internal documents and consultations on labor matters. This makes it possible to establish important processes systematically.

For new employees, one-on-one meetings are especially useful during onboarding: they help align expectations, track progress, and address difficulties in time. You can read more about how to structure this process in the article “Onboarding new employees: why it matters for retention”.

If the problem is that company rules exist only “verbally,” it is useful to review local documents and internal regulations. FlagMAN-D also helps develop and update internal regulations so that they reflect the company’s actual processes and reduce HR-related risks.

A short checklist for managers

Before each one-on-one, it is enough to check five points:

whether there are any topics left from the previous meeting;
what difficulties the employee has encountered;
what feedback is important to give;
what should be asked directly of the employee;
what agreements need to be recorded.

Conclusion

A good one-on-one is a regular communication channel between a manager and an employee.

It helps identify problems earlier, clarify priorities, provide feedback, discuss development, and understand what is happening in the team beyond reports and performance indicators.

The key is to hold these meetings regularly, give the employee enough space to speak, and end the conversation with specific agreements. Then a one-on-one becomes not a formality, but a practical team management tool.

FlagMAN-D

2026-09-25 17:04