Tyler Locke
Learning experience designer and interactive developer. I take the operations a business actually runs on — billing, patient access, contact centre workflows, onboarding — and turn them into something a room of people can practise, not just sit through.

Not slide decks about the thing. HTML, CSS and JavaScript, alongside Captivate and Articulate 360.
Drafting, prototyping, content cleanup, scenario generation. The judgement about what a room needs is still mine.
Unreliable wifi, locked-down laptops, people who have been sitting since nine. Those are the constraints.
Method
Time with the people who do the job, and the SMEs who know why it is done that way. Most of what matters is not in the process document.
Where new starters stall, where experienced people quietly work around the system. That is the curriculum.
A scenario, a game, a simulation — something with a wrong answer in it. Reading about a workflow is not the same as running one.
Track readiness and where people struggle, and revise. The first version is a draft with an audience.
Corporate training rooms have unreliable internet and locked-down laptops. A tool that needs an account, a licence or a login is a tool you cannot use on the day it matters — and I have watched that happen enough times to design around it.
So the things I make are single files. They open by double-clicking, run from a memory stick, and keep working when whatever service they might have depended on is gone. That constraint shapes everything else: no sign-ins, no seat counts, and nothing that stops being yours.
The practical part
02 / Next
Classroom games, live multiplayer built for a room of thirty, planning tools — most of it opening with no internet at all.
See the work →