The Custom eLearning Development Process, Step by Step

Custom eLearning development is divided into five stages: requirements and audience analysis, instructional design and storyboarding, content and media creation, review and quality assurance, and launch and iteration. A typical project lasts between eight and sixteen weeks, depending on duration, engagement, and the number of review rounds.

The Process at a Glance

The custom eLearning development process is designed to be sequential. Each step generates a specific output on which the subsequent stage is based. Skipping or compressing a stage does not result in time savings. It pushes the cost of such job to a later stage, where it is more expensive to repair. Understanding the custom eLearning development process before a project begins is the most dependable method to keep it on track and under budget.

Understanding what each stage produces, how long it takes, and where the common failure points are helps L&D teams manage the process more effectively whether they are running it internally or working with an external partner.

Stage 1: Needs and Audience Analysis

What happens at this stage

Needs and audience analysis defines the problem the course has to solve before any design decisions are made. A thorough analysis establishes the performance gap, what learners are currently doing versus what they need to do, identifies what the audience already knows, maps the context in which they will apply the skill, and surfaces any constraints on delivery format, platform, or timeline.

The output of this stage is a documented brief or analysis report that captures all of those findings and gets sign-off from stakeholders before instructional design begins.

Why this stage determines everything that follows

The most common cause of project failure in the custom eLearning development process is not a production problem. It is a diagnosis problem. When the performance gap is misidentified at this stage, the course ships addressing the wrong thing. Rework is expensive. A course that reaches a thousand learners and does not change behavior is not a production failure. It is an analysis failure that went undetected until launch.

The questions this stage has to answer

What behavior needs to change, and in what context? What do learners already know and believe about this topic? What is getting in the way of the desired performance? What constraints affect how the course can be delivered? How will success be measured after launch?

A thorough analysis takes one to two weeks on a well-organized project. On projects where stakeholders are hard to reach or where the performance gap has not been clearly defined before the project starts, this stage runs longer.

What the client needs to provide

Access to subject matter experts and any existing documentation, data, or previous training materials relevant to the topic. The clearer the organization can be about the performance gap and the target audience at this stage, the faster and cheaper the entire custom eLearning development process runs.

Stage 2: Instructional Design and Storyboarding

What happens at this stage

The instructional design process transforms the analysis into a learning architecture. Precise learning objectives are written first. Learning objectives state specific, measurable behaviors the learner will be able to demonstrate after finishing the course, not vague expressions of intent. Every subsequent content and evaluation choice is measured against these objectives.

The instructional designer creates the material flow based on the objectives, including what is covered, in what sequence, and why. The learning aim determines the sorts of scenarios and interaction models used. Assessment design is developed along with content, rather than after it has been completed.

Individual screens are then storyboarded. A storyboard is a screen-by-screen document that shows the on-screen text, the visual direction, any audio or narration script, and the interaction behavior for every element in the course. It is the blueprint the production team builds from.

Why storyboard sign-off matters

The storyboard sign-off is the single most important step in the bespoke eLearning production process. Modifications made during the storyboard stage are far less expensive than modifications made after production begins. A modification to a branching structure on the storyboard requires a few hours of effort. The identical modification once branching has been coded might take days.

Every organization that consistently runs the custom eLearning development process over budget has the same root cause: changes that should have been made at storyboard were made during or after production instead.

The output of this stage

Before the construction can begin, all key stakeholders must sign off on a comprehensive, authorized storyboard that covers every screen of the course. Some projects also create an alpha or prototype at this stage, which is a short section built to validate the visual design and interaction behavior before full production.

This stage typically takes two to three weeks on a standard project.

Stage 3: Content and Media Production

What happens at this stage

Production is the build phase of the custom eLearning development process. The storyboard is handed to the development team, who build each screen according to the spec. Subject matter expert content is refined into final on-screen text or narration script. Visual design is applied: layouts, typography, color, and illustration. Interactions and branching logic are coded. Audio narration is recorded, edited, and synced. Video is produced and cut where the format calls for it.

Production runs well on a well-defined project with a signed-off storyboard and available content. The development team has all they need and can continue with the build without pausing to explain misunderstandings.

On an under-scoped project, production reveals the total cost of past shortcuts. SME content that was not evaluated during the storyboard stage must be corrected promptly and at a higher expense. Branching logic that was not fully articulated needs to be updated. Visual decisions that were deferred now have to be made under time pressure.

Custom eLearning content development at this stage is only as fast as the quality of the storyboard that precedes it.

What affects production time

The course length is the most direct influencer. A thirty-minute linear course with static images progresses more quickly than a fifteen-minute branching scenario with bespoke illustrations and narration. The level of interactivity, media type, and volume of bespoke assets all have an impact on development time.

A typical production period lasts three to six weeks, depending on the course complexity. Highly interactive builds or ones that need unique video development take longer.

Stage 4: Review and Quality Assurance

What happens at this stage

The completed build goes through structured review cycles. Review in the custom eLearning development process covers three distinct types of checking, and each has a different owner.

Stakeholder review checks factual accuracy and organizational appropriateness. Subject matter experts and business owners confirm that the content is correct, current, and appropriate for the intended audience. This is not the time to redesign the course. It is the time to catch factual errors and outdated information.

Instructional design review checks learning integrity. The instructional designer reviews the built course to confirm that every screen serves an objective, that assessment items are measuring the right things, and that the feedback learners receive is useful and accurate. This layer of review is often skipped on lower-budget projects, and its absence shows in post-launch results.

Technical QA checks platform compatibility, accessibility compliance, and functional behavior. The course is tested in the delivery environment, on the devices learners will use, and against accessibility standards. Links, branching paths, scoring, and completion tracking are all verified.

How many review rounds are normal

One to two rounds of structured review is standard in the custom eLearning development process. Each round has a defined scope and a deadline for feedback. Feedback is consolidated before it is returned to the development team. Rounds that involve unlimited or open-ended feedback cycles are the primary cause of timeline overruns.

Three or more rounds typically indicate either that the storyboard was not properly approved before production, or that the review scope was not defined clearly enough before the build started.

This stage runs one to two weeks on a well-managed project.

Stage 5: Launch and Iteration

What happens at this stage

Launch covers publishing the course to an LMS or other delivery platform, configuring tracking and completion parameters, and communicating the course to learners. On most projects, the technical aspects of launch are straightforward if platform requirements were confirmed during the analysis stage. When platform requirements were not confirmed early, launch is where that gap becomes a problem.

Post-launch iteration uses data from the first cohort of learners to improve the course. Completion rates, assessment scores, time-on-task data, and learner feedback all indicate where the design is working and where it is not. A course that loses most learners at the same screen has a design problem at that screen. A course where learners consistently select the same wrong answer on an assessment item has an instructional design problem or a factual error.

The iterative nature of the custom eLearning development process

Custom eLearning development does not end with launch. The most effective programs see the initial version as a tested starting point rather than a completed product. The only source of information concerning how the course operates in real-world settings is post-launch data. Organizations that incorporate post-launch iteration into their bespoke eLearning creation process typically outperform those who consider launch as the end.

How Long Each Stage Takes

Every stage of the custom eLearning development process has a realistic duration that depends on course complexity, client-side feedback speed, and the number of review rounds. The project timeline guide breaks down each stage with typical durations and the variables that affect them, so L&D teams can set accurate expectations before a project starts.

Download the Custom eLearning Development Process Timeline Guide

How Liberate Runs the Custom eLearning Development Process

Liberate has run the custom eLearning development process across 26 industry verticals for 30 years, reaching more than 10 million learners. The process is consistent on every project: needs analysis before design, storyboard sign-off before production, a defined number of review rounds, and post-launch data reviewed before the engagement closes. That track record is reflected in Liberate being recognized as a Top 20 Custom Content Development Company.

See how Liberate approaches custom eLearning development end to end.

Frequently Asked Questions

How long does it take to develop a custom eLearning course?

A standard mid-complexity course takes eight to fourteen weeks from kick-off to launch. Short, low-interactivity courses with a single review cycle can move faster. Complex courses with branching scenarios, custom video, or multiple stakeholder groups take longer. The single biggest variable outside the development team's control is how quickly client-side feedback and approvals are returned at storyboard and review stages. A well-run custom eLearning development process with organized client-side approvals consistently finishes on schedule.

What is a storyboard in eLearning development?

A storyboard is a screen-by-screen document that specifies everything the development team needs to build each screen of the course: the on-screen text or narration script, the visual direction, the interaction behavior, and the branching logic where it applies. It is the blueprint the production team builds from, and the document all stakeholders approve before build starts. Changes made at storyboard stage cost a fraction of what the same changes cost after production has begun. A well-structured storyboard is the most important quality control tool in the custom eLearning development process.

How many review rounds are normal in the custom eLearning development process?

One to two structured review rounds is standard. Each round has a defined scope, a deadline for feedback, and a process for consolidating that feedback before it is returned to the development team. Three or more rounds typically indicate that the storyboard was not fully approved before production started, or that the review scope was not clearly defined. Unlimited revision cycles, sometimes offered as a selling point by vendors, are not a sign of quality. They are a sign that the process has no structure.

What happens if the project scope changes during development?

Scope changes after storyboard sign-off should be treated as a new work item, not absorbed into the original project. A well-structured custom eLearning development process distinguishes clearly between a revision, which is a correction to something that did not match the agreed storyboard, and a scope change, which is a request to add or alter something that was not in the original spec. The former is covered within the agreed review rounds. The latter requires a separate assessment of time and cost before work begins.

What is the difference between a review round and a revision?

A review round is a structured pass through the built course by a defined set of stakeholders, producing consolidated feedback within an agreed timeframe. A revision is the development team's response to that feedback. Most projects include one to two review rounds. A revision is not a new round. It is the work that results from one. Conflating the two is how projects end up in open-ended feedback loops that expand the timeline and cost without a clear mechanism for closure.

‍