Professional Documents
Culture Documents
Chapter 7
7-2
Systems Thinking
Definition of a “system”
– Whole > sum of parts
Application of systems thinking to businesses
– “Can’t sell from an empty wagon.”
– Defining systems boundaries
Role of “cross functional” teams in systems analysis
– Systems thinking requires cross-functional teams
to include all affected functions.
7-3
Process View of Business
7-4
Measuring Process Flows
Little’s Law
– Relates number of items in the system to arrival
rate and length of time in the system.
– Formula:
I=TxR
I = average number in the system
T = average throughput time
R = average flow rate into the process
Assumes system is in a ‘steady state’
7-5
Applications of Little’s Law
Manufacturing
Waiting lines
Invoice processing
Legal office transactions
Accounts receivable processing
Etc.
7-6
Measuring Process Flows
Capacity of a system = capacity of the most
constraining resource.
– This resource is called a ‘bottleneck.’
7-7
Flow-Process Chart Analysis
Purpose: to describe a process visually to find ways
of improving the current process.
– Find repetitive operations
– Identify bottlenecks
– Describe directions and distances of flows (people, material
and information)
– Reduce waste
7-9
Steps in process flowchart analysis
using the systems approach
1. Select a process to study
2. Form a team to analyze & improve the system
3. Decide on the objectives of the analysis
4. Define customers and suppliers
5. Flowchart the existing transformation process
6. Develop improved process design
7. Gain management approval of the improved design
8. Implement the new process design
7-10
Symbols for Flow-Process Chart
Operation (a task or work activity)
7-11
7-12
Questions to Ask in FPA
What does the customer need?, operations are necessary? Can some
operations be eliminated, combined, or simplified?….
Who is performing the job? Can the operation be redesigned to use less
skill or less labor? Can operations be combined to enrich jobs? ….
7-13
Information Flow Analysis
Purpose: to improve the efficiency and
effectiveness of the process.
7-14
Symbols for Information Processing Flow Chart
Origin of record (used to identify an operation that involves the addition
of significant data to a blank form)
Move (a step in which the record is transported from one person, department,
or work place to another)
Delay, file, and destroy (identifies a point or time at which the record is
inactive
7-15
Service Blue Printing
Flow charting of a service operation
Shows the ‘cycle of service.’
Points on SBP are “moments of truth”
Ask the same questions as in PFA (what, who,
where, when, and how)
7-16
Business Process Reengineering
(BPR)
BPR defined (Hammer and
Champy, 1993)
BPR Philosophy
Principles of BPR
Success of BPR
7-17
BPR Defined
BPR is “the fundamental rethinking
and radical redesign of business [or
organizational] processes to achieve
dramatic improvements in critical,
contemporary measures of
performance, such as cost, quality,
service and speed.”
7-18
BPR Defined
This is in contrast to incremental
change or continuous improvement of
an existing process.
“If I were recreating this company
today, given what I know and given
current technology, what would it look
like?”
7-19
BPR Philosophy
Does the reengineering consultant see the
glass as half full or half empty?
Neither.
It’s the wrong size of glass!
Or, should it be a glass? …or a liquid?
7-20
Principles of BPR
Organize around outcomes
Have the people who do the work, process
their own information
Put the decision point where work is
performed and build control into the process
Eliminate unnecessary steps in the process
7-21
The Success of BPR
According to Hammer & Champy, 50-70
percent of the organizations attempting BPR
do not achieve the results they expected.
Why?
Because they make one or more of the 17
common mistakes:
7-22
BPR Mistakes
Trying to fix a process instead of changing it
Not focusing on business processes
Focusing only on the process redesign
Neglecting people’s values & beliefs
Settling for minor results
Quitting too early
Constraining the scope of the problem & effort
Letting corporate culture & mgmt attitudes get in the way
Trying to reengineer from the bottom up
7-23
BPR Mistakes (cont.)
Assigning a leader who doesn’t understand BPR
Skimping on the resources
Not making BPR a top corporate priority
Trying to do too much at once & dissipating resources.
Concentrating only on design & not implementation.
Trying to keep everyone happy.
Pulling back if people resist.
Dragging out the effort & taking too long.
7-24
Summary
Systems Thinking
The Process View of Business
Measuring Process Flows
Flowchart Analysis
Materials-Flow Analysis
Information-Flow Analysis
Service Blue Printing
Business Process Reengineering (BPR)
7-25
End of Chapter Seven
7-26