Professional Documents
Culture Documents
Define Phase
What is a Process?
process (proses) n. A repetitive and systematic series of steps or activities where inputs are modified to achieve a value-added output
Examples of Processes
We go through processes everyday. Below are some examples of those processes. Can you think of other processes within your daily environment?
Injection molding Decanting solutions Filling vial/bottles Crushing ore Refining oil Turning screws Building custom homes Paving roads Changing a tire Recruiting staff Processing invoices Conducting research Opening accounts Reconciling accounts Filling out a timesheet Distributing mail Backing up files Issuing purchase orders
Process Maps
Process Maps are living documents and must be changed as the process is changed
They represent what is currently happening, not what you think is happening. They should be created by the people who are closest to the process
Process Map
Start
Step A
Step B
Step C
Step D
Finish
A CIRCLE WITH A LETTER OR NUMBER INSIDE symbolizes the continuation of a flowchart to another page
One of the deliverables from the Define Phase is a high level Process Map, which at a minimum must include:
Start and stop points All process steps All decision points Directional flow Value categories as defined below
Value Added: Physically transforms the thing going through the process Must be done right the first time Meaningful from the customers perspective (is the customer willing to pay for it?) Value Enabling: Satisfies requirements of non-paying external stakeholders (government regulations) Non-Value Added Everything else
B
REVIEW CASE TOOL HISTORY & TAKE NOTES
Z
LOGOFF PHONE, CHECK MAIL,E-MAIL,VOICE MAIL
C
SCHEDULED PHONE TIME?
E
SCHEDULED PHONE TIME? TRANSFER APPROPRIATE?
Y A
Y N
LOGON TO PHONE IMMEDIATE RESPONSE AVAILABLE?
TRANSFER CALL
N
EXAMINE NEXT NOTE OR RESEARCH ITEM
PHONE TIME
Y
CALL or WALK-IN?
N Z
WALK-IN N
PUT ON HOLD, REFER TO REFERENCES
CALL
PHONE DATA CAPTURE BEGINS
IF EMP DATA NOT POPULATED, ENTER CREATE A CASE INCL CASE TYPE DATE/TIME, & NEEDED BY
ANSWER?
OLD CASE
N
QUERY INTERNAL HRSC SME(S)
Y
UPDATE ENTRIES INCL OPEN DATE/TIME
AUTO ROUTE
ROUTE
ANSWER?
Y
CASE CLOSED ADD TO RESEARCH LIST
N Y
CLOSE CASE W/ DATE/TIME
N
CASE TOOL RECORD?
N C
Y B
N
TAKE ACTION or DO RESEARCH
GO TO F or E DEPENDING ON CASE
E
NEXT
Cross Functional Process Map When multiple departments or functional groups are involved in a complex process it is often useful to use cross functional Process Maps.
Draw in either vertical or horizontal Swim Lanes and label the functional groups and draw the Process Map Sending Fund Transfers
Department
Start
Request transfer
Vendor
Produce an Invoice
No
Receive payment
End
Match against bank batch and daily cash batch
Financial Accounting
Yes
General Accounting
Bank
Exercise objective: Using your favorite Process Mapping tool create a Process Map of your project or functional area. 1. Create a high level Process Map, use enough detail to make it useful.
It is helpful to use rectangular post-its for process steps and square ones turned to a diamond for decision points.
2. Color code the value added (green) and non-value added (red) steps. 3. Be prepared to discuss this with your mentor.
10
Knowing your customer is more than just a handshake. It is necessary to clearly understand their needs. In Six Sigma we call this understanding the CTQ s or critical to customer characteristics.
11
Voice of the Customer or VOC seems obvious; after all, we all know what the customer wants. Or do we??
The customers perspective has to be foremost in the mind of the Six Sigma Belt throughout the project cycle.
1. Features
Does the process provide what the customers expect and need? How do you know?
2. Integrity
Is the relationship with the customer centered on trust? How do you know?
Does the process meet the customers time frame? How do you know?
3. Delivery 4. Expense
Does the customer perceive value for cost? How do you know?
12
What is a Customer?
There are different types of customers which dictates how we interact with them in the process. In order to identify customer and supplier requirements we must first define who the customers are:
External Direct: those who receive the output of your services, they generally are the source of your revenue Indirect: those who do not receive or pay for the output of your services but have a vested interest in what you do (government agencies) Internal - those within your organization who receive the output of your work
OSSS LSS Yellow Belt v10.0 - Define Phase
13
Value Chain
The relationship from one process to the next in an organization creates a Value Chain of suppliers and receivers of process outputs. Each process has a contribution and accountability to the next to satisfy the external customer. External customers needs and requirements are best met when all process owners work cooperatively in the Value Chain.
14
What is a CTQ?
Critical to Quality (CTQ s) are measures that we use to capture VOC properly. (also referred to in some literature as CTCs Critical to Customer) CTQ s can be vague and difficult to define.
The customer may identify a requirement that is difficult to measure directly so it will be necessary to break down what is meant by the customer into identifiable and measurable terms
Product: Performance Features Conformance Timeliness Reliability Serviceability Durability Aesthetics Reputation Completeness
Service: Competence Reliability Accuracy Timeliness Responsiveness Access Courtesy Communication Credibility Security Understanding
15
Open Source Six Sigma, LLC
Developing CTQs
Step 1
Step 2
Validate CTQ s Translate VOC to CTQs Prioritize the CTQs Set Specified Requirements Confirm CTQs with customer
Step 3
Capture VOC Review existing performance Determine gaps in what you need to know Select tools that provide data on gaps Collect data on the gaps
16
Open Source Six Sigma, LLC
As a Six Sigma Belt, one of your tasks will be to estimate COPQ for your process
Through your process exploration and project definition work you will develop a refined estimate of the COPQ in your project This project COPQ represents the financial opportunity of your teams improvement effort (VOB) Calculating COPQ is iterative and will change as you learn more about the process
17
COPQ helps us understand the financial impact of problems created by defects. COPQ is a symptom, not a defect
Projects fix defects with the intent of improving symptoms.
The concepts of traditional Quality Cost are the foundation for COPQ.
External, Internal, Prevention, Appraisal
A significant portion of COPQ from any defect comes from effects that are difficult to quantify and must be estimated.
18
COPQ - Categories
Internal COPQ
Quality Control Department Inspection Quarantined Inventory Etc External COPQ Warranty Customer Complaint Related Travel Customer Charge Back Costs Etc
Prevention
Error Proofing Devices Supplier Certification Design for Six Sigma Etc
19
COPQ - Iceberg
Inspection
Warranty Recode Rework
Rejects
Visible Costs
Lost sales
(less obvious)
Late delivery Expediting costs Excess inventory Long cycle times Excessive Material Orders/Planning
Hidden Costs
OSSS LSS Yellow Belt v10.0 - Define Phase
20