When we talk about improving software, the first idea is usually to add something new: another feature, another option, another way to customize the experience.
But many times, the biggest improvements come from the opposite direction. Removing unnecessary steps, reducing decisions users should not have to make, and making common actions feel simpler.
That is where software friction appears.
Friction is everything that creates distance between the user and the result they want to achieve. It can be an extra step repeated hundreds of times, a confusing setting, a slow process, or a workflow that forces people to adapt to the tool instead of helping them complete their task.
Individually, these problems usually look small. One extra click does not seem important. Waiting a few more seconds feels acceptable. Manually repeating an action once is not a big issue.
But software is built around repetition, and small moments of friction become much more noticeable over time.
Reducing friction is not only a design problem. It is also an engineering decision.
A simple experience often depends on things users never directly see: how the application is structured, how workflows are designed, which defaults are selected, and which features are intentionally kept simple.
The goal is not always to add more possibilities. Sometimes the better decision is making the existing workflow clearer, faster, and easier to understand.
Good software does not just solve a problem. It removes everything unnecessary between the user and that solution.
What is a small improvement in a tool that completely changed your experience using it?
Top comments (0)