Customer is (not) always right: The Fine Line Between Helping and Overcomplicating

Using OWIS's built-in analytics and reporting capabilities to identify patterns in customer requests.

When implementing OWIS, it's not uncommon for customers to come forward with requests. However, a common problem faced by implementers is that customers tend to present solutions they envision, rather than clearly communicating their underlying problems. As a result, implementers often find themselves trying to fit square pegs into round holes, implementing solutions that may not be the best fit for the problem at hand.

Good implementers know that the key to success is to focus on the problem itself, rather than getting caught up in the proposed solutions. With the wide range of features and capabilities offered by OWIS, there are often many different ways to solve a specific problem. This is why it's important to sometimes say "no" to customer requests that are more like solutions, and instead work to understand and address the underlying problem.

It's important to sometimes say "no" to customer requests that are more like solutions, and instead work to understand and address the underlying problem."

To effectively manage customer requests during the OWIS implementation process, it's important to take a step back and ask yourself: "Is this request addressing a symptom or the root cause of the problem?" If it's the former, it may be worth considering saying "no" and redirecting the conversation towards finding a more sustainable solution.

One way to do this is by using OWIS's built-in analytics and reporting capabilities to identify patterns in customer requests. This can help you understand which issues are most common and where the real bottlenecks in your workflow lie. By focusing on these core issues, you can work towards creating a simpler, more efficient system that is easier for both you and your customers to use and maintain.

In conclusion, saying "no" to customers may seem counterintuitive, but it's an important part of effectively managing requests during the OWIS implementation process. By focusing on the problem at hand, you can work towards creating a sustainable solution that benefits both your customers and your organization.

Previous
Previous

Workflows, Hiding in Plain Sight: How to Uncover the Organizational Rules That Run Your Company

Next
Next

A system for everything else! How to successfully manage all of the ‘other’ problems