The Diagnostic
Where Your Product Stands
Most founders don't have a design problem. They have a clarity problem. They know something feels off but they can't name it. Is it the product? The messaging? The flow? The brand? Usually it's all four, tangled together.
This takes two minutes. Answer honestly. Not where your pitch deck says you are. Where you actually are. At the end you'll see where the gaps are and what to focus on first. No fluff. No lead gen tricks. Just a quick read on whether your design is helping you grow or quietly killing your numbers.
→ Question 1: Stage
Where is your product right now?
Pre-launch, still building
Launched, under 1,000 users
Growing, 1,000 to 50,000 users
Scaling, 50,000+ users
→ Question 2: Biggest Friction
What's the most painful problem right now?
People don't understand what we do when they land
People sign up but don't activate
People use it once but don't come back
We're growing but the experience feels held together with tape
→ Question 3: Design Maturity
How would you describe your current design setup?
No designer. Founders are designing or using templates
One designer, mostly executing, not enough time for strategy
Small team, shipping fast but no system or consistency
Established team, but design decisions don't connect to business outcomes
→ Question 4: Brand Clarity
If a stranger landed on your product right now, would they understand what you do in five seconds?
Honestly, probably not
They'd get the general idea but not why it matters
Yes, the messaging is clear
Clear but it doesn't feel different from competitors
→ Question 5: Design System
Do you have a design system?
No, we style things as we go
We have a component library but it's inconsistent
We have a system but the team doesn't follow it
Yes, actively maintained and adopted
→ Question 6: Conversion Awareness
Do you know where users drop off in your core flow?
We don't track that yet
We have analytics but haven't dug into drop-off points
We know the drop-off points but haven't fixed them
We actively monitor and optimize
→ Question 7: AI Readiness
How are you thinking about AI in your product?
Not relevant to what we're building
Interested but haven't started
Experimenting with AI features
AI is core to our product experience
Result A: Foundation Stage
↗ Your product needs foundations before polish.
The priority right now is clarity. Not visual design. Not animation. Not a design system. Clarity. Your messaging needs to land in five seconds. Your core flow needs to get a user from zero to value in under two minutes. Your visual language needs to feel intentional, not improvised.
Most products at this stage waste time on aesthetics when the real problem is communication. A beautiful product that confuses people still fails. A clear product with basic design still converts.
↗ Focus here first: Start with your landing page. Can a stranger understand what you do, who it's for, and what to do next without scrolling? If not, that's the bottleneck. Everything else is downstream.
Then map your first five minutes. Every screen. Every decision point. Every moment where a user might hesitate or leave. Fix the first drop-off point before you touch anything else.
Result B: Conversion Stage
↗ Your product works. Now make it grow.
You've built something people use. The question is whether your design is helping you grow or just keeping things from breaking. At this stage, the highest-leverage work isn't new features. It's removing friction from the flows you already have.
Most teams at this stage add complexity when they should be subtracting it. Every new feature, every new page, every new option is another place for users to get lost. The products that grow fastest at this stage are the ones that ruthlessly simplify.
Focus here first: Identify the three highest-traffic flows in your product. For each one, find the step where the most users drop off. That's your entire design priority for the next month. Fix those three drop-off points before you build anything new.
Then look at your landing page conversion. If less than 5% of visitors take your primary CTA, the page is the bottleneck, not the product.
Result C: Systems Stage
↗ You have traction. The cracks are showing.
What got you here won't get you there. The product was built fast, which was right. Now it needs infrastructure. Not because infrastructure is cool. Because without it, every new feature makes the product slightly worse. Inconsistency creeps in. Design debt compounds. New team members take longer to ship because there's no shared language.
This is the stage where most products start feeling "messy" to users, even if they can't articulate why. It's death by a thousand inconsistencies.
Focus here first: Build a minimum viable design system. Not a library of 200 components. Start with design tokens: colors, typography, spacing, and elevation. Then build your ten most-used components with clear documentation. Ship that before you build anything else new.
Then audit your product's language. Every label, every button, every error message. Inconsistent language creates cognitive load that no visual design can fix.
Result D: Leverage Stage
↗ You have the team and the momentum. Now make design strategic.
Most design teams at this stage are productive but not strategic. They ship features. They maintain the system. They respond to requests. But they're not driving the product direction or connecting design decisions to business outcomes.
The shift from here is making design a leadership function, not a service function. That means frameworks for decision-making, metrics tied to design choices, and a seat at the table where product strategy is decided, not just executed.
↗ Focus here first: Tie every major design initiative to a measurable business outcome. Not "improve the user experience." Instead: "reduce onboarding drop-off by 20%" or "increase activation rate from 30% to 45%." When design speaks in outcomes, it earns strategic authority.
Then invest in design principles that the whole company can use, not just the design team. When engineering, product, and leadership can evaluate a decision through a shared design lens, design becomes organizational infrastructure, not departmental output.
If any of this resonated, I open one slot a week for a free fifteen-minute conversation. No pitch. No proposal. Just clarity on what to focus on next.
