Level Up Slides Studio Dev Sprint
Design • Collaborate • Playtest
PROJECT BRIEFING
LEVEL UP: GAME DESIGN LAB
Form an indie dev studio to build a playable blueprint: characters, core mechanics, level layouts, and win conditions.
Team Synergy & Roles
Deep System Rules
Playtest Peer Feedback
Studio Team Architecture
Four Essential Studio Roles
1. Studio Producer
Tracks team sprint pacing, facilitates equal voice, and ensures deadlines and deliverables are met.
Habit: “What is our team consensus?”
2. Systems & Rules Lead
Defines player controls, physics, scoring logic, and balanced win/fail states.
Habit: “Is this rule clear to a newcomer?”
3. World & Level Architect
Draws Level 1 grid architecture, placing platforms, hazards, items, and checkpoints.
Habit: “How does the space teach the player?”
4. Narrative & Character Lead
Creates hero backstory, enemy behaviors, visual style, and emotional stakes.
Habit: “Why does the player care about this goal?”
Golden Rule: Roles lead discussions, but decisions require studio team consensus.
Design Anatomy
The 4 Pillars of Every Game
Pillar 1
Characters
Protagonist abilities, limitations, hitbox size, personality, and enemy behavior patterns.
Who is in this world?
Pillar 2
Mechanics
The verbs of the game: jump, dash, sneak, hack, solve. Verbs combined create emergent gameplay.
What can players do?
Pillar 3
Level Space
Geometry, obstacles, safe zones, verticality, line of sight, and pacing from easy to intense.
Where do they move?
Pillar 4
Goals & Rules
Explicit win condition, fail states, scoring mechanisms, and constraints that create tension.
Why are they playing?
Design Challenge: If one pillar changes, all others must adapt. Test their harmony! System Interconnection
Player Experience
The 30-Second Core Loop
1
Player Action
Input command (jump across chasm, cast shield, dodge enemy).
2
Game Feedback
Audio/visual reaction (sparks fly, sound cue, platform shakes).
3
Direct Reward
Coin gathered, key unlocked, health recovered, meter fills.
4
Next Tension
New obstacle appears, timer ticks down, boss awakens.
Studio Discussion: What is your player doing over and over again every 30 seconds?
Core Verbs Matter
Spatial Progression
Anatomy of a Killer Level 1
Phase 1 • Safe Nursery
Teach Without Words
Spawn in a zero-danger zone. Player tests controls and discovers basic movement before encountering lethal threats.
Example: Low obstacle requiring jump to proceed.
Phase 2 • Escalation
Combine Mechanics
Combine jump with timing, introduce roaming patrol enemies, and offer an optional high-risk/high-reward secret branch.
Example: Moving platform guarded by laser beam.
Phase 3 • Climax
The Gatekeeper Test
A mini-boss, time escape, or puzzle lock that proves the player has mastered all concepts introduced in Level 1.
Example: Defeating boss unlocks the warp portal.
Rule of Thumb: Never kill the player with something they couldn't see coming!
Quality Assurance
The Playtest & Feedback Protocol
Praise
What part of the gameplay felt genuinely fun, intuitive, or clever?
“I loved how the dash mechanic allowed me to bypass the spike trap.”
Polish
Where did the rules feel unfair, confusing, or frustratingly unclear?
“I wasn't sure if touching the red crystal was poisonous or healed me.”
Ponder
What if the studio added a twist or tweaked an existing system rule?
“What if jumping had limited stamina so players had to plan steps?”
Studio Feedback Mindset: Feedback is data, not an attack. Listen silently before responding!
Iterate & Level Up
Game Forge Project Packet Game Forge • Studio Blueprint
Part 1: Studio Identity & Game Concept Document
Page 1 of 3
Pre-Production Phase
Studio Name:
Working Game Title:
Studio Team Members & Roles:
PRODUCER
SYSTEMS LEAD
LEVEL ARCHITECT
NARRATIVE/ART
1. The High-Concept Elevator Pitch
In one punchy sentence, summarize your game: “Play as [WHO] trying to [DO WHAT] while facing [OBSTACLE/THREAT].”
Target Genre & Style:
e.g., 2D Platformer, Stealth Puzzle, Survival Runner, Top-down RPG
Target Audience & Mood:
e.g., Casual puzzle fans, adrenaline seekers; Cozy, spooky, neon-cyber
2. The 30-Second Core Gameplay Loop
What does the player do repeatedly every 30 seconds? Fill out your studio's game cycle:
Step 1: Action What input does player make?
Step 2: Feedback What does screen/audio show?
Step 3: Reward Points, progress, energy?
Step 4: Threat What pushes urgency next?
Studio Team Agreement
Our studio agrees that creative disagreements will be resolved by voting or prototyping both options. All members sign below:
Sign: ____________
Sign: ____________
Sign: ____________
Sign: ____________
Level Up Studio • Video Game Design Project Document GDD-01
Game Forge • Studio Blueprint
Part 2: Character Specifications & Core System Rules
Page 2 of 3
Systems & Rules
Protagonist (Player Character)
Name & Visual Silhouette
Hero Name & Backstory Goal:
Primary Ability / Move:
Weakness / Vulnerability:
Character Sketch / Sprite:
Draw character icon
Enemies, Hazards & Obstacles
Minor Foe (Common) Name & Patrol Pattern:
How does hero counter it?
Environmental Hazard Trap / Hazard Type (Spikes, Lava):
Timing / Trigger:
Level Boss / Apex Foe Boss Name & Attack Phase:
Telegraphed Tell & Weakpoint:
Win / Fail States & Economy
Victory Condition (Win):
What exact event completes Level 1?
Fail State (Game Over):
Health loss, timer expiry, falling?
Collectibles & Score:
What items grant points / upgrades?
Player Controls Mapping
Playtest Protocol Worksheet Playtest Lab • Peer Critique
Part 1: Quality Assurance & Gameplay Evaluation Protocol
Page 1 of 2
Peer Review Session
Testing Studio (Your Team):
Developer Studio Being Tested:
Game Title Being Tested:
Phase 1: 60-Second Pitch Test
Did the dev studio clearly explain the protagonist's goal and win condition?
Instantly clear and exciting A bit confusing on how to win
Notes on Pitch:
Phase 2: Walkthrough Test
Simulate playing Level 1 on their map grid. Where did questions arise?
Pacing felt smooth & fair Found an unfair / impossible jump
Observation on Level Flow:
Phase 3: The 3P Constructive Feedback Matrix
Be specific, kind, and helpful
1. Praise (What felt fun, engaging, or innovative?) “I really liked...”
2. Polish (Where did mechanics feel confusing or unbalanced?) “It was difficult to understand...”
3. Ponder (What creative mechanic or twist could they add?) “What if you added...”
Developer Studio Commitment
The Developer Studio writes one specific revision they will make based on this feedback:
Level Up Studio • Video Game Design Project Document QA-01
Studio Team • Collaboration Debrief
Part 2: Teamwork Skills, Conflict Resolution & Iteration Reflection
Page 2 of 2
Studio Evaluation
Studio Collaboration Checkup
Rate your studio's collaborative habits as a team (1 = Needs Work, 4 = Master Studio):
1. Active Listening & Equal Voice Every team member spoke up and was listened to without interruption.
1 2 3 4
2. Role Responsibility & Follow-Through Each member completed their role deliverables (producer, systems, level, art).
1 2 3 4
3. Consensus & Constructive Compromise Disagreements were handled respectfully through compromise or testing.
1 2 3 4
4. Growth Mindset & Feedback Integration The studio welcomed critique gracefully and iterated on their design.
1 2 3 4
Studio Post-Mortem Reflection
A. Describe a disagreement your studio had and how you resolved it:
B. How did playtest feedback from other teams change your game blueprint?
C. What is one collaboration skill you personally improved during this project?
Studio Producer Verification: All members actively contributed to today's design sprint.
Signature:
Level Up Studio • Video Game Design Project Document QA-02
Game Studio Teacher Guide Teacher Facilitation Guide
Level Up Studio: Collaborative Video Game Design Sprint
Page 1 of 2
Instructional Blueprint
Target Skill
Collaboration, consensus-building, team role accountability, structured peer critique.
Duration & Grouping
3-5 Class Sessions (45-60 min each); 4 students per studio team.
Core Deliverable
Game Forge Blueprint (GDD) + Playtest Critique Protocol + Studio Reflection.
Instructional Sprint Pacing Timeline
Sprint 1: Studio Kickoff
Introduce slides, assign 4 roles, sign team contract, brainstorm high-concept pitch & 30-sec loop.
Sprint 2: Systems & Map
Flesh out character abilities, rules, and hazards. Architect Level 1 on the 14x8 spatial grid.
Sprint 3: Playtesting QA
Studios swap blueprints for simulated walkthroughs. Execute Praise, Polish, Ponder feedback.
Sprint 4: Polish & Post
Incorporate playtest feedback, finalize blueprint, conduct studio self-assessment & showcase.
Studio Role Distribution & Interdependence
Studio Producer: The project anchor. Focuses on pacing, ensuring everyone gets turn-taking talk time, and moderating voting.
Systems & Rules Lead: The logic champion. Ensures controls are distinct, win/loss states are fair, and rules don't contradict each other.
Level Architect: The spatial designer. Leads Level 1 grid drawing, hazard spacing, and safe zone progression.
Narrative & Art Lead: The creative visionary. Builds the protagonist backstory, visual theme, and thematic coherence.
The Studio Conflict-Resolution Protocol
The 3-Minute Rule for Deadlocks:
Each conflicting member pitches their idea for 45 seconds uninterrupted.
The Producer calls a team vote.
If tied, the team tests both on grid paper or the teacher flips a coin.
Collaboration Sentence Stems:
“I hear your idea about __, but what if we combined it with __?”
“How does this rule support our core 30-second loop?”
“Before we write that down, does everyone on the team agree?”
Level Up Studio • Teacher Facilitation Guide Document TG-01
Collaboration & Design Rubrics
Evaluation Criteria for Team Dynamics and Systems Design
Page 2 of 2
Assessment & Rubric
Collaboration & Teamwork Mastery Rubric
