The Burnout Factory
For their previous three titles, Ironwood Studios relied on a brutal, industry-standard methodology for shipping games: the six-month crunch. During the final push, 60-hour weeks were quietly expected, dinners were catered to keep people at their desks, and "passion" was used as a metric for performance.
The human cost was devastating. Following the release of their tactical RPG *Ironwood Tactics*, 35% of their senior engineering and design staff resigned within three months, citing severe clinical burnout. "We shipped the game, but we broke the studio," admitted the Studio Head.
Transitioning to Sustainable Sprints
Determined to survive their next ambitious project, the studio radically structurally overhauled how they worked. They threw out their rigid, top-down Jira waterfall charts and implemented Lobbi's Agile Suite, focusing entirely on a new core metric: Sustainable Velocity.
A mandate was issued: no developer was permitted to log more than 40 hours a week. Instead of relying on brute force to hit arbitrary dates, production was forced to actually scope the game to match the mathematical output of a rested, healthy team.
Velocity Tracking with Lobbi
Ironwood heavily utilized Lobbi's intelligent Sprint burn-down charts. Rather than a producer simply guessing how long a feature would take, Lobbi tracked the exact historical average time it took a specific pod (e.g., UI Team) to complete a 5-point task.
Velocity vs. Hours Worked
If a producer attempted to load 60 points of work into a sprint for a pod that historically generated 45 points, Lobbi's AI immediately flagged the sprint as "Unsustainable" in bright red. The tool literally mathematically disabled the producer's ability to silently mandate crunch.
Empowering the Developer
Furthermore, developers were empowered to push back. If a designer encountered an unexpected physics bug that tripled the estimated time of their task, they updated the multiplier in Lobbi. The system automatically adjusted the downstream schedule, visually showing the producer exactly which features had to be cut from the milestone to accommodate the reality of game development.
The "Blame" shifted away from the developer for "working too slowly," and rested correctly on the producer for "failing to adjust scope."
A 0% Turnover Year
By treating velocity as a hard scientific metric rather than an emotional goal, Ironwood Studios shipped *Ironwood II* to stellar reviews. Crucially, they worked precisely zero weekends during the final 4-month beta phase.
Most importantly, they achieved an unheard-of 0% voluntary turnover rate following the game's launch, preserving their immensely valuable institutional knowledge for exactly their next title.