CX observations en route to Dallas

I’m attending the POD Network 2014 conference in Dallas this week.

All the service design and customer experience design exploration and reading  has sharpened my attention to detail  as I was on board two United flights.

Now I understand why Andy Polaine uses air travel as his go to example for service design workshops.

On check-in

I got stuck some weird Kafkaesque online check-in interface that required me to select a list of visa options, none of which applied to my situation. I gave up in frustration and checked in at the airport.

 At the airport

The attendants berated passengers for not using the self-serve kiosks to check-in and weigh their baggage. It took an hour and a half to self-check in, navigate the queue to the secondary check-in with the attendant, and navigate the border and immigration.

On the first flight

1. The cabin crew on my flight from Vancouver to Houston used the discourse of safety to discipline passengers as they went about they work. We were extolled multiple times to “watch your elbows, shoulders, legs….” The discourse of safety came up again when the crew had to stop its work mid-service because of turbulence. I’m all for being vigilant about the safety of passengers and crew, but when it shifts over to hyper vigilance it creates a bit of a weird dynamic. I wonder if there might be a more customer-centric way so the focus is on customers rather than on the implications of turbulence on the crew’s workflow.

2. A more serious CX moment was a behaviour some of the more experienced cabin crew on the flight exhibited. They made relentless requests to passengers to specify exactly how each person takes coffee an tea. The crew was trying to encourage people to volunteer the details without having to ask. One attendant even sarcastically praised a passenger for doing what she had asked. Obviously United doesn’t want to waste sugar packets, stir sticks and creamers. But maybe the staff shouldn’t grouse about asking people how they prefer their beverage.

3. Did I mention there was no in-flight entertainment. What happened to the movies, music and shows? I guess United assumes passangers bring their own devices.

On the second flight

3. The gate attendant let us board the flight before the security sweep of the plane had been completed. We all had to leave the plane and stand on the gangway for 5 minutes. She apologized for the mistake, but another passenger noted that the plane had been at the gate for 90 minutes before we attempted to board.

4. The weirdest moment of the day was when the male attendant on my short-haul flight into Dallas lip-synched the entire safety announcement, which happened to be narrated by a woman.

All in all, these flights featured more turbulence and worse customer service than I can remember. Clearly I don’t fly enough to recognize what is normal, but I think United has endless CX work to do.

In contrast, I drooled when I saw the Virgin America departure lounge at Love Field. They have mounted a cool collection of framed art on the wall and the place looks downright hip compared to the bargain basement blandness of the United spaces.

Getting to the hotel

If somewhat asked you the difference between a hotel shuttle and a ride share van what would you say? At Love Field, I learned these services stop in different locations and mean very different things.

I took a ride share van to my hotel. It was  a sorry example of disorganized service. There were three drivers with android tablets mulling about on the tarmac. My driver was clearly the most experienced and was trying to help his colleague know where to go. But they clearly didn’t have an automated system for grouping customers going in similar directions. We sat in the van for 10-15 minutes while they figured it out amongst themselves.

Seeing that helped me appreciate what Uber is trying to do for transportation services.

Ultimately our driver was polite, efficient, and I enjoyed seeing how tablets are being hacked by entrpreneurial transportation companies to manage point of sale, logistics and way finding on the dashboard.

It should be an interesting week in Dallas. I will keep my service design goggles on and perhaps compose a response to James Tyer’s post on applying the 70:20:10 framework to conferences. POD has a reputation for being extremely interactive, so it may offer a counterexample of how to do interactivity at conferences well.

Reforming government services and reforming university services

Gordon Ross and Jess McMullin shared some terrific links from the recent Code for America conference in San Francisco.

Tom Loosemore’s keynote on Government Digital Services in the UK was memorable for a couple of key points:
1. Transforming government service requires breaking down the caste system and silos between policy makers and front-line operators. To reform a service, all stakeholders must be at the planning and design table. Loosemore notes a key first step is for all stakeholders to attend to policy intent and for all to address user needs.

2. Loosemore talks a lot about GDS and Gov.uk as as a platform for service and the need for some parts of government to reshape themselves to cut across traditional organizational silos and boundaries between discrete castes amongst categories of government workers.

Loosemore’s talk about service transformation resonates for higher education because it challenges professional staff to consider how we might think about education as a horizontal service platform and how we might work towards integrating and reducing boundaries and hierarchies that lessen or weaken the value of the learning experience for students or scholarly experience for academics.

I am aware of at least three institutions that have already taken first steps towards using service design to ameliorate user experience in higher education: University of California Berkeley and University of Derby, and Queen’s University, Kingston. Faculty and staff at all three have started by addressing the experience for students interfacing with university systems. What I have yet to find is an example of higher education service design that integrates a focus on students experience and also addressin the complexity of university organizations and other user communities that comprise them.

Loosemore’s call for design teams to turn to policy intent led me to the insight that higher education professionals and faculty can and should attend to the fundamental principles underlying the organization and institution they are working within. In my case, that means not only attending to the dark matter of SFU policy but also the well-articulated mission and values of The Beedie School of Business. If users spend the time at the outset of a project reconnecting with fundamental policy commitments and principles that might clarify the path and direction for a specific curriculum initiative.

Finally Loosemore’s talk incudes a memorable quotation about the value of starting with policy and working forward to address user needs:

“You would be surprised at the detritus of accreted nonsense that you can strip away.”

Innovators, read Michael Quinn Patton

At the urging of my friend and colleague Barb Berry, I recently read Michael Quinn Patton‘s book Developmental Evaluation.

It has been a long time since I have read a professional text with as engaging a style and tone.

What challenges me about Patton’s book is that it addresses evaluation work at a high level of sophistication. It assumes readers are capable evaluators and explores the practice of evaluation in a way that focuses on the why? rather than the how. True the book offers lists of possible evaluation frameworks and describes cases and examples of how complexity concepts may be applied by evaluators, their clients, and collaborators. But, even though I am a dabbler in the field of evaluation, I appreciated not being told what to do and rather being able to reason my way to what might work in a given situation.

The book has resonated as I have gone about my week observing an innovative program and offering just-in-time developmental feedback to the people involved. It has primed me to attend to the emergent, unanticipated outcomes and situations and the obstacles that they have created for people.

Patton’s book will resonate for anyone who is working to develop a social innovation. It persuades me that there is value for an insider/outsider evaluator on high stakes innovation programs. Patton’s book will appeal to innovators who are already inclined towards complexity, systems thinking, and other outside-in ecological ways of looking at growing a product, service or program. Cynefin practioners may appreciate Patton’s application of Snowden and Boone.

For pioneering service and strategy designers, developmental evaluation offers ways to evaluate the impact of service and strategy prototypes and innovations. If a future goal of service design agencies is to take service designs all the way to implementation and evaluation, developmental evaluation should feature on user research teams’ learning plan.

Service design and organizational change

IMG_2698.PNG

I’m drawn to creative people and to organizations seeking to design systems and solutions, to implement them, and to effect change.

Through my work, I’ve become aware of the gaps between developing coherent strategy, a kernel, as Richard Rumelt suggests and the endless complexity of implementation. Without strong shared commitments, teams dissolve into coalitions, people reenact learned habits, and conversations turn prematurely to the IKEA-instruction sets of implementation.

Service Design: Insights from Nine Case Studies offers an interesting collection of service design project descriptions, methods and interviews surrounding a public transit service design initiative in Utrecht, Netherlands. A recurring theme in the collection is the challenge of achieving consensus and buy-in from stakeholder organizations, particularly in the early stages. Co-creation and visioning workshops were among the most successful ways of bringing people together and moving forward. Reading the project reports persuades me that leadership team coaching offers a powerful set of tools for facilitating collaboration amongst design firms, client organizations, people and users, and other stakeholders.

Planning demands that teams step out of time and context and park egos and agendas, at least momentarily, to envision shared futures.

As another example, Kronquist et. al describe the challenges of aligning all the factors to “go all the way” and implement service design innovation. To create an innovative pharmacy required significant commitments amongst the pharmacy brand, the individual pharmacy owner, and the employees and customers.

What are your insights about initiating successful service design collaborations?

Tools for Service Design

My consulting practice centres around User Experience Design (UX) and Service Design.

I’ve created a mural on Mural.ly to share my favorite resources on these area of practice. You are welcome to browse:

Here are three places your can start learning:

  1.  Service Design Network. This organization connect service designers from around the world.
  2. Smashing Magazine. The UX Design section of Smashing Magazine regularly features useful posts on user experience design approaches.
  3. Service Design Tools. This collection of communication tools demonstrates the many ways you might represent the system you are aiming to create.