This may sound familiar to you ….
Have you ever worked on an eLearning project that took forever to complete? With endless review cycles and changes by stakeholders, sending files back and forth and deadlines continuously getting pushed back? …
Here are three top tips to ensure your eLearning project is launched on time:
- Set guidelines in the initial scoping meeting
In the initial scoping meeting, let your stakholders know how many review cycles they can expect during the build phase. Two or three is a good number depending on how long the module is. If possible, put a limit on the number of stakeholders involved in the project. The fewer people involved, the less amount of changes you will receive and less chance of debate over content. After the initial scoping meeting, send out the project plan to all stakeholders involved. This will highlight the dates of all the review cycles that was agreed upon in the meeting. This ensures they know when to expect them and therefore less likely to delay reviews. It can also be a good idea to send out diary reminders for each of these review cycles, this will help ensure the stakeholders remember there is a review coming up.
- Get content signed off from the storyboard
Clarify with the stakeholder that the content needs to be finalised before the build can begin. Get all written content signed off when it’s in the storyboard. It’s far easier to edit content with tracked changes in a Word doc, than it is to make continous text changes to the Storyline file. If the Word doc is saved in a shared folder, then all stakeholders will be able to see the latest version and who has made the changes. This should ensure there are minimal text changes needed in the module during the build – saving you time in the long run.
- Use Articulate 360 Review
Use Articulate 360 Review for fast and consolidated feedback throughout your project. All feedback is collated in one space, so you don’t have to scroll through countless emails, receive duplicated feedback and confuse stakeholders with multiple versions of the module. Comments can be viewed by everyone in the project and stakeholders will see the same/latest version.
I hope these tips help get your project completed on time. Does anyone else in the community have other tips on how to get projects completed on time?