A while ago, I wrote an article in eLearnMag, stating that better design doesn’t take longer. In it, I suggested that while there would be an initial hiccup, eventually better design doesn’t take longer: the analysis process is different, but no less involved, the design process is deeper but results in less overall writing, and of course the development is largely the same. And I’m interested in exposing what I mean by the hiccup.
What surprised me is that I haven’t seen more movement. Of course, if you’re a one-person shop, the best you could probably do is attend a ‘Deeper ID’ workshop. But if you’re producing content on a reasonable scale, you should realize that there are several reasons you should be taking this on.
Most importantly, it’s for effectiveness. The learning I see coming out of not only training shops and custom content houses, but also internal units, is just not going to make a difference. If you’re providing knowledge and a knowledge test, I don’t care how well produced it is, it’s not going to make a difference. This is core to a unit’s mission, it seems to me.
It’s also a case of “not if, but when” when someone is going to come in with an effective competing approach. If you can’t do better, you’re going to be irrelevant. If you’re producing for others, your market will be eaten. If you’re producing internally, your job will be outsourced.
Overall, it’s about not just surviving, but thriving.
Yes, the nuances are subtle, and it’s still possible to sell well-produced but not well-designed material, but that can’t last. People are beginning to wake up to the business importance of effective investments in learning, and the emergence of alternate models (Khan Academy, MOOCs, the list goes on) is showing new ways that will have people debating approaches. It may take a while, but why not get the jump on it?
And it’s not about just running a workshop. I do those, and like to do them, but I never pretend that they’re going to make as big a difference as could be achieved. They can’t, because of the forgetting curve. What would make a big difference isn’t much more, however. It’s about reactivating that knowledge and reapplying.
What I envision (and excuse me if I make this personal, but hey, it’s what I do and have done successfully) is getting to know the design processes beforehand, and customizing the workshop to your workflow: your business, your processes of working with SMEs, your design process, your tools, and representative samples of existing work. Then we run a workshop where we use your examples. Working through the process, exploring the deeper concepts, putting them into practice, and reflecting to cement the learning. Probably a day. People have found this valuable in an of itself.
However, I want to take it just a step further. I’ve found that being sent samples of subsequent work and commenting on it in several joint sessions is what makes the real difference. This reactivates the knowledge, identifies the ongoing mistakes, and gives a chance to remediate them. This is what makes it stick, and leads to meaningful change. You have to manage this in a non-threatening way, but that’s doable.
There are more intrusive, higher-overhead ways, but I’m trying to strike a balance between high value and minimal intensiveness to make a pragmatic but successful change. I’d bet that 90% of the learning being developed could be improved by this approach (which means that 90% of the learning being developed really isn’t a worthwhile investment!). It seems so obvious, but I’m not seeing the interest in change. So, what am I missing?