Relationship management protects important dependencies
Relationship management in quality management means understanding and managing relationships that affect the organisation’s ability to deliver useful, reliable results. Suppliers are an obvious example, but delivery partners, specialist advisers and other relevant parties may also influence performance.
It is part of the seven quality management principles. The principle encourages informed cooperation and clear expectations. It does not mean treating every relationship alike, accepting poor performance to preserve goodwill, or assuming that a long relationship makes checking unnecessary.
Start by identifying the dependency. What result does the organisation need from the other party, and what would happen if that result were late, wrong or unavailable?
Focus attention where consequences justify it
A supplier providing a readily available office item does not usually warrant the same attention as the only specialist able to perform a critical operation. Consider consequence, technical complexity, availability of alternatives and recovery time.
Frequency of purchase is not the only guide. A rarely used service may be essential when an unusual failure occurs. Equally, a high spend does not automatically mean high quality risk if the output is simple and easily replaced.
Create a practical basis for differentiated oversight. This can be a short classification or an explanation in the purchasing decision. The purpose is to allocate attention sensibly, rather than generate elaborate ratings that nobody uses.
Agree expectations that support usable outputs
Clarify what the partner will deliver and what information the organisation must provide. Many relationship failures involve reciprocal ambiguity: the supplier lacks a clear specification, while the purchaser assumes that experience will fill the gaps.
| Topic | Question to resolve |
|---|---|
| Acceptance | What characteristics make the output usable? |
| Timing | Which dates matter and what dependencies affect them? |
| Change | Who must know before material changes occur? |
| Problems | How are concerns escalated and contained? |
| Evidence | What information demonstrates delivery performance? |
| Continuity | What happens when the normal arrangement fails? |
Keep requirements and preferences distinct. Where a characteristic is necessary, make that clear. Where alternatives are acceptable, give the partner room to propose an effective method. Excessively prescribing the method can remove useful expertise without improving the outcome.
Build communication around decisions
Communication should help the parties act. Agree which events need notification, who can decide and how urgent issues reach the right person. A monthly review is useful for trends but too slow for a change that threatens tomorrow’s delivery.
Share relevant information responsibly. A partner may need forecasts, technical changes or feedback about recurring defects to improve their service. They may not need unrestricted access to unrelated commercial or personal information. Establish appropriate boundaries for the relationship.
Listen to the partner’s view of the interface. Last-minute changes, incomplete orders or unrealistic forecasts from the purchasing organisation may contribute to failure. Relationship management requires examining the organisation’s own behaviour as well as the partner’s output.
Hypothetical example: a critical courier service
A hypothetical testing laboratory depends on a courier to collect time-sensitive samples. The contract states a collection time, but nobody has agreed who should act if a driver is delayed. Staff repeatedly discover the problem after the useful escalation window has passed.
The laboratory and courier agree a notification trigger, named operational contacts and an alternative collection decision. They test the arrangement with a simulated delay and later review actual exceptions. The laboratory also checks whether its own sample readiness causes avoidable waiting.
This hypothetical example illustrates managing a dependency through reciprocal clarity. It does not claim that every laboratory needs the same arrangement, or that a cooperative meeting substitutes for assessing actual service performance.
Evaluate performance without reducing it to a score
Review evidence relevant to the relationship: conformity of outputs, reliability, communication, recurring problems and response to change. A composite score can support screening, but it may hide a serious weakness behind good results elsewhere.
For example, consistently low prices should not mathematically cancel an unresolved failure in a critical technical characteristic. Decide which issues require attention regardless of the overall score. The guide to evidence-based decision making helps distinguish meaningful performance signals from misleading counts or averages.
Check what happened after concerns were raised. An action promise is different from an effective correction. Where performance remains unacceptable, consider stronger controls, an agreed recovery plan or a different source according to the consequence and available alternatives.
Balance cooperation with accountability
Trust can make communication faster and more candid, while oversight provides a basis for justified confidence. These support each other when expectations are clear. Informal goodwill becomes fragile if no one knows how performance is judged or what happens after repeated failure.
Before the next important partner review, choose a few recent deliveries and exceptions. Ask whether both parties understood the agreement, exchanged useful information and resolved problems through an effective route. Identify one change to the interface that could reduce uncertainty.
A useful relationship is not merely pleasant. It helps the organisation and the other party understand their commitments, anticipate disruption and make decisions that preserve the intended quality outcome.