I feel like this is an archetype. Show up out of nowhere, half-understand the problem, make a brain-dead suggestion, and then as soon as you point out the problems with that approach, they're suddenly too busy with other things to respond.
Architect: you know, I just feel like there should be a way to solve this in a proper way
Engineer (thinking): (No, you idiot, there isn't, because it's broken! I told you, all options have been tried, and this was the least painful way of doing it. Yes, it's not the ideal solution, but there's no other way, unless the upstream vendor decides to fix the issue on their end!)
I had one where the architecture team implemented the brain-dead solution, advised leadership of other teams that they should adopt the brain-dead solution, and that my team would be supporting the brain-dead solution, without consulting us, and made me into the bad guy when I pointed out that my team did not support the brain-dead solution.
We ended up supporting the brain-dead solution, but that team has now experienced 100% turn over since then.
