In mathematical optimization software, defining the weight and level (hard/soft) of each of the objectives/constraints is often difficult for the business people at software development time, due to the impact on different stakeholders. There are several ways to deal with this, one being multi-objective optimization.
Most business people typically love the idea of multi-objective optimization, in which they don't need to make though choices now, but the software will present them with a number of solutions (from the pareto front) to pick from, for every problem that the solver optimizes.
Does it ever work in production?
For a user to pick the best timetable out of 2 wildly different timetables on the pareto front, is very non-trivial. Especially because they didn't help to create the timetables to begin with. Often there are easily thousands of solutions on the pareto front. Making matters worse, the number of solutions in a pareto front scales exponentially with the number of objectives.
Do you know of any multi-objective optimization use cases that survived first contact with production usage? Cases that are actually still used by end-users in production? How does the UI handle showing multiple solutions?