Skip to main content

Two Approaches

Back in November, Seth Godin wrote about a frustrating experience almost all of us have shared. You call customer service, navigate a long sequence of touch-tone prompts, only to be informed that the office is closed. In Godin's case, he endured nine prompts.

If a typical product manager or business analyst presided over the development of this telephone navigation system, I can imagine how it went.

"Let me talk to your subject matter experts (SMEs)."

"What are the departments a customer might need to contact?"

"Let's draw a chart showing the different paths through the phone system."

Contrast this approach with the following focus on real requirements. The product manager or business analyst converses with customers and customer support to understand the problems that they are trying to solve and avoid by calling support. The problems don't just include the reason they call support in the first place. They also include potential problems with support itself.

Among the problems that customers want to avoid are:
  1. Spending a long time to resolve an issue.
  2. Expending a lot of energy (by pressing a lot of buttons or having to talk a lot).
Armed with knowledge of true customer challenges, the product manager or business analyst formulates metrics corresponding to these problems:
  • It shall take an average of no more than X seconds for a customer to resolve issue Y.
  • Outside of support hours, it shall take no more than X gestures (button presses, voice commands, etc.) for a customer to be informed that the office is closed.
These metrics are off the top of my head and no doubt could use some refinement. But the point is that the frustrating customer experience Godin described is a result of a requirements failure, a failure to understand and formulate in measurable terms the problems the customer wishes to solve and avoid.

Comments

Craig Brown said…
Good point.

Another performance imension would be completeness of the transaction.

Many many mny customer calls end up with a customer hving to call back to try to get the issue resolved a second time.

Rework numbers I have encounterred usually start in the 30-40% range (sometimes more) when companies start measuring it.
Wed Jan 07, 10:56:00 PM 2009
Anonymous said…
Thank heavens for my (UK) bank, www.firstdirect.com. Always pick up the phone after 1-2 rings. They constantly score high in user ratings even though their website is just about average.

(don't work there just thrilled when a CRM strategy really works)
Thu Feb 19, 11:00:00 AM 2009
Post a Comment

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos...
32 comments
Read more

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...
12 comments
Read more

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem...
9 comments
Read more