Development time depends on more than course length
Two 20-minute courses can require radically different effort. A simple policy update may be mostly writing and layout; a branching scenario with custom media, accessibility review and several stakeholders can take many times longer.
1. Define the deliverable
Record target duration, audience, outcomes, format, interactions, assessment, media, export standard and languages. Estimation without a defined deliverable is guesswork.
2. Estimate by workstream
- Analysis and SME discovery
- Instructional design and storyboard
- Writing and editing
- Authoring and visual build
- Media production
- Accessibility
- Review and revision
- QA, LMS testing and release
3. Apply complexity deliberately
Simple text-and-image content is faster than custom interactions, branching, animation or simulation. Estimate each high-complexity feature separately instead of hiding it inside an average.
4. Budget for review cycles
Stakeholder delay and revision are often larger schedule risks than authoring. Agree who can approve content, how feedback will be consolidated and how many review rounds are included.
5. Add contingency for uncertainty
New subject matter, unfinished source material, legal review, translation or unknown LMS behaviour justify contingency. Make the uncertainty visible rather than silently padding every task.
6. Compare estimates with actuals
After each project, record planned and actual effort by workstream. Your own historical data will become more useful than generic industry ratios.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.