Your Studio in 3 Numbers (Be Brutally Honest)
Hey All!
Imagine this:
Youâre leading a team of devs. Maybe thereâs 5 of you. Maybe thereâs 200.
Everyoneâs busy. Jira is full. Slack is on fire.
But if youâre honest⌠the game isnât really moving.
Iâve seen this pattern over and over in game studios.
From the outside everything looks funded, staffed, and âproductive.â
On the inside, leaders are stuck in planning, teams are shipping assets into a void, and morale is quietly tanking.
Hereâs the uncomfortable truth:
Itâs not because your team isnât working hard.
Itâs because you, as a leader, are fighting the wrong problems.
â
The 3 numbers that quietly predict success
Grab a notepad and rate your studio on three things, 1 to 5:
1. Vision
2. Scale
3. Workload
How to rate yourself:
1ď¸âŁ Vision (1-5)
Ask: âDo we really share the same game in our heads?â
1: If you ask 5 people âwhat game are we making?â you get 5 totally different answers.
5: People across disciplines can describe the same core experience, who itâs for, and why players will love it.
If your team doesn't share a north star, any âvelocityâ you see is fake. Youâre just scattering effort.
â
2ď¸âŁ Scale (1-5)
Ask: âHave we earned the right to be this big yet?â
1: Tech foundations and tools are not working well AND/OR we arenât able to align a team this size to the same vision AND/OR the game experience doesnât match our stated phase of development (the game wins here AND/OR the systems and processes we use are not supporting the scale of the team
5: Tech, tools, alignment, actual game experience, and work systems are solid enough that adding people actually speeds you up instead of bogging you down.
Headcount doesnât fix broken foundations. It amplifies them.
If your systems are weak, every hire multiplies confusion.
â
3ď¸âŁ Workload (1-5)
Ask: âCould we keep working like this for a year?â
1: Nights, weekends, crunch âjust through this milestoneâ forever. People are exhausted, but it seems necessary and anyway, how would we manage without it?
5: Sustainable pace. People know when to stop. You could run this way long-term without burning anyone out.
The trap with overwork is that it feels necessary and heroicâŚ
âŚbut after a few weeks, the data is clear: youâre actually going slower than if you never crunched.
â
What your lowest number is trying to tell you
Look at your three scores for Vision, Scale, and Workload.
Circle the lowest one.
Thatâs what you need to start addressing right now.
These problems donât go away or solve themselves as you keep going.
They get worse.
- If Vision is lowest, no amount of sprint planning, reports, or extra people will save you. You need painful alignment conversations, not more tasks.
- If Scale is lowest, youâve probably hired past your foundations. You donât need âmore bodies,â you need a small strike team to fix core tools, the game itself, or processes.
- If Workload is lowest, your team is paying with their health and focus. Youâll ship more by slowing down, prioritizing brutally, and actually cutting scope.
Those three numbers will tell you way more about your future ship date than any burndown chart.
â
If this hit a little too close to home, youâre exactly who I recorded this weekâs episode for.
On our recent episode, I break down:
- The 3 leadership mistakes quietly crippling game studios
- How to tell if âfake progressâ is happening on your team
- What to do if youâve already over-hired
- Why crunch almost always makes you slower (with data, not vibes)
- How to actually use this Vision/Scale/Workload check
Listen to: â3 Leadership Mistakes Quietly Crippling Your Game Studioâ
https://urlgeni.us/youtube/fyZC4l
Respectfully,
Ben C.
P.S.
If you want to solve problems like vision, scale, and workload as well as many others, Iâve recently created a Game Dev Leadership Accelerator. Itâs for leaders who feel stuck, unable to have the positive impact they desire. But that impact is possible, and you can be the one to bring it to your team and game.
If thatâs of interest, sign up here and weâll reach out to see if the Accelerator is a fit: https://forms.gle/nqRTUvgFrtdYuCbr6
Responses