How much detail do you provide in your Promapp processes and procedures? We're scoping out how to level our processes but would like to hear your thoughts/experiences on when there is too much/too little detail.
Our current scope is the following in Promapp:
Level 0 - set up Promapp Groups using the organisational hierarchy (Corporate > IT > IT Support)
Level 1 - High-level process, linking processes used by that team
Level 2 - Promapp Process, main Activities needed to achieve desired outcome
Level 3 - Promapp Procedure, summary of what Tasks need to be done to complete each Activity within the Process (listing which system is used)
Level 4 - External user guide, detailed step-by-step instructions on how to do each Task (with screenshots, videos etc.)
Our main challenge is to decide how we want people to use Promapp. Do they use it to get an overarching view of all processes required in their team and their dependencies, or do they use it for step-by-step instructions on how to perform their tasks? We've had feedback that some organisations didn't have good Promapp user engagement because there was too much detail, however we don't want there to not be enough detail that people don't get the necessary information and therefore don't find Promapp useful...
Your thoughts would be greatly appreciated!