In a medical device project setting, I believe that the most effective way of conveying lessons learned would be in the format of a PowerPoint presentation. The lessons learned section is necessary for these types of projects because how much of medical device development requires using other people's research to adapt off of. An effective lessons learned section allows others to understand the pitfalls, cutbacks and overall issues that the researchers underwent in a concise format. A PowerPoint presentation offers another layer to this information to be conveyed through how the slides are structured through images, changes in schedules or even graphs when applicable. Typing the information out in a word document can also used truthfully, but I would agree that with an important enough project that some of the information may be lost only shown through text. It would be much more engaging to learn about the more data heavy information through slides in a more concise method.

Capturing lessons learned is very important especially in fields such as medical device development where similar regulatory and design challenges appear repeatedly. In my experience working on engineering projects, a simple but structured format works best like something like a short “lessons learned” template that includes the issue, what was done, the outcome, and recommendations for future projects. This keeps the information concise and easy to review later. In terms of platforms, shared knowledge systems such as Confluence, SharePoint, or a centralized project database can be great because they allow teams to organize lessons by project phase, device type, or regulatory stage. This makes it easier for future teams to quickly search for relevant insights. I also think it is important that documenting lessons learned becomes a routine step during project closeout meetings so the knowledge is captured while it is still fresh, just as all documentation.