Can reducing workflow friction improve retention more than launching new features?
by•
One lesson I learned while building a product is that customers don't always want more functionality. Sometimes they just want the things they already use to work together without unnecessary interruptions. A few extra steps repeated manual tasks or disconnected tools might seem like minor issues from a development perspective. But for someone using the product every day those small frustrations can become a reason to leave. It made me rethink how we prioritize product improvements. For founders how do you identify and measure the small workflow problems that quietly push paying customers away?
6 views
Replies
What's worked for me is watching people do the core task rather than reading dashboards. Sit with five users, or watch five session recordings, and note every place they pause, backtrack, copy something out of the product to paste somewhere else, or open another tab to finish the job. Those are your friction points, and they rarely show up in support tickets because people just work around them. To measure it, I'd pick one key task, count the steps and the time from start to finish, then re-check after each fix. A drop in steps or time on that one task is easier to defend than a general "it feels smoother".