Blog

Chapter Communications Blog

Lessons Learned: Enhancing Medical Device Development


Author: Ruggero Paraventi, PMP author

Lessons Learned: Enhancing Medical Device Development Through Experience

 

Having had the privilege of being part of the PMO leadership team in a global medical device company, I have witnessed the crucial role that a well-structured lessons learned process plays within the industry. In this article, I will share our journey in designing and implementing the lessons learned process, emphasizing key elements, challenges faced, and continuous process improvements.

The Essence of our Lessons Learned Process

 

The process that we implemented aimed to reflect real-world experiences and challenges in medical device development, which encompassed learning from both failures and successes. To further develop our process, we consulted literature in the domain, and found advice provided by Nick Milton, in his book “Lessons Learned Handbook” [1] particularly valuable.

Key Elements of the Lessons Learned Process and Tools

 

Definition of Lesson Learned

Upon initiation, we set out to agree a univocal definition for a lesson learned within our organisation. 'Lessons Learned' is a common term for almost every PMO, however, how it is defined and interpreted varies. We found Nick Milton’s definition of a lesson learned most useful - “a recommendation, based on analysed experience (positive or negative), from which others can learn in order to improve their performance on a specific task or objective.” Adopting a similarly clear, single description of a lesson learned paved the way in designing our process.

Identification and Capture

An initial challenge that we faced was that learnings were retrospectively collected at project closure, and in some cases, several months after critical events had occurred. Valuable knowledge had been slipping through the cracks. To overcome this, we introduced a requirement for project managers to ensure that team experiences were documented in a devoted section of their project diaries, as they occurred, throughout the entire project life cycle. Milton underscores the importance of this, stating that "recording experiences and learning is vital to a successful lesson learned process."

Storage and Organization

Owing to a lacking knowledge repository, no uniformity existed in how information was stored, making it difficult to retrieve and apply past lessons. Milton's advice on “organizing knowledge” deeply resonated with us. Establishing a structured repository, and defining meaningful categories for the learnings, ensured that future teams could locate and benefit from recorded knowledge from past projects.

Dissemination

Whilst Milton's perspective is that "lessons should be disseminated to those who need them", we found that our teams were sporadically sharing their lessons with others. To ensure that our process allowed for efficient dissemination, we increasingly emphasized the importance of sharing lessons learned with other teams. Lesson-sharing was added as a standard agenda item for single functional community meetings, such as global PMO meetings or engineering forums (for learnings of more technical nature).

Actionable Improvements

Following Milton's advice that "lessons should lead to improvements", actionable lessons learned were extracted from knowledge repositories as inputs for identifying process efficiency optimisation. In this way we ensured that lessons learned systematically translated into tangible improvements, including the streamlining of project execution. Ultimately, the structured repository of lessons learned became one of the major sources supporting the definition of cross-functional, continuous improvement initiatives within our organization.

Further Improvement of our Lessons Learned Process

After the initial implementation of the lessons learned process, an analysis and evaluation task were defined for the enhancement of the process. This was introduced because of the known benefits of continuous improvement. This task was assigned to a dedicated resource, skilled in both LEAN principles and process analysis methods.

To refine and further optimise the process, LEAN workshops were conducted using virtual collaboration tools to enable optimal participation of our global PMO community. These workshops allowed our lessons learned subject matter experts to identify bottlenecks and inefficiencies, brainstorm solutions and enhancements, and gather inputs for process effectiveness changes.

The Importance of Uniformity and Quantification

The consideration of LEAN principles guided us in the retrospective analysis, highlighting the importance of two major focal elements for streamlining our lessons learned process, namely Uniform Generic Formulation, and Quantification of Impact.

The importance of having a standardized, generic format for lessons learned was recognized, because non-standardized formulations hindered the effectiveness of transference of lessons learned from one project to another. Implementing a standard syntax ensured that every team could understand and apply these lessons uniformly, avoiding ambiguity and misinterpretation.

Further it was recognised, that only through the consistent impact quantification of lessons learned relating to time, cost, resources, or other critical factors, could a proper prioritisation of learnings be achieved. This in turn enabled the ordered adoption by other projects and continuous improvement initiative selection within the organization. This data-driven approach allowed us to focus our efforts on areas that delivered the most substantial improvements.

 

The Role of Dedicated Software Solutions

In our pursuit of continuous improvement, we also evaluated dedicated software solutions for storing and sharing lessons learned in an integrated manner. Tools such as these provide a structured platform for efficiently capturing, categorising, and sharing lessons within the broader organization, further enhancing the ability to leverage learnings in real-time. Common implementation of such software within affiliated medical device companies was explored, to identify value-adds in up-scaling learning dissemination and use amongst enterprises operating in similar business contexts.

 

Realizing the Full Potential

The ability to learn from experiences is clearly indispensable, in the medical device sector as in any other industry. Through the implementation of a refined Lessons Learned Process, tailored to specific organisational needs, we better positioned our teams to avoid common pitfalls, reduce errors, and prevent costly delays. Learnings from past failures and successes also began to generate process streamlining initiatives, expedite development, and reduce time-to-market. Through understanding of pitfalls and key elements of this process, and continuous refinement of the process through LEAN principles, the organisation became committed to the practical transformation of knowledge into action. Together with the future incorporation of technology, and further incorporation of past learnings into key risk management documents, this process lays the foundation for successful leveraging of past experiences.

 

A Heartfelt Thanks

I would like to extend my heartfelt thanks to Mrs. Rosablanca Paez, who led the continuous improvement efforts, and guided our PMO team through the LEAN workshops. Her passion, expertise, and dedication were instrumental in advancing our Lessons Learned Process.

 

References:

[1] Nick Milton, “Lessons Learned Handbook – Practical Approaches to Learning from Experience”, Elsevier Science & Technology (2010)

 

Product Owner Secrets - an interactive workshop

Author: Katalin Juhász, PMP

Katalin Juhasz photo

The Product Owner (PO) role is sometimes misunderstood yet critical in Agile projects. The Switzerland chapter of PMI has organized an exciting interactive online event again on 13th October, where we could learn about this often overshadowed role. Besides discussing the secrets of the PO role - living up to the expectations of the title of the event - the participants also had the opportunity to gain a first hand experience about an facilitation method, called the fishbowl conversation format, applied in the online space. This method is built on premises, such as the value of experiential learning, assertiveness and the power of discussions, enabling an impactful learning experience. Personally I found the format just as valuable as the shared knowledge about the product owner role itself. Killing two birds with the same stone and all within 90 minutes.

 

The session was hosted by Patryk Nosalik, PMP, agile PM, project manager of the PMI Romandie Events team,  while facilitated by Maria Cortés Astudillo and Nicolas Pages, members of Agile Suisse. María is an industrial engineer, PMP, Professional Scrum Master, Professional Product Owner and Empowering People at the Workplace certified, with over 15 years of experience, successfully building and launching digital applications across multiple channels and formats. Nicolas has more than 20 years of experience in the IS/IT software industry, including 12 years in the supply chain domain acquired in Nestlé. He is a junior coach in design thinking, certified Scrum master and product owner.

 

After some introduction about the fishbowl format, four volunteers were recruited to join the imaginatory “inner circle”. The selection criteria for the volunteers was to already have experience about the product owner role (either by fulfilling this role earlier, or being close enough to a PO to have a good enough understanding of its requirements and challenges). 

The discussion has been kick-started by the four volunteers who shared their views about the “good”, the “bad” and the “ugly” aspects of the product owner role. Not only the facilitators, but also the volunteers had an impressive amount of accumulated experience, making sure the discussion was exciting enough to pin the observers in the outer circle to their screens. After 7 minutes, the observers had the chance to pair up in the breakout room, to discuss what additional questions they would like to ask from the experts in the inner circle, once everyone returned into the virtual plenary room.

 

We learnt that:

  • The biggest challenge and value of the PO role is how to maximize the customer value, while managing the (often latent) customer needs and taking into account the (capacity or technical) limitations of the available resources. 
  • A key to maximizing the customer value requires the mastering of prioritization, communication (where listening weights with double score) and good negotiation skills. It is also invaluable to have a crystal clear product vision.
  • Things can be ugly sometimes, as the PO is right in between the customer and the developer team, trying to carry out a balancing act in a never easing pressure. One wise advice was to accept the fact that it is impossible to make everyone happy at the same time, but instead aim for maximizing the customer value, while considering realistically what is possible.
  • While having a good understanding of the developer group is essential to be able to ask the right questions, it might make it more difficult for a PO to have a technical background, as it carries the risk of being dragged too much into the details of the solution. The PO has to keep focus on the “why” and “what” and strongly resist the temptation to design the “how”. 
  • Trust is a crucial resource in this constellation, as the control of designing the solution, along with estimating the resource needs falls under the responsibility of the developer team. Moreover, the PO also has to recognize the limitations of his knowledge and capabilities, to know when it is better to rely on others.
  • While the agile approach can be used in organizations preferring the waterfall approach, it takes a lot of effort to manage expectations and help the client understand how the process will be different. Clarifying, and repetitively refreshing the definition of the PO and SCRUM master could be also indispensable. 

 

While experimenting with a new format is always a risk, based on the feedback of the participants, the session was indeed very effective in helping them to get a deeper understanding of the product owner role. It also served as proof that well designed online events supported by the right technology can be just as effective as physical encounters. Witnessing the continuously improving online facilitation capabilities of these events, I feel assured that we can expect a maintained level of quality, when it's about exchanging knowledge within the PMI community.

 

We hope to continue hosting more online open space events in the future to come. Therefore we encourage all PMI members if anyone is keen to help in being part of the organisation of creating a regular cycle of interactive Open Space events, then please get in touch with Patryk Nosalik

Patryk Nosalik

 

The recording of the full event is available here.

 

Katalin Juhász, PMP

Organizational Developer at SonarSource

Product Owner Secrets Workshop – a continuation of a journey of discovery

Author: Patryk Nosalik, PMP

Late last Spring, PMI Switzerland held its first Open Spaces meeting. It was really warming to see so much genuine enthusiasm for a novel meeting format, on top of that, we did it online. And when I hear many people are missing the human networking component in other more typical webinars, one of the benefits of interactive formats is that it allows for the creation of meaningful connection. So it was here, from the people contributing and participating in the Open Space, that I was introduced to two very engaging Agilists, María Cortés Astudillo, and Nicolas Pagès.

It turned out Maria and Nicolas were keen to work with me and colleagues at PMI to create another interactive workshop, based on their successful experiences in the Agile Suisse community (agilesuisse.ch). They proposed a discussion about the Product Owner role. 

A quick search or browse of LinkedIn suggests the Product Owner (PO) is a much misunderstood or unappreciated role, and personally in the way this role was applied in my previous professional context, also left me with many unanswered questions. I’d love to share them with you, but the unique point of this workshop is that the participants who register are invited to send in via a form their 1-3 questions they have about the product owner role, be it as naïve, profound, basic, deep, personal or general as they like. Therefore, in order to not bias the event agenda before its inception, I’m having a tough time not sharing them with you! 

Nevertheless I shared this concept with both my Romandie events colleagues and Online Events back in July. We have now created a workshop you can see on our events page, https://pmi-switzerland.ch/index.php/events/events-list/product-owner-secrets-an-interactive-workshop

and invite you warmly to both explore the Product Owner role, and to experience this meeting format which you can take away and use for your own facilitations. 

The questions we will receive, up to a week before the event, will be analysed by Maria, Nicolas and me. We will create the agenda  probably starting with fundamentals before taking a deeper dive, but it will be wholly dependent on participants' input – so that could be you . Just register and you’ll get the link to the very easy form. It may be that we facilitate the discussion so that knowledgeable participants can answer the question, or it may be that the named expert speakers will do so. Of course we would expect to have time for more open discussion as we go along. 

So if you liked our previous Open Space or want to learn something new and be heard by the community, make a note to join this Product Owner workshop on the 13th October. Our facilitators are María Cortés Astudillo, and Nicolas Pagès. Maria is an industrial engineer, she is PMP, Professional Scrum Master, Professional Product Owner and Empowering People at the Workplace certified. Nicolas is a junior coach in design thinking, certified Scrum master and product owner, and has also practiced roles such as super key user, project coordinator, IT solution expert and in the last year, business analyst. Read more about Maria and Nicolas in their fascinating bios on our events page, and then challenge them with questions about the Product Owner role. Remember, the uniqueness of this workshop and relevance to you depends on those who have sent their questions in at registration (but circa 1-2 weeks before), so don’t delay! 

Finally, such workshops benefit from diversity, so share the message with colleagues on Linkedin, friends at work, it will all help harness a collaborative collective intelligence for the benefit of all participants.

Spoiler alert – if we get as many questions as we estimate, then based on experience, we may do some sort of follow up 3-4 weeks later for the most passionate amongst you!

 

VIRAK Article Understanding and Managing your Stakeholders

Author: Christine Petersen, PMP

When I ask participants in my workshops what the most important reason for failure or success in a project is, most people tell me that it’s all about their five constraints: time, budget, scope, resources and risks. 

Now once we started to analyze the root cause of the success or failure of their project, it was not directly how the five constraints were managed but how they managed their stakeholders’ – and most importantly, their KEY stakeholders’ expectations around these five constraints that made the difference. Project Managers did not identify or understand the key stakeholders in the first place, or the stakeholders did not take their responsibilities seriously.

So what is the difference? Can’t we just say that once we have defined our scope, time, costs, resources and risks, and made sure that these are then managed and kept under control, then the outcome will be a successful project?

Well, it is not that easy. Each of the five constraints need to be agreed upon by the key stakeholders at the start of the project. And once agreed upon – not easy to do – then they need to be managed throughout the project, in order to deliver what was expected.

And this is why I believe that rather than say that the critical success factor of a project is managing the five constraints, I prefer to say that the main route to project success is managing the expectations surrounding these constraints.

When we say we are managing projects, we are mainly managing people, in all their complexity. Their needs, wants, dreams, desires, pasts and futures. Their alliances, politics and goals. In summary: their expectations. And the goal is to find ways to manage our stakeholders’ expectations realistically.

So, how do we start? The first step is to analyse our stakeholders and manage the narrative. Decide who is a stakeholder, and most importantly, who is a KEY stakeholder – those people who can make or break the project. Understand these stakeholders, their concerns, constraints, requirements, expected benefits/disbenefits. Integrate their requirements, expectations and constraints in your plan, and make sure that the expectations that people have about the project can be realistically delivered. 

Start as early as possible by communicating out what the vision for the project is, what are the goals, and the realistic boundaries of what we can achieve. If we let others define these for us, then we are already too late. People already have their own ideas that are then harder to change.

Once we have decided on who will be involved as well as the main vision, goals and boundaries (our “Charter”), then the third step is to spend time with each of our key stakeholders, understanding their point of view, their needs, wants and goals, and making sure that these are aligned with the realities of our project. This takes time. Time well invested in building relationships; creating energy around the project; ensuring common goals and how to achieve these; and clarifying roles and responsibilities.

This builds the foundation for the rest of the project. It helps us create dialogue, remain in contact with all our stakeholders, keeps them aligned with the project as it unfurls, and ensures that the results of the project are accepted. You ensure that you can keep close to them as their expectations change or your plan changes.

Many Project Managers tell me that it takes too much time, that they are told to “just do it” and get the project done (which usually means skip the planning and get straight to the execution phase of the project). But can they really afford to skip the planning and ignore the people who can make or break the project? 

The last step is to keep communicating with your stakeholders throughout the project by continuously managing their expectations. I sometimes see projects fail because the stakeholders are not kept in the loop as the project progresses, they feel out of touch and sidelined, and feel that they are not heard. This will inevitably cause resistance and feelings of distrust, and finally, these stakeholders will stop cooperating, and start actively or passively sabotaging the results of the project. The Project Manager will wonder why the results of the project were not accepted and why they “failed” when the real reason was lack of communication and listening.

In summary, the five steps are: Define your stakeholders, manage the narrative, align the narrative to their expectations, create a dialogue and keep communicating. Each step is a brick in the road to success. So take the time you need, and keep communicating.

Election Committee Announcement 2022

Authors:

Elena Milusheva, PMP 

elena_-_Alp_Camci.jpg

Alp Camci, PMP

alp Alp Camci

In the PMI world, everything starts with our volunteers. And this is valid not only for the newsletter, the website and the events, but also for the chapter strategy and leadership. For the upcoming 2023-2024 election term, we are looking for active PMI Swiss chapter members who:

  • live and breathe the PMI values;
  • have practical ideas how to elevate our chapter to the next level;
  • have a hands-on attitude to co-lead various committees, workstreams and initiatives;
  • can manage complex programs and demanding stakeholders;
  • are willing to stand for the upcoming PMI Swiss chapter elections;
  • can dedicate to a 2 years-volunteer role:
    • Board of Directors
    • Election Committee Member 
    • Finance Auditor;
  • are ready for action, collaboration with great people and a lot of fun!

If we have just described you, please reach out to one of our Board of Directors members or to This email address is being protected from spambots. You need JavaScript enabled to view it. to indicate your interest in standing for election.

The application process will start in August.

Let’s empowers people to make ideas a reality.

Your Election Committee

Elena Milusheva, PMP and Alp Camci, PMP