Why 1-on-1s Matter
One-on-one meetings are the single most important recurring meeting a tech lead or engineering manager has. They are the primary venue for building trust, providing feedback, understanding what is blocking your team members, and supporting their career growth. Yet many leaders treat 1-on-1s as optional or use them as status updates, which strips them of their value.
A well-run 1-on-1 is the team member's meeting, not yours. It is their protected time to raise concerns, discuss career goals, share feedback about the team or your leadership, and get support on challenges they are facing. Status updates belong in stand-ups and project tracking tools.
The Purpose of a 1-on-1
- Build Trust: Create a safe space for honest, bidirectional communication
- Provide Feedback: Give timely, specific feedback on both strengths and areas for growth
- Career Development: Discuss long-term goals and create actionable growth plans
- Early Warning System: Surface problems before they escalate into crises
- Remove Blockers: Identify and address obstacles the team member is facing
Frequency and Duration
The right cadence depends on the team member's experience level, how new they are to the team, and the current team situation:
Recommended Cadences
| Situation | Frequency | Duration |
|---|---|---|
| New team member (first 3 months) | Weekly | 30-45 min |
| Junior engineer | Weekly | 30 min |
| Mid-level engineer | Biweekly | 30 min |
| Senior engineer | Biweekly or Monthly | 30-45 min |
| During a crisis or performance concern | Weekly | 30-45 min |
Never cancel a 1-on-1 without rescheduling. Consistently canceling sends the message that the relationship is not a priority. If you must reschedule, do so proactively and explain why.
Structuring the Meeting
A loose structure helps ensure the conversation is productive without being rigid. A good approach is to divide the time into three sections:
## 1-on-1 Structure (30 minutes)
### Their Topics (10-15 min)
- What's on your mind?
- Anything you want to discuss that we haven't covered?
- Any blockers or frustrations?
### Your Topics (5-10 min)
- Feedback on recent work
- Updates on team or organizational changes
- Observations you want to share
### Growth and Career (5-10 min)
- Progress on growth goals
- Upcoming opportunities for stretch assignments
- Skills they want to developPowerful Questions to Ask
The quality of a 1-on-1 is determined by the quality of the questions you ask. Here are categories of questions that drive meaningful conversations:
Opening Questions
- What is on your mind this week?
- How are you feeling about work right now on a scale of 1-10?
- What was the best part of your week? The most frustrating?
Growth and Career Questions
- What skills do you want to develop in the next quarter?
- Where do you see yourself in two years?
- What kind of projects would stretch you in a good way?
- Is there anyone in the company you would like to learn from?
Feedback Questions
- What is one thing I could do differently to better support you?
- Do you feel like you are getting enough feedback from me?
- Is there a team process that is not working for you?
Team and Culture Questions
- How would you describe our team's culture to someone joining?
- Do you feel comfortable raising concerns in team meetings?
- Is there anyone on the team you would like to collaborate more with?
Common 1-on-1 Anti-patterns
- Status update meeting: Using the entire time to discuss task progress. Status belongs in stand-ups.
- The monologue: The leader talks for 80% of the time. The team member should do most of the talking.
- Only when there is a problem: 1-on-1s should happen consistently, not just when something is wrong.
- No follow-through: Agreeing to action items but never following up creates distrust.
- Avoiding hard conversations: Deferring difficult feedback until performance review time is unfair to the engineer.
Documenting 1-on-1s
Keeping light notes from each 1-on-1 is essential for tracking themes over time, following up on action items, and preparing for performance reviews. Use a shared document so both parties can add topics before the meeting.
## 1-on-1 Notes: [Name] - March 15, 2026
### Topics Discussed
- Feeling good about the auth service migration, ahead of schedule
- Wants more exposure to system design work
- Frustrated by slow PR review turnaround from Platform team
### Action Items
- [TL] Connect them with Sarah on the search redesign project
- [TL] Raise PR review SLA concern with Platform team lead
- [Engineer] Draft a proposal for the caching layer improvement
### Career/Growth Notes
- Interested in moving toward a senior role within 6 months
- Wants to practice giving technical presentationsGiving Feedback in 1-on-1s
The 1-on-1 is the ideal venue for giving both positive and constructive feedback. Use the SBI model (Situation, Behavior, Impact) to keep feedback specific and actionable:
- Situation: Describe the specific context ("In yesterday's design review...")
- Behavior: Describe the observable behavior ("You pushed back on the proposed API schema with clear examples of edge cases...")
- Impact: Describe the result ("...which helped us catch a breaking change before it went to production. The team appreciated that.")
Positive feedback should be given freely and frequently. Constructive feedback should be given promptly (do not save it for months) and with genuine care for the person's growth.
Summary
Effective 1-on-1s are the foundation of strong engineering leadership. They require consistency, genuine curiosity about your team members' experiences, and the courage to have honest conversations. Invest in these meetings and they will pay dividends in team trust, retention, and performance.