I spent eight months working as Creative Director for a large, well-funded product team. Big budget, talented people, genuine ambitions. Watched them add features like collecting Pokémon cards. CRM. Then dashboards. Then analytics. Then automation. Then AI (of course). Each addition made perfect sense in isolation. Each one had a business case, user requests, competitive…
Most products I audit have great onboarding flows, polished dashboards, carefully designed settings pages. Then you hit the empty state and it’s like someone gave up. A clipart illustration. Generic copy that sounds like it was written by committee. Zero help on what to do next. Your user onboarding can be perfect, but if users…
There’s a quiet crisis in SaaS website design. Too many teams have traded clarity for theater. Instead of sites that inform, we get sites that perform — full of gradients, animations, and positioning so vague it might as well be lorem ipsum. The result? Users scroll. They’re impressed. And then they leave. Modern SaaS website…
There’s a reason your UX copy reads like it was written by a sentient HR policy. It probably was. Not literally. But by the time your crisp, punchy, human line made it through your product lead, your marketing head, your legal review, your VC’s opinion, and your cousin who “has a way with words,” it…
It sounds harmless. Polite, even. “Maybe Later” — the soft opt-out on your modal, onboarding flow, or product tour. A UX safety valve. A peace offering to the anxious user. But here’s the problem: “Maybe Later” almost always means “Never.” And worse — it trains users to avoid learning your product at the very moment…
You’ve been moving fast. The roadmap’s alive. Features shipped, launches announced, maybe even a few investors impressed. But now the product’s feeling… messy. Not broken. Just a bit bloated. A little stiff in places. UX that used to feel sharp now feels like it’s whispering through bubble wrap. If you’re here — you don’t need…
Every SaaS team hits the same wall around 10-15 features: the interface feels inconsistent, new features take longer, and someone suggests building a design system. Six months later: 83 Figma components, 40 pages of documentation, developers using it about 23% of the time. The rest is cowboy code with “urgent deadline” justifications. I’ve watched this…
I’ve spent three years looking at SaaS website design pricing pages. 31 of them, to be exact. B2B companies, $500K to $50M ARR. Here’s what I keep seeing: Average features listed: 47 Time people spend staring at pricing: 3 minutes 47 seconds Bounce rate: 64% Features they actually compare before giving up: 2.3 Support tickets…
I spent 6 weeks building a feature that saved users 40 minutes per week. Then I skipped it in user onboarding because “it felt too advanced” and “we didn’t want to overwhelm new users.” Discovery rate after 90 days: 27%. 73% of users never found it. Not because it was bad. Because I decided not…
I spent three months tracking settings usage across one product. 127 total settings. 89 visible by default. Users changed an average of 4.7 settings. Not 89. Not 31. Not even 12. 4.7. Democracy in action: you built 89 options, users touched 5% of them. The other 95% just made onboarding take 18 minutes longer and…
