I think the thing that makes the project management role so interesting is that you do not necessarily need to have a deep level of understanding in one particular field or discipline. I find that the best project managers are those that have a background related to the field they are a part of, but also have general knowledge of the other disciplines of those working under them. Because PM's mostly focus on meeting regulatory requirements, design controls, validation, etc. I think it makes sense for a PM's main specialty to be centered around regulatory/quality engineering. That way they are familiar with the project development process and understand design controls, risk management, and validation processes ultimately being able to shape and benefit the project for the better. Rather than focusing solely on a singular discipline or becoming a generalist, a well suited biomedical PM should have a main specialization in the field while also being knowledgeable about the disciplines and biomedical concepts that are the specialization of their team members. What do you believe are effective ways for PM's to effectively build knowledge across different disciplines?

I think that the answer to this is very situational. If, as a PM, you anticipate being in charge of a very niche biomedical product, and future projects you manage will also remain in that niche, it would very much be worth trying to expand your knowledge base as much as possible for that product. However, PM's are human, so I feel that, on top of their regular responsibilities, the chances of project managers being willing to become experts for each and every project they manage are slim. The project manager, as Jacob said, should have a knowledge base in biomedical engineering/science as a requirement, and depending on what company they work for, should highly consider specializing their knowledge within that company's focus. Part of our education as engineers is how to present our findings to non-engineers, so I think that an ideal situation for a cross-disciplinary team is meeting in the middle in terms of specific knowledge. Whose role should it be to ensure that the other parties are aware of the other disciplines' knowledge, do you think?

I agree with Jacob that regulatory or quality engineering are appropriate fields for a project manager to have experience in. Furthermore, a background in quality assurance greatly benefits a project manager. Understanding quality management systems (QMS) and how a company implements its processes and procedures gives insight into the different disciplines involved in medical device development. The technical and soft skills used to conduct audits and manage design controls & regulatory documents can go towards project management, such as attention to detail and problem-solving. 

I believe that a good project manager needs a lot of exposure to industry so they should have extensive work experience in research & development or systems engineering. However, I'm going to focus my response on college work. For an ideal project manager for the development of medical devices, I believe that someone pursuing this area of work should get a bachelors in biomedical engineering then get a masters degree in systems engineering. While a masters in engineering management is an option, I believe systems engineering will help out a lot as medical devices are systems themselves and not one singular product. System engineers focus on design controls, risk management, requirements traceability, and verification and validation. All of these components are key for a project manager to be successful in medical device development. Furthermore, a bachelors in biomedical engineering provides a project manager with a good understanding of medical devices in general and the science behind their development.

I do not believe that there is one specific field that a project manager should specialize in. I believe a project manager's needed background is dependent on the project. For example, at a pharmaceutical company, it may be more important for them to have a strong chemistry and biology base, while at a company that works with orthopedic implants, a mechanical engineering background becomes much more important. I think that it is important that a project manager is somewhat crossed trained in the skills that are needed in the project. Though, it is more important that they have the ability to understand the project, break it down, and be able to keep proper protocol as well, with extensive knowledge of the regulatory conditions needed for the project.

If the project manager had to be specialized in a singular discipline, I would feel that something on the end of quality assurance would be best suited to the job. It deals more with the planning and overall production of a product, and this would teach the PM to think about all parts of the project process.

I agree with how most of the responses highlight regulatory, quality, or systems engineering, but I think there’s another angle that’s just as important: communication and integration across disciplines. Instead of specializing purely in one technical field, a project manager might benefit most from developing cross-functional skills; being able to interpret technical, clinical, and business language and connect them into a coherent plan. In that sense, experience in cross-functional roles could be just as valuable as deep technical expertise because it forces you to think about trade-offs between patient needs, engineering constraints, and market realities. So rather than choosing one discipline to master, I’d argue the most successful medical device PMs are those who understand how all disciplines interact and know how to align them toward a shared goal.

The neat (and maybe painful part) of being a project manager is, that dependent on the industry, you can be expected to be a jack of all trades. In my job for example (working in a medical device manufacturer), the PMs are expected to pick up the slack and essentially act as the glue to slide in between absolutely all and any cracks that present themselves in the projects that they're responsible for.

Naturally, this can lead to a lot of stress experienced by the PMs; conversely, it also leads to a lot of learning and growth opportunities. As the saying goes: A jack of all trades is a master of none, but oftentimes better than a master of one". In my experience, knowing a bit of everything will get you further along as a PM.

I think the project manager should have expertise in a field like engineering but also put in efforts to have broad knowledge of other parts of the project. This is so they can communicate with members in other fields and make final decisions that reflect all the data and findings. If the project manager has little surface-level knowledge in each field, that is not sufficient to make a trusted final decision for a company, especially if there are unexpected test results or challenges that come about. Having expertise in a field will give the project manager an advantage, using the deep data found in his/her department, as well as the reports from the other departments, to make an educated, reliable decision for the company’s future. Also, having expertise in the project allows the manager to ask more targeted questions and understand the impact of decisions better.

Many of the points raised about regulatory, quality, and systems engineering skills being the strong foundation for a PM are essential. Yet, the regulatory or QA aspects shouldn't always be the primary specialization in all cases. I agree that those disciplines are critical/essential for ensuring compliance and safety, especially in an industry such as medical device management where several regulatory agencies apply. Focus on these disciplines only can create bias in decision making towards risk avoidance at the potential expense of actual engineering based decision making. There always needs to be a good balance between the two for a project to properly move forward. For example, a PM with stronger engineering insight or systems insight may be better equipped to understand and handle design trade-offs, technical constraints, and feasibility risks before the project ever reaches the regulatory phase. 
Additionally, I want to push back on the idea that a PM must be a 'Jack of all trades' as it is optimal. As yg385 mentions, it comes with the 'master of none' trade off. Broad knowledge is definitely valuable, however strategic depth in a discipline that informs judgement can be more valuable. Without it, a PM who is a 'jack of all trades' risks becoming a coordinator rather than a leader of a project. 
Ultimately, the most successful medical device PM is one who can adapt their specialization or focus to change based on the aspects of a project. Leaning more technical and system-focused early on, rather than a regulatory focus can pay off in the long run by ensuring project design meets regulation earlier, rather than following regulation after a project has been developed. Situationally it can save time, money, and productivity of a team. 

The most effective medical device PM would be a cross between a specialist and a generalist. Due to the cross-functional nature of MDD projects, a PM's true value may come more from understanding the regulatory backbone of biology, engineering, and as opposed to having an extremely technical understanding of the project, because this would ultimately allow the PM to anticipate integrated risks and coordinate trade-offs. 

If a PM were to ultimately specialize in a field, specializing in regulatory and quality systems would be a salient choice. Such a path of specialization would effectively impact every phase of MDD, so PMs with regulation/quality as a strong suite can better prevent costly delays. However, this does not mean that technical expertise can be ignored, as PMs still need extensive cross-disciplinary knowledge to communicate effectively. 

As the medical device industry evolves, I notice that devices are becoming systemically more complex. In light of this evolution, would PMs with greater technical fluency prove to be better candidates than PMs with a background based in extensive regulatory leadership? 

In regards to project management in medical devices, singling out one field as the best fit would be hard. It would be beneficial if some engineer (be it biomedical or other) would be a good fit, but the experience that comes with it will be the true boon to being a good PM. The PM should try and learn as much as they can, but have to remember the position they are in when making decisions and understanding the work load and what needs to be accomplished. Aiming towards being a broad integrator allows the project manager to be able to evaluate trad offs across the whole lifecycle of the product (to the best of their ability).

One thing I haven’t seen discussed yet is how the best background for a medical device PM might actually depend on what stage of the product lifecycle the project is in. Early on, when concepts are still being refined, a PM with stronger technical or biomedical knowledge may be better off to understand various aspects like feasibility. Later in development, especially as a product approaches verification, validation, and submission, regulatory and quality expertise becomes far more important.

Because of this, I don’t think there’s a single ideal discipline to specialize in across all projects. Instead, the most effective PMs may be those who build depth in one area but are also adaptable enough to shift how they contribute as a project evolves. In one team I worked on, leadership needs changed dramatically once we moved from design to execution, and the PM’s ability to shift their focus mattered more than their original background. This makes me think flexibility and situational awareness may ultimately matter just as much as discipline-specific expertise.

Cross-disciplinary skills are essential for a project manager because they enable effective coordination among teams with diverse expertise, backgrounds, and priorities. A successful PM must be able to communicate clearly across technical and non-technical domains, translating complex concepts into actionable tasks while ensuring all stakeholders share a common understanding of project goals. Strong systems thinking allows the PM to see how decisions in one area—such as engineering, regulatory, or business—impact the entire project, while adaptability and emotional intelligence help manage differing work styles, expectations, and conflicts. Together, these cross-disciplinary skills allow the project manager to align teams, manage risk, and drive projects forward efficiently despite complexity and uncertainty.