What do you think is the most common misconception about b2b products and why?
2 Answers
Asana Director of Product Management, AI • May 17
- One common misconception about b2b product teams is that they should spend most of their time thinking about the buyer (e.g. an executive, IT decision maker) rather than the individuals using the product every day. This misconception arises because in business settings, everyday users sometimes don’t have much choice in the tools they use. However, product teams who focus too much attention on the buyer and not enough on everyday users often end up building products that may get some initial traction, but ultimately become the products teams love to complain about, and in the long run, will stop using.
- We focus on making the individual experience of Asana as easy and delightful as possible, so that everyone using the product can see and feel how it’s making work less effortful every day – even if they’re not the person signing the check.
- Earning customer love and trust at every level creates a solid foundation for growing your relationship and your business. Moreover, B2B customers increasingly expect and review analytics of how their teams are using products, and if it’s clear that the folks at their organizations are highly engaged with a product and love using it, they’re much more likely to remain customers.
1205 Views
MikMak Director of Product | Formerly Discover, IRI • June 10
Misconception: B2B is about selling to businesses and so the end UI/UX is not as important.
In reality, the end user is always a person and there are people that are looking at easy products to use and making the decision to buy from you. The easier your product makes their job, the more inclined they will be to get your products. This applies for products as well as product operations - easy on-boarding, solid customer support and focus on data and reporting as possible.
268 Views
Related Ask Me Anything Sessions

Matterport VP of Product, Preethy Vaidyanathan on Product Management Career Path


GitLab Director of Product Management, Omar Eduardo Fernández on Developing your Product Management Career

Splunk Director of Product Management, Subu Baskaran on Developing your Product Management Career
Related Questions
What ideas or projects would you try to take on and lead after landing your first product management role?How do early career PM's proactively learn about skills that take them to the next level. How do they develop them. How do you overcome domain hiring bias while looking for product roles?How has being a parent changed your understanding of the world, you as a person?As a product manager, how to get better at framing and articulation? Any framework? How do you measure your own success in your role and how much have those performance indicators evolved as you grew within your role?