Harbarian process modeling (HPM) is a method for obtaining internal process information from an organization and then documenting that information in a visually effective, simple manner.
The HPM method involves two levels: Process diagrams: High-level overviews of specific processes or workflows. Systems diagrams: Mapping how each process is correlated, as well as various inputs, outputs, goals, feedback loops, and external factors.
HPM method purpose
The primary purpose of the HPM method is to first elicit process information from all relevant stakeholders and subsequently document existing processes completed within an organization. This method addresses the problem of workplace inefficiency, which can largely be attributed to the majority of processes being undocumented and informally completed.
The formal documentation of processes offers to replace ambiguity and uncertainty with clarity and transparency for the work being completed, both for process stakeholders and for upper management. The development of formal documentation also provides the opportunity to reassess process efficacy. Stakeholders will be given the chance to offer their innate insight into process strengths, weaknesses, and redundancies.
HPM output
The final output of the HPM method is the formalized master documentation of an organization's or branch's workflows and processes. This collection is divided into specific process series, each for a specific group or team. Each process series is divided into the team's major workflows which are individually documented into HPM process diagrams. Each process series also includes an HPM systems diagram which shows the relationships and connections between the various processes, inputs, outputs, feedback loops, external environment, and system goals.
HPM process diagram
HPM process diagrams provide a high-level overview of a specific workflow or process completed by a business unit. These diagrams are not meant to provide detailed instructions on procedures or codes, but instead address all major steps, decisions, and evaluations that are included in a process. Once finalized, these documents can be used as a reference for anyone in the organization. For example: The process owners can utilize the diagrams to train new employees. Other groups can reference the diagrams for enhanced understanding and communication. Upper management can reference the diagrams for increased process transparency and decision-making.
HPM process diagrams can be customized to fit the specific needs of an organization, however, typically include: Process title Process phases Timeline (if applicable) Sequential process steps Legend/key
HPM system diagram
HPM system diagrams provide a holistic view of a set of process diagrams. The system focuses on the connections and relationships between various processes. These diagrams also address the system as a collection of: Inputs Transformations Outputs Goals Feedback External factors
HPM implementation
The HPM method implementation is completed in five main phases. Meetings with stakeholders from organizational teams are conducted to identify major processes, document each process in detail, and develop implementable solutions. Information is elicited from stakeholders and then formally documented into process flowchart diagrams and systems thinking diagrams for use within the organization: initial elicitation and collaboration, preliminary documentation, follow-up elicitation and collaboration, final documentation, and project package submission.
Initial elicitation and collaboration
The first phase of the HPM method involves scheduling and meeting with each major team that makes up an organization or branch. Meetings are then conducted in the form of an interview and followed a detailed protocol to establish the meeting purpose, convey expected benefits, and to elicit information about the respective team's processes.
Meetings begin with an explanation of the purpose, as well as a list of expected benefits to each team: Clarification should then be given to all questions posed by stakeholders to ensure buy-in from all members of the respective team.
Next, each team should provide a high-level overview of all of the major processes they complete on a regular basis. Each of these processes can then be discussed in detail. The chronological order of tasks for each process is elicited and inputs, outputs, operations, decision points, and evaluations are identified.