In this episode, we are talking about sales people and how product managers can improve their work with sales people. For some product managers, sales professionals are a source of tension, maybe because they overpromise and make product commitments without first coordinating with product management. For other product managers, sales professionals provide access to customers and help arrange problem-discovery interviews. They are an ally to product management.
Regardless of your working relationship with sales professionals, there is room for improvement. To explore this topic you would be hard-pressed to find anyone better than my guest, Keith Hawk. Keith has incredible street cred for this topic as he worked in a technology support role early in this career, working with sales professionals and product management. From there he served as the Director of Technology Support, Director of Marketing, VP Customer Support, and recently retired from his long-term role as the Senior Vice President of Sales for LexisNexis, a multi-billion dollar organization with over 10,000 employees. Keith has a very rich background in the information industry and he has played a broad role in the development of LexisNexis as a company. He is also the author of the book Get-Real Selling: Your Personal Coach for REAL Sales Excellence, which greatly influenced my thoughts on the function of Sales.
Practices and Ideas for Product Managers and Innovators
Summary of some concepts discussed:
* Business-to-Business sales is about one thing – helping to make other people’s businesses more successful. Aspects of this include helping them help their customers, improving the economics of their business, and improving the personal quality of their lives.
* A poor sales person can be thought of as a bag diver – a walking, talking brochure that is just spitting out product features until they find a feature or a product someone cares about — reaching into their bag of brochures over and over.
* 3 things a good sales professional wants from product managers are:
* Availability – open communication to discuss opportunities that may require a new product feature or an entirely new product.
* Interaction – product managers that can interact with customers and understand how customers actually use products and feel their challenges.
* Formalize – define the relationship between Sales and Product Management and schedule periodic collaboration to share successes and opportunities.
* When a sales person overcommits with a customer, promising a capability that doesn’t currently exist, a big girl, big boy talk is needed between Sales and Product Management leadership. Ask if this was our money, would it be in our best interest and the best interest of the customer to create the new capability. A foundation of expectations – values and standards to live by – should exist between Sales and Product Management.
* Product Management and Sales leadership need to set ground rules for customer discovery meetings and general interactions.
* Product managers can have customer discovery meetings with sales people during the early stages of a customer sales cycle, before a sales person has created a recommendation for the customer, without concern of the meeting becoming a sales meeting.
* To avoid Sales too frequently engaging product managers to meet with customers, consider if sales engineers are needed. Also, set an expectation between Sales and Product Management for how much of a product manager’s time can be devoted to direct support of Sales, such as 10% of their time.
Useful links:
* Keith’s book,
Chad McAllister, PhD - Helping Product Managers become Product Masters
clean
40:41
TEI 128: Creating better product teams – with Nate Walkingshaw
https://productinnovationeducators.com/blog/tei-128-creating-better-product-teams-with-nate-walkingshaw/
Mon, 12 Jun 2017 11:50:00 +0000
https://productinnovationeducators.com/?p=11122
Back in episode 121 I had the pleasure of talking with Richard Banfield, one of three authors of the new book Product Leadership. Then, in episode 125 I spoke with Martin Eriksson, who also is a co-author of the book. So, it seemed only proper that I make this a true trifecta by interviewing […]
Back in episode 121 I had the pleasure of talking with Richard Banfield, one of three authors of the new book Product Leadership. Then, in episode 125 I spoke with Martin Eriksson, who also is a co-author of the book. So,
Back in episode 121 I had the pleasure of talking with Richard Banfield, one of three authors of the new book Product Leadership. Then, in episode 125 I spoke with Martin Eriksson, who also is a co-author of the book. So, it seemed only proper that I make this a true trifecta by interviewing the third co-author, which is Nate Walkingshaw. I was especially eager to do this after Richard told me that Nate is the smartest product person he knows. Nate has some firm opinions on product teams and how to structure teams to work well. You may have seen his thought-provoking post on Mind the Product titled, “Agile Died While You Were Doing Your Standup.” In our discussion, we touch on concepts from that post but dive deeper into team structures and needs for modern product teams.
Nate has started successful companies in the medical and fitness markets and has had many product experiences. Later he became the Chief Product Officer for Pluralsight, the largest providers of online technology learning, where he built a user-centered product team. In 2016 his role expanded to Chief Experience Officer where he oversees Development, Content, and Product Marketing.
Practices and Ideas for Product Managers and Innovators
Summary of some concepts discussed:
* Nate’s new book, Product Leadership, is now available. It is the first book focused on product leadership for product managers.
* Software as a Service (SaaS) has forced teams to change. The feedback loop between users and developers is now “end-of-the-day” – hours, not days.
* Siloed teams won’t work today – product teams must be fully integrated.
* Corporate strategy and technology strategy must be aligned.
* The three key elements for teams that increase velocity are:
* Vision – is there a clear vision for each product team and are they connected to the vision?
* Strategy – do team members know the product strategy and how their work fits into the strategy of the team and the organization?
* Autonomy – do team members have the freedom to explore the execution of the strategy for the team?
* Velocity also increases when team members experience first-hand how customers respond to using the product and to changes when they are made. Web collaboration tools are used with customers for real-time interactions.
* Compensate teams, not individuals, for meeting objectives.
Useful links’
* New Book – Product Leadership: How Top Product Managers Launch Awesome Products and Build Successful Teams
* Pluralsite—technology training and where Nate is Chief Experience Officer
Innovation Quote
“In a world of change, the learners shall inherit the earth, while the learned shall find themselves perfectly suited for a world that no longer exists.” ― Eric Hoffer
Thanks!
Thank you for being an Everyday Innovator and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below.