Sylvaine Droet has produced mobile platform games for studios ranging from eight people to over 80. She joined us to talk about what team structures actually hold up under production pressure, especially for businesses that are newer to game development.
The role businesses most often skip
A dedicated QA lead, not just testers, but someone who owns the bug pipeline and communicates directly with design. Without that role, bug reports pile up in spreadsheets that nobody has time to read during crunch.
Sylvaine has seen projects delayed by six weeks because a critical input bug was logged but never triaged. The fix itself took two days. The delay came from the reporting gap.
A QA lead costs less per month than one week of a delayed launch. The math is straightforward, but it is still an argument I have to make regularly.
Designer-to-developer ratio matters for platform games specifically
Platform games are level-design-heavy. Sylvaine recommends at least one level designer for every two developers on a project of this type. If that ratio is off, developers end up making level decisions they are not positioned to make well, and it shows in playtesting.
When to bring in an outsourced art team
Art outsourcing works well for background assets and tilesets, where style guides can be followed without constant creative feedback. It does not work well for character animation, where feel and timing require close iteration with the gameplay team.
Sylvaine draws a clear line between what can go external and what needs to stay in-house. Getting that boundary wrong adds revision cycles that eat into the schedule more than the outsourcing saved in cost.
Businesses entering this space often underestimate how much game development is coordination work, not just production.