The FDA Human Factors Guidance Update Is Stricter Than You Think

The FDA’s updated human factors guidance is not a paperwork update. It changes what you have to prove, when you have to prove it, and what counts as proof. If your team is still running usability testing the way you did five years ago, you are building toward a regulatory problem.

I want to be direct about what changed and why it matters for design teams specifically, because most of the commentary I have seen focuses on the regulatory affairs side of this. The design side is where the actual work happens.

What the Update Actually Changed

The FDA’s human factors guidance update placed significantly more emphasis on use-related risk analysis earlier in the development process. Under the updated framework, you are expected to demonstrate that use-related risks were identified and addressed through design before you submit, not discovered during summative testing.

The practical implication: you cannot run one summative usability study at the end of development and expect it to carry your 510(k) or PMA submission. The FDA wants to see formative study evidence showing that your design decisions were informed by user data, and that each design iteration addressed specific use-related risks identified in prior testing.

This is a fundamentally different evidentiary standard. It requires that your design process and your regulatory documentation tell the same story. If the documentation shows design decisions that were not grounded in human factors data, the submission will face questions it cannot answer.

Where Design Teams Get Caught

The most common failure point I see is the disconnect between what the design team actually did and what can be documented. Design teams often make good intuitive decisions based on domain knowledge and design expertise. Those decisions may be correct. But if they cannot be traced to specific human factors findings, they do not satisfy the updated evidentiary requirements.

A second failure point is the sequencing of usability studies. Many teams conduct formative testing, iterate the design, and then conduct summative testing as a final validation. That sequence is fine in principle, but the documentation has to show a clear chain from formative findings to design changes to summative performance. Gaps in that chain create regulatory risk.

The third failure point is the definition of the intended use population and use environment. The updated guidance is more explicit about requiring representative user testing with the actual clinical environment accounted for. Testing your cardiac monitor with engineering staff in a conference room does not satisfy the requirement. Testing it with actual cardiac care nurses in a realistic clinical context does.

How This Changes the Design Process

For design teams, the update means that human factors documentation has to be integrated into the design process from the beginning, not compiled at the end. Every formative study needs to produce findable, traceable evidence of what was discovered and what changed in response.

At Dip Studio, we build human factors traceability into the design process from the first user research phase. The formative study outputs feed directly into design decision documentation. When a design choice is made in response to a human factors finding, that connection is recorded in a format that will survive regulatory scrutiny.

This is not a compliance exercise layered on top of design. It is design practice that produces regulatory evidence as a natural byproduct. The teams that treat it as a compliance exercise create overhead and tension. The teams that treat it as good design process find that it improves their products and their regulatory outcomes simultaneously.

What This Means for Your Current Development Program

If you have a device in active development, the right question is: does your current documentation support the traceability the updated guidance requires? If you are early in development, you have time to build the right process from the start. If you are closer to submission, a gap analysis against the updated requirements is worth doing now rather than at the pre-submission meeting.

The FDA has been explicit that they will ask for formative study evidence at submission. The updated guidance is not a future-state aspiration. It is the current standard. Design teams that understand this and build accordingly will have a material advantage in regulatory timelines over those that treat human factors as a late-stage validation step.