Cleve Gibbon

content management, content modelling, digital ecosystems, technology evangelist.

Content Engine Explained

This entry is part 1 of 3 in the series Content Engine

What content challenges prevent you from engaging in broader and deeper customer relationships?  Broader with more channels and deeper through personalisation.  It’s 2017 and we continue to fight the good fight to deliver the most basic personalised experiences within a responsive web channel.  Why is that?

Because it’s hard. It’s not easy to create, manage and deliver content in a predictable, repeatable and scalable manner.  However, that’s precisely what we have to do for omni-channel personalised experiences.  So what if we designed a content engine to do just that? What might that look like?  In this three-part blog post series we explore just that.  Starting with the challenges in this post, we move onto a blueprint for a content engine and before operationalising it in the final post.

Personalised Experience = Context + Content

Let’s take a step back before hitting the content challenges to align on vocabulary.  What is a personalised experience?

A personalised experience has the right mix of context and content.  The context part is the “you” piece.  Context is a combination of first, second and third party data that provides the right time and place for an experience to happen.  Collecting, processing and activating all the data to create the context is all the hard work required to setup the optimal environment to deliver that killer consumer message.

Where there is communication, there is content. (Steven Grindlay)

With the stage set and primed by the context, it’s time to unleash the content.  We need to deliver that killer message, in the right format, to bring that personalised experience to life.  There are many different types of content to deliver; a blog, a booking, an offer, a flight, a promotion, an article, and so on. The right content delivered within the right context results is a great experience.  Falling short on either context or content diminishes the experience.  We’re going to assume those data folks have got the context part right so that we can focus on delivering great content.

Content Challenges

We work with a number of brands, marketing teams, publishers and media companies.  They are all saying the same things that we’ve boiled down into the following common set of content challenges:

•    We can’t repurpose content originating in one channel (e.g. Web) for use within another (e.g. Print).
•    We don’t know what content we really have available across the enterprise.
•    We can’t find content we know we have.
•    We can’t share content easily.
•    We can’t produce content fast enough.
•    We don’t know who’s producing what content, to what plan, and for what purpose.
•    We can’t localise content without entering a world of pain.
•    We can’t afford to procure the right content in our local markets.
•    We know what need to do but don’t know where or how to start.
•    We can’t leverage our own internal content so have to go outside to progress.

The oft cited quote from Unilever still rings true:

If only Unilever knew what Unilever knows

Unilever are looking to build an insights engine[https://hbr.org/2016/09/building-an-insights-engine] to tackle the data part of the experience problem.  I see the content engine being the other the side of the same personalised experience coin.  We could replace Unilever in the quote above with any other brand name.  They are all facing the same challenges when it comes to operationalising personalised experiences.

Summary

In order to deliver personalised experiences, we need to solve for predictable, repeatable and scalable content.  The content engine is a draft model for building content as a function within the enterprise.  It not a technology solution, although technology will definitely enable it.  Instead, it is a framework, a blueprint and set of principles for getting content everywhere it needs to be.  Let’s explore the content engine a little more in the next post.

Series NavigationContent Engine Blueprint >>

Category: content strategy, customer experience

Tagged:

2 Responses

  1. […] we can address the content challenges that exist within brands, what opportunities can organisations capitalise on now to deliver […]

Leave a Reply to Content Engine Blueprint - Cleve Gibbon × Cancel reply

Get In Touch

About Cleve Gibbon



I'm Cleve Gibbon, CTO at Cognifide where we are passionate about digital content.

My sort of up-to-date cv tells you my past, linked in shows you my professional network and on twitter you can find out what I'm currently doing.

This year I plan attend a number of events. Hopefully I'll see you there. I'm easy to find as I'm always laughing. Find out more about me and get in touch!