Industry

# Medtech

Design, quality, and regulatory each keep their own record of the product, and they meet for the first time at submission.

You will recognize this

## You have sat in this meeting.

- Regulatory affairs sees the design for the first time at the review gate, and the redline list sends engineering back two phases.
- The design history file and the engineering backlog tell two stories, and someone spends the days before each design review reconciling them.
- The cybersecurity section of the premarket submission gets written the month it is due, by whoever has threat-modeling experience.
- Before an inspection, the team rebuilds training and CAPA records from spreadsheets and discovers the sites follow different procedures.

What is changing

## What is changing in Medtech.

Under the FDA's Quality Management System Regulation, effective February 2026 and incorporating ISO 13485, quality, supplier, and cybersecurity evidence now have to hold together as one system.

Scope

### Quality begins upstream

Requirements, evidence, risk, and ownership need to be understood before regulated work moves.

Bridge

### Quality crosses boundaries

Product, clinical, quality, regulatory, security, and supplier decisions have to retain context across handoffs.

Signal

### Inspection-ready evidence

The operating system must produce trustworthy records as work happens, not reconstruct them before an audit.

Sources: [FDA Quality Management System Regulation](https://www.fda.gov/medical-devices/postmarket-requirements-devices/quality-management-system-regulation-qmsr), [FDA medical-device cybersecurity guidance](https://www.hhs.gov/guidance/document/cybersecurity-medical-devices-quality-management-system-considerations-and-content)

The system view

## Where the pressure hits the system.

Hover a part of the system to see how this industry strains it. Select it to learn more.

parts of the system

- 1 **Surface***How work enters*
- 2 **Scope***How work is understood*
- 3 **Rank***How priorities are ordered*
- 4 **Cascade***How strategy becomes work*
- 5 **Flow***How work moves*
- 6 **Bridge***How groups connect*
- 7 **Signal***How the system reads itself*

The highlighted parts are where this industry puts the most pressure on how work moves.

What good looks like

## What good looks like when it holds.

What the work looks like once the system holds, and the signal that shows it.

### Regulatory constraints shape the design before commitment

Regulatory and quality leads sign off on scope before engineering starts, not at the gate.

### Quality evidence is produced as the work happens

Audit preparation pulls existing records instead of reconstructing them from email and spreadsheets.

### Cybersecurity has a named owner from concept

Threat models and security requirements appear in the backlog alongside the first design inputs.

Where to start

## Pick the entry point that matches what you see.

Each starting point names the condition you can see today and the service that addresses it first.

[Value Stream Management If design and quality records reconcile only at review gates, start with Value Stream Management.](https://www.agileon.com/professional-services/value-stream-management)[Work Management Systems If requests reach engineering without risk, requirements, and evidence owners named, start with Work Management Systems.](https://www.agileon.com/professional-services/work-management-systems)[Operating Model Design If regulatory, clinical, and security leads cannot agree who decides on scope, start with Operating Model Design.](https://www.agileon.com/professional-services/operating-model-design)

From the field

## The same pattern, in other rooms.

Some of these come from other industries. The same component fails the same way here.

[Field story The Work Was Not Slow. The Request Was Not Ready. A regulated product company's marketing team mapped every request from submission to publication. The delay was not in the work. It was at the front of the map, where incomplete requests sat waiting for information nobody had asked for.](https://www.agileon.com/insights/the-request-was-not-ready)[Field story Two Teams Built the Same Thing Without Knowing At a medical technology company, a sprint review revealed that another team had been building the same connection for months. Nobody had been careless. Work could reach a team through more than one door, and nothing connected those doors.](https://www.agileon.com/insights/two-teams-built-the-same-thing)[Field story The Quality Problem Began Before Testing At a research and advisory firm, the internal acceptance tester was finding defects faster than she could log them. More testing wasn't the answer. Each team wrote down, and took ownership of, what done had to mean before work left its hands.](https://www.agileon.com/insights/the-quality-problem-began-before-testing)
