1-on-1 Meeting Template for Tech Leads: Agenda & Questions

The 1:1 meeting is the single most important recurring event on your calendar as a tech lead. It is where trust is built, problems surface early, and your team members feel heard. Yet most tech leads either skip 1:1s when things get busy or run them as status updates that could have been a Slack message.

Over 22 years of leading engineering teams, I have refined my 1:1 format through trial and error across startups, scale-ups, and enterprise environments. The template below is what I teach in the First Lead course, and it has been tested by over 1,000 students.

Why 1:1 Meetings Matter More Than You Think

A well-run 1:1 does three things that no other meeting can accomplish. First, it creates a private space where team members share concerns they would never raise in a group setting. Second, it gives you early warning signals about burnout, frustration, or disengagement. Third, it demonstrates that you value the person, not just their output.

I once had a senior developer who seemed fine in every standup and retro. It was only in a 1:1 that she told me she was considering leaving because she felt stuck on maintenance work. That conversation led to a project reassignment that kept a key team member for another two years.

How to Use This Template

Do not read this template like a script. Use it as a framework. Some weeks you will spend the entire 30 minutes on one topic because something important surfaced. That is exactly how it should work. The structure ensures you cover the important areas over time, not that you check every box every week.

The best 1:1s feel like a conversation between two people who respect each other. The worst feel like a performance review happening every week. Use this template to steer toward the former.

Common 1:1 Mistakes Tech Leads Make

• Turning it into a status update. If you are just asking what they worked on this week, you are wasting both of your time. Use standups and project trackers for status.
• Doing all the talking. You should be listening 70% of the time. If you catch yourself monologuing, stop and ask a question.
• Canceling when busy. This sends the message that they are less important than whatever else is on your calendar. Reschedule instead.
• Avoiding difficult feedback. The 1:1 is the right place to address performance concerns early. Waiting for a formal review is too late. For more on this, see our guide on handling underperformers.
• Not taking notes. If you do not track action items and follow up, your team will stop raising issues because nothing changes.

Adapting the Template for Different Team Members

Senior engineers often prefer less structure and more strategic discussion. Let them drive the conversation and focus Part 3 on leadership growth and architecture ownership. Junior engineers need more active guidance. Spend more time in Part 3 and provide specific, actionable feedback with examples.

For remote team members, turn your camera on and give them your full attention. Close other tabs. The 1:1 is often the only face time they get with you all week.