{"id":3469,"date":"2020-09-22T20:22:51","date_gmt":"2020-09-22T20:22:51","guid":{"rendered":"https:\/\/mbaoutcome.com\/the-hidden-costs-of-disrespecting-your-customers-whether-internally-or-in-person\/"},"modified":"2020-09-22T20:22:51","modified_gmt":"2020-09-22T20:22:51","slug":"the-hidden-costs-of-disrespecting-your-customers-whether-internally-or-in-person","status":"publish","type":"post","link":"https:\/\/www.varshabi.com\/MB\/2020\/09\/22\/the-hidden-costs-of-disrespecting-your-customers-whether-internally-or-in-person\/","title":{"rendered":"The Hidden Costs of Disrespecting your Customers \u2013 Whether Internally or In-person"},"content":{"rendered":"

[et_pb_section][et_pb_row][et_pb_column][et_pb_text]<\/p>\n

As a leader, it\u2019s critical to reflect on how you and your team talk about your customers\u2019 behaviors, needs, requests, and issues during internal meetings. I say this because your narrative sets the tone for how your employees will interact with customers, not to mention how they will think <\/em>about and interact<\/em> with your products and services. While a company\u2019s success is shaped by its culture, values, and vision, its customers drive the business.<\/p>\n

In a word, our customers keep<\/em> us in business and deserve to be treated with respect \u2013 whether in-person or during internal team meetings.<\/p>\n

Customers aren\u2019t dumb, and assuming otherwise robs you of opportunities to improve your products and services.<\/strong>If your customers are asking the same \u201cdumb questions\u201d about how to access a particular functionality, then that feature probably needs clarification or better documentation.<\/p>\n

As the Managing Partner of a company with a major product line in inspections, we have a smart customer base. I\u2019ve attached a basic electrician\u2019s training worksheet here<\/a> its pretty complex. Frankly, it contains more math than I\u2019ve used in 20 years of building software. The point is that almost all of your customers are experts in something, just not in the same things as you. (If they were, they wouldn\u2019t need you.)<\/p>\n

Though our customers at ExAM4Inspections.com are often not technically inclined, if we simply dismissed their challenges, it would rob us of the opportunity to determine whether a feature is poorly documented, a field is poorly named, or a button is in the wrong place\u2026And it could prevent us from growing our base through word-of-mouth advertising, user friendliness, and customer service.<\/p>\n

Bottom line: Nothing is simple enough<\/em> until all of your customers can understand it. The more understandable<\/em> you make your product or service, the better positioned your customer will be to succeed and foster your success.<\/strong><\/p>\n

That being said, if you find yourself in a \u201cdumb customer\u201d situation, I recommend that you do the following two things: (1) be kind, charitable, and solve the customer\u2019s problem, and then (2) ask them (in a non-sarcastic way) how they reached their conclusion. Where did they look for the feature button? Why did they think it was worked in the way they thought it did.<\/p>\n

Over the past 20 years, I\u2019ve discovered that if you ask a few clear and respectful questions, you will find that most customers are pretty reasonable and are full of insights.<\/strong> They thought the button would be somewhere it wasn\u2019t because of some other software they\u2019ve used, or it was a matter of logical inference. They asked for a last minute change because they wanted it, not because they wanted to make your life awful two weeks before the project finish line.<\/p>\n

A further advantage of taking this approach is it can create a feedback loop into your product that can be game-changing. As a case in point, we spent almost a year working with a customer who had new users leveraging our inspections app, and their number one challenge was resetting passwords. One of the issues was getting the customer to type the correct URL into the app to complete the log in. Simply put, it was a long string and, for the most part, their inspectors were older, late adopters of technology. Eventually, we decided to create a screen that housed existing enterprise customers\u2019 URLs behind their logo. By clicking on the right logo, it would fill in a user\u2019s domain URL. Not only did this solve their problem, it reduced our customer support requests by almost 80%.<\/p>\n

What about those rare cases when the question has an obvious answer, or you\u2019re working with someone who is unreasonable to the point where there isn\u2019t any value in their feedback?<\/strong>If you follow the process and mindset I\u2019ve outlined above, you will find that this happens far less often than you may think.<\/p>\n

When I shifted my thinking from wondering how a customer could<\/em> have made that mistake to investigating issues through a customer-centric lens, most of the concerns were not limited to one person and could be corrected through thoughtful design. Things I would have written off in the past as a customer being unreasonable \u2013 like a project change at the 11th hour \u2013 became opportunities for me and my team to clearly document and discuss sources of friction so that we could develop a shared understanding.<\/p>\n

In responding to the issue outlined above, we realized that we needed to adapt our customer engagement methods to manage change at the outset of a project. Only then could we avoid costly and time-consuming disagreements on these items downstream. While this didn\u2019t stop our customers from requesting changes late in the game, it enabled us to refer back to our previous conversations and navigate changes through the process we had agreed upon. This has significantly reduced our overall stress and has ensured that we take a solutions-oriented approach to improve our practices \u2013 without resorting to treating the customer as a scapegoat.<\/p>\n

Finally, some customer requests are going to be \u2013 how shall I put it? \u2013 under-informed. A fraction of the issues that cross your desk will be things that no customer should have missed. When this happens (and it will) it\u2019s important to frame the customer in a positive light to ensure you perform your due diligence on every request. It\u2019s also important because no matter how far off base, how uninformed, or how terrible the request is, they are still the reason why you are in business. Trust me, one of your competitors would gladly take a few more minutes to explain the concept for the hundredth time; spend a few more minutes to politely listen to a \u201cstupid\u201d feature request; or move a deadline a couple of days to get it right in the customer\u2019s eyes.<\/p>\n

Ultimately, your team and your employees will take their cues from you. If you blow off a customer request, it will seem ok for them to do so as well. Even when you decide that you are not going to move a customer\u2019s issue or idea forward, it\u2019s important to work through the process \u2013 if for no other reason than to set the standard for your team.<\/p>\n

When leaders take every customer request seriously, and commit to putting the customer at the center of their universe, their teams will too. This will benefit your customers tremendously and, by proxy, it will help your business tremendously. After all, happy customers make great businesses!<\/strong><\/p>\n