Author Archives: leslie

Getting Around the Roadblocks

BarCamp wiki / TransitCampBayArea

I attended the Bay Area’s first TransitCamp last weekend with citizens of the Bay Area to talk with transit organizations using Get Satisfaction.

The two-day event had an interesting and smart mix of people. There were folks there from SamTrans/Caltrain, BART, MUNI, and even city officials like past and current mayors, board members, and advocacy group members. Mixed in with the officials were plenty of concerned citizens, technology folks, designers like myself, and programmers — some independent, some from start-ups.

Tara Hunt enforced the idea that this was a weekend about solutions and not problems, as evidenced by this cute — and effective signage:

By day two, the mantra had sunk in, and everyone was saying it and adhering to it.

We talked about current issues with different transit systems, signage, schedules, numbers of stops, the confusion around multiple systems, the difficulty for new riders getting acquainted with these systems, the politics and budget constraints officials have to work with, how to make these systems more green, and various accessibility issues.

And, I found a few presenters had ideas that really rang true to what we’re trying to accomplish:

There were two “points of pain” that I heard expressed throughout this TransitCamp.

Data availability was the big issue for the application developers trying to make the Bay Area transit system more convenient and easy to use.

Ken Schmier, of NextBus, laid out a framework for an instant messaging system for MUNI riders! Check out his slideshow here. This slide in particular rang true to Get Satisfaction’s ideals of transparency:

The other main point was summed up by this good question: “How do we open up the monolith?”

There are multiple groups working on these problems, both inside the transit authority and outside the transit authority. It’s hard — but necessary — to construct clear lines of communication across these large masses of people and the multiple large, complex, government agencies. Not only is communicating with these constituencies important, but collecting real data to better inform future decisions and raise the level of the conversations is also important.

So, how do we open up this monolith?

Great question. I presented Get Satisfaction both as a suggested solution and also as an example of a system that could inspire better ways of communicating. By capturing the conversations that are already happening without them, communicating with their customers (citizens!), and giving out bits of real-time data that people value, all of these transit systems can pull from the smart ideas of their riders and make a big leap forward.

One key thing about a third-party site like ours is that it allows government employees — who are also citizen-customers – to participate outside of the burden of regulations. Some are on Get Satisfaction already, albeit anonymously. Of course, we really believe that being open about your identity is the best way to get things done, but before an organization has embraced this way of thinking, it’s great that enthusiastic and helpful employees can get out there and get involved.

I chatted with two Caltrain conductors on the way back from TransitCamp, and they both had multiple ideas about how to increase ridership, streamline the business, and make riding Caltrain more fun. That’s not even to mention all the ideas and thoughts I heard from other riders and all the smart people at TransitCamp!

These are great resources that agencies want to tap into, and with Get Satisfaction they have a platform to do so.

[Caltrain, BART, MUNI, NextBus, and TransitCamp are all on Get Satisfaction.]

Customer Service is CTRL+Z for the real world

We all make mistakes. Great customer service is like the CTRL+Z for real life, or Apple+Z for us mac users.

I’ve had three really remarkable customer service experiences this past month. The companies could have refused me service saying that it was simply my mistake: Losing my wallet, showing up for a concert on the wrong day and an application error that led to a misprint on a business card. Instead they did something better.

In all three cases the companies responded with information, help, and forgiveness. A Zipcar employee helped me get back my lost wallet and then even asked me if there was anything else he could do. When I tried to exchange tickets at a concert, Doug behind the desk, helped me understand why it wasn’t possible (even though he really wanted to) and how to make sure I’d have that option the next time. MOO Cards reprinted new cards with no questions asked, no returns required and at no charge.

I know that working on a customer service application makes me more aware of…well…customer service, but it’s also making me more aware of the cases of exemplary service. In the past I only noticed the bad examples. Nowadays, those good examples stand out because I can see what principles are guiding the actions that lead to great experiences. I can connect the dots.

Too often we’re just left frustrated with bad experiences. It can be hard to explain why it was so bad or how it can be better. Hopefully we can stop saying “that sucked” and start saying “that would have been better if they had shared more information” or “that would have been better if they had tried to understand my intentions”. We can change customer service if we have a direction.

It’s my hope that the principles of the conversation-centric approach to customer service enabled by Satisfaction will extend back out to the offline world. Unlike the cold efficiency of the phone tree which seems to have rubbed off on so many in-store service departments, Satisfaction might have a positive transformative effect online AND offline. A return to humanity in customer service through the influence of an online example. This is the kind of web app I’m excited to be building.

-Leslie

“The Challenge of Agile Development: Avoiding Half-Baked Design“ from the Web 2.0 Expo

However you want to frame it, agile development processes are changing the way we make websites. As a designer I’ve been really influenced by the developers on our team, and I learn a lot from them everyday. Today at O’Reilly’s Web 2.0 Expo I got to share some of that learning along with Alex Chaffee of Pivotal Labs. We stressed the idea that design is a group effort more than ever before, and that design is about finding the problem, not the solution.

You can also see the slides here at SlideShare. Let me know what you think! And here’s a hat tip to Leisa who seems to have started the washing machine metaphor.

-Leslie

Satisfaction through design

Howdy! I’m Leslie Chicoine, a designer for Satisfaction. I’m excited to be working with a great team on a simple and powerful concept: people-powered customer service. Part of what’s great about this team is the leeway I’m given as a designer to work collaboratively with the whole team.

Designing a web application can really isolate team members into their screens. We’re fighting this tendency in a number of ways beyond holding regular discussions. On the design side we’ve posted the site map up on a wall with wire frames and screen shots after each iteration so that everyone can discuss the current state of the design. On the development side any team member can check into our Campfire account and get minute-by-minute plain English updates on code check-ins. The point is to give everyone a lightweight view into what everyone else is doing. I’ll talk more about this Agile Design process in future posts.

This working process is similar to our philosophy of better customer service. Opening up walled-in design and development processes leads to seamless collaboration, just like opening up walled-in customer service allows customers to be heard, get involved and share a stake in the results. This makes for happier teams, customers and companies.