That’s not my experience. Every decision favors one use case or principle over another. The best design is when you have the vision and confidence to say what’s important for each those decisions and what you’re ok leaving out.
replyIt depends on how you define compromise. Is it a compromise to consider things like screen size, load wait times, or the average expected user's attention span? If so, then design is a big juggling act of compromise.
replyIf not, and compromise is just stuff like "add yet another floating ad footer to make the c-suite happy," then absolutely it should be the last tool.
When you give someone a problem, they can find a solution, but if you give them a dilemma then a compromise is almost a given.
replyTrue dilemmas are rare though, often it just means insufficient investigation of your requirements
replyI disagree, we are faced with "true dilemmas" every day numerous times, not even limited to work and creation — e.g. you might be going to a shop to buy crackers, and while you have a preferred brand, a new entrant might be half the price — do you use the opportunity to try the new one, or get the tried-and-true?
replyThese types of things are ubiquitous when designing and building products — how do you communicate to your users, how much you communicate and how much you automate, how do you target slightly different users (new customer vs old one used to old patterns in your product), what use-case is the most important one (by customer type, customer numbers, and how commonly they do something...), etc.
[dead]
reply