Designing Challenges⁠, from the brief to the payout.

CrowdPad let fans invest in creators by buying their tokens. The company wanted those tokens to unlock something, and I designed the first thing they unlocked. The easiest way to show it is to follow one challenge.

Riya has a brief from Spotify and 1,204 supporters. Before anyone can join, she makes seven decisions. My first draft asked them all on one screen and read like a tax form, so I split it: one question per screen, with the card building beside it.

That was a hunch about drop-off, not a test result. If she leaves halfway, the brief is kept as a draft. Before it goes live, she reviews the invitation and funds the rewards. A failed payment takes her back to payment, with every answer intact.

Meera supports Riya. She reads the brief, deadline and reward before deciding to join. Crowdpad checks her own wallet for Riya’s token, any amount at all⁠. We looked at Discord roles earned through reputation, but token access connected participation to CrowdPad’s creator economy. Joining checks what Meera holds. It doesn’t spend her token.

Meera films outside the app and comes back with a link. We could have taken links in the chat, the way a classroom thread does. But a link in a chat doesn’t stay attached to the challenge it answers.

While Meera makes her video, Riya comes back to the challenge. A saved brief, an unpaid reward and a live challenge need different next actions. Putting them behind the same “create” button would make her start again.

The workbench brings those return routes together. This reconstructed management flow lets her resume the missing step, see the entries coming in, then close submissions before choosing winners.

Riya opens each entry beside the brief and its guidelines, then ranks her top three. After that, on its own screen, she sees the same three people with amounts beside them before anything is paid. The judgment and the commitment each get a moment.⁠

Reviewing is also where a vague brief bites. The description says what to make; the guidelines say what counts. Without them, Riya ends up inventing rules after the entries are in.

Meera needs to know she’s waiting, not forgotten. Then she needs an outcome, including when she doesn’t place. A cash reward needs an account, a visible fee and a transfer receipt. Perks and points need their own claim paths. If the transfer fails, nothing is lost⁠.

Challenges shipped and creators used it, including creators in the UAE and South Asia who launched a token and then ran challenges for its holders. I don’t have verified numbers, so these are the ones I can stand behind.

Access was the starting point. The design was giving Riya and Meera something clear to do together.⁠