Day 4: Design a Game With Roles You'd Actually Play

Instructions

Design a real game you would actually participate in.

Part 1: Game specification

• Game type: Which of the 6 games (G1–G6)?
• Core outcome: What does winning produce?
• Duration: How long is one season?
• Player count: How many people?
• Observable measures: How do you know if it worked?

Part 2: Role design

Define 2–3 roles needed for this game. For each role, specify:

• Role name: What do you call this role?
• Core responsibility: What is this role's job?
• Observable behaviors: How can others see if you're playing this role well?
• Entry requirements: What capability do you need to take this role?
• Exit conditions: When/how does someone leave this role?
• Time commitment: How much time per week?

Part 3: Season structure

• Start ritual: How does the season begin?
• Mid-season check: How do you know if you're on track?
• End ritual: How does the season conclude?
• Outcome documentation: What artifact proves this season happened?
• Re-entry option: Could someone play again in a future season?

Part 4: The commitment

• Which role would you play? Be specific.
• For how long? Actual commitment, not aspiration.
• Who else would need to play? Name real people or describe real profiles.
• What would make you exit early? Be honest about your constraints.
• Why this game, now? What makes this worth doing?

Submission format

• Structured document with all parts complete
• Specific enough that someone could actually run this game
• Part 4 must show real thinking about constraints and commitment

What we're looking for

• Actual game design, not vague "it would be cool if..."
• Roles that are well-defined and observable
• Season structure that makes sense for the game type
• Honest assessment of whether you'd actually play
• Recognition of what infrastructure would be needed