One-on-Ones: The 30-Minute Habit That Holds a Team
How to run useful one-on-ones with engineers: cadence, agenda template, what to avoid, and the topic rotation that catches problems before they hit retros.
Table of contents
The single highest-leverage 30 minutes a tech lead spends each week is the one-on-one. Done well, problems surface here weeks before they hit retro or HR. Done poorly, the meeting becomes a status report and the engineer slowly disengages. This chapter shows the format that works and the topics that matter.
When does the 1-on-1 cadence actually start mattering?
Three signals.
You have direct reports. From the first day someone reports to you, the 1-on-1 is the contract. Skipping signals "I don't prioritise you".
Engineers are quiet in groups but issues exist. Standups look fine; retros are short; team morale feels off. The 1-on-1 is where the silence gets words.
Career growth conversations are coming. Promotion cases, mid-year reviews, growth plans need a paper trail of regular discussion - not invented at review time.
If you have no direct reports and you are a peer tech lead, 1-on-1s are still useful but optional. Use them with engineers who pair with you regularly.
What is the cost of skipping or doing 1-on-1s poorly?
Three failure modes.
Surprise resignations. "I had no idea they were unhappy." The unhappiness was there for months; it never had a 30-minute private surface.
Career stagnation. Engineer wants growth opportunities; never told manager directly. Manager assigned junior work; engineer left in 6 months.
1-on-1 as status report. "What did you ship this week?" The engineer has answered the same question at standup. The 1-on-1 becomes redundant; engineer loses interest in attending.
What does the minimal 1-on-1 format look like?
# 1-on-1: {{ Manager }} <-> {{ Engineer }}
## Standing agenda (rotates focus weekly)
- 0-5 min: Status this week (briefly)
- 5-10 min: Blockers I cannot solve myself
- 10-25 min: Rotating topic (see below)
- 25-30 min: Open / anything else
## Rotating topics (pick one per week)
- Week 1: How is the current project going? What is hardest?
- Week 2: Career goals for this quarter
- Week 3: Feedback for me (the manager)
- Week 4: Team dynamics - what is healthy / unhealthy?
## Running notes
### 2026-06-15
- Project: refund flow on track; concerned about Stripe SDK gap
- Blocker: needs design review on email template - I will ping
- Career: wants to lead the next medium-sized project
- Action: I'll find a project for them in Q3
### 2026-06-08
- ...
The shared running notes are the artifact. Engineer can scroll back to see what we agreed; manager can reference past discussions in performance review.
How does cadence scale to multi-team?
flowchart TB
EM[EM] --> Direct1[Direct report 1<br/>weekly]
EM --> Direct2[Direct report 2<br/>weekly]
EM --> Direct3[Direct report 3<br/>weekly]
EM --> Skip1[Skip-level 1<br/>monthly]
EM --> Skip2[Skip-level 2<br/>monthly]
EM --> Peer[Peer EM<br/>bi-weekly]
A typical EM with 5 direct reports and 5 skip-levels spends ~7-8 hours per week on 1-on-1s. That is the job. If the EM is also coding, the 1-on-1 budget is the first thing to cut - and it shouldn't be. The EM role is people; if there is no time for people, the role is wrong.
What failure modes does the 1-on-1 introduce?
- Becomes status report. Engineer reports work; manager asks for updates. Mitigation: status comes from standup; 1-on-1 is for what does not fit there.
- Cancelled often. "Let's skip this week, I'm slammed." Mitigation: skip rarely; if conflicts force cancellation, reschedule the same week, not "let's catch up later".
- No follow-through. Engineer raises issue; manager acknowledges; nothing changes. Mitigation: each 1-on-1 ends with action items for both sides; review at next meeting.
- Manager monologues. Manager talks 80% of the time. Mitigation: count who is talking; aim for 20% manager / 80% engineer.
When are 1-on-1s overkill?
Two cases.
Truly senior, autonomous engineer. A staff engineer who only needs you for promotion conversations and crisis decisions might prefer monthly. Ask them.
Cross-functional matrix without authority. If you are a PM with engineers who don't report to you, a weekly 1-on-1 is manager-level overkill. A bi-weekly project-context check is appropriate.
Where should you go from here?
Next chapter: hiring and onboarding - how to add people to the team in a way that increases capacity rather than slowing it. After that, performance and feedback covers the structured conversations that 1-on-1s feed into.