Our Apple site has has been very successful (IMO) in handling "list" or "rec" questions in way that seems to ensure that they don't cause most of the problems that they can if not managed carefully.
Here are some examples:
To my view, all those posts are extremely useful, but they can lead to all sorts of problems if you don't establish clear ways to control and manage em:
Limit the number and minimum usefulness required:
They essentially limit the number allowed, so they can't overrun the more specific question, and so that they're generally very useful (since they are limiting to the top handful). In their case it can be highly formulaic (I think they basically allow one "list" of "most useful new features" in each major OS releast per year (which is 2 - iOS, and OSX), plus a couple of more timeless ones, like this one. You could do something less structured, like require them to be proposed on meta and require a certain level of community support, plus only actually put one up on main infrequently.
Corollaries: make it clear in the question that questions like these are only allowed after being vetted by the community on Meta, and don't be shy about protecting them if they attract too much noise and hassle.
Don't let them break the rep system:
If you allow one, make it CW, so the person lucky enough to think of "How to Cook Evrerything" doesn't become a site demi-god with little justifcation.
Define the rules/structure for answering: Do things like making it clear in the question that each answer should be one example, and must include the speciifc reason it's useful, etc. Some sites have elected to roll those answers up to a single answer list, while others have chosen to leave them as individual answers (ususally makes sense if the answers have more descriptive content, etc.)
Accept that some questions like this can be kept up to date, and some can't: Some lists are short enough (or change so little) that communities can keep them current. Others can't, and for those, it's okay to lock (or close) them after a year or however long till that happens and say "this is here because it's still a great resource, but we no longer consider it comprehensive."