Loading…
8
Why I broke the code of silence about project shortcuts, despite the backlash
In my last role, I saw a senior engineer consistently bypassing critical testing phases to hit aggressive launch dates. Everyone on the team turned a blind eye, believing that speaking up would label you as difficult or disrupt the timeline. I couldn't stay quiet, so I reported it to management, knowing it might jeopardize my standing. It did lead to tension and even a missed promotion, but preventing a potential product failure felt more important. Would you have done the same?
3 comments
Log in to join the discussion
Log In3 Comments
willowa207mo ago
Systemic pressures often reward compliance, making ethical dissent a costly but necessary act.
8
robin_roberts7mo ago
At Acme, silence was golden, but your report made me reconsider.
2
king.lisa7mo ago
My friend Nathan used to be at a firm where not rocking the boat was the unofficial policy. Management preferred quiet compliance over any kind of feedback, which led to some truly bizarre decisions. Then an internal audit report laid out the cost of all those silent nods in stark terms. Suddenly, the same managers were holding 'listening sessions' with all the enthusiasm of a root canal. The report is probably framed in someone's office now, a monument to reluctant enlightenment.
3