I think design reviews and design changes are most important during the Check and Act phases of the PDCA cycle. The Check phase is important because it connects all the other phases of the design process together. With Check, you are looking over everything that has been done. This ensures that the design outputs align with the inputs. This also looks over the verification and validation data, which allows the team to see if there are gaps in their design. Issues will become visible in a more structured way since the Check phase dedicates a real amount of time for review as opposed to just looking for mistakes as the team is doing the project. 

For design change requests, the Act phase is the most important because corrective actions happen in this phase. The Check phase will identify the problems, but these problems need to be acted on to turn into any real, meaningful change. Moving forward with resolved risks is important to make sure the project does not fail later in the cycle, as this will end up costing more resources since one would likely have to go back in the process to address the root of the problem. 

This leads to the topic of competing pressures of limited resources and timelines. I think PMs should use the PDCA as a filter for decisions instead of as a checklist. With a filter for decisions, resources and time can be allocated to areas that are more crucial, allowing for better design changes when resources are scarce. This also encourages fixing issues before they become even more costly in the long run, since they will be prioritized higher. The PDCA allows PMs to balance efficiency with the long-term longevity of the project with prioritization. This is done through thorough documentation, evidence, and design control. For the prioritization itself, the items that would do the most damage further down the line if not addressed now should be prioritized the highest. The core requirements that need to be followed by the medical device should be prioritized higher as well. Do you think the PDCA should be followed in a flexible and prioritized manner as I described above, or should the process be more rigid for standardization purposes? How do you think AI can be incorporated to optimize how the PDCA is used? Can it be used to determine which tasks should be prioritized higher? 

I think that while Design reviews and Design change requests are important to do during the check and act phases, I think it is just as important to do these during the "Do" phase. While doing a final review as a check right before verification, there should be a continuous review process in place that is conducted as the design is designed. By having constant design reviews minor problems in the design can be caught before they become core parts of the design with other parts being designed based on the flawed portion. With these continuous reviews change requests become more important, as ensuring that they are processed quickly will help with ensuring the design progresses more quickly. Without a focus on constantly reviewing the design, minor problems may become big headaches later down the line, especially as the deadline for the project approaches. 

If there are resource pressures or the lack of resources, during the planning stage, the project manager can identify what they need, what manufacturers produce those resources, and how abundant they are with availability, material wise and team member wise. Generally speaking, with the planning stage, the project team is expected to create detailed plans to identify resources and be able to come up with resource allocation plans. The PDCA can be followed in a flexible and prioritized manner, but it should still have that framework in place, so project teams do not diverge away from their goals or forget certain aspects of the project. It can be flexible since developing devices do not particularly go as planned 100% of the time and to act on any changes necessary for the project’s performance and safety. With PDCA, that framework can be used to adapt any changes or different situations at hand. AI can be incorporated to optimize PDCA since the technology can be used to analyze and monitor data faster, perform time-consuming tasks and tests, or even suggest changes or the next steps. AI can be faster and reduce human bias and error in some cases. It can be used to determine which tasks should be prioritized based on the results gathered and the goals of the project with the timeline and deadline set by the project team and manager.
Design reviews and design change requests are most important with the monitoring and controlling process group or check stage. Verification tests are important for design control, design reviews, and device change requests. As mentioned in Dr. Simon’s lecture, the design review meetings occur in the monitoring and controlling stage or check phase and this happens at the end of every stage with input, verification, validation, and transfer. These serve as interim meetings where they must check the different designs and controls to approve the documentations in terms of tests and protocols made. This phase serves as a checkpoint for approval before moving to the next stage. Again, documents are being reviewed and changes are brought up if there are issues at hand. Finding the root cause why some of the tests are not working can help project teams find ways to bypass that to enhance performance and the planned design. They can use that time to analyze the data they have collected and compare it to the actual or planned data they want for the device performance, safety, and effectiveness. 
To follow up, there are many cases where project teams fail to acknowledge the check phase and sometimes skip it even though it is crucial to have a design review and discuss any changes needed for enhanced performance. Why would some project teams forget, skip, or neglect the check phase in the PDCA cycle and what would the consequences be?

Design reviews and design change requests are most integral during the Check and Act phases. During the Check phase, verification activities are performed, enabling teams to assess whether outputs truly meet design inputs, user needs, and regulatory requirements, or only meet milestones. Risks are also evaluated here, and verification gaps are uncovered, making this a good point in the process to consider whether a design change is necessary. Design change requests become important in the Act phase because they can be incorporated earlier. If delays extend beyond these two stages, issues may compound, leading to costly rework and compliance challenges. 

Project managers should leverage temporal pressure as a tool for decision-making rather than a source of challenge, as it helps identify which requirements are truly essential for patient safety and regulatory success. Thus, PDCA can be a structured and effective way to justify decisions, as it is grounded in data rather than urgency alone. How can project managers balance temporal pressures with meaningfully pausing for reviews?

Design review and changes are going to be most prevalent in the check stage of the PDCA. The PDCA clearly outlines the steps and processes used to develop a system or device and gives a guideline for any who are working on a project; the check phase will be where a device is scrutinized and cross examined against any constraints or objectvies the project had set out initially. As far as optimization, it depends heavily on the individual project. For some projects material constraints may be a forefront, for others perhaps a maintenance or longevity issue; overall the two major constraints that will be taken into account are cost and safety. Every project needs to adhere to these because if the FDA deems the device unsafe it will never go to market, and if the cost is too high where no one will buy it or too low where the company cannot turn a profit, the company will never continue to back the device's development. Ultimately the point of a project is to turn it into a good that can be sold for profit, as such, often the device's performance in the market is what is most heavily considered. 

Reviewing designs and design change requests are most critical during the Check and Act phases in the PDCA cycle. The PDCA provides a comprehensive outline for developing a device, from planning and testing to improving the design. During the Check phase, the design is thoroughly reviewed and analyzed to ensure that it functions properly and meets all the project’s specifications and requirements. The Act phase involves making improvements based on the findings from the design review, which helps fix problems and improve the design further. The project manager’s approach to prioritizing these activities varies from project to project. While safety and compliance considerations may be the main concerns for some projects, others may have time or resource limits. Safety and compliance are always the primary concerns because, without compliance, the device will not be approved or used. Resource management is critical in the project because reviewing and updating areas with the greatest impact will keep the project on track. The ultimate goal is to develop a functional, safe, and compliant device for its intended purpose within the budget and time constraints.

From the responses, I see that many focus on the significance of the Check and Act phases of the PDCA cycle, which is valid. However, I would like to emphasize that the plan phase is just as valuable since it has the most long term impact since it defines how effective design reviews can be in the product life cycle. In the planning phase, defining the correct design inputs, but also the criteria is essential to determine what parts can be handled through brief revisions and how change requests can affect risks, costs, and regulatory compliance. Standards must be set up early on and must be clear so design reviews can be clear and decisions can be made with informed judgments instead of being reactive.
A PM can prioritize the challenges with intention only if there has been a deliberate pathway through predefined criteria. Standards that are not clear can potentially impact the risk of a patient and cause regulatory challenges. A PDCA will be much more effective through these methods and does not have to be revisited after problems if it is structured as a backbone for a project. It is important to question if a current PM finds these proactive means to prevent reworking later on in the PDCA cycle?