Flagship · 11 weeks

Locale Scorecard Lab

Build a weekly picture of localisation health that a release manager can scan without a translator in the room to interpret it.

Dashboard with multiple performance charts

What you leave with

A living scorecard (spreadsheet or BI view — your choice) covering time-to-locale, remaining volume, LQA sample health, cost per accepted string, and an exception log. You also leave with a written gate definition aligned to your train, not to a generic “green / amber / red” poster.

We do not promise a plug-in for every TMS. If your export cannot name a locale, a timestamp, and a status, the first week is spent cleaning that pipe — which is honest work, not a hidden extra.

Modules

  1. Week 1–2 · Inventory that tells the truth. Map fields from CAT/TMS/Jira. Drop vanity columns. Name the unit you will actually manage (string, job, or screenshot set).
  2. Week 3–4 · Time-to-locale. Clock from freeze to accepted locale. Handle weekends, vendor holidays, and in-house review queues without double counting.
  3. Week 5–6 · Quality samples without flattery. Design a random LQA draw. Record severity without turning every preference into a blocker.
  4. Week 7–8 · Cost and rewind. Attach a simple cost model. Track rewinds as a performance leak rather than a moral failure.
  5. Week 9–10 · The gate. Write the rule your train will live with. Pressure-test it against last quarter’s near-misses.
  6. Week 11 · The four-minute review. Rehearse the weekly readout. Cut anything a product owner has to ask you to explain twice.
Portrait of Nia Calder

Instructor

Nia Calder ran localisation operations for a FTSE consumer brand before founding the studio in Eggerness. She still reviews alumni scorecards twice a year and refuses dashboards that cannot survive a stolen laptop and a CSV.

Informational fee

The public lab seat is listed at £1,180 for one participant, including templates and eleven live sessions. See Fees for neighbouring options. No checkout on this site.

A limitation you should know

The lab will not teach you to implement a TMS, hire linguists, or rewrite your engineering freeze policy. If engineering will not emit a timestamp, we can design around it — we cannot invent the timestamp.

Questions we hear

Do I need a BI tool?

No. Many cohorts finish in a disciplined spreadsheet. If you already live in Looker or Power BI, we will not force you back to cells.

Can two people from one company join?

Yes. We prefer a localisation owner plus someone who can export data. Fees remain per seat unless you book a Residency Block.

What if our languages are mostly machine-translated?

Then rewind rate and post-edit time become the interesting columns. We do not pretend MT removes the need for a gate.

Is there a certificate?

We issue a letter of completion. It is not a regulated qualification in the United Kingdom.

From people who sat the lab

Module six’s rewind column made our “cheap” vendor look expensive. We kept them for two pairs and moved the rest. That was not in the brochure; it was in the numbers.

Jonah Adeyemi, programme manager · Bristol

★★★★★★★★☆☆

Clear on gates. Dry on humour. I still open the week-11 script every Monday.

Platform review · 8/10

Ask about the next cohort