Everything a studio runs on
Seven areas follow the game from its first idea to the studio that ships the next one. Three foundations hold them together.
The lifecycle
Make the game
Plan Plan & produce Milestones, sprints, budget and goals, with the scope always in view. Make Wiki & docs The design, the lore and the decisions, kept current and answered with sources. Review Review Frame notes on a cut, a pose on a rig, a mix on a sound graph. Test Bugs & QA Bugs that know their build, crashes that file themselves. Ship Builds & release From a commit to a build, a store page and a release. Grow Marketing & Insights Campaigns, posts and the numbers that come back. Run the studio Run the studio Hiring, people, leave and reviews, and the money to make the next game.
The foundations
Under it all
Why one app
Shared, not stitched together
- One set of people The studio's people, roles, teams and outside companies, the same in every area.
- One set of permissions Access groups decide what each person sees in the wiki, the board, the builds and HR alike.
- One set of data A bug points at its build, a version at its task, a post at its campaign, a key result at its milestone.
- One assistant It reads across all of it, so its answers and drafts know the whole studio.