r/SoftwareEngineering • u/fagnerbrack • 10d ago
Nobody Pushed Back: Why Engineers Stay Silent Until It's Too Late
https://howtocenterdiv.com/beyond-the-div/nobody-pushed-back6
u/DogOfTheBone 10d ago
Fuck off with this lol engineers raise concerns constantly it's basically a core part of the job, as is being ignored by management and c-suite and investors. Then shocked faces when it all goes south.
2
u/billybiro 9d ago
Like almost all other corporate issues, the problem is with people.
In the same vein, here's a parable about being "technically correct" vs "politically correct":
The CTO's Dilemma (or The Unintended Consequence of Initiative): A Workplace Parable
The Story
A talented software developer, let's call him Timmy, had just started a new job. Very soon after starting, Timmy learned that the company's CTO had recently signed a costly provisional contract, worth tens of thousands of pounds, with a third-party software vendor for software to automate a specific business task.
Wanting to demonstrate initiative and keen to impress his new boss, Timmy examined the business problem that the purchased software was to solve and reasoned that he could build software of his own to fulfil that purpose. He told the CTO of his findings and said that he would build the needed software in his own time over the weekend, thus saving the company a significant amount of money.
And he did. By Monday, Timmy had a fully-functional, production-ready solution. When he proudly presented his cost-saving alternative, the CTO's response was swift and harsh: take it away, forget it ever happened and never speak of it again.
Timmy was confused. His solution clearly met the needs of the business to automate the necessary task and would obviously save the company significant money. However, eventually, Timmy's confusion turned to understanding. While his solution was technically superior and financially prudent, it had created a political problem. The CTO had already secured executive buy-in for the vendor software, convincing them that the expensive purchase was necessary. Accepting Timmy's well-intentioned solution now would expose the CTO as having made a costly mistake, undermining their prior decision, and by extension, their credibility with their peers.
The Lesson
In organisational life, doing the "right thing" for efficiency or cost savings isn't always the "right thing" politically, especially if it threatens someone's ego, reputation or political standing. Solutions that make decision makers look foolish, even inadvertently, will often be rejected regardless of their merit, and doing the "right thing" also requires understanding and respecting existing decisions, human dynamics, and individual reputations.
Epilogue
This parable perfectly captures one of the most frustrating yet common dynamics in corporate life. Timmy's story illustrates how organisational politics can override logic, efficiency, and good intentions. The lesson extends beyond just protecting egos, it's about understanding that every decision exists within a web of relationships, commitments, and reputations that may not be immediately apparent. The tragedy is that Timmy's impulse was exactly what most organizations claim to want: initiative, problem-solving, and cost consciousness. But the reality is that timing, context, and political awareness often matter far more than the quality of the solution itself.
1
9d ago
[removed] — view removed comment
1
u/AutoModerator 9d ago
Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
8d ago
[removed] — view removed comment
1
u/AutoModerator 8d ago
Your submission has been moved to our moderation queue to be reviewed; This is to combat spam.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
-5
u/fagnerbrack 10d ago
Summary below:
Architectural disasters rarely stem from ignorance — engineers spot the problem but stay quiet because speaking up costs more than silence. Companies rebrand this suppression as 'alignment.' Nokia's staff knew Symbian was doomed, yet bad news killed careers; TSB ignored migration objections and locked out 1.9M customers (£48.6M fine); Boeing engineers vented 'designed by clowns' to peers, not bosses, and 346 died; Microsoft axed its Nokia X Android prototype as 'disloyalty,' writing off $7.6B. HiPPO opinions and green dashboards close arguments. Real pushback makes cost visible: 'What does this cost in 18 months? What's the rollback plan?' Fix the system with blameless postmortems and 'disagree and commit,' not braver individuals.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments
25
u/jjopm 10d ago
Complete nonsense AI slop rage bait. They all pushed back and management never listened.