How I think
before I make.
Good process is invisible when it works. What follows is not a methodology in a box; it's the pattern that has emerged from eighteen years of figuring out what actually produces good creative work.
01
Listen before looking
Good creative work starts with understanding the problem, not rushing to solve it. I spend time listening to the brief, asking the uncomfortable questions, and making sure we agree on what success actually looks like.
02
Research & context
I dig into the category, the audience, the competitors, and the cultural context. Work that ignores its environment is work that disappears into it.
03
Concepts before craft
Before touching software, I work in words and rough sketches. The idea has to be strong enough to survive being described out loud. If it does, execution follows naturally.
04
Iterate with honesty
Feedback loops should be honest, not diplomatic. I present work with context, explain my reasoning, and make space for pushback. The best outcomes come from genuine dialogue.
05
Craft with care
Details matter. Kerning, margin, hierarchy, colour relationships. The difference between good design and great design often lives in the things people feel but don't notice.
06
Deliver and transfer
A project isn't finished when the files are sent. I make sure the work is properly documented, the people running it understand it, and the system can grow without me in the room.
Things I have found to be true across every type of project.
The brief is usually a symptom, not the problem.
What a client asks for and what they actually need are rarely the same thing. The first job is always to understand the real problem. Sometimes that means pushing back before a single pixel is moved.
Good work requires good relationship.
Creative output is a function of the working dynamic. I invest in the relationship as much as the deliverable because difficult communication produces compromised work, and nobody wants that.
Speed and quality are not opposites.
Eighteen years of project management has taught me that most quality problems come from poor scoping and unclear expectations, not from moving too fast. Clear briefs and honest timelines produce faster, better work.
Done is better than perfect, but craft still matters.
Shipping is a skill. Knowing when to stop refining and start delivering is something you develop through experience. That said, I hold a high bar for craft. Not perfectionism — precision.
Want to know how this would work for your project?
Let's have an honest conversation about scope and fit.