Designing on Principle

Open with a specific personal story. An idea you were excited about that never became anything — not because it was bad, but because you couldn’t get it out of your head and into the world fast enough. The energy faded. The moment passed. The sketch is still somewhere in a folder. Widen the lens: this isn’t just your story. Every designer you know has a version of it. We are surrounded by ideas that died before anyone could see them. The question: what if the problem isn’t the ideas — it’s the distance between having one and being able to touch it?

Bret Victor’s principle

Introduce the talk and its central argument: creators need an immediate connection to what they’re creating. When there’s any delay between making a decision and seeing its effect, ideas get lost. Describe (don’t just reference) the key demos: the tree that shimmers when you scrub a number, the platform game where you rewind time, the animation performed by hand on an iPad. Paint these vividly — the reader needs to feel the surprise that only happens when the feedback loop is instant. The line that anchors everything: “So much of creation is discovery, and you can’t discover anything if you can’t see what you’re doing.”

The gap in design work

Bring it home to our world. Where does this principle get violated in how designers work today? The mockup-to-handoff pipeline: you design something static, write a spec, throw it over a wall, and weeks later something comes back that’s close but not quite right. The idea had no room to breathe. The fidelity trap: we spend hours polishing pixels on something we’ve never interacted with. We’re designing blind — the same way Victor describes coding blind. The feasibility question asked too early: “Can engineering build this?” becomes a filter that kills ideas before they’ve been explored. We self-censor based on what we assume is possible. The core problem: in most design workflows, there is an enormous gap between imagining and seeing. And in that gap, ideas die.

Building is thinking

The central argument of the essay: prototyping isn’t a step that comes after the idea. The prototype is the idea. You don’t fully have the idea until you can see it, touch it, react to it. Use concrete examples — ideally from your own work or your team’s:

A time when building something revealed a possibility nobody anticipated from the wireframe. A “happy accident” that only happened because someone was playing with a working version. A concept that seemed great in a deck but fell apart the moment it was interactive — and the better idea that replaced it.

The principle restated for designers: the faster you can close the loop between intention and outcome, the more ideas you’ll actually have. Speed isn’t about efficiency. It’s about volume of exploration.

This is not a talk about learning to code

Anticipate the objection. Not every designer needs to write JavaScript. That’s not the point. The point is immediacy. Whatever gets you from “what if…” to “oh, I can see it” fastest — that’s your prototyping tool. Run through the spectrum: paper and scissors, Figma prototypes, voice memos describing an interaction, acting out a flow with a colleague, AI tools that generate a working version from a description, pairing with an engineer for 30 minutes. All of these count. All of these close the gap. The principle isn’t prescriptive about tools. It’s prescriptive about the relationship between you and your idea. Can you see it? Can you change it and see what happens? If not, find a way.

What boundaries have we accepted?

Shift to the bigger, more provocative argument. Victor’s talk isn’t really about tools — it’s about noticing wrongs that everyone else has accepted as normal. Larry Tesler didn’t solve a known problem. He noticed that modes were a barrier nobody else saw as a barrier. The “problem” only existed in his head until he made the world see it too. What are the modes in our design practice? What have we accepted as “just how it works” that’s actually holding ideas back?

“Designers design, engineers build.” “We need to validate before we invest in a prototype.” “That’s a v2 idea.” “We don’t have time to explore.”

These aren’t laws of nature. They’re habits. And habits can be changed.

The responsibility

Victor frames his work not as opportunity but as responsibility. When he sees ideas dying because creators can’t see what they’re doing, he feels it as a moral wrong. You don’t have to go that far. But take the softer version seriously: if we believe ideas matter — if that’s literally why we’re in this profession — then we owe it to our ideas to give them a fighting chance. That means closing the gap. It means building sooner, exploring more, and refusing to let an idea die just because the workflow didn’t have a place for it.

Close: the idea in your head right now

Bring it back to the personal. Every reader has an idea they haven’t made yet. A concept that’s been sitting in their head, maybe for weeks, maybe for years. The challenge: make it real this week. Not polished. Not production-ready. Just real enough that you can see it and react to it. See what it tells you. End on the Victor note: ideas start small. They need an environment where they can grow. You are that environment. Close the gap.

Structural note: sections I–II set up the inspiration, III–IV make the argument, V handles the objection, and VI–VIII escalate from practical to philosophical. The essay builds toward a crescendo rather than front-loading the principle the way the talk does. The talk can afford to show-then-explain because demos carry energy. The essay needs to earn the reader’s trust more gradually.