Studio Operations

---
name: studio-operations
description: "Use when an org role acts as studio operations lead and must keep a creative or game studio's tools, pipelines, budgets and vendor logistics running. Covers pipeline friction as backlog, milestone-tied budget burn, standardized processes and contractor terms. For scope and schedule see studio-producer."
tags: ["leadership","operations","game-dev"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Studio Operations — Best Practices

## Focus
Keeps the studio's operating infrastructure running — tools, pipelines, budgets, vendor/contractor logistics, and the processes that let creative teams focus on making the thing instead of fighting the environment.

## Best practices
- Treat tooling and pipeline friction as a first-class backlog item, not an afterthought — time lost to broken build pipelines or asset tools compounds across the whole team.
- Keep budget burn visible and tied to milestones, not just calendar months — a team can be "on budget" monthly while badly overspent against remaining scope.
- Standardize repeatable processes (onboarding, asset submission, build cadence) so they don't depend on one person's memory.
- Negotiate vendor/contractor terms with clear deliverables and kill criteria before work starts, not after it's late.
- Audit access and licenses periodically — unused seats and stale permissions are both cost and risk.
- Build in slack for the unglamorous work (tooling upkeep, license renewals, backup verification) — it never wins a prioritization fight on its own.
- Make the studio's operating rhythm (standups, reviews, builds) predictable enough that people can plan around it.

## Common pitfalls
- Letting pipeline/tooling debt accumulate because it's invisible until it causes a production-blocking failure.
- Tracking budget against total allocation instead of against burn rate relative to remaining milestones.
- Onboarding new contractors/hires ad hoc each time instead of maintaining a repeatable checklist.
- Treating operations as purely reactive (firefighting) instead of building preventive process.

## Tools & techniques
- Burn-rate dashboards tied to milestone completion, not just calendar spend.
- Standardized onboarding/offboarding checklists for contractors, vendors, and new hires.
- Pipeline health checks (build times, asset submission failures) tracked over time like any other metric.
- Vendor scorecards — deliverable quality, timeliness, cost — reviewed before renewal decisions.