Comment by creativeSlumber
2 months ago
> did anyone on the team really not push back?
This is the real question. If they are serious about not doing something like this again, they NEED to look at what process failed and let something like this get proposed, designed, implemented and pushed to production. Usually things get reviewed at each stage. Did the people who pushed back on this get steam rolled? If no one pushed back, that's an even serious culture question and the entire org would need training.
A serious "we won't do it again", needs to be accompanied by a COE on this for identifying what went wrong, and identifying what guardrails can be put in place and then actually implementing them.
> did anyone on the team really not push back?
That's a tough one. In the big meeting? In the small meeting? "Officially" push back? Encouraged to make the push back unofficial? Etc. Even just internally, it can be hard to quantify. From internal > external, more so.
This so much.
The number of times I’ve had to defend someone else’s customers let alone my own is exhausting.
And that dynamic is only allowed within close circles.
I’ve found once “the decision” is made, the bigger the subsequent meeting, protests are often swept under the rug.
On most occasions the worst part is that folks intentionally withhold information to get their way. And thats real hard to compete against without making an ass out of yourself, or losing the trust of others.
This is why core principals matter so much.
It seems like this was implemented as a way to insert tips, and then abused to insert ads, so the developers involved might not have been aware of that part until later?