The Studio — Design Thesis

The Wall Is
the Job Description

The boundaries between designer, engineer, and PM aren't about skill — they're about what each role can't do. AI tools are dissolving those walls. What's left is one thing: builder.

Diagram 01
Walls Define the Role

A role isn't defined by what someone can do. It's defined by what they can't. The wall between disciplines is the job description itself.

The Walled Model
Designer
Draws pictures of what code should produce.
Defined by: Can't write production code
Engineer
Interprets pictures as best they can.
Defined by: Can't design
PM
Orchestrates from the middle.
Defined by: Can't do either
Walls Come Down
Builder
Engineers can design better. Designers can build. PMs can do both. When the walls disappear, what's left isn't three separate roles — it's one thing.
Three roles, three walls
One role, direct engagement
Diagram 02
The Abstraction Gap

A button isn't a rectangle. It's two completely different abstractions of the same thing — with no shared grammar between them.

Figma Abstraction
Auto-layout frame
Nested frames + padding
Color styles + fill
Text layer properties
Component variants
Prototype interaction
Lossy
React Abstraction
<button> element
CSS box model + flexbox
Design tokens + CSS vars
Props + event handlers
Component state
Accessibility attributes
AI coding tools are the translator. They convert natural language into real divs, CSS, and component structure — bridging two languages with no shared grammar.
Diagram 03
The Material Has Changed

The material of design has fundamentally shifted. If you're designing in static mocks, you're shaping a replica — not the real thing.

01
Industrial Era
Physical Material
Wood, metal, plastic. The designer shapes the material directly. Form follows function.
The product is the object
02
Digital Era
Pixels
Screen-based interfaces. The designer creates visual representations of interactive systems.
The product is the screen
03
AI Era
Data
Real API responses, real LLM outputs, real user inputs flowing through real logic. You can't mock intelligence.
The product is the intelligence underneath
Diagram 04
The Friction Frontier Has Shifted

It's now as cheap to make the thing as it is to argue about a picture of it. The expensive part has moved.

Before — Pre-AI
Building Expensive + Slow
Debating Medium
Taste + Judgment Undervalued
After — AI Era
Building Fast + Cheap
Debating Unnecessary
Taste + Judgment The bottleneck
The risk profile of building has fundamentally changed. The expensive part is having the taste and judgment to know what to build.
Diagram 05
The Building Spectrum

Building isn't one mode. It's a spectrum you bounce between constantly. Knowing which mode you're in tells you what to optimize for.

Mode 01
Zero to One
Experimental. String together APIs, an LLM endpoint, a database. Test if the concept even works. Code is messy. You're learning, not shipping.
Code Quality
Fidelity
Speed
Mode 02
Feature Work
Middle ground. Existing product, new capability. Build with real data, test in context, iterate before pulling in a full engineering team. Hand off a working prototype, not a spec.
Code Quality
Fidelity
Speed
Mode 03
Polish
Taste-driven adjustments. CSS variables, scroll-triggered gradients, transition timing, padding tokens. What used to require a redline spec — you just do it yourself.
Code Quality
Fidelity
Speed
Diagram 06
What's Defensible Now

The pixels aren't defensible. The Figma file isn't defensible. What no model can replicate is what lasts.

Not Defensible
The Pixels
Visual output can be generated. Layouts can be composed. The artifact itself has no moat.
Defensible
Taste + Judgment
The common sense and authenticity that no model can replicate. Knowing what to build, not just how.
Not Defensible
The Figma File
Static mocks are a replica of the product, not the product itself. The spec is no longer the artifact of value.
Defensible
Supercredibility
Having built, shipped, and iterated on real products. Domain-specific sense-making that separates plausible from functional.
The walls are coming down. What's on the other side is a lot of fun — if you engage directly with the material instead of delegating through layers.
The Studio
Design Thesis
The Wall Is the Job Description