Instructional Design Project Timeline Template

The Problem: The ADDIE Model Is a Framework, Not a Schedule

Every instructional designer knows ADDIE — Analyze, Design, Develop, Implement, Evaluate. It's a solid framework for thinking about learning design. It is not a project schedule. ADDIE doesn't tell you how long Analysis takes, when Design overlaps with Development, or how to handle stakeholder review cycles that happen between every phase.

The gap between knowing ADDIE and running a project on schedule is project management. Without a Gantt chart, instructional designers lose time in two predictable ways: phases that run long because they have no end date, and dependencies that break because a later phase started before an earlier phase was truly complete. A training needs analysis that bleeds into Design because the client keeps changing requirements is the classic example. gantt-chart.io turns ADDIE phases into a real schedule with real dates so instructional designers can manage client expectations and hit delivery dates consistently.

Prerequisites

Project scope document signed: deliverables, modules, media types, estimated seat time
Client or sponsor contact confirmed with authority to review and approve at each phase gate
SME roster confirmed with their allocated hours per week for the project
Authoring tools and LMS access confirmed for development phase
Content source materials (existing training, job aids, policies, SOPs) received
Change order process agreed upon in writing before project starts

Instructional Design Project Timeline Template

Phase 1: Analyze (Weeks 1–3)

[ ] Conduct performance gap analysis: what is happening vs. what should happen?
[ ] Interview stakeholders to clarify business goals and success metrics
[ ] Analyze target audience: roles, experience levels, prior training history, job context
[ ] Review all existing content materials and identify gaps
[ ] Identify learning constraints: time available, technology access, language requirements
[ ] Document findings in Training Needs Analysis report; obtain client approval
[ ] Define scope and deliverables formally if not already done

Phase 2: Design (Weeks 3–6)

[ ] Write measurable learning objectives for each module (Bloom's action verbs, not topics)
[ ] Map learning objectives to performance gap: does each objective address a specific gap?
[ ] Design course structure: module sequence, estimated duration per module, lesson types
[ ] Define assessment strategy: what evidence demonstrates learning occurred?
[ ] Create visual design concept: style, layout, tone, interaction types
[ ] Write Design Document; obtain client sign-off before development begins
[ ] Identify any technical requirements for interactions or simulations

Phase 3: Develop (Weeks 6–14)

[ ] Write storyboard / prototype for Module 1; submit for SME and client review
[ ] Incorporate Module 1 feedback; use as the approved template for remaining modules
[ ] Write storyboards for all remaining modules
[ ] Obtain written approval on all storyboards before production
[ ] Develop course in authoring tool; build all interactions and assessments
[ ] Produce or source all media: narration, graphics, video, animations
[ ] Conduct internal QA on all modules: functionality, accessibility, consistency

Phase 4: Implement (Weeks 14–18)

[ ] Upload SCORM or xAPI package to LMS; configure course settings
[ ] Conduct technical testing across all required browsers, devices, and operating systems
[ ] Deliver pilot with representative learner group; collect structured feedback
[ ] Facilitate (or support facilitator for) live delivery if blended program
[ ] Troubleshoot any technical issues; make pre-launch revisions
[ ] Train LMS administrators and facilitators on course management

Phase 5: Evaluate (Weeks 18–22)

[ ] Collect Kirkpatrick Level 1 data: learner satisfaction surveys
[ ] Analyze Level 2 data: assessment pass rates, pre/post knowledge gains
[ ] Gather Level 3 data: behavior change on the job (manager surveys, observation)
[ ] Compare Level 4 data against business goals if metrics were defined in Analysis
[ ] Document evaluation findings and recommendations
[ ] Present evaluation report to client; discuss revisions or next-phase training needs
[ ] Archive project files; conduct team retrospective

Common Pitfalls

Skipping the Design Document sign-off: Developing content without formal sign-off on the Design Document leads to major revisions when the client sees the prototype. This single gate prevents most late-stage rework.
Develop starting before Analyze ends: Starting storyboards before the Training Needs Analysis is approved means developing for a problem that may not be fully understood. Honor the phase gates.
Evaluation as an afterthought: If success metrics aren't defined in the Analyze phase, there's nothing to evaluate in Phase 5. Define measurement methods before designing the training.
Change requests without change orders: Clients who see a prototype often want to expand scope. Without a change order process, scope creep is invisible until the project is over budget and over time.

What Good Looks Like

An instructional design project that follows this timeline delivers on time with measurable learning outcomes, minimal revision rounds, and evaluation data that demonstrates impact on the performance gap it was designed to close. The client relationship is stronger at project end than at project start.