Dice Assassin
TLDR
As the producer on Dice Assassin, a turn-based puzzle game that blends stealth, tactics, and dice-driven mechanics, I was responsible for the full production workflow. I structured planning, documentation, communication, and reporting to ensure the team delivered a polished, system-focused game loop. Using ClickUp, Miro, and Discord, I supported the team in maintaining clarity, momentum, and iteration speed throughout development.
As the producer on Dice Assassin, a turn-based puzzle game that blends stealth, tactics, and dice-driven mechanics, I was responsible for the full production workflow. I structured planning, documentation, communication, and reporting to ensure the team delivered a polished, system-focused game loop. Using ClickUp, Miro, and Discord, I supported the team in maintaining clarity, momentum, and iteration speed throughout development.
Context
Dice Assassin is a minimalist puzzle experience where each move is dictated by dice values, requiring strategic planning and precise sequencing. The project’s core challenge was to create intuitive systems with enough depth to support tactical decision-making while maintaining a clean and readable presentation. My role was to organize the production pipeline, align the team around priorities, and maintain consistency across design, art, and engineering efforts.
Dice Assassin is a minimalist puzzle experience where each move is dictated by dice values, requiring strategic planning and precise sequencing. The project’s core challenge was to create intuitive systems with enough depth to support tactical decision-making while maintaining a clean and readable presentation. My role was to organize the production pipeline, align the team around priorities, and maintain consistency across design, art, and engineering efforts.
Key Challenges
Translating complex tactical mechanics into concise production tasks.
Maintaining team alignment across a fast-paced, iterative workflow.
Ensuring consistent documentation as systems evolved throughout development.
Balancing scope and polish to fit the timeline of a compact project.
Methodology Applied
I implemented a structured sprint workflow with weekly checkpoints and high task visibility. The production approach focused on breaking down systems into manageable iterations, maintaining constant communication across disciplines, and ensuring that every mechanic had clear specifications and testable outcomes.
I implemented a structured sprint workflow with weekly checkpoints and high task visibility. The production approach focused on breaking down systems into manageable iterations, maintaining constant communication across disciplines, and ensuring that every mechanic had clear specifications and testable outcomes.
Tools Used
The production pipeline relied on:
• ClickUp for sprint planning, backlog management, and task assignments
• Miro for system mapping, logic diagrams, and UI planning
• Discord for daily communication, quick syncs, and cross-team coordination
• Google Docs for design references, documentation updates, and production notes
The production pipeline relied on:
• ClickUp for sprint planning, backlog management, and task assignments
• Miro for system mapping, logic diagrams, and UI planning
• Discord for daily communication, quick syncs, and cross-team coordination
• Google Docs for design references, documentation updates, and production notes
These tools ensured alignment across design, art, and engineering, while keeping iteration loops efficient.
Daily and Weekly Rituals
To support predictable delivery and reduce miscommunication, I established routines such as:
• Daily stand-ups focused on blockers, dependencies, and short-term priorities
• Weekly sprint planning and review sessions to refine scope
• Regular system check-ins to validate gameplay logic and mechanic behavior
• Continuous documentation updates to reflect design decisions and new specifications
• Leadership reporting summarizing progress, risks, and next steps
To support predictable delivery and reduce miscommunication, I established routines such as:
• Daily stand-ups focused on blockers, dependencies, and short-term priorities
• Weekly sprint planning and review sessions to refine scope
• Regular system check-ins to validate gameplay logic and mechanic behavior
• Continuous documentation updates to reflect design decisions and new specifications
• Leadership reporting summarizing progress, risks, and next steps
These rituals created a stable structure that supported quick iteration without sacrificing clarity.
Solutions Implemented
1. Structured sprints in ClickUp with clear deliverables for systems such as dice logic, enemy behaviors, and level layouts.
2. Visual mapping in Miro to clarify turn order rules, difficulty progression, and UI interactions.
3. Centralized communication in Discord to streamline feedback loops and facilitate interdisciplinary collaboration.
4. Consistent reporting to leadership to flag risks early, adjust scope, and maintain project alignment.
Impact and Learnings
This project strengthened my ability to manage system-heavy, minimalist puzzle games. I improved my capacity to balance production pacing with iterative design, maintain visibility across the team, and support autonomy without losing alignment. Dice Assassin reinforced my experience in guiding small teams through focused, tactical gameplay development with efficient coordination and clear strategic direction.
This project strengthened my ability to manage system-heavy, minimalist puzzle games. I improved my capacity to balance production pacing with iterative design, maintain visibility across the team, and support autonomy without losing alignment. Dice Assassin reinforced my experience in guiding small teams through focused, tactical gameplay development with efficient coordination and clear strategic direction.