You have a Master’s degree. You have a decade of experience. You’ve given the best years of your life to the tech industry. And right now, you’re on antidepressants, battling dark thoughts, because a development team can’t ship a single GET endpoint in six months.
This is the grim reality for a Product Manager in Sweden who recently posted a cry for help. Hired to lead a modernization project for a legacy enterprise system, they quickly discovered the devastating truth: the development team simply doesn’t know how to build, test, or ship APIs. While management promises customers the world, the team can’t deliver basic functionality.
Your corporate job is a Kabuki theatre. The harder you try to make it real, the faster it will destroy your mind.
You are experiencing the classic legacy enterprise trap. You thought your job was to guide modernization. In reality, your job is to sit next to a broken system and pretend it isn’t broken. But the issue isn’t the workload. It’s the cognitive dissonance. You care too much.
The most dangerous part of a toxic corporate environment isn’t the heavy workload; it’s the cognitive dissonance between your professional pride and systemic incompetence.
You are taking on the emotional weight of delivery responsibility without being given the authority to fix the actual problem. As one seasoned developer noted in response to the post, the team itself is the legacy system. You cannot force modern API outputs from a team that lacks modern skills. You are stepping on the gas of a car with no engine, wondering why you aren’t moving forward, and blaming yourself for the failure.
Surviving this requires emotional detachment, but that feels like a betrayal of everything you’ve worked for. If you stop caring about quality, who are you? You spent ten years becoming an excellent PM. If you lower your standards to match the system’s dysfunction, doesn’t that mean you’ve given up?
The truth is: separating yourself from a system designed to fail isn’t abandoning your standards. It’s preserving your sanity for a system that actually deserves your talent.
Survival isn’t learning to endure the abuse better. It’s realizing your professional identity doesn’t depend on the success of a system that doesn’t care if you live or die.
Stop trying to survive a job that is actively making you sick. Screw the APIs. Screw the legacy system. Do the bare minimum required to not get fired, use your sick leave if your doctor tells you to, and pour every remaining ounce of your energy into finding an escape route. No job—no matter how impressive the title—requires you to sacrifice your mental health to maintain the illusion of progress.
FAQ
Q: But if I stop caring, aren't I just becoming part of the problem?
A: No. You cannot fix a system that doesn't want to be fixed. Detaching in a toxic environment isn't giving up; it's triage. By doing only the work necessary to keep your job while you look for an exit, you preserve your actual skills for an organization that values them.
Q: What's the practical implication of the 'team as a legacy system' concept?
A: It means you must stop blaming yourself for missing deadlines or delivering poor quality. If the team lacks the skills to build what management promises, the failure is systemic. Your job as a PM is to document the gap, not to bleed yourself dry trying to bridge it alone.
Q: Is the contrarian take really just 'quit your job'?
A: Yes. The standard advice is to 'manage up' or 'find small wins.' The contrarian truth is that no amount of Agile ceremonies or Jira tickets will teach a team to build APIs. If the job is making you physically ill, your only winning move is to leave.