Showing posts with label Customer Centricity. Show all posts
Showing posts with label Customer Centricity. Show all posts

Thursday, 9 October 2008

Customer-centric Innovation

Great presentation on customer-centric innovation. The drivers for this are that traditional innovation is broken and the nature of competition is changing. Think left-wing rather than direct.

Wednesday, 24 September 2008

Cross-Channel Retailing - ARC Retail Presentation 2008

I attended the ARC Retail Conference this morning and gave a breakfast briefing with some of my Charteris colleagues on Cross-Channel Retailing - see slides below.

It covers 3 critical challenges that retailers are facing right now and how they could start to address them by developing low cost, high benefit customer propositions through leveraging the channel assets they already have. Here's the slides. If you want to know more just drop me an email and we'll be more than happy to have a chat.

Monday, 22 September 2008

Successful Cross-Channel Retailing Is All About The Experience

By merging physical and digital sales channels, retailers essentially hope that shoppers never leave without making a purchase because the experience was lacking or because items they wanted are not on the shelves. As online retail continues into its second decade, business strategies like customer relationship programmes and multichannel integration, that were once perceived as too complicated to integrate successfully, are now working in sync.

Multiple channels to market are therefore fast becoming the norm and the lines between these channels are blurring – particularly in terms of consumer expectation. Forward thinking retailers are moving towards a seamless customer experience across all channels. It is becoming less and less acceptable to have differential pricing, branding or experience across different channels, and successful retailers are rethinking both their organisational design and also their customer engagement strategies to ensure that their routes to market are cohesive.

The common perception is that the major driver for cross-channel retailing is cost saving through efficiency and effectiveness. Managing channels separately results in cost increases resulting from running separate order-management and customer service operations, multiple warehouses and fulfilment systems, and buyers and merchandisers duplicating effort across the different channels.

However, although emerging integration technology allowing cross-channel integration has been a key enabler, multi-channel growth is essentially driven by consumers. According to Shop.org, 34% of consumers today use at least three channels when shopping. Research has also found cross-channel shoppers to spend up to 10 times more, to generate 25 to 50% more profit and demonstrate greater loyalty than their single-channel counterparts.

The core driver behind channel convergence then is customer demand.

So where do you start?

Well, Recent McKinsey research shows that only 15% of loyalty is gained from perceived product quality and promotional strategies, leaving 85% to the actual purchasing and post-sales experiences of customers. Point being that whilst establishing clear and consistent products and services is essential, the experience is what makes all the difference.

So one good place to start is to get your people culturally ready to make the most of all the channels your business takes to market. Whilst optimizing content, applications, pricing and product selection across all channels is important, the basic human experience at least should be seamless across channels. The person who answers the phone at your call centre should be equally as knowledgeable about your products and services as your store staff, consumers should be able to find out when and where items are in stock, and have you deliver or let them pick up their purchases as per their convenience. The returns processes, checkout processes, and customer journeys through your store, should be synchronised with and as easy as they are on the web. All this can be successfully done through human facilitation.

In summary, we’re talking about developing a cross-channel customer-facing culture that ensures your staff are making your customer’s journey as enjoyable as possible, with a view to building loyalty through experience and thus competitive advantage.

Thursday, 11 September 2008

Customer Centricity: The Basics Are Not Always Enough (Part 2)

Following on from Part 1, the principle of recognising that value-adds become basic needs in mature markets applies even if you're a big brand entering a new space. Lets use Google's new browser Chrome as an example.

Google Chrome Logo

It's simple, fast and neat and provides all the basic browsing capability that it needs to, but I bet Google didn't do any Voice of the Customer analysis around lay users before release. If they had, they would've realised that a host of conveniences they haven't included are now considered as basic functionality.

They'd have known that their early adopters outside the tech-community would be young to mid-adult. People who use Gmail and Facebook and Hotmail and Yahoo and Youtube and Del.ic.io.us, and have grown used to toolbars that connect them directly to the sites they visit often. Chrome is not yet compatible with any toolbars, so it misses all those conveniences that your average Joe is used to. Even worse, Hotmail asks you to upgrade your browser and Facebook's edit and auto update features don't work perfectly - these small things are major barriers when they affect core browsing activity. Many will also just be irrationally (?) worried about their browsing habits being monitored to learn more about them to help Google's targeted advertising, and nothing in the user experience or messaging does anything to alleviate this.

Point being that most of the people who get past the privacy issue and then bother to download the browser will find that it lacks the 'basics' and thus provides no compelling reason for learning a new interface. The hype is great. Many will download it. This could have been a fantastic opportunity for Google, but I suspect most people will go straight back to the browser they use - probably IE, resulting in Google having to come back and do a whole lot more work to drive take-up, and thus in them missing out on a golden opportunity to get the jump on Microsoft in their main domain, i.e. the desktop.

Wednesday, 10 September 2008

Customer Centricity: The Basics Are Not Always Enough (Part 1)

Customer-centricity at its basic is about ensuring the customer gets what they need rather than simply what you want to offer. This is still an improvement on what most companies provide, because it involves at least listening to the voice of the customer. Better however is to give the customer what they want, over and above what they need. This is usually costlier to provide because we're talking about value-adds. Getting the details right. Caring about your customer. The really successful brands and companies do this repeatedly. They get the basics right and then pile on the value-adds. Like Apple.

Fig. What The Customer Wanted...


Ref: http://www.uoregon.edu/~ftepfer/SchlFacilities/TireSwingTable.html

In emerging markets just addressing needs is enough to get ahead.

In evolving markets, effectively meeting functional needs is often enough for competitive advantage, but value-adds start to become differentiators.

In mature markets however, basic needs themselves become redefined to include what once were value-adds. This means that if you don't already have embedded market share, at the very least you have to match the value-adds that people have gotten used to or you don't even stay in the game.

In part 2 tomorrow, we'll look at Google's new browser 'Chrome' as an example.

Monday, 8 September 2008

The Future Is Chrome... Or Is It?

So Google has released their new browser called Chrome (read about it in my post... Google's new browser muscles in on Microsoft) and everything I've read since then is proclaiming it as the future. Well, I'm not so sure.

Beta Problems

Let's start with the immediate stuff. The problem with releasing a beta version of course is that it doesn't yet have all the functionality of its established competitors. Chrome is in Beta and isn't functionally integrated with all the conveniences we've gotten used to. Here's an example - It is probably going to be a while before you can get toolbars for Chrome, which is very limiting. I use Del.ic.io.us, Google and Zemanta's toolbars. You probably use Yahoo or whatever. Until we can get versions of them for Chrome, there's really no sense in switching over.

Of course knowing Google they will learn very fast, but the speed at which the message about Chrome will spread means that a lot of people will download the beta, find that it is missing conveniences they're used to and give up on it right there. People hate stumbling over obstacles if they have working alternatives.

The main sell is that there's also lots of exciting tech stuff. A new javascript engine - do you know what javascript is? Runs Ajax faster. Do you care? Apparently this makes it the fastest browser ever... in microseconds for developer applications. To me it seems about the same as IE from a normal browsing perspective. I doubt you'll notice the difference.

So Is the Future Really Chrome?

Short answer is No.

Everyone's expecting this to be huge, but they're really they're all tech-savvy types, and not your average Joe. Personally I'm not so sure.

My main issue is that I don't see the mass market. The fact is that in any given space, once products, services or applications have matured enough to become fit for purpose, until the purpose fundamentally changes, there really is no gap to exploit.

In the computing space, operating systems, browsers, and office applications come free with the hardware. They are now sophisticated enough in functionality and user experience to do pretty much what any layman wants to do, and well enough to ensure complete satisfaction. Our computers don't crash often; existing browsers render text and multimedia fast and accurately; and there really isn't much else that most people need out of Word.

So what's the incentive? Brand? Google isn't Apple, and even if it was, how many people have ever downloaded Safari to their non-Apple machines? Do you even know what Safari is?

In a Nutshell

Point I'm making is that until the way we browse fundamentally changes, new entrants really have nothing to add for the majority of users. The future is touch screen and voice commands. When these start to become ubiquitous, what the mass market needs from browsers will change. At that point there will be a big gap for new entrants.

If Chrome was setting itself up to exploit that change, we'd be looking at the early rumblings of a browsing revolution. But it isn't. - The browser is not finger touch oriented in anyway, and in fact the functionality has become more mouse based, fiddly and precision oriented. There isn't even the 'alt' functionality needed for disabled access technologies.

So no, for the moment I don't really see Chrome taking over the world. I suspect it will be just another player like Firefox. I'll be keeping an eye on it anyway from the perspective of USP development, so if anything new comes to light that changes my view, I'll be sure to keep you posted!

Tuesday, 2 September 2008

Everything is perfect until people get involved!

Does this sound familiar? You've had a genius vision for a service or product or campaign. Worked out the revenue streams and ROI model. Got decision maker buy-in. Planned it out. Branded it. Built it. Executed every detail perfectly. Launched it. And then found that people don't use it the way you expected!

This happens all the time. Some great examples at the failblog.org website. People either don't get what you were trying to achieve, or they use it for some other purpose, or they ignore you altogether and go right ahead doing what they always did. Sometimes even other members or departments in your own organisation don't deliver it the way you expected.

You wonder what happened. And then someone asks whether you tested any of your ideas on your audience before getting it out there?

This is a classic mistake that organisations traditionally make. As creators of products and services we think we know best. We think we understand our market because we've been in business a long time, or because we imagine our audience to fit some imaginary persona, or simply because we expect our audience to be the same as us.

Here's 3 ways of making sure you don't have any unpleasant surprises when you go to market with your new offering.

  1. Identify Target Audience
    Identify your target audiences and create focus groups that cover both the people who are the target audience and also the people who will be expected to deliver the service or product. Incentivise these groups so that they have enough reason to care about what you're trying to achieve.
  2. Create Focus Groups
    Run your generic ideas past the focus group. Remember that users can only tell you what they do or don't like. They rarely help you innovate, so you'll probably still have to craft the product or service yourself and make judgement calls. Rest assured you'll learn a lot though.
  3. User Test Your Offering
    Involve the focus group in the detailed development of the product, system or service. In other words ensure you have sufficient user testing before you go live. These are costs that most organisations skimp on, but its the best money you'll spend in terms of return on investment.

Tuesday, 29 July 2008

7 Ethical Ways To Persuade People To Buy

Persuasion is not about manipulation. Here's 7 tips based on tapping into human pyschology.

  1. Show what others are doing
  2. Show user generated reviews
  3. Show scarcity of products
  4. Persuade with pictures and videos
  5. Cross and Up Sell
  6. Show authority
  7. Allay people's fears

For more detail see the original post by Lisa Halabi on the Usability News site.

Monday, 23 June 2008

5 Key Aspects of Observational Research

I discussed in my previous post how understanding the ways in which your customers engage with your products and services is a great way to draw out improvements and opportunities for innovation. Watching them engage with your offerings in their natural environment is the key, and Dave Pollard has identified 5 things to look for when carrying out observational research; otherwise known as 'ethnography' or even 'customer anthropology'.

  1. Workarounds - things people do that the existing product, process, tool or facility was never designed to accommodate, but which helps them to get the job done that they need to do.
  2. User torture - Evidence of obvious customer discomfort, either physical or psychological
  3. Obstacles and barriers - Signs that people can't do their job because of a physical or procedural barrier.
  4. Repurposed objects - Tools designed for one thing have been appropriated to do something else.
  5. Wear patterns - Evidence of stress or overuse in the product

Friday, 20 June 2008

3 Reasons Why Ethnography Is Better Than Focus Groups

Patricia Seybold's Ethnography vs Focus Groups

Ethnography is the process of doing observational research (often involving discrete video capture) on how consumers use and engage with your products out in the real world environment (in-store and/or at home). Focus Groups, on the other hand involve getting potential customers together and then quizzing them about the product in retrospective. Ethnography is a great way of drawing out improvements and opportunities for innovation, particularly around newly launched products. The trick is to ensure that product developers and designers get personally involved in the activity.

Anyway here are 3 reasons why Ethnography is better than using Focus Groups

  1. Consumers often can't remember much about products when questioned about them in retrospective and outside the normal context.
  2. Observing consumer use the product in its normal context yields much more useful data and often unexpected behaviour
  3. Recording the behaviour gives the product development team valuable footage that they can show to senior management to justify investments in product and packaging improvements

The inspiration for this post came from the Innovation Tools blog and they recommend three useful articles around ethnography

Thursday, 19 June 2008

The Key to Success in the Next Generation High-Street

The key is customer experience. Branding online is primarily about the experience, and it is making the passive, push marketing approach we've lived with since the start of capitalism obsolete. With price and quality becoming more and more homogenous on the high street, retailers must start moving towards experience focused outlets that are built around impressing and engaging their customers, rather than the traditional model of simply cataloguing or showcasing the products or services they can offer.

I feel there is significant scope to achieve this by making the in-store customer experience richer and more fulfilling by learning from the web experience.

Like Web 2.0 web-sites, the next generation high street store must demonstrate a better appreciation of the target consumer as a person rather than a product buyer. In other words it must make the shopping experience person-centric by providing space, comfort, information and social engagement, with easy points to call for help, and valid reasons to come in and enjoy the in-store experience for browsers; whilst also providing efficient entry and exit routes for shoppers who know what they want.

Retailers must conversely also appreciate the elements of the shopping experience that make store customers uncomfortable and look for avenues to cut them out, for e.g. not enough browsing space; product overcrowding; help not unavailable at the right time and place; and lengthy purchase queues.

So what could the High Street 2.0 physically look like? Well, one route might be where large stores evolve into experience-focused social spaces with products as a backdrop, while small stores leverage user computing and web technology to shift towards becoming product information hubs where consumers use touch screens to choose what they want to see, try, and buy.

Wednesday, 18 June 2008

Channel Symbiosis and the Next Generation Customer Experience

I believe that at some point in the near future, forward thinking retailers must recognise the fact that the existing model of shops as one-dimensional rooms for showcasing products by category is fast becoming outdated by consumer familiarity with the online shopping experience. On the internet, consumers can access related products, accessories, comparative price options, product information, reviews, simplified purchasing, delivery, and bargains, while also being able to feedback to others about the experience. What they cannot do is try out products for fit, look, appropriateness or ease of use before buying, or even benefit from the immediacy of collecting the item at time of purchase; so it is clear that both channels are not just relevant but highly complementary, and should be treated as such.

However, as far as I'm aware no one has made this leap towards a truly symbiotic, holistic online-offline customer experience. There is absolutely no reason why customers shouldn't be able to shop in-store with the same benefits as online. It just needs a little lateral thinking, starting with recognising that while the Web started out as a separate and independent commerce stream in order that companies could minimise risk while still learning about its capabilities and user models, it is now a well established and experience-driven business and usability model that can and should be leveraged to improve customer experience across channels in the physical world.

Friday, 23 May 2008

6 Keys to Measuring Word of Mouth Online

Some recent research from ForeSee Results shows that nearly 1/5th of all visitors to the 100 top-grossing retail Web sites came by way of recommendation, and those that came from 'word of mouth' were more likely to buy, recommend, return to the site and remain loyal.

Foresee argue that there are 6 truths about word of mouth you should consider

  1. The first is that WOM can't be bought. Com­panies should focus on “earned recommen­dations” — recommendations that follow a satisfying interaction with the company.
  2. Second, more questions are better. It isn't enough to ask a single question like “Would you recommend us to a friend or colleague?” Marketers should also ask how likely one is to communicate about their experiences.
  3. Third, measure good and bad comments. Differentiate customers spreading the “good word” from those spread­ing negative opinions.
  4. Next, use a precise measurement scale like a 10-point scale.
  5. The fifth key is to use a holistic approach. If you also ask about what is and isn't satisfying them, you'll be able to act on that data because you'll know what's driving your customers.
  6. Finally, always remember that satisfaction drives WOM every time, and measuring satisfaction can help you better predict WOM behavior.

Thursday, 15 May 2008

Personalisation vs Customisation - Part 3 - ROI

In terms of customisation, from an online retailing perspective, I don't really see the benefits against cost of development. You could provide a 'Windows Live' type page where users can customise what they see and how they see it, but frankly with mature retailers I don't see who would really use it. Shared personal profiles that users can customise similarly don't really make sense for this type of business, or at least not until social networking in the mature brand shopping context becomes significantly more embedded, if it ever does.

However, simpler customisation linked to personalisation, could be very useful; for e.g. possibly like a variation on the Amazon recommendations model, where the user could be presented with an option alongside product displays allowing them to select items into a 'not interested' and 'I like' category that can then not only automatically build them their own page they can refer to and edit later, but also feeds into the intelligent browsing stuff I was talking about in the previous paragraph - i.e. this information is used to understand what the user is looking for and preferentially feed them those products as they browse or search, thus enhancing the targeted browsing experience.

This could help retailers improve their offering to customers online, increasing not just browse to sale conversions, but also brand loyalty because the customer feels understood.

Personalisation vs Customisation - Part 2 - Implementation

User Experience experts can help with audience segmentation analysis, identifying key audience groups and defining an experience that best fits/targets them. Similar to personas, but a bit more generic and more automated; with some business logic that leverages the user's profile data and preference information along with their browsing habits to present them with the scenario that fits them.

From a technology and business intelligence perspective you could implement real time tracking and analysis of user behaviour, underpinning the automated tailoring of content presented as the user progresses through their experience. Sort of an extension of what I was talking about in an earlier post on the targeted channel experience.

Personalisation vs Customisation - Part 1 - Definition

The issue of differentiating between personalisation and customisation online is one I've experienced in discussion with a number of organisations.

The first problem lies with semantics - i.e. the definition of personalisation vs customisation with respect to the use and design of websites. I see one as automatic audience targeting (personalisation) and the other as the ability for the customer to manipulate the website to fit their needs (customisation).

As a business your first priority is to define your understanding of what each one means so that all parties are working from the same standpoint.

In terms of personalisation as per the above definition then, I believe this is the future of customer focused business intelligence. It is about understanding the customer, either as part of a larger group or as an individual and then presenting them with their own unique customer experience. In the next posts I'll explore how you can implement these and some possible avenues of ROI.

Tuesday, 13 May 2008

Women are not small men!

Developing the targeted channel experience

I was recently reading up on consumer trends and one that caught my eye was the trend towards businesses focusing on the female oriented experience. You've probably already come across taxi firms catering for female customers with female drivers like Lady Mini Cabs in Archway, and of course Sheila's Wheels with its cringeworthy adverts on TV, but it goes much deeper. Pink Ladies is a women only car hire company, Bud Light targets the female audience as does the Rosee version of Hoegarden, and there are any number of female focused sports and leisure businesses like Outdoor Divas with its excellent tagline that I've stolen for the title of this post.

Anyway, this post is not about listing businesses for women (you can read more on that at http://www.trendwatching.com/trends/femalefever.htm) but about making the point that the online male v female experience is not only lagging behind, but once again following physical norms rather than thinking freely and outside the box. Standard Chartered Bank for example has a women only store in India, but has no variation in web exerience. Where stores cater for both men and women, the majority of sites use a one-size fits all design and user-experience approach just like the high street; or you sometimes get sub-sites or variations in design when you enter sections with content specific only to women. This is just like walking into a shop that is split down the middle. Men's clothes on the right and women's on the left with maybe a different colour scheme.

We think differently, browse differently, buy different things, and process information differently so why do we have to work through the same web experience? The whole point of customisation is that businesses understand that one-size never really fits all. It just forces the consumer to accommodate the environment. Unlike the physical store however, nothing limits us from developing user specific websites. With the shift to CSS2, not just presentation but also layout is split from content. It really isn't that difficult to identify and target audience groups and then automate the experience and interface presented for all content, especially for sites where users are logged-in. And even if they aren't, "Are you male or female?" is hardly a long questionnaire to present a user when they arrive at your website.

This is not about being simplistic and changing the colour of web-sites from blue to pink, but about researching and understanding real differences in presentation needs and then developing audience specific features to engage and interact with visitors on their own terms. We are still some way from real time evolution of websites based on the way the user journeys through them (although with improvements in business intelligence and web analytics this may change), and we know that allowing users to select their own preferences is just that little bit too much work for most browsers who will never really bother, so the onus falls on businesses and their user-experience experts to develop a deeper understanding of their user groups and build a dialogue with them on their own terms.

In summary then, gender preferences are clearer than any other demographical difference so instead of the one size fits all approach, why dont we look to tailor the web experience based on the way we browse? It's ok to have women only websites but so far I haven't seen any that allow users to choose a different browsing and information experience based on their age or sex categories. The fear factor here is probably political correctness, but as web technologies get more sophisticated in terms of audience targeting, I'm guessing that it is going to happen at some point so why not be brave and get a jump on the competition?

Monday, 12 May 2008

A Practical Approach to Stakeholder Analysis

What’s the issue?

In the hunt for a decent Stakeholder Analysis template, I’ve found that there are too many options available, written by too many clever people and adapted for too many different applications. Some are too simplistic, and some vastly complex. Every organisation and project seems to have a different template. I’ve come across all sorts of intelligent sounding but essentially pointless terminology for column headings including perceptions, emotions, constraints, influence, motivations, engagement, and commitment. Consequently too often stakeholder analyses fail to end up as the points of reference they ought to be. The way I see it, for delivering small to medium scale Information Systems projects, what we need is a broad, straightforward, filterable, and useful way of looking at stakeholders, particularly in cases where time/support/resource for due diligence is limited.

What’s the real point of the Analysis?

If you are doing this for more than just a formality or high level representation, the real point is to identify and manage the human goals and needs of the project. In other words figure out who’s involved, which group’s goals take precedence, who you need to worry about, and what you need to do about it. It is worth noting that sometimes completely contrary to user-centric ideals, the end-user is not always the primary concern in the short term, with delivery success more likely assured by ticking off the primary stakeholder’s key goals. However this is a highly short-termist view, because in the end if users don’t take to the system, it will eventually adversely affect the key stakeholder, who of course will pass the blame onto design failures for the change in fortune. Longer term credibility can therefore only be ensured through end-user satisfaction, so if you have to choose only one group to satisfy, try and pick them, or at least convince the key stakeholder of their importance.

What is a stakeholder?

From a practical perspective, a stakeholder is any group or individual that is related to the project, either because they impact on it, or are impacted by it. They represent the entire human interface along the route from kick-off, to delivery and end use.

Components in a practical Stakeholder Analysis template

The following covers the range of information that you will find useful to know about the stakeholders that comprise your project environment. Delete or adapt as applicable to your needs. You should be able to outline a lot of the content by just talking to the project owner. An initial draft will quickly throw up the holes in your understanding of the project environment.

  • Group: Depending on whether or not you are dealing with representatives of departments or users, or directly with individuals who represent themselves, this column should demonstrate high level context with titles like Business Group, Business owners, Marketing Managers etc

  • Key Representative: You can add this field if you are dealing with specific individuals and feel that it would be helpful to see how they fit in the overall environment. In this case multiple individuals may belong to the same group.

  • Type: Stakeholders fit into a range of types (sometimes multiple types) as follows: Reviewers, Providers, Related Projects, Output Deliverers, Outcome Accountable, Outcome Impacted, Output Utilisers. Building tick columns for these into your template will allow you to filter by stakeholder type, which is particularly useful when designing communications.

  • Internal or External: External stakeholders can be hard to manage, so it is particularly useful to be able to identify external stakeholders with high impact on the project.

  • Priority: High, medium, or low in terms of how important their goals and needs are as success criteria for the project.

  • Delivery Involvement: Direct or Indirect. Are they directly involved in the delivery of the project or peripheral players?

  • Relationship with / Interest in project: Their role in the project.

  • Goals / Success Criteria: At this stage you will not need to worry about specific metrics, so success can effectively be viewed as the achievement of their goals. You can separate this into another column when you being to understand the specific outcomes that result from these goals.

  • Impact on Project: Details on how they affect the project in terms of role, and responsibilities, or how the project needs to adapt to fit them.

  • What does the project need from this group?: In terms of inputs or support.

  • Impact of Project: How the delivery or end product of the project will affect the user group.

  • Potential Issues or Concerns: What are they concerned about in terms of project delivery and outcome?

  • Needs: What do they need from you and/or the project delivery team

  • Management Strategy / Method of Communication: How you plan to communicate with the stakeholder and satisfy their needs as above.

Here's a sample excel template you can use for stakeholder analysis and management.