Your SaaS product might be solving the wrong problem. And most designers don't realize it.
Before jumping into Figma, designing dashboards, or creating beautiful interfaces, there's something much more important to understand.
The difference between a Business Problem and a User Problem.
In Part 01 of my SaaS Product Design Masterclass, I'm breaking down:
🔹 1.1 — Start with the Business Problem
🔹 1.2 — Understand the Business Impact
🔹 1.3 — Identify the User Problem
🔹 1.4 — How Business Problems and User Problems are connected, but different.
Here's an important thought:
A business wants to achieve a goal.
A user wants to solve a problem.
Great digital products understand both.
This is where meaningful product differentiation begins — not with UI, but with problem understanding.
🎯 This is Part 01 of my 10-hour practical SaaS Product Design series, where I'll walk through the complete process of understanding and designing a SaaS product.
If you're a UX/UI Designer, Product Designer, aspiring designer, or SaaS founder, this series is for you.
One question: Do you start your design process with business problems or user problems?
I draw logos by hand, then build everything around them: the brand, the website, the store. Lately I also make product films and ads with AI.
Recent work: an RY monogram and site for a Koreatown law firm, a winged W for a defense firm, and my family's golf eyewear brand, from the mascot to Shopify.
Starting a brand, or have one that doesn't feel like you yet? Show me what you're building.
The logo-led system reads tight because the wordmark sits clean in the negative space instead of fighting the emblem — when a brand has that kind of restraint, the Shopify store usually carries the same hierarchy into the product grid and checkout without inventing new rules....