Traditionally, user-focused activities have been conducted by specialists who either move from research to design directly themselves, or who pass the baton to others. This is partly a factor of history, but with UX now in the business mainstream it’s increasingly important to bring others closer to customers and their lives. Collaboration with stakeholders is king, but how do you do this smartly when we all have too much to do and too little time to do it in?

Why is collaboration so important?

Often product managers and those responsible for success are primarily understanding their customers via metrics such as CSAT and NPS. These are deliberately simple, but create a challenge in understanding the why behind the what, which is crucial for identifying low-level change that makes a difference.

Involving users is the key to overcoming this, but techniques for doing so owe a huge debt to an academia and rigour in experimental design. Anything involving real users or customers is moderated by specialists, with stakeholders disconnected behind a one-way mirror or getting their understanding from an after-the-fact synthesis. There are very good reasons for this, as anyone who has seen stressed product managers observe their ideas being casually dismissed in a user session can testify.

However as UX moves out of labs and into mainstream business, UX activities can’t be solely conducted on this basis. There are too few UX professionals, who are in evermore demand as it becomes a mainstream concern. Also, an increasingly multi-touchpoint world means that knowledge needed to make products more effective for their users becomes increasingly diffuse.

So why doesn’t it happen more?

Most product owners I’ve met are smart and keen to understand their audiences as much as possible, but commitment is variable. Making time is the key challenge. But there are a number of ways to bring them close to users and it’s important to offer options that are easy to access and calibrated to the time available.

Some suggested activities

Smart observation of user sessions

User research is often conducted in viewing facilities designed to make observation simple and comfortable. However, stakeholders often don’t have the time to watch them all.

You can help those dropping in by using post-it notes to construct a running analysis on the walls so anyone dipping in and out of sessions can get a concise understanding of what’s been happening.

If stakeholders can’t attend, sessions can be securely video-streamed live, or made available online afterwards. Time is always a pressure, so we’ve found its very useful to provide a one-two sentence summary of each session, pointing users towards key moments.

Attending ethnographic research

It’s becoming ever-more useful to understand user needs by observing them in their own environment. We’ve seen some revelatory moments for clients when they come with us. For example, the moment one client saw users find a helpdesk number via web search, rather than the Help Centre that had been built for them. They’d previously been mystified by CSAT complaints that the number was hard to find (it was on the Help Centre home page), until they saw in real time the many steps needed to reach that content.

Inviting stakeholders can give them a deeper understanding of user needs, but there are practicalities as observers meet them face-to-face. An effective observer briefing is very important in helping observers to attend without unduly influencing whats happening. We’ve also found it’s helpful to give observers a role and reason for being there (from the user perspective). Photos and video are immensely useful artefacts to gather, so giving observers the role of capturing these can be very helpful for all concerned.

Involving stakeholders in user diaries

Online user diaries are an immensely helpful way of capturing relevant user behavior over time. Diaries can be shared with stakeholders, to help them build their understanding, ideally in daily chunks. User photos taken by smartphones can be a particularly interesting and easily digested dip into user lives in unexpected ways. For example, on one project users supplied screenshots from an app which answered a design question we weren’t aware of – should they optimize for landscape or portrait views?

Stakeholders can also be encouraged to join diary studies as participants. While care is required in handling their results, diary participation can help even the most knowledgeable product owners reflect more on use.

Involving stakeholders and users in workshops

User needs and design workshops, synthesizing user experiences and identifying next steps are typically conducted without users being present. This is a missed opportunity. For example, in journey mapping workshops, we’ve seen stakeholders often able to identify customer touchpoints and possible issues, but have a much harder time understanding customer impact and so make changes that will really make a difference.

If you are trying to understand a user challenge, prioritize these, or design solutions, it can be immensely helpful to have real users participating in the exercise. We’ve seen vague design ideas discarded for internal reasons which triumphantly re-emerge and develop after working with customers. It requires careful briefing and facilitation, but it’s rare for participants to come away from these and not be genuinely stimulated by the event, particularly around emotive issues such as complaints handling or anything involving health.

Create informal programmes to understand users

Product managers, IT, Marketing and Operations staff may all be true professionals, but working on products they’ve not directly experienced themselves. Encouraging product use and particularly informally observing real use before a project starts can build invaluable empathy and knowledge.

A great example of informal product observation is the Follow Me Home programme run by Intuit, which has helped them to create industry-leading software. Staff members are encouraged to periodically visit real customers using their products.

Encourage a user-centred culture

Even periodic customer visits require a commitment and desire to understand the customer experience first-hand, so those involved need to perceive a value and make the customer experience the responsibility of all staff.

Internal training, mentoring and skills building workshops can be an important activity for a UX team. It increases commitment and also equips product teams with some basic skills to do some of their own research. While their time and capability to do so may be more limited, the more customer research, the better the product or service will be.

For more on this topic and others like it, join us at Customer Response Summit Las Vegas – February 6-8, 2017 at the ARIA Resort & Casino in Las Vegas, NV.

The post Bringing stakeholders close to the customer experience appeared first on Execs In The Know.

The following is a guest blog by Simon Herd, Director of Design Research at Sutherland Labs. For more information on Sutherland Labs, visit http://www.sutherlandlabs.com/. 

Many organizations have set up customer experience (CX) programs in the last 5 years, and they’re to be congratulated as it’s an important step to becoming an experience-led business.

CX programs don’t realize ultimate impact immediately, they have to prove themselves and earn trust within the organization and become true masters of their domain. Furthermore, the massive demand for talented CX professionals means that it can be difficult to get the right capability up and running quickly.

But once you have your team in place, how do you make sure resources are being directed in the right areas? Here are a few pointers for executives to watch for to help prioritize where CX capabilities should be directed to increase impact.

1. NPS/CSat scores but don’t have a clear sense of the why

NPS, CSat and other metrics are great as a warning signal of troubled waters, but they are limited in terms of understanding the ‘why’ – what’s motivating a positive or negative score? Engaging directly with customers to get to this ‘why’ – how people use services, when and where – gives context not only to negative scores, but also allows organizations to understand and build on positive experiences. Complementary activities such as social media analysis can add weight, but closer collaboration between CX and analytics teams is key to realizing a holistic view of the entire customer experience.

2. Journey maps that have been created without direct user engagement

Customer journey maps are an invaluable tool for aligning vision and road mapping the ideal customer experience. However, maps created only involving internal stakeholders, or using desk research and analytics can miss key insights and opportunities. If your organization has created maps in this way, they may not be in line with customer needs or priorities and there’s a need to get up close and personal with your customers.

3. Organization has too many customer journeys

If you have a journey map for your web experience, a journey map for your mobile experience, and yet another for your in-store experience you may be missing the bigger picture. It’s a common problem with internally focused CX teams and can be a symptom of being product (inside-out) rather than customer (outside-in) focused. Joining up all your customer experiences will help you frame your customer experience strategy and prioritize for impact.

4. Customer journeys are outdated

Remember that journey maps have a limited life span. Just as people’s behavior changes, and new products and services disrupt the competitive landscape, so too will your customer journeys. Journey maps don’t need to be constantly updated but setting realistic evaluation points will help capture the true current experience, and allow you to reframe and rethink your CX strategy.

5. CX teams lack staff who have a background in human behavior

New teams may be formed of members from product manager and marketing-related roles. These are great skills to have represented, but it’s crucial to go beyond this. The skills and mindset to understand human needs, motivations and behaviors are critical to identifying and prioritizing which design changes will have the biggest impact. For example, understanding ‘Motivation’ may not sound like it has a big business benefit, but motivation actually dictates how far customers will persist with a sub optimal product.

6. CX activity is focused at a product or channel level

Many months spent dedicating a team to developing an amazing mobile app can be severely undermined if the wider experience, such as phoning the contact center, is poor. Successful CX strategies seek to understand and optimize the entire customer journey.

7. Customer view based on demographics not needs, motivations and behavior

Behavior based personas based on real research insights provide the best way to understand what matters to your customer, and how to design for them. Traditional demographics are certainly an important element but more secondary when designing to improve customer experience.

8. No time spent observing customers use your products and services

Even the shortest period of time spent watching real use by real customers can provide a valuable reality check to all levels of stakeholders, from developer to CTO.

9. You and your teams don’t use your own products

Question why? This can be a telling indication of something that could be improved, and help align support for change. Aspire to inspire your teams.

10. International organization, but services haven’t adapted to local cultures

Small things can make or break you internationally and what’s acceptable in your culture may not be in others. For example, we recently observed cultural differences regarding privacy in Japan. Japanese customers were horrified if the last 4 digits of their credit card were shown online, whereas European audiences find it helpful.

For more information on customer journey mapping and where to start, join us November 2, 2016 for our webinar “Customer Journey Maps: A Tool When you Want Real Change.” Register now! 

The post 10 signs your CX program needs to work harder appeared first on Execs In The Know.