What is quality [PM Course discussion]

Various definitions of the concept of quality have been put forward.

One generic definition (Pass, 2006b) is as follows:

The overall characteristics of a product or service that fulfill the requirements of customers in terms of quality.

This definition aligns with the viewpoint of Joseph Juran, who, in the 1950s, defined quality as ‘fitness for use’ (as quoted in ASQ, 2019).

This definition is largely consistent with the definition of quality provided by APM (2019, p. 214):

The suitability for the intended purpose and the degree to which the output of a process or the process itself conforms to the requirements.

Now take a moment to consider the following statements about quality. Which ones do you agree with?

  1. Quality should prioritize the customer’s needs.
  2. Quality is an internal focus.
  3. Quality should be considered from the project’s inception.
  4. The execution phase of a project is crucial for achieving quality goals.
  5. Quality issues should be openly discussed to identify corrective actions.
  6. Quality problems should be concealed from customers and possibly managers.
  7. Individuals are enthusiastic about producing high-quality outcomes.
  8. Team members do not produce quality outputs without close supervision.

Share your thoughts on these statements in the discussion section below.

What is quality [PM Course discussion]

2,156 thoughts on “What is quality [PM Course discussion]

  1. Reflecting on the statements about quality, I agree with the following:

    1. Quality should be focused on the customer’s needs. This aligns with the definition of quality as “fitness for use” and ensures that the project deliverables meet the customer’s requirements.

    2. Quality should be considered from the beginning of the project. This proactive approach helps identify potential quality issues early on and prevents costly rework downstream.

    3. Quality issues should be discussed openly to find corrective actions. Transparency and open communication are essential for addressing quality problems and implementing effective solutions.

    I disagree with the following statements:

    1. Quality is focused internally. While internal processes are important, quality should ultimately be focused on meeting the customer’s needs.

    2. The execution phase of a project is the most critical to achieve quality targets. While execution is crucial, quality considerations should be integrated throughout the project lifecycle, from initiation to closure.

    3. Quality problems should be hidden from customers and possibly also managers. This approach can damage trust and reputations, and is not conducive to a culture of transparency and continuous improvement.

    4. Team members do not produce quality outputs without close supervision. While supervision is important, it’s also essential to empower team members to take ownership of their work and strive for quality excellence.

  2. Here are my reflections:

    Agree:

    1. Quality should be focused on the customer’s needs. (Customer satisfaction is key!)
    2. Quality should be considered from the beginning of the project. (Proactive approach to quality)
    3. Quality issues should be discussed openly to find corrective actions. (Transparency and open communication)
    4. People are keen on producing quality outputs. (Intrinsic motivation to deliver quality work)

    Disagree:

    1. Quality is focused internally. Quality should be customer-centric
    2. The execution phase of a project is the most critical to achieve quality targets. Quality should be considered throughout the project lifecycle
    3. Quality problems should be hidden from customers and possibly also managers. Transparency and honesty are essential
    4. Team members do not produce quality outputs without close supervision. Team members should be empowered to take ownership of their work

  3. Here are my reflections on the statements about quality:

    Quality should be focused on the customer’s needs.
    I strongly agree. Quality is ultimately determined by how well a product or service meets customer expectations and requirements, aligning with the “fitness for use” principle by Joseph Juran.

    Quality is focused internally.
    I partially agree. While internal processes (e.g., adherence to standards and procedures) are crucial for quality, they should always align with delivering value to the customer. Focusing solely internally can miss the mark on external expectations.

    Quality should be considered from the beginning of the project.
    Absolutely agree. Building quality into the planning and design phases helps prevent defects and rework later, saving time and resources.

    The execution phase of a project is the most critical to achieve quality targets.
    I somewhat agree. While the execution phase is vital for applying quality control measures, achieving quality targets depends on work done in all phases, including planning and monitoring.

    Quality issues should be discussed openly to find corrective actions.
    Strongly agree. Transparency fosters problem-solving, collaboration, and trust, ensuring timely resolution and continuous improvement.

    Quality problems should be hidden from customers and possibly also managers.
    Strongly disagree. Concealing quality issues undermines trust and accountability and can lead to larger problems if unaddressed. Honest communication is essential for maintaining relationships and resolving issues effectively.

    People are keen on producing quality outputs.
    I agree but cautiously. While most people strive for quality, organizational culture, training, and resources significantly influence their ability and motivation to achieve it.

    Team members do not produce quality outputs without close supervision.
    I disagree. Effective teams with proper training, clear expectations, and empowerment can consistently produce quality work without constant oversight.

  4. My thoughts on the below :

    “Quality should prioritize the customer’s needs”

    Hence the project in question is targeted forwards some group of people for purchase, consumption , ultimately the service or goods being produced MUST have elements that defines it as fit for use.
    Customer responds positively to good with quality as a result of there satisfaction from the usage of such product .

    Quality is an internal focus.
    In a volatile circumstance what is tagged “fit for use ” where the end users is generically not part of the project team quality cannot be said to be for internal focus .
    When feedbacks returns to the project teams, the response is basically that things have to be done the other way round, adjust has to be done in certain areas of the project to actualize the maximum quality embodied in the outputs .Volatile circumstances in a project entails the offshoots of economic , socia-political dynamics which are external factors battling against the plan for the project. So to ensure quality maintenance and control , project manager has to discard idea of making quality an internal and focus on how the customer view quality .

    “Quality should be considered from the project’s inception.”

    At planing stage and as a project manager in the making, the process of achieving this vision should be spelt out.It may take some minimal shift , but the original from inception by considering and documenting quality from the beginning will serve as a compass to direction the entire project cycle.

    “The execution phase of a project is crucial for achieving quality goals.”

    The execution stage of a project is important but not as crucial as the inception stage.Why?
    You can not give birth to what you have not conceive. The visionary and the planing stage of the entire project life cycle help the project manager to have a broader and wholistic stance in excepting and achieving quality in the output.
    The execution is when the output in the project become tangible but the inception stage sets the bedrock for actualizing this!.

  5. I agree with the statement that quality should be focused on the customer’s needs because ultimately, the customer determines what is considered quality. I also believe quality should be considered from the beginning of the project; addressing quality early ensures that the project stays on track and meets expectations.

    The idea that quality is focused internally doesn’t resonate with me. While internal processes matter, quality should always align with external customer expectations. I also don’t agree that the execution phase is the most critical; I think quality needs attention throughout the project lifecycle, from planning to delivery.

    Quality issues should definitely be discussed openly—transparency allows for better problem-solving and improvements. On the other hand, hiding quality problems from customers and managers is not acceptable. It only creates bigger issues down the line.

    As for people producing quality outputs, I believe they are motivated to do so when they have the right tools, training, and environment. However, I don’t agree with the idea that team members need constant supervision to produce quality outputs. Trusting the team and providing the right support tends to yield better results.

  6. In my opinion, I support that quality should be considered from project’s inception because the reputation of organization is tied to the quality of their products.
    At the same time I support that although organisations reputation is vital in regards to the quality of their products, it is also important to consider how customers relates to the product. Hence, meeting customers needs is equally vital as to building organisational reputation.
    I will therefore define quality as the final product of an organisational process that meet its objective and builds its reputation as well satisfy the need of the end users (customers).
    Also, it is important and crucial to consider quality at the execution phase of a project because the durability of a product in the market is a function of its quality to the general public.
    Thank you for the opportunity granted to me in this program of projects management.

  7. 1. Quality should absolutely be focused on the customer’s needs:Customer-centric quality ensures that the product or service meets or exceeds customer expectations. Aligning quality with customer needs drives satisfaction, loyalty, and long-term success.

    2. I agree that quality should be considered from the beginning of the project as quality must be integrated from the planning phase to prevent costly rework, delays, or defects later.
    3. Quality issues should be discussed openly to find corrective actions because transparency is vital for improvement.

    4. Quality problems should be hidden from customers and possibly also managers: Hiding quality issues is counterproductive. It undermines trust, damages credibility, and can lead to larger problems. Instead, issues should be addressed openly and resolved promptly.
    5. People are keen on producing quality outputs: depending on the environment, a supportive environment with clear expectations, resources, and motivation, most people strive to produce quality work. Empowerment and recognition further enhance this drive.
    Conclusion

    A customer-centric, transparent, and proactive approach to quality is critical. Organizations should balance external and internal perspectives, empower teams, and emphasize open communication to create a sustainable quality culture.

  8. Here are my thoughts on the statements:

    Quality should be focused on the customer’s needs: Strongly agree. Meeting customer needs is the essence of quality.

    Quality is focused internally: Partially agree. Internal processes support quality, but the ultimate focus is external.

    Quality should be considered from the beginning of the project: Absolutely agree. Early planning prevents issues later.

    The execution phase is the most critical to achieve quality targets: Disagree. Quality is built throughout the project lifecycle.

    Quality issues should be discussed openly: Agree, open discussions lead to timely solutions and trust.

    Quality problems should be hidden: Disagree, transparency is key to problem-solving and maintaining trust.

    People are keen on producing quality outputs: Agree as most take pride in their work if supported properly.

    Team members don’t produce quality without close supervision: Disagree, empowerment and trust yield better results than micromanagement.

    To sum it up,
    Quality requires early focus, open communication, and a balance of processes to meet customer needs.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top