Dear all, I just would like to check one idea with you. I am looking for a good way to document internal company processes. The traditional way to do such thing - create some flow chart with additional description. My experience though is that it does not work for anything quite complex  The good example of the document, describing process is PRINCE2  If you look at PRINCE2 however, there is no overall flowchart diagram in the book. It contains a bunch of diagrams on different pages with links to each other. There is a reason why there are some companies, who are trying to further clarify PRNCE2 by creating such a diagram for instance https://www.quanta.co.uk/sites/default/files/docs/prince2_process_model_v1.1.pdf Or books like:  PRINCE2 Made Simple, or PRINCE2 in Action: Project management in real terms I was always wondering, that if PRICE2 requires further clarification, then there is something wrong with the original book.  I have had my PRICE2 practitioneer certification, but even straight after exam I don't quite understand how all PRINCE2 works together and which procedures exactly Project Manager is responsible for If I imagine myself as a new Project Manager, walking into the organisation, I would expect some document, which describes how they do certain processes. I would want to know 

• What activities are to be done
• in which sequence
• who is involved each of the procedures, preferably in a form of RACI matrix (Responsible, Accountable, Consulted with, Informed.)
• I would want to know for each of the procedures which tools are involved
• I would want to be able filter all activities in different ways:
  • By responsibility (e.g. find all procedures, for which project Manager is responsible for or cunsulted with)
  • Find all tools, which are required to be used 
  • find all procedure, where a certain tool is required
•  Find a breader description of how to do every particular task, if needed.

But if one thinks of this, all of this falls very well into project schedule.

• Procedures - activities
• dependencies - links
• Roles involved one can assign as resources.
• Tools one can assign as resource as well
• References (links) to detailed project description can be put is a activity note

 And then one has a power of a project management software (e.g. MS Project) to filter and analyze this document further  The only thing which is not that straight forward - how to document splits in decisions and some loop activities. which you have in flow charts sometime. Any thoughts on this? How do you guys document your processes? P.S. I must say I also accept, that I may have some prefessional deformation after using too much of project scheduling tools. But somehow I often just don't understand things, untill they are put in a project schedule.