Those we engage in a discussion about a flowchart are people who know about the business process in question. They are being chosen because they are agents of the process - not because they are operators of a possible future system. Stakeholders might well also finish up operating a computer system as part of their regular business process work - but their role as user is incidental to their role as process agent. We therefore need to engage all those who can contribute to the design of a new business process in the flowcharting work - not just users. It is process agents who lay down requirements for a new business process - not users.
Systems have to be installed to enable the new process.
All in all this leaves the word delightfully vague - without any useful meaning of any kind. Discussing the myth, I must point out, gets me into considerable hot water with some vendors - but, despite that, they seem to tolerate my attacks on this particular sacred cow. There may be some cases where these conditions are met - but they appear to be remarkably rare. Rather than being minor or incidental such impact on the process is usually profound . Sometimes, the characteristics of business processes are inconsistent with the features of our target application.