2.1.2 Process Mapping, SIPOC, Value Stream Map

Process Mapping, SIPOC, Value Stream Map Introduction Process Mapping, SIPOC, and Value Stream Mapping are core techniques for understanding, analyzing, and improving processes. They convert complex work into visual representations that reveal: - What actually happens - Where value is created - Where waste, delays, and defects arise This article explains these tools in a focused, practical way so you can confidently apply them to real processes and improvement projects. --- Foundations of Process Visualization Why Visualize Processes Visual tools convert verbal descriptions into shared understanding. They help to: - Clarify boundaries of a process - Expose rework, delays, and handoffs - Align people on “current state” - Prioritize what to improve For advanced problem solving, the key is to use the right level of detail: - High-level view: SIPOC and top-level process maps - Detailed flow: swimlane maps, deployment maps - Flow and waste view: value stream maps (VSM) --- SIPOC Purpose of SIPOC A SIPOC diagram is a high-level view of a process from supplier to customer. SIPOC stands for: - Suppliers - Inputs - Process - Outputs - Customers It is used to: - Define the scope of a process - Align on what is inside vs. outside the process - Identify key inputs and outputs - Connect process steps to customer requirements Structure of a SIPOC A SIPOC is normally presented in 5 columns: - Suppliers: Entities that provide inputs to the process - Inputs: Materials, information, or triggers entering the process - Process: 4–7 high-level steps that describe the transformation - Outputs: Products, services, or information produced - Customers: Internal or external recipients of the outputs Key discipline: Keep the Process column at a macro level, usually using verbs: - Receive order - Verify information - Fulfill request - Confirm completion How to Build a SIPOC Steps to construct a workable SIPOC: - Define process boundaries - Determine the start event (first trigger) - Determine the end event (final outcome) - List outputs first - What leaves the process? - Include both desired and undesired outputs (e.g., defects, rework requests) - Identify customers - Who receives or uses each output? - List inputs - What is required for the process to operate? - Include critical information, materials, systems, and forms - Identify suppliers - Who provides each input? Practical tips: - Limit process steps to a small number to keep it high-level - Use simple, action-based step names - Separate “nice to have” details from critical inputs and outputs Using SIPOC for Analysis Once the SIPOC is built, it can be used to: - Check whether all key customers are recognized - Identify which inputs are likely to be critical to quality - Clarify which suppliers may influence defects or variation - Highlight missing or unclear requirements for outputs Common analytical questions: - Are there any outputs with no clear customer? - Are there inputs with unclear or multiple suppliers? - Are process steps vague or overlapping? - Are there outputs that customers do not value? --- Process Mapping Purpose of Process Mapping Process maps provide a more detailed view than SIPOC. They show how work actually flows, step by step, including: - Activities - Decisions - Handoffs - Rework loops Process maps are essential for: - Describing the current state objectively - Locating bottlenecks, delays, and rework - Designing improved future-state processes Levels of Detail Common levels of process mapping depth: - High-level map (also called a macro map) - 4–10 major steps - Good for overview and communication - Detailed map - Many steps, including decision points and rework - Good for identifying improvement opportunities - Swimlane / deployment map - Steps grouped by function or role - Highlights handoffs and communication points In practice, start with a high-level map and only move to more detailed maps as needed. Standard Process Map Symbols Standard symbols keep maps clear and consistent: - Terminator (rounded rectangle) - Start or end of process - Process step (rectangle) - Activity or task performed - Decision (diamond) - Question where flow splits based on yes/no or other conditions - Document (single wavy-bottom rectangle) - A document is created or used - Connector (small circle or labeled connector) - Jumps or links in the flow - Flow arrow - Direction of movement from step to step Maintain consistent notation within one map to avoid confusion. How to Create a Process Map A structured approach: - Define the purpose and scope - Why are you mapping? - Where does the process start and end? - Identify the main steps - Brainstorm key steps without worrying about order - Then place them in logical sequence - Sequence with decisions - Identify where decisions split the flow - Validate with people who do the work - Check accuracy and completeness - Add detail where useful - Rework loops - Handoffs between functions - Waiting points Tips for effective maps: - Use clear, action-based labels (e.g., “Review application,” not “Application review”) - Avoid jumping to idealized steps; map what actually happens - When the flow is complex, consider a swimlane format Swimlane and Deployment Maps Swimlane or deployment maps categorize steps by who performs them or by where they occur. Typical “lanes” could be: - Departments - Systems - Locations - Teams These maps are particularly powerful for exposing: - Excessive handoffs - Communication failures - Responsibilities that are unclear or overlapping Key questions to ask with swimlane maps: - How many times does work cross boundaries? - Are there steps with no clear owner? - Are there loops between the same two lanes? Using Process Maps for Analysis Once the map is created, it becomes a tool for identifying issues: - Look for rework loops - Steps where work returns to earlier steps - Look for delays and queues - Places where work waits for approvals or data - Look for complex decision points - Multiple branches that may create confusion or variation - Look for non-value-added activities - Redundant checks, unnecessary movements, excessive approvals Common analytical techniques include: - Mark each step as value-added, required non-value-added, or pure waste - Count the number of handoffs and decisions - Identify steps where defects frequently appear --- Value Stream Mapping Purpose of Value Stream Mapping A Value Stream Map (VSM) extends beyond process steps to show how value and information flow through an entire value stream. It makes visible: - Material or work-in-progress movement - Information flow (orders, schedules, signals) - Process times and waiting times - Inventory and work-in-progress levels The focus is on the end-to-end flow from initial request to delivery, viewing it as a complete system. Key Concepts in Value Stream Mapping Essential VSM elements: - Value stream - The complete set of actions (value-adding and non-value-adding) required to bring a product or service from request to delivery - Current state map - Representation of how the value stream operates today - Future state map - Desired improved flow after changes are made - Lead time - Total elapsed time from start to finish, including waiting - Process time - Time actually spent working on the item - Work-in-progress (WIP) - Number of items in process but not yet completed - Information flow - How instructions and data move between steps Structure of a Value Stream Map A typical VSM includes: - Customer box - Demand rate, requirements, frequency of orders - Supplier box - Delivery frequency, batch size, method - Process boxes - Each major operation or step, with: - Cycle time (C/T) - Changeover time (C/O) if relevant - Uptime or availability - Number of operators (if applicable) - Batch size - Inventory or WIP triangles - Number of items waiting between processes - Material flow arrows - Direction and type of physical flow - Information flow lines - How scheduling and instructions travel (e.g., manual, system, pull signals) - Timeline at the bottom - Lead time and value-added time to show the ratio of work vs. waiting Data Collection for Value Stream Mapping Accurate VSM depends on real data. Typical measures include: - Cycle time - Time required to complete one unit or transaction at a process step - Changeover / setup time - Time to switch from one type of work to another - Uptime / availability - Percentage of scheduled time the process is actually running - Yield - Proportion of units passing through a step without rework - Inventory / WIP - Count of items waiting or in process between steps - Queue / waiting time - Time items spend waiting before each process Data is often collected through: - Direct observation - Time studies - System data extraction Creating a Current State Value Stream Map A structured method: - Define the value stream - Start and end points (from specific customer request to delivery) - Map the process flow - Identify major process blocks (not extreme detail) - Add data to process blocks - Typical cycle time, uptime, batch size, yield - Add inventory and waiting - WIP counts or inventory days between processes - Map information flow - Who sends orders, how schedules are set, how signals move - Build the timeline - Sum value-added time and total lead time Key interpretation questions: - Where is most of the lead time? - Which steps have high WIP or long waits? - Where is there mismatch between information flow and material flow? - How much of the total lead time is value-added? Designing a Future State Value Stream Map A future state VSM represents the desired improved flow. When designing it, consider: - Flow improvement - Can steps be linked to reduce queues? - Can batch sizes be reduced? - Pull vs. push - Where can downstream demand trigger upstream work? - Leveling and synchronization - Can processing be balanced to reduce bottlenecks? - Quality at the source - Where can defects be prevented rather than detected later? - Information simplification - Can information flows be simplified or automated? Typical changes shown in a future state map: - Reduced WIP at key points - More direct flows with fewer detours - Shorter changeovers to enable smaller batches - Clearer pull signals between steps - Pull or continuous flow in segments of the stream The future state map becomes a roadmap for improvement actions. Each gap between current and future state points to specific projects or changes. --- Integrating SIPOC, Process Mapping, and VSM How the Tools Relate These tools are complementary and often used in sequence: - SIPOC - Defines scope, inputs, outputs, and customers - Sets a high-level boundary for detailed analysis - Process Mapping - Describes the detailed flow within that scope - Reveals rework, handoffs, and complexity - Value Stream Mapping - Looks at end-to-end flow and performance - Integrates time, inventory, and information flow A practical progression: - Start with SIPOC to clarify what is in scope and who is affected. - Build a process map to understand how work is currently done. - Develop a value stream map to understand how well value and information flow across the entire stream. Typical Analytical Questions by Tool - SIPOC - Are we clear on where the process starts and ends? - Are all key suppliers, inputs, outputs, and customers identified? - Which inputs and outputs might be critical for performance? - Process map - Where do we see rework, loops, and repeated steps? - Where are the main handoffs, and are they necessary? - Which steps appear to add no value? - Value stream map - What fraction of lead time is actual processing vs. waiting? - Where does WIP accumulate? - Where does information flow fail or cause delays? --- Common Pitfalls and Good Practices Common Pitfalls - Mapping the ideal, not the real - Describing how the process is supposed to work instead of how it actually works - Too much detail too early - Overloading the map with minor steps and exceptions - Unclear boundaries - No agreement on where the process starts and ends - Ignoring information flow - Omitting approvals, data transfers, and instructions - Not validating with process participants - Failing to check accuracy with people who perform the work Good Practices - Use real data - Base maps and VSMs on observation and factual measures - Keep symbols simple and consistent - Prioritize clarity over graphic complexity - Engage those who do the work - They are the best source of reality and detail - Iterate - Refine maps as understanding deepens and new data emerges - Link to improvement goals - Use maps to answer specific performance questions, not as ends in themselves --- Summary Process Mapping, SIPOC, and Value Stream Mapping are complementary tools for understanding and improving processes: - SIPOC clarifies boundaries, key inputs and outputs, and the connection between suppliers, process, and customers. - Process maps describe the detailed sequence of activities, decisions, and handoffs, exposing rework, delays, and waste. - Value Stream Maps show how value and information flow across the entire value stream, quantifying process time, waiting, and work-in-progress. Using these tools in combination provides a structured way to: - Define what is in scope - Understand how work is truly performed - Reveal where and how to improve flow, reduce waste, and enhance performance Mastering these techniques allows you to turn complex, messy real-world processes into clear visual models that directly guide effective improvement actions.