What are the most common mistakes in setting task quality standards?
Quality standards are essential for any project, as they define the expected level of performance and satisfaction for each task. However, setting quality standards is not always easy, and many project managers make some common mistakes that can affect the project outcomes. In this article, we will discuss some of these mistakes and how to avoid them.
-
Hong Wai OnnChemical Engineer ∙ Author ∙ Public Speaker
-
Arun BagveLeadership | Reliance | Ex-Wipro | Ex-Honeywell | APM | MES| IP21 | Digital Twin | Project Management | Process…
-
Kumar Mhatre14 years successful & rewarding experience with chemical engineering applications for petrochemical & refinery units.
One of the most common mistakes in setting quality standards is not involving the stakeholders who will use, benefit from, or evaluate the project deliverables. Stakeholders have different needs, expectations, and preferences, and they can provide valuable feedback and insights on what constitutes quality for them. By not involving them, you risk setting unrealistic, irrelevant, or inconsistent quality standards that may not meet their requirements or satisfaction.
To avoid this mistake, you should identify and engage your key stakeholders from the start of the project, and communicate with them regularly throughout the project lifecycle. You should also seek their input and approval on the quality standards, and use tools such as surveys, interviews, focus groups, or workshops to gather their opinions and suggestions.
-
Arun Bagve
Leadership | Reliance | Ex-Wipro | Ex-Honeywell | APM | MES| IP21 | Digital Twin | Project Management | Process Simulation | Estimation and Sales Support | Six Sigma Green Belt | Unisim Design | Refinery | Polymer
Yes agree, Stakeholder engagement plan should be at place from start of the project. Which information need to be shared with whom based on aap-I matrix give clear picture of commutation protocol. All information sharing hierarchy at place from first day of the project.
-
Haseeb Jamal P.E.
Senior Manager (Projects and Operations) at Nayatel Pvt. Ltd
Not involving key stakeholders, including clients, end-users, or project sponsors, in the process of setting quality standards can result in misalignment with their expectations. It is imperative to engage relevant stakeholders early in the process to understand their quality expectations and incorporate their input into the standards.
-
Ahmed Awaad, Fellow CEng IntPE(NZ)/APEC
Subject Matter Expert
The common issues include not communicating with stakeholders at the right time or avoiding conversations with them due to a problem. This often happens because the project manager anticipates that the current progress and quality will not be accepted. For example, they might avoid stakeholders who are responsible for internal approval.
-
Sudhanshu T.
PROJECT MANAGEMENT PROFESSIONAL (PMI-PMP)
Ambiguity: Unclear and vague standards lead to different interpretations among team members, causing inconsistent outcomes. Rushing the Process: Hasty definition of standards may overlook crucial aspects, compromising overall quality. Unrealistic Expectations: Setting standards beyond achievable levels can demoralize the team and hinder productivity. Neglecting Stakeholder Input: Failing to involve key stakeholders results in incomplete understanding of requirements. Lack of Continuous Review: Overlooking regular review and adjustment leads to outdated standards that don't adapt to evolving project dynamics or industry best practices.
-
Hong Wai Onn
Chemical Engineer ∙ Author ∙ Public Speaker
Based on my experience, a prevalent error is neglecting to include pertinent stakeholders in the establishment of task quality standards. When key stakeholders are not consulted, there is a risk of overlooking their expectations and requirements, potentially resulting in misalignment and dissatisfaction with the final quality. While receiving numerous feedback and inputs may seem challenging, it is precisely intended to prevent potential disagreements about quality standards in later stages.
Another common mistake in setting quality standards is not aligning them with the project objectives and scope. Quality standards should reflect the purpose and goals of the project, and support the delivery of the desired outcomes and benefits. If the quality standards are not aligned with the project objectives, they may be too high or too low, or not relevant or measurable.
To avoid this mistake, you should define your project objectives and scope clearly and explicitly, and use them as the basis for setting your quality standards. You should also ensure that your quality standards are SMART: Specific, Measurable, Achievable, Relevant, and Time-bound. This will help you to monitor and control the quality of your project deliverables, and to evaluate their success and impact.
-
Hong Wai Onn
Chemical Engineer ∙ Author ∙ Public Speaker
In my experience, a common pitfall is the failure to synchronize quality standards with project objectives. Ensuring that the established standards directly contribute to the overarching project goals is paramount. Without this alignment, there's a risk of directing attention towards aspects of quality that might not be integral to attaining project success. To overcome this, I make it a point to regularly revisit and reassess the connection between quality standards and project objectives throughout the project lifecycle. This proactive approach ensures that our quality efforts remain purposeful and aligned with the evolving needs of the project.
A third common mistake in setting quality standards is not documenting them properly. Quality standards are part of the project quality plan, which is a document that describes how the project will ensure and maintain the quality of its processes and products. Without a documented quality plan, the quality standards may not be clear, consistent, or communicated to the project team and stakeholders. This can lead to confusion, misunderstanding, or disagreement on what constitutes quality, and how to achieve and verify it.
To avoid this mistake, you should document your quality standards in a formal and structured way, using templates, checklists, or guidelines. You should also include the criteria, methods, tools, and responsibilities for quality assurance and quality control, which are the processes of ensuring and checking the quality of your project deliverables. You should also review and update your quality plan as the project progresses, and share it with your project team and stakeholders.
-
Ahmed Awaad, Fellow CEng IntPE(NZ)/APEC
Subject Matter Expert
The most common issues identified from lessons learned about this part include not having enough resources or having resources in another country that lacks sufficient experience regarding the deliverables. Additionally, issues arise when the project discipline manager fails to communicate updates and client feedback on time or does not review the completed work before sharing it with the client to ensure it aligns with the deliverables and meets the required level of detail and quality. Having a qualified person to audit, coordinate, and close any scope gaps is key to success. Also, use tier-one companies to ensure the risk is reduced
-
Hong Wai Onn
Chemical Engineer ∙ Author ∙ Public Speaker
Neglecting to document quality standards is a common oversight. Clear documentation is essential for communication and reference. Without it, there's a higher risk of misunderstandings and inconsistencies in applying quality standards. To overcome this, I've implemented a structured documentation process in my projects, creating a centralized repository for easy access. This approach enhances communication and provides a consistent reference, reducing the likelihood of misinterpretation and inconsistency, contributing to smoother project execution.
A fourth common mistake in setting quality standards is not adapting them to changes that may occur during the project. Projects are dynamic and uncertain, and they may face changes in scope, schedule, budget, resources, risks, or stakeholder expectations. These changes may affect the quality standards, and require adjustments or revisions to ensure that they are still valid, relevant, and achievable.
To avoid this mistake, you should monitor and control the quality of your project deliverables, and identify and assess any changes that may impact the quality standards. You should also use change management processes and tools to evaluate, approve, and implement any changes to the quality standards, and communicate them to the project team and stakeholders. You should also document the changes and their reasons, and update your quality plan accordingly.
-
Hong Wai Onn
Chemical Engineer ∙ Author ∙ Public Speaker
It's crucial for quality standards to be adaptable, allowing them to accommodate shifts and updates that occur throughout the project lifecycle. To address this, I proactively assess and update quality standards in response to any modifications in project parameters. This ensures that the standards remain pertinent and aligned with the evolving needs of the project. Additionally, I prioritize timely communication of these changes to the relevant stakeholders to maintain transparency and collective understanding. This way, the team can adjust their focus and efforts in accordance with the updated quality standards, fostering a more agile and responsive project environment.
A fifth common mistake in setting quality standards is not learning from the quality issues that may arise during or after the project. Quality issues are any deviations, defects, or failures that do not meet the quality standards, and that may affect the performance or satisfaction of the project deliverables. Quality issues can be a source of learning and improvement, and help you to identify and address the root causes, and prevent or reduce their recurrence.
To avoid this mistake, you should track and record the quality issues, and analyze and report on their causes, effects, and solutions. You should also use lessons learned processes and tools to capture and share the knowledge and best practices that emerge from the quality issues, and to apply them to your current or future projects. You should also celebrate and reward the successes and achievements that result from meeting or exceeding the quality standards, and recognize and appreciate the efforts and contributions of your project team and stakeholders.
-
Vahe Avetisyan
International Project Management Consultant
A very important point - "Lessons Learned". This is a dynamic list with items coming in and going out. Try to keep new items as few as possible (done a good job) and eliminate as many items as possible from the list (learned from the previous issues and they are not happening anymore). I call this exercise "using previous experience". Record not only major issues but also small ones. This will help keep track of everything.
-
Haseeb Jamal P.E.
Senior Manager (Projects and Operations) at Nayatel Pvt. Ltd
Treating quality standards as static and not incorporating opportunities for continuous improvement can hinder the evolution of processes and best practices. So we should regularly review and update quality standards based on feedback, lessons learned, and changing project requirements. Encourage a culture of continuous improvement.
-
Wai Han Ho
💊Clinical Research 💊Project Delivery 💊Maximizing potential
A common response to quality issues being noted is to perform retraining. It is worth examining how retraining will improve the quality and close the gap.
-
Hong Wai Onn
Chemical Engineer ∙ Author ∙ Public Speaker
Neglecting to draw lessons from quality issues represents a substantial oversight. Whenever quality issues surface, it becomes imperative to delve into comprehensive assessments aimed at unraveling the root causes. Implementing corrective actions based on these assessments is critical for rectifying immediate concerns and preventing recurrence. Overlooking the opportunity to leverage these experiences for continuous improvement can lead to a repetitive cycle of mistakes, ultimately jeopardizing the quality of tasks. Embracing a culture of continuous improvement involves not only resolving issues as they arise but also extracting valuable insights to fortify future processes and enhance overall task quality.
-
Kumar Mhatre
14 years successful & rewarding experience with chemical engineering applications for petrochemical & refinery units.
In my experience, sometime over commitment & too stringent deadlines leads to detriotion of quality. Organizational standards and quality procedures were not followed properly due to over pressure of task completion. Overall it leads to bad task managment and exwcution.
-
Nello P. Lopez
International Project Manager and Consultant. Investing on skills, experience, and attributes through philanthropreneurship. Matches best fit and talented freelance professionals ensuring highest quality results.
When setting task quality standards, several common mistakes that people make: Not understanding the process from beginning to end; this can lead to making the wrong decisions and not being able to identify areas for improvement. Not involving the right people. It’s important to involve people who have a good understanding of the process and can provide valuable insights. Not having a clear definition of what constitutes quality; this can lead to confusion and inconsistency in the standards. Not measuring the right things; to ensure that the standards are effective. Not having a system in place to monitor and improve the standards; this can lead to the standards becoming outdated and ineffective over time.
-
Krystn Orr
Project Management | Accessibility, Inclusion, and Equity Advocate | Consultant
For many projects, quantitative standards are the only standards set. However, qualitative data is often more informative and valuable to the people involved in the project - staff, volunteers, end-users.
-
Vahe Avetisyan
International Project Management Consultant
What is the most important - Quality or Delivery date? Different project team members will answer differently - Project Controls or QC Manager? This is a real challenge for the PM and the entire project team to maintain high-quality standards and keep the delivery date.
Rate this article
More relevant reading
-
Project ManagementHow do you tell clients and end users about project quality?
-
Management ConsultingWhat do you do if project deliverables are not meeting quality standards?
-
Employee RelationsHere's how you can guarantee project deliverables meet the required quality standards.
-
Quality AssuranceHow can you improve your quality plan and design based on project feedback?