People in Learning and Development love big data, or at least the concept of big data. It’s a perennial fixture of key trend lists, and we’re warned to ignore it at our peril. But there is risk involved in the L&D community viewing the collection of data as an end in and of itself.
When we take a look at compliance training, we often try to “justify” the learning to the reluctant user by listing the all of the empirical stuff that provides the context for the business case. “Data protection is important for us at Compuglobal Hypermeganet because in <insert recent year> there were <insert massive figure> breaches of data for our industry resulting in <insert inordinately large amount of money> in fines.” And yeah, it serves a purpose, to a point. Examples like this are an attempt at what we like to describe as a “war story” – using the worst case scenario to illustrate what a breach in compliance means.