Hello friends, in the last episode we built the Field Guide, the Credit Thief, the Knowledge Gatekeeper, the Ceiling Setter, the Darvo Operator, the Contagion. We named all of them. And if you listened, I am willing to bet that at least one of those landed a little close to home. Maybe more than one.
But I left you with a question at the end of that episode, and it is the question I want to answer today. Because how does a person like that survive? How do they thrive? How does an entire organization look at the other way while the damage accumulates?
How do talented, well-intentioned people end up working inside systems that seem almost perfectly designed to reward the wrong behavior and sideline the right people? Today, we stop looking at the individuals and we look at the building they are living in. Because here is the uncomfortable truth that most leadership books and management courses will never tell you. In the vast majority of cases, the derailer did not create the environment.
The environment created the derailer. And until we're honest about that, really honest, nothing fundamentally changes. You can replace the person as many times as you like. If you do not change the conditions, you change nothing.
Welcome back to the Career Pivot Accelerator. I'm your host Peggy McKnight, and this is episode two of our series, Beware of the person who defines your future skills for you. If you have not listened to episode one yet, I would encourage you to go back and start there. Because what we build today sits directly on top of what we named last time.
But if you're joining us fresh, welcome. Happy to have you here. You are in exactly the right place. Today we talk about the organization.
And I promise you, by the end of this episode, you are going to recognize something you have been living in so clearly that you will never be able to unsee it again. That might feel uncomfortable for a moment, but clarity is always more useful than confusion. Even when the clarity is hard, let's go. Now, some of you listening will have done the training for project management.
You know the ones, Prince II, PMP, Agile, Scrum. These are all very familiar terms to you if you have done project management training. You have sat through the stakeholder engagement modules. You have built the RACI matrix, which, for most of us who don't understand a RACI matrix, it stands for responsible, accountable, consulted, and informed.
You have written the communication plan and the risk register and the project charter. And those frameworks are genuinely valuable. And I'm not here to dismiss them. But I want to talk about asking you something.
When did you receive training on people? Did anyone teach you what to do when the knowledge gatekeeper, for example, ignores the communication plan? Did anyone show you how to handle a Darville operator who has rewritten the narrative before the retrospective even begins? Did anyone give you a framework for what happens when the person who has been there the longest decides the new system is a personal attack on their professional identity?
Almost certainly not. Because here is the gap that sits at the heart of every project management certification ever created. They teach you the architecture of collaboration, the structure, the process, the methodology, the moving pieces in the form of job titles. But they do not teach you what almost nobody teaches you is the human behavior inside the architecture.
Print 2 assumes good faith. It assumes that once roles are defined, people will honor them. PMP addresses conflict at a surface level. It tells you that conflict exists and should be managed.
It does not give you the language to identify preemptive blame at shifting in real time or recognize a competence audit disguised as a request for help. Project management frameworks teach you who should be at the table. They do not teach you what to do when the person at the table is playing games with everyone in the room. And nowhere in this gap more visible than in large-scale technology implementations.
Systems that should take 18 months, that's 1-8, instead of taking 8-plus years and maybe never getting off the ground. Multiple project leaders cycling through the same role. Change champions sitting outside the rooms where decisions about their own work are being made without them. Visual roadmaps that look like progress and function like decoration.
The frameworks did not fail. The human conditions inside them did. And that is what we are examining today. Carl Jung, who is arguably one of the most influential psychologists of the 20th century, developed the concept of the shadow self.
The idea that every individual carries not just the qualities they show to the world, but a hidden collection of impulses, beliefs and behaviors they do not acknowledge, even to themselves. The shadow is not evil. It is simply unexamined. And what is unexamined cannot be changed.
Organizational researchers have applied this same concept to institutions. And the organizational shadow is one of the most useful frames I know for understanding why workplace behaves the way it does. Every organization has two lists. The first list is the official one.
You know what I mean? The values on the wall. The language in the annual report. The words used in every town hall and onboarding session.
Collaboration, integrity, innovation, people first. The second list is the real one. The behaviors that are actually modeled. They are actually tolerated, actually rewarded when the spotlight is off and the performance review is being written.
And here is the thing about those two lists. In a healthy organization, they overlap significantly. In a dysfunctional one, the gap between them is where everything we talked about in episode one lives and breathes. The credit thief thrives in an organization whose official list says teamwork, but whose real list rewards individual heroics.
The Darvo operator flourishes, where the official list says accountability, but the real list has never once held the right people accountable. The contagion spreads fastest in organizations whose official list says inclusion, but whose real list has modeled exclusion and gatekeeping for so long that new people absorb it as normal before anyone has a chance to show them something different. The question to ask about any organization is not what does it say it values. It is what behavior has to allow to become normal because normal is the real values list.
And here is the hardest part of this conversation. The shadow is not maintained by the derailers alone. It is maintained by everyone who sees the gap between the two lists and says nothing, not because they're bad people, but because the organization has taught them through experience, through watching what happens to people who do speak up, through the slow accumulation of moments where the wrong behavior went unaddressed, that silence is the safest choice. Psychologists call this psychological safety, or more precisely, it's absence.
Harvard professor Amy Edmondson has spent decades researching what happens in teams and organizations where people do not feel safe to speak up. Her findings are consistent and very sobering. In low psychological safety environments, the official values become theater. The real values, whatever behavior is actually tolerated, becomes the operating system.
The people with the most to contribute are often the first to go quiet. Now that we've identified the psychological terms in organizations, let's dive deeper and get specific about how to identify this in your organization. The organizational shadow does not just appear, it is built, conditioned by condition, decision by decision, tolerance by tolerance. Here are the nine conditions I see most consistently in organizations where derailers not only survive, but they thrive.
Condition one, rewarding heroics over teamwork. When organizations celebrate the person who swoops in and saves the day rather than the team that built a system where the crisis never happened, they accidentally train people to create problems they can then visibly solve. The credit thief and the helicopter collaborator do not just survive in this environment. They are actively incentivized by it.
Every time a last minute rescue gets more recognition than months of careful quiet work, the organization sends a signal about what performance actually looks like here. And people very rationally respond to the signal. Psychologists call this a perverse incentive, a reward structure that accidentally encourages the opposite of the intended behavior. The organization wants stability, well-managed projects.
It rewards the dramatic intervention and then it wonders why nothing ever runs smoothly. Condition two, accountability without clarity. When roles and ownership are never clearly defined, when everyone is broadly responsible and therefore nobody is specifically accountable, blame becomes the default currency when something goes wrong. A fast-to-sfinger wins.
And the people who have spent the longest in the organization, who have the most established relationships with the people around them, who have had the most practice at the blame redirect, those people have a significant structural advantage. This is the diffusion of responsibility in its most damaging workplace form. It is not that nobody cares. It is that accountability has been spread so thin across so many people and so many layers that it effectively belongs to nobody.
And in that vacuum, the finger pointer and the darvo operator operate without friction. Condition three, collaboration as performance. This looks like a meeting scheduled for every day of the working week. Invitations to rooms that have nothing to do with your work.
Exclusion from the rooms that have everything to do with it. When organizations schedule collaboration rather than practice it, when the meeting exists to signal inclusivity or rather than to drive decisions, when the same people are invited to everything and the right people are invited to nothing, they create the perfect conditions for resentment, disengagement and the quiet sabotage of the change resistor in disguise. Researchers call this performative inclusion. And it is one of the most corrosive dynamics in a workplace because it borrows the language of belonging while delivering the experience of exclusion.
The person who is invited to every meeting that has nothing to do with their role while being absent from every meeting that shapes their work is not included, they are managed. And the difference between those two things is something the human nervous system understands even when the official narrative insists otherwise. Condition four, silence as safety. And speaking up has historically led to consequences.
Being label difficult, being sidelined, being given a lame excuse or a dismissive reassurance that it was not personal, people learn very quickly that silence is the most rational choice available to them. And in a culture of silence, the loudest voice wins. The most established voice wins. The most politically connected voice wins.
Almost always, that voice belongs to someone who has learned that the organization will not challenge them. Amy Edmondson's research on psychological safety shows that the cost of this is not just individual. It is at the organizational level. Tames with low psychological safety make more errors, innovate less, and lose their best people faster.
Not because those people are weak, but because they are perceptive. They can see clearly what the organization is and is not willing to examine. And eventually, they make a rational decision about whether to keep offering their best to a system that has demonstrated it will not receive it. Condition five, change management that excludes the champions.
This one is both common and quietly devastating. An organization undertakes a major change, a new system, a new process, a restructure. It identifies change champions, the people closest to the work, the ones with the institutional knowledge, the ones whose buy-in will make or break adoption. It gives them a title and a remit.
And then it excludes them from the design decisions, the key work tasks being decided, the rooms where the actual change is being shaped. Researchers call this the implementation gap, and it is one of the most well-documented causes of change program failure. Mackenzie's research on large-scale transformations found that projects where front-line and operational staff were meaningful involved in design and implementation had dramatically higher adoption rates and significantly lower rework costs. And yet the pattern persists.
The people who live in the new system every single day are consulted last. Briefed, late or asked to champion a change they were never invited to shape. The organization asked for champions, then it excluded them from the championship, and then it wondered why the change did not stick. Condition six, cosmetic change management, the roadmap that goes nowhere.
There is a particular kind of change management failure that is worth examining on its own, because it is so common and so perfectly illustrates the gap between the official values list and the real one. It looks like progress. It has the visual language of progress, the update meetings, the project terminology, the graphic on the wall that is supposed to show everyone where the project is going. But look more closely.
The graphic is decoration rather than a genuine accountability tool. The meetings circulate status without driving decisions. The roadmap shows a destination but no stations along the way. Or the destination is so vague and people can see some milestones that they've achieved, yet they have no clue where the next destination is or how to get there and by when.
This is the kind of roadmap where you have a destination identified. No milestones that anyone can see, track or hold the project to. And the people with the deepest knowledge of what the change actually requires, the ones who suggested the visual roadmap in the first place, the ones who know where the gaps are, are not in the room. Psychologists call the response to this ambiguity aversion.
The deeply human tendency to find uncertainty more distressing than the difficulty itself. Tell people it will be hard and they prepare. Tell them nothing and they catastrophize. A visual roadmap done properly does not just communicate progress, it reduces anxiety, builds trust, creates shared language and gives people something to orient to when the ground feels uncertain.
A visual roadmap done is theater, does the opposite. It signals that the organization does either not know where it is going or does not trust its people enough to tell them. The Dunning-Kruger effect is worth naming here too. The tendency for people with limited competence in an area to significantly overestimate their own capability within it.
Do I mean by that? A project team that cannot clearly communicate what comes next is often a project team that has not clearly defined what comes next. The communication gap is a symptom. The planning gap is the disease and the people who could see both clearly were sitting outside the room.
Condition number seven, tolerating toxic behavior in established people. This is perhaps the most uncomfortable condition of all because it requires an organization to look honestly at the gap between its stated values and its actual behavior when those values collide with convenience. The de-railer who has been there the longest, the one who has the relationship with a senior leader, the one who's technical knowledge or who's institutional history, however distant, makes addressing their behavior feel more complicated than absorbing the damage it causes. This is what researchers call exception culture.
The unwritten rule that certain people operate under different standards than any one else. The cost of it is not just to the individuals who absorb the direct impact of that behavior. The cost is to every single person in the organization who watches it happen and updates their understanding of what the real values list says, whether they realize it or not. Because here is what exception culture teaches that the people around them.
It teaches the new colleague that this is how things work here and begins the process of normalization that we discussed in episode one. It teaches the person being targeted that their experience is not important enough to address. And it teaches the bystanders, the people who see it and say nothing. That is not a place where speaking up makes a difference.
Every tolerance of behavior that violates the official values is a deposit into the organizational shadow. Enough deposits and the shadow becomes the culture. There is also a specific insidious variant of this condition worth naming, what I call manufactured inadequacy. This is where an established person ensures that a colleague is excluded from the rooms where knowledge is built, then points to that colleague's resulting knowledge gap as evidence of their incompetence.
The exclusion creates the gap. The gap justifies the exclusion. It is circular, self-reevorcing, and almost impossible to challenge from the outside because each individual steps looks entirely reasonable in isolation. Condition eight, leadership instability and the blame absorption cycle.
The Standish group whose chaos report has tracked technology projects success and failure rates for decades, consistently identifying leadership instability as one of the top three predictors of project failure. McKinsey's research is consistent on this point. The gap that is actively present and modeling the change it is asking for from others to make makes a transformation five times more likely to succeed. The reverse is also true.
Every leadership transition resets momentum, disperses institutional knowledge, and reopens decisions already made. Think back to any project you have been a part of in some way. Look at any major implementation that's cycled through multiple leaders and ask yourself, how much did it cost the organization to start from scratch each time? I think you would be astounded by the result and the answer.
Think about what leadership turnover actually means on a major project. Every new leader arrives with their own interpretation of the brief, their own relationships, their own trusted people, their own ideas about the project and what it should look like at completion. Every transition triggers a period of stalled progress while the new leader gets up to speed. Previous decisions get quietly revisited or sometimes completely changed.
Scope shifts again. Institutional knowledge. Understanding of what has already been tried, what has already failed, what the people closest to the work actually need, walks out the door with the departing leader, and has to be rebuilt from scratch every single time. Here's the part that rarely gets examined honestly.
Why do project leaders keep leaving? Sometimes it is genuinely personal, but in many cases the answer is something researchers call systemic blame displacement. It is one of the primary reasons dysfunctional organizations remain dysfunctional across decades and across generations of leadership. When a project runs into trouble and on a major implementation it always will, someone has to be held accountable.
The project leader is the most visible and the most removable. So they absorb the blame. They're replaced. The new leader arrives, the underlying conditions, the unclear governance, the shifting scope, the completing stakeholder agendas, or competing ones even.
The excluded voices, the absence of genuine accountability remain entirely intact and the cycle begins again. They carry the organizational blame so that the deeper systemic issues never have to be officially examined. You can change the leader as many times as you like. If you do not change the conditions, you change nothing.
This is why some organizations never change. Not because they lack good people, but because the system has learned to protect itself by treating people as the problem. The moment you name the person, you can stop examining the system. And examining the system requires a kind of institutional courage that is rather than any correction that is rarer than any technical skill.
So what am I trying to say? If you can examine the system that is required, not pointing fingers and placing the blame at somebody's door, that is the courage that is far rarer than any technical skill. It's so much easier to just point the finger. It's like playing hot potato.
Oh, it wasn't me. It was so and so. It deflects the energy and the blame culture onto somebody else. And for you, I'm, you know, got out of that one really quickly is how you then start to teach your organization how to behave.
Fred Brooks captured a related truth back in 1975 and what became known as Brooks Law. Adding manpower to a late project makes it later because every new person requires onboarding, creates new communication lines and generates rework on decisions already made. The instinct to solve a governance problem by adding resources is almost always wrong. And the fact that it remains the default response 50 years after Brooks documented it, it's own kind of organizational shadow.
The final condition is in some ways the most human of all and therefore the hardest to address because it does not require anyone to be malicious. None of these really are people being very insidious or very calculated or malicious. They just are who they are and possibly quite frankly don't even realize it. But nobody is required to assume anything.
It only requires everyone to assume that someone else is handling it. In psychology we call this pluralistic ignorance, a situation where everyone privately doubts, disagrees or is troubled by something, but assumes that everyone else is comfortable. So it must be me, everyone else is okay. So nobody says anything.
The dysfunction continues. The behavior goes unaddressed. The culture calcifies around what was never challenged and the derailer operates without resistance. Not because nobody sees it, but because everyone assumes the person next to them has already tried and failed or that it is above their pay grade or that raising it will cost them more than absorbing it.
The bystander organization is not populated by cowards. It is populated by people who have learned through direct experience or through watching others that the organization does not consistently protect the people who speak up. And until that changes, the most rational individual response is to stay quiet and hope somebody else finds a way through. But here is what I want you to hold on to as we move forward.
And closing the section, pluralistic ignorance only works as long as nobody breaks the silence or disagrees with the derailers. The moment somebody names what everyone can see clearly, specifically without drama, the spell has been broken. Everyone else discovers that they were not alone in seeing it and the culture shifts. Not always immediately, not always without cost, but it shifts.
The bystander organization stays broken because everyone is waiting for somebody else to go first. The anti-dirailer, which in the right conditions in place, always decides to go first. Like a moment before we close to make the cost of all of this concrete, because it is easy to talk about organizational conditions and systemic failures in the abstract. And abstractions do not fully capture what this actually looks like in a real working life.
The cost is the talented person who quietly stops contributing, not with a resignation letter, not with a dramatic exit, just a slow gradual withdrawal of their best thinking, because they brought their ideas and those ideas were adopted without credit or dismissed without engagement, or used by somebody else who received the recognition. And eventually the mental calculation shifts. Why bring my best if the return on that investment is invisibility, is what they think to themselves. The cost is the new colleague who arrives with energy and genuine enthusiasm, who looked to the people around them to understand how this place works, and who 12 months later is using the same language, the same dismissive tone, the same patterns as the most difficult person on the team.
Not because they chose those behaviors, but because nobody showed them anything different. The water they were given to swim in was contaminated before they arrived. The cost is the project that fails, not because the strategy was wrong, but because the wrong people were in the room. The work tasks were mapped by the person most invested in how things have always been done around here, rather than how they could be done better.
The change champions who could have seen the gaps were sitting outside the door. The visual roadmap was a graphic, rather than a genuine accountability tool. The project leader who finally understood the full picture was replaced, just as they were beginning to make progress. The cost is the organization that celebrates collaboration on its values wall while its most knowledgeable and committed people are updating their profiles and quietly exploring their options.
Not because the work is not meaningful, but because the gap between what the organization says it is and what it actually does has become too wide to continue ignoring. The cost of a derailleur is never just the project. It is the people who were in the room, the ones who watched, the ones who learned, the ones who decided quietly and privately that this is not a place worth bringing their best self to. And here is the number that puts all of this into context.
McKinsey's research on large-scale change programs found that 70%, 70% of them fail to achieve their intended outcomes. Not because the technology didn't work, not because the strategy was fundamentally flawed, but because the human conditions inside the project were never honestly examined. The shadow was never named. The conditions were never addressed.
And the people who could have made the difference were never genuinely invited to. They named the derailers, and now we have named the conditions that built a stage for them. And I want to acknowledge something. If you've been sitting here recognizing your organization and all of this, that can feel heavy.
It can feel discouraging. Like the problem is so structural, so embedded, so much bigger than any one person that the question of what you can actually do about it feels almost unanswerable. I understand that feeling, and I want to offer you something before we close today. The people who came through dynamics like the ones we have described, who work inside bystander organizations, who had their ideas adopted without credit, who were excluded from the rooms that shaped their work, who watched new colleagues slowly absorb the toxic patterns of the most established voice in the team.
Those people do not all look the same when they come out the other side. But the ones who come out strongest share something. They made a decision, not always loudly, not always visibly, but a decision nonetheless. They decided that the organization may have built the stage, but they were going to choose how they perform on it.
They decided that the absence of recognition from the people above them did not determine the value of what they were doing. They decided that being excluded from the room did not mean that they did not belong in it, and they kept going. They built their knowledge anyway. They documented what they knew.
They showed up for their colleagues, even when nobody was covering for them in return. They trained the person who needed training without waiting for a thank you, or even being asked to. They brought the idea even when the credit went elsewhere. Not because they were naive about what was happening around them, but because they had decided that their standard was not going to be set by the lowest standard in the room.
The organization built the stage, but you decide the performance. No casting decision, no exclusion from the room, no unacknowledged idea, no lame excuse, and no insincere appreciation can take that decision away from you. That is what episode three is about, not just surviving the conditions we have described, but becoming something the conditions cannot touch. The anti-dirailer.
The person who changes the temperature of a room by the way they show up in it. The colleague who gives real recognition when the organization gives empty validation. The professional who builds their knowledge regardless of what anyone predicted for them. The person who goes first in the bystander organization.
I've been looking forward to that episode since we started the series, and I think it might be exactly what you need right now. I will see you then. If this episode gave you language for something you have been living, share it with someone who needs to hear it today, and I would love to know which of the nine conditions do you recognize most in your organization. Come find me on Instagram or LinkedIn and tell me.
Those conversations are exactly why I do this. Until next time, my friend, the organization does not get to write your story. Only you do.