We scan new podcasts and send you the top 5 insights daily.
Functional guilds like engineering, design, and product naturally develop divergent subcultures and viewpoints over time. Forcing line-level cross-functional teams to present dirty laundry together every two weeks limits drift, ensures shared alignment on disagreements, and eliminates conflicting 1:1 side directives.
Handing off initiatives across functional silos is typically where product innovation falters. Keeping a cross-functional team—spanning sales, marketing, engineering, and development—intact throughout the entire project lifecycle ensures alignment and delivers stronger product results.
To prevent building great solutions for the wrong problems, structure reviews into two phases. First, a "Problem Alignment" meeting uses data to agree on what to solve. Only then does a "Solution Alignment" meeting review the proposed fix, ensuring efforts are correctly focused.
Instead of relying on ad-hoc updates, hold a formal review at the end of each two-week sprint to showcase completed work and outcomes. Inviting cross-functional stakeholders like the CRO or Head of Product makes them part of the process, gathers immediate feedback, and transparently demonstrates marketing's impact.
Borrowing from design's critique ritual, product teams can present works-in-progress to peers, stating the problem stage, solutions tried, and specific feedback needed. This fosters knowledge sharing and cross-pollination of ideas with low overhead.
To combat departmental silos, the Databricks executive team meets three times per week. Frequent, informal check-ins on Wednesday and Friday are crucial for building trust, ensuring the leadership team prioritizes the company's collective goals ("the first team") over their own departmental agendas.
Departments like IT and Operations often operate with conflicting perspectives. True alignment requires more than sharing views; it needs "microtranslation," where each leader explains their goals in the context of the other's world to co-create solutions.
The best products are built when engineering, product, and design have overlapping responsibilities. This intentional blurring of roles and 'stepping on each other's toes in a good way' fosters holistic product thinking and avoids the fragmented execution common in siloed organizations.
To bridge cultural and departmental divides, the product team initiated a process of constantly sharing and, crucially, explaining granular user data. This moved conversations away from opinions and localized goals toward a shared, data-informed understanding of the core problems, making it easier to agree on solutions.
To combat the slowness of specialized corporate functions, Snowflake implements "weekly war rooms." These meetings unite all stakeholders for a specific product area, forcing a vertical alignment around outcomes. The goal is to plan on Monday and see results by Friday, dramatically shortening feedback loops for new product development.
Netflix holds a weekly product review where PMs present work via a pre-circulated memo. Unlike typical meetings, all attendees, from the CPO down, are expected to have read and engaged with the memo beforehand. This transforms the meeting into a highly collaborative problem-solving session.