A Feedback is a questionnaire you send to people and collect over days, not minutes — the async counterpart to the live Sparks. Up to 10 questions, shared by code or sent to a named roster. People answer in their own time, and you can re-run the whole thing later to see whether anything actually moved.
Sparks are for the room you're standing in. Feedbacks are for everyone else: the remote half of the team, the folks who missed the workshop, the stakeholders you'd never get in one calendar slot. You write the questions once, choose how people get in, and let the answers arrive.
Nobody has to be free at the same time. The questionnaire waits.
Invite a roster and the host sees responded vs waiting — and can nudge.
Same questions, next quarter. Two cycles in, a trend line appears.
People expect a long list here. There isn't one, and that's deliberate. Every Feedback question is either a Choice or a Free text. The star rating people go looking for is not a third type; it's a switch you can flip on either of these.
A prompt with 2 to 10 options. By default people pick exactly one; turn on multi-select and they can tick as many as apply. Results come back as bars with a count per option.
An open answer, in the respondent's own words. Pick short (up to 300 characters) for a one-liner, or long (up to 2,000) when you actually want the story. Answers come back as quotes — in shuffled order.
This choice decides everything downstream: whether there's a shareable code, and whether there's a roster to chase.
Anyone holding the code or link can respond, no account needed. Share it in Slack, drop the QR on a slide. You get volume and reach; you don't get a roster, so you can't tell who hasn't answered yet.
A named roster. Each person gets their own emailed link, and the host can see who's responded and who's still waiting. There is no public code for an invite-only Feedback — try to open one by code and it's simply refused.
Opening and closing can both run themselves. The blanks are the interesting part.
| Status | What it means | What's happening to your emails |
|---|---|---|
| Draft | You're still writing it. Nobody can respond. | Nothing sent. You can add people to the roster now — they just don't hear about it yet. |
| Upcoming | Published with a start date in the future. Parked, waiting. | Still nothing sent. The invitations sit tight until the start time arrives. |
| Live | Open for responses. | This is when the invitation emails actually go out. |
| Closed | Responses locked; results frozen. | Nothing further. Start a new cycle to run it again. |
Add people by email one at a time, or import a squad's roster in one go. The thing worth internalising: adding someone to a draft does not email them. The emails go out when the Feedback opens. (Add someone to an already-live Feedback and they're mailed right away — there's nothing left to wait for.)
Not the host. Not the org. The person answering chooses, per submission, whether their name rides along. Guests responding by code are always anonymous — they have no name to attach in the first place.
An anonymous response is stored with no name and no link back to the invitation it came from.
Anonymous answers surface without a submit time, so they can't be lined up against the roster's response times.
Free-text answers are randomized (cryptographically, not by a guessable seed) before anyone reads them.
A Feedback isn't a one-shot form. Hit “Start a new cycle” and the same questions run again with a fresh code. Every past cycle keeps its own responses and its own frozen results — nothing is overwritten, and two cycles never get quietly averaged into one number.
Results are for the host who created the Feedback. Respondents answer and go — they don't get the aggregate.
On an invited Feedback, how many are in and how many you're still chasing.
For every question you switched the rating on: the average, and the full 1–5 spread.
A count per option, so the shape of the answer is obvious at a glance.
Read what people actually wrote — in an order that tells you nothing about who wrote it.
The whole lifecycle, in the order you'll actually hit it.
Start a new Feedback, give it a title, and write your questions — up to ten. For each one, pick Choice or Free text, and flip on the star rating if you want it scored too.
Code & link, or invitation only. Set a start date (or leave it blank to open on publish) and a close date (or leave it blank to close by hand).
For a code Feedback, grab the code and QR from the share screen. For an invite-only one, build the roster — by email, or by importing a squad.
It opens now, or parks as Upcoming until its start time. This is the moment invitation emails go out — not when you added people.
Recipients tap the link in their email; everyone else types the code. Each person chooses named or anonymous, answers, and they're done.
Follow responded-vs-waiting as it fills, resend a nudge where it's needed, and close it — by hand, or let the close date do it.
Run the same questions again on a fresh code. Two closed cycles in, the trend chart appears — and now you can actually see whether anything changed.
Ten questions, a code or a roster, and answers that arrive while you get on with your day.
Start free arrow_forward