See also: http://en.wikipedia.org/wiki/Parkinsons_Law_of_Triviality
Quality control rejected one program because it was indented 4 spaces instead of the standard 5, but accepted another, even though it had enough memory leaks to crash the server under certain conditions. The first was a detail; the second was an issue. It took me 2 days to get Q.C. to understand the difference.
A friend recently arrived for a dinner party an hour late and then complained to me that another spoke with her mouth full. As far as I was concerned, the first was an issue and the second was a detail. My friend thought otherwise about both.
Accounting recently spent 3 days implementing a new key policy for the private rest rooms (presumably to prevent theft) and then wrote off $50,000 of inventory because no one could find the proper paperwork. IMO, the former was a detail upon which much time was wasted and the latter was an issue that never actually got dealt with.
We spent the first hour of a recent meeting trying to determine naming conventions, but ran out of time before we decided if the customer's credit limit should be split between 2 divisions. Again, wasting time on details and not dealing with real issues. (This is a great example. One of the best ways to lose your shirt is to not deal with credit/collection/accounts receivable issues.)
My favorite on-line example: A few years ago here on hn, I posted examples of how I found some of my customers. I expected some interesting discussion, but the thread was hijacked because of the presence of 2 concepts in my original post "Bible" and "pawn shop". Lots of issues that could have provided value for people were never explored because the gang preferred to beat a detail to death. Unfortunately this sort of thing happens quite a bit on-line.
Funny how I still remember that thread. Here it is:
Examples are everywhere because all human beings prioritize and act on their priorities. But we tend to have different ideas of what's important, relevant, necessary, or good. Hence... discord.
People opposite of you become good programmers and designers.
Detail is everything and oftentimes that's that one thing that makes you stand out among competition and makes the first impression count.
/end of my opinion
You can always delegate the "details", but there's a difference between delegating and deferring (the work for yourself). Knowing what to delegate is very important, of course, which is the main point of edw519's comment, I think.
It's amazing how well this works in person, especially when trying to get something done. My number one question to another is probably, "Is that an issue or a detail?" We can almost always decide together which it is. Then, if it's an issue, we deal with it, and if it's a detail, we move on to the next issue.
This has also saved me countless hours and aggravation on-line. If I post something and someone disagrees, I quickly decide whether or not it's really an issue and only engage the other if it is. I realize that this is just a judgment call, but I'd estimate about 90% of on-line disagreements are just details. In these cases, I think it's best to simply move on.