Our eLearning development process
Three phases, 12 stages, and three sign-off gates – so nothing moves forward until you approve it, and every change happens when it's quickest and least expensive to make.
Fewer surprises. Fewer rewrites.
Most eLearning delays have the same cause: late changes made after development has started. A change agreed at storyboard stage costs a fraction of the same change made after the course is built – so our process moves the big decisions (audience, objectives, structure, and script) to the front.
Each phase ends at a gate, and nothing moves forward until you sign off. We follow ADDIE, write objectives to Bloom's taxonomy levels, and build in Kirkpatrick evaluation where you have the data.
Three phases, 12 stages, three gates
Every project follows the same path, whether it's a fully custom course or a rapid conversion – with a clear sign-off at the end of each phase.
Analysis and design
Instructional designer · Storyboard writer · Project managerWe start with the why – confirming your audience, performance gap, constraints, duration, devices, and LMS.
We write clear, measurable objectives and map each one to how it will be assessed.
We define the course structure, module breakdown, interactions, and assessment plan.
We write every screen – on-screen text, narration script, interactions, and graphic briefs – for your experts to review and refine.
Production
Graphic designer · Developer · Media teamWe develop one representative module to confirm the look, feel, and navigation before scaling up.
We produce and synchronize graphics, animation, video, and voice-over.
We bring the full course to life in Storyline, Rise, or custom HTML5, with all media in place and tracking configured.
Our QA specialists run instructional, functional, technical, and editorial testing before you see it.
Release
Developer · QA specialist · Project managerWe implement your consolidated comments and verify each one, item by item.
We load the course to your LMS for final testing in the live environment.
We deliver the final SCORM 1.2 or SCORM 2004 package, together with source files and assets.
We publish the course, set up users where required, and provide post-launch support.
Four layers of checking
Every course is tested by a QA specialist who did not develop it – before it reaches you at alpha, and again before the gold master.
Instructional
Every objective is taught and assessed, and each question tests the level it claims to.
Functional
Navigation, branching, media, resume and bookmarking, completion, and scoring logic.
Technical
SCORM packaging and tracking, LMS reporting, and browser and device testing.
Editorial
On-screen text, narration match, terminology, and brand compliance.
What you do in each phase
Your team stays in control through clear, focused review points.
- Analysis and design: share your source material, give us access to a subject-matter expert, and approve the objectives, structure, and storyboard – for regulated content, route the storyboard through your medical, legal, or compliance review.
- Production: review the prototype and the alpha, and send one consolidated set of comments using the review method we agree on at kick-off.
- Release: confirm your beta changes, test the course in your LMS, and sign off on the gold master – or let us host it and plan your launch communications with us.
Accessibility and ownership, agreed up front
Accessibility is built to the WCAG level you need and specified at the storyboard stage – because retrofitting it after a course is built costs more and works less well.
When the project is complete, you own it. Source files, project files, media, scripts, and the SCORM package are all handed over – so you're never locked in for future updates.
Then, if you need it: multilingual rollout
Your course is designed to travel from the very first storyboard – text kept out of images, room for longer languages, and narration kept as separate assets. Once the source-language course is final, we take it global through Localize – translating the content, recording native or human-reviewed AI voice-over, adapting on-screen text, and running linguistic and functional QA on every language version.
Who you'll work with
Learning project manager
Your main point of contact, from kick-off to launch.
Assistant project manager
Keeps reviews, files, and schedules on track.
Instructional designer
Shapes objectives, structure, and activities.
Storyboard writer
Writes the script and on-screen text.
Graphic designer
Creates the visual style and assets.
Developer
Develops the course in the agreed tool.
QA specialist
Tests content, functionality, and SCORM behavior.
How long does it take?
It depends on course length, interaction complexity, how much source material is ready, and how quickly reviews come back. During scoping, we agree on a schedule with named review dates – so you can plan with confidence.
Your choice of production approach
Some organizations want every asset created by people. Others are comfortable using AI to speed up parts of production. We work either way and agree on the approach with you from the start.
When we use AI voice-over, a human reviewer checks the pronunciation. That review improves quality, but AI voice can still mispronounce specialist terms – so for high-stakes or technical content, we recommend native voice artists.
Ready to start with a needs analysis?
Share your material and goals, and we'll come back with a recommended format, tool, and plan.