The two sides of Customer centricity
Yesterday, I involuntarily witnessed a customer phone call. You know, in German-speaking countries, "managers" regard large-capacity compartments of express trains as walk-in telephone booths. The man had to conduct an escalation conversation with a dissatisfied customer. In doing so, he moved very skillfully between appeasement, assurances, but also pressure (“Yes, what am I supposed to do now, I can't change the situation either”). At the end of the long phone call, the customer was satisfied to the extent that the conversation could end on a consensual basis.
Things only got really exciting afterwards, when Mr. Manager followed up in one-on-one meetings and/or conference calls with his employees. The fact that the tone of voice changed depending on the person being talked to is not unusual. Between the lines, however, it was clear that the customer's concerns were dismissed as an annoyance - mistakes happen and capacity problems are externally determined.
If you communicate this to your employees, you can spare the expense of customer centricity programs. It is then a mere mask that does not promote genuine customer understanding, but filters it out. Just like the masks in the pandemic. Customers in project business, on the other hand, are well advised to invest a lot of energy in contract design - even if it hurts and puts the brakes on. Otherwise, they will be just as defenseless against the supposedly inevitable defects in (software) development as the unfortunate person on the other end of the line was yesterday.
