Skip to main content

Ask Then Tell

As I've mentioned, SPIN Selling describes a sales process based on questioning and listening rather than telling. Many of the lessons apply to product management as well.

Now, Kristin Zhivago shares:
Salespeople like to talk, and they need to make a sale. Combine this character trait and this need, and you get the typical unsuccessful sales interaction. The salesman talks and talks, while the customer is standing there with all sorts of questions. The salesman doesn't answer the questions the customer has. The salesman answers the questions he thinks the customer has.

Truth be told, he answers the questions he has answers for.

Not only does he fail to answer the customer's actual questions, but as he prattles on, he adds to the customer's concerns.

By the time his verbal spring winds down, the customer has decided that she doesn't want to buy anything from this salesperson or his company, or that the product or service isn't what she wanted anyway.

So she walks away. The salesperson doesn't understand why. Sometimes he finally starts asking questions as the customer is drawing away. But it's too late then, because the customer has already rejected the salesperson's pitch and is making her exit.

What he should have done is start with questions.

[I thought I came across this piece via Steve Johnson's blog, but I can't seem to track down the post so I can cite it.]

Comments

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

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing
2 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardw
8 comments
Read more