![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgMnKnyTSRbI0C9KAbOB2RWFengnXpQiA8-PZOmg1xSXvaFM8m4nWlSS-xOJnfiQMRfChrCOdkiftZ4t29Esq0XpOL_o-1QLLjIBuLzYFB8inmUHhr18IBdjX1YGD9vZg40OnvRcU_nzo4F/s200/tug-of-war+sales.jpg)
Sure, we may ask on a monthly, weekly, or daily basis about what deals are working, how the numbers are lining up, and or how many customers in a key segment the sales team is seeing. But do we also take the time to ask the sales team about how our products could be enhanced, how our customer service can be improved, or how our response time could be shortened?
A common response to this question I've gotten over the years is usually something like, "Ask our sales team, why would we do that? All they are going to do is complain about our [fill in the blank]". Yet, outside of speaking directly with your customers, your sales team has day to day first hand knowledge of what is happening in the market. Especially in resource constrained companies, the sales team is a quick and inexpensive source of market knowledge.
Consider innovation and product development. Every day your sales team talks to customers about the perceived benefits of your products and handles objections about your products' perceived deficiencies. This is why in product innovation teams I lead, talking with the sales team to get their view of the world is one of the key actions at the front end of the development process. An added benefit is that they are a part of the process for products they will be asked to sell.
Get Going.
I suggest bringing a group of sales people together if possible. As they warm up they will begin to interact, build, and even feed off of each other. Like a classic brainstorming session, one idea begets another and so on and so on. If feasible, have your current product available for the group to touch, feel, and comment about.
- Look for trends in comments: I like to say that one comment is an incident, two are a coincident, three are a pattern, and four are a trend. In qualitative research like this, look for recurring themes and issues, particularly if they come from different geographic parts of your market.
- What benefits do they sell: What are the top benefits of your product that each sells? Though specific product features will be discussed, the benefits are important. This helps break the developers out being focused on product features and instead focus on what the product does for the customer.
- What do you have to defend: Though this creates the slippery slope for the session to devolve into non-product issues, try to keep the group focused on the product itself. The goal is to find the vulnerable areas of the product that customers or the competition bring up.
- Understand the bias of the participants: Many times, the most recent deals that were lost or won may cloud the comments. As a facilitator, probe beyond the initial comments. You may ask, "who else is running into this issue?" or "how often do you see that?"
- Be ready to talk about non-product issues: This is nearly inevitable. Comments on quality, lead time, turnaround time, support, and more will come up whether you want them to or not. Plan for it. Depending on the group dynamics, set aside time either before or after the product session to discuss the non-product improvements. You may be surprised at the opportunities that are uncovered.
- What price means: Price may not always bubble up, but if it does you need to be ready. As you probe, the issue will not be price, the issue will be the perceived value of your product & service offering versus the perceived value of your competition. There may be legitimate issues that are product driven, but there may also be an opportunity for sales training as well.
As a next step, take a look at where your company's next products are in the product innovation process. Have you tapped your sales team's knowledge? If not, how do you bring them into the innovation cycle?