Instructional Designer and Learning Engineer
Most instructional designers hand off the build. I don't.
Eight years in eLearning, eleven in production overall. Wherever a lesson breaks, I find why and fix it: a SCORM team at Kidvento shipping 100+ K-12 modules, and a system designed to work regardless of internet fluctuation through custom tools.
- 100+
- K-12 modules shipped
- 8
- people on my team
- 6
- languages, one master
Selected work
Design decisions, start to finish
Three problems I shipped fixes for. The outcome first, the full design write-up one click away.
Practice, not slides
A policy-recall course became branching scenarios that rehearse the calls people actually get wrong on the job. The same process now drives every compliance course I build.
Read the design notesPlays on almost any connection
Video lessons used to buffer to a stop on a shared classroom line. Now the lesson senses the connection and adjusts itself, with nothing for a school to install.
Read the build4 hours, to 10 minutes
A four-hour manual publishing checklist is now one automated pass that catches what tired hands miss at 6pm. The team got most of a day back every week.
Read the buildThe craft
I storyboard before I build
Every module starts on paper, not in Storyline. The storyboard is where the teaching decisions get made and argued, before a single screen is built. It is also where I align the SME, the visual designer, and the developer on one plan.
At Learning Owl I replaced manual asset handoff with an Illustrator to Storyline workflow built off the storyboard.
Visual revision rounds went from three, to one.How I think
Most training fails before a single slide is built, by answering "what should we cover?" instead of "what should people do differently?"
Begin with behaviour
If the honest answer to "what changes?" is nothing, I say so, and suggest what would actually help.
Practise, do not present
A scenario that mirrors a real decision beats a slide full of facts. People remember what they practised.
Experts as partners
The SME knows the content. My job is asking the questions that surface what a learner actually needs.
Design for everyone
Slow networks, screen readers, keyboard-only, six languages from one master. Anything less is half a lesson.
The differentiator
Six languages, from one master file
Localization is where most eLearning quietly breaks, and where I have spent years. Translated scripts run longer than the English source, so narration and animation fall out of sync. Numerals, registers, and reading direction all shift. The fix is design, not find-and-replace.
I have run full multilingual delivery across six Indian languages, managing translator handoff, audio re-sync, and per-language QA, then built a Flask tool that moves quiz text between storyboard, Storyline, and translation docs so the same edit does not get retyped six times.
- Re-syncNarration and animation timed back to each translated script, not the English original.
- RegisterThe formality and tone a learner expects, language by language, not a literal translation.
- One edit, onceA Flask tool parses Storyline XML so a quiz edit moves between storyboard, Storyline, and translation docs without retyping.
- QA per languageEvery variant verified for tracking, layout, and accessibility before it ships.
How I work in 2026
AI in the pipeline, not in the credits
I treat AI as production capacity, not a novelty. It drafts and accelerates; I direct and verify. The judgement about what a learner needs stays human.
The engineering edge
An instructional designer who ships his own tools
Here is the "why now": more eLearning content is AI-generated now, and build-time checks have not kept up with it. So I built the checks, and the glue, I was missing.
Storycraft
Markdown → SCORM · byte-identical builds · runs live in your browser
Write a lesson as a Markdown storyboard, get a deterministic SCORM 1.2 package out: same input, byte-identical zip. Collapses the storyboard-then-rebuild loop for compliance and localized modules where full authoring is overkill.
Read the case →scorm-kit
9 build-gate commands · 31/31 tests · 0 deps
Born from six months of SCORM postmortems. Lint, a11y, privacy, cmi5 and a one-shot report that scores a package 0 to 100 before upload, catching the silent failures Storyline ships and Moodle surfaces as a learner ticket two weeks later, caught at build time instead. CI-ready exit codes.
xapi-doctor
30 spec-cited rules · 17/17 tests · 0 deps
26 xAPI 1.0.3 rules + 4 cmi5, each mapped to a section of the spec. Turns an opaque LRS "400 Invalid request" into the exact field that's wrong, and tells you whether the LRS itself is healthy.
View on GitHubStoryboard Sync
Live tool · one edit, six languages
One quiz edit, applied across the PPTX storyboard, the Word translation docs, and the Storyline .story file, so a fix isn't retyped six times for six languages. Runs in the browser; uploads auto-delete after 30 minutes.
Experience
Eleven years, from craft to lead
KidventoLearning Engineer and SCORM Team Lead. Leading eight people, 100+ K-12 modules shipped.
Learning OwlInstructional Designer and eLearning Lead. Compliance, POSH, induction, and soft-skills courses, SME to LMS.
Learning LozixeLearning Developer. 300+ activities for the Balbharati K-12 curriculum, six-language localization.
LionbridgeLocalization Integrator. Adapted global eLearning for Indian and Southeast Asian markets.
FreelanceContent, scripting, and animation. The visual foundation the later work is built on.
If a course is slow to ship, breaking in odd ways, or changing nothing, we should talk.
Open to remote instructional-design and learning-engineering roles, anywhere.