liveBook · Manning

One-on-one meeting

Also called check-ins

A one-on-one meeting is a private conversation between two people for discussion, information exchange, feedback, support, or collaboration.

How 3 Manning books explain it

Think Like a Software Engineering Manager

A one-on-one meeting is a recurring private conversation between a manager and an individual team member for discussion, support, and feedback.

How it is used
Supports private, recurring conversations about employee needs, growth, concerns, and feedback within engineering management.
How deep it goes
Defines the meeting and gives questions, feedback practices, and workplace cases, without prescribing a fixed agenda.
Examples
Uses core working hours feedback, a behavioral coaching conversation, and introductory meetings with engineers and stakeholders.
What you can do after
Practice/perform it by asking open questions, listening, exchanging actionable feedback, and following up on individual needs.

Read how Think Like a Software Engineering Manager explains one-on-one meeting →

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.

How it is used
Provides a protected check-in for team leads, a strategic alignment conversation with the CEO, or a listening opportunity for a new leader.
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 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.

Read how Think Like a CTO explains one-on-one meeting →

Lead Developer Career Guide

A private meeting between two people for discussing concerns, feedback, support, or progress.

How it is used
Uses private conversations to understand people, provide tailored guidance, build trust, and address concerns or conflicts.
How deep it goes
Develops recurring conversations, open-ended questions, active listening, feedback, boundary-respecting support, and conflict response.
Examples
Uses career and well-being questions, team-member concerns, and an illness-related absence that develops into conflict mediation.
What you can do after
Practice/perform empathetic listening, constructive feedback, trust-building, and supportive responses to workplace concerns.

Read how Lead Developer Career Guide explains one-on-one meeting →

Also covered in

What to know first

Related concepts

Questions about one-on-one meeting

What is one-on-one meeting?

A one-on-one meeting is a private conversation between two people for discussion, information exchange, feedback, support, or collaboration.

Which Manning books explain one-on-one meeting?

Think Like a Software Engineering Manager, Think Like a CTO and Lead Developer Career Guide.

What should I know before learning one-on-one meeting?

Manning books that teach one-on-one meeting usually introduce direct report, mentoring, career goal and communication first.

What is one-on-one meeting a kind of?

One-on-one meeting is a kind of team discussion. A team discussion is a collaborative interaction in which participants exchange information, address concerns, make decisions, or coordinate work.

What are the parts of one-on-one meeting?

One-on-one meeting includes performance review.

What is one-on-one meeting also called?

One-on-one meeting is also called check-ins.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.