Improving business processes (20%) Flashcards
Where can problems with processes arise?
The current process may have problems with:
Flow through the process
Individual tasks that make up the process
Staffing performance issues
Business rules that constrain the process
Possible Process Flow Problems
Many hand-offs
Hand-offs create delay and may cause errors
Value Time Percentage
Real work on the process goal is often a small percentage of the elapsed time
Queues, Bottlenecks
Resource and timing issues, workload fluctuations
Looping
Unnecessary looping – e.g. error checking late, rather than early
Sequential tasks
Many processes merely replicate ‘manual’ systems, historic customs
IS/IT problems
Lack of integration, legacy systems, re-keying, paper intensive
Possible Process Flow Solutions
Hand-offs
Reduce the number of departments/teams/actors involved. Simplify, re-skill, change authority levels.
Value Time Percentage
Investigate where ‘dead time’ can be reduced, flow improved
Queues, Bottlenecks
Plan appropriate resources to deal with queues and bottlenecks
Critical Path Analysis can help identify where the problems are
Looping
Can we eliminate the loops – does the process need to go ‘backwards’?
Sequential tasks
Re-sequence tasks; could tasks be done in parallel?
IS/IT
Modify applications to promote integration (consider alternatives first, v expensive)
How can processes be affected by staff?
Staff are poorly or incorrectly trained
Inadequate, poor supervision (too much/not enough)
Lack of leadership by management
Low morale, poor motivation, lack of incentives
Too much change can lead to loss of morale
Measuring the wrong things – engenders inappropriate behaviour
People tend to be behave according to how they are measured
How can processes be affected by Business Rules?
Processes are often constrained by business rules
It’s often worth challenging these rules
Where does the rule come from?
Is the rule still relevant?
Could the rule be relaxed?
What would happen if we didn’t apply the rule?
Real Value Add
Tasks that contribute to customer requirements
Business Value Add
Tasks that do not contribute to customer requirements but contribute to business need
No Value Add
Tasks that do not contribute to customer requirements or business needs
Typical NVAs
Copying /Storing / Rework / Searching / Counting
What technique can be apply to NVAs
5 whys - identify root cause and look at eliminating it
The Seven Wastes
Transportation
Inventory
Motion
Overproduction
Over processing
Defects
Skills
How could we analysis tasks for potential improvements
Non-Value Adding (NVA) Tasks
Could they be reduced or eliminated completely?
Redundant Tasks
Work not needed! Historic or legacy tasks e.g. reports, storage, filing
Duplication
Effort duplicated e.g. in data capture
Measurement
Wrong/useless things being measured – affects effort and behaviour!
Governance
Inappropriate decision rights, control points, redundant business rules…
Cycle time vs Value time
Cycle Time: the total elapsed time from the initial request for goods or services (input) to the eventual delivery of those goods or services (output)
Value Time: the amount of time spent doing ‘useful work’, work of direct value to the process customer
Value time percentage
(Value Time ÷ Cycle Time) * 100
usually v low
How can scenario analysis be used to improve business processes?
Think through real world scenarios and identify gaps in our processes