When Grace Becomes Cruelty
Protecting Your Team
The engineering director waited six months too long. His lead developer had been struggling for more than a year, missing deadlines, producing code that required constant rework, and growing visibly resentful whenever anyone raised a concern. The director believed in grace. He believed in patience. He gave the developer more time, more resources, more opportunities to turn it around. Meanwhile, the rest of the team was absorbing the cost. The senior engineers spent their evenings cleaning up the lead developer’s code. The project manager restructured schedules around missed milestones. The junior developers watched and learned that poor performance has no consequences. When the director finally acted, three good engineers had already updated their resumes and started interviewing. The director had not been kind. He had been negligent, and his negligence cost the team the people he should have been protecting.
The hardest reversal in leadership is this: sometimes the most loving thing you can do is end someone’s tenure. We talk about grace as if it always means keeping someone in place. We talk about patience as if it always means waiting longer. Grace is not a single move, however. It is a judgment about what a person needs. What a person needs is not always another chance in the same role. Sometimes what they need is a clean break, a different path, or the honesty of a hard conversation they have been avoiding. The leader who refuses to make that call is not protecting the struggling employee. They are protecting themselves from the discomfort of the conversation, and the team is paying the price.
Proverbs 31:8-9 (NLT) calls the leader to a different posture. “Speak up for those who cannot speak for themselves; ensure justice for those being crushed. Yes, speak up for the poor and helpless, and see that they get justice.” These verses are most often applied to the vulnerable outside an organization, and that reading is valid. The same principle applies inside it, however. The weakest members of your team cannot always speak for themselves. The people who are “being crushed” by a leader they cannot confront need someone to speak on their behalf. They need the leader in authority to see what they cannot say and act on what they cannot change. When a struggling leader in a position of power is allowed to continue failing, the people beneath them are the ones who cannot speak for themselves. The director’s job is to speak for them.
The same insight appears in Ezekiel 34, where God condemns the shepherds of Israel for failing to protect the flock. Verse 4 (NLT) says, “You have not taken care of the weak. You have not tended the sick or bound up the injured. You have not gone looking for those who have wandered away and are lost. Instead, you have ruled them with harshness and cruelty.” The passage is devastating, but notice what it does not say. It does not accuse the shepherds of being mean. It accuses them of being absent. Not taking care is the sin. Not tending is the failure. The shepherd who fails to remove a wolf from the flock has not failed because he was unkind to the wolf; he has failed because he was negligent toward the sheep. The leader who allows a struggling team member to drain the rest of the team is not being kind to the struggling individual. They are failing to protect the people who trusted them to make the hard call.
This brings us to the framework for distinguishing grace from negligence. After watching this pattern play out across multiple organizations and making the mistake both ways, I have found three questions that clarify the decision.
The first question is about the team. Is the struggling person’s performance creating work, stress, or morale damage for others? If the answer is yes, the situation has already moved beyond a private performance issue. It is a team culture issue. The leader who frames the decision as “do I keep this person or let them go” is missing the real question, which is “do I protect the team or sacrifice them to my reluctance to act?” Grace that isolates the team impact is not grace. It is avoidance with a theological justification.
The second question is about the person. Have they been given a genuine opportunity to recover? This requires specificity. Vague feedback is not an opportunity. “You need to improve” is not a plan. The standard from Thursday’s article applies here. Ownership, plan, and timeline. If the person cannot name what they did wrong, cannot articulate what they will do differently, and does not have a clear review period, they have not been given a real second chance. They have been left in limbo. The leader who has not provided those conditions has no business reaching for the termination conversation yet. They have work to do first.
The third question is about the leader. Am I delaying this decision because of my own discomfort? This is the hardest question because the answer is often yes and the leader is the last person to admit it. Termination conversations are brutal. They exhaust you emotionally, they create anxiety in the weeks leading up to them, and they make you question every decision afterward. Avoiding that discomfort by giving “one more chance” is seductive because it lets you feel merciful without doing anything hard. The team knows what is happening. The struggling employee often knows what is happening. The only person pretending not to see is the leader who does not want to have the conversation. If the first two questions are answered (the team is being harmed, and the person has been given a real opportunity), the third question is the tiebreaker. If you are delaying because the conversation will be hard, you have your answer. The hard conversation is exactly what the team needs you to have.
Let me walk through a specific case. A department head I know had a manager who was brilliant at strategy and terrible at people. The manager could design a quarterly plan that outperformed every projection, but he could not run a team meeting without leaving two or three people in tears. The department head gave feedback. The manager improved for a week and regressed. She sent him to leadership training. He came back with vocabulary but no change. She reassigned him to an individual contributor role with a pay cut and told him the next step was exit. He accepted the change. Within three months, two of the team members who had been closest to leaving told the department head that they felt seen for the first time in two years. The department head had been so focused on saving the manager that she missed what she was losing: the rest of the team.
The city of refuge structure in Numbers 35 is a useful frame here. God established cities where someone who had killed accidentally could flee for safety. The protection was real, but it was not open-ended. The person had to stay in the city until the death of the high priest. There was a boundary around the refuge. The protection had a shape, and that shape prevented the refuge from becoming a sanctuary for guilt. The same principle applies in leadership. Grace needs boundaries. A struggling team member should get real support, real feedback, and a real timeline. There is a point, however, where ongoing protection becomes harm. The boundary is crossed when the team’s health is being sacrificed to maintain the appearance of grace.
I have made this mistake myself. I have kept someone in a role too long because I did not want to be the person who gave up on them. I told myself I was being patient. I was being generous. I was being the kind of leader who did not discard people. What I was actually being was a coward who let the team absorb the cost of my unwillingness to act. The person I was trying to protect eventually failed in a way that was more public and more damaging than it would have been if I had acted earlier. My delay did not protect them. It made their failure worse and cost the team more than it should have. I learned that the leader who waits too long to act is not merciful. They are negligent, and their negligence has a body count measured in the trust and morale of the people who stayed.
Proverbs 31 calls us to speak for those who cannot speak for themselves. Sometimes those people are the struggling team member who needs you to have an honest conversation they are too afraid to start. Other times they are the rest of the team, who need you to make a decision that protects them from a leader who should not be leading anymore. Grace is not a yes to every request for patience. Grace is the wisdom to know what a person actually needs, and the courage to give it to them even when it costs you something to deliver.
Leadership Challenge: Is there someone on your team right now whose ongoing struggle is creating work, stress, or morale damage for others? Have you given them a genuine opportunity to recover with ownership, plan, and timeline? Or are you delaying the hard conversation because you do not want to have it? The team is watching. They already know what you have not done yet.
I write about leadership at the intersection of timeless principles and modern workplaces. Follow for weekly insights on building teams that actually work. For more articles like this consider subscribing or sharing.