> you are talking about means, I am talking about ends. You see, these things are not necessarily separate, but many people fail to understand that. Continuing

> you are talking about means, I am talking about ends. You see, these things are not necessarily separate, but many people fail to understand that. Continuing shopping analogy, imagine shop sells some candies in multiple flavors. Do you need to weigh them separately when customer takes multiple flavors? The process requires you to weigh them separately. Nothing wrong will happen if you don't. Although, eventually managers will resupply you with a single flavor. > but we need to make sure the user knows these reasons and sees why they are not a hindrance in completing the task but part of the completed task. So what's the task at hand? Is it to simply sell candies to customer or maybe keep shop operational, properly stocked and then sell candies? For the shopkeeper the process may seem to start at customer entry and end at customer paying. For the shop that is just part of a grander process. It seems to me that you argue for single-person scoped processes to be treated as standalone and microoptimized, regardless of how that fits into master process. I try to argue that it is the master process you have to care about.