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 (
$cap 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 (
$f$
)

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 (
$cap 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.

Comments

Delivering a project within budget

Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process. Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...

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...

High-Tech Yuga

Search This Blog