A design challenge is the cheapest community event that exists: one good prompt, a deadline, and a way to vote. No prizes required, no scheduling calls — and yet a well-run challenge reliably produces the best custom cards a community makes all month, because constraints are creative fuel. This is a playbook for running them, drawn from how challenges work on PipGlyph and what makes design prompts succeed anywhere designers gather.
What makes a brief good
The classic mistake is the open prompt: "design a cool creature!" Open prompts produce fewer entries, not more — infinite option space is paralyzing, and entries can't be compared, so voting feels arbitrary.
A good brief has one constraint that creates tension and one axis of freedom:
- "Design an artifact that cares about the graveyard" — tension: artifacts don't usually do that; freedom: any cost, any rarity, any flavor.
- "A common that would be the best card in a draft archetype" — tension: power inside common's complexity budget; freedom: which archetype.
- "A planeswalker whose abilities all cost the same loyalty" — tension: structural; freedom: total.
Test your brief by designing two entries yourself before posting. If your two designs feel samey, the brief is too narrow. If you can't finish one in twenty minutes, it's too hard for a weekly cadence.
Sizing the window
- One week is the workhorse: long enough for word to spread, short enough that "I'll do it later" still happens this week. PipGlyph challenge pages show a days-left badge, and urgency genuinely moves entries.
- 48-hour flash challenges spike energy but only work in communities that check in daily.
- Month-long majors suit set-building prompts ("design a cycle of five") — pair them with a midpoint check-in post or they go quiet in the middle.
Whatever you pick, end on a weekend — most entries land in the final 48 hours, and people design on Saturdays.
Tags are the entry mechanism
On PipGlyph, a challenge is structurally just a brief plus a tag: entering means publishing a public card wearing the challenge tag, and the challenge page collects every tagged card automatically, ranked by likes. The editor even offers an "Enter the challenge" toggle while a challenge is live, so entrants can't typo the tag.
If you're running a challenge anywhere (PipGlyph, a Discord, a subreddit), the tag discipline matters:
- Make it short, unique, and unambiguous —
arcane-frontiers, notchallenge1. - Never reuse a tag across challenges; old entries will pollute the new gallery.
- Put the tag in the brief twice — people copy-paste from the middle of text.
Judging: community vote beats panels
Panel judging (the organizer picks winners) feels authoritative but creates two problems: it's slow, and entrants optimize for the judge's known taste. Community voting — on PipGlyph, likes on the entries — has the opposite virtues: instant, transparent, and it rewards cards that players love, which is the actual point of card design.
Two fairness rules make voting work:
- Visibility symmetry — every entry should be browsable from one page (the challenge page does this), so early entries don't dominate purely by exposure time.
- Self-votes don't count — PipGlyph's trending math already excludes self-engagement; for manual events, just state the norm.
Announce results within a day or two of close. The announcement post — winner, two runners-up, one "most audacious" — is itself content, and the "most audacious" slot keeps experimental designers entering even when they don't expect to win.
The cadence is the community
A single challenge is an event; a rhythm of challenges is a culture. The sustainable pattern:
- Weekly or biweekly, posted the same day each time.
- Rotate the constraint type: mechanical (design with keyword X), flavor-first (design THIS character), structural (a common, a cycle, a vanilla creature with great stats), and remix rounds (improve a real card — Scryfall import makes this trivial).
- Archive visibly. Past challenges with their entries stay browsable on PipGlyph; the archive is the recruitment pitch — new members scroll old briefs and think "I'd have entered that."
Running one on PipGlyph
Mechanically, a challenge on PipGlyph is one row: title, brief, tag, start and end dates, and a featured flag that puts a banner on the gallery while it's live. Entrants publish tagged cards; the challenge page ranks by likes; the window closes itself. If you'd like to see a brief in the wild, the challenges page shows the current featured run and the archive of past briefs.
FAQ
Do challenges need prizes?
No — visibility IS the prize. The winner sits on top of a permanent page, and a results post names them. If you want stakes anyway, cosmetic ones age best: the winner picks the next brief.
How many entries make a challenge "successful"?
For a small community, five genuine entries is a success — that's five designers who shipped something. Entries scale with community size and brief quality, not with prize value. The failure mode isn't low entries; it's a confusing brief that gets zero.
What if someone enters something off-brief?
Let the vote handle it. Off-brief-but-brilliant losing to on-brief-and-solid is the system working; deleting entries is moderator energy better spent writing next week's brief. Reserve removal for actual content violations.