Skip to main content

Lean Six Sigma Process

Everything! Any activity, process or procedure that transforms a number of input (s) into a number of output (s).


VOP = Voice of Process
VOB = Voice of Business
VOC = Voice of Customer

Non-Value-Added/  Value-Added Analysis (NVAA)



Example 1: Processing a lab test 
This example focuses on the process of taking a blood sample and generating a lab report. 

Inputs (
Xcap X
) 
These are the resources and information required to perform the process. 
  • Patient information: Demographics, medical history, and specific test orders from the physician.
  • Physical resources: Sterile syringes, needles, collection tubes, labeling materials, and the lab's analytical equipment.
  • Personnel: Trained phlebotomists to draw the blood, lab technicians to analyze the sample, and pathologists to verify the results.
  • Procedures: Standard operating procedures (SOPs) for blood collection, handling, analysis, and quality control. 
Process (
ff
) 
This is the series of steps that transforms the inputs into the desired output. 
  • Patient registration and sample collection: Patient arrives, verifies their identity, and a blood sample is drawn.
  • Sample preparation: The blood sample is labeled correctly and prepared for transport to the lab.
  • Analysis: The lab technician uses specialized equipment to perform the required tests on the blood sample.
  • Result interpretation: A qualified pathologist reviews the results, noting any abnormalities.
  • Report generation: The final report is compiled and delivered to the requesting physician and patient. 
Outputs (
Ycap Y
) 
This is the product or service delivered by the process. 
  • Accurate lab report: A document containing the patient's test results, verified by a pathologist.
  • Timely delivery: The report is provided within the expected turnaround time.
  • Patient satisfaction: The patient has a positive experience during the collection process and receives their results in a timely manner. 

Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more