On Being Vague In Professional Communication
I used to think "prevaricating" was a word only your grandmother used. Then I worked in a few organizations where people prevaricated so much it became the primary mode of communication. It is not something I recommend, but I also learned exactly how it works, why people do it, and the specific ways it gets them fired. Prevaricating means equivocation, hedging, or deliberately speaking in a way that obscures the truth. In practice it looks like saying "we are exploring options" when the decision was already made. It looks like "let me circle back" when you have no intention of following up. It looks like "there may be some delays on our end" when the project is already behind schedule and nobody wants to say it. People do this for reasons that are usually understandable but rarely justifiable. Fear of bad news. Bureaucratic pressure to look productive. A management culture that punishes honest bad updates more harshly than honest good ones. The person who brings bad news often gets painted as the problem. So the team learns to communicate in a way that sounds professional while actually communicating nothing.
Here is what happens next: the organization builds a communication system where facts are systematically filtered out before they reach decision-makers. A project manager reports 90% completion because the last 10% involves actual deployment and they do not want to discuss the risk. Stakeholders see "90%" and allocate budget assuming launch is imminent. Three months later everyone is surprised. The surprise is manufactured.
The Mechanics Of Workplace Prevarication
Prevarication operates on several frequency bands. The low-frequency version is structural vagueness. Status reports become templates filled with safe language. "Moving forward with next steps" appears in twelve slides and tells you nothing about what those steps actually are. This is the most common form because it requires zero effort to produce and zero accountability to maintain. The high-frequency version is outright evasion. A stakeholder asks "will the API migrate by Friday?" and the answer is "we are targeting Friday pending dependencies." This is not a target. It is a deferral. A target implies commitment. A deferral implies the speaker is buying time without having a plan for what happens after the time is bought. I encountered this problem firsthand when leading a platform migration. The engineering lead's status updates used language like "the team is aligned on the approach" and "we are in a strong position." In reality the approach had three unresolved conflicts, the team was divided, and the timeline was already unrealistic. I stopped asking for narrative updates and switched to a question-based format. Every status meeting became a set of specific questions with binary answers. "Is the database schema finalized?" Yes or no. "Can we ship to staging by Wednesday?" Yes or no. "What is blocking the No answer?" Name the blocker.
Get the Full Details
This broke the prevarication cycle almost immediately. People adapt to measurement formats. When you cannot hide behind "strong position," you either give a Yes or you name the actual obstacle. The first round of those meetings was uncomfortable. The second round produced actual data. By the third round the team had stopped trying to perform alignment and started actually solving the blockers. That is the point where status reporting becomes useful instead of decorative.
Why Prevarication Gets People Fired
The people who prevaricate believe they are being strategic. They think they are protecting themselves, their team, or the organization from unnecessary alarm. This is a calculation error. Prevarication is detectable by anyone who has read a single incident report or audited a failed project post-mortem. The pattern is recognizable. When a project fails after a trail of vague status updates, the investigation does not stop at "the project failed." It traces backward through the communication record. People who wrote "we are exploring options" when the option was already rejected get flagged. People who reported "on track" when they knew it was not on track get flagged harder. Prevarication during a crisis is treated differently than prevarication during normal operations. During normal operations it is mildly annoying. During a crisis it is negligence. I watched this happen in a compliance audit where a senior engineer had been writing status reports that said "all remediations are in progress" for six weeks. They were not in progress. They were blocked by a procurement issue that nobody had escalated. When the auditor asked for evidence of progress, there was none. The "in progress" language was prevarication dressed as professional optimism. That engineer was let go within two weeks of the audit findings being delivered.
Common Pitfalls People Miss
Beginners in workplace communication often think prevarication is about lying. It is not. It is about the gap between what you say and what is true. The gap can be one word. "We are close to done" when the work is forty percent complete is a bigger lie than "the work is not complete" presented without any qualifier. People miss this because they focus on the intent. The intent may be harmless. The gap is what gets measured. Another pitfall is assuming that prevarication protects you from difficult conversations. It does not. It delays the difficult conversation and makes it worse when it eventually happens. A stakeholder who hears "we are assessing the impact" on Monday and then learns on Thursday that the impact is catastrophic will be far less forgiving than a stakeholder who heard on Monday "the impact is approximately X and we have Y mitigation" even if X was bad news. The timing matters. The specificity matters more. There is also a category of prevarication that comes from genuine uncertainty. Sometimes people do not know the answer and they communicate in a way that hides that ignorance. "We will need to assess" when they have not actually started assessing is different from "I do not know yet but I will find out by end of day." The first is prevarication. The second is a commitment to a knowledge timeline. The second is still information, just incomplete information. Organizations should treat these two responses very differently, and most fail to do that.
What Actually Works
The workaround is structural, not behavioral. You cannot prevaricate your way out of a culture that rewards vague communication. You have to change the feedback loop. Specific metrics kill prevarication faster than any personal integrity initiative. When your team is measured on shipping features instead of writing status reports, the status reports start telling the truth because the truth is the only thing that survives scrutiny. I also recommend what I call the "single sentence rule." If you cannot summarize the current state of a project in one unambiguous sentence, you are either prevaricating yourself or someone else is prevaricating with you. The sentence should contain a fact, a number, and a date. "The API is 73% migrated as of Tuesday and the remaining work will block deployment until Thursday." That sentence can be verified. It can be wrong. It can be updated. It cannot be misinterpreted as optimism. Some tools and frameworks make this harder. Agile ceremonies, for instance, often encourage teams to report velocities and burndown charts that look clean because the data is self-selected. A velocity that excludes blocked work is not a metric. It is a fiction. The same applies to Kanban boards that show everything "in progress" without time limits. WIP limits are not productivity advice. They are prevarication detectors. If a card sits in "in progress" for three weeks it is not in progress. It is stuck. Calling it stuck is the only useful communication.
There are places where prevarication is structurally required. Client-facing communication often involves withholding competitive information or managing expectations around timelines that are legitimately uncertain. In those cases the correct approach is not to prevaricate. It is to say "I cannot share the exact timeline but here is what I can tell you: the work is in the QA phase and the earliest realistic deployment window is next week." That is boundary-setting, not evasion. The difference is whether you provide useful information within the boundaries you draw.
The Bottom Line
Prevarication is not a personality flaw. It is a systemic behavior that emerges from incentives. When your organization rewards good news and punishes bad news, prevarication is the rational response. The rational response will get you fired when the project fails, which it will, because the failure was predictable from the communication record if anyone had bothered to read it honestly.
