Product managers & owners
Product intent, clinical value, prioritisation and decision-making within a regulated development system.
Translate clinical and market intent into a product the organisation can develop and defend.
Downloadable field guides
Product intent, clinical value, prioritisation and decision-making within a regulated development system.
Articles
A practical approach to shared software assurance evidence, with clear regulatory boundaries and a worked calibration-system example.
Why standards selection for an IVD must follow the complete system, its intended purpose and the consequences of an incorrect result.
Why a long standards list is not enough—and how intended purpose, harmonisation and product-specific evidence shape a defensible standards assessment.
A playful but serious reflection on AI as assistant, reviewer and decision-maker—and why fluent answers still need evidence, judgement and accountability.
AI changes the speed and economics of medical-device development, but it does not remove the need for product definition, objective evidence, competent review or manufacturer accountability.
Why outsourcing medical-device development increases the need for intelligent manufacturer oversight—and what must be controlled before an audit or submission exposes the gaps.
Does treatment naturally progress from infusion to injection and finally to a tablet—or can digitally supported subcutaneous delivery be the better destination?
How the responsibilities of startup founders, SME management and corporate leaders differ—and why qualified external advice is most valuable before major development commitments are made.
Why absence of commercial registration does not automatically prevent a digital health technology from being used in a clinical trial—and the questions sponsors should ask instead.
A practical interpretation of Essential Performance for electronically driven injection systems, and what engineers should specify, trace and verify.
An end-to-end view of medical-device development, from intended purpose and user needs through verification, validation, transfer and maintenance.
How user needs, requirements, design outputs, risk controls, verification and validation form a coherent evidence chain.
A clear explanation of verification, validation and how both connect to user needs, design inputs and objective evidence.
What makes development evidence coherent, reviewable and defensible before an audit or submission.