Chapter 6. The Villain Effect — A Story of How Organizations Lose Themselves
Let me tell you about someone I once worked with. I'll call him James. James was the kind of person who always seemed to be in the right place at the right time. He wasn't the hardest worker on the team — everyone quietly knew that. But he was very good at one specific thing: making sure the right people noticed him when the results came in.
When the team hit a target, James was the one presenting the numbers to leadership. When something went wrong, James was conveniently in a separate meeting. He never lied — not exactly. He just had a gift for framing things. For being the face of good news, and reliably absent when the bad news arrived.
Within two years, he had two promotions. The people who did the actual work? Most of them had quietly moved on. The ones who stayed had learned something they probably wished they hadn't.
Chapter 1 — How Does Someone Like James Even Happen?
Here's the thing about James — he didn't show up as a villain. Nobody does. He showed up as a highly motivated, confident team member who delivered results. And in the beginning, that was genuinely true. He worked hard. He produced. There was nothing to question.
But over time, as he learned how the system worked, his behavior began to shift. Not dramatically — just gradually. He started investing less in the work itself and more in how the work was perceived. He stayed later, not to finish tasks, but to be seen at his desk when the manager walked by. In meetings, he made a habit of speaking last — after hearing everyone else's ideas — so he could present a polished summary as if the thinking were his own.
And the organization never pushed back. Because his numbers were fine. Actually, his numbers were excellent — on paper.
“His numbers were real. That was the hardest part. You couldn't point to a lie — not directly. The problem was everything that wasn't in the numbers.”
— a colleague, three years after James moved on to his next role
This is how it works. People like James aren't con artists. They're simply very good at reading what the system rewards — and then optimizing for exactly that. They find the gap between what's measured and what actually matters, and they take up residence in it.
“So this is how you get ahead here.”
Nobody said it out loud. But everyone was watching. And everyone understood.
Chapter 2 — The Day He Got Promoted, Everything Changed
When James received his first promotion, the team didn't say much. What was there to say? Management had made their decision. But something shifted in the room that day — something quiet, almost invisible.
The newer members of the team — the ones still figuring out how things worked here — were watching. They saw who got rewarded and for what. They drew their own conclusions. And over the next few months, without anyone planning it, the team started to behave differently. People shared less. Collaborations became more guarded. In meetings, everyone began managing their own visibility just a little more carefully.
“Okay. So that's how this place works.”
That single thought — silent, personal, never spoken aloud — is more powerful than any culture memo the company could ever write. Once people think it, the rules of the game have already changed.
The good people — the ones who genuinely wanted to do solid work and had no interest in playing these games — started leaving. Not all at once. One by one, over about a year. Each of them had a perfectly reasonable explanation: a better opportunity, a new challenge, more money elsewhere. But if you asked them honestly, the real reason was simpler. They were tired of working hard for someone else to take the credit.
The quarterly numbers still looked fine for a while. They usually do. The real damage — the trust that eroded, the talent that walked out, the habits that quietly took root — none of that shows up on a spreadsheet until it's already too late to fix easily.
Chapter 3 — It Depends on Where You Work
After working across different kinds of organizations, here's what I've come to notice: the James story doesn't play out the same way everywhere. The type of organization matters enormously. Not because people are fundamentally different, but because certain conditions make it easy for someone like James to thrive — while others make it nearly impossible.
Consider three very different workplaces: a consulting firm, a shipbuilding company, and a solid manufacturing business with about eighty people. Same James. Three very different outcomes.
In a consulting firm, James is in his element. Everyone runs on an 3 months or 6 months—perhaps 16 months clock — perform visibly, or move on. There's no time to build real trust, no long-term track record to examine. By the time anyone figures out what James has actually been doing, he's already been promoted or moved to a client company with a glowing reference. The up-or-out culture creates intensity — but it's also the perfect cover for someone who's good at looking intense without being genuinely deep. James was, in many ways, built for this environment.
In a shipbuilding company, James has a harder time at first. People stay for over twenty years . The work is physical and visible — a hull either passes inspection or it doesn't. You can't fake your way through a sea trial. The senior engineers remember exactly who solved the problem in 2009, and they'll tell you if you ask. James can still rise here, but it takes longer and demands more genuine credibility.
The catch? Once James gets entrenched in a place like this, he becomes nearly impossible to move. He's been here fifteen years. He has relationships in every department. He knows where every body is buried. No one wants to be the person who starts that fight. So he stays — sometimes for decades — and the organization learns to work around him like a permanent obstacle in the corridor.
Now put James in an eighty-person company where the founder still walks the production floor every morning. Suddenly, his whole toolkit fails. The owner was in the room when the team solved the problem — he saw exactly who did what. There's no gap between "what the numbers say" and "what actually happened" because everyone can see what actually happened. James tries to claim credit in a team meeting and three people immediately push back — not politically, just factually: "Actually, that was Minjung's idea. You were on leave that week." James can't manufacture fog in a place where everyone can already see clearly. He either adapts and becomes genuinely useful, or he leaves. Either way, the organization wins.
We spend a lot of time admiring the big consulting firm and the global shipbuilder. But in the specific fight against the James effect, it's often the unfashionable, unglamorous eighty-person company — the one nobody writes case studies about — that wins.
Chapter 4 — The Manager Who Got It Right
A few years after the James situation, I worked with a manager I'll call David. He ran a team roughly the same size, in a similar industry. But his team was different. After two years, the same people were still there. They were more capable than when they started. Under pressure, they still spoke well of one another.
I asked him once what he did differently. He thought about it for a moment and said: "I just decided from the beginning what I was actually trying to build." That was it. Not a framework, not a policy document — just a clear, early decision about what success would mean on his team.
Every review, after going through the results, David would ask: "How did you get there? Who helped you? What would have happened if you'd been on leave that week?" It wasn't an interrogation — just genuine curiosity. But that curiosity sent a clear signal: on this team, the process matters, not only the outcome. James-type behavior becomes considerably less useful in that kind of environment.
"One strong quarter tells me someone can perform under the right conditions," he said. "It doesn't tell me what kind of leader they'll be." He consulted peers. He looked at what happened to the people who worked under a candidate — did they grow, or did they quietly request transfers? A strong individual number can reflect genuine effort, or it can be the result of quietly extracting from the team around you. David wanted to know which one it was before making any permanent decision.
"A good manager's team should be able to run without them," David said. "That's the goal — not dependency, capability." He evaluated managers on whether the people under them were getting sharper, taking on more, growing confident enough to push back. That one shift changes everything about who wants to be a manager on your team, and why.
Decisions required multiple voices. Recognition was shared publicly. There was no single gatekeeper for visibility. "I'm not trying to create bureaucracy," he told me once. "I'm just making sure the loudest person in the room can't quietly rewrite the rules in his own favor." A simple idea. Harder to implement than it sounds. But it works.
On a ship, the James problem doesn't survive very long.
When you're at sea, the work is too real and the consequences too immediate for someone to fake their way through it. A first officer who claims credit for safe navigation while concealing near-misses will eventually cause an accident. The sea doesn't care about quarterly reviews. It gives you immediate, unambiguous feedback.
That clarity is rare in a boardroom. But it's exactly the kind of clarity that healthy organizations find ways to recreate — on land.
Key Takeaways
📘 Series — 성공이 만든 리더의 위기와 성장의 심리학
Maritime cybersecurity professional specializing in IACS UR E26/E27 compliance, OT system architecture, and organizational leadership in Maritime 4.0.
⚓ Join the ShipPaulJobs Community
Join →
Comments
Post a Comment