Among all of the material in this week's reading, there was one facet of memory that hit me due primarily to the relevancy and timeliness of the information. Sousa writes about the Primacy-Recency effect and describes it as "in a learning episode, we tend to remember best that which comes first and remember second best that which comes lace. We tend to remember least that which comes just past ht middle of the episode," (p. 100).
Recently we have been contending with this aspect of training among our clients. Many of our clients come to our organization for our help in crafting and developing eLearning training on their behalf. Lately, many have come to us and blatantly said; "we don't want any single module to be more than 20 minutes long." What's confusing about this is that they have some modules that are many times longer than 20 minutes. "Just split it up but make sure nothing is over 20 minutes." They have settled on this 20 minute time frame like a ship wreck survivor to a piece of flotsam.
Earlier in the text, Sousa writes about the time limits for processing new information, for adolescents and adults to be about 10 to 20 minutes, (p. 54). I'm sure that studies like the one that Sousa used for that information have filtered down to our clients and therefore they want all of their training to be 20 minutes. Is it that big a deal? It kind of is? The last one we reviewed on behalf of a client was a 48 minute training that they had cut in half to be two, 24 minute modules. The problem? They did not break it at a natural break, they did not separate the two halves into parts that made sense, nor did they necessarily do anything beyond making the learner push one button to close out the first module and another button to start the next. So instead of providing the learner a natural break and giving them time to reflect, learn, or recall, they just had them push two buttons and re-engage the training. It was a completely artificial and unneeded break. Any learner would have said it was silly to have the break there and they would have rather just continued on.
As with so many aspects of this subject there is nuance, exceptions, and no hard and fast rules. Last week I wrote about the time it might take a vacuum truck to fill 3/4 full a viscous, water-like substance from a pit while parked on level ground. Well, what if there is debris in the pit? What if the pump hasn't been maintained? What if the valve is stuck have closed? What if the liquid is viscous on top but sludge on the bottom? All of these factors make the 15 min time standard incorrect. Just as saying "make all training 20 minutes" a poor standard.
I really like that Sousa introduced the Primacy-Recency Effect and showed how the same basic cycle of "prime time" and "down-time" applies regardless of 20 minute sessions or 40 minute sessions (p. 101). There is more nuance in training design and development than just keeping things to 20 minutes. There are other techniques and tools we as training developers can use to help influence retention and recall than just 20 minute modules. Good to know, sure, but being able to add this to the mix of techniques and train effectively is what will make our organization unique. I look forward to showing our clients how we can utilize the Primacy-Recency effect to help make their training more effective.
I wonder how many of the others in this group have seen this type of subservience to training duration time limits? Or how many have helped improve their training through the Primacy-Recency effect and how it might have gone?
References
Sousa, D.A. (2016). How the brain learns, (5th Edition). Thousand Oaks, CA: Corwin.
