JD Dillon at LearnGeek.co recently asked this question about the Digital Learning Asset Framework:
“I’m still a bit confused by the intended use/impact of the information. Could you summarize the intended change to an L&D professional’s work, and overall benefit to the organization?“
Thanks JD! As for the intended changes, here are a few:
- Increased relevancy & accuracy of content
- Reduced time & administrative load for management of assets (reversioning, repurposing, retiring, etc.)
- Better filter for intake requests (fewer assets needing development)
- Improved user experiences of media
- Easier to measurement & reporting for self-improvement and business reporting needs
- Mindset shift toward smallest indivisible units of training media (aka microlearning)
- Make explicit the Strategies, Tactics, Tools, & Techniques in business logic
Business benefits? Basically to save time & money by avoiding confusion, predictable mistakes, and unquantifiable work.
One of the primary reasons behind creating the Framework is that we currently make a lot of stuff without really knowing why. That’s a serious problem which results in many symptoms.
Because of this:
- we don’t know if something we’re making really needs to be made in the first place
- it’s hard to say if what we made is doing what it’s supposed to when we’re done (because we didn’t specify what that was at the beginning)
- there’s no way to report a business value at the end when we didn’t identify one to begin with
- when it comes time to update or repurpose content, we don’t know how because we don’t know how it relates to other content or where the necessary resources are
- a lot of verifiably WRONG content ends up staying up when it shouldn’t
- plenty of people who don’t need the thing we made end up being told they need it, providing no return but still costing time/money — and breaching trust
The Digital Learning Asset Framework is, among other things, an attempt to reframe the conversation to performance, to people, and to providing value. It provides a way to document what an asset is for so that when it is revisited later, we know what to do with it. It provides a way to make clear what business reasons exist for making something, so we can gather the appropriate data to know if it worked. And it does this without stepping on the domain of any other design methodologies or technologies. No matter your budget or technical or administrative constraints, there is no barrier to entry.
Still have questions? Be cool like JD and ask them!