Why Your Project Team Isn't Telling You the Truth

Everything is green. The weekly status report says the project is on track, the major milestones are achievable, and the team assures you that everything is under control. As the project manager, you feel reasonably confident that things are progressing as planned.

Then the trouble starts. A critical deliverable misses its deadline. A technical problem that nobody mentioned turns out to be much more serious than expected. A key dependency isn't ready, or a customer discovers that the solution doesn't meet an important requirement. Suddenly, the project is in trouble, and you find yourself asking a question that every project manager has asked at one time or another: Why didn't anyone tell me?

Sometimes, the explanation is straightforward. More often, however, the reasons are complicated. Team members may be reluctant to deliver bad news or convinced that they can resolve a problem before anyone else notices.

When project managers are repeatedly surprised by information that should have surfaced earlier, they need to look beyond individual behavior and examine the environment in which their teams work. The problem may not simply be that people aren't telling the truth. It may be that something about the organization or project culture makes telling the truth difficult, uncomfortable, or seemingly unnecessary.

Silence Is a Symptom

Not every inaccurate status report is a lie. Sometimes, a team member knows a task is behind schedule but believes the delay can be made up. Someone else reports that a deliverable is nearly complete, even though several unresolved issues remain. Another person discovers a potential problem but decides it isn't worth mentioning until there is more evidence.

These situations are different from deliberate deception, but they can have the same effect on the project. The project manager makes decisions based on incomplete or misleading information, and opportunities to respond disappear over time.

There are several reasons people withhold information. Some fear criticism or damage to their professional reputation. Others worry that reporting a problem will result in additional work or conflict with a manager or colleague. Team members may also believe that the project manager is under pressure to show progress and doesn't want to hear anything that threatens the schedule or budget.

Sometimes, the problem is a lack of clarity. For example, a developer may not recognize that a technical concern could affect another team's deliverable. They may not understand which issues require immediate escalation and which can be handled independently.

Project managers should resist the temptation to treat omissions as dishonesty. The first step is to understand why the information wasn't shared. Was the individual deliberately misleading the team or operating under a different understanding of the situation?

The distinction matters because the solution depends on the cause. Deliberate deception may require formal accountability, while unclear expectations call for better communication and management practices. Fear of punishment, meanwhile, may require the project manager to change how problems are discussed and addressed.

When Bad News Is Punished

Consider a project team member who discovers that a critical task will take three additional days to complete. During the status meeting, the project manager asks why the work isn't finished. The manager expresses frustration, questions the person's competence, and demands to know why the original estimate was wrong.

The team member leaves the meeting with a clear impression: reporting a problem leads to an unpleasant experience. The next time a task begins to slip, that person may wait a few days before bringing it up, hoping to get back on schedule. If the problem gets worse, the delay in reporting it makes the situation even more difficult to resolve.

This is how a project manager can unintentionally train a team to conceal problems. The manager wants early warnings but responds to them in ways that discourage them. Over time, team members learn to present the most positive version of events rather than the most accurate one.

This doesn't mean project managers should ignore missed commitments or accept every explanation without question. Accountability is essential; the important distinction is between accountability and blame.

Accountability focuses on understanding what happened and preventing a recurrence. Blame focuses on finding someone to criticize or punish, often before the facts are fully understood. One approach encourages learning and problem-solving; the other encourages defensiveness.

When someone raises a problem early, acknowledge the value of the warning before discussing the circumstances. You might say, "I'm glad you brought this up now. Let's understand the impact and figure out our options." That response doesn't eliminate responsibility for the problem, but it reinforces the importance of timely communication.

Of course, the manager should also investigate why the issue occurred and whether the original commitment was realistic. The objective is to solve the problem and improve future performance, not to make the person who reported it regret speaking up.

Psychological Safety

The concept of psychological safety has become increasingly important in discussions about team performance. In practical terms, it means that people believe they can ask questions, admit mistakes, challenge assumptions, and raise concerns without being humiliated or unfairly punished.

This is particularly important in project management. Projects involve uncertainty and circumstances that are not always under the team's control. Even experienced professionals cannot anticipate every problem. A successful project team needs people who are willing to identify risks and question assumptions before those issues become expensive surprises.

Psychological safety, however, is not the same as making everyone comfortable all the time. It doesn't mean that every opinion must be accepted, that mistakes have no consequences, or that team members can disregard their commitments. People should feel safe raising concerns, but they must also be willing to explain their decisions, take responsibility for their work, and participate in resolving problems.

Project managers can encourage a safe environment by inviting disagreement during planning and decision-making. Instead of asking whether everyone agrees with a proposed schedule, ask what might make the schedule unrealistic. Rather than assuming that a solution is technically sound because the most experienced person supports it, invite others to identify weaknesses or alternatives.

Questions such as "What concerns you most about this plan?" and "What assumptions might turn out to be wrong?" can uncover issues that a routine status review misses. Asking "If this deliverable were going to fail, what would be the most likely reason?" encourages people to consider possible problems before they occur.

The project manager's response to the answers is just as important as the questions. If someone raises a legitimate concern that the manager dismisses or becomes defensive about, the invitation to speak openly loses credibility.

Creating psychological safety requires consistent behavior. People must see that candid communication is welcomed, considered seriously, and used to improve project decisions.

Stop Encouraging Optimistic Answers

Some project management practices unintentionally encourage people to provide answers that sound better than reality. Consider the question, "Will you finish by Friday?" An uncertain team member may still answer yes because Friday is the expected deadline and saying anything else feels like admitting failure.

The answer might reflect genuine optimism rather than dishonesty. Nevertheless, it gives the project manager a misleading impression of the work's status and the likelihood of meeting the deadline.

A better approach is to ask questions that reveal the evidence behind the forecast. What work has been completed? What remains? Are there unresolved dependencies? What could prevent completion by Friday? How confident is the team member in the estimate, and what assumptions support it?

These questions encourage a more realistic discussion. They also help the project manager distinguish between a commitment supported by evidence and a hopeful prediction.

Status reporting deserves similar attention. A green status indicator means very little if team members use different definitions of "green" or believe that reporting yellow will make them appear unsuccessful. Establish clear criteria for progress and status, and apply those criteria consistently. If a deliverable is considered complete only when it meets defined acceptance requirements, don't allow a team member to report it as complete simply because most of the work is finished.

Project managers should also recognize that estimates are forecasts. An estimate can be reasonable even when the outcome eventually differs from the prediction. The purpose of estimating is to support decisions. There will still be uncertainty.

When team members understand that honest forecasts are more valuable than optimistic promises, they are more likely to report uncertainty when there is still time to act.

Create Ways for Problems to Surface

Weekly status meetings and written reports are useful, but they shouldn't be the only ways a project manager learns about problems. Some people are comfortable raising concerns in a group; others prefer a private conversation or time to organize their thoughts before discussing a difficult issue.

Regular one-on-one conversations can uncover concerns that might not emerge in a larger meeting. Ask team members what is preventing them from making progress and what decisions or support they need. These discussions should focus on helping people succeed. Do not give the impression you are checking whether they are doing their jobs.

Risk reviews are another opportunity to discuss emerging threats and uncertainties. Retrospectives and lessons-learned sessions can help teams identify patterns in how problems are reported and handled. Anonymous feedback channels may also be useful. When team members are reluctant to raise sensitive concerns directly, they should supplement conversations.

The project manager should make it clear that raising a concern doesn't automatically mean the person reporting it must also have the solution. Team members should be encouraged to suggest options, but they shouldn't feel compelled to solve every problem independently before bringing it to the manager's attention.

Most importantly, follow through. If a team member reports a recurring obstacle and nothing happens, the person may conclude that reporting problems is a waste of time. Even when a concern cannot be resolved immediately, explain what was considered, what action will be taken, or why the issue must be accepted.

Communication improves when people see that sharing information leads to meaningful discussion and appropriate action.

What to Do When Misled

Sometimes the problem is neither an unhealthy team culture nor a misunderstanding. Individuals occasionally conceal mistakes, knowingly misrepresent progress, or make commitments they have little reason to believe they can meet. Project managers need to be prepared to address those situations as well.

Start by verifying the facts. A difference between a status report and actual progress doesn't prove intentional deception. The individual may have misunderstood the accuracy of information or made an overly optimistic estimate. Speak with the person privately and allow them to explain discrepancies.

Focus on observable facts and consequences rather than assumptions about motives. Explain what was reported and how an inaccuracy affected the project. Ask what happened and what needs to change so that future reports are reliable.

Depending on the circumstances, the appropriate response might include clearer milestones, more frequent checkpoints, objective evidence of completion, or additional support. If the individual repeatedly misrepresents information despite clear expectations and opportunities to correct the behavior, more formal performance management may be necessary.

Trust doesn't require a project manager to accept every statement without verification. In fact, clear expectations and consistent validation can make reporting more reliable. The key is to apply appropriate controls without treating every uncertainty or setback as evidence of misconduct.

A healthy project environment combines open communication with accountability. People should be able to report problems without fear of humiliation, but they must also understand that deliberately misleading the project manager is unacceptable.

Candor in Project Culture

Improving communication requires more than telling the team to be honest. Project managers must demonstrate, through their daily behavior, that accurate information matters more.

Start by examining your own reactions. When someone reports a problem, do you immediately criticize the person or challenge their assumptions? Status meetings should encourage realistic assessments. Do not reward the people who consistently report green.

Then establish practices that make candid reporting part of routine project work. Define what constitutes red, yellow, or green progress. Regularly discuss risks and dependencies, and encourage team members to identify weak or unfounded assumptions. Ask for evidence when commitments are uncertain and recognize people who raise problems early.

Don't expect a cultural change overnight. If team members have spent months learning that bad news produces criticism, they may need time to believe that a different approach is possible. Consistency matters more than one well-intentioned conversation.

Watch for signs of improvement. Problems begin surfacing earlier. Forecasts include realistic uncertainty. Team members challenge unrealistic commitments rather than silently accepting them. Status reports become more informative, and fewer surprises emerge just before major milestones.

These changes won't eliminate project problems. They will, however, give the project manager a better understanding of what is happening and more time to respond effectively.

Truth Is More Valuable

Every project encounters a variety of problems from scope creep to budget and schedule overruns. The difference between a manageable setback and a major project crisis depends on how quickly the team recognizes the problem and communicates it.

Effective project managers don't measure success by how often they hear that everything is on track. They measure it by how accurately they understand the project's condition, how quickly concerns become visible, and how effectively the team responds.

If your project team isn't telling you the truth, resist the urge to demand greater honesty. Examine the incentives and expectations that influence what people are willing to share. Encourage questions, welcome early warnings, establish clear standards, and hold people accountable for deliberate misrepresentation.

You can't prevent every project problem, but you can create an environment where the truth arrives early enough to make a difference. That's one of the most valuable things a project manager can do for a team and a project.

 Related Articles:

Project Communication That Works

Additional Resources:

Why Your Team Won't Tell You the Truth

Why Your Team Won't Tell You the Truth About Your Communication