Product UX
How the product behaves after sign-up: onboarding, flows, states, in-product copy, and UX debt.
_
Good for: PMs, founders and designers who want to fix activation, reduce friction and stop “tiny” UX decisions from quietly killing usage.
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…
There’s one part of a SaaS product that’s both incredibly revealing and tragically underdesigned: The pricing page. It’s where value meets clarity. Or confusion. Or cowardice. And it’s usually the page that gets the least love – stuck in Notion, half-baked by a product marketer, or styled like it’s still 2014. We’ve seen it all.…
You built something useful. You shipped it fast. Maybe you even ran a tidy launch thread on LinkedIn. And now… it’s dead weight. Buried in your UI. Ignored. This isn’t a development problem. Or even a design one. It’s a discovery problem – and it’s killing your product. Discovery Is the Bottleneck Most founders we…
If your settings page is longer than your actual product, you’re not giving users freedom – you’re handing them your design indecision. Settings pages that stretch endlessly downward aren’t empowering – they’re exhausting. Each toggle, checkbox, or dropdown represents a decision your team refused to make. It’s your uncertainty passed directly onto the user. A…
Your product is nice. Too nice. Everything says “maybe.” Every modal wants to know if it’s a good time. Every tooltip apologises for existing. It’s all lowercase and softly rounded — like if Helvetica had social anxiety. We get it. You want to be helpful, human, inoffensive. You want to sound like a warm breeze.…
Your product works. Mostly. The flows are familiar. The nav still kind of makes sense. Nothing’s technically broken. And yet, everything feels… off. This post is for product managers, founders, and leads who’ve started asking themselves: “Should we redesign?” Before you book a redesign sprint — stop. You might not need a redesign.You might need…
You know the one. The MVP built by a freelancer over a long weekend, styled with inline CSS, powered by a Google Sheet and a thousand silent prayers. And somehow — it worked. The team raised money. Got users. Found traction. It looked like hell, but it proved a point. That something about the idea…
The feature shipped. The onboarding was polished. The numbers looked fine. And then… nothing. No tickets. No replies. No praise. No complaints. No usage. Just empty sessions and quiet churn. And the worst part? Everyone in the room thought that meant success. This is a post about the signal inside that silence — and how…
Every designer, at some point, ships a button that doesn’t work. Maybe it launches a spinner that spins forever. Maybe it opens a modal promising a feature that hasn’t been built. Maybe it just… refreshes the page and hopes you don’t notice. We don’t talk about these buttons much. They’re awkward. They’re compromises. But they…
This isn’t a pitch. It’s not a teardown. And it’s definitely not for clout. It’s a reflex. A twitch in the brain. The quiet urge to take something you admire and… move a few things around. We’re talking about unsolicited redesigns — the ones that happen in your head, on a napkin, in a Figma…
