Production Health Check — An established studio that needs to scale, stabilize, or ship live

Predictability is the real margin: studios lose money on surprises, not on ambition.

This is a maturity assessment, not a checklist. Every statement is scored against four anchors describing what each score actually looks like, because without them everyone scores themselves a two. Answer from what happened last quarter rather than from what is supposed to happen. The result names your two weakest dimensions and what usually sits underneath them.

How to score this honestly

Score the studio as it behaved under pressure, not as it behaves when things are calm. If a process exists but was abandoned during the last crunch, it scores a one. The anchors are written so that the flattering answer and the true answer are different sentences — if you find yourself reading past an anchor to reach a higher number, that is the finding.

0 / 14statements scored

01 · Release cadence

How often you ship, how predictable it is, and whether the interval was chosen or inherited.

The last three releases went out on the date announced internally at the start.

0Absent. Dates move so often the announced date is not treated as information.1Ad hoc. One of the last three held; slips are announced in the final week.2Consistent. Two of three held, and slips were flagged with more than two weeks' notice.3Engineered. All three held, or moved once with a stated reason more than a month out.

What it costs: A slip discovered inside two weeks costs the marketing spend already committed against the original date, typically the largest single avoidable write-off in a release.

Shipping a release costs a known and shrinking number of person-days.

0Absent. Nobody has measured it. The answer is "it takes as long as it takes."1Ad hoc. People could estimate it, roughly, and it has not changed in a year.2Consistent. It is measured, and the number is known to the team.3Engineered. It is measured and has come down over the last three releases.

What it costs: A manual release process typically consumes three to eight person-days per cycle, which at a monthly cadence is most of a full-time engineer spent on the same steps forever.

02 · Milestone truth

Whether reported status matches reality, and how long a slip takes to become visible to leadership.

A slip reaches leadership within a week of the team knowing.

0Absent. Leadership learns at the milestone review, on the day.1Ad hoc. It surfaces within a month, usually through a side channel.2Consistent. It surfaces within two weeks, through the normal reporting line.3Engineered. Within a week, and the report names the date it was first known.

What it costs: Every week a slip stays invisible is a week of dependent work built on a false date, and that rework is typically two to three times the original delay.

A task reported green in the last month later turned out not to be.

0Absent. This happens most months and nobody treats green as meaningful.1Ad hoc. It happens, and it is treated as an individual failing rather than a system one.2Consistent. It is rare, and when it happens the reporting path gets examined.3Engineered. Rare, examined, and the examination has changed how status is collected.

What it costs: Status that cannot be trusted means leadership re-verifies manually, which is one to two senior days a week spent re-deriving what the report already claimed.

03 · Telemetry that produces decisions

Not whether dashboards exist. Whether anyone changed a decision because of one in the last quarter.

A decision changed in the last quarter because of something in the data.

0Absent. No example exists.1Ad hoc. One example, and it was a decision nobody disagreed with anyway.2Consistent. A clear example where the data contradicted an assumption and won.3Engineered. Several, and reversing a plan on evidence is unremarkable here.

What it costs: Telemetry that changes nothing is pure cost — typically an engineer's time to build plus a monthly platform bill, returning zero.

New instrumentation starts from a question someone wants answered.

0Absent. Events are added because they are easy to add.1Ad hoc. Added in bulk, at the start, in case they are useful later.2Consistent. Usually tied to a stated question.3Engineered. Always, and instrumentation with no question is removed.

What it costs: Event bloat raises the pipeline bill and slows every query against it, and the cost scales with players rather than with usefulness.

04 · Scope and change control

Whether a scope change has a visible cost at the moment it is made.

Adding scope produces a stated cost in the same conversation.

0Absent. Scope is added in conversation and absorbed silently.1Ad hoc. The cost is worked out later, sometimes.2Consistent. A cost is stated within a few days.3Engineered. Nothing is added without naming what moves or comes out.

What it costs: Silent absorption is how a team arrives three months late having said yes twelve times, each of which looked like a week.

When something goes in, something identifiable comes out.

0Absent. Nothing ever comes out.1Ad hoc. Things come out only when the deadline forces it.2Consistent. Trades are made deliberately, most of the time.3Engineered. The trade is explicit and recorded every time.

What it costs: A backlog that only grows converts directly into overtime, and overtime converts into the attrition that costs three to six months per departure to replace.

05 · Decision rights

Whether it is clear who decides what, and whether that survived the last time headcount grew.

For a contested call last quarter, everyone would name the same decider.

0Absent. Different people would name different deciders.1Ad hoc. Most would name the same person, and it is the founder for everything.2Consistent. Clear for the main areas, ambiguous at the edges.3Engineered. Clear, written down, and matches what actually happened.

What it costs: Ambiguous ownership adds one to three weeks to any contested decision, spent entirely in meetings about who should decide.

Work does not stop when the founder or studio head is away for two weeks.

0Absent. Most decisions wait for their return.1Ad hoc. Some things wait; the team works around the rest.2Consistent. Little waits, and what does is genuinely their call.3Engineered. Nothing waits that should not.

What it costs: A two-week absence that stalls decisions costs the whole team's throughput for those two weeks, not just the one person's.

06 · Technical risk

Whether the upgrade and the roadmap compete for the same people, and whether anyone has priced that.

The cost of the next engine or platform upgrade has been estimated.

0Absent. Not estimated. It is discussed as something that will need doing.1Ad hoc. A rough number exists in someone's head.2Consistent. Estimated and written down.3Engineered. Estimated, written down, and scheduled against the roadmap.

What it costs: An unplanned major upgrade absorbs two to four months of senior engineering, and it lands when the platform forces it rather than when the roadmap can afford it.

It is known which people the upgrade and the roadmap both need.

0Absent. The conflict has not been named.1Ad hoc. Everyone knows informally and it has never been stated.2Consistent. Named, and the trade is discussed.3Engineered. Named, and the trade has been explicitly decided by someone with the authority to.

What it costs: Two efforts sharing three senior people means both run at roughly half speed while appearing fully staffed on a plan.

0 of 14

Your production profile

The link holds your scores and nothing else. Share it with your leadership team — the disagreement about which dimension is weakest is usually more useful than the score.

01 · Release cadence

02 · Milestone truth

03 · Telemetry that produces decisions

04 · Scope and change control

05 · Decision rights

06 · Technical risk

07 · Live operations

Your production profile