To maximize the value of bringing teams together physically, focus on one of three goals. "Doing" involves collaborative work on a key project. "Learning" focuses on gaining business context. "Planning" aligns the team on strategy and roadmaps. This framework ensures gatherings are purposeful and effective.

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.

Address cultural issues by applying product management principles. Use surveys to gather data and identify pain points, then empower the team to propose solutions. Test these ideas like product features and iterate based on what works, making culture-building a shared, active process.

"Shallow fun," like happy hours, offers a temporary high without lasting impact. "Deep fun" occurs when teams collaborate on activities that improve their shared experience, such as researching the best office coffee. The goal is not the fun itself, but the bonding that happens when a group takes ownership of a shared, meaningful project.

Instead of siloing roles, encourage engineers to design and designers to code. This cross-functional approach breaks down artificial barriers and helps the entire team think more holistically about the end-to-end user experience, as a real user does not see these internal divisions.

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.

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.