Facilitate remote sessions without forcing consensus
Preparation, speaking turns and a complete case to turn remote voting into clear decisions.
1. Prepare the discussion and roles
Before sharing the link, select a few stories with outcomes, criteria and open questions. Confirm facilitator, voters and observers. Collaborators can help the organiser prepare stories and manage rounds.
Agree on an accessible voice or text channel and a reference story. Silence is not agreement. Provide an explicit way to request clarification or a break.
2. Protect the independence of the first vote
Read the story and resolve understanding questions before cards are chosen. Avoid announcing a reference number during voting. StoryFlop keeps votes private until revealed, and observers are not counted as voters.
Check that expected voters can participate before revealing. Disconnection or delay is not voluntary abstention. If participation changes, confirm it with the group and explain how to proceed.
3. Give turns to understand, not to persuade
After revealing, invite the lowest and highest voters to explain assumptions. Ask about existing components, included tests or unknown dependencies. Make room for risks not yet in the description.
If arguments repeat without information, summarise what is known. The next step may be clarification, splitting or investigation. Do not keep voting until someone changes their card through fatigue.
4. A remote case from start to finish
In this fictional exercise, three people estimate password recovery as 3, 5 and 13. The facilitator asks about email and tests. The team confirms the service exists and adds link expiry to the criteria.
The team votes again with clarified scope and agrees on 5 for this example. An unresolved question could instead end the session with an owner and next action, not a number. The template supports both outcomes.
5. Close with decisions you can retrieve
After each story, read out scope, estimate if any, risks and next action. Transfer them to the backlog. StoryFlop rooms and data are removed after 14 inactive days; history does not replace a lasting record.
At the end, ask which requirement was missing and whether everyone could participate. Use the answer for next time. Learning does not require publishing team information: public cases can be clearly identified fictional exercises.
Worked cases: from initial scope to a decision
From silence to a visible decision
Before
After 3, 5 and 13 are revealed, someone suggests “let's take 5” without asking the extremes. Two people remain silent and scope stays ambiguous.
After
The facilitator assigns speaking turns, confirms existing email, includes tests and requests a new independent vote. Then the decision is read back and recorded in the task.
Why this decision: The important change is making assumptions and agreement visible. The 5 belongs to this exercise; it does not mean a real session must end with that number.
Put it into practice
Sources and further reading
The examples and StoryFlop instructions were written for this section. These sources provide context for the method and refinement: