Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A few of the ideas, yes, but not the whole thing. But you could probably get those ideas just as easily from the linked summary.

In particular, stuff like digging beneath requirements & feature requests to understand the root cause and their current behavior. And probably also the general idea of opening up a safe space for open learning at the beginning of each conversation (which is also a common idea in other sales approaches like SPIN Selling).

Also, it would be more useful while scoping out a new product/market, and less useful for products that are already mature/defined.

So my guess is that you'd get a couple useful ideas, but not a book's worth.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: