Process Management and Process Oriented Improvement Programs: Chapter 2

Process Management and Process Oriented Improvement Programs: Chapter 2

اسلاید 1: 1Process Management and Process Oriented Improvement ProgramsChapter 2Business Process Modeling, Simulation and Design

اسلاید 2: 2OverviewProcess Management and the Power of Adopting a Process viewSix SigmaDefinitionsCost and revenue rationaleFrameworkKey success factorsBusiness Process ReengineeringWhat is it?Brief historyWhat processes should be reengineered, and when?Suggested frameworksEvolutionary vs. Revolutionary Change

اسلاید 3: 3Process ManagementPrinciples of managing, controlling and improving processesWorkflow oriented  how jobs flow through an organizationImportant elements in managing processesProcess designContinuous (incremental) improvementControl systemsPeople managementChange managementOrigins in the field of quality managementProcess control is a fundamental componentHistorically strong manufacturing focusEqually valuable in services

اسلاید 4: 4The Power of Adopting a Process ViewWeaknesses of the functional org. and division of labor paradigmFocus on skills and resource utilization rather than work outputReward systems tailored for the functional unit not the overall firmGroup behavior and cultures fostering an “us versus them” mentalityDecentralization  “firms within the firm” with their own agendaStrengths of a process viewCreates focus on work output  reduced risk for sub-optimizationLeads to transparency of how contributions of individual workers fit into the “big picture”  encourages involvement and empowermentHelps break down barriers between departmentsCreates a sense of loyalty towards the process to balance the loyalties within the functional units

اسلاید 5: 5Principles for Successful Process ManagementAssign process ownershipPerform feedback & controlDevelop & implement measuresEstablish control pointsDefine the processPhase I: InitializationPhase II: DefinitionPhase III: ControlProcess authority, scope, interfaces and handoffs are determinedWorkflow documentationBaseline for process evaluation is definedMeans and procedures for process monitoring, feedback and control are establishedAnalyze boundaries & interfaces

اسلاید 6: 6Phase I: InitializationObjective:Clarify the process scopeDetermine who will take responsibility for the processProcess ownershipNeed someone in charge to make things happenResponsibilities of a process ownerAccountability and authority for process operations and improvementsFacilitate problem solving and make sure corrective action is takenMediate between line managers with overlapping authoritiesGuidelines for assigning process ownershipManager with most resources or most work invested in the processManager that is most affected if the process failsProcess owner must have high enough position to see how the process fits into the “big picture”, needs clout to solve functional bickering

اسلاید 7: 7Phase I: InitializationAnalyzing Process Boundaries and InterfacesProcess Boundary defines the process entry and exit points where inputs flow in and outputs flow outProvides a clear picture of the process scopeDefines the external interfacesInternal interfacesHand-off points within the process boundariesMost critical where the process crosses functional or organizational bordersMost process inefficiencies are related to insufficient interface communication (= lack of coordination)Important to identify critical interfaces early on

اسلاید 8: 8The Customer-Producer-Supplier (CPS) modelUseful approach for resolving interface related problemsApplying the CPS model to all critical interfaces  adopt a view of the process as a chain of customersCoordination achieved by understanding internal & external customersInvolves negotiation and agreement between all partsProducerPROCESSCustomerSupplierInputOutputCustomer RequirementsProducer RequirementsOutput InterfaceInput Interface

اسلاید 9: 9Phase II: DefinitionObjective:Understand and document the process workflowFacilitate communication and understanding of process operationsDefine the processDocumentation of work content in individual activitiesUsually in terms of verbal descriptionsOperating procedures or Standard Operating Procedures (SOP)Documentation of process flowsUsually a flowchart based method Combination of verbal and graphical descriptionCommon information gathering techniquesInterviews with people working in the process (group or individual)Analytical observationReview of relevant documentation

اسلاید 10: 10Phase III: Control (I)Objective:Establish a system for controlling the process and providing feedback to the people involvedEstablish Control PointsControl points are activities such asInspection, verification, auditing, measuring, counting…Usually considered business value addingWithout control points and a control system the only way of assessing process performance is customer feedbackThe process ends up in a reactive modePoor quality is discovered too lateLocation of control points is determined by Criticality – impact on customer satisfactionFeasibility – physically and economically possible

اسلاید 11: 11Phase III: Control (II)Develop and Implement MeasurementsInvolves answering the questionsWhat is to be measured and controlled (Ex. FedEx)?What is currently measured (available data)?Can a business case be made for a new measurement system?What is the appropriate sampling method, sampling size and frequency?Measurements should be meaningful, accurate and timelyStatistical and graphical tools needed to turn data into information.Five measurement categories: Measures of… Conformance (to given specifications)Response time (lead-time, cycle time)Service levels (degree of availability)Repetition (frequency of recurring events such as rework)Cost (Quality, PAF, internal and external failure costs)

اسلاید 12: 12Phase III: Control (III)Performing Feedback and ControlOf critical importance for stabilizing and improving the processObjectives of control/corrective action areRegulation to maintain a certain performance levelImprovement aiming at reducing variability or raising the average performance levelFeedback is an important enabler for corrective actionPeople in the process need to understand how their actions affect the overall process and its performanceFeedback should be performed in a constructive – not punitive – mannerConstructive feedback Makes people feel that they matterEncourages involvement and commitment

اسلاید 13: 13Six Sigma Quality ProgramsSix Sigma is originally a company wide initiative at Motorola for breakthrough improvement in quality and productivityLaunched in 1987Rendered Motorola the Malcom Baldridge National Quality Award 1988The ongoing success of Six Sigma programs has attracted a growing number of prestigious firms to adopt the approach Ex. Ford, GE, AMEX, Honeywell, Nokia, Phillips, Samsung, J.P. Morgan, Maytag, Dupont…Broad definition of Six Sigma programs“A company wide strategic initiative for process improvement in both manufacturing and service organizations with the clear objective of reducing costs and increasing revenues”Fierce focus on bottom line results

اسلاید 14: 14Technical Definition of Six SigmaReduce the variation of every individual process to render no more than 3.4 defects per million opportunitiesAssuming the process output is normally distributed with mean  and standard deviation  the distance between the target value and the closest specification limit is at least 6  and the process mean is allowed to drift at most 1.5  from the targetTarget Value (T)Upper Specification Limit (USL)Lower Specification Limit (LSL)

اسلاید 15: 15The Six Sigma Cost or Efficiency RationaleReducing costs by increasing process efficiency has an immediate effect on the bottom line To assure worker involvement Six Sigma strives to avoid layoffsCommitmentReduced CostsIncreased ProfitsImprovement projectsCycle TimeYieldVariationThe Six Sigma Efficiency loop

اسلاید 16: 16Oriented around the dimensions of variation, cycle time & yieldVariationCan be divided into two main typesCommon cause or random variationSpecial cause or non-random variationNon-random variation Relatively few identifiable root causesFirst step in reducing the overall variation is to eliminate non-random variation by removing its root causesRandom variationThe result of many different causesInherent in the process and can only be affected by changing the process designThe Six Sigma Cost or Efficiency Rationale

اسلاید 17: 17Variation (cont.)Important concepts in understanding the impact of variationDispersionPredictabilityCentering Dispersion Magnitude of variation in the measured process characteristics.PredictabilityDo the measured process characteristics belong to the same probability distribution over time?For a predictable process the dispersion refers to the width of the pdf.CenteringHow well the process mean is aligned with the process target value.The Six Sigma Cost or Efficiency Rationale

اسلاید 18: 18Variation (cont.)Ideally the process should be predictable, with low dispersion, and well centeredStandard approach for reducing variability in Six Sigma programsEliminate special cause variation to reduce overall dispersion and improve predictabilityReduce dispersion of the predictable processCenter the process to the specified targetSix Sigma use traditional tools for quality and process control/analysisBasic statistical tools for data analysisThe 7 QC toolsThe Six Sigma Cost or Efficiency Rationale

اسلاید 19: 19Cycle time and YieldCycle time (lead-time, response time)The time a job spends in the processYield (productivity)Amount of output per unit of input or per unit timeImprovement in cycle time and yield follow the same tactic as for variationGain predictability, reduce dispersion and center to targetThe target is usually broadly defined asMinimize cycle time and Maximize yieldSix Sigma principleImprovement in average cycle time and yield should not be made at the expense of increased variationThe Six Sigma Cost or Efficiency Rationale

اسلاید 20: 20Determinants of the company’s revenuesSales volume closely related to market shareSales pricesRevenues contingent on how well the firm can satisfy the external customers’ desiresAn important Six Sigma Success factor is the focus on internal and external customer requirements in every single improvement projectThe Six Sigma Revenue or Effectiveness Rationale

اسلاید 21: 21The Six Sigma Cost & Revenue RationaleCommitmentReduced CostsIncreased ProfitsImprovement projectsCycle TimeYieldVariationCustomer satisfactionIncreased Market Share & potentially higher pricesIncreased Revenues

اسلاید 22: 22Centered around a disciplined and quantitatively oriented improvement methodology (DMAIC)Define, Measure, Analyze, Improve, ControlThe Six Sigma FrameworkDefineMeasureAnalyzeImproveControlTop Management CommitmentTraining Improvement MethodologyMeasurement SystemStakeholder Involvement

اسلاید 23: 23The bottom line focus and big dollar impactEncourages and maintains top management commitmentThe emphasis on - and consistent use of - a unified and quantitative approach to process improvementThe DMAIC methodology provides a common language so that experiences and successes can be shared through the organizationCreates awareness that decisions should be based on factual dataThe emphasis on understanding & satisfying customer needsCreates focus on doing the right things rightAnecdotal information is replaced by factual dataThe combination of the right projects, the right people and the right toolsCareful selection of projects and people combined with hands on training in using statistical tools in real projectsSix Sigma Success Factors

اسلاید 24: 24Introduction to ReengineeringBusiness Process Reengineering (BPR) One of the buzzwords of the late 80’s and early 90’s“…achieves drastic improvements by completely redesigning core business processes”BPR has been the subject of numerous articles and books; classical examples are:“Reengineering Work: Don’t Automate, Obliterate”, Michael Hammer, Harvard Business Review, 1990“The New Industrial Engineering”, Davenport and Short, Sloan Management Review, 1990

اسلاید 25: 25BPR Success Stories and FailuresSuccess StoriesFord cuts payable headcount by 75%Mutual Benefit Life improves underwriting efficiency by 40%Xerox redesigns its order fulfillment process and improves service levels by 75-97% and cycle times by 70% with inventory savings of $500 millionDetroit Edison reduces payment cycles for work orders by 80% FailuresAn estimated 50-70% of all reengineering projects have failedThose that succeed take a long time to implement and realize

اسلاید 26: 26Lack of support from senior managementPoor understanding of the organization and the infrastructureInability to deliver necessary technologyLack of guidance, motivation and focusFixing a process instead of changing itNeglecting people’s values and beliefsWillingness to settle for marginal resultsQuitting too earlyAllowing existing corporate cultures and mgmt attitudes to prevent redesignNot assigning enough resourcesWorking on too many projects at the same timeTrying to change processes without making anyone unhappyPulling back when people resist changeEtc…Reasons for BPR Failures

اسلاید 27: 27What does it take to succeed with BPR?Hammer and Champy“The role of senior management is crucial.”Empirical research indicates… organizations which display understanding, commitment and strong executive leadership are more likely to succeed with process reengineering projects.Common themes in successful reengineering effortsFirms use BPR to grow business rather than retrenchFirms emphasize serving customers & compete aggressively with quantity & quality of products & servicesFirms emphasize getting more customers, more work and more revenues instead of downsizing

اسلاید 28: 28Reengineering and its Relationships to Other Improvement Programs (I)Reengineering - what is that?“The fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical, contemporary measures of performance such as cost, quality, service and speed” (Hammer and Champy 1993)A number of similar definitions by other authors also existReengineering characteristicsFocus on core competencies or value adding business processesThe goal is to achieve dramatic improvement through rapid and radical redesign and implementationProjects that yield only marginal improvement and drag out over time are failures from a reengineering perspective

اسلاید 29: 29Reengineering and its Relationships to Other Improvement Programs (II)RightsizingRestructuringAutomationTQMReengineeringAssumptionsStaffingReportingTechnologyCustomer FundamentalquestionedrelationshipsapplicationsneedsFocus ofStaffing, jobOrganizationSystemsBottom-upRadicalchangeresponsibilitiesimprovementschangesOrientationFunctionalFunctionalProceduresProcessesProcessesRole of ITOften blamedOccasionallyTo speed upIncidentalKeyemphasizedexisting systemsImprovementUsuallyUsuallyIncrementalIncrementalDramatic andgoalsincrementalincrementalsignificantFrequencyUsually oneUsuallyPeriodicContinuousUsually onetimeone timetime

اسلاید 30: 30Relationship between Discontinuous (Radical) and Continuous ImprovementImprovementTimeIncrementalImprovementRadicalImprovementTheoreticalCapabilityStatisticalProcessControl

اسلاید 31: 31Brief History of BPR (I)Most agree that Michael Hammer laid the foundation to the reengineering approach……But many factors influenced the birth and hype around BPRThe origins can be traced back to a number of successful projects undertaken by management consulting firms like McKinsey in the 80’sTQM had brought the notion of process improvement onto the management agendaThe recession and globalization in late 1980’s and early 1990’s stimulated companies to seek new ways to improve business performancePrograms often aimed at increasing flexibility and responsivenessMiddle management under particular pressure

اسلاید 32: 32Brief History of BPR (II)Articles and books by Hammer, Davenport, Short, Champy etc. legitimized and defined the reengineering approachEarly success stories were heavily published in the popular pressMany consultants/vendors launched their own versions of BPRAll types of change programs were labeled reengineering Gave BPR a bad name…But many factors influenced the birth and hype around BPRThe Productivity Paradox (Stephen Roach)Despite powerful market and service innovations related to IT and increased computer power in the 1980’s there was little evidence that IT investments improved overall productivityOrganizations were not able to utilize the capabilities of the new technology – Automating inefficient processes has limited impact on productivity

اسلاید 33: 33Three forces are driving companies towards redesign (The three C’s, Hammer & Champy, 1993)Customers are becoming increasingly more demandingCompetitionhas intensified and is harder to predictChangein technology constant pressure to improve; design new products fasterflexibility and ability to change fast are requirements for survivalWhen Should a Process be Reengineered? (I)

اسلاید 34: 34Useful questions to ask (Cross et al. (1994))Are customers demanding more for less?Are your competitors providing more for less?Can you hand-carry a job through the process much faster than the normal cycle time (ex five times faster)?Have your incremental improvement efforts been stalled?Have technology investments been a disappointment?Are you planning to introduce radically new products/services or to serve new markets?Are you in danger of becoming unprofitable?Have cost-cutting programs failed to turn the ship around?Are operations being merged or consolidated?Are the core business processes fragmented?When Should a Process be Reengineered? (II)

اسلاید 35: 35Processes (not organizations) are reengineeredConfusion arises because organizational units are well defined, processes are often not.Formal processes are prime candidates for reengineeringFormal processes are guided by written policies; informal processes are not.Typically involve several departments and many employees.More likely rigid and therefore more likely to be based on invalid assumptions.What Should be Reengineered? (I)

اسلاید 36: 36Screening criteriaDysfunctionWhich processes are in deepest trouble (most broken or inefficient)?2.ImportanceWhich processes have the greatest impact on the company’s customers?3.FeasibilityWhich processes are currently most likely to be successfully reengineered?What Should be Reengineered? (II)

اسلاید 37: 37Symptoms and diseases of broken processesDysfunctional or Broken ProcessesSymptomDisease1Extensive information Arbitrary fragmentation exchange, data redundancyof a natural processand re-keying2Inventory, buffers and System slack to cope with other assets uncertainty3High ratio of checking andFragmentationcontrol to value-adding4Rework and (re)iterationInadequate feedback along chains5Complexity, exceptions Accretion onto a simple baseand special cases

اسلاید 38: 38Assessed by determining issues the customers feel strongly about and identifying which processes most influence these issuesImportanceCustomer IssuesProduct CostOn-time DeliveryProduct FeaturesAfter-sales serviceMarketProcessesProduct DesignOrder ProcessingProcurementCRMCompany

اسلاید 39: 39Determined by: Process Scope, Project Cost, Owner Commitment and the Strength of the Redesign TeamLarger projects offer potentially higher payoffs but lesser likelihood of successFeasibilityProcessFeasibilityProcess ScopeProject CostTeam StrengthOwner/Corp.Commitment

اسلاید 40: 40The process paradox refers to the decline and failure of businesses that have achieved dramatic improvements through process reengineeringTo avoid getting caught in the process paradox companies must “Get the right processes right”The Process Paradox

اسلاید 41: 41Suggested Framework for BPR (I)In general, keywords for successful BPR are creativity and innovation……but BPR projects also need structure and discipline, preferably achieved by following a well thought-out approach.BPR Framework due to Roberts (1994)Starts with a gap analysis and ends with a transition to continuous improvement.The gap analysis focuses on three questions:The way things should beThe way things areHow to reconcile the gap between 1 and 2

اسلاید 42: 42Robert’s Framework for BPROpportunityassessmentCurrent capabilityanalysisProcess DesignRisk and impactassessmentTransition planPilot testInfrastructuremodificationsImplementationand transitionTracking andperformanceContinuous improvementprocess

اسلاید 43: 43BPR Framework due to Lowenthal (1994)Consists of 4 phasesPreparing for change3.Designing for changePlanning for change4.Evaluating changePhase 1 – Goals Building management understanding, awareness and support for changePreparing for a cultural shift and acquire employee “buy-in”Phase 2 – Assumption Organizations need to adopt to constantly changing marketplaces Phase 3 - MethodTo identify, assess, map and design A framework for translating process knowledge into leaps of changePhase 4 – MeansEvaluate performance during a specified time frameSuggested Framework for BPR (II)

اسلاید 44: 44Lowenthal’s Framework for BPRPreparing forchangePlanning forchangeDesigningchangeEvaluatingchangePhase IPhase IIPhase IIIPhase IV

اسلاید 45: 45BPR Framework due to Cross, Feather&Lynch (1994)AnalysisIn depth understanding of market and customer requirementsDetailed understanding of how things are currently doneWhere are the strengths and weaknesses compared to the competition2.DesignBased on principles that fall into six categoriesService Quality – relates to customer contactsWorkflow – managing the flow of jobsWorkspace – ergonomic factors and layout optionsContinuous improvement – self sustainingWorkforce – people are integral to business processesInformation technologyImplementationTransforming the design into day to day operationsSuggested Framework for BPR (III)

اسلاید 46: 46Cross et al’s Framework for BPR CustomerRequirement analysisDesignspecificationsHigh-level designDetailed designPilot newdesignTransform the businessBaselineanalysisCurrent process reviewDesign optionsModel/validatenew designBuild in CIfeedbackDesignprinciplesAnalysisPhaseDesignPhaseImplementationPhase

اسلاید 47: 47The reengineering movement advocates radical redesign and rapid revolutionary implementation and changeA revolutionary change tacticTurns the whole organization on its headHas potential to achieve order of magnitude improvementsIs very costlyHas a high risk of failureTo reduce risks and costs of implementation many companies end up with a strategy of radical redesign and evolutionary implementation tacticImplementing the feasible plans given current restrictionsImplemented process is usually a compromise between the original process and the “ideal” blueprinted process designRevolutionary vs. Evolutionary Change

اسلاید 48: 48The critical element in choosing between a revolutionary and evolutionary approach is timeIf the firm is in a reactive mode responding to a crisis  a revolutionary approach may be the only optionIf in a proactive mode  an evolutionary tactic might workRevolutionary vs. Evolutionary ChangeElements of evolutionary and revolutionary change theories

اسلاید 49: 49Basic principle People directly affected by or involved in a change process must take active part in the design and implementation of that changeReal change is achieved through incremental improvement over timeChange should come from within the current organizationShould be carried out by current employees and leadershipShould be adapted to existing resources and capabilities  flexible milestonesShould be based on open and broad communicationNew processes and procedures are implemented before introducing new IT systemsThe Evolutionary Change Model (I)

اسلاید 50: 50Advantages of an evolutionary change tactic compared to a revolutionary approach Less disruptive and riskyIncreases the organizations ability to changeDisadvantagesTakes a long time to see resultsDoes not offer the same potential for order of magnitude improvementsVision must be kept alive and adjusted over time as external market conditions changeThe Evolutionary Change Model (II)

اسلاید 51: 51Based on the punctuated equilibrium paradigmRadical change occurring at certain instancesLong periods of incremental change in betweenRevolutionary changeHappens quicklyAlters the very foundation of the business and its cultureBrings disorder, uncertainty, and identity crisesNeeds to be top drivenRequires external resources and new perspectivesInvolves tough decisions, cost cutting and conflict resolutionThe change team is small and isolated from the rest of the organizationAvoid undue influence from current operationsCommunication with people in the process is on a “need to know” basisThe Revolutionary Change Model (I)

اسلاید 52: 52Advantages with a revolutionary implementation approachDrastic results can be achieved quicklyIf successful, the ideal “blueprinted” design is put in placeDisadvantages with a revolutionary change tacticVery strenuous for the organizationHigh probability for failureDiverts top management attention from the external marketplaceGoes against core values of many organizationsEmpowermentBottom-up involvementInnovationSecrecy creates uncertainty about the future roles of individual employees  resistance to changeThe Revolutionary Change Model (II)