Lean RA https://bsmlean.com/ en The Trouble with Dedicated Resources: Leveling the Workload https://bsmlean.com/blog/adrian-fegan/trouble-dedicated-resources-leveling-workload <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div class="field field--name-dynamic-token-fieldnode-author-picture field--type-ds field--label-hidden field--item"> <img loading="lazy" src="/sites/default/files/images/userpics/blog-adrian-fegan.jpg" width="49" height="65" alt="" typeof="foaf:Image" class="img-responsive" /> </div> <div class="field field--name-dynamic-token-fieldnode-article-meta field--type-ds field--label-hidden field--item">Published by Adrian Fegan in <a href="/blog/category/lean-laboratory" hreflang="en">Lean Laboratory</a>, <a href="/blog/category/lean-qa" hreflang="en">Lean QA</a>, <a href="/blog/category/lean-rd" hreflang="en">Lean R&amp;D</a>, <a href="/blog/category/lean-ra" hreflang="en">Lean RA</a> on January 17, 2019 </div> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><blockquote><p> Dedication of resources may seem like a good way to have “Subject Matter Experts” (SMEs) get through work quickly, but it gives rise to a costly productivity penalty.  The antidote is to level the workload across the team (without compromising the important role of the SME!). </p></blockquote> <p>Within all areas of business it is common to find specific activities being assigned to dedicated people.  Tasks of all types and frequency can be found with dedicated resources, e.g. daily tasks: ‘We have two people every day testing sterility’, or less frequent tasks: ‘I am in charge of reviewing all the incoming raw material data’.</p> <p>In some cases the work is assigned to single people, e.g. ‘I do all the incoming raw material sampling and he reviews all the printed materials’, or to small groups of people, e.g. ‘My team does the testing for all the new products with X API’.  Or, more generally, dedicating individuals to specific work streams as “Subject Matter Experts” (SMEs) is often used as a strategy to get work done efficiently, especially if tasks are seen as highly specialized. </p> <p>At BSM, assessments have shown time and time again that work streams in QC and R&amp;D labs, QA groups, and Regulatory Affairs (RA) groups, rarely have a steady enough flow of work to be suitable for the use of dedicated resources.  However, despite this day-to-day or weekly workload volatility, for several reasons (such as the “SME argument”), we find dedicated resources, and the ensuing symptoms of backlogs, stress, and a costly productivity penalty.</p> <p>The graph is an example of product testing workload for three dedicated QC testing groups in an R&amp;D lab.  Each group had a fixed resource, and was dedicated to specific products.  The aim had been for the products to be divided between groups, so that each group could specialize, and also have about the same workload, to match their resources.</p> <p><div data-embed-button="images" data-entity-embed-display="view_mode:media.full_width_image" data-entity-embed-display-settings="[]" data-entity-type="media" data-entity-uuid="061a74a1-e71f-49d0-978b-f906a50066b6" data-langcode="en" class="embedded-entity"><div> <div class="field field--name-field-media-image field--type-image field--label-visually_hidden"> <div class="field--label sr-only">Image</div> <div class="field--item"> <picture><source srcset="/sites/default/files/styles/full_width/public/images/testruns_perweek.jpg?itok=ekokvjWY 1053w" media="all and (min-width: 1200px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/testruns_perweek.jpg?itok=UZYMCeX9 600w" media="all and (min-width: 992px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/testruns_perweek.jpg?itok=UZYMCeX9 600w" media="all and (min-width: 768px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/testruns_perweek.jpg?itok=UZYMCeX9 600w" media="all and (max-width: 767px)" type="image/jpeg" sizes="100vw"></source><img src="/sites/default/files/styles/third_width/public/images/testruns_perweek.jpg?itok=dXHRS3qJ" alt="Test runs per week per group" typeof="foaf:Image" class="img-responsive" /></picture></div> </div> </div> </div> However, what seemed like an even distribution of work over the long term, proved to be very volatile in the shorter interval (daily and weekly).  For example, the weekly number of test runs for one group varies between 4 and 33 (excluding weeks with holidays).  </p> <p>Bucketing the workload into specific teams caused the members of each team to have a volatile workload and hence increased stress in the work environment: when one team had very little testing to do (a cause of stress in its own right!), another team was working late evenings and weekends to meet deadlines.</p> <p>But when the combined workload for the whole lab is considered the variation is significantly less: between 35 and 76.  This can be seen visually in the graph above.  So clearly the lab would get the benefits of repeatability and predictability that would come with levelling the workload across the groups.</p> <p>As part of a Lean lab, Lean QA or Lean RA project we help develop tools and put in place mechanisms which allow for the easy redistribution of work among team members.  This is not to suggest that there is not a place in organizations for SMEs.  It is still possible to level workloads, and respect the need for having specialists deal with certain tasks.  In fact, most Real Lean implementations free up the time of specialists to do their specialized work!</p> <p>The role of SME is very important; however, it’s worth noting that it can become the case that SMEs become experts in a particular test or work stream at the expense of other people being trained in these skills.  Leveling the workload also requires (&amp; encourages) more cross training within teams.  This in turn can lead to personal development opportunities for people and a great satisfaction in the work place as people become able to work on new things. Another benefit of distribution of work is that it can encourage greater communication between previously isolated people and resources. This leads to greater knowledge sharing and the opportunity for other improvements when tasks are being undertaken by a ‘fresh set of eyes’.</p> <p>While it feels comfortable to have tasks assigned to specific people or groups there is a significant productivity penalty to the business, coupled with higher stress for the employees. This loss can be recovered by leveling the work load and distributing the work among the team, leading to a more predictable work environment for everyone.</p> </div> <div class="field field--name-field-postscript field--type-text-long field--label-hidden field--item"><p>Our consultants can provide further information on the above and discuss any aspect of Real Lean Transformation, simply <a href="/set-call">set-up a call</a> today.</p> </div> <div > <button class="btn btn-category" > <a href="/taxonomy/term/20" hreflang="en">Levelling</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/76" hreflang="en">Levelling the workload</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/28" hreflang="en">Standard Work</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/8" hreflang="en">Lean Lab</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/13" hreflang="en">Lean R&amp;D</a></button> </div> </div> </div> Thu, 17 Jan 2019 21:36:24 +0000 Adrian Fegan 58 at https://bsmlean.com Labelling Updates in Regulatory Affairs: Is product specific dedication of resources a good idea? https://bsmlean.com/blog/gary-ryan/labelling-updates-regulatory-affairs-product-specific-dedication-resources-good-idea <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div class="field field--name-dynamic-token-fieldnode-author-picture field--type-ds field--label-hidden field--item"> <img loading="lazy" src="/sites/default/files/images/userpics/gary-ryan.jpg" width="49" height="65" alt="" typeof="foaf:Image" class="img-responsive" /> </div> <div class="field field--name-dynamic-token-fieldnode-article-meta field--type-ds field--label-hidden field--item">Published by Gary Ryan in <a href="/blog/category/lean-ra" hreflang="en">Lean RA</a> on April 11, 2018 </div> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><blockquote><p> Managing changes to the content and format of product labelling is a key function within any Regulatory Affairs Organisation. Such functions are typically structured by therapeutic area, where each provides support for a reasonably small group of specific products. </p></blockquote> <p>This may sound like a good idea as it provides each therapeutic area with a fixed point of contact and the opportunity to work with people who have some knowledge of the labelling content and previous updates for specific compounds. However, organising in this manner carries a significant cost.</p> <p><div data-embed-button="images" data-entity-embed-display="view_mode:media.full_width_image" data-entity-embed-display-settings="[]" data-entity-type="media" data-entity-uuid="cb912937-fcc1-42f1-b5ce-4f60a67f1afc" data-langcode="en" class="embedded-entity"><div> <div class="field field--name-field-media-image field--type-image field--label-visually_hidden"> <div class="field--label sr-only">Image</div> <div class="field--item"> <picture><source srcset="/sites/default/files/styles/full_width/public/images/cov.jpg?itok=uwnuGXpG 882w" media="all and (min-width: 1200px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/cov.jpg?itok=GeZhokV7 600w" media="all and (min-width: 992px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/cov.jpg?itok=GeZhokV7 600w" media="all and (min-width: 768px)" type="image/jpeg" sizes="100vw"></source><source srcset="/sites/default/files/styles/half_width/public/images/cov.jpg?itok=GeZhokV7 600w" media="all and (max-width: 767px)" type="image/jpeg" sizes="100vw"></source><img src="/sites/default/files/styles/third_width/public/images/cov.jpg?itok=c_Oilc2s" alt="The impact of dedicated groups with volatile workloads" typeof="foaf:Image" class="img-responsive" /></picture></div> </div> </div> </div>  </p> <p><strong>Figure 1. The impact of dedicated groups with volatile workloads</strong></p> <p>The graphs show the number of updates which each of the dedicated groups must manage on a weekly basis. The coefficient of variance (CoV – a normalized measure of volatility) for each is 0.5. If lead-times are to be maintained these groups would individually need to manage up to 12 updates per week (a total of 36 for the three groups). This could be achieved by either over-resourcing each group to the maximum capacity or by over-burdening people in busy weeks requiring them to work overtime.</p> <p> If we look at the alternative where the three have been combined into one group the CoV has been dramatically reduced to just 0.1, and the peak number of updates has dropped to 24 (a 33% reduction).</p> <p>We have observed that in managing labelling updates, process knowledge (being able to navigate the different types of updates and the various IT systems involved) is much more critical than any knowledge relating to specific compounds. Organising resources based on process allows us to operate in the manner outlined on the right of <strong>Figure 1</strong>, where different work-streams have been combined.</p> <h2>Lean tools for Regulatory Affairs</h2> <p>In order to enable us to implement this approach to “Lean Labelling” a number of tools / lean practices must first be put in place.</p> <h3><strong>Structured queuing</strong></h3> <p>All projects are entered in a centralised tracker, their work content estimated, and each placed in a queue according to order of priority.</p> <h3>Level loading</h3> <p>On a daily / weekly basis individuals in the group are assigned a fixed amount of work according to the level demand.</p> <h3>Flexible outsourcing</h3> <p>Despite our best efforts spikes in regulatory workload may still be inevitable and having a flexible outsourcing partner to act as a release valve during the busy periods is an important additional levelling tool.</p> <h3>Standard work</h3> <p>A standard and repeatable set of activities is documented for each task.</p> <h3>Performance management</h3> <p>KPIs for process and people are developed which allow for proactive identification and resolution of issues / opportunities for continuous improvement.</p> </div> <div class="field field--name-field-postscript field--type-text-long field--label-hidden field--item"><p>Our consultants can provide further information on the above and discuss any aspect of Real Lean Transformation, simply <a href="/set-call">set-up a call</a> today.</p> </div> <div > <button class="btn btn-category" > <a href="/taxonomy/term/53" hreflang="en">Lean in RA</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/54" hreflang="en">Regulatory Affairs</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/55" hreflang="en">Labelling. Lean Regulatory</a></button> </div> </div> </div> Wed, 11 Apr 2018 16:20:24 +0000 Gary Ryan 43 at https://bsmlean.com Lean in Regulatory Operations https://bsmlean.com/blog/alan-maloney/lean-regulatory-operations <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div class="field field--name-dynamic-token-fieldnode-author-picture field--type-ds field--label-hidden field--item"> <img loading="lazy" src="/sites/default/files/images/userpics/alan-maloney.jpg" width="49" height="65" alt="" typeof="foaf:Image" class="img-responsive" /> </div> <div class="field field--name-dynamic-token-fieldnode-article-meta field--type-ds field--label-hidden field--item">Published by Alan Maloney in <a href="/blog/category/lean-ra" hreflang="en">Lean RA</a> on July 25, 2013 </div> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><blockquote><p>BSM have been pioneering applied research into the utilization of Real Lean methodologies to solve problems and generate efficiencies in Regulatory Affairs Operations (Reg Ops) in large life science companies. Operations from a Regulatory perspective encompasses the standard activities that accompany the filing of Regulatory submissions such as Labelling, Publishing, Production, Archiving etc. <a href="/real-lean">“Real Lean”</a> is the term used to describe BSM’s approach to implementing Lean in a wide variety of industrial settings. We use this term to distinguish our approach from generic Lean implementations which primarily focus on elimination of the seven wastes. “Real Lean” has at its core a commitment to incorporate the key principles of Levelling, Flow and Standard Work as a basic operating system.</p></blockquote> <p>BSM have demonstrated that the concepts of “Real Lean” are equally applicable and effective in <a href="/real-lean/lean-regulatory-affairs">Regulatory Affairs Operations</a> and have developed a skill set capable of transforming Reg Ops groups into highly efficient, high quality, highly compliant and low cost operators.</p> <h2>Key challenges for Regulatory Operations</h2> <h3>A. Process Harmonisation</h3> <p>Many large multinational life science companies have evolved as a result of multiple mergers and takeovers of smaller organizations. When a small company is assimilated into a larger organization, the Regulatory Affairs (RA) department will often remain in situ as a satellite office retaining the support function for the products that the parent once produced. This coupled with poor harmonization of processes can result in the same basic activities/functions being executed very differently within the same company, a potential compliance issue.</p> <h3>B. Workload Volatility</h3> <p>The submission profile for any large life science multinational is likely to be inherently volatile. This volatility is present at a number of levels, each causing difficulties from an operational perspective.</p> <p>The causes of the volatility can be both internal and external. Examples of external volatility sources are ad hoc requests and directives from Health Authorities which can have a considerable impact on the overall workload, particularly if they coincide with a period of intense activity on large applications. There is nothing that can be done to “level” external sources of volatility as they are outside the control of the company.</p> <p>Measures can readily be taken to address the internal sources of workload volatility and significant improvements can be made provided you have the support of all process stakeholders. The main sources of internal volatility are;</p> <ol> <li>Unanticipated moving of submission dates</li> <li>Unlevel loading of new product launches</li> <li>Rework (caused by lack of built in quality)</li> <li>Personnel dedication</li> </ol> <p>In our experience, most Reg Ops departments are significantly over-resourced in order to cope with the volatility in their process. We term this the Volatility Penalty, and unless specific measures to reduce the impact of volatility are taken, the company will be shouldering this considerable cost burden for a very long time. </p> <h3>C. Lack of Flow</h3> <p>Delays and inefficiencies (lack of Flow) throughout the R&amp;D value stream and in the submission building process accumulate and manifest at the end of the Regulatory value stream (i.e. Reg Ops). A constant flow of urgent submissions leads to significant Work-Life Balance issues for employees as stress levels increase proportionally with the urgency level.</p> <h3>D. Lack of Appropriate Metrics</h3> <p>Reg Ops managers will be able to tell you how many submissions they process per year, but they are unlikely to have accurate data on Cycle Time, Lead Time, Touch Time, Number of Defects, First Pass Acceptance Rate etc. This is largely a cultural issue as historically there has been much focus on Compliance and little focus on Operational Excellence. Data collection is seen as a burdensome activity and to many the value of collecting information routinely is not clear.</p> <h2>Countermeasures</h2> <p>We have discussed the many issues that a Lean Project Team is likely to encounter in the Regulatory environment. Key elements of BSM’s “Real Lean” solution to address these issues are:</p> <ol> <li>Visualize the workload using queues.</li> <li>Move to a “task experts” model (as opposed to a “product expert” model).</li> <li>Level-load through workload sharing.</li> <li>Isolate routine tasks and introduce Flow.</li> <li>Utilize flexible capacity (outsourcing).</li> <li>Hold frequent workload management meetings or “huddles”.</li> <li>Implement Data Collection As Standard (DCAS) and design appropriate metrics.</li> <li>Develop effective project management and project planning capabilities.</li> </ol> <h2>Benefits of Lean in Reg Ops</h2> <p>The potential benefits of a Lean Implementation in Regulatory Operations include;</p> <ul> <li><strong>Productivity</strong> - Improvements of 400% have recently been achieved</li> <li><strong>Quality</strong> - &gt;2 fold reduction in quality defects achieved</li> <li><strong>Compliance</strong>- Improved project management and workload visibility can reduce audit observations (e.g.  implementation of safety updates in labelling (See recent blog post written by Gary Ryan 'Labelling Updates in RA')</li> <li><strong>Speed</strong> – Introducing Flow and reducing Waste reduces task cycle times.</li> <li>Work Life Balance Improvements</li> <li>Continuous Improvement Opportunities become apparent</li> <li>Provision of additional services- Freed up resources can be used to provide new services according to the business needs.</li> </ul> <p>Over the past few years, BSM have proven that the benefits of a “Real Lean” transformation in the Regulatory Environment are truly astonishing. To our mind it is no longer a question of whether or not Lean theory applies to RA, this has been proven beyond reasonable doubt. The only question is when are you going to use Lean to revitalize and reenergize your Regulatory Affairs Operations groups and gain the competitive advantage that Lean performance brings?</p> <p>Download the free white paper on Lean in Regulatory Operations.</p> </div> <div class="field field--name-field-postscript field--type-text-long field--label-hidden field--item"><p>Our consultants can provide further information on the above and discuss any aspect of Real Lean Transformation, simply <a href="/set-call">set-up a call</a> today.</p> </div> <div > <button class="btn btn-category" > <a href="/taxonomy/term/17" hreflang="en">Real Lean</a></button> <button class="btn btn-category" > <a href="/taxonomy/term/30" hreflang="en">Lean RA</a></button> </div> </div> </div> Thu, 25 Jul 2013 15:10:12 +0000 Alan Maloney 30 at https://bsmlean.com