OT: Guidelines for Great Subjective Forum Discussions

All things flight-related for Hang Glider and Paraglider pilots: flying plans, site info, weather, flight reports, etc. Newcomers always welcome!

Moderator: CHGPA BOD

Post Reply
chgpa
Site Admin
Posts: 129
Joined: Fri Dec 05, 2003 12:50 am

OT: Guidelines for Great Subjective Forum Discussions

Post by chgpa »

Apologies for this non-Flight-Related topic, it is definitely outside this forum's charter. I'll understand and acquiesce if pilots object and wish to see it moved elsewhere, just say the word.

However! Given the tone of some recent posts, so early in the (for many) non-flying winter months... I feel that it must be shared, in the hopes that we can avoid the all-too-predictable flame-wars that seem to occur at this time of year.

There are many forums dedicated to what _seem_ to be fairly objective and factual topics. Software/programming. Physics. Engineering. All that 'hard' stuff.

But even when the content area _seems_ to be so cut-and-dried, forums dealing with these topics often delve into subjective areas. And all too frequently, the resulting discussions devolve, and participants who might otherwise provide helpful and meaningful contributions choose to "check-out" of those discussions.

This is a well-understood and recognized phenomenon. It happens ALL OVER the web. So frequently, in fact, that people have tried to outline strategies to prevent it. And here's one of them:

Good Subjective, Bad Subjective

I ask you to consider the points of that post (which is excerpted below) the next time that you want to discuss controversial topics, such as:
  • Full-face vs non-full-face helmets
  • Hook-In protocol (at launch? Or prior to launch?)
  • (HG) Using wuffos for wirecrew? Or not?
  • Flying solo? Or not?
  • Flying in wave conditions? Or not?
  • PG landings : Safer than HG? Or not?
  • HG launches : Safer than PG? Or not?
  • Insert your pet-peeve here!
I don't mean to be a nag, I just want people think _before_ they post. We all benefit when the signal-to-noise ratio is high, right?

Cheers,

MarkC

Guidelines for Great Subjective Questions

Great subjective questions inspire answers that explain “why” and “how”. The best subjective questions invite explanation. If you’re asking for a product recommendation of some kind, you want answers to contain detailed information about the features and how they can be used, and why you might want to choose one over the other. “How?” and “Why?” has more lasting value than a bunch of product-feature bullet points or a giant enumerated list, no matter how extensive. In contrast, the bad subjective questions let answerers get away with hit-and-run answers that maybe provide a name and a link — but fail to provide any sort of adequate explanation, context, or background.


Great subjective questions tend to have long, not short, answers. The best subjective questions inspire your peers to share their actual experiences, not just post a mindless one-liner or cartoon in hopes of being rewarded with upvotes for being merely “first.” Sharing an experience takes at least one paragraph; ideally several paragraphs. If I’m asking about how to bake cookies, don’t give me a list of grocery items: milk. butter. vanilla. eggs. There is virtually nothing I can learn from a short, static list of grocery items that make up a recipe. Instead, tell me what happened the last time you made cookies from that recipe! Share your detailed experiences, so that we all might learn from them.


Great subjective questions have a constructive, fair, and impartial tone. The best subjective questions avoid the all too seductive route of ranting and flamebait. They set the right tone of constructive learning and collaboration from the very outset, by emphasizing that we’re all here to learn from each other, even if we have different viewpoints or beliefs about the right way to handle what are inherently subjective decisions. We’re not here to fight each other; that’s an enormous waste of everyone’s time. There is always more than one right way.


Great subjective questions invite sharing experiences over opinions. Certainly experiences inform opinions, but the best subjective questions unabashedly and unashamedly prioritize sharing actual experiences over random opinions. It’s more useful to share with us what you’ve done than what you think. Everyone has an opinion. It takes zero effort or imagination to have an opinion about anything and everything. But people who have done things, real things in the world, and have the scars and arrows in their back to show for it — now that’s worth sharing. You should be uniquely qualified to have your opinion based on the specific experiences you had. And you should share those experiences, and more specifically what you learned from your experiences, with us!


Great subjective questions insist that opinion be backed up with facts and references. Opinion isn’t all bad, so long as it’s backed up with something other than “because I’m an expert”, or “because I said so”, or “just because”. Use your specific experiences to back up your opinions, as above, or point to some research you’ve done on the web or elsewhere that provides evidence to support your claims. We like you. We want to believe you. But like wikipedia itself, {{citation needed}}. And good subjective questions make this clear from the outset: back it up!


Great subjective questions are more than just mindless social fun. The best subjective questions avoid the social pitfalls of “Getting To Know You” (GTKY) and mindless entertainment. Sometimes people just want to poll a community for ideas that might help solve a problem (best book, best approach). These can be okay when there is actual knowledge in the collection of answers. What isn’t okay are the social bonding questions which are designed just to impress others, such as “What is the coolest/stupidest/weirdest/funniest thing you saw/did/tasted today?”, or questions where the site’s actual topic is tacked on as a token afterthought, such as “Favorite food for programmers.” If you removed the “for programmers” part of this question, is it really unique to our profession? Could an average member of our community reasonably be expected to learn something that makes them better at their job from this question? If not, then it’s a bad subjective question.
Post Reply