I have spent over a decade turning science into learning, first as a classroom teacher and science program director, now as an academic specialist producing curriculum-aligned lessons at scale. These four pieces show the problem each one solved and how I built it.
A collection of HTML5 science simulations built to one behavior specification and one visual language, so each interactive looks, responds and assesses consistently.
Interactive simulations are the most effective way to let learners test ideas, but they are slow to produce and drift apart in look, controls, and pedagogy when each is built separately. Established libraries such as PhET set the bar for instructional quality, yet they can feel dated and cannot be restyled, embedded, or controlled as a private organization needs.
Secondary school learners and adult or corporate learners. Each interactive runs self-paced on a learner's own device and projected for a whole class or training room, and each is built to embed in Storyline or Rise courses.
Designer and standards owner. I set the design direction, wrote the specification and the standards for each interactive type, decided which ideas deserve interactivity, and accepted or sent back every build. The approach grew out of prototypes I built for an edtech content team, where I proposed a workflow for subject-matter experts to direct AI in building simulations.
System first. A design direction, a design-system specification, standards for each interactive type and a reusable skill that builds each interactive from them, so separately built simulations do not drift.
Screening for purpose. Every idea faces one question: does the interaction carry the learning? Click-to-reveal labels on a diagram are static content and belong in a slide deck.
Pedagogical structure. Multiple tabs of increasing complexity, so learners start simple and add variables as their understanding grows.
Presentation modes. A collapsible header for widescreen projection.
Portability. Every interactive is a single self-contained file, so it survives link rot and licensing changes.
Look and feel. The Studygram notebook style shared with the Storyline modules: notebook pages, ink-dark type, sticky-note and highlighter accents, and a handwritten display face with a clean sans-serif.
Assessment. Kept apart from the main screen, with the simulation itself as the instrument, including predict-then-reveal tasks.
An AI assistant with a set of knowledge files generates the simulations. My part is everything the assistant cannot judge: the design direction, the interface standards for each interactive type, and whether an idea deserves interactivity at all. A build is accepted only when it keeps its instructional purpose. Putting the design system into a reusable skill means a build in a new chat starts from the same rules as the last one.
I am actively exploring new instructional design and e-learning development roles. If your team is looking to expand or needs someone to lead complex learning initiatives, reach out at ivanhubert.juan@gmail.com
© 2026 Ivan Hubert C. Juan