Team Conversations
A team conversation is a short, structured discussion that turns one topic's questions into a shared view and a few owned actions; it works when the purpose is stated, facts come before opinions, everyone is heard, and the meeting ends with at most two actions that have names and dates.
Why this matters
Reading changes little. A team can read every topic in this guide and carry on exactly as before. What changes practice is a conversation in which people who share a service compare what they believe, notice where they disagree, and decide what to try next. The questions at the end of each topic are written for that purpose.
Conversations also go wrong in familiar ways. One or two people talk and the rest watch. A manager states the answer and asks if there are questions. A discussion of "our change process" turns into a complaint session. The meeting ends with a warm sense of agreement and no actions, or with eight actions and no owners. After a few such meetings, people stop attending, and "discussion" becomes a word for waste.
A short structure fixes most of this. It does not need training or a special room. This topic describes how to run a conversation using the questions in this guide: how to choose a topic and a question, how to prepare, how to open, how to draw out people who are quiet, how to handle disagreement and sensitive subjects, how to end with actions, and how to follow up. It also offers formats for different purposes and conversation starters across the guide. It draws on well-known facilitation methods, and none is required. The guide's skill for readers, service-management-guide-skill, can help to choose topics and plan sessions. This topic connects to learning paths (Topic 8.5 — Learning Paths and Certification), organizational change (Topic 8.3 — Organizational Change and Adoption), and agile management and learning (Topic 2.10 — Agile Management and Learning).
Core concepts
The unit of work. One topic, one or two questions, 45 to 60 minutes, 4 to 12 people. Longer sessions blur. Larger groups split into pairs or threes, then report.
Facilitation. Helping a group to work together effectively without telling it what to conclude. Wikipedia describes facilitation as the process of making group work easier, in which the facilitator stays neutral on content. A facilitator can be anyone on the team, and the role can rotate. In a session they manage the time, the process, and the airtime, and they do not argue a position.
Facilitator's briefing. Each question in each topic has a short briefing of three to six sentences: why the question matters, what answers you may hear, and a follow-up. It is the facilitator's notes, not a script. Read it before the session, and keep it to hand.
Purpose and outcome. Say in one sentence why the group is meeting and what you expect at the end, for example "to agree two changes to how we handle emergency changes". A vague purpose produces vague results.
Facts before opinions. Start by collecting what happened or what is, from the group's own experience, before judging. "Tell me about the last emergency change" before "is our process good?". Facts anchor the discussion and reduce arguments from general impressions.
Everyone heard. In most groups, a few people speak most of the time. Methods that give each person a turn, such as writing ideas silently before sharing (Wikipedia describes the nominal group technique and brainwriting) or discussing in pairs first, bring out more views. Wikipedia describes group dynamics and groupthink, in which a group suppresses doubts to preserve harmony. Notice who has not spoken.
Psychological safety. People speak honestly when they believe they will not be punished or mocked for it. Wikipedia describes psychological safety. Set it up: say that all views are welcome, that disagreement is useful, that nothing said will be used against a person, and that the aim is to improve the system, not to blame people. Then behave that way. See Topic 2.10 — Agile Management and Learning.
Active listening. Giving full attention, reflecting what you heard, and asking open questions. Wikipedia describes active listening. Simple phrases such as "what I hear is…" and "tell me more about…" show that you are listening and clarify meaning.
Open questions and follow-up. Open questions begin with "what", "how", or "tell me about" and invite description; closed questions invite yes or no. Each question in this guide has a suggested follow-up, which moves from discussion to action. Wikipedia describes questioning as a skill.
Handling disagreement. Disagreement is useful when it is about ideas and evidence. Name it ("we see this differently"), ask each side to state the other's view fairly, and look for the facts or experiments that could settle it. Not every difference must be resolved; sometimes the action is to find out.
Dominant and quiet voices. Thank dominant contributors and invite others: "Let's hear from people who haven't spoken." Speak with quiet people outside the session to learn what they think. Be aware of rank: junior people may hold back when senior people speak first, so ask juniors first.
Sensitive topics. Some questions touch on jobs, performance, mistakes, or conflict. Agree ground rules at the start, avoid naming individuals in examples, and offer a way to contribute anonymously, for example by writing on cards. Do not use these conversations to gather evidence against people. See Topic 8.3 — Organizational Change and Adoption.
Timeboxing. Giving each part of the session a fixed time. Wikipedia describes timeboxing. It keeps the discussion moving and ensures there is time for actions. Announce the plan at the start and watch the clock.
Decisions and actions. A conversation without a decision or an action is usually a lost opportunity. Wikipedia describes decision-making and action items. Agree at most two actions. Each has an owner, a date, and a sign that it is done. If the group cannot choose, agree who will decide and by when.
Recording. Capture the main points and actions where everyone can see, on a whiteboard, a shared document, or sticky notes. Send a short summary the same day. Wikipedia describes minutes; keep yours short.
Follow-up. Begin the next session by reviewing the last actions. If actions are not reviewed, people stop doing them. Close the loop with anyone affected who was not in the room.
Formats for different purposes. Several formats suit different aims:
| Purpose | Format | Outline |
|---|---|---|
| Understand where we are | Question round | Pick one question; individual writing for three minutes; share in turns; cluster themes; agree one thing to explore |
| Find causes of a problem | Cause discussion | Describe a real case; use five whys or a fishbone diagram (Wikipedia describes both); choose the cause that is cheapest to address |
| Anticipate risks of a plan | Pre-mortem | Imagine the plan has failed; each person writes why; share; choose the top risks and a step for each (Wikipedia describes pre-mortems) |
| Choose among options | Dot vote | List options; each person gets a few dots to place; discuss the top two; decide |
| Learn from an event | Review | What happened, what helped, what hindered, what we will change, using the topic's questions |
| Explore a topic with a wide group | Open space | People propose and join topics of interest (Wikipedia describes open space technology) |
Remote and hybrid sessions. Use a shared document or whiteboard, give people time to type, use breakout rooms for pairs, and invite remote people first. Keep cameras optional if bandwidth or comfort is an issue.
Cadence. A regular slot, such as 45 minutes every two weeks, builds the habit and gives continuity. Choose topics that connect to current work, and rotate who facilitates.
Using AI as a helper. AI can help to plan a session, turn answers into themes, and draft a summary, under the facilitator's control. Do not paste confidential or sensitive discussions into tools without approval, and keep the human judgement and the relationships in the room. See Topic 5.7 — AI Skills and Prompts.
How the lenses fit. Conversations are the practice of continuous improvement at team level. Agile practice treats them as short feedback loops. AI, automation, and analytics each have questions in every topic, and the conversation is where a team decides what to do about them.
Best practices
- Choose a topic that matters now. Pick one linked to a current problem or a coming decision. A topic with no connection to the team's work gets polite attention and no action.
- Pick one or two questions. Read the questions and the briefings, and choose those the team can answer from its own experience. Leave the rest.
- Prepare a one-sentence purpose and a plan. Write what you want at the end and a time plan, for example 5 minutes opening, 25 minutes discussion, 10 minutes choosing actions, 5 minutes close.
- Open with ground rules. Say what the session is for, that all views are welcome, that no one will be blamed, and that the aim is at most two actions. Invite additions.
- Ask for facts first. Start with a recent real case or data. Ask "what happened?" before "what do you think?".
- Hear from everyone. Use silent writing, pairs, or round-robin. Ask people who have not spoken, and ask junior people before senior ones.
- Use the briefing and the follow-up. Use the facilitator's notes to stay oriented, and use the suggested follow-up to move from talk to action.
- Handle disagreement openly. Name it, ask each side to restate the other's view, and look for facts or a small experiment that would decide it.
- End with at most two actions. Each has an owner, a date, and a sign of done. Read them back, and note what the group decided not to do.
- Follow up. Send a short summary the same day, start the next session with the actions, and tell people affected what happened.
Questions to discuss with your team
What is the last conversation we had about our work that led to a change, and what made it work? Collect examples. Expect that the good ones were short, about a real case, and ended with an owner. Follow up by agreeing one habit to repeat.
Who tends to speak in our meetings, and who does not? Ask for honest observation. Expect names. Follow up by trying one technique, such as silent writing, in the next session.
What have we stopped saying in meetings because it did not seem safe? This needs trust, so use cards. Expect a few honest items. Follow up by choosing one to discuss, and agreeing how it will be handled.
How many actions do we usually leave with, and how many get done? Check the last three meetings. Expect many actions and few done. Follow up by agreeing a limit of two and a review at the start of the next session.
Which topics in this guide should we discuss first, given what is hurting us now? Review the contents and the problems. Expect a mix. Follow up by choosing one topic and one facilitator for the next month.
How could AI help us prepare or follow up, and what must stay in the room? Discuss. Expect interest in summaries and caution about confidentiality. Follow up by agreeing a rule on what may be shared with tools.
In practice: a service management example
A county council's digital services team of fourteen has decided to use this guide, one topic a fortnight. The first session is on change enablement. The team lead, who has facilitated before, asks a senior developer to facilitate this one and rotates the role after.
The facilitator reads the topic's questions and the briefings, and chooses the one about approvals that have never refused a change. She writes the purpose on a flipchart: "to choose one approval we will try removing or replacing, and who will check the result". She plans 45 minutes. In the opening, she reads out the ground rules she has set: all views welcome, no blame, aim for at most two actions. She asks each person to write on a card, for three minutes, one approval in the current process and what risk they think it addresses.
The cards show 11 approvals. The group clusters them and the facilitator asks for facts: how many changes went through the board last month, and how many were refused or altered? The change manager has the numbers: 62 reviewed, two changed. A junior engineer, who had not spoken, says that she assumed the board would catch mistakes, so she is less careful with the details. The facilitator pauses on this and asks the group what they make of it. A discussion follows about whether the approval gives false comfort.
Disagreement emerges: a security analyst argues that one approval of firewall changes is essential, while a developer says the review adds a week. The facilitator names the difference, asks each to state the other's view, and then asks what evidence would settle it. The group agrees to look at the last year's firewall incidents.
They end with two actions: the change manager will test replacing the board approval for standard changes with a peer review and a pipeline check for one month, reporting the numbers at the next session; and the security analyst will list firewall incidents from the last year by the next session. The facilitator writes them on the flipchart, with names and dates, photographs it, and sends the summary the same day.
What changes: the team decides something specific, and the quiet junior engineer's observation changes the discussion. What remains hard: one participant dominated the first ten minutes, and the facilitator was slow to step in; the actions depend on two people with full workloads; and one manager wanted to attend only to hear conclusions. At the next session, the facilitator begins with the actions, and the team agrees to ask senior people to speak last.
Four perspectives
Product and delivery teams
Use conversations to review your own practices, such as how you release or review incidents, with questions from the relevant topic. Rotate facilitators, and bring a real case to each session.
Service and operations teams
Use short, regular sessions for incident reviews, handoffs, and improvement ideas. Protect the time, and keep actions few and owned. Invite people from neighbouring teams when a topic crosses boundaries.
Leadership and governance
Sponsor the habit, join as a participant, and avoid dominating. Ask what the team decided and what it needs. Respond to what you hear, and do not use the sessions to judge individuals.
Customers and users
Invite customers or users to a session on a topic that concerns them, such as service levels or request forms. Listen first, and share what you do with what you learn.
Agile, AI, automation, and analytics
Agile
A conversation is a short feedback loop: look at what is happening, choose one change, try it, and check next time. Keep sessions regular and light. Caution: do not turn the guide's questions into a ritual that replaces real work; stop when a session has become a habit with no effect.
AI
AI can suggest a session plan, group written answers into themes, and draft a summary and action list for the facilitator to check. Name who owns the output. Caution: do not paste sensitive or confidential discussions into unapproved tools, and do not let a summary replace what people actually said. See Topic 5.7 — AI Skills and Prompts.
Automation
Automate scheduling, reminders for actions, and the distribution of summaries, with a person confirming the content. Caution: automated reminders can feel like surveillance when used to chase individuals; use them to support the team. See Topic 6.2 — Workflow Automation and Orchestration.
Analytics
Track simple things: how many sessions were held, how many actions were agreed and done, and what changed. Caution: counting sessions rewards meetings; look at the effect on the work. See Topic 7.3 — Measurement and Reporting and the Service Management Metrics book.
Common failure modes
- A topic with no link to current work. Polite attention, no action. Choose a live problem.
- The leader gives the answer. People stay silent. Ask first, speak last.
- A few voices dominate. Others disengage. Use silent writing and pairs.
- Complaint sessions. Talk without direction. Start with a real case and end with actions.
- Too many actions. None are done. Limit to two, with owners and dates.
- No follow-up. People stop trying. Start each session with the last actions.
- Misuse of what people say. Trust ends. Keep discussions about the system, not individuals.
Maturity model
| Dimension | Initiate | Develop | Standardize | Manage | Orchestrate |
|---|---|---|---|---|---|
| Habit | Occasional | Regular but loose | Regular slot with rotating facilitator | Sessions tied to current problems and results | Conversations connected across teams and partners |
| Facilitation | Leader talks | Some structure | Purpose, plan, and ground rules every time | Facilitation skills shared and improved | Facilitation embedded in how the organization works |
| Safety and voice | Few speak | Awareness | Techniques that hear everyone and handle disagreement | Safety checked with the team | Safety and voice sustained across levels |
| Actions and follow-up | Lost | Some actions noted | Two owned actions per session, reviewed next time | Effects of actions tracked | Actions linked to the improvement backlog and planning |
Checklist
- We chose a topic linked to current work.
- We chose one or two questions and read the briefings.
- We wrote a one-sentence purpose and a time plan.
- We opened with ground rules and psychological safety.
- We asked for facts before opinions.
- Everyone had a chance to contribute.
- We ended with at most two actions with owners and dates.
- We sent a summary and will review the actions next time.
AI prompts
Plan a session.
Topic: [title]. The questions we chose: [paste]. Our team: [size and roles]. Time: [minutes]. Our current issue: [describe].
Draft a session plan with a one-sentence purpose, a time plan with segments, the opening ground rules, how to hear from everyone, two follow-up prompts, and how to end with at most two actions. Keep it to one page.
List what you are unsure of.
Group written answers into themes.
Here are answers written by team members on cards, with names removed: [paste].
Group them into up to six themes, give a count for each, and quote two short answers per theme exactly. List answers that do not fit. Do not interpret motives.
List what you are unsure of.
Draft a summary for review.
Here are my notes from a team conversation: [paste]. The agreed actions: [list with owners and dates].
Draft a summary of under 200 words with what we discussed, what we agreed, the actions with owners and dates, and what we decided not to do. Use only my notes. Mark anything unclear as [check].
List what you are unsure of.
AI skills
- service-management-guide-skill: use to choose topics and run conversations from this guide.
- agile-reflection: use to run a reflection that leads to actions.
- futurespective: use to look ahead as well as back.
- brainstorming: use to generate and sort ideas in a group.
- agile-standup: use to keep short, regular check-ins focused.
Key sources
- Esther Derby and Diana Larsen, Agile Retrospectives (2006): practical formats for team reflection.
- Edgar Schein, Humble Inquiry (2013): on asking questions that open conversation.
- Amy Edmondson, The Fearless Organization (2018): on psychological safety and why it matters.
- Wikipedia, "Facilitation (organisational)" and "Active listening": overviews of the skills.
References
- Facilitation (organisational) — Wikipedia — https://en.wikipedia.org/wiki/Facilitation_(organisational)
- Facilitator — Wikipedia — https://en.wikipedia.org/wiki/Facilitator
- Active listening — Wikipedia — https://en.wikipedia.org/wiki/Active_listening
- Psychological safety — Wikipedia — https://en.wikipedia.org/wiki/Psychological_safety
- Nominal group technique — Wikipedia — https://en.wikipedia.org/wiki/Nominal_group_technique
- Group dynamics — Wikipedia — https://en.wikipedia.org/wiki/Group_dynamics
- Groupthink — Wikipedia — https://en.wikipedia.org/wiki/Groupthink
- Timeboxing — Wikipedia — https://en.wikipedia.org/wiki/Timeboxing
- Pre-mortem — Wikipedia — https://en.wikipedia.org/wiki/Pre-mortem
- Retrospective — Wikipedia — https://en.wikipedia.org/wiki/Retrospective
- Open space technology — Wikipedia — https://en.wikipedia.org/wiki/Open_space_technology
- Ishikawa diagram — Wikipedia — https://en.wikipedia.org/wiki/Ishikawa_diagram