Lessons For The Unmerciful Servant

The Hard Truth About Serving Without Expectation

I spent seven years working in nonprofit management before I learned to stop volunteering for things that weren't mine to fix. You'd think the title would give me some kind of free pass to say yes to every request, but the opposite happened. The people who needed me the most were the ones I had to learn to say no to, because saying yes to everyone just meant I wasn't doing my actual job very well. That's not a metaphor. That's just how it works when you're the person everyone depends on and nobody checks in on you. The concept of Lessons For The Unmerciful Servant isn't about martyrdom or suffering in silence. It's about understanding what happens when you give your time, energy, and skill without the other party having any incentive to reciprocate or even acknowledge it. I watched good people burn out in this environment constantly. They called it dedication. It was called being taken advantage of by people who knew exactly how much they could extract before you broke.

What Actually Happens When You Serve Without Merciful Terms

Here's the part nobody tells you about unmerciful service. The recipient doesn't become grateful. They become accustomed. There's a difference between someone who appreciates help and someone who expects it as a baseline condition of the relationship. I had a supervisor once who would come into my office at 4:55 PM on a Friday and ask me to pull a report that took three hours. Not because he needed it by Monday morning. Because he knew I'd do it. The report was never used. He just wanted to know he could ask. The pattern is predictable if you have eyes to see it. Someone asks for a favor. You say yes. The next time they ask, the threshold has already shifted. The favor gets bigger, the timeline gets tighter, and the gratitude gets smaller. By the third or fourth iteration, you're not being asked. You're being directed. And if you push back, suddenly you're the problem. You're not a team player. You don't understand the mission. These are the exact phrases I heard when I finally stopped pulling those reports. What makes this especially insidious is that the server usually believes their own narrative. They tell themselves they're building character, or that hard work will eventually be recognized, or that the people they're serving are too important to worry about fair exchange. All of those can be true in the right context. In the wrong context, they're just rationalizations for staying in a situation that's grinding you down.

How to Recognize the Difference Between Service and Exploitation

The litmus test is simple but hard to apply in the moment. After you've done something helpful for someone, do they make any effort to understand what it cost you? Not money, necessarily. Time. Attention. Mental energy. If the answer is no, and this has happened more than twice, you're not in a service relationship. You're in an extraction relationship. I remember one specific project where I spent approximately 40 hours building a training system for a department that refused to fund it properly. They kept saying they'd circle back to budget allocation. I kept believing them because the alternative was admitting I'd wasted two weeks. When I finally stopped building features and asked for a commitment on resources, the conversation went sideways very quickly. The director told me I was being difficult. A senior colleague pulled me aside and said, "Just finish it. Nobody pays attention to the details." They were right about the details. Nobody pays attention to the details. They pay attention to the person who keeps providing them for free. The workaround I eventually developed wasn't elegant. It was setting a boundary and watching what happened when I enforced it. I told my team that after 5 PM, requests would be logged and addressed the next business day. Not ignored. Delayed. The difference matters because it gives people time to either figure it out themselves or understand that their urgency isn't universal. Within two weeks, the 4:55 PM requests stopped. Not because people became more responsible. Because they realized there was no payoff for being demanding at the end of the day.

The Counter-Intuitive Part Nobody Warns You About

Serving well sometimes requires being less available. This sounds wrong if you're the type of person who gets praised for being always-on. But availability is a finite resource, and spreading it thin across everyone who asks means you're doing mediocre work for too many people instead of excellent work for the right ones. I learned this the hard way when a client came to me with an emergency that turned out to be a formatting error they'd been too embarrassed to ask their own team about. If I'd been truly available, I would've seen through it sooner. Instead, I saw it later because I'd committed to a different project that morning and I stuck to it. The people who benefit most from your service are the ones who treat it as a privilege, not a right. They ask what they need. They offer context about why it matters. They understand that your time has alternatives. If someone can't provide any of that information, they're not ready to receive your help. They're ready to consume it. And there's a real difference between those two states.

When to Walk Away

This is the part that's hardest to write and hardest to act on. You walk away when the pattern is clear and the conversation about changing it has happened at least once, in concrete terms, with specific examples. Not "I feel overwhelmed." Something like "I can't take on additional projects this quarter. Here's what's on my plate and here's what I'm declining." If the response is anger, guilt-tripping, or silent treatment instead of acknowledgment, you now have data you didn't have before. That data should inform your next move. I had a situation where a partner organization expected me to mentor two of their junior staff members at no cost to them. No budget line, no formal agreement, no expectation of reciprocity. Just an email that said "we're counting on you" as though that made it my problem. I sent back a proposal with three options: paid engagement, shared responsibility with their senior team, or a referral to someone else. They chose referral. It took three days to find someone else. They could've done that themselves in three hours if they'd just asked the right question instead of assuming the answer was yes. The unmerciful servant learns that mercy without boundaries isn't kindness. It's enabling. And the people who benefit most from that dynamic are the ones who haven't yet learned to ask for what they actually need instead of taking what's been left within reach. Your job isn't to fix that. Your job is to stop making it easy for them to avoid the lesson.