I've been looking around different sites's metas to see how they handle different challenges of figuring out how to maintain high quality questions and answers.
With some sites, like StackOverflow, it's easy to spot a good or bad answer. It's generally either right, or it's wrong. Questions either contain facts about the problem and evidence that the question asker has researched his/her question, or it doesn't.
Project management involves many soft skills that make it hard to tell what is right and what is wrong. The Workplace SE solves this problem by enforcing the "back it up" rule:
Please note that answers should be backed up either with a reference, or experiences that happened to you personally. You should always include in your answer information about why you think your answer is correct.
As an example of what this might look like, I tried this out myself on my two latest answers:
For hard skills, or for the more technical points of project management that are taken directly from the PMI or PMBOK, we could directly cite these with a link to the documentation.
Enforcing the back it up rule is something anyone in our community can do. Comment on answers that don't cite references and challenge them. Ask for references, evidence, or something to support the content included in the answer. If the answer cannot be backed up, use your downvotes as a tool to mark that answer as potentially incorrect. Upvote answers that do cite references and that do support the answer.
What do you think? Is this a viable solution for PMSE to ensure we're giving correct answers? Are experiences enough? Should we still cite references if explaining why we think our answer is correct? If not, what are the criteria, and how should we approach this Q&A problem?
Related: Draft of a new policy for our site