stancliffneil
New Member
Wanted to share some patterns we keep running into across SaaS design work, since a lot of founders ask the same questions and the answers usually aren't what they expect.
1. Activation problems are rarely visual problems
The most common thing we see: product looks polished, traffic is decent, but activation is stuck low. First instinct is always "we need a redesign." Nine times out of ten, the actual issue is sequencing the flow is asking for something (payment, integrations, permissions) before the user has seen any real value. Nobody sat down and mapped the order of steps, it just got built in whatever order made sense during development.
Fix the order before you touch the color palette. It's cheaper and it's usually the actual leak.
2. Information architecture breaks quietly
Works fine with 5 screens. Falls apart around screen 15-20 if nobody planned where things live. Settings sprawl, navigation gets inconsistent, and every new feature adds a little more confusion instead of fitting into a pattern. By the time someone notices, it's a bigger fix than it would've been earlier.
3. Design systems aren't optional past a certain point
Once you're shipping features weekly, a shared set of components (buttons, form patterns, states) is what keeps the product from feeling like five different apps stitched together. Teams that skip this end up redesigning the same button five different ways across five screens.
4. Usability testing catches what internal review can't
Your team knows the product too well to get confused by it. A handful of real users trying to complete a core task without help will find friction points that six months of internal QA won't, because internal review is testing familiarity, not first-time comprehension.
5. Retention is an onboarding problem more often than a feature problem
When users churn early, the instinct is to build more features. Usually the actual issue is that onboarding didn't get them to a useful outcome fast enough, so they never stuck around long enough to see the features that would've mattered.
Happy to go back and forth on any of this in the thread if people have specific situations flow issues, IA cleanup, whatever. If it's useful, here's a longer breakdown of how we .
1. Activation problems are rarely visual problems
The most common thing we see: product looks polished, traffic is decent, but activation is stuck low. First instinct is always "we need a redesign." Nine times out of ten, the actual issue is sequencing the flow is asking for something (payment, integrations, permissions) before the user has seen any real value. Nobody sat down and mapped the order of steps, it just got built in whatever order made sense during development.
Fix the order before you touch the color palette. It's cheaper and it's usually the actual leak.
2. Information architecture breaks quietly
Works fine with 5 screens. Falls apart around screen 15-20 if nobody planned where things live. Settings sprawl, navigation gets inconsistent, and every new feature adds a little more confusion instead of fitting into a pattern. By the time someone notices, it's a bigger fix than it would've been earlier.
3. Design systems aren't optional past a certain point
Once you're shipping features weekly, a shared set of components (buttons, form patterns, states) is what keeps the product from feeling like five different apps stitched together. Teams that skip this end up redesigning the same button five different ways across five screens.
4. Usability testing catches what internal review can't
Your team knows the product too well to get confused by it. A handful of real users trying to complete a core task without help will find friction points that six months of internal QA won't, because internal review is testing familiarity, not first-time comprehension.
5. Retention is an onboarding problem more often than a feature problem
When users churn early, the instinct is to build more features. Usually the actual issue is that onboarding didn't get them to a useful outcome fast enough, so they never stuck around long enough to see the features that would've mattered.
Happy to go back and forth on any of this in the thread if people have specific situations flow issues, IA cleanup, whatever. If it's useful, here's a longer breakdown of how we .