Run a feedback session
Choose a survey or retrospective, prepare your team, and turn the feedback into an action you can review.
Start with a decision you need to make. “What should we change about code reviews next sprint?” gives a session a clearer purpose than “How is everyone doing?”
You need access to create the survey or retro in the intended workspace. Participants have different access needs; check the sharing settings before inviting them.
Choose a format
Section titled “Choose a format”| You want to… | Use… | Start here |
|---|---|---|
| Ask everyone the same questions | Static Survey | Create your first survey |
| Explore answers with AI follow-ups | Agent Survey, with available access and credits | Create an Agent Survey |
| Discuss a shared experience as a team | Retrospective | Run your first retro |
A survey lets people respond in their own time. A retro gives the team a shared board for discussing feedback. You can also collect a survey before a discussion, but avoid making people repeat the same work without a reason.
Prepare the session
Section titled “Prepare the session”Choose a focused time period and explain what the team will do with the feedback. Review the questions or board columns before sharing. Tell people whether they need to verify their email and what privacy settings apply.
For surveys, use the pre-send checklist. For retros, read facilitation practices and choose a format that fits the discussion.
Make it easy to contribute
Section titled “Make it easy to contribute”Give people enough context to answer, but do not suggest the answer you hope to hear. During a retro, leave quiet time for writing before the group discusses the cards. Read Feedback → Group → Vote → Review for the controls at each stage.
Send participants the participant guide if they are new to ScatterSpoke.
Review and follow through
Section titled “Review and follow through”Open the survey’s Responses section or the retro board and read the original feedback before presenting themes. A high vote count tells you what people want to discuss; it does not prove a root cause.
Choose one action, name an owner, and set a review date. Record it where the team can find it. At the next session, ask whether the action helped.
Follow the Sprint 24 example to see feedback cards become a grouped topic, a discussion, and a concrete next step.
When something goes wrong
Section titled “When something goes wrong”Use Troubleshooting for locked survey questions, blocked participants, missing results, or an Agent draft that will not continue. Check plan usage when a feature is unavailable.