A manager one-on-one meeting gives an employee and manager protected time to discuss the work, obstacles and development that do not fit a team meeting. It should not be only a verbal copy of the project tracker. The useful outcome is a better shared understanding of what the employee needs to do and what support the manager owes.
Agree the purpose and a workable cadence together, considering shifts, workload and the nature of the role. A 30-minute agenda is an illustrative starting point, not a research-backed universal frequency. Keep urgent issues out of the waiting room: required reporting and immediate support should not depend on the next scheduled one-on-one.
Prepare one useful example each
Ask the employee which situation needs attention. Review the previous agreement and bring a specific observation rather than a vague judgment. Shared preparation can be simple: the employee proposes an issue and the manager checks whether an earlier support commitment was completed.
Do not require an elaborate presentation. If a standard work tracker already contains progress information, use it briefly and spend the meeting on decisions, obstacles and learning. Explain what notes are kept and follow the organization's confidentiality and record-handling rules.
Try this 30-minute structure
Five minutes: reconnect and choose the focus. What has changed since the last conversation? Which issue is most useful to discuss?
Ten minutes: examine the work. What outcome is expected, what is getting in the way and which decision or resource is needed?
Ten minutes: feedback or development. Discuss one observed example, hear the employee's view and consider a supported next practice.
Five minutes: close the agreement. Confirm the employee's action, the manager's action and when they will review them.
Adjust the proportions when the work requires it. An employee facing a missing approval may need a decision, not a development exercise. The coaching conversation template helps when understanding the employee's reasoning is the useful next step.
Ask questions that reveal support needs
Useful prompts include: Which priority is unclear? Where are you waiting for someone else? What have you tried? What do you need me to decide or arrange? Which part of the work would you like more practice with? Ask the questions relevant to the situation, not every question on a checklist.
In a hypothetical conversation, an employee reports that two teams keep giving conflicting completion dates. The manager clarifies who can settle the priority rather than telling the employee to "communicate better." Record the manager's next action as explicitly as the employee's.
Keep development separate from surprise evaluation
Do not present a routine support meeting as informal and then quietly use it as an undisclosed disciplinary process. Explain its purpose and use approved HR and employment procedures when formal handling is required. A one-on-one does not replace those processes, nor is it a clinical conversation.
If the employee does not have a topic ready, ask about one recent work example. Silence can have many explanations; it is not proof of disengagement. Listen, clarify and offer a predictable response rather than diagnosing motivation.
Make the next meeting useful
Begin the next conversation by reviewing both sides' commitments. If the manager's action is late, say so and reset it. Repeated cancellation or unfulfilled support makes an otherwise good agenda less useful.
New supervisors can connect this routine to the first 30 days plan. If managers across the organization need help turning conversations into reliable support, discuss the development need with Shannon using examples of the work—not just a request for a better agenda.
About this resource: Prepared with AI-assisted drafting. Examples and templates are illustrative, not reported client outcomes, a validated assessment or a substitute for required policies and qualified supervision.