At Blume, “onboarding” used to mean a CS rep handholding clients through a junky process. I researched B2B onboarding standards, then designed a self-service flow that guided users through setting up their profile and fine-tuning key settings. Result? CS finally had free time to tackle bigger issues, users got onboarded without fuss, and support tickets dropped to almost zero (minus a few funny bugs in test and prod). That’s what scaling looks like.

Founders love chasing shiny numbers, but the sneaky metrics tell the real story. I always push teams to look at overlooked signals like inactive page time and mouse movement tracking. They’re often the canary in the coal mine — predicting problems before churn becomes a headline.

I’ve waded into more than one chaotic Figma file and emerged with order. My secret weapons? Tokens, variables, and consistent naming patterns. Visual consistency is great, but when your dev team is building in React, naming is everything. A well-structured system means faster shipping, fewer “where’s that button?” moments, and a team that actually trusts their design library.