Preliminary Information
Before I begin, I want to make a clear distinction insofar as I understand the principal purpose of this Stack (the following closely fits the rules as defined in the Tour and the Help Center, but may not be universally agreed upon by the community):
Worldbuilding (on-topic) is the development and consistent use of rules, designs, definitions, and explanations that identify or express an imaginary world of the querent's own creation wherein any number of stories may be told, but which are independent of any story that can be told.
Storybuilding (off-topic) is the creation of a story, no matter how well integrated with its world. It includes plot; circumstances; character & organization choices, decisions, options, and actions; and impossible-to-fit-within-SE's-rules aesthetics such as names, language evolution, the influence of culture, species or environment on design, etc.
I'm making this distinction to help clearly define the purpose of this discussion and vote. This is only about worldbuilding. At this time, all storybuilding is off-topic. Therefore, a choice to adopt a policy to accept brainstorming questions is NOT approval to accept storybuilding questions. From the on-topic Help Center page:
When asking questions keep in mind that the goal of the site is to help you build your world, not to tell your story.
If on the other hand you aren’t sure what a character (be it an individual or organization) should do, that is out of scope for the site.
Why am I Asking for This Vote?
This Stack has had a long and complicated relationship with a fundamental and arguably necessary tool of worldbuilding: Brainstorming. Indeed, one of my own earliest answers, and still the answer I'm most fond of, is an answer to a brainstorming question. Although (and if I remember correctly) the statement in the Help Center warning against brainstorming didn't exist back then, all of the Tour and Help Center rules reflected by that statement did.
Brainstorming questions always violate the basic operational model of Stack Exchange: one-specific-question/one-best-answer. Many, if not most, of the non-community rules found in the Tour and the Help Center are influenced by, if not directly supporting of, that premise. It isn't up for debate because it belongs to Stack Exchange, not us. Therefore (and not surprisingly) the first question about the viability of brainstorming questions occurred a scant two months after the miraculous graduation of Worldbuilding.SE from Area 51.
Two months! And we've been debating it ever since... for the last eight years.1 The current manifestation of the brainstorming rule is a non-committal non-rule that makes everyone tear their hair out. Neither allowing brainstorming, nor prohibiting brainstorming, it says:
If you are looking for discussion, brainstorming, or an overall process rather than specific questions and answers, the Worldbuilding Stack Exchange might not be a good place for your question.
Members of the WB.SE community, I suspect that whether you want to see brainstorming questions or not, you will all agree that the current state of affairs is unacceptable.
The purpose of this post is to affect a change to the Help Center's "On Topic" page. However, that can only be done by the moderators. We're at their mercy. However, if a solid consensus is achieved, at the very least we can point to this post as authorization to act contrary to what the Help Center says.
Argument: Brainstorming is one of the most common and most popular question types on this Stack
And because brainstorming is so common and popular, it's fundamentally impossible to stop. We've been trying for eight years to stop it. It's not working. It won't ever work. Why is obvious:
Quality worldbuilding involves dependencies. While any worldbuilder could sweep away their problem by declaring their rule to be so regardless of those dependencies, it's often the dependencies that add depth and quality to the world.
Almost none of the querents are sufficiently educated in the topic of their question to adequately understand the dependencies, their consequences, or their benefits. They may not even be capable of identifying the existence of dependencies. All they know is that their rule lacks the depth and quality they've seen in the efforts of others.
A choice to forbid brainstorming questions means rigorously policing all users, including new users, about why the round peg of a naturally creative and imaginative process is being pounded into the square hole of a software platform intentionally designed to be specific, objective, and have a clear "best solution" (from the perspective of a programmer, an answer voted "best practice"). But it's the simplest to defend because the rules are clearly stated.
Argument: Brainstorming breaks a lot of Stack Exchange's rules
This is the source of the debate. The following list of rules broken by brainstorming is probably not comprehensive. These all come from the tour, the on-topic Help Center page, the don't ask Help Center page, and the list of reasons to close a question.2
- They are ambiguous (not specific).
- They are too often story-based.
- They are too often an invitation to a discussion.
- They often lack sufficient detail, context, restrictions and requirements to avoid the prohibition against all answers having equal value.
- They can lead to too many answers.
- They are, by definition, open-ended.3
A choice to permit brainstorming questions means we are authorizing an exception to any or all of those violations. While a clear update to the Help Center authorizing brainstorming questions would help tremendously, it will not stop the occasional well-meaning user from voting to close a question for violating those rules. However, this choice is likely also easy because only the most anal of people read the Tour and Help Center anyway.
Argument: The second-to-last paragraph on the on-topic Help Center page might not be within the power of our moderators to modify
While this wouldn't stop a community policy effectively vacating the stated belief about brainstorming, it would mean that adopting a policy to vacate the belief would cause headaches for the next eight years. It would be a great help if one of the Moderators would post a comment telling us if that paragraph can, or cannot, be modified. (If it can be modified, but a new paragraph cannot be added, then the new paragraph shown in "UP VOTE" should be appended to the existing paragraph.)
Why is this important? Because policies that can only be found on Meta that don't quickly burn themselves into the community consciousness are quickly forgotten and often difficult to find. It's the weakest form of community policy.
A Proposal to End the Love/Hate Relationship with Brainstorming (AKA List Questions, Idea-Generation, and Fishing-for-Ideas)
The second-to-last paragraph on the on-topic Help Center page currently reads:
Questions must be specific as well as answerable. If you are looking for discussion, brainstorming, or an overall process rather than specific questions and answers, the Worldbuilding Stack Exchange might not be a good place for your question. Such questions may however be welcome in Worldbuilding Chat. Also see Good Subjective, Bad Subjective for why this type of question is hard, and some guidelines on how to post good subjective questions which are less likely to end up being closed.
UP VOTE: You advocate for changing this Stack's policy and Help Center page to read as follows, or similar as discussed in answers. Lined out text to be deleted. Bold text to be added.
Questions must be specific as well as answerable. If you are looking for
discussion, brainstorming, oran overall process rather than specific questions and answers, the Worldbuilding Stack Exchange might not be a good place for your question. Such questions may however be welcome in Worldbuilding Chat. Also see Good Subjective, Bad Subjective for why this type of question is hard, and some guidelines on how to post good subjective questions which are less likely to end up being closed.Questions seeking a list of possible solutions (also called list questions, brainstorming, idea generation, and fishing for ideas) are permissible only when questions are narrowly scoped by providing details, restrictions and requirements that will lead to a reasonably objective selection of a best answer. Questions deemed to be intentionally written to lead to as many answers as possible will be closed as too broad. Explaining your goals and expectations for answers would be beneficial to avoiding question closure. (Additional details here.)
DOWN VOTE: You advocate for changing this Stack's policy and Help Center page to read as follows, or similar as discussed in answers. Lined out text to be deleted. Bold text to be added.
Questions must be specific as well as answerable. Questions seeking a list of possible solutions (also called list questions, brainstorming, idea generation, and fishing for ideas) are prohibited (additional details here). If you are looking for
discussion, brainstorming, oran overall process rather than specific questions and answers, the Worldbuilding Stack Exchange might not be a good place for your question. Such questions may however be welcome in Worldbuilding Chat. Also see Good Subjective, Bad Subjective for why this type of question is hard, and some guidelines on how to post good subjective questions which are less likely to end up being closed.
The reader will note I lined out "discussion" as well. Though not specifically related to this post, the word, in the context of that paragraph, contradicts the following statement from the don't ask Help Center page, "If your motivation for asking the question is 'I would like to participate in a discussion about ______', then you should not be asking here." I consider that statement to be clear and authoritative compared to the ambiguous statement in the paragraph, above.
Details About This Vote
Comments to this post are for clarifying this post only. If you wish to voice an opinion or insight about this post, please post an answer so the community can adequately participate in the discussion.
Proposed changes to wording of either proposal would be appropriate as answers, not comments. Proposed changes will be discussed in comments to the answers and changes made as efficiently as possible.
1 I will not take the time to list the dozens — more than dozens! — of questions posted on Meta about brainstorming. If you are unfamiliar with the general problem, reading through a bunch of those posts will give you a flavor for the problem. Please search Meta using the is:q filter and, independently, the quoted phrases "brainstorming", "list answers", "list questions", "idea generation", and "fishing for ideas".
2 The appropriate Help Center page for this is here, but it's obsolete, having not been updated since the last VTC rule change by Stack Exchange. That's why I'm not linking to it in the body of the post.
3 And, by definition, they are opinion-based. But the "opinion-based" VTC reason is a big enough can of worms that it should not be discussed here and I believe there are enough other violations to suit the needs of this proposal.