The Walking Dead – 3D Environment Team Coordination
TLDR
As a game producer on a project inspired by The Walking Dead franchise, I supported the level design team by improving communication, structure, and delivery consistency. I implemented lightweight agile methods, clarified responsibilities, established clear communication rituals, and created processes that increased predictability, alignment, and adaptability within a small multidisciplinary team.
As a game producer on a project inspired by The Walking Dead franchise, I supported the level design team by improving communication, structure, and delivery consistency. I implemented lightweight agile methods, clarified responsibilities, established clear communication rituals, and created processes that increased predictability, alignment, and adaptability within a small multidisciplinary team.
Context
This project operated under constraints common to small studios: limited resources, overlapping responsibilities, and a high volume of interdependent tasks. My role focused on bringing structure, improving collaboration, and ensuring the team could deliver level design content with higher clarity and reduced rework.
This project operated under constraints common to small studios: limited resources, overlapping responsibilities, and a high volume of interdependent tasks. My role focused on bringing structure, improving collaboration, and ensuring the team could deliver level design content with higher clarity and reduced rework.
Key Challenges
1. Lack of defined roles and responsibilities, causing ambiguity and duplicated work.
2. Communication gaps due to the absence of structured processes and channels.
3. Limited planning and prioritization, resulting in reactive workflows.
4. Low adaptability to changes in design requirements and iteration needs.
Methodology Applied
I introduced a lightweight agile framework tailored to the maturity and size of the team. The approach emphasized short feedback cycles, visible task tracking, and progressive refinement of work. This methodology enabled the team to prioritize effectively, maintain steady momentum, and adapt quickly to shifting design requirements.
I introduced a lightweight agile framework tailored to the maturity and size of the team. The approach emphasized short feedback cycles, visible task tracking, and progressive refinement of work. This methodology enabled the team to prioritize effectively, maintain steady momentum, and adapt quickly to shifting design requirements.
Tools Used
I structured production workflows using:
• Jira for backlog management and task visibility
• Miro for level design reviews, diagrams, and feature breakdowns
• Confluence and Google Docs for process documentation and design notes
• Slack and Discord for daily communication and asynchronous alignment
• Internal builds and screen recording tools for playtest reviews
I structured production workflows using:
• Jira for backlog management and task visibility
• Miro for level design reviews, diagrams, and feature breakdowns
• Confluence and Google Docs for process documentation and design notes
• Slack and Discord for daily communication and asynchronous alignment
• Internal builds and screen recording tools for playtest reviews
These tools created a shared source of truth for tasks, documentation, and design intentions.
Daily and Weekly Rituals
To stabilize communication and maintain alignment, I established routines such as:
• Daily stand-ups focused on blockers, priorities, and cross-team dependencies
• Weekly syncs dedicated to roadmap updates, planning, and expectation-setting
• Sprint or weekly planning to break down tasks into actionable, short-term goals
• Regular internal playtests to review level design progress and adjust scope
• Open feedback channels to allow designers to surface risks and needs early
To stabilize communication and maintain alignment, I established routines such as:
• Daily stand-ups focused on blockers, priorities, and cross-team dependencies
• Weekly syncs dedicated to roadmap updates, planning, and expectation-setting
• Sprint or weekly planning to break down tasks into actionable, short-term goals
• Regular internal playtests to review level design progress and adjust scope
• Open feedback channels to allow designers to surface risks and needs early
These rituals increased predictability, reduced miscommunication, and fostered a collaborative environment.
Solutions Implemented
1. Introduced agile-inspired practices such as structured stand-ups, iterative cycles, and backlog management.
2. Defined clear ownership and expectations for each team member to reduce ambiguity.
3. Improved communication through consistent rituals and transparent task tracking.
4. Established incremental planning methods that strengthened prioritization and reduced rework.
5. Implemented continuous internal reviews to refine level design and integrate feedback earlier.
Culture and Team Development
I encouraged knowledge sharing, supported professional development, and maintained an open process for refining production workflows. This helped the team develop confidence, autonomy, and a more sustainable approach to delivering level design content.
I encouraged knowledge sharing, supported professional development, and maintained an open process for refining production workflows. This helped the team develop confidence, autonomy, and a more sustainable approach to delivering level design content.
