AMA: Infoblox SVP Product Management, Cisco Wireless, D Matthew Landry on SMB Product Management

(NB: I'm presuming "new" means early-in-career, not new to the company) There are plenty of opportunities to make mistakes. Good PMs are humble, inquisitive, try to contain the blast radius of potential mistakes, and update their priors based on experience. Some common patterns I see in newer product managers: Jumping to prioritization frameworks before understanding the customer and market New PMs get outsized benefits from focusing on customer discovery, market discovery, and developing intuit ...Read More

The impact that a product manager has depends much more on the type of product team and its role in the company than on the company's size. Even for a limited aspect of a product, the PM has an opportunity for tremendous impact when they have responsibility for the full lifecycle and access to the end customer or user. They will be able to generate real insights, solve real problems, and deliver real value. That said, the type of development you get does vary by company size. At a small company ...Read More

The core PM responsibilities don't change. You're still discovering customer problems, defining the product, prioritizing development, and driving adoption. What changes is the operating rhythm and where you spend your time. With enterprise, PMs invest a lot of cycles on individual customer engagement: joining sales calls, responding to RFP questions, navigating multi-stakeholder alignment, and occasionally using the roadmap for a strategic deal. The feedback loop runs through sales, customer su ...Read More

This question implies a tradeoff, but in SMB, retention and acquisition are often the same work. The things that reduce churn (faster time to value, more intuitive product experience, better reliability, fewer rough edges) are also things that improve trial conversion and word-of-mouth acquisition. If your product is losing customers because the experience is frustrating or the value isn't clear, fixing that helps both sides of the equation simultaneously. Harder decisions come around whether to ...Read More

The biggest shift is in how decisions get made and how quickly. In enterprise, you're typically dealing with multi-stakeholder buying (users, decision makers, budget holders, procurement). PMs need to understand how those constituencies interplay and make sure the product and the channel can navigate that successfully. Cycles are long, deals are large, and one customer's needs might meaningfully influence your roadmap. In SMB, the buyer and the user are often the same person. Buying decisions ha ...Read More

When considering to build a feature for a big customer, my rule of thumb: don't build before they buy. If your biggest customer wants something specific, get them to put skin in the game through a services contract or a purchase commitment contingent on delivery. But the real answer is that this is rarely a clean either/or. The question you should be asking is: what can the team work on today that maximizes short-term opportunity without hobbling long-term viability? Small fixes for many SMB cus ...Read More

Product management owns the what and why: the feature set, prioritization, and fundamental value proposition. Product marketing owns the how and to whom: messaging, positioning, and market segmentation. That division applies in SMB just as much as enterprise, but the execution looks different. For SMB, positioning has to be more concrete and oriented to specific outcomes. You're not selling to a committee that will evaluate you against an RFP matrix. You're selling to someone who has a current p ...Read More

This is an area where the PM needs to be pragmatic about the gap between what enterprise customers require and what SMB customers need. Enterprise customers typically have dedicated security teams, compliance requirements, and formal vendor review processes. They'll send you a security questionnaire, ask about SOC 2, expect SSO integration and role-based access controls, and want to know where their data lives. SMB customers rarely have those resources, but that doesn't mean they don't care abou ...Read More

In enterprise, integrations are often driven by specific customer requirements. Your customers have ecosystems of tools, and integrations can make your solution more effective, stickier, or easier to adopt. Sometimes it helps the customer retire custom glue that's challenging to maintain (whether applications or processes). The partnership conversation is often strategic and high-touch with a clear set of initial buyers. In SMB, integrations serve a different purpose. SMB customers are assemblin ...Read More