Lore

High-Velocity Design Team Practices

# High-Velocity Design Team Practices

Evan Spiegel describes a set of practices Snap's design team uses to keep ideation and output velocity high, resonating with the Organizational Duality: Scale Structure vs. Innovation Structure duality of maintaining a fast, small innovation team alongside a large operational org.

Design Process

Combines Stanford's empathy-driven human-centered design process (deep customer research feeding design decisions, see deep-listening-customer-research) with art-school-style habits: constant output and brutal, regular critique. The goal is quantity of ideas as a precondition for quality — 'if you want to have a good idea, you have to have lots of ideas.'

No-Gate Weekly Critique

A weekly design review where any idea, regardless of perceived polish, can be brought and shared without a filtering or approval step to get on the agenda. Removing the gate lets unpolished or early ideas surface and be evaluated rather than filtered out beforehand.

First-Day Presentation Ritual

New design hires present their own work on their very first day, setting a cultural expectation of high output velocity from the moment someone joins.

Deliberate Design Rotation

Designers are periodically moved across different product verticals (e.g., chat, maps, AR) rather than staying on one surface for years, to keep perspectives fresh and prevent staleness or burnout.

Design was historically an operational bottleneck at Snap — Spiegel frames this as a feature, not a flaw, of maintaining bar and coherence: 'design actually has always operated as like a bottleneck at the company, which is incredibly important.'

Designer Rotation and Early PM-less Culture

Snap deliberately rotates designers across products (chat, maps, AR) rather than letting them specialize on one surface for years — Spiegel argues fresh eyes moving between surfaces matter more than deep tenure on a single one. This pairs with an origin-story detail: Snap reportedly operated with around 200 employees before hiring its first product manager, with designers themselves doing PM-type work (spec-writing, prioritization) in the early culture — design was the default home for product thinking, not a separate function.