Two Simple Rules for Evaluating E-Learning Project Changes

By Jonathan Shoaf

Let's face it, most requests for e-learning are vague at best. The client wants an e-learning about a particular topic, they put some PowerPoint slides together with lots of words and bullets (and no graphics!) and say "turn this into e-learning." Although the client will not admit it, they are thinking they'll figure out as the project goes along. This is why its important to have a development process.

1. Background
2. Project Description & Scope
3. Storyboard
4. Prototype
5. E-learning

The earlier in this process you "figure it out", the less amount of work the developer needs to do and the less cost to the client. The goal is to work out the big hairy important details early. Later on in the process you want to be tweaking the details and not making major changes.

When change comes you will need to manage it and keep it from sabotaging the project. Handle all of the changes and the expense goes up leaving the client unhappy.  If you do not handle enough of the changes the client feels like they are losing control of the project to the developer.

I have found two rules to follow for prioritizing change in a project.  You can apply these when you see too much change coming and you need to sort out what changes to implement first.

1. If the client says it is important, the change should be at the top of the list.

You're not the client. You don't know why its important but the client does. The client will not be adament about something unless they have reason to be. If they are being a stickler about a change, ignore at your own peril. The reasons for the change can range from past mistakes made, past feedback given, company culture, or a better understanding of the learners. These are things the client knows but you don't.

If the client says it is important, then make the change. It can go a long way to building a relationship of trust between the developer and client.

2. If you think it is important, the change should be the next item on the list.

The client is relying on you to be the e-learning expert. They are not. You may know why a change is important, but the client does not. The reason it is important to you may include your understanding of how learners interact with e-learning, your understanding of bandwidth issues, your understanding of how the change impacts the clients most important requirements, your experience with iPads versus desktop computer, and more. Trust yourself. The client will learn to trust you.

The rest of the changes are less important. Trust me. What seemed important at a review, may seem less important over time if it doesn't fit these two criteria. I often purposely ignore changes that are not critical to the client and not critical to me to see if opinions will soften over time. It saves work and expense.

How do you prioritize change?