Managing a Health Game: Lessons From Tim Leinert
A game built for people living with depression and bipolar disorder puts player experience at the centre of every schedule decision. In a 35-minute Time Limit conversation, producer and product owner Tim Leinert of Mindforce Game Lab explains how he moved from traditional project management into leading video game work for a digital healthcare startup, and what that shift changes in daily practice.
Start with feelings, then learn in public
Leinert describes a charter that begins with intended emotion. Instead of locking every detail at the start, the team agrees what players should feel and what outcome the experience should support, then leaves room to learn as development proceeds. That approach suits a purpose-driven creative project, where early assumptions need testing against real reactions.
A practical checklist drawn from the episode:
- Write the charter around feelings and outcomes, not only deliverables.
- Invite the whole team to observe testing with the target group so everyone shares the same understanding of the audience.
- Keep learning loops short enough that reactions can change the plan before work hardens.
- Treat communication and expectation-setting across remote offices as core project work, not overhead.
A sprint rhythm that protects focus
The rhythm Leinert outlines is a two-week sprint cycle. Meetings are concentrated before lunch to preserve the rest of the day for focused work. Fridays have no stand-up; instead, a weekly walkthrough gives the team a shared view of progress and doubles as a cultural moment.
Use that structure as a decision tool: if a meeting can move to the morning block, move it; if a Friday update can be a walkthrough rather than a status meeting, let people see the work itself. The point is not the clock time alone, but protecting deep work while keeping visibility high.
Sign off in layers to prevent milestone surprises
Features are signed off in four layers: functionality, usability, cosmetics, and love. Each layer has its own acceptance question. Does it work? Can the intended player use it comfortably? Does it look and feel right? Has the final polish that makes the experience memorable been applied?
Checking layers in that order prevents a common failure: a feature that looks finished but has not yet been tested for usability, or one that works but has never received the cosmetic and emotional polish it needs. It also makes milestone reviews clearer, because the team can name exactly which layer is still open.
Adapting traditional project management to a living product
Leinert contrasts traditional project management with leading a product that is never quite done. In a small studio, the project manager can also help shape the vision, but the daily job remains managing expectations and communication. That distinction matters for anyone considering the role: success depends less on enforcing a fixed plan and more on keeping a shared understanding alive as the game evolves.
The episode also covers questions for a game project charter, managing a team while leaving time for strategic planning, keeping communication and culture alive, where game projects drift from plan, deciding when a design is done, and advice for becoming a video game project manager.
Frequently asked questions
What should a game project charter cover?
Start with the intended player experience, not only a feature list. Define the feelings and outcomes the game should create, then test early with people in the target group and let their reactions refine the plan.
How can a team avoid late surprises on a game feature?
Use layered sign-off: first functionality, then usability, then cosmetics, and finally the extra polish described as love. Checking each layer separately reduces late surprises before a milestone.
How can meetings protect focus time?
Protect uninterrupted work by placing meetings before lunch, skipping a Friday stand-up, and using a Friday walkthrough to share progress and reinforce team culture.
When is a game design project done?
Expect ongoing refinement rather than a single finish line. A traditional project manager needs to manage expectations and communication continuously, especially across remote offices, while still shaping the product vision.