Scarlett Massey

I think finding good design references is the easy part. Figuring out what to take from them is much harder.

For example, you find a dashboard with a really clean layout. But is it good because of the spacing, the information hierarchy, or simply because it has less data than your product?

I've been thinking about a few things worth checking before borrowing a design pattern:

• Context: What problem is this design solving, and is it similar to ours?

• Structure: Does the layout still work when the content gets longer or more complex?

• Interaction: What happens in empty states, errors, or when users need to go back?

• Tradeoffs: What did this product simplify or leave out to make the experience feel clean?

Meta question, but it's been on my mind since I had a post rejected and, rereading it, agreed with the rejection.

The difference I've landed on: content is written to be agreed with. An insight is written to be argued with. Content says "here are five lessons." An insight says "here's the one thing I believe that you might not, and here's why."

The test I now run before posting: could someone reasonably disagree with this? If not, it's content. If yes, and I can defend it, it's worth posting.

I'm curious whether other people have their own test, especially people who post here regularly and don't get rejected. What's the thing you check before hitting submit?

It's so easy to get high on the dopamine of seeing signup numbers tick up every Monday morning, even when most of those users never log back in after day three. We hit a wall when we realized our massive growth spike was just filling a bucket with a hole in the bottom. Getting the team to stop caring about vanity metrics and actually fix the onboarding friction took a real mindset shift. If you've been through this, what metrics finally forced your team to wake up and focus on actual usage instead of just new signups?