✦
Protect the spark
Preserve what makes the idea inviting before process, governance, or optimization flattens it.
Foundry readiness
Assessment begins in Stage 4
Shape the activity first, then evaluate whether it is ready for a real pilot.
—
Not yet scored0 of 8 rated
Stage one
Idea Playground
Create productive creative tension before designing the activity. Start with unexpected combinations rather than polishing your first idea. Roll the Zwicky Matrix until the environment, emotional tone, and constraint produce something interesting enough to explore. Do not judge ideas yet—you are generating possibilities, not selecting winners.
Stage two
Capture the Spark
Protect the emotional value before process takes over. Describe why someone would genuinely want to participate before thinking about moderation, scheduling, channels, prizes, or logistics. If the activity is not exciting in a concise explanation, improving the operations will not save it.
Your task: Write the title, hook, community need, source of fun, and failure boundary without solving logistics yet.
Foundry rule: If the activity cannot be described as a desirable experience before discussing channels, credits, roles, or moderation, the idea is not ready for process design.
⌛
Cap volunteer labor
Every activity needs an effort ceiling, a stop condition, and a way to finish without one person carrying it indefinitely.
✓
Prefer completion over judgment
Use participation and thoughtful recognition unless ranking genuinely improves the creative experience.
Stage three
Shape the Activity
Turn inspiration into a participant experience. Reduce the idea to something a new community member can understand without live explanation. Define how people participate, how much effort is expected, and the three essential actions they perform from beginning to end.
Your task: Choose the participation structure, set realistic effort limits, and express the complete participant journey as Receive, Create, and Share.
How much active creative time should one participant expect to spend?
How long is participation open, regardless of the time needed to make one entry?
Maximum total time the organizer should spend preparing, answering questions, reviewing, and closing.
Name the element that keeps entries meaningfully connected.
State what creators still control so the activity does not become overly prescriptive.
Stage four
Stress-Test It
Find operational risk before volunteers do. Every promising activity hides complexity somewhere. Evaluate host workload, moderation effort, accessibility, participation friction, sustainability, and likely failure points before the community discovers them during launch.
Score readiness, not originality: rate the design you have written, not the idea you hope it will become. Use 1 for a serious weakness, 3 for acceptable with caveats, and 5 for unusually strong.
Clarity in three steps
18% weightCould a new participant understand what to receive, create, and share without asking the host?
Look for undefined terms, hidden steps, exceptions, or instructions that only make sense to experienced members.
0
Audience accessibility
12% weightCan the intended audience participate with the accounts, devices, abilities, and features they are likely to have?
Consider free-tier access, mobile limitations, language, sensory accessibility, required expertise, and expensive generation demands.
0
Schedule and timezone fit
8% weightDoes the timing model give the intended audience a fair opportunity to participate?
Live formats are not inherently bad, but their exclusivity should be deliberate rather than accidental.
0
Moderation burden
15% weightCan the activity run without disproportionate review, conflict resolution, reminders, or rule enforcement?
Count the work that occurs after launch, not only the time required to write the announcement.
0
Fairness and recognition
15% weightAre selection, judging, rewards, and recognition structured so participants can reasonably perceive them as fair?
Watch for popularity effects, friend-group bias, campaigning, opaque judging, and unequal access to rewards.
0
Rights, consent, and safety
12% weightDoes the design avoid unclear ownership, unwanted reuse, unsafe themes, impersonation, or participation without consent?
This matters most for covers, transformations, collaborations, member-provided source material, and public showcases.
0
Host resilience
10% weightCould the pilot finish cleanly if the original proposer became unavailable?
Look for documented instructions, bounded duties, a backup path, and freedom from one person’s constant presence.
0
Community value after creation
10% weightWill the results be worth browsing, discussing, celebrating, or learning from after participants submit them?
Look for interpretive variety, meaningful conversation, discovery, or a reusable community artifact.
0
How the score works: the eight criteria form a weighted readiness score. Clarity, moderation, and fairness carry more weight because failure there creates disproportionate community cost. A score is withheld until every criterion is rated and at least one community need is selected. Serious weaknesses in clarity, fairness, rights, moderation, or host resilience cap the final readiness band even when other ratings are high.
Stage five
Design the Pilot
Prove the concept with the smallest successful experiment. Do not launch the perfect version first. Design a limited pilot that can show whether the activity is enjoyable, understandable, repeatable, and manageable without creating unnecessary organizer effort or participant expectations.
Pilot principle: run the smallest version that can reveal confusion, workload, engagement, and moderation risk.
Draft each field as a testable boundary, not an aspiration. A good pilot says who it is for, how long it lasts, how much labor it may consume, what success looks like, and when to stop.
Who should participate in the first test, and where will they encounter it?
How long will the pilot remain open? Include whether it is live or asynchronous.
Set a hard limit for preparation, support, review, and closing work.
Describe what participants receive, if anything. Prefer recognition unless competition is essential.
Name observable evidence that would justify repeating or refining the activity.
Define the threshold at which the pilot should pause rather than consume more volunteer effort.
Pilot lifecycle
Keep each phase deliberately small. The lifecycle should fit the pilot, not quietly become a permanent operating process.
- PrepareApprove the activity brief, prompt, and boundaries.
- LaunchPublish one clear announcement in the selected space.
- ObserveTrack real ambiguity without over-explaining the activity.
- CelebrateRecognize participation and interesting variety.
- DecideRepeat, revise, archive, or stop based on evidence.
Stage six · Main path end
Export Proposal Brief
Turn the design into something another organizer could run. The proposal should explain the activity clearly enough that another moderator or volunteer can understand its purpose, participant experience, execution, workload, risks, and expected outcomes without additional verbal context.
Share the decision-ready version: this brief preserves the creative intent while exposing workload, guardrails, and pilot boundaries.
Discord Announcement Snippet
A condensed announcement containing the title, hook, participant contract, format, and creative constraints.
0 / 2,000 characters used
Snippet Truncated to Fit Discord Limit
Full Proposal Brief
The complete pre-pilot Markdown proposal, including risk review and pilot boundaries.
Total Length: 0 characters (~0 words)
Stage seven
Close the Loop
Capture what experience taught that planning could not. Record what actually happened, where participants struggled, what exceeded expectations, and which changes should become part of future versions instead of relying on memory after the event.
Close the learning loop: separate energy from friction, then consciously choose whether to repeat, revise, archive, or stop.
Stage eight · Post-pilot review
Export Post-Event Archive
Preserve organizational knowledge for the next organizer. Archive the original activity design, pilot results, retrospective, disposition, and final recommendations so future volunteers inherit useful experience instead of repeating the same discovery work.
Preserve the complete loop: this archive records what was planned, what happened, and what the community decided to do next.
Post-Event Archive Snippet
A condensed Discord-ready summary of the operational outcome and next decision.
0 / 2,000 characters used
Archive Snippet Truncated to Fit Discord Limit
Full Post-Event Archive
The unrestricted unified Markdown post-mortem, including the original proposal, operational logs, retrospective, and disposition.
Total Length: 0 characters (~0 words)