← Back to the blog

Blog

Quality Culture in IT Projects: Learn Early

ISO 9001:2026 was published on 16 September. Alongside leadership and clearer risk management, the new edition explicitly emphasizes quality culture. For IT projects, this is more than a quality-management topic. It determines how early a project detects and processes bad news.

A recent article from the GPM Quality and Projects expert group identifies four causes behind errors: lack of awareness, lack of skill, deliberate non-compliance, and refusal to accept responsibility. For governance this distinction is useful, because not every defect calls for the same response.

An error pattern needs a governance response

Many software projects measure quality primarily by the number of open defects. That figure alone does not explain why problems arise or why they come back.

  • Lack of awareness: Requirements, risks, or dependencies were not visible. Provide better information and review earlier.
  • Lack of skill: Knowledge or experience is missing. Close the gap with training, pairing, or targeted expert support.
  • Deliberate non-compliance: Schedule or cost pressure rewards shortcuts. The steering committee must correct priorities and incentives.
  • Refusal of responsibility: No one accepts a decision or deviation. Assign an owner and a binding escalation path.

That is why I consider “zero errors” a poor governance promise. What matters is whether the project reports deviations early, classifies them properly, and demonstrably learns from them.

A practical pattern for UAT and defect triage

In the next UAT triage, add three fields: cause category, accountable owner, and agreed system change. A critical defect should not end with “fixed.” It should, for example, lead to a clearer acceptance rule, an additional reconciliation step, or changed supplier controls.

Bring recurring errors into the steering meeting every month. Report the volume and age of open defects, together with recurrence, reporting delay, and overdue learning actions. Record material decisions in the decision log.

What project leaders should do now

Look at what behaviour your project actually rewards: early warnings, or green reports for as long as possible? Define a different response for each of the four causes and track implementation like any other work package.

The number of errors is not the relevant metric. What counts is the time between the first signal and an effective change to the system.

← Back to the blog