In this phase, stakeholders will submit a form outlining their need and/or request for partnership with the training team/instructional designer(s). If the form indicates a need that sits within the scope of the training team, we’ll schedule an Intake Meeting to begin the needs analysis. This form will be attached to the invitation and will set the agenda for the meeting.

During this stage, the instructional designer will begin a formal needs analysis based on the information/data collected during intake. A weekly sync will also be scheduled between the ID and the SME (and any other necessary stakeholders) to discuss clarifying questions and review additional materials. 

If analysis confirms that a training solution is recommended, the ID will schedule a formal Kickoff Meeting with all stakeholders.

The design phase begins with a Kickoff Meeting, which will include all relevant stakeholders. The meeting's agenda is defined largely by this form, which will be filled out in advance and attached to the invitation. It covers findings, modality, objectives, content, assessment(s), and a timeline. At the end of the meeting, formal sign-off ✅ is requested, pending that there are no additional action items.

Depending upon the complexity of the project, the ID may request a follow-up Content Approval Meeting to discuss a high-level overview of the outline, script, etc. At the end of the meeting, a formal sign-off ✅ is requested, pending there are no additional action items.

The development phase varies according to the modality and the complexity of the project, but may include the development of any number of the following:

• storyboarding (text-based, lo-fidelity, high-fidelity)

• eLearning/ slide decks

• audio/video production

• general asset development (activities, graphics, etc.)

• assessments/scenarios/surveys

• facilitator guides

• closed captioning

Stakeholders will be provided the deliverables and either invited to additional Content Approval Meetings, or asked to participate in a Review Cycle, during which they will be asked for targeted feedback. I often ask for two Review Cycles, the second of which is reserved issues related to accuracy and/or bugs. Formal sign-off ✅ will be requested as necessary.

The implementation phase will vary depending upon the complexity and modality of the project, but may include any of the following:

• Train-the-Trainer

• Hand-off meeting to discuss deliverables/facilitator guide

• Scheduling

• Post-Training Report (to surface any issues)

• ILT observations

If necessary, revisions, bug fixes (etc.) will be discussed and addressed.

The evaluation phase will vary depending upon the complexity and modality of the project, but will likely include a Post-Mortem Meeting to discuss the relative success of the project and take-aways that may inform future projects. This form will be distributed in advance of the meeting, and will inform the agenda.

Depending upon the nature of the project, the team may also discuss updates and routine maintenance.