How to Run Effective One-on-One Meetings: Agendas, Feedback, Growth, and Follow-Up

Quick answer: A good one-on-one meeting is a recurring private conversation that helps a manager and employee discuss priorities, blockers, feedback, development, and the working relationship. It should not become a status-report meeting. Use a shared agenda, let the employee contribute most of the topics, prepare important items before the meeting, discuss immediate work and longer-term growth, end with clear actions, and review those actions next time. Give urgent or sensitive feedback when it is needed rather than saving everything for the next one-on-one.

One-on-one meetings work best as conversations, not mini-presentations. Image: Jwslubbock, Wikimedia Commons, CC BY-SA 4.0.

A recurring one-on-one meeting can become one of the most useful routines in a team—or one of the easiest calendar events to waste. The difference is rarely the length of the meeting. It is the design.

When one-on-ones go badly, they often turn into a rapid list of project updates, a place where the manager talks for most of the time, or a vague conversation with no follow-up. Employees may save difficult topics because there is never enough space to discuss them. Managers may cancel the meeting whenever operational work becomes busy, unintentionally sending the message that the employee’s questions and development are less important than everything else on the calendar.

When the routine works well, it creates a predictable channel for information that does not fit comfortably into team meetings or chat messages. A direct report can raise a blocker before it becomes a missed deadline. A manager can notice that expectations are unclear before performance suffers. Career interests can be discussed before someone starts looking elsewhere. Small frustrations can be surfaced while they are still solvable. Recognition, feedback, and coaching can happen continuously rather than appearing suddenly during an annual review.

This guide explains how to build that system in a practical way. It covers cadence, agenda design, preparation, open-ended questions, feedback, accountability, career development, remote meetings, difficult conversations, new employees, high performers, disengagement, documentation, follow-up, and common failure modes.

1. Define the Purpose of the One-on-One

The first design decision is deciding what the meeting is for.

A useful one-on-one usually serves several purposes at the same time:

• surface blockers and risks;
• clarify priorities and expectations;
• exchange feedback in both directions;
• discuss workload and support needs;
• develop the employee’s skills and judgment;
• talk about career direction and growth;
• strengthen the manager-employee working relationship;
• create follow-through on commitments.

What it should not be is a simple replacement for the team’s project-tracking system. If the entire conversation consists of “What is the status of Task A? What about Task B?”, the meeting is doing work that a dashboard, project board, or written update could often handle more efficiently.

GitLab’s current 1-1 guidance explicitly treats the meeting as something that should be driven substantially by the direct report, with both parties adding agenda items and the employee preferably contributing most of them. That principle is useful because the employee has information the manager cannot see from dashboards: confusion, interpersonal friction, confidence gaps, emerging ideas, workload strain, and career concerns.

Practical test: After a one-on-one, ask whether you learned anything that would probably not have appeared in a normal status report. If the answer is consistently no, redesign the meeting.

2. Choose a Cadence Based on the Person and the Work

There is no single frequency that fits every team.

GitLab currently advises managers to schedule one-on-ones at least weekly in its own environment, while also allowing synchronous and asynchronous formats to vary depending on needs. UC Davis recommends weekly check-ins during the early onboarding period for new employees. OPM’s current performance-management roadmap emphasizes regular one-on-ones and check-ins as part of a continuous-feedback culture.

These examples point to a broader rule: cadence should respond to uncertainty, experience, change, and the cost of delay.

Consider a weekly meeting when:

• the employee is new;
• the role is changing quickly;
• priorities shift often;
• the employee needs frequent coaching;
• the manager and employee work remotely with limited informal contact;
• there are active performance or development issues;
• the work contains many cross-team dependencies.

A biweekly meeting may work when the employee is experienced, priorities are stable, communication is strong, and there are other natural touchpoints during the week.

Monthly one-on-ones can be too infrequent for many manager-direct-report relationships because small problems can age for weeks before the next conversation. If monthly is the only realistic cadence, consider supplementing it with shorter check-ins.

Common mistake: Reducing frequency because the employee is a high performer. High performers may need less task supervision, but they still benefit from development, strategic context, recognition, sponsorship, and career discussion.

3. Protect the Meeting From Routine Cancellation

A one-on-one only becomes a trusted channel if it actually happens.

GitLab’s guidance explicitly warns against repeatedly pushing one-on-ones for “more important” work and recommends rescheduling when a conflict genuinely cannot be avoided. This matters because cancellation has symbolic weight. The employee cannot see every reason behind the calendar change; repeated cancellation can easily be interpreted as “my concerns are optional.”

Use these rules:

• Schedule the meeting as a recurring event.
• Choose a time that has a reasonable chance of surviving operational pressure.
• Do not cancel simply because the agenda looks short.
• If a real conflict occurs, reschedule instead of deleting the meeting.
• If one participant is on leave, skip intentionally rather than pretending the cadence still happened.

A short one-on-one can still be useful. A week with few problems may be the best time to talk about development, relationships, upcoming changes, or ideas that never become urgent enough for a crisis meeting.

4. Use a Shared Agenda That Both People Can Edit

A shared agenda turns the meeting from a memory test into a continuous conversation.

Create one private document or workspace that both participants can edit. It might be a Google Doc, Microsoft document, HR system page, project-management note, or another approved internal tool. The exact software matters less than the habits around it.

A simple recurring structure is:

• Top of mind: what needs attention now?
• Priorities and blockers: what is stuck or changing?
• Feedback: what should start, stop, continue, or change?
• Development: skills, career direction, opportunities.
• Relationship and support: what could the manager or employee do differently?
• Actions: who will do what by when?

Do not force every section into every meeting. The structure should make important topics easier to surface, not create a ritual where both people mechanically fill boxes.

GitLab recommends keeping the 1-1 document private because feedback can be sensitive. That is a useful default: restrict access to the people who genuinely need it and follow your organization’s records and privacy policies.

5. Add Agenda Items During the Week, Not Five Minutes Before

The best agenda is built gradually.

When a topic comes up on Tuesday, add it immediately rather than trying to remember it Friday morning. GitLab recommends encouraging direct reports to keep the agenda accessible during the week and suggests populating it at least 24 hours before the meeting so both people have time to think.

Good agenda items are specific enough to prepare for:

Weak: “Project Phoenix.”

Better: “Phoenix launch date may slip because legal review is still pending. Need decision on whether to reduce scope.”

Weak: “Career.”

Better: “Interested in leading a small cross-functional project next quarter; want to discuss what skills or evidence I need first.”

Specific agenda items reduce meeting time spent reconstructing context.

6. Separate Asynchronous Updates From Conversation Topics

Not everything on the agenda deserves synchronous time.

If a topic is purely informational—“The vendor contract was signed”—put it in the shared document and mark it as an update. If there is no decision, coaching need, ambiguity, or emotional nuance, the other person can read it before the meeting.

Reserve live time for topics that benefit from interaction:

• tradeoffs;
• unclear expectations;
• feedback;
• conflict;
• career choices;
• problem solving;
• important decisions;
• topics where tone matters.

GitLab’s engineering-management guidance explicitly uses asynchronous preparation to protect synchronous time for higher-value discussion. The principle applies even in fully co-located teams.

7. Let the Employee Own Meaningful Space in the Meeting

The manager may organize the routine, but the employee should not feel like a guest in it.

A practical target is to ensure the direct report has genuine control over a large share of the agenda. That does not mean the manager never raises priorities or feedback. It means the meeting does not become thirty minutes of managerial broadcasting.

You can reinforce employee ownership by asking:

• “What do you most want to leave this meeting with?”
• “Which topic should we make sure we do not run out of time for?”
• “What is taking more energy than it should?”
• “Where do you want my input, and where do you just want me to listen?”

This last question is especially useful. Sometimes an employee needs a decision. Sometimes they want advice. Sometimes they need to think out loud before choosing their own solution.

8. Start With a Real Check-In, Not Automatic Small Talk

A human opening can help people transition from task mode into conversation.

GitLab suggests asking open-ended questions such as how the person has been doing since the last conversation rather than yes-or-no questions such as “You doing okay?” OPM also emphasizes open-ended questions when discussing performance and development.

Useful openings include:

• “How has the week felt from your side?”
• “What has been easier or harder than expected?”
• “What is taking up most of your attention right now?”
• “What has gone well since we last talked?”

Do not force personal disclosure. A one-on-one is not therapy, and employees differ in how much personal context they want to share. The goal is to create room for context that affects work, not to demand intimacy.

9. Ask About Outcomes, Not Just Activity

Status questions often produce lists of tasks. Coaching questions produce understanding.

Instead of “What did you do this week?”, try:

• “What outcome are you trying to create?”
• “What changed because of your work?”
• “What is the most important decision in front of you?”
• “Where is the project most likely to fail?”
• “What assumption are we relying on?”
• “What would you stop doing if time became tighter?”

These questions help reveal judgment, prioritization, and risk—not just activity volume.

They also help prevent a common management failure: rewarding visible busyness while missing whether the work actually matters.

10. Discuss Blockers in a Way That Builds Capability

When an employee raises a blocker, the manager’s first instinct may be to solve it immediately. Sometimes that is appropriate. But if the manager solves every problem, the employee may become more dependent rather than more capable.

Use a coaching sequence:

1. Clarify the problem.
2. Ask what the employee has already tried.
3. Ask what options they see.
4. Explore tradeoffs.
5. Decide whether the employee can act independently or needs managerial intervention.

For example:

“The design team has not responded for four days” can lead to “What have you tried?”, “What deadline is at risk?”, “Who owns the dependency?”, and “Would an escalation from me help, or would that create unnecessary friction?”

The manager still provides support, but the conversation teaches a reusable problem-solving process.

11. Give Feedback Continuously Instead of Saving It for the Meeting

One-on-ones are a good place for feedback, but they should not become a storage warehouse for feedback.

GitLab advises giving positive or negative feedback promptly rather than waiting for the next meeting. OPM’s current performance-management guidance similarly emphasizes continuous feedback and regular check-ins.

Prompt feedback is more useful because the event is still fresh. The employee can connect the feedback to a specific behavior and adjust sooner.

Use the one-on-one to:

• follow up on earlier feedback;
• look for patterns;
• discuss how a behavior affects broader goals;
• ask for feedback on the manager;
• practice difficult skills;
• recognize progress.

Do not wait two weeks to mention a serious issue merely because a one-on-one is scheduled.

12. Make Feedback Specific Enough to Act On

Vague feedback creates anxiety without direction.

Vague: “You need to communicate better.”

Specific: “In the last two project reviews, the risk appeared after the deadline had already moved. I need you to surface schedule risks as soon as you believe the probability is material, even if the information is incomplete.”

Useful feedback identifies:

• the observable behavior or outcome;
• the context;
• the impact;
• the desired future behavior;
• the support available.

OPM’s performance-management materials emphasize specific examples and clear expectations. This is not only useful for formal performance management; it improves ordinary coaching conversations too.

13. Ask for Upward Feedback in a Way That Feels Answerable

“Any feedback for me?” often receives “No, all good.” The question is too broad and socially risky.

Ask narrower questions:

• “What is one thing I could do to make priorities clearer?”
• “Where am I creating extra work for you?”
• “What information do you usually get too late from me?”
• “Was there a decision recently where you wanted more context?”
• “What should I do more of when you bring me a problem?”
• “What is one meeting or process I could simplify?”

Then do something visible with useful feedback. If employees repeatedly offer suggestions and nothing changes, the question becomes performative.

OPM’s current performance roadmap explicitly encourages two-way feedback between employees and managers. The behavior that makes upward feedback credible is follow-through.

14. Distinguish Coaching From Direct Instruction

Not every situation needs a Socratic conversation.

Use direct instruction when:

• there is a safety or compliance requirement;
• the employee lacks necessary information;
• a deadline leaves no room for exploration;
• the correct process is fixed;
• the employee explicitly asks for a clear decision.

Use coaching when:

• several reasonable approaches exist;
• judgment is the skill being developed;
• the employee has enough context to propose solutions;
• the goal is long-term independence.

A strong manager moves between these modes intentionally rather than coaching everything or commanding everything.

15. Reserve Time for Development Before the Agenda Is Full

Career development disappears easily because operational topics always feel more urgent.

Protect part of the monthly rhythm for questions such as:

• “What skill do you want to be noticeably better at six months from now?”
• “Which part of your role gives you the most energy?”
• “What responsibility would you like to try that you do not currently own?”
• “What kind of problem do you want people to trust you with?”
• “Which role or career path are you curious about?”

UC Davis’s current Experience Conversations toolkit treats career development, future readiness, wellbeing, retention, inclusion, and manager support as legitimate one-on-one topics. Those areas are easy to miss if the meeting is designed only around immediate tasks.

16. Turn Career Goals Into Near-Term Experiments

“I want to become a manager” is not yet a development plan.

Translate the goal into evidence-building experiences:

• lead a small project;
• mentor a newer employee;
• facilitate a retrospective;
• write a project plan;
• present to a senior stakeholder;
• handle a cross-team negotiation;
• own a process improvement.

Then ask what support is needed and what success would look like.

This prevents career development from becoming an abstract promise that gets revisited every three months without action.

Useful one-on-one notes should capture decisions, commitments, and development themes rather than a transcript of every sentence. Image: Shixart1985, Wikimedia Commons, CC BY 2.0.

17. Talk About Workload Before It Becomes Burnout

Workload conversations should be concrete.

Instead of asking “Are you busy?”, ask:

• “Which commitment is most at risk?”
• “What work is taking more time than we planned?”
• “What are you doing that we could stop or delay?”
• “Which dependency is creating repeated rework?”
• “If one priority had to move, which should it be?”

This makes workload manageable as a prioritization problem rather than a test of endurance.

If the employee describes persistent exhaustion, anxiety, or health concerns, the manager should stay within the manager role: discuss workload, resources, leave, organizational support, and appropriate HR or employee-assistance resources rather than trying to diagnose or provide therapy.

18. Use the Meeting to Clarify Expectations

Many performance problems begin as expectation mismatches.

The employee thinks “done” means the draft exists. The manager thinks “done” means stakeholders have approved it. The employee thinks speed is the priority. The manager thinks accuracy is.

Ask:

• “What does success look like for this?”
• “What matters most: speed, quality, cost, or learning?”
• “Which decisions can you make without me?”
• “When should you escalate?”
• “What would make me say this was excellent rather than merely complete?”

OPM’s communication guidance emphasizes clarifying expectations and involving employees in planning and development. One-on-ones are an ideal place to correct ambiguous expectations before they harden into frustration.

19. Discuss Relationships and Cross-Team Friction

Some of the most important blockers are relational rather than technical.

Ask periodically:

• “Which relationship is making your work easier?”
• “Which relationship is creating friction?”
• “Where do you feel we are misaligned with another team?”
• “Is there someone whose expectations you do not understand?”

Do not immediately label another colleague as “difficult.” Clarify what actually happened, what was expected, and whether the issue is role clarity, incentives, communication style, resource competition, or a specific behavior.

The goal is to help the employee navigate the organization, not create a private gossip session.

20. Recognize Good Work With Specificity

Recognition is more credible when it identifies what was valuable.

Generic: “Great job.”

Specific: “The way you summarized the customer risk in two sentences let the leadership team make a decision quickly. Keep using that level of synthesis in executive updates.”

OPM’s communication guidance emphasizes timely recognition connected to achievements. The lesson is practical: name the behavior or outcome you want repeated.

Also learn the employee’s preferences. Some people appreciate public recognition. Others prefer a private note or expanded responsibility.

21. Do Not Turn the One-on-One Into a Performance Review

Performance is a legitimate topic, but the meeting should not feel like a recurring hidden appraisal.

If every one-on-one is dominated by rating language, employees may stop raising uncertainty, mistakes, or ideas because the conversation feels evaluative rather than developmental.

Use the meeting for continuous feedback, clear expectations, and coaching so formal reviews contain fewer surprises. OPM explicitly recommends a continuous-feedback approach and notes that performance assessments should reflect prior feedback and ongoing discussions.

Formal performance processes still need to follow your organization’s policies. The one-on-one supports them; it does not replace them.

22. Handle Performance Concerns Directly and Fairly

If performance is materially below expectations, avoid hints.

Explain:

• what expectation applies;
• what specific behavior or result is not meeting it;
• why it matters;
• what improvement looks like;
• what support is available;
• what timeline or formal process applies, if relevant.

Do not improvise formal disciplinary or legal processes in a casual one-on-one. Follow your organization’s HR policy and applicable law.

OPM’s employee-relations guidance warns against waiting until appraisal time to surface unacceptable performance. That principle is broadly useful: serious concerns should not arrive as a surprise months later.

23. Use “Start, Stop, Continue” for a Structured Feedback Moment

OPM’s current monitoring and development guidance recommends the Start, Stop, Continue model as one approach during feedback conversations.

Ask both people:

• Start: What would improve the work if we began doing it?
• Stop: What behavior or process creates unnecessary cost or friction?
• Continue: What is working and should be protected?

This format is especially useful when the conversation has become vague. It creates a balanced structure that includes strengths, not only problems.

24. Make Difficult Conversations Specific and Private

Sensitive feedback should be discussed in an environment where the employee can respond without an audience.

For remote work, confirm that both participants have enough privacy before raising a sensitive topic. For office work, avoid discussing performance concerns in open seating areas.

Use calm, observable language. Do not speculate about motives.

Instead of “You do not care about deadlines,” say, “The last three deliverables were submitted after the agreed date without an early warning. I want to understand what is causing that pattern and agree on a different escalation point.”

This keeps the conversation anchored in behavior and problem solving.

25. Do Not Diagnose Personal or Medical Problems

If an employee’s behavior changes, a manager may notice something is wrong. The manager should not diagnose depression, addiction, anxiety, ADHD, or another medical condition based on workplace observations.

Focus on work-related facts, support, and available resources. If the employee raises a health or disability issue, follow the organization’s HR and accommodation processes.

This boundary protects both the employee and the manager from turning a workplace meeting into unqualified medical advice.

26. Give New Employees More Structure

New employees often need a different kind of one-on-one.

UC Davis’s onboarding guidance recommends weekly one-on-one check-ins early in the first 90 days to clarify questions, address concerns, monitor progress, and reinforce role expectations.

Useful onboarding topics include:

• What still feels unclear?
• Which system or process is hardest to understand?
• Who do you need to know better?
• Which expectations surprised you?
• Where are you waiting for access or information?
• What would help you feel more confident next week?

New employees may not know what they are “allowed” to ask. More structure reduces that ambiguity.

27. Gradually Reduce Task Detail as Competence Grows

As an employee becomes more experienced, the one-on-one should evolve.

Early conversations may focus on how to perform specific tasks. Later conversations can shift toward outcomes, tradeoffs, stakeholder management, leadership, development, and strategic context.

If the meeting still covers the same low-level details a year later, ask whether the employee is gaining autonomy or whether the manager is holding too tightly to task supervision.

28. Challenge High Performers Without Making Them Carry Everything

High performance often attracts more work. That can become a punishment.

Use one-on-ones to distinguish development opportunities from load dumping.

Ask:

• “Which stretch work would actually build a skill you want?”
• “What are you carrying only because you are reliable?”
• “What should we transfer to create space for higher-value work?”
• “Where do you want more visibility or sponsorship?”

Growth should increase capability and opportunity, not simply increase volume.

29. Discuss Retention Before Someone Resigns

Do not wait for an exit interview to ask why an employee might leave.

UC Davis and UC Berkeley currently recommend broader “Experience Conversations” that can include retention, wellbeing, career development, belonging, and manager support. These can be incorporated into ongoing one-on-ones.

Questions might include:

• “What keeps you here?”
• “What part of the job would you most like to change?”
• “What would make this role meaningfully better six months from now?”
• “Where do you feel underused?”
• “What opportunity would be hard to say no to if another company offered it?”

Do not ask for promises to stay. Use the answers as information about conditions you may be able to improve.

30. Treat Remote One-on-Ones as Deliberate Synchronous Time

Remote teams lose many informal hallway conversations, so the one-on-one may carry more relational weight.

Prepare asynchronously so the live call is not spent reading updates. GitLab’s remote-management guidance explicitly frames synchronous one-on-one time as valuable and recommends preparation beforehand.

Practical remote habits include:

• use a stable private meeting link;
• avoid multitasking in chat or email during the call;
• share the agenda on screen only when useful;
• leave space for conversation rather than reading line by line;
• document actions immediately;
• check audio and privacy before sensitive topics.

Camera use should follow organizational norms and individual accessibility needs rather than being treated as universal proof of engagement.

31. Adapt for Different Communication Styles

Some employees think aloud. Others need time before answering. Some prefer direct feedback; others process better when given context and time.

GitLab’s guidance explicitly notes that one communication style does not fit everyone.

Adapt without lowering clarity. For example:

• send important questions before the meeting;
• allow the employee to add written responses;
• pause after difficult questions instead of filling silence;
• summarize decisions in writing afterward;
• ask how the person prefers feedback to be delivered.

Adaptation is not avoidance. A manager still has to communicate expectations and difficult feedback clearly.

32. Make the Meeting Accessible

Accessibility can affect scheduling, communication format, note taking, visual material, audio, and the pace of conversation.

Ask what helps the employee participate effectively rather than making assumptions. Options may include captions, written agendas in advance, accessible documents, additional processing time, shorter meetings, or other accommodations through the formal organizational process.

Do not require disclosure of unnecessary medical detail. Focus on creating an effective and compliant work environment.

33. Do Not Force a Fixed 30-Minute Format

Thirty minutes is common, but the duration should match the purpose.

A 20-minute weekly meeting can work well when there is a strong agenda and frequent contact. A 45- or 60-minute conversation may be useful for monthly development discussions, a major transition, or a complex issue.

The important design choice is not “What is the standard length?” but “Can we discuss the important topics without rushing or filling time artificially?”

If the meeting repeatedly ends with important items untouched, either increase the duration, improve asynchronous preparation, or reduce low-value status content.

34. Time-Box Topics Without Cutting Off Important Context

Time-boxing helps prevent one minor issue from consuming the entire meeting.

Mark agenda items as:

• decision needed;
• discussion;
• FYI;
• feedback;
• development.

If a complex topic needs more time, decide explicitly whether to continue and drop something else, or schedule a separate conversation.

Do not rush a sensitive issue simply because the calendar says only four minutes remain. Move the operational items instead.

35. Record Decisions and Actions, Not a Full Transcript

Notes should help future follow-up.

Capture:

• decisions;
• commitments;
• deadlines;
• important goals;
• development themes;
• follow-up questions.

Avoid documenting casual personal details that have no legitimate business purpose. Follow company policy for sensitive employee information, performance notes, and HR records.

OPM’s current performance roadmap emphasizes maintaining secure, up-to-date records of goals, feedback, reviews, and coaching where appropriate. The implementation must still follow your organization’s policies and applicable law.

36. Assign Every Action to One Owner

“We should look into that” is not an action item.

Write:

• “Manager: ask finance about training budget by Friday.”
• “Employee: draft proposal for the new reporting process before next 1:1.”
• “Manager: introduce employee to product lead next week.”

If both people “own” an action, it often means neither does.

37. Begin the Next Meeting by Reviewing Commitments

Follow-through creates trust.

At the start of the next meeting, quickly review open actions. If something was not completed, explain why and reset the commitment rather than silently carrying it forward.

This is especially important for manager actions. Employees notice quickly when managers repeatedly promise introductions, resources, decisions, or development opportunities and then forget them.

38. Use a Separate Space for Formal HR Processes

One-on-one notes should not become an improvised legal file.

If a situation enters formal performance management, disciplinary action, accommodation, leave, investigation, compensation review, or another HR process, follow the organization’s designated systems and policies.

You can still discuss relevant work issues in the one-on-one, but do not assume a private shared document satisfies formal documentation requirements.

39. Do Not Promise Confidentiality You Cannot Guarantee

Managers should respect privacy, but there are situations where information may need to be escalated—for example, certain safety, harassment, discrimination, legal, or policy concerns.

Avoid saying, “Anything you tell me stays between us,” unless that is genuinely true under your organization’s obligations.

A more accurate approach is to handle information discreetly and explain when you may need to involve HR or another appropriate function.

40. Use Questions That Reveal Risk Earlier

Some questions are valuable because they surface problems before metrics do:

• “What are we not talking about that we should be?”
• “Where are you relying on an assumption you do not trust?”
• “What commitment feels unrealistic?”
• “What problem are you solving manually that keeps coming back?”
• “Which stakeholder are we most likely to surprise?”
• “What are you avoiding because it feels difficult?”

Do not use every question every week. Rotate them when the conversation needs depth.

41. Use Questions That Reveal Learning

Development is easier to see when you ask about changes in judgment:

• “What do you understand now that you did not understand three months ago?”
• “Which mistake changed how you work?”
• “What decision are you now able to make without help?”
• “What kind of feedback are you hearing repeatedly?”
• “What would you teach a new person about this job?”

These questions make growth concrete and can reveal areas where the employee is ready for broader scope.

42. Use Questions That Reveal Motivation

Motivation is not always about compensation or title.

Ask:

• “Which work do you look forward to?”
• “Which work drains you even when you are good at it?”
• “When did you feel most useful recently?”
• “What kind of recognition is meaningful to you?”
• “What would make your role feel more challenging in a good way?”

Managers cannot redesign every job around preferences, but understanding motivation improves assignment, recognition, and development decisions.

43. Use Questions That Reveal Managerial Blind Spots

Managers experience the team differently from employees.

Ask:

• “What process looks simpler from my seat than it really is?”
• “Where do you think leadership has incomplete information?”
• “What team frustration has become so normal that we stopped questioning it?”
• “What decision did I make recently that had an unexpected consequence?”

These questions can turn one-on-ones into a useful sensor for organizational problems.

44. Know When a Topic Needs a Separate Meeting

Not every issue belongs inside the recurring one-on-one.

Schedule separate time when:

• the topic needs multiple stakeholders;
• a detailed project design is required;
• formal HR participation is needed;
• the conversation is time-sensitive and cannot wait;
• the issue will consume the entire meeting and crowd out employee-owned topics.

Moving a topic does not mean avoiding it. Give it a specific time.

45. Do Not Use the One-on-One to Replace Team Communication

If several employees need the same information, communicate it to the team rather than repeating it privately in every one-on-one.

Use one-on-ones for individual interpretation: “How does this change affect your work?” rather than making each employee discover the announcement separately.

This prevents inconsistent information and frees one-on-one time for higher-value discussion.

46. Create a Monthly Development-Focused Meeting

If weekly one-on-ones are always crowded with operational issues, designate one meeting each month as development-heavy.

A development agenda might include:

• career direction;
• recent learning;
• skill gaps;
• stretch opportunities;
• relationships and visibility;
• feedback patterns;
• next-quarter goals.

This preserves long-term thinking without requiring every weekly meeting to be perfectly balanced.

47. Create a Quarterly Relationship Reset

Every few months, ask whether the one-on-one itself is working.

Questions:

• “Is this cadence still useful?”
• “Do we spend too much time on updates?”
• “What topics are missing?”
• “Do you have enough space to bring difficult issues?”
• “Should we change the agenda format?”
• “Are my follow-ups reliable?”

The meeting process should evolve with the relationship.

48. Worked Example: A One-on-One That Has Become a Status Meeting

Maria manages a product analyst. Their weekly 30-minute one-on-one sounds like this:

“Where are we on the dashboard? Did finance send the data? Is the experiment report done? What about next week’s launch?”

The analyst answers each question. The meeting ends. Career goals have not been discussed for four months.

Maria redesigns the process:

1. Project status moves to the team’s written weekly update.
2. The shared one-on-one agenda has sections for top-of-mind issues, blockers, feedback, development, and actions.
3. The analyst adds agenda items during the week.
4. Maria reads the status update before the meeting.
5. Live time focuses on decisions and coaching.

The next one-on-one includes a difficult stakeholder relationship, a question about prioritization, and the analyst’s interest in learning experimentation design.

The meeting did not become longer. It became more valuable because information moved to the right channel.

49. Worked Example: A New Employee Who Says “Everything Is Fine”

David is two weeks into a new role. Every one-on-one begins with “Any questions?” He says no.

His manager switches to structured onboarding questions:

• “Which process is still confusing?”
• “Who do you need more context from?”
• “Which task took longer than you expected?”
• “What are you unsure you have authority to decide?”
• “What would make next week easier?”

David reveals that he does not understand the approval process and has been waiting two days for access to a reporting system.

The manager resolves the access issue and explains approval authority. The lesson is not that David was hiding information. He did not yet know which problems were normal enough to ask about.

50. Worked Example: A High Performer Who Is Quietly Disengaging

Leah consistently exceeds expectations, so her manager assumes she needs little attention. Their one-on-ones become less frequent.

During a quarterly career conversation, the manager asks, “Where do you feel underused?” Leah explains that she has been doing the same type of work for a year and wants exposure to customer strategy. She has also been approached about a role elsewhere.

The manager cannot promise a promotion, but can create a concrete development path: Leah joins a strategic customer project, presents insights to leadership, and mentors another analyst so some routine work can be transferred.

The important point is not that every retention concern can be solved. It is that regular one-on-ones create a chance to learn about the concern before the resignation email.

51. Troubleshoot Common One-on-One Problems

“The employee never adds agenda items.”

Make the purpose clearer. Ask for one topic in advance. Use specific prompts rather than “add anything you want.” New employees may need examples before they understand what belongs there.

“We run out of time every week.”

Move status updates asynchronous, mark priorities, and separate deep project work into another meeting.

“The conversation is awkward.”

Use more specific questions and allow silence. Awkwardness often comes from vague prompts or the manager feeling obligated to fill every pause.

“The employee only brings complaints.”

Listen for legitimate patterns, then shift toward options: “What outcome do you want?”, “What can you influence?”, and “What support do you need from me?” Do not dismiss repeated concerns simply because they are uncomfortable.

“I am doing all the talking.”

Prepare fewer speeches. Ask one open question and wait. Treat the direct report’s agenda items as the center of the meeting.

“The employee wants answers I do not have.”

Say so. Agree on who will find the answer and by when. False certainty damages trust more than an honest “I need to check.”

“We keep discussing the same blocker.”

Convert discussion into an action, escalation, decision, or explicit acceptance. Repeated conversation without ownership is a system failure.

“One-on-ones feel repetitive.”

Rotate deeper topics: development, relationships, workload, process improvement, motivation, future readiness, and career goals.

“The employee becomes defensive during feedback.”

Slow down, use specific observations, explain impact, invite their perspective, and clarify the future expectation. Do not dilute important feedback into ambiguity merely to avoid discomfort.

“The employee rarely speaks about career development.”

Ask narrower questions about skills, assignments, and interests. Some people do not have a five-year career plan, but they can still identify what they want to learn next.

52. A 30-Minute One-on-One Template

This is a starting point, not a mandatory script:

Minutes 0–5: Check-in and priorities

• How has the week felt?
• What topic matters most today?

Minutes 5–15: Blockers and decisions

• What is stuck?
• Where is a decision or escalation needed?

Minutes 15–22: Feedback and working relationship

• What should we start, stop, or continue?
• What could I do differently as your manager?

Minutes 22–27: Development

• What are you learning?
• What responsibility do you want next?

Minutes 27–30: Actions

• Who owns each action?
• What should be reviewed next time?

If a sensitive or important topic emerges, abandon the template and handle the real conversation.

Meeting formats can vary, but clarity about purpose, ownership, and follow-up matters in every setting. Image: Albinolongoria, Wikimedia Commons, CC BY-SA 4.0.

53. A Five-Minute Preparation Routine for Managers

Before the meeting:

1. Read the employee’s agenda items.
2. Review last meeting’s open actions.
3. Identify one piece of specific recognition or feedback if there is one.
4. Check whether a deadline, workload change, or organizational announcement affects the employee.
5. Choose one development or relationship question if the agenda is light.

This prevents the manager from arriving and asking the employee to explain everything from scratch.

54. A Five-Minute Preparation Routine for Employees

An employee can prepare by asking:

1. What do I need a decision on?
2. What is blocked?
3. What am I unsure about?
4. What feedback do I need?
5. What do I want my manager to understand that is not visible in the normal workflow?

Add the most important items to the shared agenda before the meeting.

55. A Monthly Health Check for the One-on-One System

Review the process, not just the conversation.

Ask:

• Are meetings happening consistently?
• Does the employee contribute agenda topics?
• Are actions completed?
• Is development discussed at least periodically?
• Are feedback and recognition timely?
• Are operational updates consuming too much time?
• Are difficult topics surfacing early enough?

If several answers are no, change the structure rather than concluding that the employee “does not like one-on-ones.”

Frequently Asked Questions

How often should one-on-one meetings happen?

Weekly or biweekly is common, but the right cadence depends on role maturity, change, communication needs, and organizational context. New employees and rapidly changing work usually benefit from more frequent check-ins. The key is consistency and enough frequency to surface issues before they become stale.

How long should a one-on-one be?

Many teams use 30 minutes, but 20, 45, or 60 minutes can be appropriate. Choose a duration that allows meaningful discussion without filling time artificially. If important topics repeatedly spill over, improve asynchronous preparation or increase the time.

Should the manager or employee own the agenda?

Both should contribute, but the direct report should have meaningful ownership. GitLab’s current guidance explicitly prefers the employee to contribute most agenda items. Managers still need space for feedback, priorities, and important organizational context.

Should project status be discussed?

Only when discussion is needed. Routine status can often be shared asynchronously. Use synchronous time for blockers, decisions, tradeoffs, feedback, and topics where context or coaching matters.

Should negative feedback wait until the next one-on-one?

No. Important feedback should generally be delivered close to the relevant event. The one-on-one can follow up on it and discuss patterns, but delaying meaningful feedback simply because a meeting is scheduled reduces usefulness and can create surprises.

What if there is nothing on the agenda?

Do not cancel automatically. Use the time for development, workload, team relationships, process improvement, future goals, or feedback. A quiet operational week can create room for the conversations that are normally crowded out.

Should one-on-one notes be shared?

A private shared document between manager and employee is common, but follow your organization’s policy. Sensitive HR or formal performance records may belong in designated systems. Do not store unnecessary personal details.

Should managers ask about personal life?

Managers can create space for personal context that affects work, but employees should not feel pressured to disclose private information. Respect boundaries and stay within the manager role.

Can one-on-ones be asynchronous?

Some updates and even some structured check-ins can happen asynchronously, especially in distributed teams. However, sensitive feedback, complex coaching, relationship building, and nuanced discussions often benefit from synchronous conversation. GitLab currently supports a mix while still recommending regular synchronous contact.

How can a manager get more honest feedback?

Ask specific, answerable questions and demonstrate follow-through. “What information do I give you too late?” is easier to answer than “Any feedback for me?” Employees become more candid when prior feedback leads to visible action rather than defensiveness.

Conclusion: Make the Meeting a Reliable Place for What Other Systems Miss

A strong one-on-one is not defined by a template. It is defined by the quality of information, decisions, feedback, development, and follow-through that the meeting makes possible.

Keep routine updates asynchronous when possible. Use a shared agenda. Let the employee own meaningful space. Ask open-ended questions that surface blockers and judgment. Give feedback promptly. Protect time for development. Document decisions and actions without turning the meeting into surveillance. Most importantly, complete the commitments you make.

The biggest mistake to avoid is treating the one-on-one as expendable whenever work becomes busy. Busy periods are often when unclear priorities, overload, and hidden blockers matter most.

If you want one practical change for the next meeting, add one question to the agenda before the employee does: “What is one thing you need from me that would make your work easier or more effective?” Then make sure the answer produces a real decision, action, or honest explanation.

Sources and Further Reading

• GitLab Handbook — 1-1 Meetings
• GitLab Handbook — Engineering Manager Meetings
• U.S. Office of Personnel Management — Performance Management Roadmap for Supervisors
• U.S. Office of Personnel Management — Communication Skills
• U.S. Office of Personnel Management — Monitoring and Developing
• UC Davis Human Resources — Experience Conversations Toolkit
• UC Davis Human Resources — The First 90 Days
• Atlassian — 1-on-1 Meeting Template

Image Credits

• “Wikimedia UK office meeting.jpg” — Jwslubbock, Wikimedia Commons, CC BY-SA 4.0.
• “Business professional engages in note-taking during a meeting at a modern office desk.jpg” — Shixart1985, Wikimedia Commons, CC BY 2.0.
• “Women at Work Meeting.jpg” — Albinolongoria, Wikimedia Commons, CC BY-SA 4.0.