discussion papers

	Process Mapping – 5 tips for better process maps
	Maximising the business benefit from your quality management systems
	The hidden costs of pretend processes
	Keep it simple, stupid, says visiting consultant
	Comparison - managed v static processes
	Do you need process management?
	Automation vs Change
	How does Promapp add value?
	Positive process culture
	Process Management vs Document Management

Do you need process management?

There is not a structured approach to creating and storing process information.
Each project captures process information in its own way, there is no consistency .
Capture process information in a central repository, rather than in various ad-hoc locations on the network.
There is over dependence on a few key staff.
Key staff members hold a lot of process information. If they leave process knowledge may be significantly eroded.
Mitigate against loss of knowledge – treat process knowledge as an asset. Create a central information asset that will grow over time, rather than erode.
For each process breakdown there is a separate assessment of who needs to be involved.
There is no clear big picture of key processes, stakeholders, and how they interconnect .
It takes time to figure out which process stakeholders need to be involved in changes, who needs to be notified, and what other processes may be affected.
Processes are not visible.
There is not a consistent understanding of how processes are performed.
Whether it's day-to-day small enhancements or a companywide transformation, a clear understanding of current processes is needed before they can be improved.
Key processes are not owned
Ongoing improvement of processes is inhibited without process ownership and responsibility. Remove this barrier, assign ownership and make staff accountable.