-1

I'm looking to facilitate a collaboratively produced team manual of sorts. It would have things like a vision/mission statement, shared principles, rules of thumb, etc.

I'm interested in the best practices for facilitating this. This may include good examples describing the processes behind them.

Does anyone have good examples or know of something that can help?

closed as primarily opinion-based by gnat, mcknz, Masked Man, Chris E, Xavier J Nov 28 '16 at 14:56

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    this reads way too much like "I can haz documentation plz" – user5621 Nov 2 '16 at 17:55
  • This is off-topic as it can be opinion based and/or us doing the work for you. If you want an essay on the positives of a manual like that, that'd be appropriate. – user49741 Nov 2 '16 at 17:55
  • I'm interested in the processes around creating the documentation, Joe. I'm looking for examples so I'm not reinventing the wheel. If I'm in the wrong place or I'm doing this wrong, please let me know. I appreciate the help. – Jason Rollins Nov 2 '16 at 18:53
-1

The best example I can find is the Netflix slidedeck. I am not speaking of the content (which is good), rather about the way it was created. The author discussed the company culture with people in the organization, interpreted what they said, and she was the sole author and creator of the document. In my experience, this is the best way to create such a document.

I have been through many meetings at many companies where we attempted to creat a manual by committee. The results was always the same. Every person in a group of people will have a bee in their bonnet about something different. The group discussion will bounce around endlessly, and the opinions will never crystallize onto a unified view on any topic. A document produced this way will be a hodge-podge, or it will be so washed out that it has zero impact.

You need to listen to everyone's opinions on the matter, then distill them into a few general principles. Each person will present problems from their past that they want to prevent. They will blame the problems on the culture, and suggest changes to the culture to solve the problem. However, some part of the problem is undoubtedly due to their personality. Your job as listener is to remove some of the personality portion of the problem and extract the true cultural aspects. Universal personality traits (ego, ambition, introvert vs extrovert) have to be factored into your solution, but you may not want to cater to idiosyncrasies.

0

If your question is about the format and not the content, the appropriate tool for this is a wiki. It's a better flow than a repo, because it's easy to access and always show the most recent by default.

There are many free services, and pay-for-privacy options out there. It's also really easy to host your own with any number of open source tools.

I have worked in organizations that effectively use wikis for this type of thing. If you're developing code, redmine integrates one with some M/R functionality.

Not the answer you're looking for? Browse other questions tagged or ask your own question.