Book: SPIN Selling

It's mainly a book detailing how to sell high-value products with a long sales cycle, but SPIN Selling enlightened me in two ways. Not only did it help me understand the perspective of a sales person, it also gave me some deeper insights into product management.

"S.P.I.N." stands for "situation/problem/implication/need-payoff". The idea is that you use a series of questions to uncover the customer's situation, the problems she faces in the context of the situation, the implications (monetarily and otherwise) of these problems, and what she needs to solve the problems.

Though the facilitative process the book details is for sales, many of the same techniques and principles apply to the one-on-one interviews that product managers conduct. I recommend the book.

Comments

Vegas said…

I heartily agree with you - I recently moved from sales into PM, and use the SPIN questioning method when gathering market data and building a case during waves. Huthwaite recently released a new book called 'Escaping the price driven sale' - there are some interesting points in there regarding 'the unforeseen problem' and the 'unanticipated solution'. If you liked SPIN then you will love this book.

Unforeseen problem - the customer has a problem they are either unaware of or have not given sufficient weight to it. This makes validation difficult as you have to build the problem first before they will think that your solution is worthwhile

Unanticipated solution - they have a problem but they are not aware that the product you have solves the problem. This often happens because they are fixated on a particular route to a solution. Sometimes it helps to show that they can achieve the same desired outcome through an alternate route.

What is funny with SPIN selling is that it is actually an old book (20 years or something) - yet when I read it, I still found it to be the best book on consultative methodologies that I had ever read.

Nice blog btw :)

Fri Apr 24, 10:00:00 AM 2009

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

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

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

Cauvin

Search This Blog