One of the interesting things I found using Twitter during its early days was the subtlety that had been applied to user features & functions…a subtlety that appeals to designers and developers, and the web savvy, but that in many day-in-day-out working applications can be a barrier to entry for naive users.
Perhaps the best example of this for us was the Ideas Channel we rolled out at Insurance Australia Group. One of the key requirements was based on the fact that management did not want the uptake of the application to impact service levels in front line environments, like call centres and retail stores.
Considering the initial skepticism (manifesting in a tiny budget) we were faced with after they had already had a poor experience from a large (and expensive) solution provider, we knew how critical this key requirement would be and how little onging support we’d receive if we could not clearly demonstrate that it had been met.
So what was the metric by success against this requirement would be measured? Time…customer service levels, and in terms of requirements, there is little that matters more to the contact centre and retail aspects of the business than how well it manages service levels and handling times.
Add to that the need to allow participants an interface that facilitates the capture of ‘flash of brilliance’ moments that come during customer and customer information systems interactions, and you are looking at delivering a user interface that is so easy to use, it requires little thought, thereby reducing the risk of dilution of insight as it is transposed to the application.
Mindful of this, we firstly needed to understand the demographic of users…call centre and retail consultants.
Surprisingly, a large proportion of consultants where in a bracket that rarely use any PC applications outside of those provided to them on their work machines… we had discovered our lowest common denominator in terms of user application savvy and designed the user interface to enable that group.
When we rolled out the application, we provided several channels through which users could plug in if they needed help using the app, and closely monitored service levels.
On a user base of nearly 5000, no-one came through on any of the help lines and there was no impact on service levels, even though after 2 weeks, we had captured more than 200 individual insights and generated three times as many conversations within the app.
So the lesson here is…know your audience and the size of the lowest common denominator group…design to the needs of the largest lowest common denominator group based on their environment and experience…and most importantly…measure….measure….measure.
