Observe
Notice significant behaviour, evidence, uncertainty, recurring patterns, contradictions and consequences—not merely execution status.
Make it visible: record what was actually observed, its context and references to supporting evidence.
Publication 02 · Professional Expression 01 · Working Practice v0.1
Human-Centred Quality in Practice: The Test Manager
From managing testing to stewarding understanding. A working expression to use, challenge and improve through practice.
A working professional expression
This is not a job description, competency framework or maturity assessment. It proposes a simple pattern through which a Test Manager can make the development of quality understanding visible.
Human-Centred Quality does not replace test strategy, planning, governance, risk management, reporting or leadership. It asks what those activities ultimately enable: sufficient understanding for people to make responsible judgements about quality.
OBSERVEINTERPRETUNDERSTANDJUDGEIMPROVESTEWARD
Practice is not Capability.
The Practice describes what Human-Centred Quality looks like when expressed through professional work. Capability asks how effectively and consistently people and organisations are able to express it. Before assessing capability, make the Practice visible.
The model expressed as Test Management
Six practices. Existing work. A different orientation.
Interpret
Encourage plausible explanations without allowing an explanation to silently become fact. Invite perspectives capable of changing its meaning.
Make it visible: preserve interpretations separately from observations, including alternatives and uncertainty where material.
Understand
Bring evidence, interpretations, experience and context together into the best current coherent explanation. Make what remains unknown explicit.
Make it visible: record current understanding, what supports it and significant remaining uncertainty.
Judge
Help those responsible for decisions understand evidence, consequence and uncertainty sufficiently to act responsibly.
Make it visible: record the judgement or recommendation, rationale, material uncertainty and contributors.
Improve
Ask what should become better because of what has been learned—not merely whether an activity or defect was completed. Return later to discover what happened.
Make it visible: record intended change, intended outcome and, when known, actual outcome.
Steward
Decide what learning deserves to survive the immediate situation and make it available without turning every observation into organisational knowledge.
Make it visible: preserve reusable learning with provenance and evidence; identify where or with whom it should be shared.
The HCQ Record
Make the development of understanding durable.
The record is an information model, not a prescribed tool. Use an existing platform, structured document, database, XML, JSON or another mechanism that preserves the distinctions below. A record may begin incomplete and develop as understanding develops.
Context / concern
Observe — What did we notice?
Observation:
Evidence / reference · Contributor · Date:
Interpret — What might it mean?
Interpretation(s) / alternative interpretations:
Uncertainty:
Understand — What do we currently understand?
Current coherent explanation:
What remains uncertain:
Judge — What does this understanding mean for action?
Judgement / recommendation and rationale:
Contributors / material consequence:
Improve — What should become better?
Action / change and intended outcome:
Actual outcome — return when known:
Steward — What deserves to survive?
Reusable learning / where it should be shared:
Worked example
One concern, allowed to develop.
A peak-load test provides the starting observation. The record grows only as evidence and understanding grow.
Observe
Three test executions timed out after submission during peak-load testing. The same journey completed within expected time outside the peak-load window. Evidence: test run and performance log.
Interpret
One interpretation suggests capacity degradation under concurrency. An operational perspective adds that delayed confirmation may cause users to resubmit. Production-equivalent behaviour remains uncertain.
Understand
Current evidence suggests the transaction may succeed while confirmation is delayed. The quality concern is therefore not only response time, but whether users can know their action succeeded.
Judge
Do not treat the timeout only as an isolated performance defect. Extend targeted testing and seek agreement on acceptable mitigation before the release recommendation.
Improve
Validate duplicate-submission safeguards and explicit submission-state feedback. Return later to record whether the change actually improved the outcome.
Steward
Candidate reusable pattern: delayed acknowledgement can convert a performance symptom into a user-decision and duplication risk. Preserve the evidence and share where relevant.
What should you do next Monday?
Try it on one consequential concern.
- Choose one concern where developing understanding could genuinely improve a decision.
- Start with what was actually observed. Do not manufacture the rest of the record.
- Invite other perspectives where they can change the interpretation.
- Keep uncertainty visible.
- Record consequential judgement and what is changed.
- Come back later and record what actually happened.
Then ask: Did making the development of understanding visible improve anything?
Guardrails
Keep the Practice useful.
Do not record everything
Use selective durability for consequential, uncertain, contested, recurrent, cross-disciplinary or reusable concerns.
Do not turn Practices into gates
The arrow describes developing understanding, not six mandatory workflow states. New evidence may move the record in any direction.
Do not turn the Record into a score
Record counts and completion percentages do not demonstrate Human-Centred Quality. Ask whether understanding and decisions improved.
Try it · challenge it · contribute
This is a working expression, not a finished standard.
Use it once. Then tell us what practice reveals. Does this resemble credible Test Management? What is missing? What becomes bureaucracy? Where does a Practice behave differently in your environment? What existing tool already supports part of it?
- What survived contact with real delivery?
- What did not?
- What did making understanding visible change?
- What would you alter before another Test Manager tried it?
Practice first. Capability follows from understanding what is actually practised.
This Test Manager expression is the first role-aware working release. Test Analyst and Test Architect working expressions are now available alongside this one. They are compared to expose what remains common and what changes with professional perspective. Test Lead remains deliberately open for contribution.
Compare the professional expressions Return to the Initiative roadmap