1-on-1 Meeting Guide for Tech Leads: Structure, Questions, and Templates

Of all the meetings on a tech lead's calendar, one-on-ones are the most important — and the most frequently done poorly. I have seen tech leads treat them as status updates, skip them when things get busy, or turn them into monologues about what the team member should be doing differently. None of these approaches work.

Done well, one-on-ones are the foundation of everything else: trust, feedback, career development, conflict resolution, and retention. Done poorly, they are a waste of everyone's time. After conducting thousands of one-on-ones over my career and training 1,000+ tech leads on this skill, I have distilled what works into this comprehensive guide.

Why 1-on-1s Matter More Than Any Other Meeting

One-on-ones serve purposes that no other meeting format can fulfill:

• Trust building: Trust is not built in group settings. It is built in private, honest conversations where people feel safe being vulnerable. Without trust, feedback does not land, concerns go unraised, and problems fester.
• Early warning system: People rarely announce their problems in team meetings. In a private 1-on-1, they are far more likely to share frustrations, concerns about colleagues, or signs of burnout. These early signals let you address issues before they become crises.
• Career development: Group settings are terrible for personalized career discussions. Each person has unique goals, strengths, and development areas that require individual attention.
• Feedback channel: Both giving feedback and receiving it are best done privately. Your team member needs space to process feedback without an audience, and they are more likely to give you honest feedback about your leadership in a 1-on-1 than in a team retrospective.
• Retention: Research consistently shows that the relationship between an employee and their direct manager is the single strongest predictor of retention. One-on-ones are where that relationship is built.

Frequency and Duration

There is no universally correct frequency, but here are the guidelines I recommend:

Critical rule: Never cancel a 1-on-1. Rescheduling is fine. Canceling sends the message that the meeting — and by extension, the person — is not important. If you consistently cancel 1-on-1s, you are actively eroding trust. The day you skip a 1-on-1 is often the day your team member needed it most.

Duration should be 30 minutes minimum. I find that shorter meetings do not leave enough time for the conversation to move beyond surface-level topics. For complex situations — career discussions, performance conversations, or relationship building with new team members — 45 minutes is better.

The 3-Part Meeting Structure

I recommend a simple three-part structure that keeps the meeting focused while allowing flexibility:

Part 1: Their Agenda (10-15 minutes)

Start by asking what they want to discuss. This is their meeting, not yours. Whatever is on their mind takes priority. Common topics include blockers, frustrations, questions about projects, feedback on team dynamics, or career concerns. Listen actively — this is not the time for you to problem-solve. Understand first.

Part 2: Your Agenda (5-10 minutes)

After addressing their topics, share what you want to discuss. This might be feedback on recent work, context about upcoming changes, questions about their experience, or topics from your leadership perspective. Keep your agenda items brief. If a topic requires extended discussion, schedule a separate meeting.

Part 3: Growth and Development (5-10 minutes)

End with a forward-looking discussion. What skills are they developing? What challenges are they tackling? What projects or opportunities would stretch them? This section is sometimes skipped when the first two parts run long, but make it a priority at least once a month — it is where the magic happens for long-term retention and engagement.

The Question Framework

The quality of a 1-on-1 depends on the quality of your questions. Here is a framework organized by category. You do not need to ask all of these in every meeting — pick 2-3 that fit the context.

Opening Questions

• "How are you doing? Not the work question — how are you, really?"
• "What is on your mind this week?"
• "What is the highlight of your week so far?"
• "Is there anything you want to talk about that you have been putting off?"

Work and Projects

• "What is the biggest challenge you are facing right now?"
• "Is there anything blocking your progress that I can help with?"
• "What part of your current project is most engaging? Least engaging?"
• "Do you feel like you have clarity on what success looks like for your current work?"
• "Are there any decisions that need to be made that are stalling?"

Team and Collaboration

• "How are things going with the rest of the team?"
• "Is there anyone you are finding it difficult to work with?"
• "Do you feel like your opinions are heard and valued in team discussions?"
• "Is there something the team should start doing, stop doing, or continue doing?"

Career and Growth

• "What skills do you want to develop in the next 6 months?"
• "Where do you see yourself in 2-3 years?"
• "Is there a type of work you wish you were doing more of?"
• "Do you feel like you are growing in this role? What would accelerate that?"
• "Is there someone in the organization you would like to learn from?"

Feedback (For You)

• "Is there anything I could be doing differently to support you better?"
• "What is one thing I should change about how I lead the team?"
• "Do you feel comfortable giving me honest feedback? What would make it easier?"
• "Was there a recent situation where you wished I had handled things differently?"

Your First 1-on-1 with a New Team Member

The first 1-on-1 sets the tone for the entire relationship. Invest extra time and thought into making it meaningful. Here is a structure I use:

Introduction (5 minutes): Share a bit about your background, your leadership style, and what you care about. Be genuine and specific: "I believe in direct feedback delivered with empathy. I would rather tell you something uncomfortable early than let it build up."

Learning about them (15 minutes): Ask questions to understand their motivations and preferences:

• "What brought you to this team?"
• "What motivates you at work? What drains your energy?"
• "How do you prefer to receive feedback?"
• "What does a great week look like for you?"
• "What are your career goals for the next 1-2 years?"

Setting expectations (10 minutes): Be explicit about how 1-on-1s will work:

• "This is your meeting. You set the agenda. I am here to support you."
• "Nothing you share here goes to the team without your permission."
• "I will never cancel this meeting. If there is a conflict, we will reschedule."
• "I encourage you to bring hard topics. The harder the topic, the more important it is to discuss."

Logistics (5 minutes): Agree on frequency, duration, and format (in-person, video, walking meeting). Set up a shared document for agenda items and notes.

Career Growth Conversations

Career conversations deserve special attention. They should happen at least monthly as a dedicated portion of the 1-on-1. Here is how to make them effective:

Understand their aspirations. Do they want to move into management? Go deeper technically? Start something of their own? There is no wrong answer, but you cannot support their growth if you do not know where they want to go.

Assess gaps honestly. Based on where they want to go, what skills or experiences are they missing? Be direct about this. Sugarcoating helps nobody. "You want to become a senior engineer, and I think your technical skills are strong. The gap I see is in your ability to influence technical decisions across the team without being the one who implements everything."

Create development plans together. Identify specific actions: "Over the next quarter, I would like you to lead the design review for the new authentication system. This will practice your communication skills and give you experience driving cross-team alignment."

Follow up. Development plans without follow-up are worthless. Check in on progress monthly. Adjust the plan as circumstances change. Celebrate growth when you see it.

Giving and Receiving Feedback

One-on-ones are the primary venue for feedback, both giving and receiving. Here is how to do both well:

Giving Feedback: The SBI Model

Use the Situation-Behavior-Impact (SBI) framework to make feedback specific and actionable:

• Situation: "In yesterday's design review..."
• Behavior: "...you interrupted Maria three times while she was presenting her approach..."
• Impact: "...which made her visibly uncomfortable and prevented the team from hearing her full proposal."

Then open a dialogue: "What was going on for you in that moment?" This approach avoids generalizations ("you always interrupt people") and character judgments ("you are disrespectful"). It focuses on observable behavior and its concrete impact.

Receiving Feedback

The hardest feedback to receive is feedback about your own leadership. But it is also the most valuable. When asking for feedback:

• Ask specific questions rather than general ones. "What is one thing I should change?" is better than "Do you have any feedback for me?"
• When you receive feedback, say "thank you" first. Do not defend or explain. Process it later.
• Follow up on feedback you have received. "Last month you mentioned I should give more context when assigning projects. How am I doing on that?"
• Show vulnerability. If you only ask for feedback when everything is going well, people will not believe you want honest input.

Handling Difficult Conversations

Some 1-on-1s will involve difficult topics: performance concerns, interpersonal conflicts, or personal issues affecting work. These conversations are uncomfortable, but avoiding them is always worse. The First Lead course includes roleplay exercises for each of these scenarios, but here are the fundamentals:

Performance Concerns

When you need to address underperformance:

1. Do not delay. The longer you wait, the harder the conversation and the less fair to the person. They deserve to know where they stand.
2. Be specific. "Your performance is not meeting expectations" is useless. "In the last three sprints, you have completed 40% fewer story points than planned, and two of your PRs required significant rework after code review" is actionable.
3. Seek to understand. Ask what is going on. There may be personal issues, unclear expectations, or team dynamics you are not aware of.
4. Create a concrete plan. Define specific, measurable improvements with a timeline. "Over the next four weeks, I need to see on-time completion of at least 80% of your committed stories." See our performance review guide for more detail.
5. Follow up consistently. Check progress weekly. Acknowledge improvements. Address continued shortfalls directly.

Interpersonal Conflicts

When two team members are not getting along:

1. Meet with each person individually first. Understand each perspective without judgment.
2. Look for common ground. Often, both parties want the same outcome but disagree on the approach.
3. If needed, facilitate a joint conversation. Set ground rules: use "I" statements, focus on behaviors not personalities, seek solutions not blame.
4. Follow up to ensure the resolution is holding.

Personal Issues Affecting Work

When someone shares personal difficulties:

• Listen with empathy. Do not rush to problem-solve.
• Ask how you can support them at work. Reduced workload? Flexible hours? Time off?
• Know your company's resources: EAP (Employee Assistance Program), mental health benefits, leave policies.
• Follow up, but respect boundaries. Check in without prying.

Common Mistakes to Avoid

• Turning 1-on-1s into status updates. If the entire conversation is about project progress, you are doing it wrong. Use standups and project tools for status. 1-on-1s are for the person, not the project.
• Doing all the talking. You should be speaking less than 30% of the time. If you are talking more, you are not listening enough. Ask more questions. Embrace silence — it gives people space to think.
• Solving every problem. When someone shares a challenge, your instinct as an engineer is to jump to solutions. Resist this. Ask "What have you considered?" or "What would you do if you were the decision maker?" Coaching is more valuable than advising.
• Avoiding difficult topics. If you know there is an elephant in the room and you do not address it, you lose credibility. Your team member knows you know, and they are waiting for you to bring it up.
• No notes or follow-through. If you commit to something in a 1-on-1 and do not follow through, you are actively destroying trust. Keep notes. Track action items. Deliver on your promises.
• Same questions every week. Rotating your questions keeps the conversation fresh and explores different dimensions of the person's experience.

Ready-to-Use Templates

Weekly 1-on-1 Template

Date: ____
Name: ____

## Their Topics
-
-

## My Topics
-
-

## Key Takeaways
-

## Action Items
- [ ] (Them):
- [ ] (Me):

## Notes for Next Time
- 

Quarterly Career Check-In Template

Date: ____
Name: ____

## Career Goals Review
- What are your current career goals?
- Progress since last check-in:
- What has changed?

## Strengths and Growth Areas
- What are you doing well?
- Where do you want to improve?

## Development Plan
- Skill to develop:
- How (project, mentoring, training):
- Timeline:
- Success criteria:

## My Commitments
- How I will support your growth:
- Opportunities I will create:

Difficult Conversation Preparation Template

## The Issue
What specific behavior or situation needs to be addressed?

## Evidence
What concrete examples do I have? (SBI format)
- Situation 1:
- Situation 2:

## Impact
What is the impact on the team, project, or individual?

## Desired Outcome
What change do I want to see?

## Support
What support can I offer to help them improve?

## Possible Reactions
How might they react? How will I respond?

## Follow-up Plan
When will I check in on progress?

"The 1-on-1 is where leadership actually happens. Not in team meetings, not in Slack channels, not in all-hands presentations. In the quiet, honest, one-on-one conversation where a person feels seen, heard, and supported — that is where you build the trust that makes everything else possible."