It is Tuesday morning, 9:14 AM. Daniel, an engineering manager, opens Slack and sees the same project deadline written three different ways across three threads. One says May 12. One says May 19. One says “end of May, Patrick confirmed.” Patrick is on PTO.
The actual deadline, in the project doc Daniel wrote himself, is May 14.
By 11 AM, two engineers have shifted their sprint plans based on the wrong dates. By Thursday, a designer in another team has rescheduled a review. By the time Daniel catches it, six people are working off three different versions of the truth, and the real deadline is 16 days away.
This is workplace misinformation. Not a dramatic conspiracy. Just everyday distortion that compounds quietly until something breaks.
What workplace misinformation actually is
Workplace misinformation is any false or distorted claim about facts that affect work, deadlines, decisions, headcount, comp, project status, that gets treated as true and spreads through the team. It is not the same as a difference of opinion. Opinions are about interpretation. Misinformation is about facts that can be checked against a primary source and found wrong.
It spreads the way most workplace information spreads. Through gossip in 1:1s, sloppy paraphrases in Slack, inherited assumptions in status updates, and the occasional fake report that nobody pressure-tested. A 2022 Pew Research survey of 19 countries found misinformation ranked as the second most serious global concern. Edelman’s 2024 Trust Barometer shows employers remain one of the few institutions people still trust, which means the cost of a manager being a sloppy source is unusually high.
There is a psychological reason this is sticky. The misinformation effect, identified by Loftus and Palmer (1974), shows that how a question is worded can plant false memories of what someone saw. In teams, the same thing happens with phrasing in status updates and Slack messages. The wording becomes the memory.
Here is the playbook.
Step 1: Detect
Detection is the practice of noticing patterns across separate conversations that suggest a shared false belief is forming.
Most managers do not catch misinformation when it starts. They catch it three or four conversations in, when the pattern is already costing time. The signals are usually quiet:
- Confused 1:1s. Two reports in two days ask you the same oddly specific question, like “is the launch really pulled to next quarter?” That is a leak point. Someone told them something you did not say.
- Contradictory status updates. The same project shows two different states in two different Slack channels. Not a difference in detail, a difference in fact.
- Stories not adding up across teams. A peer manager mentions a decision you do not remember making. Trace it.
- The “I heard” opener. Multiple people on your team start a sentence with “I heard that” or “apparently.” That phrase travels with rumors.
- Decisions getting pre-litigated. Reports start objecting to a decision that has not been made yet. Someone told them it was already decided.
Daniel’s signal was three different deadlines in three threads. The pattern was the tell. Once you train yourself to notice the pattern, not the individual claim, you will catch most things in the first 24 hours.
Step 2: Trace
Tracing is finding whose pen the false claim originally came from, separately from who repeated it.
This is the step managers most often skip, because it feels like a witch hunt. It does not have to be. The point is not to punish, it is to understand whether you are dealing with a one-off mistake, a systemic information gap, or someone shaping a narrative.
Trace through three quiet questions in 1:1s:
- “Where did you first hear that?” Asked neutrally, not accusingly.
- “When you say Patrick confirmed it, did he say it to you, or did someone tell you he said it?” The chain shortens fast.
- “Is there a doc or message I can look at?” If there is no source, you have your answer.
Most of the time, you will find the chain ends with one person who paraphrased a real conversation badly. That is a coaching moment, not a discipline moment. Sometimes you will find the chain ends with someone repeatedly originating false claims. That is a different conversation. It usually points to a deeper issue: they feel out of the loop, they want influence, or they are testing whether bad behavior gets caught.
A useful frame: separate the originator from the amplifiers. Amplifiers passed along what they heard. The originator made it up or distorted it. Your response should be different for each.
Decision callout: misinformation vs. difference of opinion
Before you correct anything, check which one you are dealing with.
- Misinformation: “The launch is delayed to Q3.” Checkable against a doc. Either true or false.
- Difference of opinion: “I think the launch should be delayed to Q3.” Not a fact, a position. Treat it with debate, not correction.
If you correct an opinion as if it were a false fact, you will look defensive and you will train your team to stop sharing opinions. Always run this check before you act.
Step 3: Correct
Correction is the public restoration of a shared fact, done in a way that fixes the record without humiliating the source.
Three rules.
Correct in the same channel where it spread. If the wrong deadline went out in #eng-product, the correction goes in #eng-product. Skip the separate DM; skip the all-hands. Same room, same audience.
Lead with the fact, not the blame. Daniel’s correction should read something like: “Quick note, the real deadline for the launch is May 14, not May 12 or May 19. Source is the project doc, link below. If you replanned based on a different date, let’s regroup in standup tomorrow.” That is it. No “someone said,” no “I heard a rumor.”
Address the source separately, in private. After the public correction, message the originator 1:1. “Hey, I noticed the May 19 date came from your thread, can you walk me through where that came from?” Calm, curious, low stakes. If it was a paraphrase mistake, they will tell you. If they get defensive, you have learned something.
The mistake managers make is doing this in reverse. They confront the originator in public to look decisive, and they let the wrong fact sit uncorrected in the channel for two more days. That order kills trust twice.
If you find yourself rehearsing the correction in your head and getting tangled in tone, that is a signal to slow down and practice it out loud. Risely’s Merlin can run rehearsal conversations on exactly this kind of script. You write the situation, Merlin role-plays the team, and you get a feel for how the words land before you post them. The point is not to memorize a line, it is to stop sounding either flat or accusatory.
Step 4: Prevent recurrence
Prevention is the design of team norms and shared truth artifacts that make false claims either fail fast or never start.
You cannot stop misinformation by telling people to “communicate better.” You stop it by making the truth easier to find than the rumor.
Four things that work:
- One source of truth per project. A single doc or board where the deadline, owner, and status live. If someone asks you a status question, your answer is “let me link the doc,” not a paraphrase. Paraphrases are how distortion enters.
- A decision log. A running list of decisions made, with date and who decided. When someone says “I thought we decided X,” you can both look. This kills the most common kind of workplace misinformation, the false memory of a meeting.
- A 1:1 question every week. Add a standing prompt: “Heard anything about the team or project you are not sure is true?” Ask it for four weeks straight. People will start surfacing rumors before they spread.
- A norm against “I heard.” Tell the team explicitly: when you share something about the team, say where it came from. “Patrick told me in our 1:1” is fine. “I heard somewhere” is not. This single norm cuts amplification in half.
These are not heavy. They are five-minute artifacts. The reason most teams do not have them is that no one was the manager who decided to set them up.
Closing CTA
Most workplace misinformation does not get caught by policy. It gets caught by a manager who notices the pattern, traces it without panic, corrects it without humiliating anyone, and quietly upgrades the team’s information habits. Those four moves are skills, and like any communication skill, they get sharper with practice and feedback.
If you want to rehearse a correction conversation before you have to send it, or pressure-test how you would handle the originator in 1:1, try Merlin free. Risely has coached over 3,000 managers across 40+ organizations through exactly these conversations, with an average 26% skill improvement in 12 weeks. You can also start with a quick read on where you stand on oral communication or integrity.
FAQs
What counts as workplace misinformation?
Workplace misinformation is any false or distorted claim about facts that affect work, like deadlines, decisions, headcount, or pay, that spreads through the team and gets treated as true. It is different from a difference of opinion. Opinions are about interpretation; misinformation is about facts that can be checked against a primary source.
How is misinformation different from disinformation?
Misinformation is wrong by accident. Someone heard a half-truth and passed it on. Disinformation is wrong on purpose. Someone shaped a false claim to push an outcome. Most workplace incidents are misinformation, but managers should still trace the source, because the response differs.
Should I name the person who started the rumor in a public correction?
No. The goal of the correction is to fix the team’s shared understanding, not to assign blame in front of others. Correct the claim publicly, address the source privately. Naming people in front of the room creates fear and pushes future rumors underground, which is harder to manage.
What if the misinformation is about me as the manager?
Treat it the same way. Detect the signal, trace the source, correct in the same channel where it spread, and address it directly. Defending yourself in a panicked all-hands makes it worse. A short, factual message in the relevant Slack thread, followed by a 1:1 with whoever started it, usually closes the loop.