I’ve never believed that creativity belongs exclusively to the cloisters of art. It isn’t some mystical gift bestowed upon a fortunate few, nor does it live exclusively among colors, clever typography, and the posturing of the terminally cool.
Creativity is a tool. A flex of the mind. It becomes especially useful in those uncomfortable places where convention has run out of answers and the usual solutions have stopped working. An engineer confronting an impossible constraint, a scientist questioning an accepted explanation, or a person navigating the contradictions of human behavior might all find themselves exercising it. No paintbrush required.
Admittedly, I’ve spent much of my professional life in a field where creativity is practically part of the job description. It’s reasonable to assume I’ve been giving the proverbial right side of my brain quite a workout. But I’ve always been more balanced than my job title might suggest.
I’m just as fascinated by what happens behind the curtain of aesthetics. The mechanics of a website. The logic of an unfamiliar system. The small, maddening mystery of something that should work but doesn’t.
And there’s a particular satisfaction in solving a problem whose answer can be tested. In finding out not simply whether something looks or feels right, but whether it actually does what it’s supposed to do.
I don’t see these interests as competing with my love of visual design. They’re part of the same curiosity. The questions are different, perhaps, but the pleasure of figuring something out is remarkably similar.
I’ve always been fascinated by the distance between what we expect and what actually happens.
People are especially interesting in this regard. We can witness the same event, hear the same words, and emerge with entirely different accounts of what occurred. We believe in our own experiences. Everyone has assembled a perfectly reasonable interpretation from the information available to them, filtered through a lifetime of experiences no one else knows anything about.
It’s remarkable we understand one another at all.
Design involves a smaller, more manageable version of this problem. At least, we hope it’s manageable.
A client has an idea of what they want to communicate. A designer interprets it. An audience encounters the result and brings its own expectations, experiences, and assumptions. Something that makes perfect sense to the person who created it can be utterly bewildering to the person expected to understand or use it.
I’m interested in all sides of that equation. What did someone think they were asking for? What did I understand them to mean? What assumptions went unquestioned? Was the problem in the design, the explanation, or our understanding of what was needed in the first place?
Sometimes answers are straightforward. Other times, one question reveals six, and what was supposed to be a solution is a hydra.
But I like that. 😏
There is something deeply satisfying about discovering that a problem wasn’t quite the problem you thought it was. It requires a willingness to be wrong, or at least incomplete in your understanding. And I think that’s where curiosity becomes more useful than certainty: it leaves room for whatever you haven’t considered yet.
A substantial part of my career has unfolded outside the boundaries of what people generally imagine design to be.
I taught myself web design and development because I wanted to understand how to build the things I was designing. Knowing what something ought to look like wasn’t enough. I wanted to know what made it work, what made it fail, and what I could do about either possibility.
That instinct has led me through unfamiliar software, tangled code, broken layouts, and the occasional problem that seemed determined to defy every reasonable explanation. I’ve spent plenty of time reading documentation, testing possibilities, undoing my own mistakes, and discovering that the thing I was trying to fix wasn’t necessarily the thing that was broken.
But the technical work has also changed the way I think about the visual work.
A design doesn’t exist in a vacuum. It has to accommodate real content, actual devices, different people, and circumstances that rarely resemble the perfect conditions of a mockup. A beautiful layout that falls apart when someone increases their text size isn’t quite finished. Neither is an elegant interaction that leaves its user wondering what to do next.
Constraints can be frustrating, of course. They can also be wonderfully productive. Sometimes they force you to abandon the first solution you fell in love with and discover something better.
I’ve found that the same principle applies to working with people.
Clients don’t always arrive with neatly articulated requirements. They arrive with ideas, intentions, preferences, and sometimes conflicting expectations. Making something useful out of those conversations requires careful listening, asking better questions, identifying constraints, and finding a workable path from an idea to a finished result.
There’s also the less glamorous machinery of professional practice: organizing projects, coordinating schedules, managing revisions, resolving problems, and making sure the work actually gets delivered.
I’ve worn enough hats to wonder how much a job title can reasonably be expected to contain.
None of this is especially romantic. Much of it happens quietly, long before a finished design has anything resembling a finished appearance. But it shapes what the work becomes.
And it has made me increasingly skeptical of the idea that creative freedom means having no constraints.
An empty page can be exhilarating, but it can also be remarkably unhelpful. There are infinitely many directions to take, and no particular reason to choose one over another. A real problem gives those possibilities something to respond to.
The purpose of a design, the people it needs to reach, the limitations of the medium, the practical realities of making it—all of these things create tension. And tension, I’ve found, can be an excellent source of ideas.
Not every limitation deserves to be accepted without question. Some are arbitrary. Some are based on assumptions that don’t hold up under examination. Some are simply the residue of how things have always been done.
That’s another reason I like asking why.
Sometimes the answer reveals a necessary constraint. Sometimes it reveals that the constraint was never necessary at all.
And sometimes it turns out that the problem you’ve been carefully solving is not the problem anyone actually needed solved.
I love the visual aspects of design. The unexpected composition, the small typographic adjustment that changes everything, the strange satisfaction of finding exactly the right shape.
But I don’t think those moments happen separately from the less visible work. They’re informed by the questions, the constraints, the awkward conversations, the failed experiments, and the discoveries you didn’t know you were looking for.
Sometimes the most creative decision is the one nobody notices. Something works, something makes sense, and the person using it never has to wonder why.
I like the idea that creativity can be loud and expressive, or so quiet that it disappears into the usefulness of what you’ve made.
I find both equally fascinating.