Most people think of customer service as a frontline job. You handle complaints, close tickets, move on. And on the surface, that's exactly what it is.
But after months of handling cases, I started noticing something: the same complaints kept coming back. Different people, different accounts, same underlying problem. And that problem was almost never technical.
The real source of most failures
When a customer is frustrated, the instinct is to fix the symptom in front of you. Refund the charge. Reset the account. Escalate the ticket. Case closed.
But if you actually listen — and I mean listen past what they're saying to what's making them say it — you start to see patterns. The frustration usually isn't about the specific thing that went wrong. It's about the gap between what they expected and what they got.
That gap is a design problem. Someone designed a process, or an interface, or a communication flow — and they designed it in a way that created the wrong expectation. The customer did exactly what they thought they were supposed to do, and something broke anyway.
That's not a user error. That's a system error.
What MIS taught me to see
In my systems analysis coursework, we spent a lot of time on something called process mapping — drawing out every step of how a task gets done, who does it, what information moves between steps, and where bottlenecks form. It's dry on paper. It becomes very real when you're watching a queue of forty open cases and can literally trace each one back to the same two broken handoffs in a process that nobody has revisited in three years.
Good systems don't just work. They fail gracefully. They give people the right information at the right time so that when something does go wrong, the person on the receiving end understands why, and knows what to do next.
Bad systems make people feel stupid for using them correctly.
The thing I'll carry forward
I'm going to spend my career building things — software, processes, systems, teams. And every time I do, I'm going to remember what it felt like to be on the other end of something that was built without the user in mind.
Not as a design principle. As a personal standard. Build things that treat the person using them as intelligent. Build things that fail clearly. Build things where, if something goes wrong, the next step is obvious.
Customer service didn't teach me to be more patient with people. It taught me to be less patient with poorly designed systems.