A HEALTHY TEAM CAN SHIP THE WRONG GAME.
Team assessment tells you whether a studio can execute. Whether the game is worth executing is a separate question, and Title Review answers it in time for greenlight, the next funding gate, or the slate decision.
What you'll know after this
- Whether the game's core premise has been proven or only asserted
- Whether the plan and the content it requires are the same size
- Which title patterns are present, and whether it's still early enough to fix them
Good milestones, failed launches
Milestone review is built to catch execution problems, and it catches them well. A title can pass every gate on schedule, on budget, and at quality, and still fail on the day it meets its audience. The questions that would have caught it are not necessarily questions about the team.
Signals the title itself is the risk
- The build is competent but nobody can say what makes it worth playing
- Scope has grown since greenlight and nothing has been cut
- The audience thesis hasn't been re-tested since the project started
- Content targets have never been divided by a measured production rate
- The business model requires content the design doesn't or can't produce
What a Title Review checks
- Core premise: whether the fun has been demonstrated or asserted
- Vision integrity: how far the current game has moved from the funded one
- Audience: what incumbent game must the audience leave to play this, and whether that's still true
- Content math: remaining assets against demonstrated rate
- Model fit: whether the design and the business model want the same things
The 5 Title Failure Patterns
Five patterns that predict a title fails at market rather than in production. They're invisible in a milestone build, because a milestone build is designed to show that production is working.
The Unvalidated Core
Fun asserted, never demonstrated
Warning signs:
- The team describes systems and features, not a specific moment
- The slice was hand-built outside the pipeline that has to make the rest
- No unmoderated playtest where a new player kept going without prompting
- “It gets good a few hours in”
What this costs you:
Production doesn’t resolve this. It converts an unproven premise into an expensive one, with content, marketing, and a date attached.
Vision Drift
The game in production is not the game that was funded
Warning signs:
- The pitch has gotten longer with each review rather than sharper
- Features have been added since the last gate; nothing has been removed
- Reference titles quietly changed and nobody noticed
- No record exists of what was decided since greenlight, or by whom
What this costs you:
Marketing sells the funded version and the team ships the drifted one. Afterward it gets diagnosed as a marketing failure.
Audience Fiction
No named player, or the player is the team
Warning signs:
- Comparisons are only to outlier successes, never to failures in the category
- Positioning is a genre and a setting, not a compelling reason to switch
- “There’s nothing else like it” offered as a strength
- The audience thesis was validated once, years ago, in a different market
What this costs you:
You lose the whole investment at launch, and no amount of marketing can rescue it.
Content Math Failure
A scope nobody has divided
Warning signs:
- The content plan is stated in hours of gameplay, not units of production
- No measured rate exists from finished, shipped-quality work
- Per-unit cost is assumed to fall later, once the tools land
- The final third is budgeted at the same cost as the first
What this costs you:
You get a strong opening and a thin back half, or the schedule absorbs the gap and the budget goes with it.
Model and Design at War
The design can't produce what the business model needs
Warning signs:
- The retention plan needs content the design doesn’t naturally produce
- Monetization surfaces with no design owner
- A post-launch roadmap that assumes a live team nobody has staffed or budgeted
- Platform or pricing assumptions changed since greenlight and the case was never re-run
What this costs you:
You fund a game that is simultaneously a weak single-player experience and a weak live one.
Three of the five are only visible as changes over time, so a single review will miss them where a comparison against the last two reviews will not.
When each pattern is cheapest to catch
| Stage | Pattern | What settles it |
|---|---|---|
| Concept / greenlight | Audience Fiction, Model Conflict | A named incumbent game that the player leaves, and why |
| First playable | Unvalidated Core | Unmoderated play, with a new player continuing unprompted |
| Vertical slice | Content Math | A measured rate on real, shipped-quality work |
| Production | Vision Drift | A diff against the last two reviews, and a list of cuts with owners |
| Alpha | Content Math (confirm) | Remaining units ÷ demonstrated rate, against the calendar |
| Beta / pre-launch | Audience Fiction (retest) | External playtest retention: D1, D7, session length |
Every one of these is cheapest to detect before the stage where it usually gets discovered, and that gap is where the value of the review sits.
What is a Title Review?
A short, structured read on a single title, scoped to the decision in front of you. I review what the project has produced, play what exists and if possible organize a playtest, and talk to the people making it. What “on track” means depends on stage, genre, and studio, so every question is calibrated to all three. Each engagement is a fixed fee agreed before kickoff.
Materials
Pitch and pillars, current plan and budget, milestone history, playtest and user research results, and the last two reviews where they exist.
Play
If possible, organize a structured playtest; I also play the build the way a player would, not the way a demo is guided. Where there's no build yet, I read what stands in for it.
Assessment
Which patterns are present, whether it's still early enough to correct them, and a recommendation framed for the decision you're making.
When publishers bring me in
The same review supports four different decisions.
At a greenlight gate
A build review shows what the team prepared. A title review asks whether the game underneath it justifies the production budget that follows.
Before signing an external title
An independent read on the pitch itself, alongside your legal and financial diligence. The cheapest possible point to find an audience problem.
Portfolio review
Several titles assessed against the same framework, so the comparison between them means something.
When the model changes
A platform, pricing, or portfolio decision made above the project rewrites its business case. Someone has to re-open the question without it reading as the team's failure.
How it works
Three steps, sized to fit inside a normal review cycle.
Kickoff
We agree the decision you’re making and the questions you need answered. I review materials in advance: plan, budget, milestone history, research results, prior reviews.
Duration: 1-2 days
Review
Time with the build and with the team. Play sessions, working conversations with leads and with people who didn’t prepare for me, and a read of the production data against what the plan assumes.
Duration: 2-5 days, on-site or remote
Synthesis and Recommendation
Which patterns are present, how far each has run, and what correcting them would take at this stage. You receive a written report with a decision-ready recommendation of proceed, pass, or proceed with conditions, followed by a debrief call.
Duration: 1 week
Total Timeline: 1-3 weeks from kickoff to final report
Short enough to sit inside a review cycle, thorough enough to change a decision.
The report
- 1Executive Summary: proceed / pass / proceed with conditions
- 2Pattern Analysis: which of the five are present, and how far each has run
- 3Stage Calibration: what should be true by now, and what isn’t
- 4Evidence: the playtest data, production rates, and build observations behind each finding
- 5Recommendation: framed for the decision in front of you, with what would have to change
The other half of the read
Title Review tells you whether the game is worth executing. It doesn't tell you whether this team can execute it. Studio Assessment covers the second question.
Common questions
The question a milestone build can't answer.
Greenlight, continue-or-stop, and slate decisions all improve with an independent read on the title itself. You get a decision-ready report inside a normal review cycle.
Confidential consultations with no obligation. All engagement details treated as confidential. NDA available upon request.