35 years of product design wisdom from Apple, Disney, Pinterest, and beyond

Design is clear thinking made visible.

Design is not merely visual polish; it is the intentional act of imagining the future you want to live in and then taking the steps to make it real.

Why: This mindset aligns the entire organization around a shared future state and integrates decisions across vision, mission, tenets, strategy, and execution.

"Design is trying to imagine the future you want to live in and then take the steps to make it real."

Design must be in the root DNA from day one; it cannot be grafted on later.

Companies that are design-led (not necessarily designer-led) embed design thinking from founding. Apple, Airbnb, Patagonia and Porsche exemplify this coherence.

Why: Post-hoc design injection creates fragmented products and diluted vision; early integration enables small, aligned teams to ship faster and with higher quality.

"I've never seen somebody grafted on after the fact. It's there at the beginning in the root DNA or it doesn't exist."

Keep inception teams tiny until the vision is crystal clear; scale only after clarity.

The original Mac was built by ~20 people; the iPhone core team was ~24. Large groups slow discovery and dilute creative genius (Brian Eno’s “scenius”).

Why: Small teams foster collective genius and rapid iteration; once the vision is fixed, larger teams can confidently execute their slice without ambiguity.

"You get the Beatles with four people. You don't get the Beatles with eight people."

Replace vague principles with opinionated tenets that force daily decisions.

Tenets are decision-making tools (e.g., “documentation is a failure state,” “start simple, let users opt into complexity”). They settle debates once and for all.

Why: Principles like “simple, clear, beautiful” are unarguable platitudes; tenets create a shared compass that lets distributed teams move autonomously yet coherently.

"Tenets are really decision making tools... nobody would ever argue the opposite [of principles]."

Every frustrating interaction steals emotional energy from real life; we have a moral obligation to give it back.

Modern users endure hundreds of digital interactions daily; each poor experience saps energy they’d rather spend with family or passions.

Why: Software is an anonymous medium—creators rarely see the cumulative human cost of bad UX—so we must proactively design to restore, not drain, users’ lives.

"We have an obligation as product people to put that emotional energy back into people's lives."

Design should report to engineering (or be phase-zero of engineering) to guarantee what ships matches intent.

When design sits inside engineering timelines, constraints, and culture, engineers are partners from day one, reducing late-stage surprises and resentment.

Why: Engineering brings feasibility and cost reality early; design retains influence over the final shipped experience rather than handing off specs.

"Design is most successful at impacting what ships at the end if design is considered phase zero of the engineering process."

When moving companies, carry values (e.g., user excellence) but recalibrate behaviors to the new culture.

Apple alumni often fail when they transplant Apple behaviors (direct, intense debate) into cultures that prize different interaction styles (e.g., Pinterest’s “say the hard thing” posters).

Why: Behaviors are culture-specific; values are portable. Re-learning expression prevents “bouncing off” the new culture and increases odds of success.

"Hold on to the values, but not the behaviors."

Make engineers and PMs fall in love with the idea so it becomes part of their soul, not mere buy-in.

Early, ambiguous collaboration with “creative technologists” who can dwell in uncertainty ensures the eventual solution feels co-owned.

Why: Order-taker dynamics produce mediocre execution; co-creators defend and enhance the vision under pressure.

"It's not a matter of getting their buy-in, it's a matter of them being a part of it."