A one-on-one creates space to discuss work and support
A one-on-one meeting is a dedicated time between a manager and an employee to discuss their work situation. Its purpose should be agreed upon, rather than assumed to be obvious by its name.
In an illustrative team, a specialist completes tasks but regularly receives conflicting comments from two people. During the group status update they say “Everything is in progress” because the discussion focuses on deadlines. A separate conversation lets them clarify expectations and agree on who makes the final decision.
Such a meeting should not automatically be confused with a performance review, a disciplinary conversation, or a discussion of personal health. If the conversation has a special purpose, it must be stated in advance. A person must understand what is happening and how the information will be used.
- Report
“How many tasks are completed?” May be useful in its format.
- One-to-one
“Where do you have to guess expectations, and what would make the work clearer?” A different question with a different outcome.
How to prepare both sides
The employee can choose important questions, obstacles and observations to discuss. The manager should review previous agreements and consider where support is needed. Neither side should own the whole agenda.
| Situation | Possible question |
|---|---|
| Unclear Expectations | By what signs will we understand that the result is good enough? |
| Conflicting instructions | Who makes the final decision in this work? |
| Overload | What doesn’t fit now and what options are there? |
| New responsibility | What support is missing for the next step? |
| Past agreement | What has changed since our decision? |
You don't need to ask all the questions in a row. Select those that apply to your current situation. The list helps get you started, but carefully clarifying your answer is more important than completing the questionnaire.
How to listen and clarify
- Observation
“It’s hard for me to finish the material.” Too broad for now.
- Clarification
Two reviewers’ comments contradict each other.
- Decision
Identify the approver and the process for combining feedback.
Don't jump to advice before you understand the situation. “Just prioritize” is of little help if the employee does not have the right to choose between conflicting assignments. Sometimes useful action is required from the leader.
Separate fact, interpretation and request. Together we can reconstruct a specific episode: what was said, what action followed, where the expectation arose. This reduces the risk of arguing with a general assessment instead of the actual problem.
How to record agreements and protect privacy
Record only what is needed to continue the work and agree on who can access the record. Do not put sensitive information into a shared project out of habit. Check the actual access rights of the chosen location rather than inferring them from a note’s title.
- Formulate a specific action for each party.
- Specify the expected outcome and when to review it.
- Agree on what exactly can be kept in the record.
- Select a location with suitable access.
- At the next conversation, check the fulfillment of agreements.
In the illustrative situation, a neutral action is enough: “Agree on the process for accepting the material.” The shared task need not contain personal judgements about colleagues or a verbatim emotional conversation. Keep context separately within agreed boundaries.
Questions for three different situations
For overload, start with specifics: “Which work is crowding out other work right now? What can only be postponed with my decision? Where do my expectations conflict?” You can clarify “Everything is fine” through a recent incident, but do not pressure someone to admit a problem they cannot or do not want to discuss.
For development, different questions help: “Which problem would you like to learn to solve? What can you already do independently? Which next project would offer useful practice, and what help is needed?” End with an achievable opportunity rather than a promise of abstract growth. A manager should not guarantee promotion without the authority to do so.
For collaboration, ask: “When did we last understand an agreement differently? What context was missing? What should change in the feedback?” Examining one case is more useful than labelling someone “communicative” or “closed”.
Employees can prepare questions for their manager too: which outcomes matter most now, where independent decision-making ends and how work will be assessed. A one-on-one lets both sides compare expectations rather than simply receive an assessment from above.
Example of a conversation that ends with support
The employee says: “I cannot finish the article; I am constantly interrupted.” Instead of advising better planning, the manager asks about recent interruptions. It emerges that two other participants regularly request urgent edits and consider their requests an agreed priority.
Agreement: the manager agrees on a unified procedure for urgent requests, the employee, before the next meeting, notes which requests actually interrupted work. There is no need to record every minute or turn the meeting into surveillance. Observation is limited to a specific hypothesis about the causes of the delay.
A shared task can contain the neutral action “Agree on the process for urgent changes”, without personal judgements about the employee. Keep personal notes and sensitive information only where access rights are understood and verified. Discuss what is recorded and who can see it; do not promise absolute secrecy if your obligations impose limits.
At the next meeting, they check whether the number of conflicting requests has changed and whether it has become easier to complete the work. If not, they reconsider the decision. The very fact of regular meetings does not prove support: it is manifested in the implementation of agreements.
Record the action without personal details
Start with one task: “Agree on the process for accepting the material.” Record the expected outcome in the description: an identified approver, an agreed way to combine comments and participants who know the new rule. You do not need to move the entire article into the service; save what you will need while doing the work.
Schedule an action after the conversation while the agreement is fresh. Keep only neutral working language in the shared task and check actual access to the record.
- Create a task with a specific action in its title.
- Add the completion conditions and necessary context to the description.
- Choose a day and check whether the work fits alongside your other commitments.
Signing up for Sinqly is free. You can also work through the article's example in an ordinary document; the app helps you return to the actions you chose.
How to maintain a healthy rhythm
Frequency depends on role, changes and support needs. A new participant may need more frequent contact, while an independent participant may need a different rhythm. Don't cancel a meeting every time there's no immediate problem, but don't keep your calendar ritual empty of content either.
Periodically ask if the format is helping and what is missing in it. If important issues are continually left unsaid, check the purpose, safety and behavior of the participants, not just the length of the meeting.
Trust is maintained by the fulfillment of agreements. A thoughtful conversation loses its value if the promised help disappears every time the calendar closes.
More questions to clarify
Who draws up the agenda?
Both sides can add topics. Leave room for the employee’s questions rather than making the conversation solely a list of the manager’s instructions.
Are detailed minutes necessary?
Not necessarily. Agreed work actions and necessary context with appropriate access are enough. Excessive recording of sensitive details may be inappropriate.
Is it possible to hold a meeting online?
Yes, if the conditions allow you to concentrate and respect the agreed boundaries of the conversation. Format itself does not determine quality.
Was this helpful?
Rate the article and tell us what was missing. Your feedback goes to the Sinqly team and will not be published on the site.
Sources and notes
- Atlassian: One on One Meeting Agenda
- The suggested process reflects editorial practice; it does not promise identical results for everyone.
Employee onboarding: a first-month plan
Organize a new employee's first days and month: access, a clear first task, support and feedback. An illustrative onboarding plan for a small team.
Work procedure: describe a process people actually use
How to describe a repeatable work process: inputs, steps, roles, exceptions and updates. An illustrative enquiry-handling procedure you can test in practice.
Company knowledge base: structure, first articles and update rules
How to build a minimal employee knowledge base: first instructions, a clear structure, owners and updates. Help people find and use answers, rather than simply store them.