LabHub

Blog

Effective One-on-One Meeting Guide

한국어English日本語

Effective One-on-One Meeting Guide

Introduction: Why the 1:1 Is Essential

The 1:1 is the most underrated and, at the same time, the most powerful management tool in any organization. In High Output Management, Andy Grove declared flatly that the 1:1 is a manager's single most important tool. During his tenure as CEO of Intel he ran dozens of 1:1s every week, taking the pulse of the whole organization through them.

And yet in many organizations the 1:1 is not run well. According to a 2025 Lattice survey, 43% of employees feel they are not having a meaningful conversation in the 1:1 with their manager, and 36% of managers reported that they struggle to prepare for one.

There are two core reasons 1:1s fail. First, the purpose is unclear. Status reporting, feedback, career conversations, and brainstorming get mixed together, and none of them gets done properly. Second, preparation is thin. Both the manager and the teammate end up wondering "what are we going to talk about today?" minutes before the meeting starts, over and over.

This article draws on Camille Fournier's The Manager's Path, Kim Scott's Radical Candor, Will Larson's An Elegant Puzzle, and Lara Hogan's 1:1 framework to lay out a practical 1:1 guide that both managers and ICs can use.

The Essence of the 1:1: What Is This Time For

The 1:1 Belongs to Your Teammate

In the a16z blog post "One on One", Ben Horowitz stresses that the 1:1 is not the manager's meeting but the teammate's meeting. This is not a mere slogan; it is the essential philosophy of the 1:1. The teammate should drive the agenda, and the manager's role is to listen and support.

The Four Purposes of a 1:1

PurposeDescriptionFrequencyExample
Building rapportForming trust and psychological safetyEvery 1:1Catching up, personal interests
Exchanging feedbackGiving and receiving feedback both waysBiweeklyBehavioral feedback using the SBI model
Career developmentDiscussing long-term growth directionMonthlySkill development plans, promotion paths
Clearing blockersFinding and removing impediments to workAs neededCross-team collaboration issues, technical decisions

Note: a 1:1 is not a "status report" slot. Share project progress in standup or through asynchronous tools, and use the 1:1 for the context, emotions, and worries hiding behind the numbers.

The Manager's View: Preparing and Running 1:1s

The First 1:1: Laying the Foundation of the Relationship

Lara Hogan lists questions you must ask in a first 1:1 with a new teammate. These questions are essential for understanding the other person's communication style and motivations.

Questions to ask in a first 1:1:

  1. "How do you prefer to receive feedback? Right there in the moment, or after some time has passed?"
  2. "When do you feel most motivated?"
  3. "What frustrates you?"
  4. "Is there anything about me, as your manager, that would be useful for you to know?"
  5. "Is there anything outside work that matters a great deal to you?"

Write down the answers and keep referring back to them in later 1:1s.

An Agenda Design Framework

A 1:1 agenda works best when it is run flexibly inside a fixed structure.

A 30-minute 1:1 structure (recommended):

TimeContentDriven by
0-5 minCheck-in: how they are doing, energy levelTeammate
5-15 minTeammate's agenda: worries, blockers, ideasTeammate
15-22 minManager's agenda: feedback, context sharing, coachingManager
22-28 minCareer and growth conversation (biweekly)Both
28-30 minWrap up action items, prepare for the next meetingBoth

A 60-minute 1:1 structure (a monthly deep dive):

TimeContentDriven by
0-10 minCheck-in and review of the previous action itemsBoth
10-25 minTeammate's agenda: topics that need an in-depth discussionTeammate
25-40 minCareer development: goals, skill gaps, growth plansBoth
40-50 minFeedback exchange, including a request for feedback on the managerBoth
50-55 minOrganizational context: strategy, changes, where things are headingManager
55-60 minWrap up action itemsBoth

Effective Questioning Techniques

The most important skill in a 1:1 is asking questions. A good question helps a teammate organize their own thinking and find their own solution.

Comparing question types: good questions vs bad questions

Bad questionThe problemA better alternative
"Everything going fine?"A closed question that ends in yes or no"What was the most challenging thing this week?"
"Why did you do it that way?"An interrogating question that provokes defensiveness"What were you weighing when you made that decision?"
"Anything I can help with?"Too vague, easy to answer with "nothing""Is there anything stuck in your current work that I could unblock for you?"
"How is the project going?"Invites a status report"What worries you most about the project?"
"Is the team mood okay?"Draws out only a surface-level answer"Has anything on the team felt uncomfortable or in need of improvement lately?"
"You want a good review, right?"A question that applies pressure"Is there a growth area you especially want to focus on next quarter?"

Michael Bungay Stanier's seven coaching questions (drawn from The Coaching Habit):

  1. "What is on your mind?" (Kickstart Question)
  2. "And what else?" (AWE Question - And What Else)
  3. "What is the real challenge here for you?" (Focus Question)
  4. "What do you want?" (Foundation Question)
  5. "How can I help?" (Lazy Question - so that you do not hand over a solution immediately)
  6. "What are you saying yes to?" (Strategic Question)
  7. "What was most useful for you in this conversation?" (Learning Question)

How to Deliver Feedback

The SBI Model (Situation-Behavior-Impact)

The SBI model, developed at the Center for Creative Leadership (CCL), is the most widely validated framework for delivering feedback concretely and objectively.

Structure:

An example of positive feedback:

"During the incident response last Wednesday (S), you shared the situation in the team Slack channel first and proposed how to split up the roles (B), and because of that the whole team aligned quickly and we cut 30 minutes off the recovery time (I)."

An example of developmental feedback:

"In yesterday's code review (S), your review comment said only 'this is wrong' (B), and the junior developer could not tell why it was wrong, got confused, and the PR sat still for two days (I). Next time, could you write out why it is a problem along with an alternative?"

The COIN Model (Context-Observation-Impact-Next)

The COIN model adds Next (the next step) to SBI, which makes the feedback more action-oriented.

Structure:

Example:

"In this sprint planning (C), you took on every technically difficult task yourself (O), which shrinks the growth opportunities for the rest of the team and raises your own burnout risk (I). In the next planning, would you try handing some of the challenging tasks to other teammates and mentoring them through it? (N)"

Coaching vs Mentoring vs Directing: When to Use Which

ApproachCore behaviorWhen it fitsExample
CoachingAsking questions so they find the answer themselvesThe teammate has the capability but cannot find a direction"How do you think you might approach this problem?"
MentoringSharing your experience and advisingThe teammate is facing something for the first time and needs a reference point"I ran into something similar, and back then this approach worked well."
DirectingTelling them concretely what to doAn emergency, or a severe lack of experience"For now, do A first and handle B tomorrow."

In The Manager's Path, Camille Fournier stresses that an excellent manager moves flexibly between coaching, mentoring, and directing depending on the situation. Only directing a senior engineer violates their autonomy; only coaching a junior engineer can leave them unable to find a direction and frustrated.

The IC (Individual Contributor) View: Getting Value Out of Your 1:1

The 1:1 Is Your Time

For an IC, using the 1:1 well is the strongest piece of leverage available for career growth. Rather than waiting for the manager to lead a good 1:1, it is far more effective for the IC to prepare and drive the meeting actively.

A Pre-Meeting Preparation Checklist

What to prepare 48 hours before a 1:1:

CategoryItem to checkExample
Sharing resultsTwo or three main results from the week"Merged PR #234 and improved search speed by 40%"
BlockersWhat is stuck and exactly what help you need"Cannot proceed because the data team's API spec is not finalized"
Feedback requestsThe specific area you want feedback on"Is there anything I could improve about yesterday's presentation?"
CareerGrowth topics you want to discuss"I want to build system design skills; what opportunities are there?"
Organizational contextQuestions about direction and strategy you are curious about"Is there anything about next quarter's team roadmap I could learn early?"

Drawing Out the Career Growth Conversation

Many ICs feel that "it is hard to bring up career topics" in a 1:1. The framework below makes it easy to open a career conversation naturally.

Will Larson's career conversation framework (drawn from An Elegant Puzzle):

  1. Establish where you are: "In the role I am doing now, what am I doing best and where am I falling short?"
  2. Set the goal: "Could we talk about the kind of role I would like to be doing six months or a year from now?"
  3. Analyze the gap: "What skill do you think I most urgently need to develop in order to get there?"
  4. Ask for the opportunity: "Is there a project or an opportunity where I could develop that skill?"
  5. Check the progress: "How am I tracking against the growth goal we discussed last month?"

Communicating Blockers and Frustrations Effectively

When you raise a frustration or a blocker, the key is to acknowledge the emotion but keep the conversation focused on the solution.

A bad example: "Team A misses their dates every single time and it is so annoying. Please do something about it."

A good example: "Coordinating schedules with Team A keeps running into trouble. Concretely, the last three API spec handoffs were each delayed by more than a week, and because of that our team's sprint plan gets shaken every time. Would it be all right for me to talk to the Team A lead directly? Or could you escalate it on our behalf?"

Structure: describe the situation + the concrete impact + a proposed solution or a specific request for help

Optimizing 1:1 Frequency, Duration, and Setting

The Right Meeting Frequency

SituationRecommended frequencyDurationWhy
A new teammate (onboarding period)Twice a week30 minFast adaptation and trust building
Junior engineerWeekly30-45 minContinuous coaching and growth support
Senior engineerWeekly or biweekly30 minRespect autonomy, go deep when needed
Your manager's manager (skip-level)Monthly30 minTaking the temperature of the whole organization
A crisis or conflict situationDaily or every other day15-30 minFast situational awareness and support

The core principle: Camille Fournier warns that reducing the frequency of 1:1s is fine, but cancelling a 1:1 sends the message "you are not important."

The Psychology of Time and Place

Running 1:1s in a Remote Setting

The Particular Challenges of a Remote 1:1

A remote 1:1 comes with difficulties that in-person meetings do not have.

ChallengeEffectResponse strategy
Fewer nonverbal cuesHard to read emotional stateEncourage cameras on, check on feelings explicitly
"Zoom fatigue"Reduced focus during the meetingKeep it under 30 minutes, sometimes use audio only
Time zonesHard to find a workable slotTake turns absorbing the inconvenient hour
Missing contextYou lose the information an office gives you for freeSpend longer catching up at the start of the 1:1
IsolationA weaker sense of connection to the teamCheck on relationships with teammates during the 1:1

Tips for Running Remote 1:1s

  1. Keep the camera policy flexible: instead of pressure to always be on camera, offer the option: "we can talk without cameras today if that is more comfortable"
  2. An asynchronous agenda up front: write the agenda in a shared document 24 hours before the meeting so the meeting time is used efficiently
  3. Use a digital whiteboard: use Miro, FigJam, and similar tools to visualize career maps or goal planning
  4. No recording: as a matter of principle, do not record a 1:1, for the sake of the trust and candor it depends on
  5. Sometimes just call: a plain phone call with no screen sharing can make the conversation more relaxed and more honest

Comparing 1:1 Tools and Templates

FeatureNotionFellow15FiveLatticeGoogle Docs
Agenda sharingO (free-form)O (structured)O (structured)O (structured)O (free-form)
Action item trackingManualAutomaticAutomaticAutomaticManual
1:1 note historyOOOOManaged manually
Calendar integrationExternalNativeNativeNativeNative
Feedback requestsXOOOX
Performance managementXOO (strength)O (strength)X
Team dashboardXOOOX
Price (per person/month)Free-$10$6-$9$4-$14On requestFree
Learning curveMediumLowLowMediumVery low
CustomizationVery highMediumMediumMediumHigh

Recommendation: for a small team of five or fewer, Google Docs or Notion is plenty. To run a consistent 1:1 process across an organization of 20 or more, Fellow or 15Five is effective. If you need integration with a performance management system, Lattice is a good choice.

Common Mistakes and Antipatterns

Antipattern 1: The 1:1 That Degenerated into a Status Report

Symptom: every 1:1 opens with "what did you do this week?" and closes with "what will you do next week?"

The problem: that conversation can happen in standup or on the Jira board. The unique value of the 1:1 - the deep conversation, the feedback, the career discussion - disappears.

Solution: set a rule. "Let us share project status asynchronously in Slack, and use the 1:1 to talk about the worries, the challenges, and the growth hiding behind the status."

Antipattern 2: The 1:1 That Keeps Getting Cancelled

Symptom: "this week is busy, let us push it to next week" - and only one or two actually happen each month.

The problem: in Radical Candor, Kim Scott warns that cancelling a 1:1 is like making a withdrawal from the relationship's savings account. Repeated often enough, the teammate concludes "I am not a priority for my manager."

Solution:

Antipattern 3: The 1:1 Where Only the Manager Talks

Symptom: the manager spends most of the time explaining organizational direction, passing along instructions, and sharing their own opinions.

The problem: the teammate only listens and closes with "understood." They never get out what they actually wanted to say.

Solution: apply the 70/30 rule. Aim for the teammate talking 70% of the time and the manager 30%. The manager needs to lead the conversation with questions, and to practice being comfortable with silence.

Antipattern 4: The Perfunctory "I Am Fine" 1:1

Symptom: "how are things?" - "fine." - "anything else you need?" - "no." - over in five minutes.

The problem: when only surface conversation repeats, psychological safety never forms and the real problems never come up for air.

Solution: use specific questions to draw the conversation deeper. "What took the most energy out of you this week?" produces a far richer conversation than "are you fine?"

Antipattern 5: The 1:1 Without Feedback

Symptom: six months of 1:1s, and not a single piece of specific feedback from the manager.

The problem: hearing about "areas that need improvement" for the first time at the performance review is a shock, and the chance to improve has already been lost.

Solution: apply Kim Scott's Radical Candor framework. Practice caring personally (Care Personally) and challenging directly (Challenge Directly) at the same time.

High challenge directlyLow challenge directly
High care personallyRadical CandorRuinous Empathy
Low care personallyObnoxious AggressionManipulative Insincerity

Most managers slip easily into Ruinous Empathy, avoiding honest feedback in the name of being considerate. It is comfortable in the short term, but it is the most harmful pattern of all for a teammate's growth.

Failure Cases and How to Recover

Case 1: Recovering a 1:1 That Lost Its Trust

Situation: the teammate finds out that the manager repeated something they shared in a 1:1 to another colleague. From then on the teammate keeps the 1:1 strictly surface-level.

Recovery procedure:

  1. Acknowledge and apologize: "I sincerely apologize for repeating what you shared with me last time to someone else. I recognize that I broke the trust of this 1:1."
  2. Reset the boundary: "From now on, nothing that comes up in our 1:1 will be shared without your explicit agreement."
  3. Invest the time: rebuilding trust takes time. Rebuild it through consistent behavior.
  4. Confirm: at the end of every 1:1, ask "is there anything from today that I may or may not share with others?"

Case 2: Introducing 1:1s to a Team That Never Had Them

Situation: you join as a new manager and the team has no 1:1 culture at all. The teammates react with "why would we do that?"

Introduction procedure:

  1. Explain the purpose: explain the purpose of the 1:1 in a full team meeting. "I care about each of your growth and each of your concerns, and I want dedicated time for that."
  2. Start with low expectations: begin with 30 minutes every other week to reduce the burden.
  3. Focus early on the relationship: spend the first month on getting to know each other, and start the deeper work conversations gradually.
  4. Collect feedback: after a month, ask "is the 1:1 helping? Is there anything to improve?"
  5. Share the wins: when a concrete problem gets solved through a 1:1, let the value of it be known naturally.

Case 3: Running 1:1s During a Conflict

Situation: two teammates are in serious disagreement, and each of them pours out their complaints about the other in their separate 1:1s.

Response procedure:

  1. Listen in each 1:1: hear both sides out without judging.
  2. Establish the facts: strip out the emotion and lay out the objective facts.
  3. Coach in the individual 1:1s: coach each of them toward understanding the other person's perspective.
  4. Propose a three-way meeting: when they are ready, propose a three-way meeting with the manager as mediator.
  5. Reach an agreement: get concrete behavioral commitments, and follow up on them in later 1:1s.

A 1:1 Question Bank (30 Example Questions by Category)

Rapport and Check-In (Questions 1-6)

  1. "If you rated your energy level this week from 1 to 10, what would it be? And why?"
  2. "Is there anything outside work you are enjoying lately?"
  3. "What made you laugh recently?"
  4. "What is the thing you cannot get out of your head right now?"
  5. "What was the most rewarding moment for you this month?"
  6. "Are you sleeping and resting well lately?" (checking for burnout signals)

Work and Projects (Questions 7-12)

  1. "What was the most challenging piece of work this week?"
  2. "What is the most uncertain part of what you are working on right now?"
  3. "What feels most unnecessary in your current work?"
  4. "Is there a blocker I could clear for you?"
  5. "What decision are you proudest of on the current project?"
  6. "If you were handed one extra day, what would you spend it on?"

Feedback (Questions 13-18)

  1. "Is there something I could be doing better as your manager?"
  2. "What has been working well inside the team lately?"
  3. "Is there a team process you feel needs improving?"
  4. "Was there a decision I made recently that you had doubts about?"
  5. "Is there an area of your work where you would like more frequent feedback?"
  6. "Is there anything about how our team communicates that feels uncomfortable or inefficient?"

Career Growth (Questions 19-24)

  1. "What kind of engineer do you want to be a year from now?"
  2. "Of the things you are learning in your current work, what is the most valuable?"
  3. "Is there a skill you want to develop but have had no opportunity to?"
  4. "Is there someone you look to as a role model? Why them?"
  5. "What do you think you most need to focus on right now to get promoted or level up?"
  6. "Is there more I could be doing for your growth?"

Team and Organization (Questions 25-30)

  1. "What is your favorite thing about this team?"
  2. "On a scale of 1 to 10, how much psychological safety do you feel the team has?"
  3. "What do you think a new teammate would find hardest to adjust to?"
  4. "If there is something our team is missing, what would it be?"
  5. "Is there anything about working with other teams you would like to see improved?"
  6. "Is there something our team could do better across the company as a whole?"

A 1:1 Meeting Note Template

Running effective 1:1s requires a consistent note template. Below is a template you can put to use immediately.

A weekly 1:1 note template:

FieldContent
DateYYYY-MM-DD
Check-inEnergy level (1-10), a one-line update
Teammate's agenda(written in advance by the teammate)
Manager's agenda(written in advance by the manager)
Discussion(recorded during the meeting)
FeedbackSummary of the feedback exchanged
Action itemsWho, what, by when
Next meeting agenda (advance)What you definitely want to cover next

Additional fields for the monthly deep dive:

FieldContent
Career goal progressProgress against last month's goals
Skill developmentWhat was learned, what was applied, what is next
Long-term concernsLong-range concerns about the team, org, or career
Feedback for the managerThe feedback the teammate wants to give the manager

Measuring the Effectiveness of 1:1s

How do you measure whether 1:1s are working? Combine quantitative and qualitative indicators.

Indicator typeWhat is measuredSign of a healthy state
Quantitative1:1 cancellation/deferral rateUnder 10% per month
QuantitativeAction item completion rateAbove 80%
QuantitativeTeammate satisfaction surveyAbove 4.0/5.0
QualitativeDepth of conversationGoes past surface talk into worries, feelings, and vision
QualitativeFeedback frequencyRegular two-way feedback between manager and teammate
QualitativeEarly detection of problemsRaised in the 1:1 first and resolved before escalation

Summary: The Core Principles of a Good 1:1

  1. The 1:1 belongs to your teammate: they drive the agenda and the manager listens
  2. Consistency is everything: do not cancel; hold it at the same time, with the same structure
  3. It is a deep conversation, not a status report: cover "how does it feel, what is hard" rather than "what did you do"
  4. Feedback is a gift: exchange concrete, timely feedback using the SBI and COIN models
  5. Have career conversations regularly: go deep on growth and career at least once a month
  6. Write it down and follow up: keep notes, track action items, and check on them in the next meeting
  7. Practice two-way feedback: managers should ask their teammates for feedback too, and change their behavior accordingly

A good 1:1 is built by the effort of both the manager and the teammate. It can feel awkward and formulaic at first, but practiced consistently it visibly changes the trust, the growth, and the results of a team. In your next 1:1 today, try just one of the questions from this article.

References

Comments

No comments yet.

Sign in to leave a comment