April 14, 2009 Jim Butler Julia Heany.  A process is a series of steps or actions performed to achieve a specific purpose.  A process can describe the.

Slides:



Advertisements
Similar presentations
CAUSE & EFFECT DIAGRAM (Fishbone or Ishikawa Diagram) Dr
Advertisements

Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
Plan-Do-Study-Act Cycle and QI Tool Refresher
Lean Six Sigma Green Belt Training
Algorithms An algorithm is a finite sequence of instructions, logic, an explicit step-by-step procedure for solving a problem. Specific algorithms sometimes.
Jim Butler QI Coach.  All improvements are a result of a change, But not all changes result in an improvement. Dr. Deming is purported to have said:
Project Title Livingston High School Department of Technology Education Innovation, Education and Design for the Future Team Members: Technology and Design.
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Chapter 2 - Problem Solving
ME 142 Engineering Computation I Fundamentals of Procedural Computer Programming.
Chapter 2 - Problem Solving
Workshop on Flowcharts Presented by: Larry Parker, BSMT (ASCP), MHSA, ASQ CQA American Society for Quality Central Arkansas Section 1407.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education 3-1.
Basics of Computer Programming Web Design Section 8-1.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education 3-1.
Steps of a Design Brief V Obtained from workshop-July, 2014-in Guildford County.
Action Logic Modelling Logic Models communicate a vision for an intervention as a solution to a public health nutrition (PHN) problem to:  funding agencies,
Chapter 2- Visual Basic Schneider
PRESENTED BY NASIR ABBAS. FLOW CHART CONTENTS What is a flow chart? Flow chart symbols.
Management Tools Problem Solving Chapter 17 Doug Winter, Christy Blew, Anh Le, Jennifer Stoltz.
The Program Design Phases
Fishbone (Ishikawa) Diagram Fishbone (Ishikawa) Diagram Purpose: to identify all of the possible factors that contribute to a problem, [also called the.
CONSTRUCTION OF A FLOW CHART DR OKUNOWO BOLANLE EDM UNIT.
Algorithm & Flowchart.
Fundamentals of C programming
Scott D. Duncan, MD, MHA, FAAP. Science of Safety We cannot improve quality and safety of healthcare until we view the everyday delivery of healthcare.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
YUSUF OZ FATIH BOLUKBAS HUSEYIN ANIL KARABULUT NETWORK AND BLOCK DIAGRAMS.
The Importance and Value of Process Improvement. Rationale for Process Improvement Establishing an attitude and culture of quality improvement and continuous.
WorkOut Method A3 for Facilitators What is a WorkOut? A methodology that helps teams identify opportunities to improve the way work gets done. Why are.
Quality Control Chapter 12- Management and Planning Tools
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
CQI (TQM) Tools and Time Management. CQI or TQM?? u CQI – Continuous Quality Improvement or u TQM – Total Quality Management Technically, there are some.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Detailed Process Mapping
Design the program Create a detailed description of program –Use charts or ordinary language (pseudocode) Identify algorithms needed –Algorithm: a step-by-step.
PROGRAMMING LANGUAGES Prof. Lani Cantonjos. PROGRAM - set of step-by-step instructions that tells or directs the computer what to do. PROGRAMMING LANGUAGE.
Steps of a Design Brief Panther Creek SciVis V
Project Title Pascack Hills High School Department of Technology Education STEM Concepts used to Design and Fabricate Inventions & Innovations Team Members:
Participate in a Team to Achieve Organizational Goal
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Activity diagrams. Introduction ● Activity diagrams are a behavioural model that represent the dynamics of the system. ● An activity diagram is essentially.
CORE 1: PROJECT MANAGEMENT Designing. This stage is where the actual solution is designed and built. This includes describing information processes and.
Flowcharting A Quality Improvement Tool. Quality = Inspection Statistical methods assisted in prevention of defects – The need for inspection declined.
Chapter 3 Systems Documentation Techniques Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 3-1.
Understanding Task Analysis
Interrelationship Digraphs
Program Design BUILDING A HOUSE. Steps to Designing a Program 1. Define the Output 2. Develop the logic to get that output 3. Write the program.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Livingston High School
Chapter 2 - VB 2005 by Schneider- modified by S. Jane '081 Chapter 2 - Problem Solving 2.1 Program Development Cycle 2.2 Programming Tools.
Flowcharts. Learning Objectives To learn how to break down tasks How to create a flowchart.
New 7 QC tools By Shuai Zhang Kun Wang.
FLOW CHARTS IN PROCESS DESCRIPTION FRANK CHINGARANDE.
Cause effect identification using Fishbone Diagram Powered by: Jazz PresentationJazz Presentation.
Presentation prepared by: Marilyn Shaw University of Northern IA This multimedia product and its contents are protected under copyright law. The following.
Steps of a Design Brief V Purpose of a Design Brief  A design brief is the process used to solve problems or complete presentations.  It is very.
Algorithms and Flowcharts
Learning outcomes 5 Developing Code – Using Flowcharts
Management & Planning Tools
7/14/16 CTC-RI IBH Pilot Quarterly Meeting
Programming Flowcharts
Activity Diagrams Activity diagrams describe the workflow behavior of a system.  The diagrams describe the state of activities by showing the sequence.
ME 142 Engineering Computation I
What you assess makes a statement about what you value
CAUSE AND EFFECT DIAGRAM
Systems Documentation
Introduction to Flowcharts
Presentation transcript:

April 14, 2009 Jim Butler Julia Heany

 A process is a series of steps or actions performed to achieve a specific purpose.  A process can describe the way things get done.  Your work involves many processes.

 A pictorial representation of the sequence of actions that comprise a process. Quality Learning Australia Pty Ltd 2006

 It provides an opportunity to learn about work that is being performed.  Dr. Myron Tribus said You don’t learn to flowchart, You flowchart to learn. Most processes today are undocumented.

 Document processes. ◦ Provide a reference to discuss how things get done. ◦ Describe and understand the work we do.  Analyze and improve on processes. ◦ Identify of areas of complexity and re-work. ◦ To generate ideas for improvement. ◦ Illustrate process improvements.

 Assemble the Team.  Agree on which process you wish to flowchart.  Agree on the purpose of the process.  Agree on beginning and ending points.  Agree on level of detail to be displayed.  Start by preparing a narrative outline of steps.  Identify other people who should be involved in the flowchart creation, or asked for input, or to review drafts as they are prepared.

 Start & End: An oval is used to show the materials, information or action (inputs) to start the process or to show the results at the end (output) of the process.  Activity: A box or rectangle is used to show a task or activity performed in the process. Although multiple arrows may come into each box, usually only one arrow leaves each box.  Decision: A diamond shows those points in the process where a yes/no question is being asked or a decision is required.  Break: A circle with either a letter or a number identifies a break in the Flowchart and is continued elsewhere on the same page or another page.

 Flowchart what is, not what you would like the process to be.  Flowcharting is dynamic. Use Post-it motes, dry erase markers, pencil, etc.  All flowcharts must have start and stop points.

 Flowchart the process that is used to obtain approval to attend conferences.

 Brainstorming and Affinity Diagrams can be used to identify processes you wish to flowchart.  There is no single right way to flowchart. It is a tool to learn about your organization and work.  Flowcharts can be used in a variety of settings outside Quality Improvement, such as: - Orienting new employees - In-service presentations - Brainstorming possible process changes - Creating or revising policies and procedures that support the process - Creating measures - Identifying logical outcomes of a process

 To identify underlying or root causes of a problem  To identify a target for your improvement that is likely to lead to change

 Construction ◦ Draw an arrow leading to a box that contains a statement of the problem ◦ Draw smaller arrows (bones) leading to the center line, and label these arrows with either major causal categories or process categories ◦ For each cause, identify deeper, root causes Cause 1 Effect/Problem Cause 2 Cause 3 Cause 4

 Find the right problem or effect statement ◦ The problem statement should reflect an outcome of a process that you control or influence ◦ Be specific ◦ Reach consensus  Find causes that make sense and that you can impact ◦ Generate categories through:  Brainstorming  Looking at your data ◦ Ask “why?” to achieve a deeper understanding ◦ Know when to stop  Stick to what you and your managers can control or directly influence  Make use of your results ◦ Decide if you need more data ◦ Consider causes that come up again and again, and causes that group members feel are particularly important