Build Day · Formats

You pick the format. I show up with your content already in it.

Build Day is a live session where your team’s real training becomes a working game. The part that makes it work is that we do not start from a blank page. You choose one of three proven formats when you book, send me your content, and we spend the day making it yours.

How it works

Three steps, and only one of them is the day itself.

Step 1 · At booking

Choose a format

Pick the game shape that fits the behaviour you are training. Each one already exists, already works, and has been used with real learners.

Step 2 · A week ahead

Send your content

Your scenario, your policy, your document, your questions. Whatever shape it is in. I build your material into the format before we meet.

Step 3 · The day

We make it yours

You see your own content running in the first ten minutes, then we shape it together. You direct, I drive, and it is finished when we finish.

This is the difference between a Build Day and a demo. Nobody watches me invent a game from nothing, which would be a slow morning and a nervous afternoon. You watch your own training become playable and then spend the time on the decisions that actually matter.

The formats

Three shapes, chosen for what they teach.

Pick by the behaviour you want people to practise, not by which looks the most fun. I will tell you honestly if your content fits a different one better.

Format 01 · Timed run

2-D platformer

A character runs through a world under time pressure, dodging hazards and collecting what matters. Learners spot something wrong at the start, then race to act on it.

Best for: urgency, prioritisation, and consequence. Anything where the lesson is that hesitating costs you something.

Proven on: phishing awareness and PHI handling, most recently with a live room of sixty in August 2026.

You choose
  • The scenario and what goes wrong
  • The setting and backdrop
  • Your character, from six, or your own
  • Every line of dialogue
  • What the hazards represent
  • The win and lose endings
Format 02 · Find the problem

Document review

A realistic document appears on screen and learners click what is wrong with it. An email, a form, a contract, a chart, a report. Getting it wrong explains why, rather than just marking it red.

Best for: compliance, quality control, and judgement calls. Anything where the skill is noticing.

Proven on: redaction and PHI review, and phishing email inspection.

You choose
  • The document, from yours
  • What counts as a problem
  • The feedback for each miss
  • Flag it or redact it
  • How forgiving the scoring is
  • What happens when they finish
Format 03 · Arcade recall

Question-driven arcade game

A familiar arcade game with your questions built into the play. Answer to advance, clear levels, beat a score. The game carries the repetition so the questions do not feel like a quiz.

Best for: knowledge that needs repeating until it sticks. Onboarding, product facts, terminology, annual refreshers.

Proven on: several titles shipped as portable web objects and running inside Storyline and Rise courses today.

You choose
  • Which arcade game
  • Your questions and answers
  • Feedback for each wrong answer
  • Difficulty and pacing
  • Your colours and branding
  • Where it gets published

The guardrails

What is fixed, and what is yours.

The fixed half is what makes a single day enough. The mechanics already work, so none of the day is spent making a game function. All of it is spent on what the game teaches.

Fixed

  • The game mechanics and how it plays
  • The overall structure and flow
  • Roughly how long a round takes
  • That it runs in a browser with no install
  • That it works on its own or inside your LMS

Yours

  • All the content, wording and scenarios
  • Characters, setting and artwork
  • Colours, logo and branding
  • Feedback, scoring and endings
  • Difficulty and how forgiving it is

How you get it

Packaged for wherever it needs to live.

You pick this at booking, because it changes how I build it. All three are things I ship already, not experiments.

For your LMS

SCORM package

A zip you upload like any other course, reporting completion and score back to your LMS. SCORM 1.2 by default, which is the most widely supported. 2004 on request.

For Storyline or Rise

Web object

A folder you insert straight into a course you are already building, so the game is one activity inside your module rather than a separate thing to launch.

For everywhere else

A hosted link

I publish it and you get a URL to share, embed in your intranet, or drop in a message. No LMS involved, works on a phone.

If it is going into an LMS, we upload and launch it together before the day ends. Ten minutes then beats finding out three weeks later that it will not open.

If you want to keep building

The version where you do not need me again.

A standard Build Day ends with a finished game that is yours. This adds the part that decides whether there is a second one: the source it was built from, and a team that can change it without calling me.

You get the source

The repo, not just the export

The whole project, not the packaged output. New questions, changed copy, a different scenario, swapped art — all of it is editable, because you have the thing it was made from.

Your team learns it

A working session on your build

Not a generic tutorial. We change your game together: rewrite a question, adjust the difficulty, swap a character, republish it. Everyone does it once themselves, on the thing they will actually maintain.

You can see it working

Tracking, and a view you own

We set up what gets reported and confirm it lands in your LMS. If you want more than completion and score, we build a simple view of how people are actually playing — where they quit, what they retry — and you host it. No login of mine to depend on.

Someone goes further

Seats in the Academy

For the person on your team who wants to build the next one from nothing rather than edit this one. Six weeks, live, with the same tools I use.

From $5,000. Priced per team, because it moves with how many people are in the working session and how many Academy seats you want. Tell me both and I will give you a number, not a range.

Before the day

What I need from you, and when.

None of this needs to be polished. Rough notes and an existing deck are enough. Send it a week out so your content is already running when we start.

Which format? One of the three above. If you are torn, tell me the behaviour you are training and I will pick.
What should change? One sentence on what people should do differently afterwards. This shapes everything else.
Who is playing? Role, how much they already know, and whether this is new learning or a refresher.
Your raw content The policy, deck, document, scenario or question bank. Whatever exists, in whatever state.
Anything that must be exact Regulated wording, legal phrasing, or terminology that cannot be paraphrased.
Brand assets Logo, colours, fonts. Optional, and I can work without them.
Where it will live A link, your LMS, Storyline, Rise, or your intranet. This decides how I package it.

Your training, playable, by the end of the day.

Tell me what you are trying to teach and I will tell you which format fits, honestly, including if the answer is that a Build Day is not what you need.

Book a call See all workshops