An organisation’s must knows. Know your context. Know your products and services. Know your customers, and if the words "design" and "development" have crept into the marketing spin, the contract, or even the expectations, then you'd better get your head around the design clauses. There really isn’t much to do with them other than to identify each component and compare them to the company activities. Don’t build a process or a system that tries to encapsulate the 1 million what-ifs; focus on the core activities and have review points to decide on whether further detail or records are needed to meet the above requirements.
Remember to keep it simple and be realistic. Remember, you get to decide whether design and development are core processes, so take a good, hard look.
The good news is that this clause can be deemed ‘Not Applicable’. And if you deem it, claim it, then you need to justify it. A simple justification is a statement along the lines of…The company does not design or develop our product/service range. Then you record this in a format that is easily retrievable when asked. I keep such statements in the quality manual, cross-reference tables, management review minutes, or business plans.
A simple way to think about it is: Design is about deciding how an outcome will be achieved. Compliance is about meeting requirements that have already been decided by someone else.
If an organisation is creating a plan, process, methodology, framework, or other documented arrangement that determines how work will be carried out, there is a good chance design is involved. If they are following requirements set by legislation, standards, regulators, clients, or contracts, then the focus is generally compliance rather than design. Engineering design is usually easy to identify, but design activities exist in many industries and can be much less obvious.
Some examples of design outputs could include:
- Traffic control plans
- Wiring schematics
- Site layout plans
- Plant and equipment movement plans
- Drainage and runoff plans
- Lighting layouts
- Temporary works designs
- Service delivery models
- Operational workflows
- Emergency response arrangements
- Maintenance strategies
- Workforce rostering and resource allocation models
- Business continuity plans
When assessing whether design is in scope, try asking: Could another competent organisation, working to the same requirements, reasonably come up with a different solution, process, plan, or arrangement and still achieve compliance? If the answer is yes, design is probably involved.
At Quality IQ, we claim to design, develop and implement quality management systems. We are even ISO 9001-certified to do so. Nice huh! We then back these claims up in our quality manual, our project management procedure, our business plan and review all such stuff in our management review meetings. There is no ambiguity, and the records are easy to find in myQualityTM. The secret to demystifying the design process has been not to try to describe the incredibly complex permutations of moulding a quality management system around a corporate structure, but to have review points to ensure that the design facets are being met. A very large checklist. A monumental number of templates and examples. Trained and skilled consulting resources to match needs and expectations, using the very quality management system itself that we are developing to look after the review elements and records during the design process by recording them in their own management reviews, corrective actions, audits, risks, objectives and so on.
The great news is that we have a very simple verification and validation process, which is the ultimate success of the certification for our clients. Beautiful symmetry here. And even better news is that the guarantee we provide to all our clients means that certification and the ultimate in design delivery are always met. Noice.
* Partof this article was an excerpt from a recent Global Mark newsletter. Thanks, Chris.