Why the silence we call kindness is quietly charging interest

AI is moving fast and most people are falling behind. 

The Rundown AI keeps you ahead of the curve. 

It's a free AI newsletter that keeps you up-to-date on the latest AI news, and teaches you how to apply it in just 5 minutes a day.

Plus, complete the quiz after signing up and they’ll recommend the best AI tools, guides, and courses — tailored to your needs.

Sign up to start learning.

Fellow project or program manager,

Early in my career, I watched a good teammate I supervised become disengaged over time, and I said nothing and did not reach out to her.

She was talented and well liked, however over a few weeks her commitments began to slip. A deliverable a few days late. Then a status update that never arrived. I told myself the kind thing to do was to give her room. I did not want to embarrass her, and if I am honest, I did not want the discomfort of the conversation either. So I waited. I covered the gaps. I reworded my own management report updates to make the delay look smaller than it was. A few weeks became a couple of months, and by the time the problem was too large to hide, the trust between us had already thinned and the ongoing operational projects had paid for my silence in ways I could not take back.

Here is the part I did not expect. When I finally sat down with her, the conversation I had dreaded for weeks went nothing like the disaster I had rehearsed. She was not defensive. Instead, she was relieved. Something was going on that I had never thought to ask about, and once we addressed it openly, we could actually solve it together. The relationship did not break. It grew stronger. And I walked away with a lesson that has shaped the way I think about work relationships ever since. My avoidance had been costing me the very thing I was trying to protect.

Most of us are carrying at least one conversation right now that we know we need to have and keep finding reasons not to. The teammate whose work has slipped. The stakeholder who nods in the meeting and de-prioritizes the tasks we need them to complete afterward. The PMO co-worker whose comment landed wrong three weeks ago and still has not been addressed between you.

Do we tell ourselves that letting it go is the right choice? Do we call our avoidance patience, or professionalism, or keeping the peace, when what we are really protecting is our own comfort?

I understand the instinct completely, because I lived it. For an early-career project or program manager the fear runs even deeper, because so much of the work happens through people who do not report to you. You manage by influence and relationships rather than authority, and it feels as though one hard, difficult conversation could cost you the very goodwill you depend on to get anything done.

Here is what I have learned real managing projects. Silence is not free. The missed commitment we choose not to address quietly becomes the standard the team learns to expect. The frustration we swallow does not disappear. It leaks out sideways, in our tone and in the trust others place in us. We want interest to work for us, not against us, and an avoided conversation is a debt that compounds. It grows in the dark until it costs far more than the conversation ever would have.

This is the reframe I most want you to carry out of this issue, because it changes everything about how the conversation feels before you walk in.

A servant leader does not have the difficult conversation to win it. We do not have it to discharge our own frustration or to feel the small relief of finally saying the thing verbally. We have it because the other person deserves the truth in a timely manner to do something useful with it. That is the whole difference. Withholding a concern to protect our own comfort is not kindness, even though it wears the costume of kindness so convincingly that we fool ourselves. It robs a project team colleague of the chance to grow, to adjust, or simply to explain what we could not see from the outside.

Think about what avoidance actually does to the person on the other end. When we stay quiet about a problem, we are deciding, on their behalf and without their consent, that they are not capable of receiving hard feedback and responding to it well. We are managing them as a fragile thing to be worked around rather than respecting them as a professional who can handle the truth. My cross functional teammate did not need my protection. She needed my honesty, and she needed it weeks before she got it. The most caring thing I could have done was also the thing I was most afraid to do.

I have come to believe that the willingness to have the honest conversation is one of the truest tests of servant leadership we ever face. It is easy to serve people by making their day smoother. It is much harder, and far more valuable, to serve them by telling them what they need to hear so they can become who they are capable of becoming. Presence, the steady and credible way we carry ourselves, is what earns us the standing to be believed in that moment. The difficult conversation, handled with care, is where we spend that standing well. We are not choosing between the relationship and the truth. Told with respect and timely, the truth is what deepens the relationship.

None of this makes the conversation easy, and I would be doing you a disservice to pretend otherwise. What helps is having simple courage to follow through with the potentially difficult conversation, so the moment stops feeling like a cliff edge and starts feeling like a path. Here is the strategy I return to, and each piece of it becomes a concrete step for you below.

Open with the shared goal rather than the grievance, so the other person knows from the first sentence that you are on the same side of the table. Describe what you actually observed in specific and factual terms, not in judgments about their character. Ask a genuine question and then truly listen, because most of what looks like resistance turns out to be a pressure or a private need you simply had not seen yet. Then agree together on one concrete next step, so the conversation ends in shared motion instead of lingering tension. That is the entire method. It is not complicated. It is just deliberate, and being deliberate is exactly what turns a dreaded confrontation into an act of service.

Travis Bradberry, in his book Emotional Intelligence 2.0, gives us the research backing underneath everything above. His work maps emotional intelligence across four skills, and the one most of us find hardest is relationship management, the ability to use our awareness of ourselves and others to handle our interactions well, especially the potentially difficult ones. Bradberry's point is that the conversations we avoid are precisely the ones that quietly erode trust, because avoidance does not protect a relationship. Over time it starves it.

Bradberry states that the strength of our relationships is decided by our willingness to step into the difficult conversations rather than avoid them.

Read that as a project leader and not merely as a manager of tasks. Every conversation we sidestep to keep the peace is a small withdrawal from the account of trust we depend on to lead. The people around us feel the withdrawal even when we say nothing, and in the long run it quietly costs us the credibility we were trying so hard to keep.

I do not want you to simply read this and move on. I want you to take it into a real relationship this week. Here are three deliberate steps you can start now.

1.     Identify the one conversation you are avoiding with a specific project team colleague or stakeholder, and name what the silence is already costing. Write down the single conversation you have been putting off, then write down what the avoidance is costing you, the project team, and the other person right now. Seeing the compounding cost on paper is usually what turns a dreaded conversation into an obvious one. You cannot manage a debt you refuse to look at.

2.     Open with the shared project goal, and describe what you saw, not who they are. Begin the conversation with the project outcome you both want, then describe the specific behavior you observed in factual terms. "The last two updates came in after the deadline" is something a person can actually work with. "You are unreliable" is something a person can only defend against. Deliberately separate the behavior from the character, every single time.

3.     Ask one real question, then stop talking. After you have named your concern, ask what you might be missing and then let the silence do its work. Most of the time the thing that looked like resistance is a pressure or a need the other person has been carrying alone. The conversation you feared as a confrontation becomes the moment the relationship finally gets honest.

As you learn to have the hard or potentially difficult conversation early and with care, something quietly shifts. You stop paying compounding interest on the truths you were too afraid to uncover with other people. You become the project leader people trust precisely because they know you will tell them what they need to hear while there is still time to use it. That is a very different way to lead than managing around problems and hoping they resolve themselves, and it is fully available to you, one deliberate conversation at a time. You can do this!

Now I would like to hear from you. Reply to this issue and tell me the one conversation you have been avoiding with a project stakeholder, and the first honest sentence you plan to open it with. I read every reply, and the best ones may show up in a future Voice from the Field so we can learn from one another.

One more thing. Everything I have written here comes out of the book I am writing on servant leadership and emotional intelligence skills for project and program managers. If you would like to go deeper on how honest, human-centered conversations build the trust that carries a project, you can download Chapter 5 of my upcoming new book, free. Just reply and I will send it your way.

Serve well, lead well, and grow the leaders around you.

Mark

On Becoming a Servant Leader is a bi-weekly newsletter on servant leadership and emotional intelligence for project managers who want to deliver valued outcomes for their teams and the people they serve.