Forum

Notifications
Clear all

Customer Needs and Design Input

72 Posts
70 Users
0 Reactions
17.7 K Views
(@noahyoussef)
Posts: 69
Trusted Member
 

I belive that both inputs and specifications have their intended purposes. In terms of actually constructing a device, it is impossible to do so based on solely inputs. Specifications are needed for the actual construction of the device and for the device to be constructed identically during the manufacturing process. However, inputs are important because they lay out how the design meets the intended needs without going into unnecessary detail. For instance, when describing a project to a group of investors, it is much more useful to talk to them about the inputs rather than the specifications. The inputs as the question of how the device works without the unnecessary details such as individual measurements or tolerances. Also, you need an input document in order to make a specifications document. 


 
Posted : 12/11/2023 9:47 pm
(@31746439)
Posts: 69
Trusted Member
 

The Design Input Document (DID) and Design Specification Document (DSD) are both important for developing a medical device, but they serve different purposes. The DID provides a broad overview of the product concept, describing what the device should do and what the customer or user needs. It’s more qualitative and helps the team visualize the product’s goals and appearance. The DSD, on the other hand, gives quantitative technical details—such as measurements, materials, and tolerances—that guide manufacturing and ensure product consistency. The main advantage of the DID is flexibility and creativity during early development, while the DSD ensures precision and compliance with regulatory and quality standards. Without the DID, designers might lose sight of user needs; without the DSD, the product might not meet safety or performance requirements. 


 
Posted : 05/11/2025 1:27 pm
(@nevinantony)
Posts: 76
Trusted Member
 

In terms of design controls, the connection between the Design Input Document (DID) and the Design Specification Document (DSD) is essential to guaranteeing that a product is created methodically, precisely, and in accordance with legal requirements. In the process of developing a product, each has a specific function: the DSD specifies how the device will fulfill its requirements, while the DID specifies what the device must perform. Effective communication and responsibility throughout the project depend on this separation, which guarantees clarity between engineering execution and user needs. The DSD outlines how to turn that vision into a concrete, testable, and manufacturable reality, while the DID explains why the product should exist and what it should accomplish from a functional and therapeutic standpoint. Together, they provide the basis for traceability, which is essential to FDA and ISO 13485 design control compliance and guarantees that each design choice can be linked to an original user requirement. Without one, the process is either too restricted or too unclear. This raises the question of which document, in your perspective or experience, is more difficult to accurately maintain: the DSD with its intricate engineering limitations or the DID with its changing user requirements. In the end, the DID and DSD are complementary components of a single, well-managed design process. One guarantees that the device performs its intended function in a safe and efficient manner, while the other guarantees that the design can be consistently produced in accordance with those criteria. When combined, they safeguard the patient's safety as well as the product's integrity, which is the ultimate objective of any medical device development endeavor.


 
Posted : 06/11/2025 5:24 pm
 ri62
(@ri62)
Posts: 72
Trusted Member
 

Understanding customer needs and translating them into clear design inputs is a fundamental step in medical device development, typically documented in the Design Input Document (DID). Customer needs, gathered from clinicians, patients, and other end users, are analyzed and converted into measurable, testable requirements within the DID. These inputs then guide the creation of the Design Specification Document (DSD), which details the engineering and technical parameters necessary to meet those needs. A well-prepared DID ensures that the DSD accurately reflects safety, performance, and usability expectations. Failure to properly document and link customer needs in the DID and DSD can lead to design gaps, usability problems, or noncompliance with regulatory standards. Continuous communication among design, clinical, and regulatory teams ensures that these documents stay aligned throughout development. Ultimately, well-structured DID and DSD documents help ensure that the final medical device meets user expectations, regulatory requirements, and clinical performance goals.


 
Posted : 08/11/2025 10:47 am
(@gk376)
Posts: 72
Trusted Member
 

Design input is the customer’s side where we, as the engineers, confirm broadly what the requirement is; when breaking down the logistics and physics of it all, the design specifications are planned. It is not that one is more important than the other; they are both required as steps in the design process. I would have no idea what my project was if I wasn’t building the design input document, but when I am actually making the product, I need those specifics. Say, for example, we are building a plane; the design input could be that it needs 120 seats, then the design specification will break down the seat dimensions and plane dimensions to accommodate the seating requirement. I don’t see a disadvantage in either one is simply the draft to the other. That said, would you consider formally presenting the design input, or is that something you would consider replaceable once the design specifications are formulated? 


 
Posted : 26/10/2026 3:28 pm
(@andrewg)
Posts: 34
Eminent Member
 

Posted by: @rv347
↑

In design controls, there is the DID and DSD documents. DID is design input and gives a broad description of the product (ex, "red knob"), whereas the DSD is design specification and gives a very specific description(ex, "red knob 3cm in diameter dyed with red #5 from Vendor x with a tolerance of 0.001cm"). What do you think the advantages and disadvantages are of each document and why are they both necessary?

Since DID documents often come from nontechnical personnel, they can sometimes come off as an unrealistic wish list that needs to be reeled in by technical staff in the DSD. On the other hand, the DID is full of insights from customers personnel who may be more familiar with client needs that may not have been taken into consideration otherwise. I think both are necessary, as the DID sets the scene for what the client is looking for, and the DSD ties it to physical and fiscal reality.

What steps do you think should be taken that the vision set by the DID is reflected in the specifications set by the DSD?

 


 
Posted : 29/10/2026 5:38 pm
(@nm234)
Posts: 70
Trusted Member
 

With design controls, it is quite easy to identify the advantages that the DID and the DSD bring to the document. The DID helps the user identify the location and even a broad description of it for the purpose having the design be understandable no matter the version of the product. The DSD offers specific dimensions and measured expectations for the product to have so it can easy be remade by anyone following the instructions properly. Both of these serve the purpose of showcases the design and having the intentions of the design be entirely understandable for the benefit of the reader as well as the designer themself. A disadvantage from these design controls could be that depending on how drastic of changes made to the design, the previous document becomes a lot less understandable when compared to the current design. It is then that the intention of the design becomes lost and more difficult to be able to replicate it. 


 
Posted : 01/11/2026 4:48 pm
(@alina-kolenovic)
Posts: 33
Eminent Member
 

Both documents are necessary to communicate key aspects of the device design. The DID design input document is primarily used for addressing high-level, broader design inputs such as the specific user needs that the device will address, the regulatory requirements it will meet, and how it is meant to function.  The advantage of the DID is that it clearly defines what the device is and what the device should achieve. This can be presented to stakeholders to gauge interest in the device and whether moving forward is a good option. This document provides more flexibility in choosing later choosing specific design features/characteristics. The lack of specific details in the DID presents a disadvantage to the engineering teams who will have to actually build and put together the device. When it comes to the DSD, this is when the design inputs mentioned in the DID are expanded upon and converted into exact specifications that can be created and tested. This document is advantageous to the engineering and development teams required to build the device and provide information that supports repeatability. The DSD details the requirements and how to measure them so that they can later be verified and validated. The disadvantage of this document is that there is much less flexibility than with the DID. Once requirements are mentioned in the DSD they are meant to be closely followed and any changes would have to be submitted for approval. 


 
Posted : 01/11/2026 5:55 pm
(@jf31634027)
Posts: 72
Trusted Member
 

The most important advantage of the DID is that it's a general overview of the things that need to be done to create the product. It gives more freedom to the engineers who create the product since it doesn't include any specific information on how the product should be designed. If specific components aren't mentioned, the engineers can use their freedom to pick them based on what they think works best. However, the disadvantage is that the requirements may be too broad and execution may not satisfy the customer needs. The DSD, on the other hand, includes detailed information about the product, which makes manufacturing the product easier. The disadvantage of this is that its very specific and can make changing the design or replacing components difficult. In my opinion, both documents are necessary because they have different functions. The first document gives us a broad overview of what the product should do and a general idea of it while the second one specifies on execution and how it should be done. 


 
Posted : 03/11/2026 2:20 pm
(@randa)
Posts: 35
Eminent Member
 

The good thing about the DID is that it gives an overall description of the device and what the user needs. However, it is not descriptive in detail, so it would be hard to build or test the device from it alone. The good thing about the DSD is that it is very detailed, which gives better information on exactly what is needed. A bad thing about it is that it might not be realistic. For example, a tolerance of 0.001cm is very tight and could be hard or expensive to manufacture. Companies need both instead of one so that they know the overall goal as well as the specifics for the medical device.


 
Posted : 03/11/2026 3:02 pm
(@ed273)
Posts: 31
Eminent Member
 

I think both the DID and DSD are important since they provide different information needed for the medical device. The DID gives the general idea of what the device needs to accomplish, while the DSD are the requirements the engineers need to follow. The DID helps the egnineers on the main purpose of the device without giving the engineers any limitations but does not provide enough details on how to actually make the device. Overall, the DSD is what helps engineers know what they need the device to do. By knowing the requirements, they can understand the purpose of the device and what it is set out to do. In my senior design project, my team is making a robotic device that follows a patient while applying resistance during gait training. One of our requirements is for the robot to maintain a safe following distance. We specified the distance as 50 cm with a tolerance of +/- 10 cm. This is where the DSD is important, as this is a requirement with a specified measurement. 


 
Posted : 08/11/2026 10:12 pm
(@areemoshe-booker)
Posts: 33
Eminent Member
 

Both of these documents complement each other very well in the conception of medical device development. Its seems like approaching a design from two different angles to ensure the best of both worlds and provide customers with a device that is desirable and useful on the market. While they both perform separate goals being qualitative and quantitative the purpose of having them housed in separate documents allows for almost a two factor form of security with device conception. I wouldn't say that one has a significant advantage over the other but that they assist one another quite well in ways that if you had one alone it would feel as if devices were incomplete and unready for market standards.


 
Posted : 08/11/2026 10:56 pm
Page 5 / 5
Share: