0:02 the first tool that we will discuss
0:03 under measure phase
0:06 is a process map process map will help
0:07 us to understand
0:09 the current state of our process as we
0:11 move along to the other tools
0:14 of the measure phase a process map is
0:16 used to visualize the nature and the
0:17 flow of the steps
0:20 in a process it breaks down the process
0:23 into its many sub-processes
0:25 it analyzes each of these steps separately
0:26 separately
0:28 which minimizes the number of factors
0:30 that can contribute to the variation in
0:31 the process
0:33 here are the usual mapping symbols that
0:35 we use for a process map
0:38 the first symbol is an ellipse it
0:40 denotes start and end points
0:43 it identifies where the process starts
0:44 when where the process
0:46 ends the second symbol is an activity symbol
0:47 symbol
0:49 that denotes process steps which are
0:50 being done
0:52 inside the entire process the third symbol
0:53 symbol
0:56 is a decision symbol it depicts decision
0:57 nodes or
0:59 points these are where questions are
1:01 being attached
1:03 so that a decision maker can be guided
1:05 of what are the next step
1:07 arrows are used to represent the process
1:09 flow it will give us an idea
1:11 of which will be the next step the
1:14 circle denotes a connector
1:16 a connector connects the process map to
1:17 another flow
1:20 or another page connectors are used to
1:22 make your visualization cleaner
1:24 compared without using them you will be
1:26 using these process map symbols
1:28 as you create your actual process map
1:30 from the case study that was given to you
1:30 you
1:33 here's an example of a process map this
1:35 process map is called
1:38 a macro level linear process map when we
1:39 say macro
1:42 only general details are provided in a
1:43 process map
1:45 when you say linear it only shows the
1:46 linear flow
1:50 of the process example register for the
1:50 training as
1:53 a start attend the training as the first activity
1:54 activity
1:56 take exam as the second activity
1:58 followed by a decision
2:01 did you pass the exam if no you will go
2:01 back to the
2:04 exam if yes then congratulations
2:07 you can now get your certificate here
2:09 are some guidelines when you are doing a
2:10 process map
2:11 process maps are said to be leaving
2:14 documents and must be changed as the
2:15 process changes
2:17 meaning once there is a change that has
2:18 been introduced
2:20 the process map should be updated
2:22 accordingly when you're using process
2:24 map for problem solving
2:27 and process improvement make sure that
2:29 you were able to map what is happening
2:31 to better understand the potential
2:32 causes of the problem
2:35 rather than mapping the ideal state
2:36 wherein we cannot get
2:38 any insight from doing it should you
2:39 face to a problem
2:42 that you don't have any idea of how the
2:43 process operates
2:45 you are free to ask a help from a
2:46 subject matter expert
2:48 so that he will guide you on what will
2:51 be the next steps on how you could map
2:53 your project scope here is another
2:55 example of a process map this is called
2:57 a deployment process map
2:58 the difference between the deployment
3:00 process map and linear process map
3:03 is the availability of column headers
3:05 which corresponds to what we call
3:08 process owner or activity owners for
3:10 this case we have production
3:13 stores purchasing and supplier using a
3:15 deployment process map we will be able
3:16 to see
3:18 the balance between the workload among
3:20 each activity owner
3:22 it will also give us an idea of the
3:24 accountability and responsibility
3:26 of the activity owners to their
3:28 respective process steps
3:31 in this way we can better trace what
3:31 would be
3:33 the source of the problem as we
3:35 investigate it moving forward
3:38 if we're trying to create a process map
3:39 and we want to identify the potential
3:40 causal step
3:43 this particular type of process map is
3:44 the better choice over the linear
3:45 process map
3:47 here are some essential tips when you're
3:49 doing process mapping
3:51 first don't map for mapping state don't
3:52 just go
3:54 and observe the place where you want to
3:55 get information
3:57 but rather have in mind that you're
4:00 doing this for the greater objective
4:03 of solving the problem as mentioned you
4:04 have to go and observe
4:06 this process is called walking the
4:08 process or gembawa
4:11 gemba means actual workplace in japanese
4:14 what you want to do in the gemba is to
4:15 observe and engage yourself
4:18 to frontline workers so that you will
4:19 have an idea
4:21 of what is happening in the process by
4:23 engaging yourselves with them
4:25 you will have an idea of what are the
4:27 problems that they are encountering
4:29 and what are the typical solutions that
4:30 they are implementing
4:33 number three map what the process really is
4:34 is
4:36 as mentioned you have to map what is
4:38 currently happening and not what is ideal
4:38 ideal
4:41 for you to get the actual insights that
4:43 will give benefit to what you are doing
4:46 and last always keep it simple this is
4:48 for the sake of understanding of your stakeholders
4:49 stakeholders
4:51 and other team members so that they can contribute
4:52 contribute
4:55 more on what you are to be so these are
4:56 the steps
4:57 that you might want to consider when