Even roles far from the customer, like engineering, make countless micro-decisions. Without an intuitive understanding of customer pull—what they're trying to achieve and why they're blocked—these decisions will likely miss the mark, even when just following a requirements document.

Design and engineering teams should stop treating Figma as the ultimate source of truth. It is a simulacrum. The real source of truth is what customers experience in production. Orienting the entire team around the live product ensures everyone is solving for the actual user experience.

Many founders hire UX help expecting a final "graphic design polish" on an already-defined product. The real value comes from a design partner who ideates alongside the core team from the beginning, ensuring the product's structure is coherent before it's built.

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.

The traditional, linear handoff from product spec to design to code is collapsing. Roles and stages are blurring, with interactive prototypes replacing static documents and the design file itself becoming the central place for the entire team to align and collaborate.

Shift the definition of "done" from "code checked in" to "logged in as the user and verified the feature works as intended." This simple directive forces engineers to engage with the product from a user's perspective, fostering ownership and higher quality work.

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.

Technical tools are secondary to building a successful design system. The primary barrier is a lack of shared vision. Success requires designers to think about engineering constraints and engineers to understand UX intent, creating an empathetic, symbiotic relationship that underpins the entire system.

At Snap, all features must receive design approval before shipping. Evan Spiegel views this function as a crucial, intentional bottleneck. While it can slow down development and annoy other teams, he believes it is essential for maintaining a cohesive, high-quality customer experience across the entire product.