§1 The Quality Framework

Quality metrics establish the objective standard for project deliverables. Rather than relying on subjective assessments during User Acceptance Testing (UAT), they provide verifiable targets that definitively prove a requirement has been met.

An effective Quality Metrics matrix relies on four foundational columns:

ID: A unique identifier (e.g. QM-01) used to trace the metric across testing logs, Jira tickets, and final sign-off documentation.
Item: The specific component, process, or deliverable being evaluated.
Metric: The exact data point being observed. This must be a quantifiable figure, percentage, or binary state.
Measurement Method: The tool, mechanism, or report used to capture the data, alongside the strict threshold for failure/success.

KEVOS® Principle: Never track a metric you cannot reliably measure. If the Measurement Method requires a subjective manual review without a strict rubric, it is an opinion, not a metric.

Contents

§2 Worked Example: Web Project

The following table demonstrates a completed Quality Metrics matrix for a corporate website overhaul (Mary's Consulting - New Company Website).

Notice how every item includes a specific tool (like Lighthouse CI or BrowserStack) and an exact numerical threshold (like < 2.5s or 100%).

ID	Item	Metric	Measurement Method
QM-01	Accessibility	WCAG 2.1 AA findings	Third-party audit at A031; defect count by severity
QM-02	Performance - LCP	Largest Contentful Paint (75th percentile)	Lighthouse CI on 5 representative pages; target < 2.5s on 4G
QM-03	Performance - CLS	Cumulative Layout Shift (75th percentile)	Lighthouse CI; target < 0.1
QM-04	Defect density	Defects per page template	Count of Sev-1/Sev-2 defects ÷ 12 templates; target < 0.5
QM-05	Defect resolution time	Average days from logged → resolved	Jira report by severity; target Sev-1 < 2 days; Sev-2 < 5 days
QM-06	Code review coverage	% of PRs with peer-reviewed approval	GitHub branch protection; target 100%
QM-07	Test coverage	% lines covered by automated tests	Jest coverage report; target > 70% on JavaScript components
QM-08	Security - OWASP scan	Number of high/critical findings	ZAP/Burp scan before UAT; target 0 high/critical
QM-09	Content quality	% of pages signed off by Marketing Lead	Tracked in content QA log; target 100% before UAT
QM-10	Bio submission rate	% of in-scope consultants with submitted bio	Christine's tracker; target 60% by Sep 25
QM-11	Cross-browser	Browser/device combinations passing smoke tests	BrowserStack matrix: Chrome, Firefox, Safari, Edge × desktop+mobile; target 100%
QM-12	Uptime (post-launch)	Production availability during hypercare	Pingdom monitor; target ≥ 99.9% over 14-day hypercare window

Contents

§3 Quick Reference

Automate First

Whenever possible, select metrics that can be extracted automatically via CI/CD pipelines (e.g. Jest, Lighthouse) rather than manual tracking.

Clear Thresholds

Ensure your targets are definitive. Avoid words like "fast" or "secure". Use exact figures (< 0.1) or absolutes (0 critical findings).

Baseline Agreements

Standardise your matrix and secure stakeholder sign-off prior to the execution phase to prevent goalpost shifting during final delivery.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Quality Metrics. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Use Quality Metrics as a decision instrument rather than an administrative form. The subject terms—quality, metrics, framework, worked, example—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.

Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.

A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.

Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.

Step-by-step operating method

Name the decision. Write the decision, approval, handover or control activity the completed template must support.
Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.

Completion and governance protocol

Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.

Information type	Minimum useful content	Review test
Outcome	Observable change and intended recipient	Not merely a deliverable or activity
Measure	Definition, baseline, target, frequency and source	Two reviewers would calculate it the same way
Ownership	One accountable role plus contributors and approver	Authority matches responsibility
Uncertainty	Assumption, risk or issue with response and trigger	Status reflects current reality
Control	Version, approval, review date and change rule	Current baseline is identifiable

Common failure modes and recovery actions

1. Watch for

Filling every box even when a field is not applicable instead of recording why.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Writing vague statements without an owner, measure, date or evidence source.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Copying a previous project without revalidating assumptions and stakeholders.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Using the document as a private worksheet when it is meant to support a shared decision.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Creating an approved baseline but failing to define who maintains it and when.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.