Sketches, writing, and other creative pursuits.
Keeping design on track.
Design is, by nature, an iterative process. Our work often starts off as a simple idea or observation. A small hook we capture and refine over time. With each iteration the picture becomes more clear. We explore ideas, test assumptions, refine solutions, and adjust based on feedback. This cycle is what allows us to build better, more thoughtful experiences over time. Small increments, carefully planned, can help guide teams to success even when visibility is low. But iteration can sometimes slip into spin.
Spin happens when you’re moving, but not necessarily forward. You revisit the same decisions repeatedly, tweak details endlessly, and start to lose sight of what you’re solving for. It’s a frustrating place to be, and it often feels like progress, even when it’s not.
The way out
When you’re stuck in spin, the best thing you can do is revisit the original research. Go back to the interviews, usability tests, survey data—whatever you started with. Re-reading it after a few design cycles can bring new clarity. You’ll see patterns you missed before, interpret feedback differently, and reconnect with the real needs of your users. More often than not, the direction you’re looking for is already in the data—you just need to see it from a new angle.
Better still—make it a habit
The best way to avoid spin in the first place is to build regular check-ins with your research into your design process. That could mean reviewing insights at the start of each sprint, sharing key quotes with your team, or simply blocking time each week to reflect on user feedback.
Keeping research top of mind helps ground design decisions and ensures the work stays focused on what matters most: the people you’re designing for.
May 19, 2025
The organized designer.
As designers, we often focus on the core skills of our craft — breaking down complex topics, building prototypes, and writing clear documentation. These are the skills we usually associate with “growth.” But there are also less talked-about skills that can make our work better. Being organized is one of them. It helps you stay focused and spend more energy on solving design problems, and it’s a skill worth developing over the long term.
So what does it mean to be organized? For me, it means keeping a collection of reliable resources and having a simple system to find and use them when I need to. Since creating my own system, I spend less time on logistics and more time thinking clearly. In this post, I’ll explain how my workflow works, in case it helps you too.
A personal archive
There’s a lot of design content online, and not all of it is useful. Building a personal archive means collecting high-quality information and tagging it so it’s easy to find later.
I use Notion to manage mine. I have an Inbox where I save articles, blog posts, and other resources I come across. I read them, and if they’re helpful and well-sourced, I add them to my archive. If not, I delete them. I tag each item by type, topic, and the design phase it fits into. Tagging is key, so let me explain more.
Tagging system
Tagging helps me find what I need later. First, I tag the content type — article, podcast, video, etc. Then I tag the topic — like brainstorming, interviews, or documentation. Finally, I tag the design phase — discovery, definition, or design.
With these tags, I can create filtered views to show only the most relevant sources for whatever I’m working on. I can save these views or share them by link.
Connecting it to my task manager
These views become really useful when I link them to my actual tasks. It’s only helpful to have an archive if you use it at the right time.
For example, if I’m working on a design concept and brainstorming ideas, I can create a view with content tagged “brainstorming” and “definition.” Then I link that view to the corresponding task in my task manager. That way, I have clear next steps and quick access to helpful resources.
In summary
This system takes time to build and maintain, but it’s paid off. I feel less stressed, more focused, and more confident in how I work. It’s been so helpful that I’ve started using it in my personal life too — for planning, appointments, or even garden projects. It frees my mind from remembering little things so I can focus on solving problems and learning new things.
May 18, 2025
A design "gut check".
A good rule of thumb I picked up is this: if you can’t explain a topic simply and clearly, you probably don’t understand it as well as you think. I’ve come to rely on this idea as a kind of “gut check” in my own work. When I’m designing something — especially for complex systems or unfamiliar user groups — I ask myself a few key questions. Do I truly understand who the audience is? Can I explain, in plain language, how they’ll interact with the product or service? And do I understand what ripple effects a design change might have on their workflow or goals?
If I stumble while answering any of those, it usually means I need to dig deeper. Maybe I’m missing critical context, or I’ve made assumptions that need validating. The act of trying to explain something clearly forces me to confront the limits of my understanding. It reveals blind spots I may have overlooked and pushes me to seek out more input — whether that’s from research, user interviews, or conversations with subject matter experts.
This process has become one of the most valuable tools in my design toolkit. It’s not just about simplifying for others; it’s about sharpening my own thinking. When I can describe a problem and its context clearly, I’m more confident in the design decisions I make — and I’m better equipped to communicate those decisions to others.
May 2 2025
A modular booking flow.
This was an old design I’ve always liked. A resort was quickly adding new entertainment options, and we needed a booking system that could grow with it. We broke the process into simple, modular steps that could be reorganized to work with any product. By using common parts—like picking a date, choosing between two pass types, or entering guest numbers—buying concert tickets would feel just like booking a week-long stay. The goal was to make the design easy to learn and remember.
A simple product page.
I explored a product detail page that offered only the next step in the purchase path. Basing the interface sequence on observed in store customer behaviour, the application would feel familiar and offer all of the necessary features, but appear radically simpler.
