I’m Sabrina and I’m a web content consultant on the Co-op Insurance digital content team. Recently, me and my colleagues Elliot and Huw got together with Co-op Group Digital and content strategist Sarah Richards to start putting together some content design principles. This post is about the reasons for doing this, as well as what we did in the first of the 2 content workshops. We’ll talk about the second workshop in another post soon.
Balancing good content with insurance rules and regulations
On the Co-op Insurance team, we’re working towards an easy-to-use service that lets customers put in their details, choose the right cover for them, get a quote and buy the insurance. It should be simple. But the insurance industry is governed by rules and regulations. Because of this we’ve found that content design (the words, the prompts and the order the pages appear) can be overlooked which is dangerous because good content design puts the user first. The user, or customer, should be able to visit the site and find what they’re looking for easily and quickly. Putting together some content design principles will help us put the customer first, always.
Taking a user-centred approach
Our user testing and customer journey mapping showed us that customers want to reach their insurance quote quickly and easily. However, it was easy to put perceived business needs above customer needs. This meant we were inclined to put small print in a more prominent position than other insurers which meant that the site was full of ‘important’ information that nobody reads.
Customers shouldn’t need to understand the complex financial issues attached to buying insurance. It’s our job to mask quirks, legalese and regulations with plain, compliant English.
We’re working towards putting a content style guide together to improve the way we approach content, particularly with regard to education of stakeholders. Meeting people from around the Co-op in the 2 workshops has helped us do that.
Workshop 1: mapping the process
We used different coloured post-its to map out the process we go through to get new content on the site. This way it was easy to see:
- the number of steps and the timeframes they happen in
- at which points stakeholders get involved
- digital and approval systems
- where the pain points are
We used blue post-its for each step in the publishing process. We then added pink post-its to show which stakeholders are involved and at what point. Seeing the stakeholder involvement mapped against the whole process is a good way to see where early stakeholder engagement might help smooth the process further down the line.
We also mapped out where digital approval systems are used. This helped to identify the influence that such systems have on both stakeholders and steps.
Finding pain points is the first step to fixing things
Finally we added in more post-its to highlight the parts in the process that are usually troublesome. Linking the pain points to the steps helped us investigate why these parts are tricky and also identify any recurring themes. The workshop gave the team some great ideas about how we can improve the process and how pain points can be reduced or eliminated. We’ll use this to help set out a new process for publishing content and it will feed into our content design principles.
It isn’t easy changing process or behaviour, particularly when there are a lot of stakeholders involved. But the process mapping is a solid starting point and it is a great tool to spark discussion around change.
We’ll be blogging about our second workshop on user stories soon. You can sign up to the blog to make sure you don’t miss it.