Process means different things to different people. When groups of people used to working with certain types of processes view other areas they think and act in their own image.
What do I mean?
Well, transactional process i.e. people dealing with high volume high replication activity, model measure and simulate. Data is key and they use it on occasions to the the extreme using methods like six sigma to measure slight variations in variability to eliminate defects and produce highly repeatable consistent processes.
Whilst processes in the professional area, where the activity is nearly always different in one way or another, are viewed by transactional people as "Are these really processes?" and they often try to codify the variability much to the frustration of the users who rapidly get turned off.
The theme with professional processes is that there are scenarios around a standard theme or best practice approach. Process mapping and improvement is no less valuable than "paper factory" processes; it is just different.
Learning to see and to communicate how best to do things doesn't mean necessarily turning a professional job into a production line.
The message here is appropriateness e.g.use the right approaches and tools don't impose your views or experience on areas that just happen to be different - business and process architecture is not a black and white game.
Forcing inappropriate methods on to people never reaches a satisfactory outcome.