Last week I spent two days polishing an edge case in a settings panel maybe 2% of users would ever hit. Meanwhile my onboarding flow still has a broken redirect I've been ignoring for a month.
I think it's a comfort thing, polishing a small, contained feature feels productive and safe. Fixing the core flow means touching stuff that's scary to break, so it keeps getting pushed down the list.
Lately I've been trying a dumb gut-check before every commit: "would a user even notice if I stopped right here?" If the honest answer is no, I stop and move to something that actually blocks someone.
Curious how you all draw that line, is it a rule, a gut feeling, or do you just ship when you're sick of looking at it?
Let me start from where i'm sitting: i talk to founders, hiring managers, and recruiters every week, and the same conversation keeps coming up. nobody trusts their pipeline anymor
Application volumes have doubled since 2021. Cheating on technical assessments doubled in just six months last year, from 15% to 35% of candidates. One in three hiring managers has personally caught a fake identity in an interview. @Anthropic had to rewrite their interview questions after so many people cheated during the interview with Claude.
Feature creep happens so fast when you're trying to make every early customer happy. We made the exact same mistake and ended up with a cluttered product that confused new signups during onboarding.
When we finally decided to remove two unused features, a tiny group of vocal users complained, but our main activation rate shot up right after.
Sending a polite heads-up email with a simple alternative helped soften the blow.
Did you face any backlash when you started cleaning up your dashboard?
I spent almost a year preparing. Reading, planning, sketching, learning. I told myself I was building the foundation for what would come next.
The thing I was actually doing was avoiding the start. Every week of preparation was a week I did not have to fail at something real. And preparation looks exactly like work from the outside, so nobody questioned it, and I did not have to either.
There is a feature in my product that exactly one customer uses. It costs me infrastructure, maintenance, and a little attention every month. The numbers say I should have killed it two years ago.
I keep it because I remember the conversation when they asked for it. They were at a company with a real problem, and I was small enough to actually solve it for them. It was one of the first times I felt like I was building something that mattered to a specific human being.
I cancelled something last week and I could not explain to the founder why. Not because the reason was complicated. Because it was embarrassing. The product worked fine. I just stopped opening it.
That is the most common kind of churn and almost none of it gets reported honestly. People say price or features or a competitor. The real answer is usually that a habit never formed. The product was fine and it was not quite the shape of my day.
