APPENDIX E: PROCESS MAPPING BASICS

define the purpose of the processa nd communicate why it exists what is your objective?

define the scope for each process; how will you know when you are done? what iss uccess?

make note of the core activities within with a processo r function wouldf ail establish the logical order of activities to ensure process success visually represent and test your work-flow

Process: An organized group of interrelated activities that work together to achieve specific, discrete outputs that are of value to a customer, user group, or other key stakeholders.

Activity: An activity is a unit of work performed by one accountable function – often one at a time and in sequence. Activities consume resources and result in a work product/deliverable/artifact.

Task: A task is a step performed to complete an activity. Several work steps may be required to complete an activity. In other words, a task is the lowest logical work unit within a process.

Process Map:

A visual representation of a sequence of interactions between supporting activities and tasks.

It identifies what and who is involved in completing each necessary step; and provides an end-to-end perspective of all work being performed.

Beyond identifying which processes to design and visually represent, here are some key considerations:

• Define and communicate the purpose of the process. Why does it exist? What does it do for us?

• Establish an immersive narrative. Start from the end and describe what our future state looks and feels like.

• Define the following:

• Process Owner

• Interfaces

• Inputs and Outputs

• Metrics

• Test your process. Ask “what if?” and “so what?” and establish or eliminate redundancy, recursion or verification points.