Planning for Quality, Not Inspecting It In: A Practical How-To Guide
Philip Crosby's famous dictum 'quality is free' rests on a specific premise: the cost of preventing defects is lower than the cost of detecting and correcting them after the fact. This premise has been validated repeatedly in manufacturing, software development, and capital project delivery. The implication for project managers is direct: inspection at the end of a process is the most expensive way to achieve quality, not the most reliable. Planning quality in from the start -- through clear requirements, thoughtful design, explicit work standards, and proactive reviews -- is both cheaper and more effective.
Here is a practical how-to guide for planning quality into a project from day one.
Step 1: Define Quality Requirements as Specifically as Possible
Most quality problems trace back to ambiguous or incomplete requirements. 'The system shall be reliable' is not a quality requirement; 'the system shall have an unplanned downtime rate of no more than 0.5% in any 30-day period, measured over the first 12 months of operation' is a quality requirement. At project initiation, require that all quality-relevant requirements be expressed in measurable, verifiable terms. If a requirement cannot be tested, it cannot be verified -- and unverified requirements will be interpreted differently by different people.
Step 2: Build Quality Reviews Into the Project Schedule
Design reviews: At the end of each design phase, hold a formal review of the design against the quality requirements. The review should include people who were not involved in producing the design (fresh eyes catch what the designer misses). Document what was reviewed, what was found, and what was changed.
Constructability and reviewability reviews: For physical deliverables, have the people who will build or test the work review the design before construction or testing begins. They will identify buildability issues, missing specifications, and testing gaps that the designer may not have considered.
Stage gate reviews: At each major project stage gate, include an explicit quality assessment as part of the go/no-go decision criteria. A project that has accumulated unresolved quality issues should not pass a stage gate without a documented plan for resolving them.
Step 3: Establish and Enforce Work Standards
Defects often arise not from bad intent but from inconsistent practices -- different people doing the same task in different ways, with different outcomes. Work standards reduce this variability. For critical project activities (procurement quality checks, inspection sign-offs, testing procedures), document the standard procedure, train people on it, and verify through random audits that it is being followed. A work standard that exists in a document but is not followed is not a work standard -- it is a fiction.
Step 4: Track Quality Metrics Proactively
Establish leading quality indicators that give you early warning of quality trends, rather than only tracking lagging indicators (defects found at final inspection). Leading indicators might include: design query volume and cycle time (high query volume in detailed design suggests the preliminary design was insufficiently developed); inspection pass rate at first attempt (declining first-pass yield is a signal of process deterioration); ratio of rework hours to total hours (increases in rework ratio are a leading indicator of systemic quality problems). Review these metrics at each project milestone meeting.
XNM provides project management and quality management advisory services to public-sector and capital-project clients. Reach out to XNM's program & project delivery advisory team to discuss quality planning and management for your project.