Hybrid Team Retrospective: Questions and Action Plan

To run a hybrid team retrospective, give everyone the same place to contribute, review specific examples of how work went, and leave with a small change, a named owner, and a review date. Use the 45-minute agenda and action-plan template below to examine office days, remote collaboration, and the handoffs between them.

This version is for team leaders, People Ops partners, and workplace operators reviewing an established working pattern. You can use it after a busy delivery period, a change in team membership, or repeated coordination problems. The timings are suggested starting points; extend the discussion or narrow its scope when needed.

What a hybrid team retrospective should produce

A hybrid retrospective can describe a meeting with some people in a room and others joining remotely. It can also review the way a hybrid team works. This guide covers both: an inclusive session whose subject is everyday coordination across locations.

Aim to leave with three things:

• One useful habit to preserve, with a concrete example of why it helped.
• One problem the team can describe without guessing at a colleague's motives.
• One agreed change with an owner, a review date, and a way to tell whether it helped.

Keep the scope within the team's authority. If an issue needs a budget decision or a change to company policy, record who will take it forward and what answer the team needs. A retrospective should not quietly create a new attendance requirement.

The CIPD's hybrid working guidance, published in November 2021, recommends ongoing dialogue and review of working arrangements. Use the retrospective as one place for that conversation, while keeping individual circumstances out of a public group record.

Prepare one shared place for input

Send the review period, purpose, questions, and shared document before the session. State who can read the notes and which decisions this group can make. Atlassian's retrospective play similarly recommends clarifying how information from the discussion will be shared.

Invite people who experienced the work being reviewed, including colleagues who were rarely in the office. Choose a facilitator and someone to capture the agreed actions. In a small team, these can be two lightweight responsibilities rather than dedicated roles.

Ask each person to add an observation in this format:

• Situation: what work was happening, and roughly when?
• Observation: what happened that another person could recognise?
• Effect: what became easier, slower, unclear, or harder to join?
• Question: what do we need to understand before choosing a change?

For example: “The design review started before the remote reviewer joined. We repeated the opening discussion. How should we confirm everyone is ready?” This gives the group something specific to examine.

Avoid prompts that assume the answer, such as asking why people are not coming in enough. Ask which work needed shared time, whether the right people could participate, and what got in the way.

Set up participation across the room and the call

Use a shared document or board that everyone can open and edit. Test access from a remote participant's account before starting. If someone cannot use the chosen tool, agree how they can contribute and check the captured wording with them.

In the room, use a tested microphone and speaker arrangement. If people join the call on individual laptops to access materials, follow the room's audio setup so several live microphones do not create feedback. Keep the discussion on the shared call and write down decisions before it ends.

Use these facilitation rules:

• Start with quiet individual input before discussing themes.
• Invite remote contributions explicitly and allow written responses or a pass.
• Read a selected observation aloud so everyone knows what is being discussed.
• Pause when someone loses access to the conversation or working material.
• If the room connection fails, reconnect individually where practical or continue in writing with a clear response deadline.

For the equipment and connection checks, use the hybrid meeting checklist. Keep this session focused on the work once participation is working.

A 45-minute hybrid retrospective agenda

This suggested agenda totals 45 minutes. It works best with one review period and a small set of issues. Choose only a few of the questions below for any one session.

Minutes 0 to 5: confirm the purpose

Name the period being reviewed and the decision you want to leave with. Remind everyone where the notes will go. Ask whether anyone needs a different way to contribute. Establish that the discussion concerns work practices and observable events.

Minutes 5 to 10: check the previous action

If this is a recurring retrospective, read the previous commitment first. Was the change attempted? What happened? If it never started, identify the obstacle before adding another commitment. For a first session, use this time to name a useful practice to keep.

Minutes 10 to 20: collect and clarify examples

Give people quiet time to write. Then clarify the observations without arguing about solutions. Separate an observed event from an explanation: “We missed the handoff” is different from “Nobody cares about documentation.” Ask what information would help distinguish possible causes.

Minutes 20 to 30: choose one issue

Group related observations and select a problem the team can act on. Consider its effect on the work, who is affected, and whether the next step is within your control. A quick vote can help set the agenda, but check whether a less popular issue prevents someone from participating at all.

Minutes 30 to 40: write the action

Describe the smallest practical change that addresses the selected problem. Name one owner to coordinate it, the people who need to help, and any approval needed. Choose what you will inspect at the review. Atlassian recommends action owners and deadlines; the record below adds the evidence and decision you will revisit.

Minutes 40 to 45: read back the agreement

Read the action aloud and invite corrections from the room and the call. Confirm what stays unchanged, where the record lives, and when the team will review it. Keep unresolved topics in a separate list with an owner for the next step.

Twelve questions about hybrid teamwork

Use these as a question bank, not a questionnaire to complete in full. Ask for a recent example before discussing a general preference.

Office-day purpose and overlap

• Which piece of work moved forward because the right people were together?
• When did we plan to collaborate but miss a person, a room, or a useful time window?
• Which activity filled our shared office time without needing us to be together?

Microsoft Research's suggestions for hybrid work, published in September 2021, recommend coordinating some office days with close collaborators and matching office time to activities that benefit from being together. These questions test your team's experience; they do not establish a universal number of office days.

Information and decisions

• Which decision was easy to find later, and what made the record useful?
• Where did a conversation in the office leave someone elsewhere missing context?
• Which handoff needed extra messages before the next person could begin?

Participation and working conditions

• When could people contribute equally, regardless of location?
• Which meeting, space, or tool made participation or focused work harder?
• What would we need to change so a colleague could contribute without changing their location?

Planning and follow-through

• Which change to an office-day plan reached the affected people in time?
• Which previous action helped, and what evidence supports keeping it?
• What is the smallest change we can review after the next relevant work cycle?

If overlap is the problem, use the office-day planning worksheet after the retrospective. Use the session to identify the coordination need before redesigning everyone's week.

Copy-and-use retrospective action plan

Copy these fields into your shared document. Keep the observation and the proposed explanation separate so you can change your mind when new information appears.

Session record

• Team and review period: [team; dates or work cycle]
• Purpose: [the working practice we are reviewing]
• Facilitator and note owner: [names]
• Contributors and missing perspectives: [who contributed; whose input is still needed]
• Notes visible to: [audience and location]
• Practice to preserve: [habit and a specific helpful example]
• Selected issue: [observable event and its effect]
• Possible explanation: [our current interpretation; what remains uncertain]

Change and review record

• Proposed change: [what we will do differently in a named situation]
• Scope: [people, work, or locations included]
• Owner and collaborators: [who coordinates; who helps]
• Approval or dependency: [needed decision, resource, or none]
• Start and review: [when it begins; when we will discuss the result]
• Evidence to bring back: [work record, examples, or feedback we will inspect]
• Constraint to protect: [something the change must not make harder]
• Decision at review: [keep, adjust, stop, or gather more evidence]
• Agreement to update: [the existing rule or document, if the change is adopted]

When the team adopts a change, update the relevant part of its hybrid team agreement. Keep the retrospective record as the explanation for that change, rather than creating another competing set of rules.

Worked example: a decision made after the call

Consider this fictional example. A team finishes a hybrid planning call, but colleagues in the room continue talking and change a priority. The remote colleague works from the earlier decision and later needs to revise the work.

The first proposal is to require everyone to attend the next office day. The facilitator asks whether the problem was location, access to the decision, or both. The group chooses to test a decision-recording change before altering the schedule.

Its action record reads:

• Observation: the final priority changed after the shared call ended.
• Change: the meeting owner posts the final decision in the shared work record. Any later proposal to change it goes back to the affected group before work continues on the new direction.
• Owner: the planning meeting organiser.
• Review point: after the next two office-day cycles, a suggested test window.
• Evidence: the decision records and feedback from the people acting on them.
• Constraint: the process must let colleagues respond within their agreed working hours.
• Review question: did everyone who needed the decision have the same version before acting?

There is no measured result in this example. It shows how to turn a complaint into a change that can be examined. If the review finds that the relevant people still cannot collaborate, investigate their shared working window next.

Follow up without restarting the whole discussion

At the review, distinguish “we did not try it” from “we tried it and it did not help.” For an unstarted action, resolve the dependency, reduce the scope, or drop it deliberately. For an attempted change, compare what happened with the issue and constraint in the record.

Keep a useful change when the evidence supports it. Adjust it when the benefit came with an avoidable cost. Stop it when it failed to address the problem. If the work cycle did not give you a fair test, record what evidence is missing and set a new review point.

For changes that depend on knowing who plans to be together, Officedays in Slack lets colleagues share their planned office days and see the team's plans. Use that visibility to arrange the work the retrospective identified, then review whether the coordination helped.

Sources and methodology

Sources checked on 21 September 2026. This article combines first-party practical guidance with an Officedays-authored agenda, question bank, and action record. It is an operational template, not an original empirical study or a validated assessment instrument.

• Atlassian, Sprint Retrospectives. Current playbook page; publication date not stated. Supports clear sharing expectations and assigned actions. The 45-minute agenda here is our suggested adaptation.
• Microsoft Research, Suggestions for hybrid work. Published 9 September 2021. Used for coordination and activity-fit guidance, not a current attendance benchmark.
• CIPD for the Flexible Working Taskforce, Hybrid Working: Practical Guidance. The document is dated November 2021 despite its 2024 hosting path. UK-focused practical guidance, explicitly not government guidance; used here for ongoing review, not legal interpretation.

Agenda timings, the number of questions, and the example review window are editorial choices you can adapt. The worked example is fictional and contains no claimed customer outcome.