How to use ScatterSpoke
Follow a practical workflow to collect feedback, understand what people mean, and agree on a useful next step.
ScatterSpoke helps you collect feedback through surveys and retrospectives, then explore what people said with Ask. Start with one question you want to answer. You do not need to set up every feature before your team can contribute.
1. Choose what you want to learn
Section titled “1. Choose what you want to learn”Make the goal specific. “Improve the team” is hard to act on. “Find out what slowed down our last sprint” gives people something concrete to discuss.
For example, a product team might want to understand why work keeps carrying into the next sprint. They can ask about blockers, unclear requirements, and time spent waiting for reviews.
Choose one collection method:
| Your goal | Start with |
|---|---|
| Ask everyone the same questions and compare answers | A Static Survey |
| Let AI ask follow-up questions to understand an experience | An Agent Survey |
| Discuss a shared experience together | A retrospective |
2. Collect feedback
Section titled “2. Collect feedback”For a first survey, keep the questions focused. Ask about one thing at a time. Include an open question so people can explain a rating or raise something you missed.
Follow Your first survey to create a short survey, review it, publish it, and get a link to share.
For a team discussion, follow Your first retro. Give people quiet time to write before discussing their feedback. This helps people contribute without having to compete for speaking time.
Before sharing, check the participant experience and the privacy settings. Tell people what you are asking, how the feedback will be used, and when you plan to discuss the results.
3. Read before drawing conclusions
Section titled “3. Read before drawing conclusions”Open the responses or retro cards and read what people actually wrote. A repeated theme is worth exploring, but a count alone does not explain what caused it.
Compare specific examples. If several people mention “slow reviews,” look for whether they mean code reviews, design approval, or a decision from another team.
Use Ask to explore a focused question such as:
What blockers do people mention, and which feedback supports each one?
Follow the sources in the answer. Check that the evidence matches the time period and team you care about. Treat an answer without enough evidence as a reason to investigate further.
4. Agree on a next step
Section titled “4. Agree on a next step”Choose an action small enough to try before the next check-in. Name an owner and a date to review it with your team.
For example: “For the next sprint, we will set aside 20 minutes each afternoon for pending reviews. We will check whether this reduced waiting time at the next retro.”
Share what you heard, what you will try, and what you are not changing yet. People are more likely to give useful feedback when they can see what happened after the last round.
5. Check back
Section titled “5. Check back”At the next survey or retrospective, ask whether the action helped. Keep the wording of any rating question consistent if you want to compare answers over time.
If nothing improved, return to the original examples. The team may have identified a symptom rather than the cause, or the action may need more time.
Keep learning
Section titled “Keep learning”- Question types — choose a format that fits the question.
- Responses and transcripts — inspect what came back.
- Retrospective best practices — make a team discussion useful.
- Roles and permissions — understand access before inviting people.