Serving People and Doing Business in the Experience Economy

Last March I attended the IA Summit 2017 in Vancouver where Elissa Frankle gave the presentation called. All Roads Lead to the Bathroom: Why Thinking of Visitors as People Makes Museums (and everywhere else) Better”

Elissa, a Museum Experience and Education Specialist, shared insightful methods and practices of serving museum visitors, which ultimately match the intended purposes of UX design.

Among other concepts she reminded us that people have physiological needs as stated in Maslow’s Hierarchy of needs. She highlights the idea that we need to think about visitors as, well, people.

She then sincerely asked “What is a user?”

For a discipline that prides itself if identifying and assigning meaning in what it does, this ought to be one the most important questions we ask ourselves for how we serve people in the future as the mediums we work in change from strictly digital to physical environments. Recognizing not only the context in which people live but recognizing them as people with needs .

In my current role, we only refer to our customers or users as “guests.” A term that I have become fully endeared to. When I think of welcoming a guest to my home or our place of business I intrinsically have a feeling of service towards them. It implies a status of how they should be treated and what we want them to feel like when they spend time with our services and products.

What we call the people we serve influences the way we think about them and how we solve problems for them.

“Customers” — is a shorthand for people who pay companies money for the exchange of goods and services.

  • The hospitality and service industries usually refer to their customers as “guests.”
  • Healthcare refers to their customers as patients.
  • The Radio Industry calls their customers listeners

Designers adopted the moniker “user”, discreetly describing the person “using” the tool for a specific task.

“Personas.” were created in an effort to humanize the user and validate their goals. We are now using a myriad of tools and methods in order for us to get into users’ heads, understand them and learn more about them. Tools like customer journey maps, service blueprints, field studies, usability testing.

This brings me to a problem within the UX Design community that I’ve been sharing with others since I had small but powerful experience.

A few years ago while working for one of the largest hospitality & service companies in the world I was taken aback when I recognized that the working language did not include concepts, methods or references from the growing field of service design. I had admired this company’s brand, business and dedication to service and wondered how they had missed these working tools. At one point I cornered a business manager I respected and shared the principles of service design with him. After thanking me for the wonderful storytelling and clear and succinct presentation he shared that the concepts and principles I just presented were “…what we in the hospitality industry call doing business.

I realized then that working in the defense of design, I had been making a prideful mistake. I had been so focused on the dogma of UX Design & Design Thinking that I had been missing a prime opportunity to learn from the best service professionals around. All too often we pat ourselves on the back for being focused on the “user.” Using our design sensibilities and specialized methods to make the best products, we seem to believe that we have the best way to make great products. This is often expressed by terms, tools methods and approaches that get coined as best practices.

In our effort to provide clarity for meaning in digital experiences we ended up creating new vocabulary for things that people live every day. And then we’re surprised when they don’t recognize our own description of their successes. This dedication to the dogma of design then creates an opportunity for misunderstanding if we don’t recognize it and stay dedicated to solving the problem.

Did this company have a holistic view of their business and each touchpoint? Yes of course. Did it look like a customer journey map at the time? Probably not. I’m sure they may have a few now, but the point remains. Design Thinking seems to be the new vocabulary for “doing business” and being customer centric.

Recently this year I saw Jared Spool share the idea that companies must have “infused UX” to accomplish great products that serve the users’ needs and create. Does that mean that a company must have a design team to achieve “infused UX?” I wholeheartedly agree that infused UX occurs in the development of truly disruptive products. But as heretical as this sounds for a career UX designer, I have come to believe the answer is no.

Infused UX does not have to look like the words and the concepts we are telling ourselves as designers. But it does have to be people focused and it does have to solve people’s problems.

A Product Director once shared with me some frustrations she had about working with designers. Stating that “they seemed so focused on empathy for our guests, whom they had only “met” through research but seemed to not have empathy for their partners of the team of different disciplines, with whom they work with every day. Focusing on best practices of Design Thinking all the while forgetting to practice empathy with real people.”

We’ve all gotten caught in the trap of “doing things the right way.” Many years ago, a leader of mine shared with me that in anything there is no perfection. There are less effective activities and more effective activities.

If empathy is the greatest differentiator between Design Thinking and other problem-solving methods, then we must practice it as much as possible, especially with those we work with. In other words, how you treat people around you affect the product you build that mean to serve people.

So, what do we do about this? As in any solution set, the answer lies in small things we can do today to move in that direction. From these experiences, here’s how I expect we might pivot in our working relationships and approach to design in the service of people.

Look at our organizations and see if we can discover activities that are customer focused that may not be recognized as “Design Thinking” activities; highlight them, support them, support the people who make those activities go. Be a part of the conversation. Offer help or at least a listening ear.

There are any number of techniques that could be considered in the Design Thinking wheelhouse. What techniques have room for improvement, can be modified, can be realized in different ways?

Find a way to define the people we serve as people; not just people who do a defined task with our companies once in a while, but as people.

Focus on being more effective, rather doing things the “right way.”

Spend as much time as possible learning the business. What services do they provide that solve people’s problems? How do they make money doing that?

Learn more about your business partners, co-workers etc. Who are they? What have they learned?

Identify where there is evidence of design thinking in your organization, and either leave it alone, celebrate it and/or learn from it, make it better if you can and learn from it.

Focus on the problem space and use everything available to solve the problem.

Interdisciplinary teams must value each member’s knowledge base and contribution equally regardless of where their knowledge base comes from.

Focus on people as people with needs and their problems rather than users and their goals.

Have a service oriented mind.

Whether or not you think your company is doing Design Thinking, the real challenge is to focus on people as people; and solve problems for them.

One last story to bring it all home.

In 2009 I attended DMI’s Re-Thinking Design Conference in San Francisco. Which I characterize as the best Design Managers in the world mashed up with the best MBA’s in the world as an experiment. I heard a business professor describe the first time she completed a card sort. She described it as a very powerful almost religious experience and was very excited to promote how helpful it was. I was once again flabbergasted at the ignorance for something I did almost every day. But I also recognize that I might be as excited about a data evaluation technique that I’ve never done before. And that the key to this was having a breadth of people in the room to share differing opinions finding a way to develop that holistic view. In any case there is no room for pride.

What is Design Thinking? …User Experience Design? Any way you put it, It’s serving people and doing business.

From Mapping to Spatial Interpretation

I recently read A conversation with Ken Jennings and Jesse James Garret.  @UXMagazine about Ken Jennings’ book Mapheads which was published in 2014. They discuss the relationship of maps and design. It reminded me of my early love for maps and the fascination I’ve had with them over time. As quoted from Ken Jennings “…elegance of the map as a solution to a visual problem ‘How do I convey information about the world?’ This is at the core of the UX designers goals.

33a6f0aacf3eb3ac2b3d586d1751efde

Every summer, my family would hit the open road for a vacation that normally included a lot of driving in our Ford Fairmont wagon, stops at seemingly random roadside historical markers and trips to baseball stadiums that were supposedly “on our way” to our final destination.

I lay in the “way back” section of the car, pouring over the intended route while imagining, alternate ways to get where we were going. Reviewing the various map symbols, topography and exchanges almost became another outlet for daydreaming and envision the possible excitement that lay ahead in the journey. It also caused me to think about how I would represent the 5420wisklandmarks as we passed them by and I saw exactly what they looked like. I recognized this desire to store and think about information in a spatial way. Ken Jennings shares his thoughts about it by saying. “That spatial way of storing information is apparently deeply hardwired into how our brain wants to learn things.”

This reminded me of the the quote from UX Researcher Ben Scheidermen  who states “The purpose of visualization is insight, not pictures

fitbitWe see this value being manifest in our products everywhere now. Real-time data in relation to geography and time exposing the state of the environment around us giving us the ability to maximize the experience we live in. Examples include a rise in Data Visualization products like Domo and systems that expose real time data like wearable devices, home automation and  electric connected cars.

Ironically it was all there before. We just didn’t have the ability to expose it in the moment. And now we can tap in to that “deeply hardwired” way of storing information.

just-ui-to-conversational-uiAs Conversational UI, AI and ML become more of a reality understanding how to design great experiences has become more and more about the choices made about what to include and what to strip away.

How does this change the work done as an Experience Designer? It doesn’t. It really just makes it all that  more important. There are now endless opportunities for feedback and interaction with people and our products. As I was once told by a former executive, “It looks like your job is going to get a little harder now.”

I would suggest however that now, more than ever a firm understanding of the core principles of usability are needed to combat the never ending battle against scope creep and adding features because you can, never stopping to wonder if you should.


Other great topics addressed in the A conversation with Ken Jennings and Jesse James Garret.  @UXMagazine 

  • Importance of how visualization of a map influences people’s perception about the concept of topic.
  • Cartographer’s building on top of each other’s work.
  • Marriage of Maps and Mobile devices
  • Importance of geotagging
  • Maps as a metaphor for conceptual journey’s

Looking for some design principles resources?

Try these sites (designprinciplesftw.com), (uxhow)

Can you Hack it?

 

I just spent a weekend engaging with students and hackers at the LA Hacks,Screen Shot 2017-02-11 at 7.15.25 AM.png hackathon on the campus of UCLA. It was both and exciting and humbling event. Watching people bang out working product in 36 hour stretch of time. They had about 90 teams giving it the ole college try.  I was also impressed that the sophistication at which the teams thought about what they were trying to do.

Have you ever done one?

Words that make all the difference

Player Created Content: Resurrecting and old discussion. It’s been said that gamification is dead. Is it true? It’s pretty apparent that just making a leader board or giving nicely designed badges to your users is not going to engage them in meaningful ways. But I believe the principles of behavioral psychology behind this research is still very valid. The question is what is the carrot and what is the stick? Check out this blast from the past video from Amy Jo Kim.

Olympic UX Fail

Normally I don’t like to focus on the negative, but a UX Fail of this nature was surprising. For a site that so many people will be using.

I got this error when I was booking passage to the Vancouver Olympic Events at Whistler. Important to note was that unless you had proof of accommodations at Whistler you could not drive up on your own. They required that you take some sort of public transportation and strongly recommended using the Olympic Bus Network. So when I received this “Purchase Error” several times without instruction on how to fix it, I was very concerned. After calling the Olympic Bus Network several times only to get a recording, I resorted to email as the next quickest option. An email was returned to me stating that there was probably a mismatch on my CC number or Event Code. Now don’t you think that would have been very simple to code in there? As much as I loved my Vancouver Olympic Experience, I have to give this one a big fail.