Milestones
Name the current ship. Date a gate when the playtest is real, or park it. Hand refill can follow the current milestone so the day stays honest.
Studio planning
Unity project management: cycles, guilds, and decks
Studio planning for Unity teams: how guilds, decks, and cycles frame the work before anyone draws a Hand. This is not the Unity product lander, and it is not a daily-task or tool-comparison guide.
The studio frame
Guilds, milestones, decks, then Hand. Same charcoal cards as every other long-form page.
Guilds and seats
A guild is the studio container: boards, roles, and paid seats. Start free. Solo Pro and Team when the cap matters.
Learn more
Kanban and decks
Decks, cards, and lanes you actually use: features, bugs, polish, spikes. Filter by milestone without cloning a 40-field issue type forest.
My Hand
A small active set with a real WIP cap. Pull a few cards, ship them, then draw again. The rest of the board stays visible and quiet.
Learn more
Plan the studio, then plan the day
Unity project management is the shape of the workspace: who is in the guild, which decks exist, and which cycle is current. Daily tasks sit inside that shape. If you only tune WIP and never name decks or a current gate, every card fights every other card for attention. If you only draw org charts and never pull a Hand, the plan never becomes a build.
Guilds as the studio container
A guild is the team that shares boards, seats, and permissions. One Unity project can be one guild. A wider studio can split products or disciplines if the workstreams should not share a backlog. Keep the count small. Extra guilds create extra Hand rituals and extra Discord mappings.
Decks instead of a single infinite board
Decks are how Brainloot groups work (features, bugs, content, engines). Unity teams usually need a production deck, a bugs deck, and a place for spikes or polish. Do not clone a Jira issue-type forest on day one. Add a deck when a filter becomes a daily argument, not when someone likes a new column name.
Cycles as the current ship
Cycles (milestones) let the board show the current gate without deleting the rest of the backlog. Date them when a playtest or store build is real. Park them when the work is still a pile. Hand refill can follow the current cycle so makers do not pull vertical slice and live-ops cleanup in the same five cards.
Where this page is not pointing
For the editor companion and Scene pins product story, use the Unity lander. For Hand, Focus, and Discord as a daily loop, use game-dev task management. For Codecks, HacknPlan, Jira, and scene notes as a shopping list, use Unity task management tools. For guild Discord mappings and /bug intake, use Discord in the loop.
FAQ
- How is Unity project management different from daily task management?
- Project management is the studio frame: who is in the guild, which decks exist, and which cycle or milestone is current. Daily task management is the Hand you pull inside that frame. Mixing them turns every stand-up into a re-org.
- What are cycles, guilds, and decks in Brainloot?
- A guild is the studio or product team. Decks are lanes of work (features, bugs, content) on the board. Cycles (milestones) are time-boxed or parked gates so the board can filter to the current ship without deleting the backlog.
- Should I use this page or the Unity task management guide?
- Use this page to design the studio plan. Use the Unity task management guide when you are comparing Brainloot, Codecks, HacknPlan, Jira, and scene notes as tools. Use the Unity lander when you want the product story for the editor companion.
- Can a small Unity crew skip cycles?
- Yes. A solo or tiny team can live in one guild, a few decks, and a Hand. Add a current cycle when you need a shared "this milestone" filter for playtests or a publisher build.
Related
Ready to level up your workflow?
Start free, pull a few cards into My Hand, and ship from one studio board.