I was inspired to write this column by a colleague’s story about a delivery service she once worked for. The company promised customers a courier arrival window of 30- to 60-minute. The system determined the deliveries’ order and route, but couriers took more convenient routes instead. Since the app didn’t allow them to reorder the addresses, they logged deliveries manually and entered the data into the system at the end of the day. As a result, customers saw delayed and often incorrect order statuses.
Eventually, the company adapted the system to the couriers’ behavior and let them manually switch between delivery points. Thanks to this, it began receiving up-to-date information on the couriers’ movements, and customers could be notified of changes to the estimated time of arrival. In this situation, the workaround revealed exactly where the product team’s vision diverged from users’ actual behavior, and the team used this to improve the product.
Following on that, let's dive into how workarounds help product teams and how to respond to them.
Why a product workaround can reveal more than a feature request
New features usually emerge either from the product team’s vision or from user feature requests. But a new feature doesn’t necessarily make the product better. Users assume the feature will improve their interaction with the product. The team spends resources implementing this request without ever figuring out what problem the new feature was supposed to solve — or whether it will solve it.
Workarounds are the opposite. We see how a user has adapted their work to their needs. For example, an employee has a CRM but also maintains an Excel spreadsheet. They spend extra time transferring data, risk making mistakes, but still go back to the spreadsheet. So something in this alternative is important enough to them that they put up with these inconveniences.
Workarounds reveal the discrepancy between how a product was designed to work and how people actually work, and what they expect from it.
Reasons for product workarounds
At first glance, all workarounds seem the same: users do part of the work manually or turn to third-party tools. But the reasons for this behavior vary. Here are the common ones.
The product doesn’t cover real-world user scenarios
This is a common problem for B2B products, which are designed around the buyer’s requirements rather than those of daily users. A manager may understand which processes need automating but may not be aware of all the nuances of their employees’ work. As a result, the product handles standard scenarios well but misses specific workflow stages. For example, the user prepares a request or a contract within the system and this document needs the manager’s approval. But this stage is simply missing in the workflow. It results in the necessity to export files and continue review via email or a messaging app.
A UX issue or user distrust
Sometimes, the required feature exists in the product and even works perfectly, but users simply don't know about it. For instance, if the function is hidden somewhere deep inside the menu or pop-ups when it shouldn't. It makes users continue to perform the tasks manually even though the product can cope with them.
Another case is when the user knows about the feature but avoids it deliberately because of having a bad experience with the product earlier. In such situations the problem is related not to design itself but to the lack of trust. And it is hard to eliminate even after the improvement.
The alternative way of working is simply more convenient
Sometimes users prefer a third-party tool simply out of habit. For example, a corporate system may have a built-in chat, but employees keep using Slack or Microsoft Teams. For the product team, this is a workaround for the intended feature, but it doesn’t necessarily mean a problem for the business — that needs to be determined separately.
It’s in users’ interest to circumvent the rules
This is a reason the product team has almost no control over. Let me explain using the example of a logistics company that launched a brokerage platform.
Developers created a plugin that automatically hid certain companies considered unreliable — for example, those that had previously lost cargo. Brokers didn’t like this: they began disabling the plugin to have a wider selection of carriers and close more deals. When the disabling option was restricted, brokers, despite the risks, still found ways to negotiate with banned carriers.
In this case, the feature worked correctly: it protected the business from risky deals. The reason for the workaround lay outside the product itself, in users’ motivations.
How to respond to workarounds and why you shouldn’t rush to development
Although workarounds suggest that the product isn’t working as intended, there isn’t always a need to immediately build new features; or make urgent changes at all. First, assess their consequences for the business.
Depending on those consequences, various solutions are possible.
Add the missing feature
If users regularly have to perform an important part of their work outside the product and this impacts the business (for example, data is lost or information leaks) the feature should be implemented.
One caveat: choose very carefully what goes into development. AI has simplified coding, but has also increased the temptation to create unnecessary features. With these new capabilities, a team can turn into a “feature factory,” where success is measured by the number of new features rather than the problems solved. Some benchmarks also point to the need for moderation in development. For example, Pendo reported that only about 6% of features account for 80% of product usage. This doesn’t make the remaining 94% unnecessary, but they rarely become the “core” features that are the reason people choose the product.
Make a feature more accessible
This is a situation where a solution already exists and can fully meet the user’s need, but it isn’t obvious, isn’t understood, or is buried deep in the menu. Your task is to highlight it and teach users how to use it, and if necessary, also demonstrate its reliability or give users more control. If the reason for the workaround is a lack of trust in the system, you first need to verify its reliability and then help users see the results for themselves.
Integrate tools instead of duplicating features
People and businesses rarely choose just one product for their work. According to the results of a survey of over 1,000 IT leaders as part of the MuleSoft Connectivity Benchmark Report, the average-sized organization uses 957 applications, but only 27% of them are integrated with one another. Sometimes it’s enough to set up an integration so that data is transferred automatically, allowing people to continue working in the systems they’re used to.
Leave everything as is
Doing nothing is a solution that’s often overlooked. Not every workaround necessarily needs to be brought back into the system. If it doesn’t affect the quality of work and doesn’t require additional costs, the best solution is not to intervene.
Most important lesson: observe
The most valuable product solutions are born from observing actual behavior. If you see a workaround, first try to understand when or where people switch to the other products, and then – what and how often do they do there.
Then simply talk to them. Ask about the reasoning behind their selection of this workflow and what stops them from finishing the task within the product itself. Compare your insights with product analytics data and inquiries from the support team; they can tell you what people complain about most as they regularly interact with users. When the same issues occur on different levels, it might be a sign of a genuine need. And a workaround itself might be a clue rather than a problem.
So, what I always recommend first: Figure out what problem the user is trying to solve.

Member discussion