At Raion Games we shipped five titles with a cross-functional team of seven - developers, artists, designers, and QA. People sometimes hear that and assume the trick was working everyone to the bone. It was closer to the opposite. The only way a small team ships repeatedly is by being ruthless about scope and gentle with the people.
I led production across the lifecycle, concept to completion, and the recurring lesson was that finishing is a skill you practice, not a heroic sprint at the end.
Scope is the lever, every time
With seven people you cannot do everything, so the real job is deciding what not to do. For each title we got clear on the core - the thing that had to be great - and protected it, then cut hard around it. A smaller game that ships and feels finished beats an ambitious one that never crosses the line. Saying no to good ideas was most of the work.
A small team does not ship more by working more. It ships more by carrying less per title.
The team is the asset, so protect it
Five titles only happens if the same seven people are still there and still want to be. Burning out the team to hit one deadline costs you the next four games. So I tried to keep the pace sustainable, the milestones realistic, and the wins visible. People do their best work when they are not running on empty.
What shipping five times with a small team taught me:
- Define the core of each title and defend it. Cut everything that is not it.
- Treat finishing as a habit, not a final heroic push.
- Keep milestones honest, so the team trusts the plan.
- Protect the people. They are the thing that ships the next game, and the one after.
The investment we raised and the titles we shipped were real wins, but the one I am quietly proudest of is that we did it without grinding the team into the ground.