Keep your game dependable after launch.

Game brief

A concise definition of the game objective, current state, audience, constraints, and decisions that shape this engagement.

• The game objective and owner are named.
• Known constraints and unresolved assumptions are recorded.

Operating work

The recurring management or maintenance work required to keep the game stable, current, and useful.

• The agreed game scope is complete.
• The output has been checked against the primary game outcome.

Review record

A visible record of feedback, decisions, checks, and accepted limitations for the game.

• The agreed review checkpoint is complete.
• Open decisions are separated from accepted scope.

Operating log

A practical log of game changes, observations, incidents, and recommended next actions.

• Ownership and next actions are clear.
• Relevant files, links, and decisions are accessible.

01 / Establish the baseline

Confirm what the game must accomplish, what already exists, and which constraints cannot move.

02 / Run the operating rhythm

Maintain the game against the agreed reliability, compatibility, and change expectations.

03 / Monitor changes and risk

Review the game against its intended audience, critical use cases, and agreed success signals.

04 / Record improvements and next actions

Close the game cycle with accepted decisions, documented limits, and the next useful action.