Manager–employee communication and listening
Glad We Met Summary: Make One-to-One Meetings Useful
*Glad We Met* helps managers make recurring one-to-one meetings useful to the employee by sharing agenda ownership, addressing work and relationship needs, and checking whether the promised support actually happens.
One-Sentence Answer
Glad We Met helps managers make recurring one-to-one meetings useful to the employee by sharing agenda ownership, addressing work and relationship needs, and checking whether the promised support actually happens.
What The Book Is About
A manager finishes a weekly meeting satisfied: the project dates are clear. The employee leaves disappointed: the conflict blocking those dates never came up. This guide uses that mismatch to explain Rogelberg's subject. A meeting can supply the manager with information while failing the person it is meant to support.
The book concentrates on the recurring conversation between a manager and a direct report. Its published contents move from setup and agendas to conducting the conversation, follow-through, evaluation, and special cases such as skip-level meetings. That gives it a narrower and more usable focus than a general book about running team meetings. The bibliographic details and chapter sequence are available in the Oxford University Press record.
Who Should Read It
- New managers who have inherited a calendar full of 1:1s without being taught what these meetings should accomplish.
- Experienced managers whose direct reports answer every check-in with a polite statement that everything is fine.
- Employees who want to bring a clearer question or request to an existing meeting with their manager.
- Remote team leaders who need private space for discussing access to information, coordination problems, and development.
Choose a different starting point if you need a formal investigation, a performance-management policy, or specialist support for a serious workplace complaint. A better 1:1 can help surface a problem; it does not replace the process needed to resolve it. Readers seeking facilitation for a whole group will also need a different meeting design.
Main Summary
Rogelberg treats the manager's one-to-one as a regular opportunity to understand and support a particular employee. The issue is not simply whether the meeting exists. Its purpose, preparation, conversational balance, and follow-through determine what kind of experience it becomes. A recurring slot used only to inspect tasks can preserve the appearance of attention while leaving important concerns untouched.
Two distinctions organize a useful reading. First, the direct report should actively shape the agenda rather than merely answer a manager's questions. The book discusses a listing approach and a core-question approach. Second, the meeting should address both practical needs and personal needs. Work may need a decision or an obstacle removed; the person also needs to be heard and treated with respect. These are connected aims, not competing halves of a rigid timetable. The publisher's chapter on agenda creation and chapter on the general model explain these distinctions.
The book is therefore as much about managerial listening as meeting logistics. A manager can ask an open question and still take over by interrupting, supplying an answer too early, or treating disagreement as disloyalty. Conversely, a warm conversation can feel pleasant while leaving an important decision unresolved. Useful attention needs both understanding and action.
The interpretation offered here is to examine one recurring meeting as a continuing relationship: what the employee can introduce, how a concern is explored, what help is agreed, and what happens before the next conversation. The five practices below are this guide's editorial selection, not a new five-step framework attributed to Rogelberg. Our worked example follows a service coordinator who cannot get a handoff problem addressed. It illustrates choices a reader could test, not an event or measured result reported in the book. The test is whether the employee gets clearer support and a credible response, rather than whether the manager completes a template.
Key Ideas
1. Give the employee real influence over the agenda
Rogelberg's agenda chapter describes two approaches: both people can list topics, or they can agree on core questions that open useful areas of discussion. In either case, the direct report's contribution matters. An agenda made entirely by the manager can turn even a friendly meeting into an oral reporting requirement. An agenda should help a concern enter the conversation before the available time disappears.
In our service-team example, coordinator Mira adds an item about late handoffs from another department. Her manager adds staffing and next month's rota. At the start, they compare urgency. Mira explains that the handoff issue is already causing customer callbacks, so they choose it first. This is more meaningful influence than inviting additions after the manager has used twenty-eight of thirty minutes.
A practical adaptation is to keep a short shared list that both people can edit. It can contain a decision needed, an obstacle, or a longer-term development question. There is no requirement to complete every item in order. If something new becomes urgent, state which item will move and when it will return.
Do not make preparation another hidden burden. An employee working shifts may need paid time or an accessible way to add an item. Also preserve a route for concerns that should not sit in shared notes. The point is access to the conversation, not compliance with a document. Revisit the format if it consistently privileges the person with more writing time or organizational confidence.
2. Address practical and personal needs in the same exchange
The book's general model distinguishes practical needs from personal needs. One concerns progress on work; the other concerns how the person is treated and understood. The publisher's personal-needs chapter identifies behaviors including empathy, transparency, involvement, kindness, and appropriate vulnerability. These should inform the interaction rather than become a checklist of emotions the employee must display.
Mira needs her manager to negotiate a handoff deadline. She also wants the manager to recognize that repeatedly apologizing to customers for another team's delays is wearing her down. An answer that supplies a new spreadsheet without acknowledging her account misses part of the problem. Sympathy without a decision about the handoff misses another part.
The manager can first reflect the issue accurately: Mira is absorbing uncertainty at the customer-facing end, not simply asking to avoid coordination work. They can then distinguish what the manager can decide, what another department must negotiate, and what temporary support is available. Mira should be able to correct that description before the manager acts on it.
This does not require personal disclosure unrelated to work. Someone can decline to discuss home life and still receive considerate management. Nor does a respectful conversation mean every request will be granted. A clear explanation of a constraint, an honest account of authority, and a date for a response may be more supportive than vague reassurance. The two needs meet when the person has both usable information and evidence that their account affected the discussion.
3. Facilitate understanding before supplying the answer
Rogelberg's model emphasizes the manager's role as a facilitator rather than a dominating speaker. That matters because experience can make a manager quick to recognize a familiar problem and slow to discover what is different this time. Letting the employee speak means more than reducing the manager's word count. It means allowing information to change the manager's understanding.
Suppose Mira says that the handoff system is broken. Her manager remembers a previous software problem and starts offering technical fixes. A better move is to ask for a recent example. Mira describes a case in which the information was available, but nobody knew who could approve a late change. The bottleneck concerns authority, not missing software. A premature answer would have added work without addressing the obstacle.
Readers can practice a short sequence of their own: invite a specific incident, check what the person tried, and ask what kind of help would now be useful. This is an application exercise, not a named sequence from the book. The manager may eventually need to instruct, decide, or give feedback; exploration helps make that response relevant.
Avoid treating silence as agreement or forcing the employee to solve a problem outside their remit. A direct report may need time to think, use written notes, or say that they do not know. Equally, a manager should not hide a necessary decision behind endless coaching questions. Explain when the conversation is moving from understanding to a managerial decision, and leave room to correct mistaken assumptions.
4. Make support visible between meetings
The book includes a dedicated section on what happens after a 1:1, and its general model includes note-taking by both parties. The communication lesson is continuity. If a manager listens carefully and then forgets a promise, the next invitation to speak carries less weight. Notes help only when they preserve an accurate commitment rather than create a detailed record nobody uses.
In Mira's case, a useful ending distinguishes two commitments. She will bring one anonymized example of a late approval; the manager will speak with the other department's lead by Thursday. They also agree how Mira will hear back if that conversation does not happen. The following meeting can begin with an update instead of requiring Mira to retell the entire history.
That example is this guide's proposed practice. It deliberately records what the manager owes as well as what the employee owes. Otherwise, an apparently shared action list can become a one-sided assignment sheet. A commitment should identify an owner, an observable next step, and a reasonable time for a response. If the answer depends on someone else, record that dependence rather than promise an outcome.
Keep the record proportionate. Agree what belongs in shared notes, where it is stored, and who can access it. Sensitive personal details do not need to be copied into a routine task list. When priorities change, acknowledge the change and renegotiate the commitment. Quietly dropping it leaves the employee guessing whether the concern was forgotten, rejected, or considered unimportant.
5. Ask whether the meeting is useful to the person receiving it
The book ends its main meeting cycle with evaluation, including a chapter asking whether the 1:1 worked. A manager's positive impression is insufficient evidence. The person who controls the agenda and can authorize action may feel productive even when the other participant leaves with the original uncertainty. Evaluation should therefore invite a specific account of value and allow the answer to change the meeting.
After several conversations, Mira's manager could ask which part of the 1:1 helped and which subject keeps getting crowded out. Mira might say that urgent handoffs receive attention but career questions never reach the top of the list. The next adjustment could protect time for that question in an agreed future meeting. It would be premature to conclude that every meeting needs a longer duration.
In his published interview about one-to-ones, Rogelberg discusses employee-shaped agendas and the responsibilities of both participants. Our application is to ask for feedback about the process in language the employee can safely answer: what should we keep, and what should we change? Do not demand praise in response to an abstract question about whether you are a good manager.
Power remains relevant. An employee may fear that criticizing a meeting will affect their prospects. Explain how suggestions will be handled, thank them without argument, and demonstrate a modest change. Where appropriate, an organization may need a separate confidential feedback channel. The conversation becomes more credible through repeated responses, not a single invitation to be candid.
Practical Takeaways
- Explain what the recurring 1:1 is for before changing its format.
- Ask the direct report to add a topic early enough for it to affect the agenda.
- Choose between a short topic list and a few agreed core questions; test which is easier for that person to use.
- When a concern sounds familiar, ask for a recent example before giving the familiar answer.
- Check both the work obstacle and whether your response accurately reflects the employee's account.
- Record the manager's commitments alongside the employee's, with a time for a response.
- Ask what the meeting helped with and change one element in response to useful feedback.
- Keep urgent escalation routes open between scheduled meetings; the calendar must not become a reason to delay help.
How To Apply It
For one existing manager–employee pair, test a small reset over several meetings. First explain the intention: the slot should help the employee discuss work, obstacles, and development. Ask what the current format makes easy or difficult. Agree how to add topics and what should stay out of shared notes.
Before the next meeting, each person adds a short list. At the opening, identify which item matters most today. During that item, check the actual incident and the help requested. At the end, read back the important commitments and invite correction. Before the following meeting, send the promised update, including an honest explanation if progress stalled.
Then assess the reset together. Has an issue become easier to raise? Is support more specific? Is there still a topic that never gets airtime? These observations are a practical learning record, not a validated score or proof that the book caused a performance improvement. Adapt the cadence and format to real constraints while preserving dependable access.
Best Related Books
- The Coaching Habit is a better next choice for practicing brief coaching questions. Glad We Met offers the wider recurring-meeting setting in which those questions may be used.
- Humble Inquiry examines the stance of asking and learning across status differences. Read it when your questions sound open but your responses still discourage correction.
- The Fearless Organization broadens attention to the conditions for speaking up across a workplace. A well-run 1:1 cannot by itself repair organizational retaliation or silence.