“We should prepare better” can end a remote retrospective without giving anyone a clear next step. Ask the team what happened, which change it wants to try, and when it will look at the result.
This 25-minute routine helps a small remote team turn one recent work observation into a bounded process experiment. It draws on the Scrum Guide’s description of inspecting how work went and identifying useful improvements. The timings and experiment card below are suggested facilitation choices that teams can adapt to their own working rhythm. The Scrum Guide, Sprint Retrospective
Choose a recent period and gather a few records
Before the call, name the work period you want to discuss. A team might choose the past week’s review meetings or the last completed project stage. Bring a few existing task records, meeting notes, or documents that participants can inspect together.
Keep the scope small enough for a concrete conversation. “How did we prepare for the last three review calls?” gives people a shared set of events to examine. Invite everyone to add a brief note before the discussion, including something that helped the work go smoothly.
Use the first three minutes to confirm the scope and agree to describe events and working conditions. Give people time to correct a note or say that their view of an event differs. The facilitator’s next question should help the group understand what happened.
Separate what happened from a possible explanation
Use five minutes for observations and six minutes to discuss explanations. Put the two kinds of notes in separate parts of the document.
Consider an explicitly fictional example. A remote team reviews notes from three design-review calls. In two calls, someone asked which document was the latest version before the review could begin. These events and counts are invented to illustrate the routine.
The observation is that the question occurred in two of those three calls. “People did not read the invitation” is a possible explanation. So are an outdated link, an unclear document title, and a participant who could not open the intended file. Ask which details the records support and which questions still need answers.

For each proposed explanation, ask someone to point to a record or describe the event they observed. If the team cannot resolve it during the call, keep the uncertainty in the note. You can still choose a useful change to test without agreeing that you have established the cause.
Pick one change the team can actually try
Spend the next five minutes selecting a change within the team’s control. Ask what would make the next similar event easier to start, how much work the change requires, and whether the team can reverse it after the trial.
For the fictional team, one option is to put a clearly labelled link to the current review document in the calendar invitation. The team can test that change over its next three design-review calls. The organizer checks the link with the document owner before each call.
Keep other proposals in the notes for later consideration. If the team changes the invitation, document structure, review checklist, and meeting format together, it will have more difficulty explaining what it wants to keep afterward.
If the group needs a longer discussion to select among options, schedule that discussion with a clear decision to make. Remote team decision sessions
Write the experiment while everyone is still present
Use four minutes to complete a short record in the team’s existing document or task system. For the fictional example, it could read as follows.
- Change to try. Add one clearly labelled current-document link to each of the next three design-review invitations.
- Owner. Mira coordinates with each organizer and document owner, then keeps the result notes together.
- Expectation. Participants should be able to find the intended document from the invitation when the call begins.
- What to record. For each call, note whether the invitation contained the intended link, whether participants could open it, and whether someone asked which document to use. Add a brief explanation when available.
- Review date. November 20, 2026, after checking how many of the three calls have taken place.
- Decision to revisit. Keep, adjust, or stop the invitation change based on the records and participant feedback.

Decide in advance what would count as a promising result. For this trial, the team might look for all three invitations to contain the intended link and no requests to locate the document at the start of those calls. That is a proposed review criterion for this example. It is not a measured outcome or a general benchmark.
If fewer than three calls occur before the review date, record the smaller sample and decide whether to extend the trial. If the link is correct but access still fails, record the access issue before adding more invitation text.
Close the loop at the agreed check
Use the final two minutes to read back the change, owner, and review date. Confirm where participants will put observations during the trial and how they can raise a problem before the next retrospective.
At the check, start with the records. Did the team make the planned change? What happened in the calls? What did participants find useful or cumbersome? A short trial can inform the next process decision while leaving uncertainty about why the outcome changed.
If you run the retrospective in Focus Room, allow the call, shared notes, and work-record hostnames participants need in the participating browser during the active extension session. Test access before the meeting and keep the experiment record in your usual team tools. Focus Room website-rule setup

