A Client Horror Story
That time when you ruin Christmas nationwide for a missing single character of code…
Watch the full episode →Hey everyone, welcome to another episode. I’m genuinely excited about this one because I’ve got with me tonight someone I’ve been looking forward to having on the show for a while—the one, the only, the awesome Andy Reinhold. Andy, how are you doing tonight?
I’m doing great, Morgan. Thanks for having me. I’ve been looking forward to this.
I’m glad you’re here. Before we dive into what I suspect is going to be a wild story, I have to ask—what are you drinking? That looks like something worth talking about.
Tonight I’m finishing up a bottle of Monkey Shoulder. It’s a blended malt Scotch—really smooth, easy to drink, and honestly a great introduction if you’re just getting into Scotch. Not too hard to find either, which is important.
I love that you factored in accessibility. Every once in a while someone comes on here and casually mentions some rare, impossible-to-find, hundred-year-old bottle like we’re all just supposed to relate. I’m like, no—I need something I can actually buy. I was thinking of grabbing a Macallan tonight, but I figured I should stay grounded. I’ve got to perform.
Exactly. You’ve got to perform.
Speaking of performance, let’s jump straight into it. I’ve got my drink—well, technically water, but let’s pretend—and I’m ready. Tell me everything.
Alright. So, I used to work as a consulting manager at a Big Four consulting firm. This was a number of years ago, so I feel safe telling the story now. My focus was on large-scale technology transformation projects—specifically modernizing legacy systems. And when I say legacy systems, I mean really legacy. Think mainframe-level stuff. You’ve probably heard about mainframes in history books or maybe in passing, but the reality is they’re still everywhere. Government systems, financial institutions—there’s a surprising amount of critical infrastructure still running on software originally built decades ago.
Every once in a while I read something about governments trying to update systems that are running on software older than the engineers maintaining it.
That’s exactly the kind of thing I was working on. In fact, this story specifically involves a system tied to Social Security. I was working on the state side of things. So, there’s this complex relationship between federal systems and state systems. The federal government sets overarching rules, but states handle a lot of the actual administration—determining eligibility, processing payments, managing cases. That means constant communication and data exchange between systems. My job was to manage a massive project to modernize a portion of the state system—taking software that had originally been built for mainframes and moving it onto a more modern architecture.
That sounds like one of those things where, if it goes well, no one notices—but if it goes badly, it’s catastrophic.
Exactly. That was literally our goal: flip the switch and no one notices. That’s success. But the reality was… the risk was enormous. We were dealing with software that had evolved over decades. Every policy change, every new administration, every legislative tweak—everything had been layered into this system. It wasn’t clean. It wasn’t elegant. It was a dense, tangled web of logic that had been patched and extended for years. And on top of that, the people who understood it were retiring.
That’s a risk I’ve honestly never thought about before—knowledge literally disappearing.
It was happening constantly. Every month, someone retired. And with them went years—sometimes decades—of institutional knowledge. We’d hit a piece of code, have no idea what it meant, and the one person who could explain it had just left the week before. So now imagine this: a massive, high-stakes system, millions of lines of code, evolving rules, and shrinking expertise. And we had to modernize it.
No pressure.
None at all. We ended up building a team that eventually grew to over a hundred people. Developers, analysts, testers—everyone working together to manually analyze and recreate this system. And when I say manually, I mean it. We didn’t have the advanced AI tools people talk about today. We had humans reading code. Interpreting it. Mapping it out. At one point, I had someone calculate how many lines of code we were dealing with. It was in the millions. I still wear that as a badge of honor—we analyzed a million lines of code with human effort.
That’s both impressive and terrifying.
It was both. After months of work—almost a year—we finally completed our portion. We tested everything, reviewed it with the government, coordinated with federal systems, and eventually… we went live. And for three weeks, everything was perfect. No complaints. No anomalies. No alerts. Silence. We thought we had done it.
That’s the most dangerous kind of silence.
Exactly. Then mid-December rolls around. Saturday morning. I got an email from my senior manager—cryptic, urgent. Then a call. “There’s a big problem,” he says. “Don’t check the news.” So of course, I check the news. And I found a local newspaper article. The headline—paraphrased—basically says our company has ruined Christmas.
Oh no.
Yeah. The article explains that people in the state had started noticing something strange—their Social Security checks were smaller than expected. Not dramatically smaller. Not something that would trigger system-wide alarms. But smaller. And here’s the thing: from a statistical perspective, it looked like noise. Normal variation. Nothing alarming. But for the individuals receiving those checks? It mattered. If you’re relying on that money to buy groceries, pay bills, maybe even get presents for your family—being short even a few dollars is a big deal. And there was a video in the article. A man saying he couldn’t afford presents for his family. That’s when it hit. We hadn’t just introduced a bug. We had impacted real people.
That’s when it stops being abstract.
Completely. We mobilized immediately. Full war room. Senior leadership involved. Long hours, rotating shifts—we worked nonstop. Within about 48 hours, we were able to patch things enough to ensure people received the correct payments. But we still didn’t know what caused the issue. That part took longer. Weeks. Every day the system ran, more incorrect payments were being generated. We were fixing them as they appeared, but the root cause remained hidden. Finally, after Christmas, we found it. It was a single logical error. Instead of using “greater than or equal to,” the code used “greater than.” One missing “equals.” That’s it. That tiny omission affected a small subset of people—but consistently. And because it was such a narrow edge case, it slipped through everything.
That’s both horrifying and kind of poetic.
Yeah. It’s one of those things that perfectly illustrates what software really is—just a long chain of precise rules. And if one rule is even slightly off, the consequences can ripple out in ways you don’t expect. Looking back, there are two things that really stayed with me. First, the people. Even after everything, my team and I could eventually laugh about it. We had been through something intense together. Second, the personal impact. At the time, I took everything incredibly personally. The news coverage, the pressure, the responsibility—I internalized it all. I was anxious, stressed, constantly questioning myself. It wasn’t until later—after I left, after I went through therapy—that I realized how much I had tied my identity to my work. I had anxiety. I had this deep need to prove myself. And that environment—high pressure, high stakes—it amplified everything.
I’ve heard that about consulting firms—they often hire people who take things personally because those people push themselves harder.
That’s exactly right. And I fit that mold perfectly. I had a chip on my shoulder. I wanted to prove myself. And it worked—I performed well, got recognized, moved up quickly. But it came at a cost. Eventually, I had to step back and ask myself: how much of this is worth carrying personally? Because at the end of the day, we fixed the issue. No one was permanently harmed. And I learned something important—You can care deeply about your work without letting it consume you.
That’s a powerful takeaway.
Yeah. And honestly, that’s what I carry forward now. Do your best. Take responsibility. But don’t lose yourself in the process. Because sometimes, all it takes is one missing “equals” to remind you how human everything really is. That’s how I looked at it at that time—and it makes sense.
What’s fascinating about your story, though, is how unique it is compared to most client horror stories we hear. Every story is different, of course, but this one stands out in a very specific way. At the time, it was clearly a disaster for the client—bad press, public scrutiny, real-world consequences. But for you personally, in that exact moment, it felt like an exciting challenge. You were young, ambitious, rising fast. It felt like an opportunity. And then, years later, you look back and realize—this was exactly the kind of environment that slowly pulls you into something unsustainable. Something that, over time, becomes miserable.
Yeah. That’s exactly right. That’s a really good way to put it. And honestly, if I went back now, knowing what I know today, I think I’d handle it differently. I’d still take on something challenging—but I’d navigate it better. I’d set better boundaries. I’d be more aware of what it’s doing to me. But in your twenties? It’s really hard to see that. When you’re in it—working 60-hour weeks, constantly chasing the next milestone—you just don’t have the perspective. You’re too deep in it. At least, I was. I know some people can handle that pace long-term, but for me, it didn’t work. I remember one of my last conversations before I left. There was a partner I really admired—someone I wanted to be like. I sat down with him and told him, honestly, that I really wanted to make it work… but my body just couldn’t keep up anymore. And that was the truth. Physically, I couldn’t do it anymore. I had to stop.
Wow. That’s… powerful. And also very real. I really appreciate that shift in perspective—that you were able to step away, reflect, and actually see what was happening. Because a lot of people don’t. They just keep climbing, keep pushing, and then—decades later—that’s their whole life.
Yeah. Exactly. Now, I try to approach things very differently. I’ve spent a lot of time in therapy, a lot of time reflecting, and I’ve realized that I need structure—not just in work, but in how I make decisions about my life. So I use systems and frameworks now. That’s how I operate. One of the biggest ones for me is what I call a “values compass.” I define my core values, and then I use them to guide both big and small decisions. For me right now, those values are freedom, self-care, and authenticity. And they can evolve over time—but as long as I’m making decisions that align with those values, I know I’m on the right path. There’s a book that really influenced this way of thinking for me— Designing Your Life by Bill Burnett and Dave Evans. I recommend it all the time. One of the key ideas from that book is that there’s no such thing as the “right” choice—there’s only good choosing. So if I make a decision based on my values, even if things don’t work out perfectly, I’m still okay with it. Because I know I made that choice intentionally.
I’ve never heard of that book or that exact concept, but it really resonates with me. It aligns a lot with how I think about work and business. I’m very process-oriented. I care deeply about the process —how decisions are made—more than obsessing over whether the outcome is perfect. Because if your process is strong, your outcomes tend to be strong. And what you’re describing is basically the same thing—but applied to life decisions. Also, I love the phrase “values compass.” That’s a great way to frame it. What’s interesting, though, is how different people define their values. For example, you mentioned authenticity. And for me personally, I’ve always had a bit of skepticism about that value. Because in my experience, if you just tell people to “be authentic,” a lot of the time that doesn’t lead to great outcomes. Some people’s “authentic self” isn’t exactly something we want to encourage. Like, if someone says, “My authentic self just wants to make money and take advantage of people,” that’s… not great. So it raises an interesting question—how do we think about authenticity in a meaningful way?
Yeah, that’s a really fair point. And honestly, it’s something I’ve thought about a lot. There’s another book I read— Reinventing Your Life by Jeffrey Young and Janet Klosko. I’m not a huge fan of the title, but the content is incredibly insightful. It’s rooted in cognitive therapy, and the authors were actually students of Aaron Beck. The book introduces this concept of “life traps”—patterns of thinking and behavior that people fall into based on past experiences, often tied to childhood or trauma. And what’s interesting is that a lot of the behaviors we see in people—like chasing money at all costs, or being overly competitive, or shutting others out—can actually be traced back to these deeper patterns. They’re often coping mechanisms. For me, that was definitely true. When I was chasing success, climbing the ladder, pushing myself to the limit—it wasn’t just ambition. It was also about trying to compensate for something deeper. For example, one of my life traps was feeling unseen—like I wasn’t acknowledged enough. So my way of dealing with that was to achieve. To prove myself on paper. So when I talk about authenticity now, I don’t mean it in the sense of “this is exactly who I am and I’m fully aligned with it.” It’s more aspirational. I don’t fully know who I am yet. That’s something I’m still figuring out. And authenticity, for me, is about moving closer to that understanding over time. It’s a goal, not a fixed state.
That’s a really thoughtful way to frame it. It actually reminds me of something from ancient philosophy—“know thyself.” It’s one of the foundational ideas in Greek philosophy, especially associated with Socrates. So in a way, what you’re describing is very much in that tradition—this ongoing process of self-discovery. And I think there’s a way to reconcile both perspectives on authenticity. There’s a line I remember from a book I read years ago— Zen and the Art of Motorcycle Maintenance . I might be paraphrasing, but the idea goes something like this: “How do you write something amazing? First, become an amazing person. Then just write naturally.” And I think that idea applies more broadly. If you want to be authentic in a meaningful way, it’s not just about expressing whatever you feel in the moment. It’s about becoming someone worth expressing. Then, authenticity becomes powerful.
That’s really interesting. I like that a lot. And I think I see that in people I admire. Not necessarily people in the spotlight—but people I’ve worked with, mentors, individuals who stand out. They’re not perfect, but they’re exceptional in their own way. They’ve developed something deeply—whether it’s communication, technical skill, or just how they relate to others. I had one mentor who was incredible at building relationships. He paired strong technical knowledge with outstanding interpersonal skills. Watching him interact with clients—it was like an art form. A lot of what I learned about client communication came from observing him. He had mastered something. And that made him interesting, impactful. So yeah, I think there’s truth to what you’re saying—develop something deeply, something that energizes you, and then build from there.
Exactly. And I’d add that part of the journey is learning to recognize the difference between two types of difficulty. There’s the kind of difficulty that comes from being on the wrong path—and there’s the kind that comes from being early in the learning process. In the beginning, almost everything feels hard. It’s what I like to call the “valley of suck.” The challenge is figuring out—am I struggling because this isn’t right for me, or because I just haven’t gotten good at it yet?
That’s such a great way to put it. I actually think about that with my son. He’s four, and he gets frustrated easily when something doesn’t come naturally. So I try to tell him: “Practice makes it easy.” Not perfect—easy. Because perfection isn’t really the goal. You’re never going to do something perfectly every single time. But you can get to a point where it feels natural, where it flows.
I love that distinction. And to tie it back to client management—one of the frameworks I use is this: every client breakdown is always the responsibility of both sides. Not equally, necessarily. It could be 99.9% the client’s fault and 0.1% yours. But that 0.1% still matters. Because that’s where your opportunity to improve is. If you focus on that small percentage—what you could have done better—you get stronger over time. And eventually, the things that once caused major problems become manageable, even trivial.
Exactly. That’s where growth happens. You go through enough of these situations, and what once felt overwhelming becomes routine. You build experience, resilience, perspective. And that’s when things start to click.
And I think that’s a perfect note to end on. This conversation went in a lot of different directions—but there’s a kind of elegance to how it all connects. From client disasters to personal growth, from parenting to philosophy—it all ties together. And honestly, kids might just be the ultimate difficult clients.
They really are. The most difficult—and the most important.
And definitely the only ones you can’t fire.
Exactly.
Andy, this has been fantastic. I’ve really enjoyed this conversation—getting to hear your story, your reflections, and everything you’ve learned along the way. And to everyone who made it all the way to the end—thank you for listening. We hope you enjoyed it and took something valuable from it. ©2026 Client Horror Stories by Beloved by Clients – Privacy Policy, Terms & Conditions – Resources – Beloved by Clients