I was recently working with a client and interviewing some front-line team members regarding their work and interactions with their Customers.
I’m really proud of this organization because it seems to be filled with Customer-centric people. That’s wonderful and I salute the leadership of this business for promoting such a spirit of good CX. They’re also clearly making it part of their hiring process, and also making it integral in the development of their people. Bravo.
But here’s what I also noticed:
The team had a bit of a myopia about concerns that could potentially lead to friction for their Customers.
In one instance, someone in an interview brought up a communication issue between their digital (Customer-facing) system and their own internal CRM. This led to frequent instances whereby a Customer thought he’d done something that would yield certain results, but when he interacted with a human team member within the organization, there was no record of the action from the internal perspective.
The hero story here was that this team member prided herself on fixing it every time it occurred. By “fixing it,” I mean (and as she’d tell it) that when the Customer inquired about it, she would put on a good face, pretend she did see the request on her own internal CRM system, and proceed accordingly. Which is to say, from the Customer’s perspective, all seemed perfectly in order. Even if it took a minute or two longer than it otherwise should, likely the Customer wouldn’t even be aware of the extra step or two this team member went through to ensure a smooth experience.
Excellent!
But, I said, how about taking a note?
As I pulled the thread a bit, this person shared that this sort of thing happens a few times a day with a few different Customers, and when I interviewed some of her contemporaries, they also said that, yeah, it happens quite a bit, but we all have work-arounds and fixes.
That’s kind of the issue here: Such Customer-centric culture will engender the ‘can-do’ attitude among your team and encourage them to find fixes and always make it right for the Customer. They’ll “make it work” and “do what it takes” and “make diving catches” all day long.
They’ll take great care of the “outer loop” by ensuring that the Customer is made whole or otherwise taken care of. In fact, in this instance, they’re even out ahead of the loop as it’s often that the Customer is unaware altogether that there even was a problem (or a potential problem, at least).
But if all those incidents sit out there and nobody takes a look at the systems and processes causing those (again, fortunately here, usually only potential) issues, they’ll keep happening.
What happens when a new or otherwise distracted or careless team member lets one of these instances slip through the cracks? What if it’s a super busy day and things pile up, making it less feasible to make the fix? Each of us, sometimes, has a bad day. I even asked it explicitly: “Do you ever not get things fixed for a Customer?” “Oh yeah, from time to time, sure,” was the answer.
And that’s where we were finally able to start talking about root-cause issues and systematic failures. That’s where we were finally able to start fixing things.
The system will run better, team members will be less flustered, and you can almost completely eliminate even the chance that a Customer has a bad experience.
So don’t just save the Customer from that bad circumstance…look deeper and remove the issue at the root.






Leave A Comment