There’s a particular kind of excitement that comes with having an idea you really like. You can already picture what it will look like, how someone will interact with it, and why it might work. And then you begin making it. That’s usually when things get interesting.
Studying Integrated Design & Media at NYU has encouraged me to work through ideas in different forms: sketching, physical prototyping, creative coding, and interactive experiments. One thing these activities keep reinforcing is that the version I imagine and the version I actually make are rarely identical. Sometimes the gap between them reveals a technical constraint. Sometimes the interaction doesn’t feel as intuitive as it did in my head. And sometimes a different possibility becomes visible simply because the idea now exists outside my imagination.
Making something changes the questions.
When an idea lives only in a description, it’s easy to agree with it. Once it becomes a prototype, people can respond to something specific. They can point to the part that’s confusing. They can try an interaction in a way you didn’t expect. They can show you where your assumptions don’t match their understanding. This is one reason I’ve come to appreciate low-fidelity explorations.
A rough sketch can create a conversation without making the design feel settled. A clickable prototype can reveal navigation problems before anyone invests time in building the complete experience.
And a small coded experiment can help test whether an interaction feels as interesting in practice as it sounds in theory.
A polished screen can be surprisingly persuasive.
I’ve noticed how easily visual polish can make an idea feel finished.
Once something has attractive typography, refined spacing, and carefully chosen colors, it becomes harder to separate the quality of the presentation from the quality of the underlying decision. That’s why I try to keep asking what the design is actually solving.
Does this interaction reduce effort?
Does the information hierarchy make sense?
Am I simplifying the experience, or simply making it look cleaner?
Would someone understand this without me explaining it?
These questions are often more useful than asking whether I like the screen.
Iteration is a way of thinking.
I used to associate iteration primarily with changing a design after receiving feedback. Now I think of it more broadly. Every prototype is an opportunity to learn something about the idea, the materials, the interaction, or the people who might use it. Sometimes that means making a small adjustment. Sometimes it means discarding a direction that looked promising. Neither is necessarily a failure. The value is in understanding what changed and why.
Something I’m learning to practice: Be committed to the problem, not overly attached to the first solution.
