Are you a Checklist Designer or a Problem-Solving designer?
Why does it matter which you are?
Well, one of these designers will:
struggle to know how to move forward in projects
waste time on design tasks that don't matter
see little to no results from their design solutions.
This designer often feels stuck in their career and doesn't get the promotion.
Which designer is that?
The Checklist Designer 📋
By the end of this newsletter, you’ll understand the difference between the two types of designers and what steps to take to become a Problem-Solving designer.
How do I know this designer exists?
As much as I don't want to admit this…
I used to be that designer.
And now, I meet more and more designers falling into the same trap:
Obsessing over the process rather than the problem.
So, ask yourself:
Am I a Checklist Designer, just ticking off design tasks on a list for the sake of it?
Or am I designing with purpose?
I'd like to introduce you to both types of designers so you can answer honestly.
Meet the Checklist Designer 📋…
This designer treats UX as a to-do list of design tasks to complete.
They focus on methods and activities without questioning if they're truly needed.
Resulting in designs that lack impact.
Here's why this approach doesn't work:
😕 They don't consider the project's needs, leading to confusion on what to do next in their project
😕 They use design methods without understanding why, making it hard to explain their decisions.
And yes, these are the designers who often add personas to their case studies because that's the norm.
Now, before this sounds like I'm shaming these designers, let me make one thing clear...
This is not the designer's fault.
This is a systemic problem due to:
Bootcamps that teach a checklist of methods and call it "design thinking."
Courses that prioritize the design process over problem-solving and critical thinking.
Companies that don't understand design and push for meaningless activities.
No wonder so many designers get it wrong. When the industry teaches the wrong approach, how are we expected to learn what design truly is?
If you're reading this and thinking, ‘Oh no, I think I do this’, don't worry.
Awareness is the first step toward change.
I've been there. I once did an entire user journey mapping exercise… and I still don't know why 🫠
Meet The Problem-Solving Designer 🧠
The Problem Solving Designer is different.
They choose their tasks based on what the project needs at that moment.
They don't ask:
What tool or activity should I use?
Instead, they ask:
What do I want to achieve?
What must I do to get closer to solving the problem?
This approach means considering what the project needs at each stage rather than just following a process.
The focus is on making progress toward a solution, not just completing tasks for the sake of it.
How can you tell if you're a Checklist Designer or a Problem-Solving designer?
Take one of your past projects.
Review what you did and ask yourself:
Why did I do this?
What was I hoping to gain or learn from doing this?
If you can clearly explain why the activity was necessary to move the project forward, you're likely a Problem-Solving Designer.
If you can't clearly explain it, you might be a Checklist Designer, just ticking off tasks on your checklist.
How do you become more of a Problem-Solving designer?
Before starting any task, ask yourself: *What value will this provide?*
If you can't see how it moves the project forward, reconsider if it's the right step.
Example:
You're considering creating a user flow.
Ask: Why am I doing this? What will it help me understand?
✅ Use a user flow if you need to map out user steps and ensure the journey makes sense.
❌ Skip it for simple tasks like log in or sign up, where the path is already obvious and straightforward.
Consider how each design task, framework, or tool will help you learn or improve.
Conclusion
Design success isn't about the process you take.
It's about the results you create.
A perfect process won't get you a promotion.
The impact your designs have will.
