"How can I maximize my widgets-produced-in-six-months output given that I'm constrained by having $x budget?" - constraint that could give you a different solution than higher or lower budget.
"How can I maximize my widgets-produced-in-six months output AND my customer satisfaction given that I'm constrained by having $x budget" - now you have to compromise one or the other.
Here I'm talking about the physical design of how the widget is made as it's the first super-concrete example that popped to mind, but almost any sort of design operates in a similar multiple-goals world.
Compromise is stuff like what I'm going through, right now. The user needs to know that a set of locations on a map, can also be displayed as a sortable list, but the affordances for that access are not working with the overall design. It's extremely easy to add a button, but it messes with the screen layout.
We'll figure it out, but we can't ignore it. It's too important to our users, so we may have to make a graphical compromise. It's really tempting to think that "stupid users should know better," but that's a fairly destructive mindset.
However, most folks (not just designers) have a difficult time with compromise, these days. It's become a value judgment (You're "weak," if you compromise).
I learned, when I was a kid, that I can't always get what I want (I think that someone even sang about it, way back then).
The art of compromise, is one of the most valuable skills I had, during my career, and I'm still at it. In fact, I was just texting with a team member, a few minutes ago, where we have to come to a compromise.
It's pretending there isn't one.
Every product optimizes for something. The interesting question is what it chose to sacrifice.
More often than not, a compromise means that the problem wasn't scoped out well enough, and it ends up partially solving a problem that didn't need solving.
eventualcomp•38m ago
There might be a deeper point being communicated, not sure, but I see no issue here.