What does the first type focus on according to the speaker?

The first type focuses on implementation support, with engineers delivering features and designers often unable to produce beautiful mocks due to time constraints. The emphasis is on practical, scrappy executions rather than polished decks. Timestamp: 8 seconds.

How is the output of the first type described?

The first type is said to produce scrappy versions of features rather than long, polished designs, because designers don’t have time to lead with elaborate mocks. This reflects a shift toward rapid, in-context product support. Timestamp: 16 seconds.

What does the second type of design work focus on?

The second type centers on creating the vision or direction for things. However, its form is changing due to evolving technology, moving away from long-term, heavily decked visions toward more iterative, near-term guidance. Timestamp: 28 seconds.

How has the horizon for the second type changed?

The horizon has shifted from 2–10 year visions to roughly 3–6 month visions, reflecting faster change and the need to point teams quickly in the right direction. Timestamp: 45 seconds.

What practical alternative to a traditional deck is mentioned?

Instead of a beautifully told deck, the speaker mentions creating a prototype that points people in the right direction as a more practical deliverable. This emphasizes prototyping as a guiding tool. Timestamp: 50 seconds.

Design has evolved into two paths

Lenny's Podcast

People & Blogs2 min read1 min video

Mar 4, 2026|2,019 views|26

Save to Pod

Key Moments

TL;DR

Design now follows two paths: execution support and near-term vision via prototypes.

Key Insights

Design work has split into two main paths: execution support and vision/direction.

Execution-focused design prioritizes rapid implementation and collaboration with engineers over polished mocks.

Vision-focused design is shortening horizons (3–6 months) due to fast-changing tech, not multi-year decks.

Prototypes replace or supplement traditional decks as the primary tool for direction and learning.

Teams must adapt workflows to faster cycles, embracing cross-functional collaboration and flexible planning.

TWO PATHS OF DESIGN

Design work now exists along two parallel tracks: one focused on execution and implementation, and another focused on vision and direction. The execution path emphasizes turning concepts into shippable features, often with engineers assembling solutions quickly and designers pressed for time. The vision path aims to shape the future direction, but its scope is shifting as technology evolves, moving away from distant long-term plans toward shorter, more actionable horizons that prioritize rapid learning and iteration.

EXECUTION-FOCUSED DESIGN

On the execution side, design becomes a collaborator that enables delivery rather than a gatekeeper of perfect concepts. Engineers leverage cloud-based tools and agile methods to implement features, while designers provide lightweight support and guidance. The pace forces scrappy, practical work instead of elaborate mockups or grand narratives. The emphasis is on usability, consistency, and rapid iteration within existing constraints, ensuring features can be delivered without bottlenecking sprints.

VISION-FOCUSED DESIGN IN A SHORTENING HORIZON

The vision-oriented path still seeks direction, but its horizon is shrinking from multi-year bets to 3–6 month outlooks. This reflects how technology and markets evolve too quickly for long, static plans. Rather than crafting a highly polished deck, designers may produce directional prototypes or lean concepts that help teams align, test assumptions, and pivot as real-world feedback comes in. The goal becomes guiding momentum and reducing risk in the near term.

PROTOTYPES AS DIRECTIONAL TOOLS

Prototypes emerge as a primary vehicle for conveying intent and reducing uncertainty. Instead of waiting for a perfect narrative, designers create tangible, testable artifacts that illustrate how a feature could work and what users experience. Prototypes enable rapid learning across product, engineering, and leadership, enabling quicker adjustments and clearer alignment. This shift emphasizes experimentation over exhaustive storytelling and elevates hands-on demonstration as a decision-making tool.

IMPLICATIONS FOR TEAMS AND PROCESSES

The dual-path reality reshapes roles, collaboration, and workflows. Designers must be versatile, fluent in both fast, testable artifact creation and strategic direction. Cross-functional collaboration with engineers becomes essential to translate prototypes into live features. Product management must adapt to shorter roadmap cycles, while organizations adopt faster iteration, prototyping, and planning flexibility. Long-range, static visions yield to adaptable, evidence-driven strategies that respond to rapid tech and market shifts.

Common Questions

The speaker describes two paths: (1) design work that supports implementation and execution, and (2) design work that creates the vision or direction for products. The framing sets up a contrast between building features and guiding strategy. Timestamp: 2 seconds.