Why Saying “I Don’t Know” Can Make You a Better Project Manager

 

The idea that a project manager must have all the answers is one of the most common illusions in the early career.

It is partly cultural. In some organizations, managers are expected to be “the experts.”

It is also personal. When you are starting out, you want to prove you deserve the role. That combination creates pressure to speak, even when you should stay quiet.

The problem is that giving the wrong answer just to avoid embarrassment creates bigger issues later.

A misleading estimate, an overpromise, or a technical explanation that is not correct will come back to damage trust. And in project management, once trust is gone, it rarely comes back easily.

There is a paradox here. Saying “I don’t know” can actually build credibility. It may sound counterintuitive, but people value honesty more than fast, shallow answers.

When you admit you do not know something and commit to finding out, three important things happen.

First, you signal that you are dealing with reality, not with appearances.

Second, you show ownership, because you take responsibility to bring the right information later.

And third, you open the door for collaboration, by inviting others to contribute their knowledge instead of pretending you hold it all.

I have seen this in practice many times. At one point, managing a portfolio in a global company, I was asked about a technical issue outside my expertise. I could have tried to improvise, but instead I said, “I don’t have that detail right now, let me bring our architect to explain it properly.” Later, one of the executives told me they appreciated that I did not “play smart” in that moment. 

Still, this does not mean you should throw “I don’t know” around carelessly. How you say it matters.

If you sound nervous or insecure, the message received is incompetence. If you say it calmly, with confidence and a clear next step, the message received is professionalism. There are many ways to phrase it that protect your authority.

You might say, “I don’t have the data right now, but I will confirm and get back to you tomorrow.” Or, “That is outside my area, let me bring the right person to answer it.” Or, “I want to make sure I give you an accurate response, can I circle back after checking with the team?”

These are small scripts, but they change the perception from weakness to responsibility.

Another nuance is knowing when you should never be in the position of saying “I don’t know.” For example, if you are asked about project goals, key risks, or the overall timeline, you cannot be unprepared.

Those are the foundations of your role, and not knowing them will quickly destroy your standing.

Preparation is non-negotiable for the essentials.

The art lies in knowing which questions are critical to your authority, and which questions are better handled with humility and collaboration.

Think for a moment about the sports field. A coach is not expected to know the exact oxygen intake of every athlete, but they are expected to know the strategy, the formation, and the conditions of the game. When a question falls outside their scope, the right move is to call the medical team, not to invent an answer.

Project management works the same way. You are not supposed to be the expert on every detail. You are supposed to make sure the team of experts works together in the right direction.

Over time, practicing this balance creates a reputation.

People will come to see you as someone who does not bluff, someone who respects facts, someone who knows when to speak and when to defer.

That reputation is far more powerful than being seen as the project manager who always has something to say.

Ironically, it is the willingness to admit not knowing that marks the difference between a task coordinator and a trusted leader.

So ask yourself, what would you rather be remembered for? The project manager who always had an answer, even if wrong, or the project manager who always brought the right answer at the right time?

The truth is, nobody can know everything in a complex project. Pretending otherwise is a trap. Admitting it, with confidence and responsibility, is one of the most underrated skills a young project manager can develop.

And maybe the real question to leave with you is this: when was the last time you gave an answer you were not sure about, and what would have happened if you had simply said, “I don’t know, let me find out”?