We’ve heard about learning engineering and while the focus is on experience design, the pragmatics include designing content to create the context, resources, and motivation for the activity. And it’s time we step beyond just hardwiring this content together, and start treating it as professionals.
Look at business websites these days. You can customize the content you’re searching for with filters. The content reacts to the device you’re on and displays appropriately. There can even be content that is specific to your particular trace of action through the site and previous visits. Just look at Amazon or Netflix recommendations!
This doesn’t happen by hardwired sites anymore. If you look at the conferences around content, you’ll find that they’re talking industrial strength solutions. They use content management systems, carefully articulated with tight definitions and associated tags, and rules that pull together those content elements by definition into the resulting site. This is content engineering, and it’s a direction we need to go.
What’s involved is tighter templates around content roles, metadata describing the content, and management of the content. You write into the system, describe it, and pull it out by description, not by hard link. This allows flexibility and rules that can pull differentially by different contexts: different people, different role, different need, and different device. We also separate out what it says from how it looks, using tags to support rendering appropriately on different devices rather than hard-coding the appearance as well as the content and the assembly.
This is additional work, but the reasons are several. First, being tighter around content definitions provides a greater opportunity to be scientific about the role the content plays. We’re too lax in our content, so that beyond a good objective, we don’t specify what makes a good example, etc. Second, by using a system to maintain that content, we can get more rigorous in content management. I regularly ask audiences whether they have outdated legacy content hanging around, and pretty much everyone agrees. This isn’t effective content governance, and content should have regular cycles of review and expiry dates.
By this tighter process, we not only provide better content design, delivery, and management, but we set the stage for the future. Personalization and customization, contextualization, are hampered when you have to hand-configure every option you will support. It’s much easier to write a new set of rules and then your content can serve new purposes, new business models, and more.
If you want to know more about this, I hope to see you at my session on content at DevLearn!