Veeva structures its product teams using a "two in a box" model that pairs a customer-facing strategy leader with an internal product leader. This formalizes the integration of market feedback directly into the development lifecycle, with the strategy role acting as the "glue" across all customer-facing functions.

Related Insights

A strong product-marketing relationship goes beyond friendship. To achieve true alignment, marketing must embed product leaders into their processes from day one, inviting them to keynote jam sessions and press release reviews to eliminate surprises and build shared ownership.

Embed engineers directly with customers to hear feedback and ship solutions, often on the same day. This radical structure eliminates layers of communication (Product Managers, Customer Success) and scales the 'founder energy' of talking to users and immediately building what they need.

To keep growth aligned with product, foster a shared culture where everyone loves the product and customer. This isn't about formal meetings, but a baseline agreement that makes collaboration inherent. When this culture exists, the product team actively seeks marketing's input, creating a unified engine.

Rainbird hosts 'fly-in' events, bringing customer groups (like architects or contractors) to its headquarters. These events include an 'innovation lab' where product managers showcase early-stage concepts under NDA. This institutionalizes customer feedback, making it a predictable and recurring part of the development process.

Oshkosh's CVC team is a hybrid, not siloed in one department. It includes members from corporate development, a venture lead in a tech hub (Bay Area), and a counterpart in an engineering business unit. This structure ensures that strategic goals, technological feasibility, and market deal flow are constantly aligned.

Rippling structures teams into business units led by GMs who oversee product, sales, and implementation. This is driven by the belief that a unified team focused on a specific customer problem (e.g., IT) delivers a superior end-to-end experience compared to a traditional matrixed organization.

The 'CEO of the product' metaphor is misleading because product managers lack direct authority. A better analogy is 'the glue.' The PM's role is to connect different functions—engineering, sales, marketing—with strategy, data, and user problems to ensure the team works cohesively towards a shared goal.

To build trust and deliver value, product managers cannot be 'tourists' who drop in on other departments transactionally. They must become 'locals'—deeply integrated, trusted partners who are regulars in cross-functional conversations and are seen as being 'in the battle' together with sales, marketing, and other teams.

The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.

Optimal product leadership structures separate the long-term, visionary role from the tactical, execution role. One person focuses on the big picture and selling the future ("the house"), while the other translates that chaos into immediate, actionable work ("fixing the walls").