One of the first things people tend to struggle with is "what unit to use when creating a process diagram." If the granularity is inconsistent, you won't be able to compare diagrams side by side later.
Business Granularity
Tasks are divided into the following hierarchy.
- Department…Example: Sales
- Task Type…Example: Target Selection, Appointment Execution, Business Meeting
- Task…A series of actions composed of multiple operations with a clear objective. Example: Pre-appointment preparation, Pre-meeting preparation
- Operation…A series of movements composed of multiple actions with a defined purpose. Example: Check customer information, Open the talk script
- Action…The smallest unit of movement completed in a single motion. Example: Dial the registered number
Process diagrams are created at the "Task" level. Granularity finer than "Operation" is handled by Teachme Biz Manuals.
Tips for Listing
- Clarify the creation policy…Note down the purpose for which it is being created
- Assign creators by name…Decide on individual names rather than "the sales department"
- Use specific process diagram names…Write something like "Pre-appointment preparation" rather than just "Sales"
List in Stages
- Start with at least 5…List the tasks you want to turn into process diagrams, then start by creating the one with the highest priority
- Once familiar, aim for around 20…Expand the scope after you understand how to create them. Increasing the number from the start will result in inconsistent granularity
If you can't think of 20, look for tasks that involve many conditional branches and are difficult to explain verbally, tasks that only experienced staff can handle, or tasks like troubleshooting that require judgment every time.
Related
Three ways to create a process diagram
https://help.process.teachme.jp/hc/en-us/articles/61439204394393