Corporate Gaslighting at Work: The Starter Pack Nobody Asked For

Ever leave a workplace meeting and immediately call your best friend just to confirm that you did, in fact, hear what you think you heard?

Welcome to the Corporate Gaslighting Starter Pack.

In this episode of Please Mute Your Trauma, Tiffany Collins takes on workplace gaslighting, broken promises, corporate buzzwords, psychological contracts, organizational justice, workplace trauma, and the strange systems that somehow keep underperformers protected while the person actually improving everything gets labeled “difficult.”

With plenty of humor, Tiffany explores what happens when an organization says it values transparency, innovation, and employee voice—but employees learn that honesty can come with consequences.

We also look at the leadership side of the equation, including a real example from Alan Mulally’s leadership at Ford and what happens when leaders make it safer to tell the truth instead of perform success.

Because sometimes disengagement is not laziness.

Sometimes resistance is memory.

And sometimes cynicism is grief wearing business casual.

If you have ever documented a conversation “just to confirm your understanding,” panicked over a calendar invite titled “Quick Sync,” or wondered why the person holding the entire department together was somehow the one who got cut, this episode is for you.

Work becomes meaningful when dignity is protected.

Transcript

SPEAKER_00 0:00

Have you ever walked out of a meeting and felt this overwhelming need to call your bestie? You know the one, the one that's never worked at your organization. They have never met a single one of your coworkers. But somehow, through the years of detailed storytelling, screenshots, emergency post-meeting phone calls, they know the entire org chart. They know who your boss is, they know who never answers an email, and they know who takes credit for everyone else's work. And they definitely know who Darlene is. At this point, they may not even be your best friend. Instead, they may be an unpaid external consultant with absolutely no confidentiality agreement. So you call them and ask, I need you to help me. Did I misunderstand every word in the English language? Or did they just say the exact opposite of what actually happened? Because in your mind, you're in the meaning. You took notes, you have the email string, and yet, somehow, you're wondering whether you hallucinated the entire fiscal year. If that sounds familiar, congratulations! You may qualify for the corporate gaslighting starter pack. Today we're going to be talking about broken promises, corporate performance theater, and one of the great mysteries of organizational life. Why Darlene is still working there? Well, Marcus, the guy who made everything more efficient, got fired. Hi, I'm really glad you're here. If this is your first episode, welcome. I'm so glad you found us. Pull up a chair, we've been saving you a seat. This is Please Meet Your Trauma, the podcast for anyone who has ever been told to speak up, think differently, and challenge the status quo. But please don't make anyone uncomfortable. I'm Tiffany Collins. I'm a recovering overthinker. I'm often too curious for corporate comfort, and the person who hears, that's not what we meant, and immediately opens the email chain like it's exhibit A. Because if the meeting, the email, and the official explanation are telling three different stories, I'm gonna have lots of questions. So now, the corporate gaslighting starter pack comes with a few essential items: a folder on your desktop labeled documentation, three unfinished emails that begin just to confirm my understanding, a full nervous system response every time the calendar invitation appears titled QuickSync, and the ability to recognize the sentence, this is a great opportunity, as the threat it actually is. There's also a premium edition. Premium members receive an employee engagement survey that is absolutely anonymous. Except for the unique link they sent directly to your individual email address. You get a branded notebook with the organization's values printed on the front, but no pen, because there was no budget for pens. There was, however, a budget for a three-day executive retreat at a luxury resort where senior leadership gathered to discuss why employees need to become more resilient. I'm sure that conversation was exhausting for them. So respect the recover time. And around here, we're gonna talk about workplace trauma, dignity, meaningful work, leadership, and the strange corporate magic that keeps Darlene employed and sends Marcus packing and turns every obvious problem into a communication opportunity. Because organizations are built by humans, run by humans, and somehow act as though no human being could possibly change them. Today we're gonna laugh a lot about covert buzzwords, the vague calendar invitations, the invisible budgets, the high-performing employees who are rewarded for their competence with an exciting new opportunity to perform even more unpaid labor. But beneath the absurdity, there is something real. There are human beings inside these organizations, human beings creating the systems, human beings trying to lead within them, human beings trying to survive them, and human beings who begin questioning their own judgment when what the organization says repeatedly conflicts what they can plainly see. Let's be honest here. This is a podcast that is not anti-HR. It's not even anti-leadership or anti-business. It is profoundly pro-human because no one may have intended the harm, but the harm still lands on a person. And that's what we're going to talk about today. So before I really dive in and say gaslighting approximately 47 times in the next 40 minutes, I want to make one portant distinction. Gaslighting is a serious pattern of psychological manipulation. It is not simply disagreement or one awkward conversation or every bad management decision or someone remembering an event differently. And not every difficult day at work is trauma. When we use words like gaslighting, toxic, and trauma too casually, they lose the precision we need when someone is genuinely experiencing manipulation, betrayal, humiliation, or harm. So today I want to be clear that I'm using corporate gaslighting to describe a repeated organizational pattern. The organization's language conflicts with the reality the employees are living. And when someone names the conflict, the organization reframes the problem as something wrong with the employee. The workload exceeds the available time and resources, but you need better time management. Expectations change without warning, but you're told you struggle with adaptability. You are excluded from the decision, but you need to remain more collaborative. Resources were promised and never arrived. But perhaps you misunderstood. The organization values innovation. You offer your idea, no, not like that. It values transparency. But the official announcement arrives 17 minutes after everyone heard the rumor. It asks you to bring your whole self to work and you bring your one inconvenient emotion. And suddenly someone is sliding the employee assistance brochure across the table. That gap between language and reality is where people begin questioning themselves. They stop asking questions, they delete the email, they may begin sentences with, maybe I'm overthinking this. Or I don't want to make this a big deal. Sometimes the employee has not lost confidence. They have learned that confidence is dangerous. Questions make them difficult. And trusting their own perception might cost them something. And leader, stay with me here. This is not a villain hunt. I'm asking what happens in your organization when someone tells you something you do not want to hear. How do you respond? Do they receive curiosity and support? Or do they slowly become the problem? People learn what is safe to say by watching what happens to the first person who actually tells the truth. The Gaslighting Starter Pack includes a translation guide because the words are technically English, but do not always mean the things you think. For example, we value transparency. Translation. We will share information after the decision is irreversible. The rumor has reached three departments, and the one authorized person is conveniently unavailable. We encourage employees to speak up. Translation. Please speak up about topics we already agree with. Another one. We're like family. Which family? A healthy one? Or the one nobody discusses Thanksgiving and everyone communicates through one exhausted grandparent and someone gets cut out of a will for setting a boundary? I always wonder: do families require PTO for the dentist? Do they put you on a performance improvement plan? I know. Do they eliminate your bedroom through strategic household realignment? Maybe we're not a family. Maybe we're a group project with health insurance. That's okay. An organization can keep its promises, communicate honestly, pay fairly, and let people go home at five without pretending to be their mother. We're a fast-paced environment. Translation. Normalized understaffing until urgency became the culture. Every email is a high priority. Every deadline was discovered only 14 minutes ago. Everyone is sprinting. And no one knows which direction we're actually going. What we need is another person, but what we purchase is another project management platform. Woo! Now the same understaffed people spend six hours entering impossible workloads into a prettier dashboard. This is a great opportunity. For whom? One person leaves, everyone else inherits the work, and there's no title, authority, or pay. Only an opportunity to stretch. Let's be honest. I have stretched an organization so far that I'm no longer an employee. I'm an organizational resistance band. And I have other duties as a sign, which apparently means IT, facilities, therapist, event planner, and the printer whisperer. You know, you fix the printer once, and now you own all technology indefinitely. The phrases are not automatically dishonest. Sometimes work is fast-paced, and sometimes there is truly no budget. The problem begins when supportive language repeatedly disguises itself as an unsupported reality. I know the next budget conversation because, well, I've lived it repeatedly. We know things are busy. We know you need another person. Just hold on until the next budget is approved. The first time, it feels reassuring. I mean, they see it. Relief is coming. There's a light at the end of the tunnel. I can keep pushing because I know this is temporary. People can survive a tremendous amount when they believe strain has an end date. Then what happens is the budget comes, looks at how efficiently you are drowning, and decides you're doing a great job. We cannot make it work this cycle. But next quarter, after the restructuring, as soon as we have greater clarity, and eventually over time, the next budget becomes a mythical creature in Hindwoods. There have allegedly been sightings near the end of a Q4, and no credible evidence has ever been produced. Meanwhile, you're still doing the work. You solve problems before they become visible. You fill gaps so effectively that leadership starts believing, there are no more gaps. What happened? The more heroically an employee compensates for a broken system, the less broken the system appears. Well, everything is getting done, yes. Because one person is holding the department together with caffeine, calendar reminders, and rapidly deteriorating thread of their last nerve. A system not collapsing does not mean it's healthy. Sometimes a human being has positioned their body underneath it. The organization says, oh, you're such a rock star. We do not know what we did without you. Those segments often sound like recognition or a plus. Sometimes, let's be honest, these are resource allocation strategies. If I call you exceptional, perhaps I do not have to stop asking you to perform at an unsustainable level. And leaders, we know budgets and constraints are real. And sometimes the answer is generally no. But an honest no is more humane than a hopeful maybe repeated for 18 months. If the resource isn't coming, say it. Please. If the organization chose another priority, on the choice. Do not use possibility to extract another year of unsustainable performance. Eventually, we know you need help, stops feeling like empathy, and it starts feeling like evidence. There is a concept in organizational research called the psychological contract. It is not your written employment contract, it is the unwritten agreement employees believe exists between themselves and the organization. For example, I work hard and my contribution will be recognized. I am honest with you and you'll be honest with me. I show loyalty and that loyalty will mean something. I accept short-term strain because you told me support is coming. Those expectations do not have to appear in writing to shape a relationship. When they feel repeatedly violated, people do not only feel disappointed, they can feel betrayed. Because the loss is not merely the additional employee who never arrived. The loss is trust. The loss is the belief that words can carry meaning. Shocking. The loss is the assumption that effort and outcome are connected. Eventually, employees change. They may still show up, they may still smile and complete their work, but they stop believing. Sometimes the employee's body remains at the desk long after the trust has left the building. Every organization has a Darlene. And before anyone emails me, Darlene is fictional. So if your name is Darlene and you're innovative, emotionally intelligent, excellent with PDFs, congrats. This is not you. Unless you print the email and bring it to my office. Then we need the duck. Our Darlene has worked here at this organization for 27 years. She survived six CEOs, four restructurings, two mergers, a software migration, an office flood. Yes, that did happen. And an executive who promised to disrupt the status quo. He was gone in 18 months, but Darlene is still there. She prints emails. She highlights them and responds electronically. She has instructions for a system retired in 2009. And my favorite, she refers to PDFs as that Adobe thing. When someone suggests a new process, Darlene says, that's not how we've always done it. And everyone immediately abandons hope. But Darlene also knows things. She knows why the policy exists, where the original document is, which executive tried it in 2011, and again in 2015, and who has the actual authority versus who simply uses the largest font emails. Susan may be extraordinarily adapted to her organization. She knows which initiatives are real and which leaders will leave. She knows that if she waits long enough, everyone may, fingers crossed, return to her 2004 spreadsheet. Susan may have been a Marcus once. Maybe she had ideas. Maybe she questioned the 17 signature process. And maybe leadership one time said stay in your lane. Often enough that she learned new ideas create more work. Speaking up creates attention, attention creates risk. That does not excuse every performance problem. Dignity does not mean an absence of accountability. If everyone privately complains about Darlane, but every performance review says meets expectations, the organization is participating in the fiction. The organization has avoided one uncomfortable conversation with 14 review cycles. The prize is resentment across the department. And then there's Marcus. Marcus has been at the organization for three years. She notices a weekly report requires four employees, two spreadsheets, a shared drive, a manual for reconciliation, and one person whose only job appears to be changing the font before leadership sees it. Why does this take six hours? It just does. Couldn't we automate it? Darlene says, we tried that. Nobody remembers when, or how, or why it failed. But organizational folklore declared automation impossible. So Marcus built a prototype. The six-hour process now takes 23 minutes and 47 seconds. Leadership applauds. This is exactly the innovation we want. So Marcus automates three more processes. And then seven, and then twelve. He trains the team, he writes instructions, saves hundreds of hours, reduces errors, creates a dashboard, and becomes the person everyone calls when something breaks. Marcus does not even say circle back. Marcus returns with the answer. Then comes his review. Your technical performance is excellent. Any sentence, let's be honest, beginning with excellent performance, should end there. But we all know it never does. But we would like you to be more strategic. Apparently, strategy is not improving the organization. Strategy is saying cross-functional alignment while pointing at three arrows. Maybe Marcus needs executive presence. Sometimes that's legitimate. And sometimes it means your results are excellent, but your competence makes everyone uncomfortable. We cannot write that on this form. Marcus asks direct questions. He makes work visible, and when you make work visible, you also make inefficiency visible. Some organizations want innovation as long as it does not inconvenience the existing power structure. Then Marcus receives a calendar invitation titled Organizational Update. Those are my favorite. Normally you have an HR person who's on the call wearing that careful expression. If someone asks to deliver the sentence or the news, they never want to turn to Marcus's position has been eliminated. The business is moving in a different direction. What direction? Back towards the fax machine. His work will be redistributed. So the work exists, the petition does not. Important distinction, apparently. For 48 hours, everything seems fine. Then the dashboard stops refreshing. No one has the credentials. The report runs, but no one understands it. Did Marcus document this? Yes, it isn't a shared drive. What do you mean you can't find the shared drive? Because Marcus created the folder structure. Can we call him? No. Marcus has boundaries now. Leadership holds an emergency meeting about operational resilience, which is apparently what we call firing the person who knew how the operation worked. Employees are asked to remain flexible and view as an opportunity to cross-train. Darlene quietly sneaks over retrieves her 2009 finder. And somewhere in the interwebs, Marcus receives a LinkedIn endorsement from Microsoft Excel. Justice for Marcus! Before we start a GoFundMe for Marcus and nominate Darlene for an employee of the century, let's slow down. Because this is where organizations get extremely complicated. Darlene is not automatically the villain, and Marcus is not automatically perfect, even though it might feel like it. And there may be information the rest of the office does not have. Maybe Marcus's role really did have to be eliminated. Maybe the organization needed different skills. Maybe there were concerns that could not be shared. And all of that is possible. Confidentially, confidentiality matters. Hard business decisions are not automatically unethical just because they hurt someone. And here's the part leaders sometimes miss. Everyone who remains is still trying to make sense of what they just watched. They do not have access to the executive meeting, the legal advice, the budget model, or the 17-tab spreadsheet from Doug and Finance, who keeps guarding it like a nuclear code. They have the pattern. They saw Marcus improve the work. They saw Darlene remain largely untouched. They heard leadership say performance matters. And then they watched an outcome that did not seem connected to performance. So now they're asking questions. Not out loud, obviously. Out loud, they're saying, wow, that is really unfortunate. In the group chat, they're asking, if Marcus was not safe, what exactly are the rest of us doing here? Because when Marcus leaves, the team does not only lose Marcus, they learn something. They learn that being useful and being safe may be two completely different employee benefits. They learn that improving the system does not necessarily mean the system will protect you. They learn we value innovation. May have terms and conditions nobody bothered to attach. Culture is not the sentence painted above the reception desk. Culture is the answer employees develop to questions like what happens around here when someone tells the truth? What happens when someone makes a mistake? Because that's gonna happen. What happens here when a high performer becomes inconvenient? And let's be honest, what happens when doing the right thing costs the organization money? If employees bring ideas and every idea creates more unpaid work, I mean, logically, they're gonna stop bringing ideas. If they ask questions and the questions are reframed as negativity, shocking, they're gonna stop asking questions. If they take initiative and initiative is rewarded with three additional jobs and a thank you emoji, I mean they're gonna adjust. Then my favorite is when leadership looks around six months later and says, What? Are people just do not engaged anymore? They were engaged, you just trained it out of them. Sometimes what leaders call resistance is memory. Sometimes what leaders call disengagement is self-protection. And sometimes cynicism is grieved for business casual and carrying a reasonable water bottle with the company logo. We laugh at this because it is recognizable. The quick sync, the anonymous survey that knows exactly who you are, the magical next budget, the employee who receives more work as a reward for doing the first work well. The consultant who presents your own idea back to you in a nicer font. The humor gives us enough breathing room to talk about what's underneath it. Because work is not only where people earn money. And for someone who has experienced trauma before, certain workplace patterns can feel painfully familiar. Unpredictability, anyone? Powerlessness, being told their perception is wrong, monitoring someone else's mood because that mood determines whether the day is safe. Trying to become indispensable because being needed once felt like a protection. Staying silent because, let's be honest, speaking honestly, only made things worse. And no, not even a stressful day is trauma. Sometimes Tuesday is just terrible. And sometimes there are weird, wacky Wednesdays. But organizations can intensify trauma. They can reactivate old survival patterns, right? They can create chronic fear or instability, betrayal, or humiliation. And the body pays attention to patterns, not necessarily mission statements. Your nervous system doesn't read integrity in vinyl lettering above the copier and say, oh, thank God, I was worried until I saw that wall decal. It remembers that the last three quick chats ended badly. It remembers that expectations changed without warning. It remembers the last person who raised a concern suddenly became not aligned. So a calendar invitation arrives and your chest tightens. You replay the last week. Did I miss something? Did someone complain about me? Am I getting fired? You screenshot the invitation as a quick chat contains forensic evidence. You joined the call and discovered they wanted your opinion on the holiday party. Wonderful! Yet my body prepared for unemployment. And you wanted to know whether I preferred cater tacos or pasta. That is why the email begins, just to confirm my understanding, is not always pass or aggressive. Sometimes it's just a person trying to rebuild reality in writing. They're creating an external memory because they no longer trust that today's conversation will remain tomorrow's truth. A trauma-informed perspective does not only ask, what is wrong with this employee? As we've discussed, it also asks what happened here. What pattern did this person learn? What is this environment reinforcing? And what would make honesty, voice, choice, and dignity safer again? That does not eliminate accountability. Trauma does not mean consequence-free. That would be nice. It does not mean managers become therapists, they're not trained in the same thing, and definitely does not mean mandatory office yoga while the worklard remains impossible. Please stop giving people breathing exercises when what they really need is adequate staffing. Breathing is wonderful. I do it often. So is another employee. Confidentiality should not become a smoke bomb. You may not be able to tell employees everything, but you can still say, I understand why this looks inconsistent. We should have communicated sooner. This is going to affect the team. And my favorite, we made a mistake. Those statements matter, but they have to be followed by action. After a while, an apology without change is not repair. Now, before we decide that every letter communicates exclusively through vague PowerPoint slides and the phrase moving forward, I actually want to tell you a real story. And I promise this is not the part of the podcast where I suddenly become a graduate seminar speaker. There's no quiz. So in 2006, Alan Malale became CEO to Ford. Ford was not having what we would professionally describe as a good year or season. The company was forecasting a $17 billion loss. Billion. But some B. That feels like the kind of number where somebody should probably say, hey, quick heads up, things are not ideal. Malali started at weekly meetings where a leader showed the condition of the business using color-coded charts. Green meant things were on track. Yellow meant there was a concern. Red, as we can think, meant there was a problem and help was needed. Simple. Except every chart was green. Hundreds and hundreds of charts, all green. The company was preparing to lose 17 billion dollars. And somehow every slide people presented basically said, crashing it. That is not a dashboard. That is denial with conditional formatting. Lilali kept asking where the problems were. And everyone in the room suddenly became fascinated by their notebooks. Because the leaders had learned over time that bringing a problem upward was dangerous unless they had already solved it. Which sounds responsible until you realize it means the biggest problems are the ones most likely to remain hidden. Eventually, Mark Fields, who led Ford's North American operations, had a production issue affecting the Ford edge. So he decided to mark the chart red. Someone has team essentially said, Well, it's been nice knowing you. Do you have your resume updated? Because red did not mean we found something important. Red men, please update your LinkedIn before lunch. So Fields put the red chart on the screen, and the room waits. And this is the moment. What is the new CEO of Ford going to do with the first person who admits something is wrong? Mulilly started clapping. Not because the production problem was good, and not because losing money is a fun team-building exercise. He clapped because reality had finally entered the meeting. And then he asked, How can we help? And suddenly people started offering engineering support, manufacturing help, technical experience, and resources. The problem moved toward a solution. And over the next few meetings, the charts changed. Here were greens, there were yellows, there were reds, and a whole corporate rainbow. Not because Ford suddenly developed more problems, but the problems were already there. The organization developed more honesty. And this is the part that I always kind of come back to in my mind. The chart did not change the culture or the organization. The leader's response to the first red chart changed the culture. Malilly didn't say, Mark, I'm concerned about the energy you're bringing into this space. He did not ask whether Mark had considered being more solutions-oriented. He did not send him a resilience podcast and a schedule that said follow up in 30 days. He treated the truth as useful. He made it safer to reveal reality than to reform in success. And leaders, please listen to me. This is where I want you to think about your own organization. How do you respond when someone brings you a red chart? What happens in your face before you say a word? What happens in your tone or your questions? Your next calendar invitation? Do you become an explorer or become curious? Or does an employee leave thinking, crap, I will never do that again? Corporate gaslighting says, the problem is your perception. Good leadership says, thank you for showing me reality. What do we do next? Willelly's line was simple. You can't manage a secret. And honestly, you cannot fix a problem everyone is professionally committed to pretending does not exist. So here's the question I think every leader should ask. What happens to the first red chart? Not the tenth one. Not after the organization launches a speak up campaign with matching email signatures. The first person who says, this is not working. Are we going to make the meeting deadline? The workload is unsafe. The team does not trust this decision. What happens to that one individual? Are they thanked? Are they met with curiosity or wanting to tap into their expertise to learn more? Or do they become negative, difficult, not strategic? And my personal favorite, not a team player because there's no I in team. Because the first response teaches the entire organization. If the first red chart gets punished, the next 299 will be green. Not because everything is fine, but because everyone learned what color survival requires. The question is not whether employees are interpreting your decisions. They are. The question is whether they trust you enough to bring that interpretation back into the room. Because when people stop telling leadership the truth, leadership doesn't have fewer problems. It has fewer visible problems. And we all know that that's not the same thing. This is where we return to the humans. Darling may be surviving a system that trained the initiative either. And Marcus may be exhausted from being rewarded with more work every time he proves he can handle more work. Understanding those realities does not erase accountability. Intent and impact can exist at the same time. A leader can be under pressure, but yet still hold power. A decision can make financial sense and still be handled completely wrong. Compassion without accountability makes excuse making. Accountability without compassion becomes punishment. And we need both. We all know we need both. The deeper question is not simply who is the problem. It is systems produce characters. Reward silence and you create silent employees. Reward heroics and you create burnout. Avoid every uncomfortable performance conversation and you create resentment. Punish the first red chart, and we all know the rest will be green. Again, not because everything is fine, but because we're quick learners and we learn the script. Before I close, I have five things. And I promise none of them require a workbook. Number one, I hope you watch the pattern, not the slogan. One delayed promise may be understandable. One poorly handled decision can be a mistake. But repetition matters. Who gets the resources? Whose mistakes become learning opportunities? Who gets told to be more resilient? What happens to the first person who brings bad news? A value is not what's printed on a wall. A value is what the organization protects when protecting becomes inconvenient. Number two, leaders pay attention to your first response. An open door policy means very little if people regret walking through it. Before defending, ask, what are you seeing? What information am I missing? What impact is this having? What support would help? You do not have to agree with every interpretation, but reality has to be safer than performance theater. Number three, stop confusing heroics with health. If one employee works nights, fixes every emergency, covers multiple roles, and prevents the department from collapsing, the employee may be extraordinary. The system is not. Do not look at someone surviving an impossible workload and decide the workload must be reasonable. Do not reward competence with endless additional labor and label it development. Being needed is not the same as being supported, and being indispensable is not the same as job security. Sometimes it just means nobody knows the password. Number four, ask fairness questions. Was the outcome fair? Was the process fair? Was a person treated with dignity? Was the explanation honest enough to make sense? A painful outcome can still be handled fairly. A reasonable decision can still detract trust when the process is secretive, inconsistent, or humiliating. And confidential should not mean we will now communicate exclusively through smoke signals. And the last one, number five, rebuild trust in reality. Employees separate facts from interpretation. What was said, what changed, what pattern are you noticing? Talk to someone grounded, not the coworker who responds to every inconvenience with you need to quit immediately. We do love that person. But they probably are just not the best strategic advisor. Self-trust is not certainty, it's the ability to examine reality without automatically abandoning your own perspective. And leaders, I want to encourage you to tell people what you can. Name the constraint, acknowledge the impact, and when you get it wrong, do not say we're sorry you felt that way. Please don't say that. Say we did not communicate this well. We failed to follow through. We understand where your trust was damaged. Then explain what changes next time. Repair is never weakness. So this week's corporate red flag is we reward innovation, followed immediately by punishing the person who reveals that the existing system does not make sense. Innovation that is only welcome when it confirms what leadership already believes is not innovation. It's a decoration. And this week's green flag, a leader who can hear this process is not working without translating it into or saying I'm a bad person. A leader who sees the first red chart and says, Thank you for telling me. What do we need to understand? And how can we help? That's not weakness. Let's be honest, that's leadership. So why does Darlene still work there while Marcus got fired? Sometimes there's a reasonable answer. Sometimes there's information we're just not privy to. Sometimes Darlene carries more value than anyone might recognize. And sometimes Marcus's contribution was real, but the organization needs changed. And sometimes the answer is less flattering. Sometimes organizations protect familiarity over performance. Sometimes they avoid accountability because discomfort feels more threatening than inefficiency. Sometimes the person improving the system accidentally exposes everyone who benefited from the system, remaining confusing. Let's be honest, the problem isn't not that Darlene has a job. Darlene deserves dignity. The problem is when standards cannot be explained consistently. The problem is when Marcus' experience teaches everyone that contribution offers no protection. The problem is when employees are told not to believe what they can plainly see. So, yes, justice for Marcus. But also at the same time, development for Darlene, courage for the manager, honesty for the leadership, support for HR, better information for finance, and dignity for every human affected by the system. Because organizations become humane when they remember every decision lands somewhere on a person, a family, a body, a nervous system, on someone's belief about whether their work mattered. I want to say thank you today for pulling up a chair with me. If this episode made you laugh or think, or immediately text your work bestie, Darlene is still here. Please share it. And one final question: What is the red chart in your organization that everyone is afraid to show? I want to encourage you to share your story at pleasemeetyourtrauma.com or call 188-629-5081. It may help an employee realize they're not imagining what happened. It may help a leader recognize a pattern, they still have time to change. And I have a feeling this is not the last time we're gonna hear about Darlene. So until next time, remember work becomes meaningful when dignity is protected. And that means protecting your own. See you guys next week.