Employees can deliver ultimatums (“I’ll quit unless…”), even if that’s not their real intention. Poor communication meets unretractable threats. As managers, we need to avoid panic, listen for underlying issues, and identify solutions.
Occasionally building something unique and small for a single customer makes sense. But enterprise software companies can easily fall into the habit of including custom work in too many of their major deals… with disastrous results. This (long) post lays out root issues and possible solutions.
Product leaders need to push their teams toward regular direct user/customer feedback, unmediated by sales or marketing or support. I’m suggesting one live user interview per week. But how can we find time for that, and make it important enough to compete with other urgent work?
Many infrastructure development teams don’t have a product manager. That forces an architect or senior developer to manage a range of responsibilities they are not best equipped to handle: settling conflicting business priorities; internally “selling” the value of architecture; tying technical decisions to business metrics; making connections between software and end user joy.
Enterprise companies are structurally different from consumer and SMB companies, and product management tools are different – even though we have similar product/market goals. What should B2C product folks want to know before crossing over?
Product managers need to talk — often — with actual end users and buyers. We need to listen, interview, understand and empathize with paying customers. Unmediated by marketing, sales or researchers. What organizational barriers block this essential work, and can we remove some of them?
Your different audiences have different (often opposing) goals and incentives, which means they probably want different product decisions and therefore different roadmaps. You need to understand and anticipate their agendas.
What are the questions that various groups really want to ask, and how does that shape our roadmap conversations?
Enterprise (B2B) sales teams deal with the world one account at a time; product managers deal with whole customer segments. This naturally creates some friction, which good companies anticipate and manage.
Talking generically about ‘customers’ or ‘users’ can generate lots of confusion, especially in B2B or B2B2C situations. We can be more precise by saying doctors, or shoppers, or data analysts, or whatever we really mean.