Ali Durrant wearing a raised VR headset, beside another person seated at a computer workstation.
Ali Durrant

Build stronger production capability across your studio.

Practical training and implementation support for production teams that need clearer systems, stronger judgement and more consistent delivery.

Discuss your studio

Where production starts to break down

We help studios change the conditions behind recurring production problems—not just add another process.

Four recurring studio production conditions linked to practical changes: shared habits, stronger foundations, decision-ready reporting and earlier escalation.

How the work happens

Every engagement is adapted to the studio, but the work follows a clear path from diagnosis to adoption.

A four-stage studio growth path: diagnose capability gaps, design the right intervention, deliver practical learning and embed the change.
  1. Diagnose. Clarify the studio context, audience and most important capability gaps.
  2. Design. Select or adapt modules, delivery format and practical exercises.
  3. Deliver. Facilitate learning using studio-relevant examples and tools.
  4. Embed. Support adoption through follow-up, implementation guidance or advisory input.

The work should leave something useful behind.

Depending on the engagement, that may be a shared model of the problem, a decision map, workshop outputs, reusable production tools or a clearer operating approach—not just a slide deck.

Studio Risk Foundations · Academy training examples

Worked course examples, not client work or client outcomes.

13 / Worked example

Leadership Risk Roll-Up

Decision-ready one-page example showing patterns, threshold breaches, and leadership choices.

Backend / live ops

Shared backend constraint now threatens two committed beats

Threshold / appetite
Threshold crossed
Decision required
Approve capacity shift and resequence one beat
Owner
Production Director
Due / review
29 Mar 2026

Tech art / outsource

Shader validation gap is still driving vendor rework

Threshold / appetite
Near threshold
Decision required
Approve stricter acceptance gate and backup trigger
Owner
Tech Art Director
Due / review
02 Apr 2026

Release / QA / community

Launch readiness remains exposed if rehearsal cover stays thin

Threshold / appetite
Low appetite: player trust
Decision required
Keep rehearsal and confirm support rota
Owner
LiveOps Lead
Due / review
05 Apr 2026

Selected fields · example review dates retained from the source.

21 / Worked example

Risk Culture Charter and Working Agreement

Short behavioural agreement for raising concerns, responding seriously, and closing the loop.

  1. Raise early

    Team leads bring threshold signals within one working day.

  2. Challenge safely

    Calibration meetings use anchors and evidence.

  3. Record the decision

    All gate outcomes receive a decision record reference.

  4. Follow through visibly

    Top actions are linked to backlog items and checkpoints.

  5. Escalate clearly

    Escalation note sent within two hours of incident trigger.

  6. Learn and carry forward

    Post-incident actions are reviewed at the next programme review.

Selected fields · working rules and how they show up in practice.

Portrait of Callum Godfrey.
Callum Godfrey
“Liam is all about ensuring teams have the skills and support they need to define their own futures.”
Callum Godfrey · Compass Head of Studio, nDreams

Tell us what your teams need to do more confidently or consistently.

We will recommend an appropriate programme, workshop or implementation route.

Discuss your studio