Day 4 — designing what happens when a survey DOESN'T work out
Most survey platforms only design the happy path: sign up, take
survey, get paid. I spent today in Figma designing what happens when
it doesn't go that way:
- You don't qualify for a survey (still get a small thank-you payout)
- A survey fills up while you're mid-attempt (compensated, not just
"sorry") - A "verifying your response" state, since trust in payouts matters
as much as the payout itself
Still zero app code — but I'd rather get these edge cases right in
design than patch them in after real users hit them.
Would love opinions: as someone who's used survey/gig platforms, does
seeing the payout and $/hr upfront (before starting) actually change
whether you'd bother? Or does it not matter much?
Trending on Indie Hackers
I like that you're spending time on the failure states rather than just the successful flow.
For survey platforms, users usually decide whether they trust the product when something goes wrong, not when everything works. Designing those moments deliberately can end up being a much bigger differentiator than adding another survey provider.