I was the one who first marked that question as "reference question (being too broad and open-ended)", and I'll try and explain my POV on this. I'll use an analogy (a library, a book and a dictionary) and a technic described by Justin Bariso in his article about Jeff Bezos running a meeting.
I'll just plagiarize, parody and pastiche a great part of the article and its ideas (1)
Bad meetings: We've all experienced them. Whether it's poor planning, too much talking, or lack of preparation, bad meetings waste precious time and money.
Translated and adapted to:
Bad questions and bad answers. We've all experienced them. Whether it's poor writing, [ too broad / straight to the point / unclear / harsh ] answering, or lack of explanation, bad questions/answers waste precious time and energy.
There we go, now, I'll give it a 1st try as my draft about this "parody"...
"It all comes down to following three simple rules".
Too many persons = too many different opinions = too many problems.
#1. "Two pizza" teams now becomes "two options" answers.
If you've ever read a question or answer with too many ideas behind them, you can understand the wisdom in this. The broader the question, the greater number of options and ramifications -- and the more difficult it becomes to reach conclusions and make decisions. But with the "two options" answer rule, you get the balance of obtaining diverse viewpoints and ideas, while remaining agile and manageable.
Too many ideas = too many different options/offshoots = too many problems.
RULE N°1 : Have a "SIMPLE" DIRECT QUESTION, that can be answered WITH NO MORE than 2 options, and you'll have a GREAT QUESTION.
#2. No PowerPoint - it's not just bullet points now becomes "No-switch answer"
Somebody for the answer has prepared a narratively structured memo. It has real sentences, and topic sentences, and verbs, and nouns. The great answers are written and rewritten, shared with other members who are asked to improve the work. They simply can't be done in a minute or two.
Answers like these are a great idea because our brains process good storytelling much better than hard data. Such narrative answers give members the chance to fully communicate the thoughts behind their ideas, and give readers the chance to better understand full concepts.
No ON/OFF answer - it's NOT just a TL;DR then some bullet points.
RULE N°2 : Have a "SIMPLE DIRECT" ANSWER, that can be read/understood WITH NO MORE than 2 options, and you'll have a GREAT ANSWER.
#3 "Start with silence" now becomes "Start with silence" :)
We read those questions. And then we discuss it. And then everyone has actually read the question, they're not just pretending to have read the question. You can imagine why this is so beneficial. "Full sentences are harder to write". They're even harder if you haven't properly read and understood what OP means.
InterPersonal Problems need time for listening, understanding, and answering.
RULE N°3 : write a NICE ANSWER, that take into account the HUMAN PART of it, the questioner or reader's feelings, and you'll have a GREAT ANSWER.
... Long darn thing, isn't it?... :D
Summary: simple question => simple answer. Be as precise as possible when asking AND answering. Any abstraction doesn't seem reasonable, for the same reason that...
But, wait!... Where's that part about "a library, a book and a dictionary"? ;)
In a library, you have separated areas related to a topic. Each area has shelves. Each shelf has books. Each book has chapters. Each chapter has (part of) an idea. Each line of the chapter unrolls and explains the idea. You can't put a library in a chapter, it works the other way around. Any broad question is like looking for a book in the Library of Congress with no plan to help and many guides, each one of them with its own idea about where you should be looking for your book. Seems too broad and opinion based to me, you may be treading the hallways for hours, days, years... :)
In a dictionary, it's even more easy to find what you're looking for, because of the classification system for data, that you know and learn early.
IPS (based on the SE model) is intended, by its creators, to be a library, but with a dictionary style of filing. Make it too broad, and you'll have to search for a very long time for a hypothetically result.
Last but not least...
Be Nice (as per our policy, but not only). At IPS, we don't deal with technical problems. We deal with real human beings and their problems. We don't superficially read, say "hey, I can fix this", don't take time to think about it, then open a folder/drawer and a jack-in-the-box answer pops up, take it, put it here, light on/off, and there you go! I, unfortunately, too often, read some kind of harsh wording that, well, you know... might be suited for a "technical answer" about a "technical problem". But we don't write a book, only lines of it, and we don't write documentation neither. Too broad or too long a question will lead to either a straight-to-the-point answer, or to a looooong looooooong indigestible half-baked mess (who just said this one is? ^^)
The community has decided that it would be great, and therefore, it became mandatory, that every answer is backed-up by data, be it book, personal knowledge/experience, anything that shows why and how it (should) work.
It's not what you intended to say, or the proud own-understanding of yourself, that really matters. It's what the OP and the future users will read and understand.
Conclusion - La Anilla : to me, your question (this one, not the one referenced) is very clear, well written, and has one goal. It took me that long (in time and words) to try to answer. I don't even know if I succeeded. Imagine for a moment if your question had been too broad, unclear, or opinion-based... ;)
(1) if I can't do that for any [ legal / intellectual / ethical ] reason, please let me know ASAP so that I can delete it, thanks.