> They often don't really understand my use case. They only hear one part of what my team is trying to do, and then act like they know what I need. Yes, your su

> They often don't really understand my use case. They only hear one part of what my team is trying to do, and then act like they know what I need. Yes, your suggestion works for the use case you know about, but not for the 10 other use cases I need to design for. So then can you not say "but I also have REQUIREMENT_X for this project? Do you think that your solution will mesh with this other need I have?" If you can't have a technical discussion defending why you feel your solution is the best then you must not be confident about your solution.