You can not use it, but it is more valuable to have it! Therefore, as a small white product manager at this time, we should exert our subjective initiative to build a set of processes to meet such demands. Here, I divide this process into three steps: 1. Sort job function email list out the process Taking grouping requirements as an example, we need to sort out the flow chart, which can be divided into two perspectives, user perspective and business perspective. job function email list The user's perspective is to think from the user's point of view. If a user uses the function of grouping,
What steps need to be completed and which job function email list process needs to go through. The business perspective is to think from the business perspective. It should be noted here that the business perspective is often multi-role, because a function is likely to involve multiple business roles, so when thinking, it should be targeted first. combine. First sort out the process of a job function email list business department separately, and then string together the processes of the entire business department involved to complete the entire business perspective flow chart. Here is an extra point, that is the question of the granularity of flowcharts.
As a product manager of Xiaobai, I often have problems job function email list with too large or too small particles, resulting in a poor experience for those who read flowcharts. The reason for this problem is that when drawing the flow chart, I did not think clearly about who the object of the flow chart is. Here I share three granularities: company level, department level, job function email list and role level. Company level: That is, your flowchart needs to be displayed at the company meeting, then at this time,