Feedback on your eLearning Development
It is part of the eLearning development workflow, to receive feedback on different components at different stages during this development. Usually, this feedback encompasses things that might not work within the context of the eLearning module, either graphics, audio or functionality.
Whatever the case, here are a few tips to deal with the different rounds of feedback throughout the duration of an eLearning project:
Don’t take it personally: It is true that some times the feedback you receive might look like it’s directed at you and your skills as an eLearning developer, however, it’s not the case, since the person reviewing the different versions of an eLearning module, is looking at it from a learner’s perspective, so things that may be obvious to you, like navigations, positioning of the elements on screen, etc., may be less intuitive for a learner, which is ultimately the target audience, so try to always look at the feedback as objectively as possible.
Must have’s vs nice to have’s: There is always two kinds of feedback, must have’s or show-stoppers, which are basically things that need to be fixed for the eLearning to properly work, for example, completion tracking: if it’s not marking completion correctly, even after getting to the end of the eLearning or passing a Knowledge Check, it is something that needs to be fixed for the client to sign off. On the other hand, we have nice to have’s, which usually amount to personal preferences from the reviewers or the client, and are things that even if they are not implemented won’t interfere with the correct functionality of the eLearning module, for example, if you have a piece of music at the beginning of a module, and are asked to change it for something different.
It is okay to push back: Not all the feedback needs to be implemented, and as long as you have a reasonable explanation as to why that peace of feedback is not necessary, and your client understands and agrees, you can always push back. Sometimes feedback comes from a place of confusion because maybe the client was picturing something different. It happened to me once that a client had an idea of what the eLearning module should look like, but when I produced something entirely different, the client was thrilled with the end result.
Hopefully these tips help you with managing the feedback on your eLearning module.
