Skip to main content

Zipcar smashed my enthusiasm

How should a company react to a customer's suggestion?

Since I am only staying 6 months in Washington, I don't want to buy a car. Renting for the duration is expensive. Furthermore, I live on the border between Washington and Maryland -- we won't even talk about the joys of trying to park when two different jurisdictions are involved in policing on-street parking! But life without a car is difficult in the US. So this led me to choose Zipcar - a car sharing service.

Zipcar is really cool: you pay by the hour or by the day. You have a broad selection of cars parked nearby. Just reserve, walk to the car, swipe you smart card and off you go! Couldn't be easier. And you can even use your smartphone as a remote control to unlock the door. The geek in me smiles from ear to ear.

Now they have many models to choose from, but my favorite model is not close by, so I asked them if they could position one to a nearby parking location. Here is how they answered me:

Dear Peter,

Hi! Thank you for the time you have taken to offer your thoughts and suggestions. We sincerely appreciate this, and do take suggestions and input seriously. While we can not act on every suggestion immediately, we compile them all for future reference and planning. If you have any further suggestions please feel free to forward them to us here at Zipcar. If you have any further questions or concerns, please do not hesitate to contact us.

Thanks and have a nice day!

Regards, (name)
Zipcar Member Services

What are people thinking when they write answers like this? This is classic Management 1.0 with a lot of sugar coating on top! It's quite friendly, but the meaning is clear: It ain't gonna happen. Ice water. Disappointment.

Now, I have really don't have anything bad to say about Zipcar. But my inner self is saying, 'yet another soulless corporation'. In my eyes, Zipcar's NPS rating has gone from 10 down to 7.

Let me tell you another story: I was an early adopter of Target Process. I had an idea for a feature which I communicated to TP. It was simple and made TP much easier to use (at least for me). They put the suggestion on a site where their customers could vote on the suggestions they liked best, and in each release they implemented a few. In the next release, there was my feature! They may even have skipped the voting process - it was a real win. In fact, in happened so fast, I am not sure they did it for me. But who cares? I spent the next two years telling people about 'my feature' in Target Process and how cool TP was that the reacted so quickly.

A suggestion is an opportunity to delight a customer. A suggestion is an opportunity to win an evangelist.

Since then, I have always encouraged Product Owners to include some 'sweets' for their customers in each release, just so that the customer can proudly point to 'their' features in the product. It does wonders for your customer delight ratings.

When you take the time to make a suggestion, what answer would you to receive? Here's what I would like:
Dear Peter,

Thanks for you suggestion! Delighted customers customers are top priority at Zipcar. I have checked on availability, and we can put your favorite car at a nearby location within 30 days. We'll leave it there for three months, and if the demand justifies it, it can stay there permanently. I hope you enjoy the car!
If you have any further questions or concerns, please do not hesitate to contact us.

Thanks and have a nice day!

Regards, (name)
Zipcar Member Services

You can bet I'd be telling everybody about 'my zipcar' for months there after, and I would be motivated to drive it a lot. If that happened to you, how long would you be singing the praises of Zipcar?

It is anybody listening at Zipcar? Why don't you try that answer again?

Update 28-Feb: Once this article came out on twitter, their DC Office reacted very quickly and with a smile. Within a week, there was a BMW at my nearest location. Thanks, Zipcar!


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…