liveBook · Manning

One-on-one meeting

As explained in Think Like a CTO

A one-on-one meeting is a private, recurring conversation between a manager and an individual team member focused on the person's well-being, concerns, and development.

A one-on-one meeting is a regular, private conversation between a manager and one person. With a team lead, its purpose is to check on well-being, hear concerns, and support development—not to run through project status. Hold it weekly or every other week for about 15–30 minutes, and protect the time rather than routinely postponing it. section 6.5

Let the person raise difficulties, including concerns about your management style. Listen, sympathize, and offer guidance where useful; you do not need to have every answer. A short conversation can also help a new lead reflect on a mistake and make a small correction before it grows. section 6.5

Table 6.3 Meeting format (view table figure)

In-scope topics

Out-of-scope topics

Personal goals

Project updates

Areas for improvement

New tasks you want them to address

Concerns they have regarding their execution

Disciplinary talks

Analysis of a recent event

Gossip about other members

Company updates

Use the meeting-format table to keep the conversation focused. Personal goals, areas for improvement, and reflection on a recent event belong here; project updates, new task assignments, disciplinary talks, and gossip do not. section 6.5

A conversation that opens a door

If a team lead is nervous about addressing the group, a one-on-one gives them room to say so and ask for help. You might also ask how they felt a recent conversation went before offering your own observation. section 6.5

The format changes with the relationship. A regular one-on-one with the CEO can focus on long-term strategy, expectations, and alignment beyond day-to-day management meetings. When taking over a group, meet individually with as many people as possible and ask what they would change. Listen before promising solutions: their answers help you understand the organization. section 2.1.3 section 14.7

How Think Like a CTO covers it

How deep it goes
Defines cadence, duration, confidentiality, conversation boundaries, and listening practices, while directing project updates and disciplinary talks elsewhere.
Examples
Uses a nervous team lead, reflection on a recent conversation, and a new leader's question about what employees would change.
What it assumes
Assumes responsibility for team leads or a working relationship with a CEO; defines the meeting format without requiring a specialized method.
What you can do after
Practice/perform it by protecting regular private time, listening to individual concerns, and keeping operational or disciplinary topics in other meetings.
How it connects
Connects team management and leadership development with managing up and strategic alignment.

Also explained in

Compare how 3 books explain one-on-one meeting →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.