mjflkitty said:
Example of service they release is server scan. before it used to take hours to scan our server, now it takes 15mins. Meaning they are responsible for enhancing and developing new services. Like what I said they develop and release different services, so I was asking them if for them customer satisfaction comes before quality. They said because the effectiveness of their process lies after releasing the service like "server scan". I was telling them that they should be able to claim that their service is working during beta/dry run testing, but they said not all of their service is undergoing that process. But in their process map it states that it should undergo. Am i not right in telling them that quality must come after customer satisfaction. And i still have to ask them why 3 months?Corrct me if' i'm wrong, and please bear with me.
- Why does their process map not match what they actually do? If there is more than one process flow path, then why are all options not indicated?
- If the "plan" is to slowly move all processes to what is documented on the process map, where is the plan/timeline showing their planned progress versus actual progress?
Questions I as you mjflkitty are:
- Why do you believe that quality must come after customer satisfaction? I mean, I'm trying to understand what you believe is the "flow" of ISO requirements, but I'm not doing a very good job at it.
- Looking back at the original question, you asked if an organization should say a product is of good quality before handing it over to the Customer. Are you talking about final inspection?
