Read a sample: 1. Give the Meeting a Purpose
A manager and an employee sit down for their regular one-on-one. The manager opens a project tracker and asks for an update on each item. The employee answers. The manager mentions a deadline, offers a quick reminder, and asks whether there is anything else.
“No, I think that covers it,” the employee says.
The meeting ends on time. Both people return to work. What neither of them mentions is that the employee has been receiving conflicting requests from two team leads and is unsure whose direction to follow. The employee assumed the meeting was for reporting progress, not raising a problem that might sound like a complaint. The manager assumed that if something important were wrong, the employee would say so.
The meeting was not necessarily unpleasant or disorganized. It simply had a purpose too narrow for what the employee needed.
A useful one-on-one is a recurring conversation between a manager and an employee about the employee’s work and the support needed to do it. It gives the employee room to raise concerns, discuss meaningful progress, and identify obstacles or decisions that need attention. It also gives the manager an opportunity to understand the work more fully, clarify expectations, and follow through on commitments.
That purpose sounds straightforward, but it changes how the meeting is run. The manager is not there only to collect information. The employee is not there only to provide updates. Both people are there to make the work more understandable and manageable.
Managers need to know what is happening. Employees need to communicate progress. A one-on-one can include an update, especially when that update leads to a useful discussion. The distinction is what happens next.
A status report answers questions such as:
- What has been completed?
- What is in progress?
- What is due next?
- Is the work on track?
A one-on-one can start with those questions, but it should not have to stop there. It can explore what the answers mean:
- Which part of the work needs a decision?
- What is making progress harder than expected?
- Are the priorities still clear?
- Where would additional context or support help?
- What has the employee noticed that the manager may not see?
Consider the difference between asking, “Is the client proposal finished?” and asking, “How is the proposal coming together, and is anything making it harder to move forward?” The first question may be appropriate when the manager needs a direct answer. The second opens the door to a conversation about the work.
The employee might explain that the proposal is progressing but that a key assumption remains unresolved. The manager can then help determine who should make the decision. If the conversation ends with “It’s on track,” neither person has learned as much.
This does not mean every update needs to become a long discussion. Some work is proceeding as expected, and a brief acknowledgment is enough. Nor should a manager pretend not to need reliable information about deadlines. The point is to keep reporting in proportion. When routine updates are already available in a shared document, project system, or team meeting, the one-on-one can focus on interpretation, priorities, obstacles, and support.
A useful test is to ask: If the employee sent me the same information in writing, what would we still need to discuss? The answer often points toward the most valuable part of the meeting.
A practical purpose statement does not need to sound formal. A manager might tell an employee:
> “I’d like our one-on-ones to be a regular time to talk about your work—what’s going well, what feels unclear, and where you need support from me. We can cover updates when they help, but I don’t want this to feel like a report-out.”
That statement gives the employee a reason to bring more than a list of completed tasks. It also places a responsibility on the manager: if the employee raises something difficult, the manager must be willing to listen and determine what can reasonably happen next.
Three related purposes can guide the conversation.
Make room for employee concerns. A concern might involve a confusing process, an unrealistic workload, a strained working relationship, or uncertainty about a decision. It does not have to be dramatic to deserve attention. Small points of friction can affect work repeatedly, and employees may hesitate to raise them if every conversation is reserved for urgent problems.
Discuss meaningful progress. Progress is more than a count of completed tasks. An employee may have solved a recurring problem, learned a new part of the work, improved a handoff, or discovered that an original plan needs to change. Talking about progress helps both people see what is moving forward and what that progress requires.
Identify needed support. Support can take different forms. The employee may need a decision, clearer priorities, an introduction, access to information, coaching, or help addressing a barrier. Sometimes the most useful thing a manager can do is listen and help the employee think through options. At other times, the manager needs to take action outside the meeting.
These purposes overlap. An employee describing progress may reveal a concern. A concern may lead to a conversation about priorities. A request for support may show that an expectation was never clear. The meeting does not need rigid sections for each topic. It needs enough openness for the relevant topic to emerge.