It's not a complete answer but I've seen talking about the costs help. That's what's making them overlook things anyways.
What they see is dollars now but not dollars later. Often these data issues can rise to the level that it could destroy the entire business. You might be called a party pooper, but truth is people like this want to keep the party going. It's hard to understand that sometimes keeping the party going means saying no. But it's just the same dealing with drunk people, say no by saying yes to something else. Like presenting another solution. Though that's way easier said than done...
Just remember, everyone is on the same team. People don't say "no" because they don't want to make more money. A good engineer says "no" a lot because your job is to find solutions. It usually sounds like "I don't think that'll work but we might be about to...". If you stop listening without hearing the "but" you can't solve problems, you can only ignore them. Which *that* is not being a team player.
We're always rushing and the truth is that doing good is much harder than doing bad or "evil". I put it in quotes because it's very easy to do things that are obviously evil post hoc but was done by someone trying hard to do good. So I find this language to be a problem because it is easy to dismiss with "I'm not a bad person" and "I'm trying to do good". Truth is that's not enough. Truth is mistakes happen. We work with asymmetric information. It only becomes your fault when you recognize and don't take steps to fix it (or active ignorance).
Sometimes things take nuance. Sometimes it takes more than a few sentences to convey. But who reads longer anyways?
What they see is dollars now but not dollars later. Often these data issues can rise to the level that it could destroy the entire business. You might be called a party pooper, but truth is people like this want to keep the party going. It's hard to understand that sometimes keeping the party going means saying no. But it's just the same dealing with drunk people, say no by saying yes to something else. Like presenting another solution. Though that's way easier said than done...
Just remember, everyone is on the same team. People don't say "no" because they don't want to make more money. A good engineer says "no" a lot because your job is to find solutions. It usually sounds like "I don't think that'll work but we might be about to...". If you stop listening without hearing the "but" you can't solve problems, you can only ignore them. Which *that* is not being a team player.
We're always rushing and the truth is that doing good is much harder than doing bad or "evil". I put it in quotes because it's very easy to do things that are obviously evil post hoc but was done by someone trying hard to do good. So I find this language to be a problem because it is easy to dismiss with "I'm not a bad person" and "I'm trying to do good". Truth is that's not enough. Truth is mistakes happen. We work with asymmetric information. It only becomes your fault when you recognize and don't take steps to fix it (or active ignorance).
Sometimes things take nuance. Sometimes it takes more than a few sentences to convey. But who reads longer anyways?