Successful process mapping: business process definition
What is a process?
In this post, we will answer this first question. Why is this question important?
Why this question is important
You need to define processes for your organisation, or you will spend time and money revising your process maps. Without a clear understanding of processes in your organisation, you cannot monitor them, which in turn affects the overall performance of your business.
To understand process mapping better, we need to define a process first.
A process is a series of steps taken to achieve an outcome.Â For example:
- Recruitment (could be one process, or it could beÂ several processes)
- Payroll (could overlap between HR and Finance)
- Purchasing (could be one big process, with up to 20 smaller processes)
You can classify processes based on their function, namely:
- Technical processes (engineering or technical industry-related processes, e.g., water purification)
- Business processes (organisational processes, e.g., purchasing)
- System processes (computer or system-specific processes, e.g., backup)
Usual elements of a process
Elements are useful components of a process. Processes have:
- Multiple inputs and outputs
- A boundary (a start and an end)
- An owner (whoâ€™s responsible for managing the process)
- A supplier (who provides the input)
- A customer (who receives the final output)
- Roles (who carry out tasks)
- Time / event triggers (what starts the process)
- Metrics (performance indicators or KPIs)
- Resources (e.g., equipment)
In the next post we will look at types of processes.
Useful resource: Â http://www.bptrends.com/surveys_landing.cfm