Process Mapping Basics: How to Create a Process Map

How to Effectively Process Map Your Business

Introduction to Process Mapping

• The speaker emphasizes the importance of process mapping for building business systems, stating it is a crucial skill.

• They introduce a simple approach to process mapping using basic symbols on a whiteboard or paper.

Key Symbols in Process Mapping

• Action Box: Represents observable actions that occur within the process.

• Decision Diamond: Indicates decision points where multiple paths can be taken, connected by arrows showing flow direction.

• Start/Stop Oval: Marks the beginning and end of the process; useful for defining boundaries when space is limited.

• Predefined Process Folder: Acts as a container for complex steps (e.g., quality assurance), allowing for easier reference without cluttering the main map.

Determining What to Map

• The speaker suggests starting with a Process Org Chart, which helps identify all business functions holistically before systemizing them one by one.

• For those not working with their team, they recommend focusing on areas that are both valuable and problematic—identifying pain points that hinder delegation or efficiency.

Selecting Scope and Detail Level

• Once an area is chosen, define its scope by determining clear start and stop points. An example given is mapping from booking a call to project creation.

• The distance between these two points will guide how detailed the mapping should be, aiming for measurable and delegatable actions rather than minute breakdowns.

Example of Actionable Steps

• Each step in the process should represent discrete actions manageable within one work session (20 to 90 minutes).

Sales and Onboarding Process Mapping

Introduction to Process Mapping

• The speaker introduces the concept of combining sales and onboarding into a single process flow, emphasizing the importance of clarity in mapping out steps.

• The focus is on capturing actions without getting bogged down by details about who performs them or what technology is used; this allows for a cleaner initial map.

Steps in the Process

• The first action identified is "book call," which serves as the starting point. The next step involves determining what happens after this action.

• A confirmation email follows the booking, but again, specifics about who sends it are not included at this stage to maintain simplicity.

Handling Delays

• Discussion on how to represent delays in process mapping; rather than complicating with symbols, consider if a delay adds value to the process.

• If a delay does not contribute actively (e.g., waiting for a call), it may be omitted from the map altogether.

Decision Points

• After completing the call, a decision point arises: determining if the client is a good fit. This question guides subsequent actions based on yes/no responses.

• It’s important that all paths from decision points are mutually exclusive, ensuring clarity in outcomes.

Finalizing and Reviewing the Map

• Once initial mapping is complete, checks are performed to ensure all steps connect logically from start to finish and that decision points have clear paths labeled.

• The speaker emphasizes embracing some chaos during physical mapping sessions while ensuring all necessary steps are captured accurately.

Quality Checks

• A thorough review of each step ensures no actions or client interactions are overlooked; adjustments can be made as needed.

Process Mapping: Key Steps and Insights

Importance of Noting Double Click Areas

• The speaker emphasizes the need to document "double click areas" during process mapping, which are moments that require further exploration or detail.

• A suggestion is made to prioritize these areas based on their pain points and value for future process mapping efforts.

Defining Major Actions in Process Mapping

• After capturing the initial process map, it's important to label it clearly (e.g., "sales to onboarding") to define major actions involved.

• The speaker encourages repeating this exercise across various business functions to ensure comprehensive understanding and documentation.

Filling Gaps in Process Understanding

• The self-directed approach allows individuals to fill in pieces of their processes, with the understanding that some gaps may be identified later during collaborative work.

• This step is crucial as it helps define what the business does before moving on to understand why those processes exist.

Transitioning from What to Why and Who

• Once the "what" is established, attention shifts to identifying "who" is responsible for each action within the defined processes.

• Recognizing who manages these tasks ensures accountability and clarity within the organization.

Tactical Implementation: When and How

• The next step involves determining "when" specific actions occur, which aids in reducing cognitive load on team members by providing clear timelines for tasks.

• Finally, defining "how" tasks should be executed involves creating instructions or templates that guide team members without overloading them with details.

Handoff Point for Responsibility

Understanding the Role of "Who" in Process Ownership

Defining the "Who"

• The "who" refers to the assigned owner responsible for creating Standard Operating Procedures (SOPs), instructions, and templates. Their role is crucial in ensuring processes are documented effectively.

• If the assigned owner is inexperienced, it becomes essential to educate them thoroughly on each task they need to perform, providing them with all necessary information.

Knowledge Transfer and Application

• When knowledgeable team members are involved, they can independently manage processes without needing further guidance from leadership.

• In cases where a new process arises that no one understands (e.g., new financial regulations), external resources such as consultants or online materials can be utilized to provide necessary knowledge.

Addressing Potential Errors

• Concerns may arise about whether the assigned owner will execute tasks correctly. It's acknowledged that mistakes may happen initially but are part of a learning cycle.

• This cyclical process involves continuous feedback where errors lead to adjustments in instructions and intervals for future tasks.

Continuous Improvement Cycle

• Empowering team members like Johnny allows for ownership of their work while ensuring they receive ongoing input regarding metrics and feedback on performance.

• A consistent flow of information is vital for improving processes over time, making it measurable through established systems.

Visibility into Processes