Why this matters

This guide is full of practices, but practices do not change anything by themselves. What changes a team is people agreeing, in a room or on a call, that something should be different and deciding what to do. The quality of those conversations varies enormously. Some teams talk about the same complaints every week and leave with nothing. Others spend an hour on a well-chosen question and leave with a plan.

The difference is rarely talent. It is usually structure: a clear purpose, a way to hear from everyone, a question worth asking, and a decision at the end. This topic describes a small set of formats that provide this structure, and then collects questions from across the guide so that a facilitator can find a good one quickly. It is designed as a source of ideas to talk about with teams, which was one of the aims of the whole guide.

The sources for the formats are modest. The Wikipedia article on facilitators describes the role in general terms; the Lean Coffee website describes one format in detail; and the Scrum Guide describes the Sprint Retrospective (see Topic 1.4 — Delivery Forecasting and Planning Metrics). The Wikipedia article on retrospectives treats agile retrospectives only briefly. Much of the rest of this topic is practical advice drawn from the skills in this guide and from common facilitation practice, which the text flags as such.

Core concepts

What a facilitator does

The Wikipedia article describes a facilitator as someone who helps a group work together better, understand their common objectives, and plan how to achieve them, staying neutral and taking no position in the discussion. Basic skills include timekeeping, following an agenda, and keeping records; higher-order skills involve understanding group dynamics, and listening skills include paraphrasing, drawing people out, and balancing participation. The article describes facilitators of various kinds, in business, education, training, conflict resolution, and small groups, and names professional bodies, the International Association of Facilitators (founded 1994) and the International Institute for Facilitation (founded 2003), each with its own certification. You do not need a certificate to facilitate a team conversation. You need to be fair, keep time, and care about the outcome.

The facilitator can be a team member who takes the role for one meeting, a coach, or an outsider. Rotating the role spreads the skill. If you are the person with the most authority in the room, consider asking someone else to facilitate, so that people speak more freely.

Choosing a format

Format Use it to… Typical length Detail in
Lean coffee Discuss whatever the group most wants to talk about, without a pre-set agenda 45–60 minutes This topic
Liftoff Align a new team or project on vision, objectives, stakeholders, and an initial plan Half a day or more The agile liftoff skill
Chartering and working agreements Agree how the team will work together 60–90 minutes The agile charter skill
Retrospective Look back at a recent period, and choose changes 45–90 minutes Topic 3.15 — Continual Improvement and the agile reflection skill
Futurespective Imagine possible futures and prepare 60–90 minutes The futurespective skill
Showcase or review Show working results to stakeholders and gather feedback 25–60 minutes The agile showcase skill
Stand-up Share the day's plan briefly 15 minutes The agile standup skill
Incident or postmortem review Learn from a specific event 45–60 minutes Topic 3.2 — Incident Management

The lengths are common practice and offered as such. Adjust to your group.

Lean coffee

The Lean Coffee website describes it as "a structured, but agenda-less meeting," in which participants build an agenda and start talking. It began in Seattle in 2009, started by Jim Benson and Jeremy Lightsmith, who wanted a group to discuss lean techniques in knowledge work without a formal organization. According to the site, a session works like this:

  1. Set up a simple board with three columns: Ready (to discuss), Doing, and Done.
  2. Build the agenda. Each person writes topics on sticky notes and places them in the Ready column, then briefly introduces their topics.
  3. Vote. Each person gets two votes, placed as dots on the notes. The topics are ranked by votes, and the group discusses them from the top.

The site describes the format as using the least structure necessary, and it does not specify timeboxes or formal rules; many groups add short timeboxes, with a quick vote to extend. The site says that Lean Coffee is a trademark of Modus Cooperandi, so use the name accurately and credit the source. Lean coffee works well for service teams because the agenda comes from the people doing the work, so pressing issues surface fast.

Retrospectives

The Wikipedia article on retrospectives describes a retrospective as a project team meeting held at the end of a project or process, often after a period of continuous software delivery, in which the team discusses what went well, what could be improved, and how to apply the lessons. The Scrum Guide's Sprint Retrospective is when the team inspects how it worked, including people, processes, tools, and its definition of done, and plans improvements; the guide gives three hours as the limit for a one-month Sprint. The article gives no agenda, so for structure, see the agile reflection skill and the section on continual improvement. Whatever the structure, the test is that each retrospective ends with a small number of owned actions that are checked next time.

Liftoffs, charters, and working agreements

At the start of a team or project, the team benefits from agreeing on why it exists, what it is trying to achieve, who its stakeholders are, and how it will work. The agile liftoff skill describes this as the initial stage of an agile project in which the team defines and aligns on goals, objectives, and an initial plan. The agile charter skill describes collaboratively defining a project's vision, objectives, and working agreement with a diverse stakeholder group. A working agreement is a short set of rules the team writes for itself, such as how quickly to answer messages, how to handle disagreements, and what counts as done. Keep it short, write it together, post it, and revisit it.

Futurespectives

A futurespective, as the skill in this guide describes it, is a forward-looking group exercise, imagining possible future scenarios to inform current decisions, as a counterpart to a retrospective. For a service team it might ask how demand, technology, or regulation could change in two years and what the team should do now. It draws on scenario planning and SWOT analysis.

Conversation design

Whatever the format, a good conversation has:

  • A purpose stated in a sentence at the start.
  • A question worth asking, specific and open, answerable from the team's own experience.
  • A way to hear from everyone, such as writing silently before talking, or going round the room.
  • Facts before opinions, such as recent events or data.
  • A decision or action at the end, with an owner and a date.
  • A safe atmosphere, in which people can describe mistakes and disagree without penalty (see Topic 3.2 — Incident Management on blameless review).

Remote and mixed groups

Online sessions need more structure, not less: a shared board, explicit turn taking, shorter segments, and a clear signal for dissent. Mixed groups, with some people in a room and some remote, tend to favor those in the room, so have every participant join from their own device, or give remote participants first turn.

Limits

The formats here are widely used, but the sources read for this guide provide no evidence on their effectiveness. The Lean Coffee site describes the method without outcome data, and the Wikipedia article on facilitators names no criticisms. Treat each as an experiment, and judge it by whether the team ends with decisions it follows through.

A curated list of conversation starters

The questions below come from across the guide. Each is a good way to open a team conversation, and each topic gives briefings for facilitators. They are grouped by purpose.

To open a new team or a new year

  • Which of the four values does our team already favor in practice, and which do we only claim to favor? (Topic 1.1 — Agile Manifesto)
  • Which of the twelve principles do we follow best, and which do we follow least? (Topic 1.2 — Agile Principles)
  • What services do we provide, in the words our users would use? (Topic 2.1 — IT Service Management)
  • Who is accountable for each of our services, and would they say so? (Topic 5.5 — Product and Service Ownership)

To improve how we work

  • What is the oldest item on our board, and why is it still there? (Topic 1.5 — Kanban)
  • What did our last retrospective change, and how do we know it worked? (Topic 1.4 — Delivery Forecasting and Planning Metrics)
  • What got better in the last quarter because of something we decided to change? (Topic 3.15 — Continual Improvement)
  • What are we doing that we could stop doing without harming a customer? (Topic 1.2 — Agile Principles)

To improve how we run services

  • What do we do in the first ten minutes of an incident, and who decides? (Topic 3.2 — Incident Management)
  • Which incident keeps coming back, and what do we think causes it? (Topic 3.3 — Problem Management)
  • What does our approval step actually catch? (Topic 3.4 — Change Enablement)
  • Which alerts do we ignore, and why? (Topic 3.10 — Monitoring and Event Management)
  • What would we be unable to do if one named person were away for a month? (Topic 3.9 — Knowledge Management)

To talk about customers

  • What does a user experience when they contact us, from the first moment to the answer? (Topic 3.1 — Service Desk)
  • What does a good day look like for our users, and how would we know? (Topic 3.7 — Service Level Management)
  • If we followed one request from the first contact to the customer's receipt, how long would it take, and how much of that is working time? (Topic 5.4 — Value Stream Management)

To talk about risk, money, and rules

  • Which of our services must come back first, and how do we know? (Topic 3.12 — Service Continuity Management)
  • What do we pay for that nobody uses? (Topic 4.1 — IT Asset Management)
  • What does the next nine cost us? (Topic 3.11 — Availability, Capacity, and Performance)
  • Which rules apply to us, and where is the text? (Topic 5.7 — Governance, Risk, and Compliance)

To talk about change and learning

  • What problem are we trying to solve with this change, and who feels it? (Topic 5.8 — Organizational Change and Adoption)
  • What did each of us learn last quarter, and how did we learn it? (Topic 1.10 — Agile Learning)
  • What happens to our behavior when a number is a target? (Topic 5.6 — Metrics and Measurement)

Best practices

  1. State the purpose of every conversation. Write a one-sentence purpose, share it in advance, and repeat it at the start. A meeting without a purpose rarely produces one.
  2. Pick the format to fit the purpose. Use lean coffee when you do not know what to talk about, a retrospective to learn from the last period, a liftoff at the start, a futurespective to look ahead.
  3. Prepare one good question. Choose an open question that the team can answer from its experience. The questions in this guide are written to be used this way.
  4. Rotate the facilitator. Let different team members run sessions. It builds skill and prevents the loudest voice from setting the agenda.
  5. Keep time. Agree timeboxes at the start, show the clock, and extend by a vote. Meetings that run over lose the people who are quiet.
  6. Hear from everyone. Use silent writing, round-robin, or small groups so that each person contributes before open discussion.
  7. Use facts first. Begin with data or a recent event, and then discuss meaning. This keeps conversations out of general complaint.
  8. End with actions. Choose at most two or three actions, give each an owner and a date, and write them where the team will see them.
  9. Follow up. Start the next session by checking last time's actions. A team that skips this learns that actions do not matter.
  10. Protect safety. Agree ground rules that make it safe to speak, such as discussing events and not blaming people. Step in when they are broken.
  11. Vary the setting. Change place, format, and participants now and then, including customers and people from neighboring teams, when appropriate.
  12. Review the conversations themselves. Once a quarter, ask which sessions led to change and which did not, and adjust.

Questions to discuss with your team

Which meetings do we hold that lead to a decision, and which do not?

Ask each person to list the regular meetings they attend and mark each as producing decisions, information, or neither. Compare. Meetings that produce neither are candidates for change or removal. The facilitator can ask what the purpose of each was meant to be. Pick one to redesign.

What do we keep talking about without resolving?

Collect the topics that return in every retrospective or stand-up. Ask what stops resolution: no owner, no authority, no information, or fear. Choose one topic and design a conversation for it with a specific question and an action at the end.

Who speaks most and least in our meetings, and what would change that?

Observe over a few sessions, or ask people to reflect. Do not name individuals in the group discussion. Discuss formats that balance participation, such as silent writing first. Try one in the next meeting.

What is our working agreement, and when did we last look at it?

Ask whether the team has written one. If so, read it aloud and ask whether it describes how the team works. If not, draft three rules together. Agree a date to review it.

What would we like to know about our customers' experience that we do not ask?

Brainstorm questions for users, then consider inviting a user or a support colleague to the next review. The aim is to bring outside voices in. Choose one question and a way to ask.

What future change are we least prepared for?

Invite the team to imagine one big change in two years: a new regulation, a supplier collapse, a technology shift. Ask what the team would regret not having done. This is the seed of a futurespective.

In practice: an agile ITIL example

A regional ambulance service's IT department has a team of eleven that runs the dispatch system. Its fortnightly retrospective has become a ritual: the same complaints are raised, nobody expects action, and attendance has fallen to six. The team lead asks a colleague from another department to help redesign the conversations.

The coach suggests three changes. The first is to replace the retrospective, for one cycle, with a lean coffee: everyone writes topics, votes with two dots, and the group discusses the top ones for eight minutes each. The second is to start each session with facts. The coach prepares a one-page summary of the fortnight's incidents and deployments. The third is to end with at most two actions, each with a name and a date, and to open the next session by reviewing them. In the first session, the topic that rises to the top is the handover between day and night shifts, which nobody had put on a formal agenda.

Over two months, attendance returns to ten, the team agrees a working agreement about handover notes, and three actions are completed. A futurespective on the dispatch system's likely demands in two years leads the team to ask the ambulance service's operations manager about planned changes to call handling. Some issues remain. One senior engineer still dominates discussion, two actions were dropped when a major incident intervened, and the night staff, who work different hours, cannot attend. The lead asks the senior engineer to facilitate a session so that he practices listening, makes a rule that dropped actions must be explicitly postponed or canceled, and arranges a short night-shift session run by the night staff.

Four perspectives

Product and delivery teams

Delivery teams already hold many ceremonies. Review which lead to change, add lean coffee or a futurespective for variety, and invite operations and support colleagues to join. Use questions from the guide to turn complaints into plans.

Service and operations teams

Operations teams hold incident reviews, shift handovers, and planning. Give them structure: facts first, a question, and actions at the end. Ask delivery and customer colleagues to join some sessions, and run sessions for night and day shifts that include both.

Leadership and governance

Leaders shape the conditions for honest conversation: time to meet, safety to speak, and follow-through on what the team asks for. Attend occasionally, listen more than you speak, and act on the actions that need you. Avoid dominating sessions.

Customers and users

Customers and users can enrich team conversations. If invited to a review or a futurespective, describe your needs concretely, and respond to what you see. Tell the team what conversations they could have that would help you.

Common failure modes

  • No purpose. The meeting meanders. Instead, state a one-sentence purpose in advance.
  • The same people talk. Quieter members stay silent. Instead, use silent writing, round-robin, or small groups.
  • Complaint without facts. The session circles old grievances. Instead, begin with data or a recent event.
  • No actions. Talk ends with nothing to do. Instead, choose two or three actions with owners and dates.
  • No follow-up. Last time's actions are never checked. Instead, open each session by reviewing them.
  • Unsafe atmosphere. People fear blame and say little. Instead, set and enforce ground rules.
  • Format as ritual. The structure is kept and the point is lost. Instead, review which sessions lead to change and adapt them.
  • Boss as facilitator. The most senior person runs the room. Instead, rotate the role or ask someone neutral.

Maturity model

Dimension Initiate Develop Standardize Manage Orchestrate
Purpose and format Meetings have no stated purpose Some meetings have an agenda Each recurring conversation has a purpose and a chosen format The usefulness of conversations is reviewed Conversations are designed jointly with other teams and customers
Participation and safety A few people dominate Some techniques for broader participation Techniques for hearing everyone and ground rules are routine Participation and safety are checked and improved Participation spans teams, suppliers, and customers
Decisions and follow-through Talk rarely leads to action Some actions are recorded Actions have owners and dates and are reviewed next time Action completion is tracked and effects checked Actions are coordinated across teams and linked to the improvement list
Facilitation skill One person facilitates A few people can facilitate Facilitation rotates and people are coached Facilitation quality is reviewed with feedback A community of facilitators supports teams across the organization

Checklist

  • Each recurring meeting has a one-sentence purpose.
  • We choose the format to fit the purpose.
  • Each session has one good question prepared.
  • The facilitator role rotates.
  • Everyone has a way to contribute before open discussion.
  • Sessions start with facts, not only opinions.
  • Each session ends with at most three actions with owners and dates.
  • The next session starts by reviewing the previous actions.
  • The team has a short, written working agreement that it reviews.
  • We review once a quarter which conversations led to change.

AI prompts

Purpose: design a conversation around one question.

Help me design a 45-minute team conversation about this question: [paste a question, for example from the guide].

Team: [number of people, roles, remote or in person].
Why the question matters now: [one or two sentences with recent facts].
What happened last time the team discussed it: [describe, or write "never"].

Give a timed plan: a one-sentence purpose, how to open with facts (list the facts I should bring, using only what I described), a way for everyone to contribute before open discussion, two or three follow-up prompts, and a closing step that records at most two actions with owners and dates. Keep it free of any particular tool. Ask clarifying questions first, mark assumptions, and list what you are unsure of.

Purpose: plan a lean coffee session.

Plan a lean coffee session for [number] people in [in-person or remote].

Context: [describe what the team is dealing with right now].
Time available: [minutes].

Give: how to set up the board with Ready, Doing, and Done columns; how to collect and introduce topics; how voting works (two votes each); suggested timeboxes with a quick vote to extend; how to capture actions; and how to close. Add three prompts the facilitator can use to seed topics if the group is quiet. Credit lean coffee to its originators and note that the name is a trademark. Ask clarifying questions first if information is missing, and list what you are unsure of.

Purpose: draft a working agreement for a team.

Help us write a working agreement.

About the team: [roles, size, locations, hours].
Frictions we have noticed (facts only): [list].
Rules or commitments we must respect (on-call, security, contracts): [list, or write "none known"].

Propose a one-page draft with eight to twelve short statements under the headings: communication, meetings, decisions, handovers, learning from mistakes, and wellbeing. Mark which statements respond to the frictions I listed. Suggest how the team can review the agreement in three months. Do not invent facts about our team. Ask clarifying questions first, and list what you are unsure of.

Purpose: prepare a futurespective.

Plan a 75-minute futurespective for a team of [number] who run [service].

Time horizon: [for example two years].
Forces we already know about (technology, regulation, customer needs, suppliers; list only what you actually know): [paste].
Decisions the team may face in the next year: [list].

Provide a timed plan: set the scene, generate possible futures (without inventing facts about our environment), look at what each future would mean for the service, choose actions that help in several futures, and record them with owners. Include questions for the facilitator. Ask clarifying questions first, mark assumptions, and list what you are unsure of.

AI skills

  • agile-reflection: use to run a retrospective that ends in a real change.
  • futurespective: use to look ahead together and prepare for possible futures.
  • agile-liftoff: use to launch a new team or project with shared vision and plan.
  • agile-charter: use to agree a team's purpose and working agreement.
  • brainstorming: use to generate many ideas quickly before choosing among them.

Key sources

  • Lean Coffee (leancoffee.org): the originators' description of the agenda-less meeting format.
  • Facilitator (Wikipedia): an overview of the facilitator's role, skills, and types.
  • The Scrum Guide (Ken Schwaber and Jeff Sutherland, scrumguides.org): the Sprint Retrospective and other events.
  • Retrospective (Wikipedia): a brief note on retrospectives in software development within a general article.

References

  1. Lean Coffee — Jim Benson and Jeremy Lightsmith, leancoffee.org — https://leancoffee.org/
  2. Facilitator — Wikipedia — https://en.wikipedia.org/wiki/Facilitator
  3. Retrospective — Wikipedia — https://en.wikipedia.org/wiki/Retrospective
  4. The Scrum Guide (November 2020) — Ken Schwaber and Jeff Sutherland, scrumguides.org — https://scrumguides.org/scrum-guide.html
  5. Scrum (software development) — Wikipedia — https://en.wikipedia.org/wiki/Scrum_(software_development)
  6. Brainstorming — Wikipedia — https://en.wikipedia.org/wiki/Brainstorming
  7. Scenario planning — Wikipedia — https://en.wikipedia.org/wiki/Scenario_planning
  8. SWOT analysis — Wikipedia — https://en.wikipedia.org/wiki/SWOT_analysis
  9. Agile software development — Wikipedia — https://en.wikipedia.org/wiki/Agile_software_development