Design from the inside

Back to Devoured - May 07, 2026

DEVOURED

Design from the inside

Tech designbackendstartupenterprisesoftware-engineeringproduct

Designers at high-growth startups should work in the production codebase and ship code like developers instead of creating Figma prototypes or building consensus.

What: Author argues designers must work directly in production codebases rather than prototyping tools, using an extended metaphor of redesigning a chaotic office from the inside with tape on floors instead of floor plans. Key practices: work in real codebase with live data, ship code through CI/CD, build rituals organically instead of imposing processes, collapse feedback loops by doing support rotations and writing SQL queries yourself.

Why it matters: Engineering velocity at AI-era startups has outpaced traditional design processes, transforming consensus-building and documentation from coordination tools into bottlenecks that slow teams down.

Deep dive

Core metaphor: Architect hired to redesign chaotic office where employees modified space faster than floor plans could track, bathrooms were duplicated because finding originals was harder than building new ones, no single source of truth exists
Solution: Design from inside using high-viz tape on floors to redirect traffic, close dead-ends, gradually knock down abandoned walls, expand hallways incrementally—each small change reveals new problems to solve
For product designers, code is the tape: make small changes directly to product surfaces that incrementally reveal improvements, ship through CI/CD pipeline like any other code
Work in the codebase: Resist prototyping sandboxes and demo environments—if someone needs to translate your designs into code, you're on the outside not inside
Create tight links: Use real data from actual API endpoints, map design tokens 1:1 between Figma and code, work at realistic screen sizes and conditions
Ship continuously: Put code up for review, use LLM coding agents to turn designs into production-ready code with a few prompts
Build rituals, don't introduce processes: Behave as if the process already exists (make the PRD and send it, schedule the review meeting) until repetition makes it ritual
Collapse feedback loops: Do support rotations yourself instead of waiting for ticket summaries, write SQL queries for usage data instead of waiting for dashboards, instrument product yourself
Don't ask permission or seek consensus: Make the change from inside the product, see what happens, iterate based on real behavior

Original article

Engineers at high-growth startups can build so fast and independently that trying to map out the product area is a lost cause. Architects design buildings from the outside using floor plans and schematics to paint a perfect picture of reality. Engineers have to design from the inside out and make small changes to product surfaces that incrementally reveal improvements. This means creating tight links between design environments and the real product, collapsing feedback loops, and shipping.

Explore all 73 articles in today's digest