<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Your RCA Experience by Yvonne Henry</title>
      <link>https://padlet.com/yhenry1/BI321YourRCA</link>
      <description>Make a video to tell us how you have experienced a RCA in your life (job or home).  Answer the following questions:     1. Your experience with a Root Cause Analysis investigation that you have participated in. (remember to respect confidentiality and not mention any company or product brand names)   2.  How do you think the wrong Root Cause being identified from an investigation will impact a company (give 2 examples of outcomes)   3.  What transferable skills do you think are most important to individuals who conduct RCA&#39;s regularly </description>
      <language>en-us</language>
      <pubDate>2018-01-24 14:03:18 UTC</pubDate>
      <lastBuildDate>2026-03-12 03:13:13 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>M. Alejandra Ahumada 301347153</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3310391290</link>
         <description><![CDATA[<ol><li><p>Problem: In a previous job (pharmaceutical industry) I was involved in an RCA investigation due to a non-conformity acquired due to the disorder in the samples to be analyzed. By using the 5'S tool and the fishbone diagram, it was possible to identify the procedures established for inadequate cleaning and organization. Corrective actions included updating standard procedures, staff training and implementing continuous monitoring.</p></li><li><p>Impact of incorrect root cause identification:</p></li></ol><p>Incorrect identification could lead to cross-analysis in samples, error in issuing a final result and non-compliance with standards.</p><p>Additionally, unnecessary costs could arise from having to re-analyze all samples to verify results and also the duplication of work materials.</p><ol start="3"><li><p>Key transferable skills for RCA professionals:</p></li></ol><p>It is absolutely necessary to have analytical thinking to solve problems in the shortest possible time, attention to detail, collaboration and communication in the work team and possible decision making under pressure.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-01-30 21:32:06 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3310391290</guid>
      </item>
      <item>
         <title>Guilherme Sussumu Ueno (301246619)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3312209216</link>
         <description><![CDATA[<p>Food waste was a huge problem in the restaurant where I work as a Baker. For example, many times I took frozen pastries out of the freezer, they were stuck in one big clump, for which I had absolutely no use. I realized that the equipment was not holding a constant temperature because it always broke down; sometimes several times a month. After thinking about it for a while, I told the Chef and my manager that maybe the issue was not with the freezer itself, but an electrical problem. Having only 1 freezer with other 4 fridges running under the same restaurant, especially in summer would overload the system. However, what also catch my eyes was that people were leaving the freezer door open for too long, making things worse. </p><p><br/></p><p>To try to resolve this, I suggested to the Chef and Manager that we could install a system that I had seen in some other professional kitchens, that limits how often the freezer can be opened and sound an alarm if the door stays open for too long. Surprisingly, they agreed with my suggestion and once the new system was implemented, thawed food stopped being an issue, and waste went down, allowing the restaurant to save money. </p><p><br/></p><p>This experience taught me how to find the real root cause of a problem is important. In this specific situation, if we continued to repair the freezer without looking further, there would have been much more waste of food and money. A wrong RCA can lead to bad decisions such as replacing expensive equipment when the real issue is the user behavior. People who frequently perform RCA often develop strong problem-solving skills that allow them to think critically about the different causes, pay attention to details to identify patterns and communicate clearly. These skills can help both professional and personal life. </p>]]></description>
         <enclosure url="https://media1.giphy.com/media/3pqXvSjuC7rgWpYRrr/giphy.gif" />
         <pubDate>2025-02-01 22:38:36 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3312209216</guid>
      </item>
      <item>
         <title>Siddhi Patel - 301281860</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3312689348</link>
         <description><![CDATA[<p>During one of my food science projects, I worked on testing a <strong>rosemary extract-infused pectin-based film</strong> as an alternative to plastic packaging. At one point, we noticed that the film wasn’t effectively preventing microbial growth on blueberries, even though rosemary extract has known antimicrobial properties. Initially, we assumed the issue was due to the extract’s concentration being too low. However, after conducting a <strong>Root Cause Analysis (RCA)</strong> using the <strong>5 Whys method</strong>, we discovered that the real problem wasn’t the concentration—it was the uneven distribution of the extract within the film matrix. This meant that some areas had less antimicrobial activity than others. After adjusting our film preparation method to ensure a <strong>homogeneous dispersion of rosemary extract</strong>, we saw a significant reduction in fungal growth and extended shelf life of the blueberries.</p><p>Misidentifying the root cause in an investigation can have major consequences. For example, if a company incorrectly blames ingredient spoilage on supplier quality rather than improper storage conditions, they might switch suppliers unnecessarily while the real problem persists, leading to financial loss. Another example is misattributing packaging failures to the film’s composition rather than environmental humidity—resulting in wasted R&amp;D resources and ineffective solutions.</p><p>For effective RCA, I’ve learned that <strong>analytical thinking</strong> is essential to break down problems logically, while <strong>attention to detail</strong> ensures that small but crucial factors aren’t overlooked. Additionally, <strong>problem-solving skills</strong> help in applying findings to create effective, long-term solutions. In the food industry, getting to the true root cause isn’t just about fixing a problem—it’s about preventing it from happening again.</p>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/3351262056/ae3ee71d8d31da74d271a74152689551/WhatsApp_Image_2024_11_28_at_19_42_08_6dde4ad2.jpg" />
         <pubDate>2025-02-02 19:12:05 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3312689348</guid>
      </item>
      <item>
         <title>Gurpreet Kaur Bhangu (301395936)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3312751689</link>
         <description><![CDATA[<p>While working at A&amp;W at the airport, we once received several customer complaints about their burgers tasting off. My manager asked me to help figure out what went wrong. We checked the ingredients, storage conditions, and preparation process. After investigating, we discovered that a new team member had mistakenly used the wrong sauce, altering the flavor. To prevent this from happening again, we provided additional training and improved ingredient labeling for clarity.</p><p>Misidentifying the Root Cause in an investigation can have serious consequences. For instance, if a restaurant assumes a food quality issue is due to a supplier when the real problem is improper storage, they might switch suppliers unnecessarily while the actual issue persists. Similarly, in a food production facility, if an equipment failure is blamed on human error instead of a mechanical defect, the machine might continue breaking down, leading to costly delays and inefficiencies.</p><p>Successfully conducting an RCA requires strong problem-solving skills to systematically identify the real issue, communication skills to collaborate with different team members, and keen attention to detail to spot subtle mistakes that could be overlooked. These skills ensure that investigations lead to accurate conclusions, allowing businesses to implement the right corrective actions and prevent similar issues in the future.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-02 21:07:52 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3312751689</guid>
      </item>
      <item>
         <title>Avaniben Rathod(301410514)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3312965300</link>
         <description><![CDATA[<p>A few months ago, I was working in a restaurant. Customers were complaining that their orders were wrong. The manager asked us to find out why this was happening. At first, we thought new employees were making mistakes. But after watching the process, we found the real problem. The order ticket printer was not working properly. Sometimes, it printed incomplete orders, so the kitchen staff missed some items. After fixing the printer, customer complaints decreased.</p><p>If we had blamed only the employees, it would have been unfair. Some workers might have quit their jobs. Also, if mistakes continued, customers might have stopped coming, and the restaurant would lose money.</p><p>To do a good Root Cause Analysis, a person needs to be careful and pay attention to small details. They should also be good at asking questions and working with others to find the real problem.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-03 02:33:01 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3312965300</guid>
      </item>
      <item>
         <title>Sukhjeet kaur (301407574)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3314547746</link>
         <description><![CDATA[<p>During my time working in a restaurant, we noticed an increase in customer complaints about food orders being incorrect. Customers received meals with missing ingredients, incorrect burgers, or sides they hadn’t ordered. To address this, the manager asked me to help investigate the root cause.</p><p>After observing the workflow, I found that new employees were struggling to follow order instructions, and there was miscommunication between the front counter and kitchen staff. Additionally, during rush hours, employees hurried, leading to mistakes. We resolved this issue by implementing a double-check system before serving orders and providing staff training on accuracy and communication.</p><p>If the wrong root cause is identified during an investigation, the actual problem remains unsolved, which can negatively impact the company in several ways.</p><p>Example 1: Increased Customer Complaints and Loss of Reputation</p><p>If a restaurant receives complaints about food quality and incorrectly assumes that the issue is due to ingredient suppliers rather than improper food storage, the real problem persists. As a result, customers continue receiving spoiled or low-quality food, leading to negative reviews, decreased customer trust, and loss of business.</p><p>Example 2: Financial Loss Due to Ineffective Solutions A manufacturing company facing frequent machine breakdowns might incorrectly blame employee negligence instead of faulty maintenance procedures. If they implement unnecessary employee training instead of fixing the actual maintenance schedule, machine failures will continue. This leads to increased repair costs, production delays, and financial losses.</p><p>Through this experience, I developed several transferable skills that are valuable in any workplace:</p><p>•Problem-Solving: I learned how to analyze issues, identify their root causes, and implement effective solutions.</p><p>•Communication Skills: Clear communication between team members helped reduce errors and improve workflow.</p><p>•Attention to Detail: Ensuring accuracy in orders minimized mistakes and improved service quality.</p><p>•Teamwork and Collaboration: Working closely with coworkers allowed us to create a more efficient system.</p><p>•Time Management: Managing orders effectively, even during busy hours, helped improve overall restaurant operations.</p><p><br/></p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-04 02:32:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3314547746</guid>
      </item>
      <item>
         <title>Ha Nguyen Hien Nguyen (301186381)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3314548865</link>
         <description><![CDATA[<p>My Root Cause Analysis Experience. </p>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/3358078165/997e2ea49b4260201106ca54863a044c/video.webm" />
         <pubDate>2025-02-04 02:33:41 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3314548865</guid>
      </item>
      <item>
         <title>Shazia Jawed (301336269)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3316293667</link>
         <description><![CDATA[<p>Last semester, while I was focused on my studies, my husband took over grocery shopping and cooking for a few weeks. During this time, we both noticed a distinct and unexpected change in the taste, texture, flavor, and even the aroma of our food, which became unappetizing. As a result, we found ourselves turning to restaurant food more often, and home-cooked meals were being consumed less. This shift was puzzling and difficult to explain, prompting us to investigate the issue thoroughly.</p><p>I meticulously reviewed all aspects of our grocery shopping, checking both packed and unpacked items, as well as dried and refrigerated goods. I also inquired about any changes in the stores where we shopped during that period, as well as whether any new spices or special ingredients had been used in the cooking process. Despite all these efforts, the root cause remained a mystery.</p><p>Next, I checked the refrigerator to ensure that it was functioning properly and maintaining the correct temperature. Everything appeared to be in order, except for the cooking oil. We had switched to a new brand of virgin coconut oil, which seemed to be the culprit. Upon further inspection, I discovered that the oil was actually a solid, white animal fat that was so hard it didn't melt even on low heat. It was devoid of typical coconut smell, soft creamy texture, and taste. This not only ruined the other ingredients in our dishes but also led to significant food waste.</p><p>Identifying the correct root cause of such issues is critical. If the underlying problem is not properly understood, it can result in further damage and loss, whether in a household or business setting. Implementing corrective actions in the wrong areas will not resolve the problem, and may even worsen the situation. In addition, failure to address the root cause can undermine product quality, leading to dissatisfaction, harm to the reputation, and a loss of consumer confidence. To any company, it could be detrimental to the entire staff.</p><p>The transferable skills which are required for RCA of any problem are consistency, cooperative behaviour, analysing each of the minor detail, and attentiveness.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-05 03:26:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3316293667</guid>
      </item>
      <item>
         <title>Anike Blessing Pauline (301366795)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3318324010</link>
         <description><![CDATA[<p>One evening, I noticed that the bread I had been baking at home kept collapsing in the middle after coming out of the oven. At first, I assumed I was using the wrong flour or that my yeast had expired, so I tried different brands, but the issue persisted. To find the root cause, I carefully analyzed each step by measuring ingredients, adjusting kneading times, and monitoring baking temperatures. After multiple tests, I discovered that the real issue was over-proofing the dough, which weakened the gluten structure. Once I adjusted the rising time, the bread finally came out perfect.</p><p>If I had wrongly identified the cause as low-quality flour and kept switching brands, I would have wasted money without fixing the issue. Similarly, in a company setting, misidentifying the root cause can lead to wasted resources and unresolved problems. For example, if a restaurant blames inconsistent food quality on staff inexperience rather than faulty equipment, they might hire more staff instead of repairing or replacing malfunctioning ovens. Another example is a food manufacturer blaming packaging defects on worker mistakes when the real issue is a misaligned production machine, leading to continued waste and financial losses.</p><p>The most important transferable skills for individuals conducting RCA investigations include analytical thinking to systematically evaluate possible causes, attention to detail to notice small but crucial factors, and problem-solving skills to implement lasting solutions. Effective communication is also key, as findings must be clearly conveyed to ensure corrective actions are properly executed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-06 10:33:50 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3318324010</guid>
      </item>
      <item>
         <title>Diya Patel 301403928</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3319219496</link>
         <description><![CDATA[<p>In my personal experience, I was once involved in a small investigation among my housemates to figure out who had eaten my food from the fridge. This wasn’t a formal investigation by any means, but it was a situation where I had to gather information, ask questions, and analyze the behavior of my roommates. I began by checking if anyone had access to the fridge recently, what time the food was last seen, and if there were any clues left behind. As part of the investigation, I also had to review past instances of food disappearing and cross-reference patterns. Eventually, it turned out that one of my roommates had mistaken my meal for their own, and after reviewing everything, we resolved it by setting clearer food-sharing boundaries. Though it was a lighthearted situation, it demonstrated the basic principles of root cause analysis—gathering facts, identifying patterns, and solving the problem by addressing the underlying issue, in this case, miscommunication.</p><p>If the wrong root cause is identified during an investigation, it can have serious consequences for a company. For instance, if a company identifies an operational error as the cause of a production issue, but the real cause is equipment failure, the company might invest time and resources in correcting human errors, only to have the same issue arise again. This can lead to wasted effort and missed opportunities to fix the actual problem. Another potential outcome could be poor decision-making in response to the wrong diagnosis. For example, if a company assumes customer dissatisfaction is due to poor service when the real issue is faulty product quality, they may waste resources on training staff while ignoring product improvements, leading to continued customer complaints. For anyone conducting RCAs, some important transferable skills include critical thinking to accurately assess data and identify root causes, strong communication to gather insights from different stakeholders, and problem-solving to implement effective solutions that prevent recurrence.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-06 23:53:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3319219496</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3319375914</link>
         <description><![CDATA[<p>In my healthcare role, I participated in a Root Cause Analysis (RCA) investigation when a patient had an adverse reaction to a medication. Through the RCA process, we discovered the root cause was a miscommunication between the pharmacy and nursing staff about the dosage instructions, not the medication itself. Identifying the wrong root cause in healthcare can lead to serious consequences, such as compromised patient safety and inefficient resource allocation. For example, misidentifying a cause could result in continued patient harm or wasted efforts on the wrong solutions. Key transferable skills for conducting RCAs in healthcare include analytical thinking, attention to detail, communication, collaboration, problem-solving, and a deep understanding of healthcare systems to ensure accurate identification and resolution of issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-07 02:32:42 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3319375914</guid>
      </item>
      <item>
         <title>Harmanpreet kaur (301435325)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3319378392</link>
         <description><![CDATA[<p>In my healthcare role, I participated in a Root Cause Analysis (RCA) investigation when a patient had an adverse reaction to a medication. Through the RCA process, we discovered the root cause was a miscommunication between the pharmacy and nursing staff about the dosage instructions, not the medication itself. Identifying the wrong root cause in healthcare can lead to serious consequences, such as compromised patient safety and inefficient resource allocation. For example, misidentifying a cause could result in continued patient harm or wasted efforts on the wrong solutions. Key transferable skills for conducting RCAs in healthcare include analytical thinking, attention to detail, communication, collaboration, problem-solving, and a deep understanding of healthcare systems to ensure accurate identification and resolution of issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-07 02:35:36 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3319378392</guid>
      </item>
      <item>
         <title>Nirali Sivalingam (301318235)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3320380462</link>
         <description><![CDATA[<p><br/></p><p>A few years back as an agriculture student, I was involved in an RCA investigation during a summer internship at a local farm. The farm had been experiencing poor crop yields in their cornfields, despite using the same farming practices as previous years. My team was asked to determine the root cause of this issue. We applied tools like the 5 Whys and Fishbone diagrams to investigate possible factors, including soil health, irrigation systems, and seed quality.</p><p>After a thorough investigation, we discovered that the root cause was a decrease in soil pH due to overuse of certain fertilizers in previous seasons. This led to nutrient deficiencies in the soil, affecting the growth of the corn. By adjusting the soil pH and changing the fertilizer regimen, the farm was able to improve crop yields and prevent similar issues in the future.</p><p>However, I’ve seen the consequences of misidentifying the root cause. For example, if the team had blamed poor seed quality without addressing soil health, they might have wasted money on new seeds and continued to experience low yields. Similarly, blaming the irrigation system when the soil was the true issue would have led to unnecessary repairs, causing delays and unnecessary costs.</p><p>In agriculture, key transferable skills for conducting RCAs include analytical thinking, attention to detail, and the ability to collaborate with multiple stakeholders like farmers, agronomists, and environmental experts. These skills help ensure that the correct cause is identified and that effective, sustainable solutions are implemented to improve agricultural practices.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-07 19:14:23 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3320380462</guid>
      </item>
      <item>
         <title>Prachi Kaintura (301403514)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3320381021</link>
         <description><![CDATA[<p>I recall a personal experience at home that required a Root Cause Analysis (RCA). One evening, I noticed that our electric bill had surged dramatically over the past few months. My family and I decided to figure out the cause to avoid unnecessary expenses. We began by systematically checking all our appliances and electrical devices.</p><p>Through our investigation, we discovered that our old refrigerator was malfunctioning and consuming excessive electricity. To address this issue, we replaced the old refrigerator with a more energy-efficient model. This change resulted in a significant reduction in our electric bill, bringing it back to normal levels.</p><p>Misidentifying the root cause can lead to wasted efforts and unresolved problems. For example, if we had mistakenly blamed the increased electric bill on frequent usage of smaller devices such as our TV or laptops, we might have imposed restrictions on their use without addressing the real problem, leading to continued high bills. Similarly, if a company misidentifies poor-quality materials as the reason for product defects instead of recognizing flaws in the manufacturing process, they might continue to face quality issues even after changing suppliers.</p><p>Conducting RCAs regularly requires transferable skills such as analytical thinking and effective communication. Analytical thinking allows individuals to systematically evaluate data, identify patterns, and draw logical conclusions. Effective communication is crucial for gathering accurate information, ensuring that all stakeholders understand the findings and recommended corrective actions, and coordinating with various departments. These skills are essential for thorough investigations and implementing effective solutions.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-07 19:14:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3320381021</guid>
      </item>
      <item>
         <title>Raj Virani 301349131</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3320513141</link>
         <description><![CDATA[<p>During my time at home, I had to conduct a <strong>Root Cause Analysis (RCA)</strong> when my refrigerator suddenly stopped cooling properly. At first, I assumed the issue was with the thermostat, so I adjusted the temperature settings, but nothing changed. Instead of jumping to conclusions, I took a step back and investigated systematically. I checked the vents for blockages, inspected the door seal for leaks, and finally realized that excessive frost buildup was blocking airflow. The real root cause turned out to be a faulty defrost system. After manually defrosting and replacing the defrost heater, the refrigerator functioned properly again.</p><p>If the <strong>wrong root cause</strong> is identified, it can lead to wasted time and resources. For example, if I had assumed the fridge was broken beyond repair, I might have <strong>spent hundreds of dollars replacing it unnecessarily</strong>. Alternatively, if I had only adjusted the thermostat without looking deeper, the issue <strong>would have persisted, causing food waste and additional costs</strong>. This highlights why proper RCA is crucial in both personal and professional settings.</p><p>Key <strong>transferable skills</strong> for effective RCA include <strong>critical thinking</strong> to assess problems logically, <strong>attention to detail</strong> to catch subtle causes, and <strong>patience</strong> to test different possibilities before jumping to conclusions. Additionally, <strong>problem-solving skills</strong> are essential to finding practical solutions based on the investigation’s findings. These skills apply across many fields, from home maintenance to technical industries, where identifying and resolving issues efficiently is crucial.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-07 22:52:06 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3320513141</guid>
      </item>
      <item>
         <title>jai kaur 301379431</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3320925136</link>
         <description><![CDATA[<ol><li><p>My RCA experience:<br>We had this recurring issue where our product kept failing quality checks. It was super frustrating. We got together as a team and started digging deep. We used the 5 Whys technique, asking "why" over and over until we got to the bottom of it. Turns out, it wasn't just one thing causing the problem - we found out that our supplier had changed their material without telling us and our machine settings weren't adjusted properly. It was like solving a mystery.</p><ol start="2"><li><p> Wrong root cause:<br>Oh man, if we mess up finding the real root cause, it can be a disaster for a company. Here are two examples:</p><p>Wasted time and money: Imagine spending tons of cash on fixing something that wasn't even the real problem. That's just throwing money down the drain.</p><p>Recurring issues: If we don't fix the actual root cause, the problem's just gonna keep coming back. It's like playing whack-a-mole with our problems.</p></li></ol></li></ol><ol start="3"><li><p>Important transferable skills:</p><p>We need to be curious and ask the right questions to get to the bottom of things like a detective.</p><p>RCA is all about working together and getting different perspectives.</p><p> Sometimes the root cause isn't obvious, so we can get creative.</p><p>We need to explain our findings clearly so everyone understands and can take action.</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-08 16:51:22 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3320925136</guid>
      </item>
      <item>
         <title>Mohseena Fatema (301277054)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321048209</link>
         <description><![CDATA[<ul><li><p><strong>Experience with Root Cause Analysis (RCA)</strong>:<br>In my previous role as a baker and food science professional, I participated in RCA investigations related to product quality issues. One situation involved inconsistent texture in a gluten-free product. The RCA involved mapping the production process, analyzing ingredients, and identifying deviations in storage conditions and mixing times. The investigation revealed that variations in the water absorption properties of different flour batches were causing the issue. A new sourcing protocol and tighter process controls solved the problem.</p></li><li><p><strong>Impact of Identifying the Wrong Root Cause</strong>:</p><ul><li><p><strong>Increased Costs</strong>: Addressing symptoms rather than the actual problem can lead to unnecessary expenditures on equipment changes or additional testing without resolving the issue.</p></li><li><p><strong>Damage to Reputation</strong>: Persisting issues may affect product quality, leading to consumer dissatisfaction and negative brand perception if complaints continue.</p></li></ul></li><li><p><strong>Transferable Skills Important for RCA Investigators</strong>:</p><ul><li><p><strong>Analytical Thinking</strong>: Ability to break down complex processes and identify causal relationships.</p></li><li><p><strong>Effective Communication</strong>: Engaging cross-functional teams and clearly documenting findings for actionable resolutions.</p></li><li><p><strong>Attention to Detail</strong>: Ensuring no potential contributing factor is overlooked.</p></li><li><p><strong>Problem-Solving Mindset</strong>: Finding creative solutions and thinking beyond immediate observations.</p></li></ul></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-08 22:36:14 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321048209</guid>
      </item>
      <item>
         <title>BENJAMIN EBOH (301291836)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321080176</link>
         <description><![CDATA[<p><strong>1. Experience with a Root Cause Analysis (RCA) Investigation</strong></p><p>A recurring product contamination issue was initially suspected to be a raw material problem. Using 5 Whys and the Fishbone Diagram, RCA revealed that improper sanitation in a specific production line caused cross-contamination. Corrective actions included enhanced training, updated cleaning protocols, and stricter verification to prevent recurrence.</p><p>4ostricter verification to prevent recurrence.</p><p><strong>2. Impact of Identifying the Wrong Root Cause</strong></p><p>If the wrong root cause is identified, it can have serious consequences for a company. Two possible outcomes include:</p><ol><li><p><strong>Recurring Quality Issues</strong> – If the investigation misidentifies the problem, corrective actions will not resolve the actual issue. This can lead to repeated product failures, increased waste, and higher operational costs.</p></li><li><p><strong>Regulatory &amp; Compliance Risks</strong> – Misidentifying the root cause in food safety incidents can lead to non-compliance with industry regulations. This could result in product recalls, legal penalties, and loss of consumer trust.</p></li></ol><p><strong>3. Transferable Skills Important for RCA Investigations</strong></p><p>Individuals who conduct RCAs regularly need several key skills, including:</p><ul><li><p><strong>Analytical Thinking</strong> – The ability to break down complex problems and systematically identify contributing factors.</p></li><li><p><strong>Attention to Detail</strong> – Ensuring that all possible causes are considered and that conclusions are based on accurate data.</p></li><li><p><strong>Collaboration &amp; Communication</strong> – Working with cross-functional teams to gather insights and effectively communicate findings and corrective actions.</p></li><li><p><strong>Problem-Solving</strong> – Developing and implementing effective solutions to prevent recurrence of issues.</p></li><li><p><strong>Knowledge of Industry Standards</strong> – Understanding regulatory requirements, quality management systems, and food safety protocols to ensure compliance.</p></li></ul><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 01:00:29 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321080176</guid>
      </item>
      <item>
         <title>Gagandeep Singh (301378945)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321524262</link>
         <description><![CDATA[<p>As a warehouse associate, I was once involved in a Root Cause Analysis (RCA) when there was a recurring issue with missing inventory. My supervisor asked me and a few other team members to help investigate why certain products were not matching the records. We checked different areas of the warehouse, reviewed shipping logs, and even observed the loading process. Eventually, we discovered that the issue was due to a labeling error—some products were being placed in the wrong section, leading to miscounts during inventory checks. Once we identified the problem, the company implemented stricter labeling procedures, and the issue was resolved.</p><p>If the wrong Root Cause is identified, it can lead to wasted time and resources. For example, if the company had blamed theft instead of a labeling issue, they might have increased security measures unnecessarily, adding extra costs without solving the real problem. Another consequence could be continued inventory shortages, leading to delayed shipments and unhappy customers.</p><p>The most important transferable skills for conducting RCA are attention to detail, problem-solving, and communication. Being able to analyze data, ask the right questions, and communicate findings clearly helps in identifying the true Root Cause and preventing future issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 18:08:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321524262</guid>
      </item>
      <item>
         <title>Anjana Babu (301431539) </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321560410</link>
         <description><![CDATA[<p>The Case of the Water Leak</p><p>One morning, I stepped into the kitchen and found a small puddle of water near the fridge. Assuming someone had spilled water, I wiped it up, but the next day, the same puddle appeared. This made me realize that I needed to conduct a<strong> </strong>Root Cause Analysis (RCA) to find the source of the problem. I first checked if the fridge was leaking, but everything seemed fine. Then, I noticed that the water dispenser tray was full, and the overflow was slowly dripping onto the floor. After emptying and cleaning the tray, the issue was resolved.</p><p>If I had misidentified the root cause and assumed the fridge was broken, I might have called a repair technician unnecessarily, leading to extra expenses. Another possible consequence of not identifying the true cause could have been mold growth if the water leakage had continued unnoticed.</p><p>This experience reinforced the importance of attention to detail, observation, and logical thinking—skills that are crucial in any RCA process. Whether at home or in a workplace, taking a step-by-step approach to identifying the real problem can prevent unnecessary costs and long-term issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 19:12:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321560410</guid>
      </item>
      <item>
         <title>Mutiu Oyetunde (301334575)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321562669</link>
         <description><![CDATA[<p><strong>1. Experience with Root Cause Analysis Investigation:</strong><br>As a security personnel in a retail store, I was involved in a physical confrontation with a male customer who assaulted the store cashier due to frustration over slow service. I intervened, physically restrained the individual, and removed him from the premises. However, I did not report the incident to the police or my supervisor, believing that since the issue had been resolved, no further action was necessary. This incident highlights the importance of conducting a thorough Root Cause Analysis (RCA) to understand the underlying issues and improve response protocols. If I had participated in an RCA at the time, I would have assessed the sequence of events, identified gaps in security procedures, and recommended improvements.</p><p>The RCA would have involved:</p><ul><li><p>Gathering information from witnesses, CCTV footage, and other evidence.</p></li><li><p>Analyzing the root causes of the altercation, including store policies, staff training, and customer frustration.</p></li><li><p>Identifying corrective actions to prevent similar incidents, such as de-escalation training and better communication protocols.</p></li></ul><p>By reflecting on this experience, I recognize the importance of reporting procedures and structured investigations to mitigate risks.</p><p><strong>2. Impact of Identifying the Wrong Root Cause:</strong><br>Failure to correctly identify the root cause of an incident can lead to significant negative outcomes for a company. Two possible consequences include:</p><ul><li><p><strong>Increased Liability and Legal Issues:</strong> If an RCA incorrectly attributes blame to an individual without considering broader systemic issues, the company may face lawsuits or reputational damage. In this case, failing to report the incident could lead to legal consequences if the customer returns and causes further harm.</p></li><li><p><strong>Recurrent Security Breaches:</strong> If the root cause of the altercation is misidentified (e.g., blaming slow cashiering instead of lack of security protocols), the store may not implement necessary preventive measures. This can lead to repeated violent incidents, endangering employees and customers.</p></li></ul><p><strong>3. Transferable Skills for Conducting RCA:</strong><br>Professionals conducting RCA must possess key transferable skills to ensure thorough and accurate investigations. The most important skills include:</p><ul><li><p><strong>Analytical Thinking:</strong> The ability to systematically assess incidents, gather data, and identify patterns is crucial. RCA practitioners must differentiate between symptoms and true root causes.</p></li><li><p><strong>Communication and Reporting:</strong> Clear documentation and reporting skills are essential to convey findings accurately to stakeholders. Security personnel must be trained to report incidents comprehensively, ensuring management has the necessary information to act.</p></li></ul><p>By applying these skills, organizations can ensure effective RCA processes that enhance safety, security, and operational efficiency.</p><p><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 19:16:04 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321562669</guid>
      </item>
      <item>
         <title>Manpreet Kaur 301307370</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321577734</link>
         <description><![CDATA[<ol><li><p>In a Root Cause Analysis (RCA) investigation, I was involved in analyzing a recurring issue of dough inconsistencies in a pizza store. The investigation involved collecting data on dough preparation, storage, and usage times. We reviewed equipment settings, ingredient quantities, and employee training. By using techniques like the "5 Whys" and flowcharting, we discovered that a temperature fluctuation in the dough-proofing room was affecting consistency. The team then implemented a monitoring system to ensure the temperature remained stable.</p></li><li><p>If the wrong Root Cause is identified in an investigation, it can lead to ineffective corrective actions, wasting both time and resources. For example:</p><ul><li><p>If the investigation incorrectly blames the dough mixer for inconsistencies when the actual issue was temperature fluctuations in the proofing room, fixing the mixer would not resolve the problem, leading to continued product inconsistency.</p></li><li><p>Misidentifying the root cause might also cause the team to focus on unnecessary process changes, such as altering ingredients, when the real issue lies in employee training, leading to increased costs without improving the product quality.</p></li></ul></li><li><p>The most important transferable skills for individuals conducting RCAs regularly include:</p><ul><li><p><strong>Critical thinking</strong>: The ability to analyze data objectively, question assumptions, and logically assess potential causes.</p></li><li><p><strong>Problem-solving</strong>: To devise effective corrective actions based on the root cause.</p></li><li><p><strong>Communication</strong>: Clear and concise reporting to ensure that the team and stakeholders understand the findings and solutions.</p></li><li><p><strong>Attention to detail</strong>: Ensuring no step in the investigation is overlooked, as small details can be key to identifying the true cause.</p></li><li><p><strong>Team collaboration</strong>: Working across departments to gather diverse insights and form a comprehensive understanding of the issue.</p></li></ul></li></ol>]]></description>
         <enclosure url="https://live.staticflickr.com/65535/52205866014_7206957661_b.jpg" />
         <pubDate>2025-02-09 19:40:28 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321577734</guid>
      </item>
      <item>
         <title>Akshita Khaira (301379414)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321600952</link>
         <description><![CDATA[<p>Hey everyone! I wanted to share a time when I had to go through a Root Cause Analysis, and how getting it wrong can really mess things up especially in a fast-food setting like Popeyes. Plus, I’ll talk about the key skills that make RCA investigators really good at what they do. </p><p><br/></p><p>So, I was part of an RCA investigation where customers were complaining that a certain menu item wasn’t as crispy as usual. At first, most people thought the issue was the frying oil maybe it wasn’t being changed often enough. But when we actually dug into it, we found something completely different.</p><p>It turned out the real issue was in the batter prep. The team wasn’t letting it hydrate for the right amount of time before frying, which messed with the texture. Once we fixed that process, the crispiness was back to normal. It was a great reminder that first impressions can be misleading, and you really have to go step by step to find the real cause.</p><p><br/></p><p>Now, what if we had just assumed it was the frying oil and moved on? Well, two things could’ve gone really wrong:</p><ol><li><p><strong>Wasting Time and Money</strong> – If they started replacing oil more frequently, that would’ve added unnecessary costs without solving anything.</p></li><li><p><strong>Customer Trust Issues</strong> – If the product kept coming out soggy, customers might stop coming back. And let’s be real when people crave that crispy Popeyes crunch, they expect to get it every time.</p></li></ol><p><br/></p><p>To get to the real root cause, you need a mix of different skills. Here are three big ones:</p><ol><li><p><strong>Being Super Observant</strong> – Sometimes, tiny details make a huge difference. In our case, just watching how the batter was handled gave us the answer.</p></li><li><p><strong>Thinking with Data, Not Assumptions</strong> – It’s easy to guess, but real problem-solving means checking logs, testing processes, and actually proving what’s going wrong.</p></li><li><p><strong>Clear Communication</strong> – You have to explain findings in a way that makes sense to everyone, from kitchen staff to managers. Otherwise, the fix never actually happens.</p></li></ol><p><br/></p><p>So yeah, RCA is all about finding the <em>real</em> reason behind a problem instead of just guessing. It can save a company a lot of money and keep customers happy. Hope you found this interesting, and if you’ve ever had to troubleshoot a problem like this, I’d love to hear about it!</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 20:25:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321600952</guid>
      </item>
      <item>
         <title>usman javaid cheema (301379157)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321603662</link>
         <description><![CDATA[<p>hey Everyone. As an Uber driver, you’ve likely conducted informal RCAs—such as investigating low ratings by identifying issues like navigation errors or communication gaps. Similarly, in food science, RCAs analyze issues like contamination by tracing their root causes.</p><p><br/></p><p>2. Impact of Identifying the Wrong Root Cause</p><p>Wasted Resources: Misdiagnosing contamination as a storage issue instead of cross-contamination leads to unnecessary costs.</p><p>Regulatory Risks: Blaming suppliers instead of internal sanitation failures can cause legal penalties.</p><p>3. Transferable Skills</p><p>Analytical thinking, attention to detail, problem-solving, communication, and adaptability—all skills you’ve developed as an Uber driver—are crucial for RCA investigations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-09 20:30:51 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321603662</guid>
      </item>
      <item>
         <title>Camille Anne Bumanglag </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321711603</link>
         <description><![CDATA[<p>During one of our nutrition education programs, we faced an unexpected staffing problem. We were short on marshals, and the event was already underway. The only available person who could assist was our assigned driver. Since his task was only to transport us from the warehouse to the venue and he had no driving duties during the event, we asked him to help manage the crowd and support the team on-site. It seemed like the most practical solution at the time to keep things running smoothly.</p><p>However, after the event, the Accounting Department raised concerns. They claimed the situation could be seen as "double compensation" since the driver was technically being paid for tasks outside his usual role. They insisted that his involvement was a form of negligence, implying that drivers should not take on responsibilities beyond transporting staff.</p><p>This prompted a series of discussions between the Accounting, Project Management, and implementation teams. We explained that it was never our intention to misuse resources but rather to make sure the event succeeded despite the lack of personnel. The Accounting Department acknowledged our explanation but emphasized the importance of adhering to defined roles. In response, we agreed to develop contingency plans to ensure that future programs had adequate staffing.</p><p>This experience taught us valuable lessons about communication and problem-solving. While the driver’s efforts were out of goodwill, having proper planning and staffing structures would prevent similar situations in the future. It reminded us how important teamwork and alignment between departments are in resolving challenges effectively.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 00:25:20 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321711603</guid>
      </item>
      <item>
         <title>Meghna (301352562)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3321823076</link>
         <description><![CDATA[<p>1.⁠ ⁠Experience with Root Cause Analysis Investigation: While working at Tim Hortons, I participated in a Root Cause Analysis (RCA) investigation to address inconsistencies in product quality, particularly in baked goods. The issue was identified as variations in texture and consistency. We examined the process, gathered feedback from staff, and used the “5 Whys” method to determine that the problem stemmed from a miscalibrated oven. After adjusting the oven settings and introducing more frequent checks, we saw improvements in product consistency and quality.</p><p>	2.	Impact of Identifying the Wrong Root Cause: If the wrong root cause is identified, it can lead to wasted resources and continued issues. For instance, a company might spend time and money on repairs or changes that don’t address the real problem. In some cases, this could also lead to recurring product issues that frustrate customers and negatively impact the brand’s reputation.</p><p>	3.	Transferable Skills for RCA Investigators: Conducting RCA requires strong problem-solving skills, as it’s necessary to break down complex issues into smaller, manageable parts. Attention to detail is essential for gathering accurate data, while effective communication is crucial for collaborating with team members and implementing corrective actions. Additionally, critical thinking plays a key role in considering all potential causes and ensuring that the right issue is addressed.</p>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/3384124974/3897b2dd51fd6ff743a83a16aa4b5b57/Tim_Hortons__Calgary__Alberta_province__Canada___April_2022___02.jpg" />
         <pubDate>2025-02-10 02:27:22 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3321823076</guid>
      </item>
      <item>
         <title>Juli Fernando (301386791)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3322068124</link>
         <description><![CDATA[<p>1.&nbsp;&nbsp;&nbsp;&nbsp; When I was working in a manufacturing industry in the Philippines, one of my job responsibilities was to facilitate the validation and investigation of customer complaints. On one occasion, customers reported that a pail of products delivered to them contained black specs or sediments settling at the bottom. Upon receiving the complaint, we checked the remaining stocks of the same batch / lot numbers stored in our warehouse and discovered that some of these products also contained black specs or particles. To identify the root cause of the issue, we reviewed production records and interviewed the production personnel who were working at that time. We also conducted a traceability analysis to examine the raw materials used during production.</p><p>&nbsp;</p><p>Our investigation revealed that the black particles originated from one of the major ingredients. Initially, these black specs were not detected in the raw material bags because our incoming material inspection team only performed random sampling and testing based on a predefined sampling plan. Consequently, we raised our concerns with the supplier of this ingredient, who confirmed that a problem with their equipment was causing contamination due to leaching. As a result, they have covered all costs incurred in production, including damages from returned items. Additionally, they replaced all stocks of the raw materials originally delivered to us. &nbsp;In response to this issue, we implemented additional quality checks for the raw materials and revised our procedures for both incoming material inspection and production.</p><p>&nbsp;</p><p>2.&nbsp;&nbsp;&nbsp;&nbsp; Identifying the wrong root cause during the investigation may lead to negative consequences to the company:</p><ul><li><p>The company may implement corrective actions that do not address the actual issue. As a result, product defects may continue leading to increasing and recurring customer complaints and returns and damage to company’s reputation and loss of customer trust.</p></li><li><p>It can also lead to wasted resources, such as spending time and money on necessary corrective actions or training and may result in recurring issues and potential financial losses.</p></li></ul><p>&nbsp;</p><p>3.&nbsp;&nbsp;&nbsp;&nbsp; Some of the transferable skills essential for individuals conducting Root Cause Analysis (RCA) include <strong>analytical and problem-solving skills</strong>, as well as <strong>collaboration and teamwork</strong>.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 06:36:50 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3322068124</guid>
      </item>
      <item>
         <title>Vidhi Dangi (300798874)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3322589212</link>
         <description><![CDATA[<p><strong>Root Cause Analysis Reflection:</strong></p><p><br/></p><p>During my time as a QA technician at a bakery and raw material manufacturer, I was involved in an investigation regarding an issue with a batch of whipping cream that did not meet specifications. The cream had developed an acidic taste, curdling, and fat lumps, which were identified during routine quality checks. Initially, there was speculation that the issue stemmed from a formulation or processing error, but upon further investigation, I discovered that the root cause was improper temperature control during shipping and receiving. The product had been left above 4°C for several hours, leading to fermentation and increased acidity. After presenting my findings, corrective actions were taken to reinforce proper cold chain management.</p><p><br/></p><p>If the wrong root cause had been identified, it could have led to unnecessary changes in production processes, wasting time and resources while failing to prevent future occurrences. Additionally, overlooking the actual cause could have resulted in repeated quality failures, leading to customer complaints, potential recalls, and reputational damage.</p><p><br/></p><p>For individuals conducting RCA regularly, critical thinking and attention to detail are essential. Strong communication skills are also crucial, as findings need to be clearly explained to different teams to ensure corrective actions are properly implemented. This experience reinforced the importance of thorough investigations in maintaining product quality and preventing recurring issues.</p><p><br/></p><p>Thank you,</p><p>vidhi</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 14:00:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3322589212</guid>
      </item>
      <item>
         <title>SRUTHI  THAZHATHEVEETTIL SURESH -301281016</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323088517</link>
         <description><![CDATA[<p>I once took part in an examination using Root Cause Analysis when we ran into a general problem with process efficiency. In order to identify the underlying problem, I had to work with the team to collect evidence, examine important variables, and apply organized techniques like process mapping and brainstorming. In the end, we found that the problem was caused by a procedural flaw, emphasizing the significance of careful research. However, there can be severe repercussions if the incorrect root cause is identified. For instance, it may result in resource waste—spending time, money, and effort on the wrong problem—or harm to one's reputation since persistent problems could undermine stakeholder and customer confidence. Critical transferable abilities including problem-solving, teamwork, and attention to detail are necessary for conducting effective RCA. Critical thinking guarantees&nbsp;collaboration makes use of team knowledge, all options are taken into account, and attention to detail helps prevent the omission of important details that could result in inaccurate conclusions.<br><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 19:18:37 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323088517</guid>
      </item>
      <item>
         <title>Dishaben Patel (301396736)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323142317</link>
         <description><![CDATA[<ol><li><p>I was involved in an RCA investigation after a product at our production facility failed a major quality check. We discovered a texture inconsistency and assumed it was due to machine calibration issues. However, by following the RCA procedure with the help of a temperature log, we determined that the true problem was an unnoticed change in an ingredient supplier's composition. This meant that our product did not reach the desired level, despite the fact that our equipment was functioning properly.</p></li><li><p>Identifying the wrong root cause can have catastrophic implications. First, organizations may take unnecessary corrective actions, such as replacing expensive equipment, while the true problem is elsewhere. Second, misdiagnosing a problem can lead to recurring failures, lose customer trust, and result in financial losses.</p></li><li><p>To do RCA effectively, you must have strong analytical abilities to objectively examine data, communication skills to work across teams, and attention to detail to guarantee that no potential causes are missed. Patience and problem-solving skills are also required to find the underlying root cause.</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 20:02:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323142317</guid>
      </item>
      <item>
         <title>Wardul Zannat (301376597)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323161168</link>
         <description><![CDATA[<p><strong>1. Experience with a Root Cause Analysis (RCA) Investigation:</strong></p><p>As a <strong>sanitation manager</strong>, I participated in an RCA investigation after recurring microbial contamination in the production area. Using the <strong>5 Whys method</strong>, we identified inadequate cleaning of hard-to-reach areas as the root cause. We revised cleaning protocols, retrained staff, and implemented verification steps, successfully reducing contamination incidents.</p><p><strong>2. Impact of Identifying the Wrong Root Cause:</strong></p><p>A wrong root cause can lead to <strong>recurring issues and increased costs</strong>, as unresolved problems cause production delays, recalls, and regulatory fines. It can also result in <strong>reputation damage</strong>, where persistent quality issues erode customer trust, attract negative publicity, and invite stricter regulatory scrutiny.</p><p><strong>3. Important Transferable Skills for RCA Investigators:</strong></p><p>Key skills include <strong>analytical thinking</strong> to identify patterns, <strong>attention to detail</strong> to ensure accuracy, and <strong>problem-solving</strong> to develop corrective actions. Strong <strong>communication and collaboration</strong> help gather information and implement solutions, while <strong>decision-making</strong> ensures effective resolutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 20:20:25 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323161168</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323217748</link>
         <description><![CDATA[<p><br/></p><p>As an crew member at a resturant, we noticed that the <strong>basmati and brown rice</strong> stored in the hotwell was becoming dry and unappetizing over time, especially during busy hours. Initially, I thought the issue might be caused by <strong>overcooking the rice</strong> or insufficient water during cooking. However, after carefully observing the hotwell and consulting with the kitchen staff, I identified the <strong>real issue</strong>: the <strong>temperature of the hotwell</strong> was set too high, causing the moisture in the rice to evaporate too quickly, making it dry and tough. Furthermore, the rice wasn’t being properly covered, which exacerbated the moisture loss.</p><p>To solve this, I decided to move the rice to a <strong>backup heat station</strong> instead of the high-temperature hotwell. The backup heat station maintained a gentler, more consistent heat, preventing the rice from drying out. We also ensured the rice was covered to retain moisture. This change successfully kept the rice moist throughout service, reducing waste and improving the overall quality.</p><p>Had I only focused on adjusting the rice recipe or assumed it was overcooked, I would have continued to face the same issue. By identifying the root cause and making adjustments to the heat source, we were able to improve both the quality and efficiency of service.</p><p>This experience emphasized the value of <strong>critical thinking</strong>, <strong>problem-solving</strong>, and <strong>attention to detail</strong> in addressing operational challenges. These skills are crucial in identifying the right solutions and ensuring optimal product quality in a fast-paced work environment.</p>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/3388641791/3fce7e7a8061ba48cd7159f08b3e2945/image.png" />
         <pubDate>2025-02-10 21:23:16 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323217748</guid>
      </item>
      <item>
         <title>Melvin Paul Alfred (3010328475)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323316447</link>
         <description><![CDATA[<p>In my role as a QA Officer, I participated in a Root Cause Analysis (RCA) investigation to address inconsistent product texture in a food production line. Using the <strong>5 Whys</strong> technique, we discovered the root cause was a calibration error in a temperature control device, leading to inconsistent cooking temperatures. Corrective actions included recalibrating equipment, retraining staff, and enhancing monitoring systems, which resolved the issue and prevented recurrence.</p><p>Identifying the wrong root cause can severely impact a company. For example, misattributing a problem to human error instead of equipment malfunction can waste resources on unnecessary retraining while the actual issue persists. Similarly, incorrectly blaming a single batch of raw materials for a systemic production issue can lead to ongoing quality problems, customer dissatisfaction, and potential recalls, damaging the brand’s reputation.</p><p>Key transferable skills for effective RCA include <strong>analytical thinking</strong> to break down complex problems, <strong>attention to detail</strong> to ensure no critical information is missed, and <strong>communication skills</strong> for gathering and presenting findings. <strong>Problem-solving skills</strong> are essential for developing practical solutions, while <strong>collaboration</strong> ensures effective teamwork. Additionally, <strong>technical knowledge</strong>, such as understanding HACCP and GMP in food science, is crucial for identifying root causes. These skills are not only vital for RCA but also transferable across roles and industries, enhancing professional versatility.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-10 23:47:17 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323316447</guid>
      </item>
      <item>
         <title>Karen Joy Penero (301277611)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323509737</link>
         <description><![CDATA[<p>     One of my responsibilities in my previous job was handling customer complaints. To effectively address these complaints and prevent recurrence, a thorough Root Cause Analysis (RCA) investigation must be conducted to implement corrective and preventive actions. Based on the annual management meeting, the most frequent complaint was hair found in the finished product. Through a systematic root cause analysis, which I led with the QA Coordinator and Production Team Leader, it was determined that the existing disposable hairnets were insufficient to contain hair strands, even when female food handlers tied their hair. As a result, a tailor-made, washable hair restraint was introduced, designed to be worn over the disposable hairnet. This new restraint covered the entire neck, leaving only the eyes exposed when worn with a facial mask. After implementing this preventive action, complaints related to hair contamination decreased significantly, demonstrating the effectiveness of the corrective measures stemming from a proper RCA.</p><p>     Identifying the wrong root cause during an investigation can result in <strong>significant loss of man-hours</strong>. For example, the time spent on investigation, implementing corrective and preventive actions, and training personnel for product or process changes is wasted if the real root cause is not addressed, potentially allowing the issue to recur. Moreover, incorrectly identifying the root cause can <strong>damage the company’s reputation</strong>. Recurring complaints due to failure to address the true root cause of non-conformance may erode customer confidence.</p><p>     Key transferable skills for individuals who regularly conduct RCAs include <strong>problem-solving</strong>, <strong>cause-and-effect analysis</strong>, and <strong>decision-making</strong>.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-11 03:17:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323509737</guid>
      </item>
      <item>
         <title>Oforiwaah Smith 301399493</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3323574357</link>
         <description><![CDATA[<p>During one of my food safety experiments, I had to conduct a Root Cause Analysis (RCA) after unexpected bacterial growth appeared in control samples that were supposed to remain sterile. I systematically traced the issue back to a possible contamination source, considering factors like improper sterilization, media preparation errors, or environmental exposure. After multiple rounds of investigation, I discovered that a minor inconsistency in autoclaving times had led to incomplete sterilization of some materials. Once this was corrected, the issue was resolved, reinforcing the importance of precise protocol adherence in microbiological work.</p><p>Identifying the wrong root cause in an RCA can have serious consequences for a company. For example, if a food production facility wrongly attributes microbial contamination to packaging rather than inadequate sanitation procedures, they might invest heavily in unnecessary packaging changes while the real issue persists. Similarly, in quality control, misdiagnosing a texture defect in a processed food product as an ingredient issue rather than a processing parameter error could lead to wasted resources and continued product inconsistencies. The most important transferable skills for those conducting RCA regularly include critical thinking to analyze data objectively, attention to detail to recognize subtle deviations, and strong communication skills to collaborate effectively with different teams and ensure solutions are properly implemented.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-11 04:31:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3323574357</guid>
      </item>
      <item>
         <title>Shabnam Rezaei-K 300913882: Root Cause Analysis (RCA) </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3324649365</link>
         <description><![CDATA[<p>My Root Cause Analysis (RCA) Experience in Dairy Processing</p><p>In a dairy plant, we aimed to develop a flavored yogurt dip with smoked eggplant. However, the final product exhibited excessive syneresis (water separation), affecting its texture and stability.</p><p>To identify the root cause, we conducted an RCA investigation:</p><ul><li><p>Ingredient composition was checked fat and protein levels were within specifications.</p></li><li><p>pH and acidity were measured, and values were stable</p></li><li><p>Processing conditions were reviewed—revealing that the eggplant puree had excess moisture content, which disrupted the yogurt’s gel network and led to water release.</p></li><li><p>Root cause: The eggplant puree was not properly drained before incorporation, leaving too much free water in the final product.</p></li></ul><p>Solution: We optimized the formulation by improving the pre-treatment of the eggplant, incorporating a proper draining step and also using the proper amount of emulsifiers to remove and stabilize excess moisture before mixing it into the yogurt base. This adjustment improved product consistency and prevented syneresis in future batches.</p><p>2. Impact of Identifying the Wrong Root Cause</p><p>If the wrong root cause had been identified, it could have led to:</p><p>1.&nbsp;&nbsp;&nbsp;&nbsp; Unnecessary ingredient modification – If we had assumed that the yogurt base formulation was incorrect, we might have unnecessarily altered protein and fat ratios, increasing costs without solving the problem.</p><p>2.&nbsp;&nbsp;&nbsp;&nbsp; Process inefficiencies and customer complaints – If we had overlooked the excess moisture from the eggplant, future batches would have continued to experience syneresis, leading to customer dissatisfaction, product returns, and reduced shelf life.</p><p>3. Key Transferable Skills for RCA Investigations</p><p>· Scientific analysis</p><p>· Data interpretation</p><p>· Process optimization</p><p>· Problem-solving</p><p>· Attention to detail</p><p>· Critical thinking</p><p>· Collaboration</p><p>· Communication</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-11 18:43:16 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3324649365</guid>
      </item>
      <item>
         <title>Aimee Alindayo 301364814</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3325038810</link>
         <description><![CDATA[<p>During my experience as an assistant chemist at the Department of Environment and Natural Resources (DENR) in the Philippines, along with my studies at Centennial College, I was involved in Root Cause Analysis (RCA) investigations focused on inconsistencies in laboratory testing. One notable case dealt with unexpected discrepancies in sample results. To uncover the underlying issue, we meticulously examined testing protocols, equipment calibration logs, and sample handling methods. Our investigation revealed that the problem originated from inadequate sample preparation. As a result, we implemented additional training for the staff and established stricter procedural checks to ensure this issue wouldn’t happen again.</p><p><br/></p><p>Identifying the wrong root cause during an investigation can have significant repercussions. One major effect is the implementation of ineffective solutions, which can lead to increased costs. Misidentifying a problem might cause unnecessary actions, like replacing equipment that was functioning properly, wasting both time and resources. Additionally, there are regulatory and quality risks to consider. In sectors such as food production or environmental testing, failing to address the actual cause of a problem can lead to compliance issues, inaccurate reporting, or even product recalls, ultimately harming a company’s reputation and trustworthiness.</p><p><br/></p><p>To carry out RCA investigations successfully, several transferable skills are vital. Analytical thinking is essential for evaluating data, spotting trends, and pinpointing the actual root cause. A keen attention to detail ensures that every aspect of the investigation is thoroughly examined. Effective communication and teamwork skills are important for clearly documenting findings and collaborating with various teams to implement corrective measures. Finally, adaptability is crucial, as investigators need to stay open to various possibilities and avoid making assumptions that could lead to erroneous conclusions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-12 01:29:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3325038810</guid>
      </item>
      <item>
         <title>Disha Patel (301411100)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3325303531</link>
         <description><![CDATA[<p><br/></p><p><br/></p><p>One of the most memorable investigations I participated in was during my time working in the pharmaceutical industry. A batch of medicine did not meet the expected potency levels, and as part of the quality control (QC) team, I was asked to help identify the root cause. Initially, the production team suspected that an error occurred during the weighing of raw materials. However, after a thorough RCA, we found that the issue stemmed from improper mixing during the granulation process. The impeller speed was too low, leading to inconsistent distribution of active ingredients. Once we corrected the mixing parameters, the problem was resolved, and future batches met quality standards.</p><p>Identifying the wrong root cause in an investigation can have serious consequences for a company. For example, if the issue in my case had been wrongly attributed to the weighing process, unnecessary retraining and raw material adjustments could have been implemented, leading to wasted time and resources without solving the real issue. Another example is in food production—if a contamination issue is incorrectly blamed on packaging instead of improper sanitation, the actual risk remains, potentially leading to product recalls and consumer safety concerns.</p><p>Conducting RCAs regularly requires strong analytical and problem-solving skills. Attention to detail, effective communication, and critical thinking are essential to identifying the true root cause. Additionally, teamwork is crucial because multiple departments are often involved in finding solutions. Reflecting on this experience, I realize how important a structured approach to problem-solving is, not just in the workplace but also in everyday life situations.</p><p><br/></p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-12 06:05:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3325303531</guid>
      </item>
      <item>
         <title>Musharrat Nazia (301271864)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3326848759</link>
         <description><![CDATA[<p>During my role as a security guard, I encountered a recurring issue with unauthorized access to restricted areas in the building. To determine the root cause, I conducted a Root Cause Analysis (RCA) using the 5 Whys technique. Initially, it seemed like employees were simply neglecting security protocols, but after further investigation, I discovered that the keycard system had occasional malfunctions, causing some doors to remain unlocked. Additionally, a lack of awareness among staff about security procedures contributed to the problem. To address this, I reported the keycard issue to management for immediate technical inspection, suggested refresher training for employees on access policies, and worked with my supervisor to implement clearer signage for restricted zones. These corrective actions improved security compliance and reduced unauthorized access incidents. This experience reinforced the importance of problem-solving, attention to detail, and communication—skills that are transferable across various roles and industries.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-13 04:54:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3326848759</guid>
      </item>
      <item>
         <title>Rhema Grace Morado          301346256</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3327737020</link>
         <description><![CDATA[<p>I participated in a Root Cause Analysis (RCA) to address a recurring issue with non-conforming product volumes as a previous QA Analyst in a manufacturing plant. During the investigation, I worked with the production and maintenance teams to analyze data from production logs and equipment calibration records. Using tools like the "5 Whys," we identified that the root cause was a subtle deviation in the filling process caused by inconsistent machine settings. We implemented a solution by standardizing the machine settings and enhancing operator training. This approach resolved the issue and improved overall process reliability.</p><p><br>Incorrectly identifying the root cause can have far-reaching consequences for a company. For example, if the problem were blamed on operator error without addressing the underlying equipment issue, the non-conformances would continue, resulting in product wastage. These scenarios demonstrate how improper RCAs can waste resources, harm customer trust, and damage a company’s reputation.</p><p><br>Successful RCAs require a strong foundation of critical thinking and analytical skills to accurately interpret data and identify patterns. Attention to detail is equally vital to thoroughly examine all contributing factors. Effective communication and teamwork are also critical, as RCAs often involve collaborating with various departments to gather insights and implement corrective actions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-13 17:01:39 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3327737020</guid>
      </item>
      <item>
         <title>Chukwudi Uche - 301363306</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3328058431</link>
         <description><![CDATA[<p><br/></p><p>During my time managing a night club some years back, a nightclub customer suffered a <strong>life-threatening injury</strong> after slipping and falling near the bar. This is types of falls have been occurring since we changed the flooring of the club, and this particula incident was the 6th in abouth same number of months. The previous cases were ignored because they were not severe.  However, the severity of thus 6th incident prompted the nightclub management to conducts a <strong>Root Cause Analysis (RCA). </strong>At that time, it didn't occur to me that what we were doing was known as the<strong> 5 WHYs method</strong>, but we generally thought we were just trying to find a solution that would ensure no customer slips in the club again. </p><p><strong>The questions we asked to help us solve the "slipping" problem included:</strong></p><ol><li><p><strong>Why did the customer suffer a life-threatening fall?</strong><br>→ Because they slipped on a wet floor and hit their head on the edge of a table.</p></li><li><p><strong>Why was the floor wet?</strong><br>→ Because a drink was spilled and not cleaned up immediately.</p></li><li><p><strong>Why was the spill not cleaned up?</strong><br>→ Because there was no dedicated staff responsible for cleaning spills in real-time.</p></li><li><p><strong>Why was no staff member assigned to monitor spills?</strong><br>→ Because the nightclub management did not prioritize floor safety, even after previous incidents.</p></li><li><p><strong>Why didn’t the management prioritize floor safety?</strong><br>→ Because there was no formal incident tracking system, and past incidents were ignored since they were not severe.</p></li></ol><p><strong>Root Cause Identified:</strong></p><p>The nightclub lacks <strong>a proper incident tracking system and a safety policy</strong> for handling spills, leading to repeated falls and eventually a life-threatening injury.</p><p><strong>Corrective Actions:</strong></p><ol><li><p><strong>Implement an Incident Reporting System:</strong></p><ul><li><p>All waitstaff were compelled to report any spill in or around their service table to the janitor through the walkie-talkie</p></li><li><p>Ensure every incident is reported and reviewed by management.</p></li></ul></li><li><p><strong>Assign Dedicated Spill Response Staff:</strong></p><ul><li><p>We had to employ a janitor who's only job was to ensure every reported spill is cleaned off the floor within 1-3 MINUTES. </p></li><li><p>Equip them with quick-cleaning materials like absorbent mats and floor signs.</p></li></ul></li><li><p>Use anti-slip mats near the bar and other spill-prone areas.</p></li><li><p><strong>Conduct Regular Safety Audits:</strong></p><ul><li><p>Management should perform routine inspections to ensure compliance.</p></li><li><p>Encourage customers and staff to report hazards immediately.</p></li></ul></li></ol><p><strong>Conclusion:</strong></p><p>The nightclub ignored early warning signs, allowing minor incidents to escalate into a <strong>life-threatening situation</strong>. By implementing <strong>proper safety policies, tracking incidents, and training staff</strong>, similar accidents can be <strong>prevented in the future</strong>.</p><p><br/></p><p>Question - How do you think the wrong Root Cause being identified from an investigation will impact a company (give 2 examples of outcomes)</p><p><br/></p><p>Answer - If the wrong root cause is identified during an RCA, it can lead to <strong>ineffective solutions</strong>, wasted resources, and continued problems. Here are two key outcomes:</p><ol><li><p><strong>Recurring Incidents &amp; Increased Liability:</strong></p><ul><li><p>If a nightclub falsely concludes that customers are falling due to <strong>excessive alcohol consumption</strong> rather than <strong>slippery floors</strong>, they might increase security checks on intoxicated guests instead of fixing the floor issue.</p></li><li><p>This would <strong>not prevent future falls</strong>, leading to <strong>more injuries, lawsuits, and financial losses</strong> from legal claims and damaged reputation.</p></li></ul></li><li><p><strong>Wasted Resources &amp; Reduced Productivity:</strong></p><ul><li><p>If a manufacturing company investigates a defective product issue and wrongly attributes it to <strong>human error</strong> rather than <strong>faulty machinery</strong>, they might spend <strong>money retraining employees</strong> instead of fixing or replacing the malfunctioning equipment.</p></li><li><p>This would <strong>not solve the real problem</strong>, leading to <strong>more defective products, higher production costs, and potential customer dissatisfaction.</strong></p></li></ul></li></ol><p><br/></p><p>Question - What transferable skills do you think are most important to individuals who conduct RCA's regularly</p><p><br/></p><p>Answer - <strong>Critical Thinking &amp; Analytical Skills</strong> – The ability to logically break down a problem, ask the right questions, and evaluate multiple possible causes.</p><ul><li><p><strong>Attention to Detail</strong> </p></li><li><p><strong>Problem-Solving Skills</strong></p></li><li><p><strong>Communication &amp; Collaboration</strong></p></li><li><p><strong>Data Collection &amp; Interpretation</strong></p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-13 22:20:17 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3328058431</guid>
      </item>
      <item>
         <title>Ayobami Adegbenro - 301268004</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3328319920</link>
         <description><![CDATA[<p>During my undergraduate days, my laptop was stolen from my room closet with the lock vandalized. I immediately informed the hostel security team, who asked me and my roommates a few questions. A few days. later, the laptop was found in a deserted classroom. CCTV footage revealed that one of my roommates' friends was the culprit. </p><p><br/></p><p>If the investigating committee had named my roommate, who was the prime suspect, the perpetrator without due diligence, that would have not only damaged the university's reputation but also my roommate's. He would have carried the tag for life as a thief—a dent that may never be fixed even when the truth got out.</p><p><br/></p><p>Root Cause Analysts must be critical thinkers who are able to look beyond the surface. They must be good communicators with excellent emotional intelligence, possessing abilities to ask questions without being confrontational.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-14 03:05:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3328319920</guid>
      </item>
      <item>
         <title>Oforiwaah Smith 301399493</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3328321898</link>
         <description><![CDATA[<p>I want to share a story about a Root Cause Analysis  was part of during an internship in the food industry. While I can’t share specific company or product details, I can tell you it was a situation where a batch of product had an unexpected texture issue something customers noticed right away. The team was tasked with figuring out what went wrong, and I was lucky enough to be part of the investigation.</p><p>We started by mapping out the entire production process, from ingredient sourcing to packaging. It was like detective work! At first, everyone assumed the issue was with the mixing step because that’s where texture is primarily determined. But after digging deeper looking at data, interviewing team members, and testing samples we realized the real problem was actually a slight variation in one of the raw ingredients. It wasn’t obvious at first, but the ingredient supplier had made a small change without notifying us. This experience taught me how important it is to look beyond the obvious and question assumptions during an RCA.</p><p>If the wrong root cause had been identified, it could have led to some serious consequences for the company. For example:</p><ol><li><p><strong>Wasted Resources</strong>: The company might have invested in upgrading mixing equipment or retraining staff, which wouldn’t have solved the actual problem.</p></li><li><p><strong>Customer Trust</strong>: If the issue persisted, customers might have lost confidence in the product, leading to decreased sales and a damaged brand reputation.</p></li></ol><p>From this experience, I learned that RCA requires a mix of technical knowledge and soft skills. Attention to detail is crucial, but so is communication. Being able to ask the right questions, listen to different perspectives, and collaborate across teams is what really drives a successful investigation. These are transferable skills that apply to so many areas, not just food science.</p><p>Overall, this RCA was a great learning experience for me. It showed me how important it is to stay curious, dig deep, and not settle for surface-level answers. Looking forward to hearing your stories too.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-14 03:06:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3328321898</guid>
      </item>
      <item>
         <title>Manmeet Kaur 30128172</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3328486749</link>
         <description><![CDATA[<p>A month ago at Tim Hortons, a customer complained that their coffee tasted "off." We first assumed the cream was bad, but after replacing it, complaints kept coming. My manager asked me to investigate.</p><p>After checking the coffee beans, filters, and machines, I found the issue—someone had mistakenly refilled the regular coffee dispenser with decaf grounds, throwing off the brewing ratio. We fixed it by retraining the team, and the problem stopped.</p><p>Misidentifying the root cause could have led to wasted products or lost customers. In a company, blaming the wrong factor—like replacing good equipment or disciplining employees for a process issue—can be costly.</p><p>Key RCA skills include attention to detail, problem-solving, and teamwork. This experience showed me that small mistakes can have big consequences, and finding the real issue is crucial for smooth operations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-14 06:17:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3328486749</guid>
      </item>
      <item>
         <title>Mandeep Saini (301379495)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329275127</link>
         <description><![CDATA[<p><br></p><p>As a cashier at Dairy Queen, I noticed frequent customer complaints about incorrect orders. To find the cause, my team conducted a Root Cause Analysis (RCA). We examined possible issues like miscommunication, system errors, or human mistakes. After careful observation, we found that the receipt format was unclear, making it difficult for kitchen staff to prepare the correct orders. Once the receipts were reformatted, order accuracy improved, and complaints decreased.</p><p>Impact of Identifying the Wrong Root Cause</p><p>If a company identifies the wrong root cause, it can lead to wasted time and money. For example, if management had assumed employees needed retraining instead of fixing the receipts, it wouldn’t have solved the issue. Another major consequence is loss of customer trust—if mistakes continue, customers may stop coming back, leading to bad reviews and lower sales.</p><p>Important Transferable Skills for RCA</p><p>Successful RCA requires observation and attention to detail, as small issues can cause big problems. Problem-solving is crucial to finding practical solutions. Communication skills help explain the findings clearly, and teamwork ensures effective problem resolution.</p><p>RCA is valuable in all workplaces, including restaurants, as it helps businesses improve efficiency, reduce mistakes, and keep customers happy.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-14 19:25:51 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329275127</guid>
      </item>
      <item>
         <title>Tasmiyabanu Chauhan (301323101)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329348393</link>
         <description><![CDATA[<p>I recently addressed a recurring issue with houseflies in my home by employing a Root Cause Analysis (RCA). At first, I suspected that they were entering through open windows and doors, so I ensured that these were kept closed; however, the problem continued. To investigate further, I monitored the areas where the flies congregated and searched for possible attractants. Upon inspecting trash bins, drains, and food storage locations, I discovered that a neglected bowl of overripe bananas in the kitchen was the primary source of the problem. After disposing of the spoiled fruit, cleaning the surrounding area, and enhancing waste management practices, the issue was resolved. This experience underscored the importance of a systematic approach in identifying the actual root cause.</p><p><br/></p><p>Identifying the underlying cause during an investigation is essential for a company, as errors can result in significant consequences. A primary concern is the misallocation of resources and the escalation of costs. For example, if a food manufacturer incorrectly attributes contamination to ingredient sourcing instead of a hygiene issue in the production process, they may incur unnecessary expenses to address the incorrect problem. Another serious implication is the potential for customer dissatisfaction and harm to the company's reputation. If a business fails to accurately identify a product defect, customers may continue to encounter issues, leading to complaints and a decline in trust. For instance, an airline that prioritizes minor scheduling concerns rather than tackling operational inefficiencies may witness a decrease in ticket sales due to persistent delays.</p><p><br/></p><p>Effective root cause analysis (RCA) depends on a variety of essential skills. The ability to think critically and maintain a sharp focus on details allows investigators to systematically examine issues, ensuring that no significant elements are overlooked. Proficient problem-solving skills are essential for executing suitable corrective measures once the root cause has been identified. Additionally, effective communication and collaboration are crucial for working with others to implement solutions successfully. Lastly, adaptability and open-mindedness enable professionals to reevaluate assumptions and explore alternative causes if initial conclusions are found to be erroneous. By refining these skills, individuals can enhance their problem-solving capabilities and create lasting solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-14 21:29:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329348393</guid>
      </item>
      <item>
         <title>Hinal Choksi (301377952)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329456719</link>
         <description><![CDATA[<p>I was previously employed at an organization as a food technologist and one of the issues we observed was that our frozen indian flatbread remained stiff and chewy instead of soft and pliable. After we employed root cause analysis we monitored the thawing and cooking process to identify the factor which affected the texture of the bread. For further investigation we also monitored the bathc production and also monitored the quality of incoming raw ingredients. We later found the problem with the mix of ingredients and we changed the ratios as well as the freezing temperatures and corrected the product resulting in a soft and pliable flatbread. </p><p>Impact of wrong RCA:</p><p>Had we just focused on the post production changes and not studied the ratios of ingredients we would have wasted finances in accquiring machines which would have still yielded the same result and we would also have lost customers due to a poorly formulated product.  Leading to losses for the company. One motivation that drew us to find solution was to deliver a quality product to our consumers. </p><p>Some of the skills that are necessary for root cause analysis are analytical skills, eye for detail and good teamwork along with problem solving skills to work efficiently in the food industry and the lesson we learned was that a small change in the ingredient can impact the entire finished product and hence it is necessary to study the properties of each ingredient and their role in the final product to formulate a good product.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-15 02:27:11 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329456719</guid>
      </item>
      <item>
         <title>Victoria Sanchez (301373675)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329469120</link>
         <description><![CDATA[<p>1. A few years ago, I was involved in a Root Cause Analysis (RCA) investigation at work. The company I worked for in quality control for dental prosthetics was receiving complaints about defects in the final products being delivered and with this customer satisfaction had decreased. </p><p>I was part of a small team in charge of identifying the root cause of this problem.</p><p>To start, we began by collecting the orders, we also asked some questions to production and logistics departments. Throughout this process, we discovered that the problem was not only the final product with incorrect specifications but that the deeper problem lay in the lack of communication between the logistics department that received the product and design orders which were updated if the client needed new modifications and the production department in charge of processing each order that did not receive updates of these orders.</p><p>By identifying the real cause, we were able to implement a better communication protocol between both departments with the design of a corporate communication chat to avoid future errors. Thanks to this, we managed to regain the trust of our clients by delivering products with specifications that meet their requirements.</p><p>2. Identifying the correct root cause is essential, since if the wrong one is identified, it can have several negative impacts.</p><p>For example: If the wrong problem is addressed, the implemented solution will not be effective. As in the case of defective products, if we had only focused on production and had not addressed the issue of communication between departments, we would continue to look for faults in external equipment or materials, but we would not notice the update of unreceived orders.</p><p>Also, if the company had not managed to identify and address the root cause correctly, production problems would have continued to occur and, as it is a recurring problem, this would have damaged the relationship with customers.</p><p>3. Finally, 1. A few years ago, I was involved in a Root Cause Analysis (RCA) investigation at work. The company I worked for in quality control for dental prosthetics was receiving complaints about faults in the final products being delivered and with this customer satisfaction had decreased. I was part of a small team in charge of identifying the root cause of this problem.</p><p>To start, we began by collecting the orders, we also spoke with the production, logistics and customer service departments. Throughout this process, we discovered that the problem was not only the final product with incorrect specifications but that the deeper problem lay in the lack of communication between the logistics department that received the product and design orders which were updated if the client needed new modifications and the production department in charge of processing each order that did not receive updates of these orders.</p><p>By identifying the real cause, we were able to implement a better communication protocol between both departments with the design of a corporate communication chat to avoid future errors. Thanks to this, we managed to regain the trust of our clients by delivering products with specifications that meet their requirements.</p><p>2. Identifying the correct root cause is essential, since if the wrong one is identified, it can have several negative impacts.</p><p>For example: If the wrong problem is addressed, the implemented solution will not be effective. As in the case of faulty products, if we had only focused on production and had not addressed the issue of communication between departments, we would continue to look for faults in external equipment or materials, but we would not notice the update of unreceived orders.</p><p>Thus, if the company had not managed to identify and address the root cause correctly, production problems would have continued to occur and, as it is a recurring problem, this would have damaged the relationship with customers.</p><p>3. Finally, I believe that there are three key skills during root cause analysis: Starting with critical thinking to look beyond the problem and ask the right questions to identify the causes is essential. Additionally, the ability to communicate clearly with different departments and stakeholders when gathering accurate information, and finally the teamwork to collaborate effectively, share ideas and analyze findings.</p>]]></description>
         <enclosure url="https://pixabay.com/get/g787f9f6c2d50babda639aee8b2cb6f926cbc81ccd8109a57ac0ac220692670846ba704ca0590192d271e711fefd44a6f.jpg" />
         <pubDate>2025-02-15 03:02:20 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329469120</guid>
      </item>
      <item>
         <title>Brenda Soliano 301252702</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329487629</link>
         <description><![CDATA[<p>My Root Cause Analysis experience involves a problem with cooked rice that was not always thoroughly cooked. My spouse still didn't like the cooked rice, even after I tried a few fixes, such as changing the heat when all the water above the rice evaporates, that is when using a kettle in cooking. I also tried to use a new rice cooker. Since my husband thought the cooked rice was perfect when I used extra water when cooking it, I concluded that the insufficient amount of water used during cooking was the root cause of the issue.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-15 03:51:29 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329487629</guid>
      </item>
      <item>
         <title>Angela Velasco (301392936) </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329861961</link>
         <description><![CDATA[<p>One time, I had to conduct a Root Cause Analysis (RCA) at home when I noticed that a container of leftovers I had saved was missing from the fridge. I initially assumed that one of my roommates had taken it by mistake, but instead of jumping to conclusions, I decided to investigate. I asked everyone in the apartment if they had seen or taken the food. After some discussion, I realized that the container had been moved to a different shelf, and someone had thought it was theirs. This situation taught me the importance of asking questions, gathering evidence, and considering different possibilities before assigning blame.</p><p>If the wrong Root Cause is identified in an investigation, it can lead to major consequences. First, in a company, misidentifying the cause of a product defect could result in unnecessary corrective actions, wasting time and resources while failing to solve the actual issue. Second, if a workplace safety incident is incorrectly analyzed, the real hazard may not be addressed, leading to potential future accidents or legal liabilities.</p><p>Key transferable skills required for effective RCA include critical thinking, as investigators need to analyze all possible causes and not make assumptions. Another crucial skill is communication, as gathering accurate information from different sources is essential to pinpoint the true root cause. These skills are not just valuable in the workplace but in everyday problem-solving as well.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-15 19:29:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329861961</guid>
      </item>
      <item>
         <title>Sasoon Margarosyan (301202539)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329903438</link>
         <description><![CDATA[<p>During my High school year i was employed as a driveway sealer in a established asphalted company. My positions requirement was to drive a truck which contained a solution and compressor to client house and seal their drive way. at one moment the compressor which sprays this solution was creating any pressure and the machine was not working as indented. </p><p><br/></p><p>by identifying the incorrect root cause of this issue, the company was losing at least 2 to 3 client a day due to malfunctioning equipment. This also affected the company negatively by causing there employees (such as me) to repair the machine whit ought the correct knowledge potently causing more harm to the equipment. </p><p><br/></p><p>i believe the most important skill an individual could have when conducting a RCA is attention to details and creative thinking when communicating. </p><p><br/></p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-15 21:57:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329903438</guid>
      </item>
      <item>
         <title>Genesis Servigna 301391481</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3329937540</link>
         <description><![CDATA[<p>While working in the packaging crew at a pork processing facility, I noticed that many packages on the conveyor had leaks, which was a major issue for product integrity. I set them aside and went to check the sealing machine, where I informed the operator about the problem. He told me the machine was broken, and maintenance needed to take over. As a result, production was paused until the issue was fixed. The root cause was equipment failure, likely due to wear and tear or lack of preventive maintenance. This situation helped me understand the importance of regular machine checks and better communication between departments to catch issues before they affect production.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-16 00:08:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3329937540</guid>
      </item>
      <item>
         <title>Sanjay Kundanari (301403830)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3330000139</link>
         <description><![CDATA[<p>A problem with cooked rice that wasn't always cooked through is the subject of my Root Cause Analysis experience(RCA). I tried a few solutions, such turning up the heat when all the water above the rice evaporates—that is, when using a kettle to cook—but my spouse still didn't like the cooked rice. I also tried using a brand-new rice cooker. Since I used more water to boil the rice and my husband thought it was excellent, and at last I deduced that the primary source of the problem was the inadequate amount of water utilized during cooking.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-16 03:01:04 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3330000139</guid>
      </item>
      <item>
         <title>Lisa Nwokolo - 301317802</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3330308415</link>
         <description><![CDATA[<p>I had always been excited about trying new activities, and one day, I decided to go <strong>ice skating alone</strong>. It was my <strong>first time</strong>, and while I had watched others skate before, I didn’t have any formal training. Shortly after getting on the ice, I struggled to maintain balance but kept pushing myself to continue. Suddenly, I lost control, fell awkwardly, and felt a sharp pain in my ankle. After a trip to the emergency room, it was confirmed—I had fractured my ankle.</p><p>After reflecting on the incident, I identified <strong>several factors</strong> that contributed to my injury:</p><ol><li><p><strong>Lack of Experience:</strong> Since it was my first time skating, I didn’t have the proper technique or balance needed to control my movements.</p></li><li><p><strong>Loose Skating Shoe:</strong> The skate on my injured ankle was slightly loose, reducing ankle support and stability. This likely contributed to my fall and made my ankle more vulnerable to injury.</p></li><li><p><strong>Skating Alone:</strong> Without guidance or a helping hand, I had no one to correct my form or assist me when I started losing control.</p></li></ol><p>Impact of Identifying the Wrong Root Cause</p><ol><li><p><strong>Misidentifying the Issue as Just Bad Luck</strong></p><ul><li><p>If I had simply assumed that my injury was caused by <strong>bad luck</strong>, I might have returned to skating without addressing the real problems. This could have resulted in another fall and possibly a more severe injury.</p></li></ul></li><li><p><strong>Focusing Only on the Loose Shoe and Not My Inexperience</strong></p><ul><li><p>If I had only blamed the loose skate and not considered my lack of experience, I might have thought that <strong>wearing tighter skates would solve the problem</strong>. However, without proper skating lessons, I would still be at risk of falling and injuring myself again.</p></li></ul></li></ol><p><strong>Transferable Skills for Effective RCA</strong></p><p>Conducting an RCA requires several important skills that are useful in various aspects of life:</p><ul><li><p><strong>Adaptability &amp; Continuous Learning:</strong> Learning from failures and adjusting future actions accordingly is key to avoiding repeated mistakes.</p></li><li><p><strong>Risk Assessment &amp; Decision-Making:</strong> Understanding potential risks (like skating alone for the first time) can help in making safer and more informed decisions.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-16 15:18:38 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3330308415</guid>
      </item>
      <item>
         <title>ERICKSON EUGIN (301351191)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3331081811</link>
         <description><![CDATA[<p>At our pizza shop, we encountered an issue during winter where the pizza dough wasn’t rising properly when they are out from oven, leading to an inferior final product. Initially, when I started preparing the dough in the summer, I didn’t measure the water temperature, as the ambient conditions didn’t cause noticeable differences. However, as winter arrived, my boss noticed the lack of proper rising of pizza crust. We experimented with different flour brands and adjusted the proportions of yeast, sugar, salt, and water, but nothing seemed to work. After further investigation, we discovered that despite having a water heater, the water temperature had dropped significantly, lowering the final dough temperature from the ideal 21°C to around 17-18°C. This drop reduced yeast activity, affecting the proofing process. Additionally, once the dough was prepared, we refrigerate it in large Cambro containers, which may have restricted airflow and further impacted proofing.</p><p>To resolve the issue, we implemented a standardized water temperature of <strong>19°C during winter and 17°C during summer</strong>, ensuring consistency in dough preparation. We also began <strong>monitoring water temperature before mixing</strong> and switched to <strong>smaller storage containers</strong> to improve air circulation during proofing. These adjustments resulted in a significant improvement in dough quality, restoring the proper rise and texture of our pizzas. This experience highlighted the importance of careful temperature control and optimized storage methods in achieving consistent product quality. </p>]]></description>
         <enclosure url="https://pixabay.com/get/gabc57c5f2ad6cfec23b81bca231ac3fcb63a38f96b9b4ae5644203bd9fb561ee3be8d6047f0f1f5172f191644d888882.jpg" />
         <pubDate>2025-02-17 08:48:10 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3331081811</guid>
      </item>
      <item>
         <title>Shivani Patel (301428681)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3331253495</link>
         <description><![CDATA[<p>In a previous research project, I was part of a team investigating a recurring issue with a bioreactor used in a lab experiment. We were studying microbial fermentation to produce a specific enzyme, but after several runs, the fermentation yield was consistently lower than expected. This was a critical issue, as the enzyme was needed for further analysis in the project.</p><p>Our first step was to gather all the data from the previous fermentation cycles: temperature, pH levels, oxygen supply, and nutrient concentration. The initial hypothesis was that the low yield was due to suboptimal conditions in one of these parameters, but after reviewing the data, it wasn’t clear where the problem lay. We performed additional tests, including microbiological analysis of the cultures and checks on the equipment, but none of these seemed to be the cause either.</p><p>Finally, after re-evaluating the data with more attention to detail, we discovered that the root cause was actually a malfunction in the temperature control system. The system was intermittently failing to maintain the required temperature range, which resulted in temperature fluctuations that stressed the microbial culture, lowering its activity and overall yield. Once the temperature system was recalibrated and stabilized, the fermentation yield improved significantly.</p><p>This investigation highlighted the importance of thorough data analysis and considering all possible factors. If we had identified the wrong root cause, for example, blaming the nutrient levels or the microbial strain itself, we would have wasted resources and continued to see poor yields despite not addressing the actual issue.</p><p>If the wrong root cause is identified, there are several potential negative outcomes:</p><ol><li><p><strong>Wasted resources</strong>: Misidentifying the cause could lead to unnecessary adjustments, such as altering nutrient formulations or changing experimental conditions, without solving the problem. In a laboratory setting, this can result in wasted time, reagents, and energy.</p></li><li><p><strong>Loss of credibility</strong>: If a company or research team consistently misidentifies the root causes of their issues, it can damage their reputation. In research, especially, the trustworthiness of findings depends heavily on properly identifying and solving problems. If solutions are based on incorrect assumptions, it can lead to flawed outcomes and decreased confidence in future work.</p></li></ol><p>For individuals conducting RCA in scientific settings, <strong>critical thinking</strong> is essential. You need to approach problems systematically, examining all variables and avoiding biases. <strong>Attention to detail</strong> is another crucial skill—missing small discrepancies in data can lead to overlooking the actual problem. Finally, <strong>collaboration</strong> plays a major role, as multiple perspectives can help uncover blind spots and improve the investigation process.</p><p>This experience really reinforced how a methodical and careful approach to RCA can lead to clear, effective solutions. Even in scientific research, the ability to ask the right questions and evaluate all possibilities is key to identifying the true cause of problems and moving forward with confidence.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-17 11:34:11 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3331253495</guid>
      </item>
      <item>
         <title>Melina Selimi 301270971</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3331435648</link>
         <description><![CDATA[<p>At my previous co-op position, I remember that the scientists that had projects they used to store their prototype samples in a room with shelves. There were a lot of projects going on that time and the shelves we un organized and when someone needed to take a sample and review it it was hard for everyone to find it . Fist it was really inconvenient to ask everyone where the samples were and also a big waste of time. After having a lot of chats with the manager and the scientist leader we figured out that sometimes other team members were not taking the samples back to that room but forgetting them on their desks or in the lab somewhere. That's why I started helping by organizing that project room with a code on each shelf , scientists name and registering everything on the excel data sheet that was shared with everyone on the team to find samples easier and put them back at the same spot. </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-17 14:16:20 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3331435648</guid>
      </item>
      <item>
         <title>Kayanule Duke (30130096)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3331823970</link>
         <description><![CDATA[<p>While working in a bakery, we noticed that a batch of bread had an unusually hard texture. Initially, we suspected issues with the dough formulation, but after further investigation , we discovered that the oven temperature had been unintentionally increased. A cook, who was preparing pies at a higher temperature, had adjusted the settings without realizing it would impact the bread. This investigation highlighted the need for separate ovens to prevent such issues in the future.</p><p>Wasted Resources: If we had incorrectly blamed the flour or yeast, we might have discarded good ingredients and adjusted a recipe that wasn’t the real issue, leading to unnecessary costs.</p><ul><li><p>Transferable Skills for Conducting RCA:</p><ul><li><p>Analytical Thinking: Ability to assess different factors that could contribute to the problem.</p></li><li><p>Attention to Detail: Noticing small changes, such as an altered oven temperature.</p></li><li><p>Problem-Solving: Finding solutions, like investing in a second oven to prevent future conflicts.</p></li><li><p>Communication: Coordinating with team members to ensure best practices are followed.</p></li></ul></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-17 21:29:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3331823970</guid>
      </item>
      <item>
         <title>Darshana Vinod (301352395)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3332162685</link>
         <description><![CDATA[<p>I’ve participated in a Root Cause Analysis (RCA) investigation at a previous job where we were dealing with recurring malfunctions in lab equipment. The RCA revealed that the issue wasn’t with the equipment itself but with improper calibration due to a lack of staff training. Once we identified this root cause, we implemented a training program, which resolved the issue. Identifying the wrong root cause can lead to wasted resources, like unnecessarily replacing equipment, or implementing ineffective solutions that don’t actually solve the problem. For RCA, important transferable skills include analytical thinking to interpret data, problem-solving to find solutions, communication to gather input from others, attention to detail to catch small but significant issues, and teamwork to collaborate effectively during the investigation. These skills are valuable not only for RCA but for any problem-solving situations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-18 03:44:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3332162685</guid>
      </item>
      <item>
         <title>Richanelle Martinez (301387411)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3332197123</link>
         <description><![CDATA[<p>During my time as a QC technician, I encountered a critical issue with the longitudinal seal (LS) on a production line. Upon turnover, I received the line as ready for production, with CIP completed, swabbing done, and the correct packaging materials set up, including lot codes and best-before dates. My colleague asked me to double-check the codes to ensure accuracy. Before production started, the operator called me to the Filler room, where it was our responsibility to inspect the first four packages coming off the line for any defects. As production began, I noticed that two out of the first four packages had blocked seals on the LS side. To confirm the issue, we took another four packages, and the same problem occurred. Recognizing the potential impact, I immediately asked the operator to stop the line and informed the production supervisor and the on-duty mechanic. Unfortunately, since the defect appeared intermittently, all the packages produced up to that point—about 10 cases—were rejected.</p><p><br/></p><p>The production team, including the supervisor, mechanic, and operator, began investigating the cause. We first checked the machine’s pressure and temperature settings, which were all within the standard range. Despite this, the mechanic and operator made assumptions about the issue and attempted adjustments. They restarted the line with a few packages to test, but the problem worsened instead of improving. At that point, we shifted our focus to other possible causes, inspecting different machine components—except for the sterile section located on the upper part of the machine. This section could not be accessed without stepping down or shutting down the equipment, as it required re-sterilization after any direct contact. After exhausting several checks and adjustments without success, the production supervisor made the decision to halt production and step down the machine for further inspection. Upon closer examination, we discovered that one of the rollers responsible for sealing the LS strip had accumulated plastic buildup. This roller was supposed to be checked and cleaned during CIP, as stated in the sanitation checklist. When the team questioned the operator from the previous shift, it was revealed that he had been under pressure to complete sterilization by a specific time, leading him to rush through the cleaning process.</p><p><br/></p><p>Incorrect root cause analysis (RCA) can have serious consequences for a company, as seen in this case. Misidentifying the problem led to unnecessary machine adjustments, extended downtime, and increased material waste. Instead of immediately identifying the real issue—the plastic buildup on the roller—the team focused on machine settings, delaying the resolution. As a result, production was disrupted, and 10 cases of product had to be discarded. If the correct RCA had been applied earlier, troubleshooting would have been more efficient, minimizing both financial losses and operational setbacks. Effective RCA requires strong analytical thinking and attention to detail, ensuring that all possible causes are thoroughly examined before making adjustments. These skills are essential for preventing costly mistakes and improving overall problem-solving efficiency in a production environment.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-18 04:23:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3332197123</guid>
      </item>
      <item>
         <title>301403427</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3332937778</link>
         <description><![CDATA[<p>I recall a time during my work at Wendy’s when there was an issue with a batch of sandwiches not meeting the quality standards. Several customers had complained about the sandwiches being undercooked, and the supervisor asked me to help with the investigation. It wasn’t the first time this had happened, so I was asked to help identify the root cause.</p><p>We started by reviewing the entire process: the ingredients, the preparation time, and the cooking procedure. I helped by talking to the team members involved in each step and paying attention to any unusual patterns. After careful investigation, it turned out that the oven’s timer had been malfunctioning, causing the sandwiches to be undercooked. It was a simple fix: recalibrating the oven. We resolved the issue quickly, but it made me realize the importance of looking beyond the surface.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-18 15:23:28 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3332937778</guid>
      </item>
      <item>
         <title>Hung-Yi Liang 301356542</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3333215579</link>
         <description><![CDATA[<p><strong>The Case of the Missing NDS</strong></p><p>When I was a kid, my cousin and I were playing with my <strong>Nintendo DS (NDS)</strong> when she suddenly decided to hide it somewhere in the house as a prank. At first, I panicked because I had multiple game progress saved, and losing it would have been a disaster. Instead of searching randomly, I took a <strong>logical approach</strong> to figure out where she might have hidden it.</p><p>I started by <strong>analyzing her behavior</strong>—he was laughing and avoiding eye contact, which meant she was enjoying watching me struggle. So, I asked myself: <em>Where would she hide something quickly but still be able to see my reaction?</em> I ruled out faraway rooms and focused on places within view. I then <strong>recalled previous pranks</strong> where he hid things under couch cushions or inside drawers. After methodically checking those spots, I finally found my NDS tucked under a pile of pillows on the sofa.</p><p><strong>Outcome &amp; Lesson Learned</strong></p><p>By <strong>staying calm, analyzing clues, and thinking logically</strong>, I was able to solve the mystery without wasting too much time. This childhood experience was my first introduction to <strong>Root Cause Analysis</strong>—instead of randomly searching, I used reasoning, past knowledge, and behavioral cues to identify the most probable hiding spots. If I had jumped straight into looking everywhere without a plan, I might have taken much longer to find it. Looking back, this was an early lesson in problem-solving and critical thinking!</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-18 19:17:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3333215579</guid>
      </item>
      <item>
         <title>Mohammad Juned (301278343)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3333551838</link>
         <description><![CDATA[<p>During my time at work, I was involved in a Root Cause Analysis (RCA) when our security cameras stopped functioning properly. Since the cameras were crucial for monitoring and security, our manager needed to determine when they had last been operational. The team was asked if they had noticed any issues before, and I recalled that they were working fine during my shift on Wednesday. After gathering responses from everyone, we pinpointed that the cameras were last confirmed to be working on Monday night.</p><p>Upon further investigation, we discovered that the Monday night security guard was the last person to log out of the system. However, they admitted they didn’t verify if the system logged out correctly because they were tired and eager to leave. The Tuesday morning security guard noticed the issue but didn’t report it immediately due to boredom and a lack of urgency. Digging deeper, we found that the night guard had been trained by another security guard (Guard X), who wasn’t qualified to train new hires. Guard X had taken over training responsibilities because senior guards were on leave, but the manager hadn’t been updated due to the holiday rush and staffing shortages.</p><p>This situation showed how identifying the wrong root cause could negatively impact a company. For example, if management had blamed only the Tuesday guard for negligence, they would have missed the deeper issue of improper training. Another possible outcome could have been costly delays in fixing the cameras if the real cause—staffing issues and lack of communication—had not been addressed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-19 01:54:06 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3333551838</guid>
      </item>
      <item>
         <title>Zully Cevallos (301359492)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3336217264</link>
         <description><![CDATA[<p>As a teacher, while I haven't conducted formal workplace investigations in the same way a manager might, I have certainly participated in inquiries and problem-solving scenarios that mirror aspects of an investigation. For example, I've been asked to provide information to administrators regarding incidents involving students, such as playground altercations or classroom disruptions. This often involves gathering information from multiple students, documenting observations, and trying to understand the root cause of the issue. It's similar to fact-finding in a formal investigation, although on a smaller scale. I've also worked with colleagues to investigate discrepancies in student work or assessment results, which requires careful analysis and collaboration to identify potential errors or inconsistencies.</p><p><br/></p><p>And yes, the roommate fridge scenario is a classic example of a mini-investigation! It involves gathering circumstantial evidence (empty containers, suspicious crumbs), questioning potential culprits (with varying degrees of directness), and trying to deduce the most likely scenario. It's definitely a less formal process, but the underlying principles of gathering information and identifying a cause are the same! So, while my "investigations" might not be as structured as those in a corporate setting, the skills of observation, information gathering, and analysis are definitely transferable.</p>]]></description>
         <enclosure url="https://pixabay.com/get/gc79e3fab32d0fbed832985ea4863c453dd8b517cd47ec611ab78f2da19018416d9bbb158a1e00dc41e4bd383c8d025f7.jpg" />
         <pubDate>2025-02-20 15:37:52 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3336217264</guid>
      </item>
      <item>
         <title>Sukhmandeep kaur(301435330)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3338797706</link>
         <description><![CDATA[<p>A few years ago, I was part of a group project at school where we struggled with coordination and missed deadlines. Initially, we assumed that the problem was with one group member not doing their part, so we focused on discussing that issue. However, after talking to everyone and evaluating how we were working together, we realized the true problem was poor communication within the group. We hadn’t set clear expectations for each task, and everyone had different ideas of what needed to be done. Once we addressed the lack of communication and set specific roles and deadlines, the project moved much more smoothly.</p><p>If we had continued to blame the one person, nothing would have changed. The same issues of confusion and missed deadlines would have kept happening, and the group’s overall performance would have suffered. Another outcome could have been resentment from the blamed member, leading to conflict and further reducing the group’s effectiveness.</p><p>Through this experience, I learned that effective communication and collaboration are essential for group success. Active listening was important in understanding each person’s perspective and finding the real issue. Also, problem-solving skills are critical, as we needed to assess the situation holistically to understand the root cause of our struggles.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-23 02:08:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3338797706</guid>
      </item>
      <item>
         <title>Archana Pavuluri (301379948)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3340702236</link>
         <description><![CDATA[<p>I took part in a Root Cause Analysis (RCA) investigation while &nbsp;working in food quality assurance and discovered that a batch of spinach dip had variable flavor and texture. Data collection on components, production techniques, and supplier consistency was the first step in our team's RCA procedure to identify the root cause. Analysis revealed that a supplier had supplied spinach with a greater than normal moisture content, which affected the texture of the finished product. The problem was fixed by tightening supplier standards and modifying the recipe formulation.<br><br>If the incorrect root cause is found, a business may suffer serious repercussions. First, it could result in recurring product failures, raising production costs and generating financial losses from wasted raw materials.Second, trying to address the root reason could damage customer trust since persistent quality problems can result in recalls, complaints, or a bad image of the brand.<br><br>Critical thinking is one of the most crucial transferable abilities for RCA experts since they need to evaluate several possible causes and correctly analyze data. Furthermore, it is essential to pay close attention to details to make sure that no contributing aspect is missed. Effective corrective measures require that RCA findings be communicated to cross-functional teams in a clear and concise manner, which calls for strong communication skills.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-24 18:07:06 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3340702236</guid>
      </item>
      <item>
         <title>Sargun Bajwa(301430105)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3344338911</link>
         <description><![CDATA[<p>While I worked as a Co-op Student Lab Technician, I saw that even though students followed the same protocol, their experiment outcomes varied. I looked into it by making sure the equipment was calibrated, the glassware was clean, and the reagents were of high quality. I looked over every aspect and discovered that the results were impacted by residue from incorrect glassware washing. Repeating appropriate cleaning procedures fixed the problem.<br><br>If there is a wrong root analysis, there could be serious repercussions for any company. A corporation wastes resources on needless repairs if it misdiagnoses a manufacturing problem as machine failure rather than a procedural error. Recalls and reputational harm may result from food producers mistaking contamination for poor quality ingredients rather than inadequate cleanliness.</p><p><br/></p><p>To effectively identify difficulties, conducting root cause analyses (RCAs) calls for critical thinking, attention to detail, and problem-solving skills. Strong communication and collaboration are also key skills for the smooth functioning of any industry.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-26 23:31:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3344338911</guid>
      </item>
      <item>
         <title>Parneet Kaur - 301433608</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3344625070</link>
         <description><![CDATA[<p><strong>The Case of the Missing Snack Box</strong></p><p>During my graduation, I lived in a hostel where I shared a room with a roommate. One day, I noticed that my entire plastic container, which held my cookies and snacks, had disappeared. At first, I suspected my roommate—after all, it seemed likely that she might have taken a few cookies. But taking the whole container? That seemed unusual.</p><p>Determined to find out what happened, I searched my room and asked my hostel mates if they had seen it. No one knew anything. I even checked common areas, but my snack box was nowhere to be found. The mystery remained unsolved.</p><p>A few days later, I saw something surprising—a stray dog casually walked into the hostel, entered another student’s room, and took something before running away. That’s when it clicked: maybe a dog had come into my room and taken my snack box! While I never recovered my missing container, this observation led me to believe that the real culprit was not my roommate, but rather a four-legged thief.</p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><p>If I had wrongly blamed my roommate, it could have created unnecessary tension between us. Similarly, in any investigation, identifying the wrong root cause can have negative consequences. Based on my experience, here are two possible outcomes of misidentifying a root cause:</p><ol><li><p><strong>Damaged Relationships:</strong> Just as wrongly accusing my roommate could have caused a misunderstanding, misidentifying a cause in a workplace investigation—such as blaming an employee for a missing item when it was actually misplaced—can lead to conflict and mistrust among colleagues.</p></li><li><p><strong>Unresolved Issues:</strong> If I had focused only on questioning my roommate and never considered other possibilities, I would never have realized that the dog might have been responsible. Similarly, in a company, if investigators focus on the wrong cause, the real problem may persist. For example, if a business assumes that a drop in sales is due to employee performance rather than an external market factor, they may take ineffective corrective actions.</p></li></ol><p><strong>Transferable Skills for Root Cause Analysis</strong></p><p>Through this experience, I realized that certain skills are essential for conducting a proper investigation:</p><ul><li><p><strong>Observation Skills:</strong> If I had not noticed the dog stealing from another room, I might have never considered that possibility for my own missing container. In any investigation, paying attention to small details is key.</p></li><li><p><strong>Open-mindedness:</strong> Initially, I was convinced that my roommate must have taken my snacks. But keeping an open mind helped me explore other possibilities. In an RCA, jumping to conclusions too soon can lead to the wrong findings.</p></li><li><p><strong>Analytical Thinking:</strong> Instead of reacting emotionally, I examined the situation logically—first questioning my roommate, then checking different locations, and finally observing patterns before forming a conclusion. Similarly, in a professional setting, RCA requires careful analysis rather than assumptions.</p></li></ul><p>This experience taught me an important lesson: investigations should be based on facts and evidence rather than assumptions. Whether in daily life or the workplace, a thorough RCA helps solve problems effectively and prevents misunderstandings.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 03:55:32 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3344625070</guid>
      </item>
      <item>
         <title>Soledad Ortega - 301403685</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3344634113</link>
         <description><![CDATA[<p>At the laboratory where I was doing an internship there was an issue because a reagent was running out fast. This reagent was used mostly to maintain the desired pH of a buffer solution. So, the person who wanted to know what was happening asked us how we perform titration and other techniques necessary for the preparation of that buffer. However, it seemed that everybody was doing it correctly. They prepared the buffer solution to check if something was unusual and found out that the ph-meter used for that specific procedure was not working properly. It hasn’t been calibrated for some time unlike the other ph-meters from the lab.</p><p>As seen in the example, If they would have just blame the students they might have not find the real issue and the problem would have continue. However, if the wrong root cause is identified it can be disastrous for a company. It can economically impact it because the problem will still be there, and resources will be lost. The reputation of the company can be affected too. If the root cause is not the right one the problems will persist, and the trust of costumers and consumers will be affected.</p><p>Due to this the individual who perfomrs Root Cause Analysis regularly should show a high performance of critical thinking while paying attention to details. This person should be able to “see outside the box” so that the real issue to a problem can be found.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 04:05:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3344634113</guid>
      </item>
      <item>
         <title>Priya Parmar - 301396731</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3344711497</link>
         <description><![CDATA[<p>During my research on garlic's antimicrobial capabilities, I discovered contradictions in the results—some tests indicated considerable bacterial suppression, while others did not. To determine the underlying cause, I investigated potential parameters such as garlic extract manufacturing process, storage conditions, and bacterial strain variances. After further testing, I observed that freshly prepared garlic extract has better antibacterial properties than aged extracts. The variation resulted from variations in active chemicals throughout time.</p><p><br/></p><p>If the wrong underlying cause had been identified, it could have resulted in inaccurate conclusions, such as presuming garlic was ineffective when the real problem was improper preparation. It would also have wasted time by repeating studies without addressing the underlying issue. Throughout the process, I used critical transferable skills such as problem solving to identify and resolve the issue, data analysis to compare test findings, and attention to detail to ensure uniformity in all tests. I used Root Cause Analysis (RCA) to increase the accuracy of my study and assure dependable outcomes. <br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 05:39:14 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3344711497</guid>
      </item>
      <item>
         <title>Shruti Doshiyad(301398229)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3344713815</link>
         <description><![CDATA[<p>During my internship at a Rapturebiotech company, I worked on problem-solving and quality control, including Root Cause Analysis (RCA). In one case, we investigated inconsistencies in a fermentation process. Using the 5 Whys and Fishbone Diagram, we found that variations in nutrient composition were causing the issue. To fix this, we improved raw material testing and adjusted process controls. Identifying the wrong root cause can have serious effects. For example, if a company blames equipment failure when the real problem is microbial contamination, the issue will keep happening. This can also lead to financial losses and damage a company’s reputation if the problem isn’t properly fixed. To do RCA well, key skills include analytical thinking to find the real cause, attention to detail to notice small changes, and good communication to work with teams. Problem-solving and data analysis also help in making the right corrections and preventing future issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 05:41:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3344713815</guid>
      </item>
      <item>
         <title>Shruti Shah (301395610)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3345837011</link>
         <description><![CDATA[<p>One weekend, I decided to bake a cake for a family gathering. I’d watched countless YouTube videos, followed recipes carefully, and was feeling confident about the whole process. I mixed the ingredients, preheated the oven, and set the timer. Everything seemed to be going perfectly. However, when I pulled the cake out of the oven, I was shocked to find that it had collapsed in the middle. It looked nothing like the fluffy cake I was expecting. I was frustrated, but determined to figure out what went wrong.</p><p>I could’ve easily blamed myself, but instead, I decided to approach this problem like a mystery to solve. I thought back to everything I had done—from the mixing to the baking. I knew I hadn’t missed any ingredients, but something wasn’t adding up. I decided to do a little Root Cause Analysis (RCA) by retracing my steps.</p><p>I started by looking at the recipe again and watching a few more YouTube videos. One of the videos mentioned that overmixing the batter could cause the cake to collapse. That rang a bell! I realized that while I was following the instructions, I had spent a bit too much time mixing the batter, trying to get it perfectly smooth. It turned out that overmixing the batter could have incorporated too much air, causing the cake to rise too quickly and then collapse when it cooled down. I called a friend who bakes often, and they confirmed that under-mixing is often better for cakes, as it helps the batter rise more evenly and gently.</p><p>Armed with this new insight, I decided to try again, but this time, I mixed the batter just enough to combine the ingredients, avoiding the overmixing. I also made sure to check the oven temperature to ensure it wasn’t too hot, which can also lead to the cake collapsing. When I pulled the cake out of the oven this time, it was perfectly risen, golden on top, and beautifully firm. It was exactly what I had envisioned!</p><p>Had I not identified the root cause—overmixing the batter—the same issue might have occurred again. Instead of blaming myself, I took a systematic approach to figure out what went wrong, and this time the cake turned out perfectly.</p><p>This experience taught me that baking, like any other process, requires attention to detail and patience. Just like RCA in problem-solving, sometimes the key to success is in figuring out the small details—whether it's how long to mix the batter or making sure the oven temperature is right. Now, whenever I bake, I apply that same thinking: stop, analyze, and adjust as needed. It’s a lesson that goes beyond the kitchen.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 22:00:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3345837011</guid>
      </item>
      <item>
         <title>Sonu Mahato (301396573)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3345857787</link>
         <description><![CDATA[<p>When I worked as a Quality Control Technician in a pharmaceutical company back home, I was part of a team that investigated a recurring issue with some of our production batches. At first, we thought the problem was with the raw materials, since some batches were failing our quality tests. But after digging deeper, we found out the real issue was the way the materials were being stored. The storage conditions weren’t ideal, and that was affecting the materials' stability. Once we fixed the storage setup and put better monitoring in place, the quality of the batches improved, and the issue was solved.</p><p>If we had misidentified the root cause, the company could have spent a lot of time and money trying to fix things that weren’t actually the problem. For example, if we’d just focused on the raw materials, we could have ended up changing suppliers or making unnecessary adjustments to production equipment. That would’ve been a waste of resources. Worse, if we hadn’t caught the storage issue, the same problems might have kept happening, causing delays and potentially affecting the company’s reputation.</p><p>From my experience, I think the most important skills for conducting RCAs are problem-solving and attention to detail. It’s all about digging into the data, asking the right questions, and not jumping to conclusions too quickly. And of course, communication is key, especially when you’re working with multiple departments to uncover the true cause of a problem.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-27 22:33:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3345857787</guid>
      </item>
      <item>
         <title>Nimitha Muraleedharan (301379406)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3346144641</link>
         <description><![CDATA[<p>As an IELTS tutor, I had this one group of students who were struggling with the reading and writing sections. Despite knowing the material, their scores just were not improving, and I could not figure out why. At first, I assumed the issue was that they were not fully understanding the content, so I focused on teaching more vocabulary and grammar. But as I spent more time working with them, I realized the real problem was not their knowledge but their test-taking strategy. They were not managing their time well during the exam, and because of that, they were rushing through the questions and missing important details.</p><p>Once I figured out what was really going on, we worked on time management strategies. I taught them how to skim and scan the reading passages, and how to allocate their time properly so they would not feel rushed. After a few weeks of practicing, their scores started to improve. If I had not understood how deeper the the root cause is, I probably would have just kept teaching them grammar and vocabulary, which would not have helped with their time management problem at all. That would have meant more frustration for them and no real improvement in their results.</p><p>This experience really showed me how important a few key skills are when figuring out the root cause of a problem. For one, <strong>attention to detail</strong> is crucial as you need to notice patterns and listen carefully to what is going wrong. Also, <strong>good communication</strong> is essential. I had to ask my students what they were feeling during the exam and really understand their challenges. Finally, <strong>critical thinking</strong> helped me step back and question the obvious answers. It made me think beyond the surface and find the actual cause. These skills are important not just in teaching, but really in any situation where you’re trying to solve a problem.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 04:03:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3346144641</guid>
      </item>
      <item>
         <title>Marie-Joy Cruz </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3346231762</link>
         <description><![CDATA[<p>During my Food Science Technology research on <em>Listeria innocua</em> in ice cream, we noticed unexpected inconsistencies in bacterial growth results across different trials. To determine the root cause, we conducted a Root Cause Analysis (RCA) by systematically reviewing each step, including sample preparation, incubation conditions, and equipment sterility. We discovered that temperature fluctuations in storage placement were affecting bacterial survival, leading to unreliable results. If we had misidentified the root cause, we could have wasted time and resources while continuing to produce inaccurate data. This experience highlighted the importance of critical thinking, attention to detail, problem-solving, and teamwork in ensuring accurate RCA investigations, not only in research but in any industry where quality and consistency matter.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 06:00:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3346231762</guid>
      </item>
      <item>
         <title>Hereldus(301350813)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3346310059</link>
         <description><![CDATA[<p>As a food technologist, I once participated in a Root Cause Analysis (RCA) investigation at a dairy processing plant where we experienced an unexpected increase in microbial contamination in our yogurt products. Our team meticulously examined each step of the production process, from raw material reception to packaging. Through careful data analysis and systematic questioning, we discovered that a recent change in our cleaning protocol had inadvertently created conditions favorable for bacterial growth in hard-to-reach areas of our filling equipment. This experience highlighted the importance of thorough investigation and the interconnectedness of seemingly unrelated factors in food production.</p><p>The RCA process taught me valuable lessons about the critical nature of identifying the true root cause in the food industry. Misidentifying the root cause could have led us to implement ineffective solutions, potentially resulting in continued product contamination and serious food safety risks. Moreover, it could have damaged our reputation with retailers and consumers, leading to significant financial losses and potential regulatory issues. This experience reinforced the importance of analytical thinking, attention to detail, and cross-functional collaboration in maintaining food quality and safety standards.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 07:46:51 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3346310059</guid>
      </item>
      <item>
         <title>Jino Sabu (301336209)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3346325707</link>
         <description><![CDATA[<p><strong>Fixing Unexpected Browning in Homemade Dried Banana Chips</strong></p><p>I decided to make homemade&nbsp;<strong>dried banana chips</strong>&nbsp;a while ago&nbsp;as a healthier snack. I sliced some ripe bananas and put them in the oven to dry. After a few hours, I expected <strong>crisp, golden-yellow chips</strong>, but instead, they turned <strong>dark brown and unappetizing</strong>.</p><p>I was disappointed and started questioning <strong>what went wrong.</strong> 🤔</p><p><strong>Applying Root Cause Analysis (RCA) to My Mistake</strong></p><ol><li><p>The banana chips turned dark brown instead of golden-yellow. The texture was fine, but they <strong>looked unappealing</strong>.</p></li><li><p>I had used <strong>fully ripe bananas</strong> (not overripe). I sliced them evenly and <strong>baked them at a low temperature</strong> for drying. I did <strong>not</strong> do any pre-treatment (just sliced and dried).</p></li><li><p><strong>Why did the bananas turn brown?</strong> → Enzymatic browning (oxidation) occurred. <strong>Why did oxidation happen?</strong>  Polyphenol oxidase (PPO) in bananas was still active. <strong>Why was PPO active?</strong> I didn’t blanch or use an anti-browning agent before drying. <strong>Why didn’t I use a pre-treatment?</strong>  I didn’t realize it was necessary.</p><p><strong>Why didn’t I know?</strong> → I skipped researching proper drying methods.</p></li><li><p><strong>I didn’t pre-treat the bananas to prevent oxidation, leading to browning.</strong></p></li></ol><p><strong>Correcting My Mistake &amp; Learning from It</strong></p><p>After realizing my mistake, I tried again, this time following a <strong>better process:</strong><br>✅ <strong>Soak the banana slices in lemon water</strong> for a few minutes before drying.<br>✅ <strong>Tested blanching</strong> (a quick steam treatment) before drying to stop enzyme activity.<br>✅ <strong>Controlled the drying temperature</strong> to reduce browning reactions.</p><p>The result? <strong>Perfectly golden, crispy banana chips!</strong> ✨</p><p><strong>Life Lesson Learned:</strong></p><p>Sometimes, small <strong>preparatory steps</strong> (like blanching or using lemon juice) make a <strong>huge difference in the outcome</strong>—not just in food, but in life too.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 08:03:54 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3346325707</guid>
      </item>
      <item>
         <title>Leeja Johnson (301403846)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3346961409</link>
         <description><![CDATA[<p>I was once involved in an investigation at the yogurt plant where a batch of yogurt wasn’t turning out right—something was off with the texture. It wasn’t as smooth and thick as it should have been. At first, we thought maybe the fermentation process had gone wrong or the temperature was off, but when we looked closer, the problem wasn’t what we expected. It turned out that the pH meter used to measure the acidity during fermentation had been miscalibrated. This led to the fermentation happening too quickly, which messed with the yogurt’s consistency. Once we figured that out and fixed the pH meter, the batches started turning out perfectly again.</p><p>If we had just assumed that the problem was with the fermentation process or the ingredients and didn’t catch the pH meter issue, we would have kept making the same mistake. The texture of the yogurt would’ve continued to be off, and that could have led to unhappy customers or even recalls, which no company wants. On top of that, if we’d been fixing the wrong thing, we would’ve wasted time, energy, and money, which could’ve hurt the company’s bottom line.</p><p>When it comes to RCA, it’s all about being able to think critically and pay attention to all the little details. we can’t just look at the obvious things; sometimes the problem is hidden in plain sight, like with that pH meter. Communication is also huge because we need to share our findings with the team clearly so everyone’s on the same page and the right changes are made quickly.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 18:10:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3346961409</guid>
      </item>
      <item>
         <title>Asmit Shrestha (301348100)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347018267</link>
         <description><![CDATA[<p>During our experiment investigating the antimicrobial effect of <em>Lactobacillus acidophilus</em> on <em>E. coli</em> in lettuce, we encountered inconsistent bacterial reduction across different trials. Initially, we suspected that variations in <em>L. acidophilus</em> concentration were responsible, but after conducting a Root Cause Analysis (RCA), we systematically examined other factors such as bacterial suspension preparation, sample handling, and incubation conditions. Through careful observation, we discovered that inconsistent homogenization of lettuce samples and slight variations in incubation temperature were affecting our results. To address this, we standardized the homogenization process and maintained strict control over incubation conditions, which improved the reliability of our findings. This experience reinforced the importance of method standardization, data verification, and process consistency<strong> </strong>in scientific research.</p><p>Misidentifying the root cause of an issue can have serious consequences. One major impact is misinterpretation of experimental results, which can lead to incorrect conclusions and flawed scientific recommendations. For example, if we had wrongly assumed that <em>L. acidophilus</em> concentration was the main issue, we might have adjusted the bacterial suspension rather than addressing the actual cause—sample homogenization. Another significant consequence is ineffective food safety recommendations. If an RCA fails to identify the true cause of <em>E. coli</em> survival, a promising antimicrobial method might be dismissed, leading to poor decision-making in food preservation strategies. Conducting RCA requires critical thinking, attention to detail, data analysis, and problem-solving skills, all of which are transferable to industries such as food safety, quality control, and scientific research</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 19:12:27 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347018267</guid>
      </item>
      <item>
         <title>Genina Joy Fusi - 301366085</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347100253</link>
         <description><![CDATA[<p>During my time as a QA technician, I participated in a Root Cause Analysis investigation following a recurring issue in product quality. The situation involved an increase in customer complaints regarding defective packaging, which led to contamination risks. Initially, the team suspected that a supplier change was the root cause, as the issue coincided with the introduction of new materials. However, after conducting a thorough RCA using the "5 Whys" and fishbone diagram methods, we discovered that the actual problem stemmed from a misalignment in the sealing equipment, causing inconsistent seals. Once identified, corrective actions included recalibrating the machinery and implementing a more rigorous maintenance schedule. As a result, the defect rate significantly decreased, and customer complaints dropped.</p><p>Identifying the wrong root cause in an RCA investigation can have serious consequences for a company. First, ineffective corrective actions may be implemented, leading to recurring issues and increased costs. For instance, if the supplier had been wrongly blamed in my case, switching materials would not have resolved the problem, wasting time and resources while the real issue persisted. Second, customer trust and company reputation could suffer due to repeated quality failures. If defects continue despite supposed corrective actions, customers may lose confidence in the brand, leading to loss of business and potential regulatory scrutiny.</p><p>Conducting RCAs regularly requires several transferable skills. Critical thinking is essential to systematically analyze data and avoid jumping to conclusions. Attention to detail ensures that no contributing factor is overlooked, helping to accurately identify the root cause. Additionally, strong communication skills are crucial when collaborating with cross-functional teams, presenting findings, and ensuring corrective actions are understood and implemented effectively. These skills allow QA professionals to conduct thorough investigations and contribute to long-term quality improvements.</p><p>&nbsp;</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 21:05:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347100253</guid>
      </item>
      <item>
         <title>Kashish Panchal-301402603</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347164557</link>
         <description><![CDATA[<p>While working on a project related to food preservation, I was involved in an RCA investigation when a batch of homemade tomato paste developed unexpected spoilage before its expected shelf life. Initial quality tests showed microbial growth, which indicated that something had gone wrong in the preservation process. After testing different hypotheses, we discovered the root cause: inconsistent heating during pasteurization. A temperature variation in certain batches allowed heat-resistant microbes to survive, leading to spoilage over time.</p><p><em>Corrective Actions Taken:</em></p><p>Standardized Heating Procedures: We calibrated equipment and set stricter controls to ensure uniform heating.</p><p>Additional Quality Checks: Regular microbial testing before and after pasteurization was implemented.</p><p>Process Documentation &amp; Training: The team was retrained on temperature monitoring and verification steps.</p><p>Impact of Identifying the Wrong Root Cause</p><p>Wasted Time and Resources – If we had assumed that the issue was due to ingredient contamination instead of heating inconsistencies, we might have focused on sourcing different tomatoes rather than fixing the actual pasteurization process. This would have led to continued spoilage and financial loss.</p><p>Reputation Damage – If this had been a commercial product, persistent spoilage issues could have resulted in customer complaints, loss of trust, and possible regulatory scrutiny for failing to maintain food safety standards.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-02-28 23:38:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347164557</guid>
      </item>
      <item>
         <title>Hrishika Raj 301379931</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347197456</link>
         <description><![CDATA[<p><strong>1. My Experience with a Root Cause Analysis Investigation</strong></p><p>I’d like to share my experience with a <strong>Root Cause Analysis (RCA)</strong> investigation that I participated in. While I can’t mention specific company or product names due to confidentiality, I can describe the process and what I learned.</p><p>In one instance, we were facing a recurring issue with a piece of equipment that kept malfunctioning, causing delays in production and increasing costs. My team was tasked with conducting an RCA to identify the root cause of the problem. We used the <strong>5 Whys</strong> technique, which involves asking "Why?" repeatedly until we reached the root cause. For example:</p><ul><li><p>Why did the equipment fail? Because a critical component overheated.</p></li><li><p>Why did it overheat? Because the cooling system wasn’t functioning properly.</p></li><li><p>Why wasn’t the cooling system working? Because the filters were clogged.</p></li><li><p>Why were the filters clogged? Because they hadn’t been cleaned regularly.</p></li><li><p>Why weren’t they cleaned regularly? Because there was no maintenance schedule in place.</p></li></ul><p>Through this process, we discovered that the root cause was the lack of a maintenance schedule. We implemented a preventive maintenance plan, and the issue was resolved. This experience taught me the importance of digging deep to find the true root cause of a problem.</p><p><strong>2. Impact of Identifying the Wrong Root Cause</strong></p><p>Identifying the wrong root cause during an RCA can have serious consequences for a company. Here are two examples of potential outcomes:</p><ol><li><p><strong>Wasted Resources:</strong> If the wrong root cause is identified, the company might invest time and money into fixing the wrong problem. For example, if a machine failure is incorrectly attributed to operator error, the company might spend money on retraining employees instead of addressing the actual issue, such as a faulty component.</p></li><li><p><strong>Recurring Issues:</strong> If the real root cause isn’t addressed, the problem will likely keep happening. This can lead to ongoing inefficiencies, increased costs, and even safety risks. For instance, if a product defect is blamed on a supplier’s materials but the actual issue is a flaw in the manufacturing process, the defect will continue to occur, damaging the company’s reputation and customer trust.</p></li></ol><p><strong>3. Transferable Skills for Conducting RCAs</strong></p><p>Conducting RCAs regularly requires a set of transferable skills that are valuable in any industry. Here are the ones I think are most important:</p><ol><li><p><strong>Analytical Thinking:</strong> The ability to break down complex problems, analyze data, and identify patterns is crucial for uncovering the root cause.</p></li><li><p><strong>Communication:</strong> Effective communication is key when working with a team to gather information, share findings, and implement solutions. This includes both verbal and written communication.</p></li><li><p><strong>Attention to Detail:</strong> Small details can often lead to big discoveries. Paying close attention to every aspect of the problem is essential for an accurate RCA.</p></li><li><p><strong>Problem-Solving:</strong> RCA is all about solving problems, so having a systematic approach to troubleshooting and finding solutions is critical.</p></li><li><p><strong>Collaboration:</strong> RCA often involves working with a team, so the ability to collaborate, listen to others, and incorporate different perspectives is important.</p></li><li><p><strong>Patience and Persistence:</strong> Sometimes, finding the root cause takes time and multiple attempts. Being patient and persistent ensures that you don’t stop until the real issue is identified.</p></li></ol><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 01:20:15 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347197456</guid>
      </item>
      <item>
         <title>Mobisola Onipede 301400742</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347199304</link>
         <description><![CDATA[<p><strong>Root Cause Analysis Reflection</strong></p><p><br>While working in the Quality Control (QC) department of a bakery ingredient manufacturing company, I was involved in a Root Cause Analysis (RCA) after a customer reported receiving a mislabeled product—a bag of donut mix labeled as cake mix. This was a serious issue, as the two products were manufactured on separate lines but shared the same conveyor system at a convergence point.</p><p><br/></p><p>The mistake could have caused not only customer dissatisfaction but also regulatory complications.</p><p>I began the investigation by reviewing the production records and identifying the operators for both shifts involved. After analyzing the situation, I discovered that a bag had been removed for weight adjustment at the end of the morning shift. </p><p><br/></p><p>However, due to an improper handover between shifts, an afternoon shift operator unknowingly placed the adjusted bag back on the wrong production line, causing the mix-up. The root cause was inadequate shift handover procedures.</p><p><br/></p><p>To prevent future occurrences, we implemented a new handover protocol where both morning and afternoon shift operators met together in a full-team session, supervised by a manager. This ensured critical information was exchanged clearly and reduced the chances of similar errors.</p><p><br/></p><p><strong>Impact of Incorrect RCA on a Company</strong><br>Identifying the wrong root cause could have led to:</p><ul><li><p><strong>Recurring Issues &amp; Financial Losses</strong> – The same problem would persist, causing more complaints and potential recalls.</p></li><li><p><strong>Reputation &amp; Compliance Risks</strong> – Mislabeling could result in regulatory fines and loss of customer trust.</p></li><li><p><br/></p></li></ul><p><strong>Key Transferable Skills for RCA Investigators</strong></p><ul><li><p><strong>Attention to Detail</strong> – Analyzing production logs revealed the root cause.</p></li><li><p><strong>Communication &amp; Listening</strong> – Engaging with operators ensured accurate information.</p></li><li><p><strong>Problem-Solving &amp; Critical Thinking</strong> – A structured approach helped identify the true cause.</p></li></ul><p>This experience emphasized the importance of thorough investigations and corrective actions in maintaining quality control.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 01:25:06 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347199304</guid>
      </item>
      <item>
         <title>Jeslin Mariya Chakkalakkal Jacob-301403954</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347493948</link>
         <description><![CDATA[<p>A few years ago, I was part of a team at work where we noticed a recurring issue with a critical process. The problem was causing delays and frustration among team members, but no one could pinpoint exactly why it kept happening. My supervisor asked me to join a small group to investigate the issue. We started by gathering data, interviewing team members, and mapping out the process step by step. At first, it seemed like the issue was caused by a lack of communication between departments. However, as we dug deeper, we realized the root cause was actually a poorly designed workflow that created bottlenecks. Once we identified this, we proposed a redesign of the process, which significantly improved efficiency and reduced delays.</p><p>If the wrong root cause had been identified, the company could have faced serious consequences. For example, if we had blamed the issue solely on communication and implemented more meetings or check-ins, it would have wasted time and resources without solving the actual problem. Another potential outcome could have been decreased morale among employees, as they might have felt unfairly blamed for something that wasn’t their fault.</p><p>From this experience, I learned that transferable skills like critical thinking, attention to detail, and effective communication are crucial for conducting RCA. Critical thinking helps you look beyond the obvious and dig deeper into the problem, while attention to detail ensures you don’t overlook important clues. Communication is key because you need to collaborate with others, ask the right questions, and present your findings clearly to stakeholders.</p><p>This experience taught me how important it is to approach problems methodically and remain open to discovering unexpected root causes. It also showed me how RCA can lead to meaningful improvements when done correctly.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 15:19:47 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347493948</guid>
      </item>
      <item>
         <title>Samuel Olagbegi (301405500)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347529505</link>
         <description><![CDATA[<p>I had an experience at home when troubleshooting a persistent issue with a faulty kitchen appliance. Instead of repeatedly fixing the symptom, i applied RCA by checking the electrical connections, testing different settings, and eventually discovering that the issue stemmed from a power fluctuation rather than the appliance itself.</p><p><br/></p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><ol><li><p>If a company wrongly attributes bacterial contamination in food to packaging rather than improper storage, they might invest in unnecessary packaging solutions while the real issue (temperature control) remains unaddressed. This could lead to continued contamination, product recalls, and financial loss.</p></li><li><p>If a hospital misdiagnoses an infection as being caused by a specific bacteria without conducting proper tests, the patient may receive incorrect antibiotics, leading to prolonged illness or antibiotic resistance.</p></li></ol><p><br/></p><p><strong>Transferrable Skills Important for RCA</strong></p><ol><li><p>Critical Thinking</p></li><li><p>Attention to detail</p></li><li><p>Analytical and data interpretation skills</p></li><li><p>Communication and collaboration</p></li></ol><p> </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 16:49:30 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347529505</guid>
      </item>
      <item>
         <title>Michelle Paucar (301382289)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347541955</link>
         <description><![CDATA[<p>During the development of my crunchy fruit leather snack, I encountered a significant challenge that required deeper investigation. Some batches exhibited excessive sourness, making them unappealing during sensory evaluations, while others had inconsistent textures, some were too brittle while others remained overly chewy. Initially, I attributed these issues to ingredient selection and drying time, treating them as separate problems. However, as inconsistencies persisted, I realized a more comprehensive analysis was necessary to identify the underlying cause.</p><p>To systematically assess the issue, I conducted a root cause analysis, testing different fruit combinations and closely monitoring the drying process. through this approach I discovered that certain fruits released excess acidity when dehydrated, which intensified their sourness. Simultaneously, fluctuations in drying temperature and airflow distribution were impacting the final texture, preventing a uniform crunch. This finding indicated that the problem was not isolated to ingredient selection but was instead influenced by the interaction between raw material composition and process parameters.</p><p>To address these challenges, I refined the fruit formulation by blending sour fruits with natural sweeter ones, achieving a balanced flavor without the need for artificial additives. Additionally, I optimized the drying conditions, ensuring consistent temperature control and uniform airflow to mantain the desired texture across all batches. As a result, the product achieved sensory acceptance, improved production consistency, and enhanced process efficiency, allowing for successful transition from development to commercialization. This experience reinforced the importance of conducting thorough root cause analysis early in the development process to prevent larger-scale production inefficiencies and ensure product quality.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 17:23:28 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347541955</guid>
      </item>
      <item>
         <title>Kartik Pathania (301258301)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347559481</link>
         <description><![CDATA[<p>During my time as a <strong>Research Technician</strong>, I was part of a <strong>Root Cause Analysis (RCA)</strong> investigation that aimed to determine why a batch of experimental plants showed unexpected nutrient deficiencies despite following the standard fertilization protocol. The issue became apparent during a routine evaluation when the plants exhibited stunted growth and chlorosis. Our team conducted a thorough analysis, reviewing all variables from soil composition and watering schedules to environmental conditions and potential cross-contamination. After a series of tests and discussions, we traced the issue back to a mislabeled batch of nutrient solution that had lower nitrogen content than specified. By identifying this root cause, we were able to adjust the nutrient mix promptly, which helped the plants recover and allowed the research project to proceed without significant delays.</p><p>Identifying the wrong root cause during an investigation can have serious repercussions for a company. For example, if a company misattributes a <strong>quality control issue</strong> in a food production line to machine malfunction instead of a <strong>supply chain issue</strong>, it may invest heavily in equipment repairs while the real problem persists, leading to continued production delays and potential <strong>reputational damage</strong>. Another scenario could involve a misdiagnosis of a <strong>process failure</strong> in a greenhouse environment, such as attributing <strong>poor crop performance</strong> to <strong>lighting issues</strong> rather than an <strong>underlying irrigation problem</strong>. This could lead to wasted resources on new lighting systems while the crop yield continues to suffer.</p><p>When it comes to <strong>transferable skills</strong> for those conducting RCAs regularly, I believe that <strong>critical thinking</strong> and <strong>attention to detail</strong> are paramount. An investigator must dissect complex situations, analyze data meticulously, and consider all possible variables. Additionally, <strong>communication skills</strong> are vital, as the RCA process often involves collaborating with different departments and presenting findings clearly and effectively. The ability to remain <strong>objective</strong> and avoid jumping to conclusions is also critical, as it ensures that the analysis is based on evidence rather than assumptions. Ultimately, an effective RCA investigator combines <strong>analytical prowess</strong> with <strong>collaborative problem-solving</strong>, leading to more accurate diagnoses and sustainable solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 18:17:05 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347559481</guid>
      </item>
      <item>
         <title>Bach Lam (309397716)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347582883</link>
         <description><![CDATA[<p>There was a time when our induction range cooktop was not functioning properly, displaying error codes we could find in the manual to diagnose the problem. Instead of jumping to conclusion and buying a new induction range cooktop (very expensive), we used RCA and the help of a some relatives to find out that the issue was not the appliance itself the wiring was the issue. We ended fixing the wiring ourselves with guidance of an electrician (relative) and ended up fixing the issue without spending too much money.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 19:32:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347582883</guid>
      </item>
      <item>
         <title>Prakriti Poudel - 301379161</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347615769</link>
         <description><![CDATA[<p>As a cashier at a grocery store, I participated in a small investigation to find out why the cash register was short by $20. At first, we thought it could be theft or fake bills, but after reviewing receipts and payments, we found the real cause is that one of the cashier gave a customer too much change.</p><p>If we had wrongly blamed theft, the store could have spent money on unnecessary security cameras or blamed an innocent cashier, damaging trust among staff.</p><p>The most important skills for root cause analysis are attention to detail, to catch small mistakes, and teamwork and communication, to work together and share observations. This experience showed me that finding the true cause prevents bigger problems.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 21:30:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347615769</guid>
      </item>
      <item>
         <title>Mohammad Fahad Noor (301379915)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347624502</link>
         <description><![CDATA[<p>I participated in an RCA investigation related to food spoilage in a controlled storage environment. The issue involved unexpected spoilage of dairy products before their expiration dates. To identify the root cause, I worked with my team to analyze factors such as storage temperature, humidity levels, packaging integrity, and microbial contamination.</p><p>After conducting microbial tests and reviewing storage logs, we discovered that inconsistent temperature regulation in the refrigeration unit was accelerating bacterial growth. The issue was traced back to a malfunctioning thermostat. Once identified, the faulty component was replaced, and additional monitoring procedures were implemented to prevent future occurrences.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-01 22:05:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347624502</guid>
      </item>
      <item>
         <title>Asma Refaideen (301205451) </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347691713</link>
         <description><![CDATA[<p>During my co-op experience in a chemistry lab, I was involved in a <strong>Root Cause Analysis (RCA)</strong> when we noticed contamination in a batch of prepared media. The issue was flagged when multiple samples showed unexpected microbial growth despite following standard preparation procedures. My supervisor asked me to help investigate the potential cause, so I retraced our steps, checked equipment calibration, reviewed cleaning logs, and ensured proper handling of sterile materials. After carefully analyzing each factor, we discovered that a pipette used for media preparation had not been properly sterilized. This led to corrective actions, including retraining staff on sterilization protocols and implementing a more rigorous equipment-check process.</p><p>Identifying the wrong root cause in an investigation can lead to <strong>serious consequences</strong> for a company. <strong>First, it can result in recurring product defects or contamination issues</strong>, causing financial losses and damaging customer trust. <strong>Second, it can lead to unnecessary corrective actions</strong>, wasting time and resources on fixing the wrong problem while the real issue persists.</p><p>Individuals conducting <strong>RCA investigations</strong> need strong <strong>critical thinking, attention to detail, and problem-solving skills</strong>. They must also have <strong>effective communication skills</strong> to collaborate with different teams and ensure findings lead to meaningful corrective actions. This experience reinforced the importance of <strong>thorough investigation and accurate root cause identification</strong> in maintaining product safety and quality.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 02:38:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347691713</guid>
      </item>
      <item>
         <title>VAIDEHI BHATT 301396714</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347712652</link>
         <description><![CDATA[<p>1. RCA Experience:</p><p>In my previous job, I performed an RCA analysis when a major system failure caused huge delays in operations. We gathered data, scanned logs, and interviewed employees to determine the root cause. It seemed at first like a hardware failure, but upon closer inspection, it was discovered that an incompatibility issue was created by a software update that caused system crashes.</p><p>2. Impact of Identifying the Incorrect Root Cause</p><p>If we had incorrectly identified the root cause as a hardware failure, the company would have spent money replacing functional hardware while the actual problem persisted. Furthermore, prolonged downtime might have cost money and upset customers.</p><p>3. Transferable Skills for RCA</p><p>Critical thinking plays an important role in effectively analyzing the data and pinpointing underlying issues. Moreover, communication skills are essential in getting the information effectively and having all the stakeholders clear about the findings and solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 03:33:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347712652</guid>
      </item>
      <item>
         <title>RUSHIT PATEL 301409928</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347712817</link>
         <description><![CDATA[<p>1. RCA Experience:</p><p>An RCA experience was faced at home when my vehicle was not starting several times. I initially assumed that it was the battery and replaced it, but the problem still persisted. Upon closer inspection, I tried testing the alternator and understood that it was not charging the battery properly, which was actually the cause of the problem.</p><p>2. Impact of Identifying the Wrong Root Cause:</p><p>Had I just replaced the battery, I would have still been facing the same issue, spending money unnecessarily and getting frustrated. In a corporate setting, an incorrectly diagnosed RCA can lead to repeated operational failure and lost monetary resources.</p><p>3. Transferable Skills for RCA</p><p>Attention to detail is required to recognize patterns and likely causes that may not easily reveal themselves. Furthermore, problem-solving enables one to rationally attack problems and systematically rule out likely false assumptions to uncover the real cause.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 03:34:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347712817</guid>
      </item>
      <item>
         <title>Yan Yin Sin (301350498)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347734815</link>
         <description><![CDATA[<ol><li><p>RCA experience</p></li></ol><p>When I was a research assistant, our team worked on formulating a new biodegradable clay material. One of our goals was to apply this material in 3D printing, which required turning it into filaments using an extruder. However, we faced repeated failures—the filament either broke during extrusion or had inconsistent thickness. To identify the root cause, we asked a series of "why" questions. We determined that the filament broke because it wasn’t cooling properly after extrusion, making it too weak to withstand the pulling force of the filament maker. Digging deeper, we found that the material had a lower melting point, and the extruder temperature was too high, causing it to become too molten. Adjusting the temperature resolved the issue, allowing us to produce stable filaments.</p><ol start="2"><li><p>Incorrectly identifying the root cause in an investigation</p></li></ol><p>One major impact is the waste of resources, such as time, raw materials, and labor, when ineffective solutions are implemented based on the wrong root cause. Additionally, failing to address the true cause can lead to a loss of customer confidence. If a product defect or process failure is seemingly resolved but resurfaces over time, it can damage the company’s reputation and credibility, potentially leading to financial losses or regulatory issues.</p><ol start="3"><li><p>Important transferable skills for successful RCA</p></li></ol><p>Conducting effective RCA requires key transferable skills, particularly critical thinking and attention to detail. Critical thinking helps break down complex problems, analyze patterns, and ensure that conclusions are based on solid reasoning rather than assumptions. Attention to detail is essential in identifying subtle factors that could contribute to the issue, preventing oversight of important variables. These skills allow RCA professionals to systematically approach problems and implement lasting solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 04:49:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347734815</guid>
      </item>
      <item>
         <title>Vindhya Bindu Stalin (301379918)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347743031</link>
         <description><![CDATA[<p><br/></p><p>I was previously employed as a Customer Service Representative at a retail store, and one of the issues we observed was that some customers were charged twice for the same item at checkout. After we employed Root Cause Analysis (RCA), we monitored the POS (Point of Sale) transaction history and reviewed customer receipts to identify the factor causing the duplicate charges. For further investigation, we also observed cashier interactions with the barcode scanner and checked the system logs for inconsistencies.</p><p>We later found that the issue was caused by barcode scanners registering double scans without showing an alert in the system. To correct this, we implemented scanner recalibration and software updates, ensuring accurate item registration and preventing further incorrect charges. This solution resulted in a smooth and error-free checkout process, leading to higher customer satisfaction.</p><p>Impact of Wrong RCA</p><p>Had we just focused on human error and blamed the cashiers, we would have misidentified the root cause and failed to solve the actual issue. This could have led to unjust disciplinary actions against employees while the problem continued to affect customers, resulting in financial losses due to refunds and a decline in customer trust. One motivation that drove us to find a solution was to ensure fairness in transactions and maintain a positive customer experience.</p><p>Key Skills for Root Cause Analysis</p><p>Some of the essential skills required for Root Cause Analysis include:</p><ul><li><p>Analytical Thinking – The ability to review data and identify patterns.</p></li><li><p>Attention to Detail – Observing small inconsistencies that could lead to bigger issues.</p></li><li><p>Problem-Solving Skills – Implementing corrective actions to prevent recurrence.</p></li><li><p>Teamwork &amp; Communication – Collaborating with colleagues and managers to effectively address the issue.</p></li></ul><p>One lesson we learned from this experience is that small errors in technology can have a significant impact on operations. It is essential to analyze all possible factors before making decisions and implementing changes.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 05:17:29 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347743031</guid>
      </item>
      <item>
         <title>Seemabanu Diwan-301431171</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347756393</link>
         <description><![CDATA[<p>1. In my experience with Root Cause Analysis (RCA), I participated in an investigation to address a recurring issue with delays in our internal processes. Initially, we assumed the problem was related to technical issues, like equipment or software malfunctions. However, as we followed the RCA steps—gathering data, identifying the symptoms, and asking detailed questions—it became clear that the root cause was actually a communication breakdown between departments. This miscommunication was causing delays, as key information wasn't being passed along efficiently. The investigation taught me the importance of digging deeper into problems rather than jumping to conclusions based on surface-level symptoms. It was a valuable experience that reinforced the importance of a structured approach to problem-solving.</p><p>2.Identifying the wrong root cause in an investigation can have serious consequences for a company, leading to wasted resources and a continued lack of progress. For example, if the wrong issue is pinpointed, the company might spend significant time and money fixing the wrong problem. This could result in inefficient resource allocation, as was the case when a company mistakenly upgraded software to solve a problem, only to find out the issue was related to employee training. Another potential outcome is a decline in morale and trust among employees. If the wrong root cause is addressed and the solution doesn't resolve the issue, employees may feel frustrated and lose confidence in the company’s ability to solve problems effectively, which could lead to disengagement and lower productivity.</p><p>3. For individuals who conduct RCA regularly, several transferable skills are essential. First, critical thinking is key, as it allows individuals to analyze problems logically and differentiate between symptoms and actual causes. Being able to break down complex issues into manageable parts is fundamental to finding the real root cause. Effective communication is also crucial, as RCA often requires collaboration across different teams. Being able to ask the right questions, listen actively, and convey findings clearly ensures the process runs smoothly. Additionally, a problem-solving mindset is important, as individuals must be creative and adaptable to uncover the root causes of problems. Lastly, attention to detail plays a vital role in the RCA process. Small details often reveal the underlying issues, and being thorough and methodical ensures that nothing is overlooked, leading to more accurate conclusions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 06:02:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347756393</guid>
      </item>
      <item>
         <title>Vaibhavkumar Rabari (301403844)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3347932756</link>
         <description><![CDATA[<p><strong>My Root Cause Analysis Experience at an Ice Cream Plant</strong></p><p>As a <strong>Production Officer at an ice cream plant</strong>, I once had to investigate why a batch of ice cream had a <strong>grainy texture</strong> instead of being smooth and creamy. At first, some team members thought the issue was caused by a <strong>problem with the milk powder supplier</strong>, but instead of making quick assumptions, we decided to do a proper <strong>Root Cause Analysis (RCA)</strong>. We checked the <strong>ingredients, mixing process, and freezing conditions</strong>. After testing different possibilities, we found that <strong>a slight temperature fluctuation in the freezing process</strong> was causing tiny ice crystals to form, ruining the texture. Once we adjusted the freezing settings, the issue was fixed, and the next batch came out perfectly.</p><p>If we had misidentified the problem and blamed the supplier, we might have switched to a new one unnecessarily, wasting <strong>time and money</strong> while the real issue remained. Worse, if we had sent out the defective batch, customers would have complained, hurting our <strong>brand’s reputation</strong>.</p><p>This experience taught me how important <strong>critical thinking and problem-solving</strong> are when conducting an RCA. <strong>Attention to detail, teamwork, and clear communication</strong> also play a big role in finding and fixing problems efficiently. It showed me that in any workplace, whether in food production or another industry, <strong>finding the real cause of an issue is key to keeping things running smoothly</strong>.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 12:50:22 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3347932756</guid>
      </item>
      <item>
         <title>Smita Patel [ 301405077]</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348122289</link>
         <description><![CDATA[<p>Sure! Here’s a way you can write about your experience in root cause analysis:</p><p>During my time as a Quality Analyst in a pharmaceutical company, I frequently participated in root cause analysis (RCA) investigations to identify the underlying causes of product quality issues, deviations, or customer complaints. My role involved analyzing data, conducting thorough investigations, and collaborating with cross-functional teams to pinpoint the root cause of the problem. I employed various problem-solving methodologies like the 5 Whys, Fishbone diagrams, and Failure Mode Effects Analysis (FMEA) to facilitate these investigations.</p><p>One of the key aspects of my job was to ensure that corrective actions were identified and implemented to prevent recurrence. For instance, in one investigation, a batch of products failed to meet specified quality standards. I helped analyze the production process, reviewed equipment maintenance records, and assessed the handling of raw materials. Through this investigation, we identified a gap in equipment calibration, which was the root cause of the issue. Following corrective actions, such as recalibrating the equipment and revising maintenance schedules, product quality improved significantly.</p><p>I also assisted managers in investigations of customer complaints by performing data analysis, looking at product batches, and reviewing the entire process flow to ensure the issue was effectively addressed. My experience in RCA taught me the importance of being thorough and systematic, as well as the value of teamwork in uncovering and resolving issues.</p><p><br/></p>]]></description>
         <enclosure url="https://pixabay.com/get/gd91078e3055af257909c4cfbe1fa4a3fa82f31fe06e9c1d2a40262eb891dbd3c5911c18b11528d00661d8b30c089d475.jpg" />
         <pubDate>2025-03-02 19:02:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348122289</guid>
      </item>
      <item>
         <title>Kalgi Patel - 301281397</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348168349</link>
         <description><![CDATA[<p>When I worked at Subway, I observed that the sandwich bread was regularly drying out before being utilised, which resulted in unneeded waste and complaints from customers. I carried out a Root Cause Analysis (RCA) to determine the primary problem in order to fix this. I discovered that excessive moisture loss was being caused by inappropriate storage in open racks after looking into the handling procedures, baking process, and storage conditions. I recommended enhancing the rotation mechanism to guarantee that older batches were consumed first and storing the bread in a container with controlled humidity as a remedial measure. </p><p><br/></p><p>If the incorrect root cause is found, a business may suffer serious repercussions. For instance, needless formulation adjustments might have resulted in increased expenses and no gain if we had believed that the bread recipe, rather than storage, was the problem. Similar to this, failing to determine the underlying cause of food safety accidents can result in ongoing contamination concerns, harm to a brand's reputation.<br><br>Analytical thinking, meticulousness, and problem-solving skills are essential transferable talents when doing RCA. To guarantee that discoveries are appropriately communicated to the team and result in successful remedial actions, strong communication skills are also crucial. I learnt from my RCA experience how crucial it is to conduct in-depth research and accurately identify problems in order to increase productivity and preserve food quality.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 20:47:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348168349</guid>
      </item>
      <item>
         <title>Oorja 301295598</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348189664</link>
         <description><![CDATA[<ul><li><p><strong>Experience with a Root Cause Analysis Investigation</strong>:<br>In my role as a food Quality Assurance (QA) professional, I participated in an RCA investigation involving a recurring quality issue with a batch of products. The investigation began after multiple customer complaints about the consistency of the product's texture. The team worked together to gather data from different stages of the production process, including raw material analysis, machine settings, and environmental conditions. After investigating, we identified that the root cause was a slight fluctuation in the temperature settings of a critical piece of equipment. By adjusting the temperature parameters and implementing tighter monitoring controls, the issue was resolved. </p></li><li><p><strong>Impact of Identifying the Wrong Root Cause</strong>:<br>a) <strong>Recurring Issues</strong>: If the wrong root cause is identified, corrective actions might address only the symptoms and not the true underlying issue. For example, if the issue was due to machinery settings, but the investigation falsely pointed to raw material quality, corrective actions focused on raw materials would not prevent the issue from happening again, leading to continued customer complaints.</p><p>b) <strong>Inefficient Use of Resources</strong>: Misidentifying the root cause can lead to wasted time, effort, and resources. If a company focuses on fixing an incorrect cause, it may divert resources away from the real problem. </p></li><li><p><strong>Transferable Skills for Conducting RCA in Food QA</strong>:<br>a) <strong>Analytical Thinking</strong>: The ability to assess data and look for patterns is crucial in identifying the true root cause of quality issues. b) <strong>Attention to Detail</strong>: In food quality assurance, even the smallest change in a process or ingredient can lead to significant variations in product quality. An eye for detail allows professionals to spot inconsistencies that may indicate an underlying issue, making it an essential skill for RCA.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 21:35:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348189664</guid>
      </item>
      <item>
         <title>RIYA PATEL (301351161)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348235678</link>
         <description><![CDATA[<p>During my food science studies, I participated in a Root Cause Analysis (RCA) investigation for a contamination issue in a food processing facility. A batch of products failed microbial testing, and we analyzed potential causes such as raw material quality, sanitation procedures, and employee handling. After a thorough investigation, we identified improper cleaning of the separator as the root cause. To address the issue, corrective actions were implemented, including staff retraining and updates to the Sanitation Standard Operating Procedure (SSOP).</p><p><br/></p><p>Identifying the wrong root cause in an RCA can have serious consequences. For example, if the issue was mistakenly attributed to raw materials instead of improper sanitation, the company might unnecessarily switch suppliers, leading to wasted time and financial loss. </p><p><br/></p><p>Additionally, failing to address the actual cause can result in repeated safety violations, regulatory penalties, and loss of consumer trust, ultimately damaging the company’s reputation.</p><p><br/></p><p>To conduct an effective RCA, key skills are required. Critical thinking helps analyze complex problems, while attention to detail ensures no contributing factors are overlooked. Strong communication and teamwork are necessary for gathering accurate information and implementing solutions. Lastly, problem-solving skills are essential for developing corrective actions that prevent recurrence and improve overall operations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-02 23:22:39 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348235678</guid>
      </item>
      <item>
         <title>Taranjeet Kaur (301379927)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348455991</link>
         <description><![CDATA[<p>The role of Junior Food Technician required me to participate in Root Cause Analysis (RCA) investigations that focused on resolving repetitive product quality problems. The research consisted of data examination and ingredient handling inspection along with equipment monitoring. A key ingredient storage issue proved to be the main cause that produced the quality issues after extensive assessment. When organizations fail to identify correctly the original cause behind their problems it leads to problematic results. Such incorrect root cause identifications result in unnecessary spending on both resource adjustment costs and machinery modifications since the actual problem exists within ingredients. On-going quality problems from such an incorrect diagnosis would damage both the company's reputation and eventually erode client trust. The skills needed for RCA are analytical thinking to conduct objective data evaluation as well as problem-solving abilities to discover effective solutions, clear communication for teamwork, detailed assessment of crucial factors and teamwork which incorporates multiple perspectives. A successful RCA investigation depends on acquiring these vital competencies in any business sector.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 03:22:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348455991</guid>
      </item>
      <item>
         <title>HIRAL PATEL - 301428364</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348470280</link>
         <description><![CDATA[<p>In a lab setting, I participated in a Root Cause Analysis (RCA) when a microbial contamination issue affected our fermentation results. Initially, we suspected improper sterilization of the media, but after applying the 5 Whys method, we discovered that the contamination originated from an improperly sealed bioreactor inlet. If the wrong root cause had been identified, it could have led to wasted resources and repeated contamination, as fixing sterilization procedures wouldn’t have addressed the real issue, or data integrity issues, where inaccurate results could mislead future experiments. Key transferable skills for effective RCA in a lab include critical thinking to analyze experimental deviations, attention to detail to identify small procedural errors, and problem-solving to implement corrective actions and prevent recurrence.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 03:37:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348470280</guid>
      </item>
      <item>
         <title>Kashish Modi (301374833)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348507130</link>
         <description><![CDATA[<p>I was part of a Root Cause Analysis (RCA) at a retail store when we started getting a lot of customer complaints about delayed orders. To figure out what was going wrong, we looked at order records, talked to employees, and checked inventory logs. We found that a recent update to our inventory system was causing stock mismatches, that led to delays in fulfilling orders. To fix the issue, we set up real time inventory tracking and improved communication between the sales and warehouse teams to prevent it from happening again.</p><p>If the wrong root cause is identified, it could have create bigger problems for our company. When issues aren't properly fixed and they keep happening again and again then it frustrates the customers.For example, if slow checkout times are blamed on employees instead of a faulty POS system, staff might get unfairly blamed while the real problem continues, leading to frustration and lost sales. Similarly, if missing stock is blamed on theft rather than a system error, the company might spend extra on security and insurance instead of fixing the real issue. </p><p>Solving these kinds of problems regularly requires a few key skills. You need strong problem-solving and critical thinking to get to the real cause of the issue. Attention to detail is also important when looking at sales, customer complaints, and inventory records. Good communication helps in working with different teams to gather information. Adaptability is also crucial since things change quickly in retail, and quick decision-making is often needed. Most importantly, a customer-first mindset helps ensure that solutions not only fix the issue but also improve the shopping experience.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 04:15:42 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348507130</guid>
      </item>
      <item>
         <title>Karanjot Kalsi(301405116)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348517051</link>
         <description><![CDATA[<p><strong>My Experience with a Root Cause Analysis Investigation:</strong></p><p>"I was involved in a Root Cause Analysis (RCA) at a previous job when there was a consistent issue with product quality in our production line. After gathering data and speaking with staff, we identified that the root cause was inconsistencies in the raw materials provided by a supplier. Once we standardized ingredient checks, the problem was resolved, and the quality improved."</p><p><strong>Impact of Incorrect Root Cause Identification:</strong></p><ol><li><p><strong>Resource Misallocation</strong>: Misidentifying the problem, like blaming equipment instead of raw materials, could lead to wasted resources on repairs that won’t solve the issue.</p></li><li><p><strong>Unresolved Problems</strong>: If the wrong root cause is targeted, the problem will likely continue, damaging product quality and customer trust.</p></li></ol><p><strong>Transferable Skills for RCA:</strong></p><ol><li><p><strong>Critical Thinking</strong>: To analyze problems logically and identify underlying causes.</p></li><li><p><strong>Communication</strong>: To gather information and share findings effectively.</p></li><li><p><strong>Attention to Detail</strong>: To spot small issues that could lead to the larger problem.</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 04:26:18 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348517051</guid>
      </item>
      <item>
         <title>Manpreet(301403869)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348544938</link>
         <description><![CDATA[<p>In my healthcare role, I took part in a Root Cause Analysis (RCA) investigation following a patient’s adverse reaction to a medication. Through the RCA process, we determined that the issue stemmed from a miscommunication between the pharmacy and nursing staff regarding dosage instructions, rather than the medication itself. Incorrectly identifying the root cause in healthcare can have serious repercussions, such as jeopardizing patient safety and misdirecting resources. For instance, addressing the wrong issue could lead to ongoing patient harm or wasted efforts on ineffective solutions. Conducting RCAs effectively requires key transferable skills, including analytical thinking, attention to detail, communication, collaboration, problem-solving, and a strong understanding of healthcare systems to accurately identify and resolve issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 05:01:07 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348544938</guid>
      </item>
      <item>
         <title>Anjali Saini (301274030)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348553075</link>
         <description><![CDATA[<p><strong>Story:</strong><br>A few months ago, I experienced a situation that required me to conduct an informal Root Cause Analysis at home. One evening, I noticed some of my favorite snacks were missing from the fridge, and I was sure I had not finished them. After confirming that no one in my household had claimed responsibility, I decided to conduct a small investigation. I asked each roommate in a calm, non-accusatory way if they had eaten them. After a few days, one roommate admitted to eating them, but it turned out that they had forgotten to buy more when they ran out of their own snacks. The cause of the missing food was not malice, but simply forgetfulness and a lack of communication.</p><p><strong>Impact of Identifying the Wrong Root Cause:</strong><br>In a more professional setting, if the wrong Root Cause is identified, it could lead to serious consequences. For instance, if a company experienced repeated production delays and incorrectly identified equipment malfunction as the root cause when it was actually poor communication between teams, this could lead to unnecessary expenses on repairs, leaving the real issue unaddressed. Similarly, in a food safety context, if a company wrongly attributes a contamination incident to inadequate packaging when the actual cause is improper storage, they could waste resources improving packaging instead of focusing on the right corrective actions, leading to potential future problems.</p><p><strong>Transferable Skills for RCA:</strong><br>For individuals conducting RCA regularly, several transferable skills are essential. Strong <strong>analytical skills</strong> are crucial to gather and assess data accurately. <strong>Critical thinking</strong> helps in evaluating possible causes and considering all angles of a situation. Additionally, <strong>communication skills</strong> are key, both for gathering information from others and for presenting findings clearly. <strong>Attention to detail</strong> is necessary to avoid overlooking small factors that could have a significant impact. Finally, <strong>problem-solving abilities</strong> are important to come up with effective solutions once the root cause is identified.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 05:11:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348553075</guid>
      </item>
      <item>
         <title>Alinah Ira Pahang (301368093)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348600272</link>
         <description><![CDATA[<ol><li><p><strong>Experience with Root Cause Analysis (RCA) Investigation:</strong><br>While working as a Medical Office Administrator at a clinic, I participated in an RCA investigation related to frequent delays in patient appointments. Patients were experiencing long wait times, which led to complaints and operational inefficiencies. My role included gathering data on appointment scheduling, patient check-in times, and physician availability. Through the investigation, we discovered that the main issue was improper scheduling—multiple double bookings were occurring due to miscommunication between administrative staff and the electronic booking system. The corrective actions included updating scheduling protocols, retraining staff on appointment management, and implementing a clearer communication process between front-desk staff and physicians.</p></li><li><p><strong>Impact of Identifying the Wrong Root Cause:</strong></p><ul><li><p><strong>Decreased Patient Satisfaction &amp; Reputation Damage:</strong> If the clinic had mistakenly attributed the delays to patient tardiness rather than internal scheduling issues, they might have enforced stricter late arrival policies instead of addressing the real problem. This could have frustrated patients further, leading to lower satisfaction and potential loss of clientele.</p></li><li><p><strong>Operational Inefficiencies &amp; Staff Burnout:</strong> Misidentifying the root cause could have led to ineffective workflow changes, increasing administrative workload without solving the delays. If staff continued to manage double bookings, it could have resulted in stress, errors, and reduced overall efficiency.</p></li></ul></li><li><p><strong>Most Important Transferable Skills for RCA Investigators:</strong></p><ul><li><p><strong>Problem-Solving &amp; Analytical Thinking:</strong> RCA requires breaking down issues logically to pinpoint the true source of the problem. In a clinic setting, this means analyzing workflow inefficiencies, patient flow, and administrative processes.</p></li><li><p><strong>Attention to Detail:</strong> Small scheduling errors or overlooked policies can cause significant operational issues. Careful examination of processes is crucial for accurate root cause identification.</p></li><li><p><strong>Communication &amp; Teamwork:</strong> RCA in a clinic involves coordinating with medical staff, administrators, and management. Clear communication ensures that all stakeholders understand the findings and collaborate on effective solutions.</p></li><li><p><strong>Adaptability &amp; Process Improvement:</strong> Investigators need to remain open to reassessing initial assumptions and continuously refining procedures to prevent recurrence. In a healthcare environment, flexibility in problem-solving is essential for improving patient care and operational efficiency.</p></li></ul></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 06:07:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348600272</guid>
      </item>
      <item>
         <title>Roshna Benadict (301355281)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348630033</link>
         <description><![CDATA[<p>A while ago, I was involved in a Root Cause Analysis (RCA) investigation for a food manufacturing issue where a batch of products failed to meet quality standards. Initially, it seemed like a simple case of incorrect ingredient measurements, but after digging deeper, we discovered that a calibration issue in the weighing system was actually the root cause. If we had just focused on operator error and retrained staff without fixing the calibration, the issue would have kept recurring, leading to more waste and compliance risks. This experience reinforced how crucial it is to verify findings before implementing solutions.</p><p>If the wrong root cause is identified, it can have serious consequences. One example is increased financial loss—companies might waste money on unnecessary training or equipment replacements without actually solving the real problem. Another example is compliance risks—if a food safety issue isn’t properly addressed, it could lead to regulatory violations or product recalls.</p><p>From this experience, I realized that attention to detail, problem-solving, and collaboration are key skills for RCA investigations. Asking the right questions, analyzing data objectively, and working with different departments to validate findings can make all the difference in preventing future issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 06:39:04 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348630033</guid>
      </item>
      <item>
         <title>Lovejot Kaur (301286670)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3348832285</link>
         <description><![CDATA[<p>A few months ago, while working in a food production setting, I was involved in a Root Cause Analysis (RCA) investigation related to an issue with inconsistent product weights. Some batches of the product were coming out underweight, leading to complaints and the risk of regulatory non-compliance. My supervisor asked me to assist in gathering data and observing the production line to help pinpoint the cause.</p><p>After reviewing the batch records and monitoring the process, we initially suspected that the issue was due to incorrect equipment calibration. However, after further investigation, we discovered that the real cause was a variation in raw material moisture content, which was affecting the final product weight. If we had stuck with the wrong root cause (equipment calibration), we would have wasted time and resources making unnecessary adjustments while the actual issue persisted.</p><p>Misidentifying the root cause in an RCA can have serious consequences for a company. For example, if a food safety issue is wrongly attributed to a minor packaging defect rather than a contamination source, it could lead to repeated recalls and damaged consumer trust. Similarly, in a production setting, focusing on the wrong issue can result in unnecessary downtime, increased costs, and failure to meet regulatory standards.</p><p>Individuals who regularly conduct RCA need strong analytical thinking, attention to detail, and problem-solving skills. Communication is also crucial, as effective collaboration with different departments ensures that all potential factors are considered. Looking back, this experience taught me the importance of not jumping to conclusions and thoroughly investigating all possible causes before implementing corrective actions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 09:38:43 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3348832285</guid>
      </item>
      <item>
         <title>Robert Kowal 301252289</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349081806</link>
         <description><![CDATA[<p>For my Root Cause Analysis (RCA) experience, I remember an incident at work where a mistake was made in a food processing line that led to an incorrect product being sent out. My manager asked me to help investigate the issue. At first, we thought it was a packaging error, but after going through the entire process from production to packing, we realized that the mistake had occurred much earlier in the process during the ingredient measurements. The wrong ingredient was added, which threw off the rest of the production. After we identified this root cause, we implemented a new procedure for ingredient checks to ensure that this didn’t happen again. The outcome was positive; we were able to stop future errors, and we saved the company from a larger quality control issue.</p><p>If the wrong Root Cause had been identified, it could have led to the company continuing to make the same mistake. For example, if we had assumed it was a packaging issue and made no changes to the ingredient measurement process, the same problem could have kept happening, wasting time and resources. Additionally, customer trust could have been affected if the product continued to be incorrect.</p><p>The transferable skills that are most important for people who regularly conduct RCAs are strong problem-solving abilities, attention to detail, and the ability to ask the right questions. It’s important to approach the situation with a curious mindset, thinking through all possibilities and not jumping to conclusions too quickly. Effective communication is also key, as you need to work with different team members to gather information and collaborate on the solution.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 13:30:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349081806</guid>
      </item>
      <item>
         <title>Farhat Christopher (301395565)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349384204</link>
         <description><![CDATA[<p>During my time in the food industry, I participated in a Root Cause Analysis (RCA) investigation when a batch of a new product failed to meet quality standards. The issue involved unexpected texture changes and off-flavors, which were identified during routine quality checks. As part of the investigation, I worked with the quality assurance and production teams to analyze the formulation, ingredient sourcing, and processing conditions. After carefully tracing each step, we discovered that a supplier had modified the particle size of a key ingredient, which altered its functionality in the final product. By addressing this root cause, we adjusted the formulation and implemented stricter ingredient specifications, preventing future occurrences.</p><p>Identifying the wrong root cause in an RCA can have serious consequences. For example, if we had incorrectly blamed storage conditions instead of the ingredient modification, the company might have wasted resources on unnecessary warehouse upgrades while the issue persisted. Another potential outcome of a misdiagnosis is repeated product failures, leading to customer complaints, recalls, or even regulatory actions, ultimately harming the brand’s reputation.</p><p>Conducting RCA requires strong analytical thinking, collaboration, and attention to detail. Investigators must be able to gather and interpret data, communicate effectively with cross-functional teams, and remain objective to avoid jumping to conclusions. These skills are essential to ensuring that corrective actions truly address the problem, improving product quality and overall efficiency.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 16:52:42 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349384204</guid>
      </item>
      <item>
         <title>Karthika Sheeja (301283038)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349788415</link>
         <description><![CDATA[<p>One day, during my time as a QA assistant, we noticed a batch of products failing to meet quality standards. The issue was small cracks forming in the packaging, which could lead to contamination. The first assumption was that the packaging machine was faulty, so maintenance adjusted the settings. However, the problem kept happening. We decided to conduct a full <strong>Root Cause Analysis (RCA)</strong>.</p><p>After reviewing production logs, testing different materials, and speaking with the team, we discovered the real issue. The packaging material was stored in a colder area, making it brittle before use. Once we controlled the storage temperature, the problem stopped. If we had only focused on the machine, we would have wasted time and money on unnecessary repairs while the issue continued.</p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><ol><li><p><strong>Increased Costs</strong> – If a company fixes the wrong issue, it wastes money on repairs, retraining, or new materials that don’t solve the problem.</p></li><li><p><strong>Loss of Customer Trust</strong> – If poor-quality products keep reaching customers, it damages the company’s reputation and could lead to recalls.</p></li></ol><p><strong>Key Transferable Skills for RCA</strong></p><ul><li><p><strong>Critical Thinking</strong> – Asking “why” multiple times to dig deeper into the real cause.</p></li><li><p><strong>Attention to Detail</strong> – Small clues often lead to big discoveries.</p></li><li><p><strong>Collaboration</strong> – Talking to different teams helps uncover hidden factors.</p></li><li><p><strong>Problem-Solving</strong> – Thinking beyond the obvious to find effective solutions.</p></li></ul><p>Every RCA is a learning experience. Finding the real cause prevents future problems and makes the company stronger.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-03 23:58:20 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349788415</guid>
      </item>
      <item>
         <title>Sharanjit (301405174)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349820448</link>
         <description><![CDATA[<p>You may use this script for your Root Cause Analysis (RCA) video: <br><br>--- [Preface] <br>Hi everyone, today I'll talk about my experience participating in a Root Cause Analysis (RCA) investigation, the consequences of choosing the incorrect root cause, and the essential transferable skills required of RCA specialists. <br><br>[1. My Experience with RCA] <br>I have experience addressing quality and safety concerns from my employment and studies in food science and microbiology. In one instance, a food product had an unanticipated microbial infestation. To find the source, our team performed an RCA investigation. </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 00:33:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349820448</guid>
      </item>
      <item>
         <title>Anita Khadka (301348501)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349827795</link>
         <description><![CDATA[<p>When I used to work in a laboratory for cosmetics, I investigated on a batch of facial cream with an odd texture and separation of the constituents. My manager requested me to assist in determining the source of the problem. We began by examining the formulation, constituents, and blending procedure. Upon close observation, we realized that the emulsification was carried out at an incorrect temperature, and hence the final product was unstable. We had realized this later on, and we redesigned the process parameters and had more stringent controls for the monitoring of temperatures, which assured product consistency.<br><strong>If the incorrect root cause were identified, there would have been two issues of severe concern:<br>Product Recall &amp; Cost Loss</strong>: If the problem were because of the ingredients and not the mixing procedure, the company would have likely wasted costly raw materials unnecessarily, bearing heavy expenses and production loss.<br><strong>Customer Complaints &amp; Brand Damage</strong>: If the defective product were placed on sale without quality assurance, customers would have observed the separation and complained, demanded returns, and hurt the business reputation.<br>Performing RCA from time to time demands analytical reasoning, problem-solving, and accuracy. In the laboratory setting, scientific procedure and quality assurance knowledge is required to make sure that each product is safe and performs as required.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 00:41:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349827795</guid>
      </item>
      <item>
         <title>Temilola 301221278</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349867991</link>
         <description><![CDATA[<p>I once participated in a Root Cause Analysis (RCA) investigation to troubleshoot recurring food product contamination. Initially, we suspected that equipment malfunction was causing the issue, but after further investigation, we discovered the contamination was actually happening during the packaging stage. The initial misidentification of the root cause had serious consequences, as it led to wasted time and resources before we pinpointed the true source of the problem. If the wrong root cause had been identified, it could have resulted in unnecessary equipment repairs or overlooking critical issues in the packaging process, allowing the contamination problem to persist.</p><p>From this experience, I realized that critical thinking and communication are key transferable skills for anyone conducting RCAs. Critical thinking allows you to objectively analyze all possibilities, ensuring you don’t overlook any potential causes. Communication is equally important because RCA often involves collaborating with various teams, and clear, open communication ensures everyone’s expertise is considered. This experience reinforced that RCA isn’t just about fixing problems but understanding the broader context and learning from the process.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 01:17:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349867991</guid>
      </item>
      <item>
         <title>Florence Parmar (301395559)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349902869</link>
         <description><![CDATA[<p> I want to share a personal experience with a Root Cause Analysis, or RCA, and talk about the critical impact it can have when done correctly, or incorrectly."</p><p><strong>[Scene 1: My Experience with RCA]</strong></p><p><em>Voiceover or On-Camera:</em><br>"I’ve had the opportunity to participate in an RCA investigation in a previous role. The situation involved a production issue that was causing delays and impacting overall efficiency. The team was tasked with identifying the root cause behind the bottleneck.</p><p>During the investigation, we gathered data, interviewed team members, and performed a series of tests. The main challenge was not jumping to conclusions. At first, we assumed the issue was related to machinery malfunction, but after thorough investigation and data analysis, we discovered that the root cause was actually a miscommunication between two departments which resulted in delayed material shipments. It taught me the importance of a systematic approach to RCA – not just fixing the symptoms but identifying the underlying cause."</p><p><strong>[Scene 2: The Impact of Wrongly Identified Root Causes]</strong></p><p><em>Voiceover or On-Camera:</em><br>"Now, what happens if the wrong root cause is identified during an RCA? The impact can be significant. Let me give you two examples."</p><p><strong>Example 1: Financial Loss</strong><br>"Imagine a company identifies a machine malfunction as the root cause of production delays, but in reality, it’s a supply chain issue. If resources are spent replacing the machinery, the root cause remains unaddressed. This leads to wasted costs, and the real issue will continue to affect operations, ultimately reducing profits."</p><p><strong>Example 2: Employee Morale</strong><br>"Another consequence could be on employee morale. If a company blames employees for inefficiencies when, in fact, the problem lies with outdated processes, it can create frustration and a lack of trust. Employees will feel unfairly blamed, leading to disengagement and possibly higher turnover."</p><p><strong>[Scene 3: Transferable Skills for RCA]</strong></p><p><em>Voiceover or On-Camera:</em><br>"Conducting a successful RCA requires a mix of technical and interpersonal skills. Here are three transferable skills that I believe are crucial."</p><p><strong>1. Analytical Thinking:</strong><br>"Being able to break down complex problems into smaller, manageable pieces is essential. This involves collecting data, analyzing it, and using critical thinking to avoid jumping to conclusions."</p><p><strong>2. Communication:</strong><br>"Clear communication with everyone involved in the process is vital. You need to ask the right questions, actively listen, and ensure that all relevant parties are on the same page."</p><p><strong>3. Problem-Solving Mindset:</strong><br>"RCA isn't just about identifying what went wrong – it's about fixing it. The mindset needs to be solution-oriented, ensuring that once the root cause is identified, corrective actions are both effective and sustainable."</p><p><strong>[Closing Scene: Wrapping Up]</strong></p><p><em>Voiceover or On-Camera:</em><br>"In conclusion, RCA is a powerful tool for problem-solving, but it requires careful analysis, clear communication, and critical thinking. Identifying the wrong root cause can have far-reaching consequences, so it's crucial to approach it methodically. I hope you found these insights helpful, and if you’re involved in RCAs, remember that the right skills and approach can make all the difference."</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 01:45:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349902869</guid>
      </item>
      <item>
         <title>Neha Koshy (301437399)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349929939</link>
         <description><![CDATA[<p>A few months ago, our take-out shop started receiving frequent customer complaints about incorrect orders. At first, we assumed it was just a busy weekend mix-up, but when the mistakes continued, my manager decided to investigate. Since I work at the front counter, I was involved in figuring out what was going wrong.</p><p>Initially, we thought the issue was with the kitchen staff misreading order tickets, so we focused on reminding them to double-check orders. However, the mistakes kept happening. After taking a closer look at the process, we discovered the real problem—the new receipt printer was slightly misaligned, cutting off parts of the order details. Since we had identified the wrong root cause at first, we wasted time on unnecessary solutions instead of addressing the actual issue right away.</p><p>Misidentifying a root cause can significantly impact a business. First, it can lead to financial losses—if we had continued blaming the kitchen staff, we might have retrained or even replaced employees unnecessarily, without solving the real problem. Second, it can damage customer trust. People were already frustrated with incorrect orders, and if the mistakes had continued, they might have stopped ordering from us altogether.</p><p>This experience showed me how important certain skills are in root cause analysis. Attention to detail is crucial—if we hadn’t closely examined the receipts, we wouldn’t have noticed the misalignment. Problem-solving and critical thinking are also essential because they help in questioning initial assumptions and digging deeper to find the actual cause. Lastly, communication plays a key role. Since I interact with customers directly, sharing their feedback helped the team see the problem from different perspectives.</p><p>Looking back, this was a valuable lesson in the importance of identifying the real cause of a problem before implementing solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:08:10 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349929939</guid>
      </item>
      <item>
         <title>Anna Antony-301429306</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349951421</link>
         <description><![CDATA[<p>In my cookie shop, we once got a complaint that the cookies were too raw and tasted bad. To figure out what went wrong, we looked at everything, from the ingredients to the baking process. After checking everything, we found that the problem was with the oven it wasn’t set to the right temperature, so the cookies weren’t baking evenly. Once we fixed the oven, the cookies turned out perfect.<br>If we had figured out the wrong cause, it could have led to more problems. For example, if we thought the dough was the problem, we might have changed the ingredients, wasting time and money. Another issue could be that if we didn’t fix the oven, the problem would have kept happening, leading to more complaints and harming our reputation.<br>When doing RCA regularly, there are a few important skills needed. First, problem-solving is important to figure out the real cause of the issue. Communication is key to share your findings with the team. Paying attention to small details, like oven settings, is also important. And finally, teamwork is crucial because solving the problem often needs help from different people, like bakers or equipment experts.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:23:30 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349951421</guid>
      </item>
      <item>
         <title>Elizabeth Thomas (301403915)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349965493</link>
         <description><![CDATA[<p><br/></p><p>There was a time at work when we kept having issues with the cash register not balancing at the end of shifts. At first, we thought it was just small mistakes or carelessness, but it kept happening. I decided to look more closely at what was going on. After observing the shift changes, I realized the issue was that there was no clear system for handing over responsibilities. When employees switched shifts, there was confusion about who was responsible for what, which led to the discrepancies.</p><p>Once we identified that, we created a clear handover process, where each employee knew exactly what needed to be done during the transition. After implementing that change, the register issues stopped. I learned that it’s important to really dig into a problem to understand what’s causing it, rather than just assuming it’s something simple. If we had just assumed people were making mistakes, the issue would have kept happening.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:34:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349965493</guid>
      </item>
      <item>
         <title>Navjot Kaur (301398471)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349988019</link>
         <description><![CDATA[<p>A time when I participated in a Root Cause Analysis was during my internship at a food manufacturing facility. There was an issue with a batch of product that failed quality checks, and I was part of the team investigating the cause. We went through several steps, starting by reviewing the production process, checking for any equipment malfunctions, and interviewing the staff involved. It turned out that a minor adjustment to one of the machines was overlooked, which led to inconsistent temperatures during processing, affecting the product quality. The RCA helped identify the specific issue, and we were able to correct the settings and prevent future issues.</p><p>If the wrong root cause had been identified in this case, it could have led to wasted resources and additional problems. For example, if the team had focused on the raw materials rather than the equipment malfunction, they might have discarded good ingredients unnecessarily and delayed the production process. Another outcome could have been a failure to address the real issue, leading to a repeat of the problem in future batches.</p><p>When conducting RCA regularly, transferable skills such as attention to detail, problem-solving, and communication are critical. Attention to detail helps ensure that nothing is overlooked during the investigation. Problem-solving skills are needed to analyze the data and determine the most likely root cause, while communication skills are necessary for collaborating with different teams and conveying findings clearly. These skills are essential for anyone responsible for conducting thorough investigations and making data-driven decisions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:52:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349988019</guid>
      </item>
      <item>
         <title>Dolly 301404357</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349989265</link>
         <description><![CDATA[<p>I participated in an RCA when microbial contamination was found in a food production batch. Using the 5 Whys and Fishbone Diagram, we identified improper cleaning of a mixing tank as the root cause. The sanitation procedure was updated, and staff received additional training.</p><p>2. Impact of Wrong Root Cause:</p><ul><li><p>Recurring Issues: If the real problem isn’t addressed, defects or contamination will continue, leading to recalls.</p></li><li><p>Wasted Resources: Unnecessary corrective actions, like replacing suppliers, increase costs without solving the actual issue.</p><p><br/></p><p><br/></p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:53:16 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349989265</guid>
      </item>
      <item>
         <title>Quennie Besa (301367539)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3349996093</link>
         <description><![CDATA[<p>In my previous job, our team was responsible for analyzing proficiency samples to evaluate our ability to enumerate, isolate, and characterize microorganisms. We meticulously followed all necessary protocols and precautions to ensure accurate results. However, when the proficiency test results were released, we did not achieve a perfect 100% score. Acknowledging the issue, we took full responsibility and conducted a root cause analysis. Through careful backtracking and investigation, we discovered that one of the proficiency samples had been contaminated during transport. This experience reinforced the critical importance of maintaining strict controls and ensuring sample integrity to prevent testing errors.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 02:58:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3349996093</guid>
      </item>
      <item>
         <title>Quennie Besa</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350021621</link>
         <description><![CDATA[<ol><li><p>In my previous job, our team was responsible for analyzing proficiency samples to evaluate our ability to enumerate, isolate, and characterize microorganisms. We meticulously followed all necessary protocols and precautions to ensure accurate results. However, when the proficiency test results were released, we did not achieve a perfect 100% score. Acknowledging the issue, we took full responsibility and conducted a root cause analysis. Through careful backtracking and investigation, we discovered that one of the proficiency samples had been contaminated during transport. This experience reinforced the critical importance of maintaining strict controls and ensuring sample integrity to prevent testing errors. As a result, we implemented more stringent protocols to mitigate similar risks in the future.</p></li></ol><p>&nbsp;</p><ol start="2"><li><p>Identifying the wrong root cause can hurt a company in several ways.</p><p>a. Ineffective Solutions<strong> –</strong> if the wrong cause is identified, the company may apply fixes that don't solve the real problem. For example, in the case of the proficiency test, the company might spend money on more sophisticated instruments or materials, when the real problem lies in the way the samples are being transported.</p><p>b. Recurring Problems – incorrectly identifying the cause can lead to the same problem happening again. For instance, in the case of the proficiency test, if the issue is not correctly traced to sample contamination during transport, the company may continue to face similar problems in future tests.</p></li><li><p>The key transferable skills for those who conduct RCAs regularly are:</p><p>a. Critical Thinking- analyzing situations to find the real cause of a problem.</p><p>b. Problem-Solving- finding solutions that address the root cause and prevent future issues.</p><p>c. Attention to Detail- carefully reviewing data and processes to avoid missing important information.</p><p>d. Communication- explaining findings and solutions clearly to others.</p><p>e. Collaboration- working with teams to gather information and solve problems together.</p></li></ol><p>&nbsp;</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 03:17:40 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350021621</guid>
      </item>
      <item>
         <title>Ajay Kumar Javvadi-301375317</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350031714</link>
         <description><![CDATA[<p>At work, I encountered a situation where an error in the food processing line resulted in the wrong product being sent out. My manager asked me to assist in investigating the issue. Initially, we suspected a packaging mistake, but after thoroughly reviewing the entire process—from production to packaging—we discovered that the error had actually occurred much earlier during the ingredient measurement stage. An incorrect ingredient had been added, disrupting the rest of production. Once we identified the true root cause, we introduced a new ingredient-checking procedure to prevent similar mistakes in the future. This proactive approach successfully reduced errors and helped the company avoid a major quality control issue.</p><p>If the wrong root cause had been identified, the company might have continued making the same mistake. For instance, if we had assumed it was only a packaging issue and failed to address the ingredient measurement process, the error could have persisted, leading to wasted time, resources, and potential damage to customer trust.</p><p>Conducting effective Root Cause Analyses (RCAs) requires key transferable skills, including strong problem-solving abilities, attention to detail, and the ability to ask the right questions. It’s essential to approach investigations with a critical and open mindset, considering all possible factors before drawing conclusions. Additionally, effective communication is crucial, as collaboration with different team members is necessary to gather information and implement corrective actions successfully.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 03:25:01 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350031714</guid>
      </item>
      <item>
         <title>parth jatiya (301293190)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350032449</link>
         <description><![CDATA[<p>last semester, during our project in food science  there was a minor problem in one of our experiment. it was a antibiotic test use well on the agar. however, due to some problem there was visible growth instead of bacterial zone even for the know anti biotic. </p><p>at that time we tried to applied RCA indirectly, to the experiment to find out the root of the problem. at first we thought that there is some problem with the antibiotic strip that we used. but upon testing it again on other media it showed result. upon further investigation, it turns out to be problem with the agar thinness.</p><p><br/></p><p>if we didn't do proper RCA and blamed the antibiotic strip our entire result would be misleading and would give false positive results. that would have affected out entire project in the end.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 03:25:39 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350032449</guid>
      </item>
      <item>
         <title>Sufail Santhipurath 301428330</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350069645</link>
         <description><![CDATA[<p>During my internship at Milma dairy plant, I got the chance to be part of a Root Cause Analysis (RCA) investigation when a production line started facing frequent equipment breakdowns. It was a bit overwhelming at first, but the team worked together to dig into the issue. We looked at everything—interviewing operators, checking maintenance records, and even reviewing how the machines were being used. After some digging, we discovered that the real issue was poor maintenance of a crucial piece of equipment. By pinpointing that, we were able to set up a more rigorous maintenance schedule and avoid further breakdowns, which felt like a big win.</p><p>On the flip side, I also saw how a wrong root cause could have a huge impact. There was another incident where we thought spoilage was caused by an issue with refrigeration. But as we kept investigating, we found out the problem was actually with how the raw materials were being handled before refrigeration. If we’d just fixed the cooling system, the issue would’ve continued, and the company would have wasted resources while customers suffered from spoiled products. It made me realize how crucial it is to find the real root cause, or else you end up solving the wrong problem, which only adds to the headache.</p><p>Looking back, I see how important it is for RCA investigators to have certain skills. Analytical thinking is key to connecting the dots and understanding the data. Communication skills are just as important to make sure everyone is on the same page, especially when working with different teams. And problem-solving is at the heart of finding solutions that actually stick. These are the skills that helped me contribute to the investigation, and I can see how they would be essential in any situation where you need to solve complex problems.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 03:56:22 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350069645</guid>
      </item>
      <item>
         <title>SAI KIRAN </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350073614</link>
         <description><![CDATA[<p>During my time in <strong>food science and microbiology</strong>, I participated in a Root Cause Analysis (RCA) investigation to address a recurring issue with <strong>product contamination in a beverage manufacturing process</strong>. Using tools like the <em>5 Whys</em> and <em>Fishbone Diagram</em>, we identified the root cause as <strong>improper sanitation of equipment during production</strong> and implemented corrective actions, such as <strong>revising cleaning protocols and training staff on proper hygiene practices</strong>. This resolved the issue and improved <strong>product safety and quality</strong>. However, identifying the wrong root cause can have serious consequences, such as wasted resources or damaged customer trust. For example, if contamination is misdiagnosed as a raw material issue instead of equipment sanitation, the problem persists, leading to financial losses and reputational harm. Conducting effective RCAs requires key transferable skills like analytical thinking, attention to detail, communication, problem-solving, and objectivity, which are essential for uncovering the true cause and implementing lasting solutions."</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:00:23 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350073614</guid>
      </item>
      <item>
         <title>Pragatiben Patel: 301379444</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350078922</link>
         <description><![CDATA[<p>During my time in a food production facility, I participated in a <strong>Root Cause Analysis (RCA)</strong> when we encountered an issue with improperly sealed product packaging. Initially, the sealing machine was suspected to be the problem, but after investigating various factors, we discovered that the actual cause was a change in <strong>packaging film thickness</strong> by the supplier. Identifying the wrong root cause in an investigation can have serious consequences. For example, <strong>wasted resources and increased costs</strong> can result if a company spends money on unnecessary repairs while the real issue persists. Additionally, <strong>damage to brand reputation</strong> can occur if defective products reach customers, leading to recalls or loss of consumer trust. To conduct an effective RCA, certain <strong>transferable skills</strong> are essential, including <strong>critical thinking, attention to detail, effective communication, and data analysis.</strong> These skills help ensure that problems are thoroughly analyzed and properly addressed, preventing future issues and improving efficiency. My experience taught me that a structured and accurate RCA is crucial for long-term success in any workplace.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:05:43 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350078922</guid>
      </item>
      <item>
         <title>Camilo Vanegas (301299033)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350079806</link>
         <description><![CDATA[<p>During a lab project, our microbial test results were inconsistent. Initially, we suspected contamination, but after conducting an RCA, we discovered the issue was due to improper dilution techniques and an incorrect agar medium. Fixing these errors led to reliable results, reinforcing the importance of structured problem-solving.</p><p>Misidentifying the root cause can lead to serious consequences. One example is wasted resources, where a company might invest in unnecessary sanitation efforts instead of addressing a contaminated ingredient. Another impact is regulatory issues, where incorrectly blaming equipment failure instead of poor employee training could lead to audit failures, product recalls, and loss of customer trust.</p><p>Individuals conducting RCA need a combination of technical and soft skills. Critical thinking and attention to detail help in identifying true causes and ruling out false ones. Communication and collaboration are crucial for gathering insights and ensuring corrective actions are implemented effectively. Additionally, problem-solving and adaptability allow investigators to use structured methods, such as the 5 Whys, to avoid assumptions and reach accurate conclusions.</p><p>Conducting an effective RCA prevents recurring issues, saves costs, and improves overall efficiency in any industry.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:06:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350079806</guid>
      </item>
      <item>
         <title>Aastha Patel</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350091996</link>
         <description><![CDATA[<p>was once involved in a Root Cause Analysis (RCA) investigation at a company where we were trying to identify why a certain process failure was happening repeatedly. The issue was related to a product defect, which was affecting the production timeline and increasing costs. Initially, our team thought the issue was due to a specific part in the machinery, so we focused on troubleshooting and replacing the part. However, after further investigation and digging deeper into the process, it turned out that the real root cause was improper training for the operators using the equipment, which caused errors in setup and operation. The root cause wasn't the machinery itself, but the lack of understanding in how to use it efficiently.</p><p>When the wrong root cause is identified, the impact on the company can be significant. For example, if the wrong cause had been addressed in this situation—say, replacing machinery unnecessarily—it would have resulted in wasted time and resources. The operators would have continued to make mistakes, leading to more defects. Another potential outcome is that the real issue wouldn’t have been fixed, and the same problems could have resurfaced, ultimately leading to customer dissatisfaction and financial losses.</p><p>In terms of transferable skills, I think strong analytical skills are crucial for anyone conducting RCA regularly. You need to be able to sift through large amounts of data, separate the noise from the important signals, and identify patterns. Communication is another key skill because you often need to collaborate with different departments or teams to get the full picture and ensure everyone is on the same page. Being persistent and open-minded is also important, as the first answer might not always be the right one, and you have to dig deeper to truly understand the issue.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:18:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350091996</guid>
      </item>
      <item>
         <title>Muskan Madaan (301349143)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350092734</link>
         <description><![CDATA[<p>Hi everyone! I want to share my experience with Root Cause Analysis (RCA) during my BSc in Microbiology. In our lab, we once got inconsistent bacterial growth results on agar plates. To find the root cause, we performed an RCA using the <strong>5 Whys</strong> method. We traced the issue back to improper sterilization of inoculating loops, which was due to incorrect autoclave settings. After correcting the settings, the issue was resolved.</p><p>Identifying the wrong root cause can have serious consequences. <strong>First</strong>, if we had blamed contaminated media instead of sterilization, the problem would have continued, leading to inaccurate research. <strong>Second</strong>, in industries like pharmaceuticals, misidentifying causes can lead to unsafe drugs, affecting public health.</p><p>Key transferable skills for RCA include <strong>critical thinking, attention to detail, and problem-solving.</strong> Communication is also crucial to ensure corrective actions are understood. RCA helps prevent errors and improve lab practices.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:19:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350092734</guid>
      </item>
      <item>
         <title>SHRUSHTI BAROT 301403910</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350093579</link>
         <description><![CDATA[<p>I once participated in a Root Cause Analysis (RCA) investigation involving a recurring issue in a production process. Initially, the team suspected that the problem stemmed from equipment failure, but through thorough analysis using the <strong>5 Whys method</strong> and <strong>Fishbone Diagram</strong>, we discovered that the actual root cause was a procedural gap in employee training. Addressing this issue with enhanced training programs significantly reduced the recurrence of errors. Identifying the wrong root cause can have serious consequences; for instance, a company may waste resources fixing the wrong problem, such as replacing machinery when the real issue is operational errors, leading to unnecessary costs. Additionally, misidentifying the root cause can create compliance and reputation risks, especially in industries like healthcare or manufacturing, where unresolved issues can lead to safety violations or regulatory fines. The most important transferable skills for conducting effective RCA include <strong>critical thinking</strong> to analyze data objectively, <strong>attention to detail</strong> to recognize overlooked variables, and <strong>strong communication</strong> to collaborate with cross-functional teams and document findings accurately. Proper RCA ensures long-term process improvements and prevents costly mistakes.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:20:47 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350093579</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350101957</link>
         <description><![CDATA[<p>likhitha morapakula-301432704</p><p>During a lab project, we encountered inconsistent microbial test results. Initially, we thought contamination was the cause, but after performing a root cause analysis (RCA), we identified improper dilution techniques and the wrong agar medium as the issues. Correcting these errors led to reliable results, highlighting the importance of structured problem-solving.</p><p>Incorrectly identifying the root cause can have serious repercussions. For instance, a company might waste resources on unnecessary sanitation efforts rather than addressing a contaminated ingredient. Additionally, misattributing the problem to equipment failure instead of inadequate employee training can lead to audit failures, product recalls, and a loss of consumer trust.</p><p>RCA requires both technical and soft skills. Critical thinking and attention to detail help pinpoint true causes, while communication and collaboration ensure that corrective actions are properly implemented. Problem-solving and adaptability are essential for applying structured approaches, like the 5 Whys, to avoid assumptions and reach accurate conclusions.</p><p>Effective RCA helps prevent recurring issues, reduces costs, and enhances overall efficiency in any industry.</p><p>4o mini</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:29:19 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350101957</guid>
      </item>
      <item>
         <title>Vaibhavi Brahmbhatt - 301403898</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350122134</link>
         <description><![CDATA[<p>During my role as a Milk Prep Room Aide at SickKids, I participated in a Root Cause Analysis (RCA) investigation to address a labeling discrepancy in prepared milk. A prepared bottle did not match the required patient specifications, prompting an internal review. The investigation team, including milk prep staff, quality control, and nursing representatives, used the 5 Whys method to identify potential causes such as procedural errors, workflow issues, or miscommunication. After reviewing preparation logs and observing the workflow, we found that the issue stemmed from misinterpretation of handwritten feeding orders, leading to incorrect fortification of milk.</p><p><br/></p><p>If the wrong root cause had been identified, it could have led to serious consequences. For example, attributing the issue to equipment failure instead of a miscommunication problem would have meant the real issue persisted, potentially putting patient safety at risk. Additionally, misdirected corrective actions—such as replacing a functioning system rather than improving communication protocols—would have resulted in unnecessary costs and delays. To prevent recurrence, we implemented electronic feeding orders, added verification steps in labeling, and conducted staff training to ensure accuracy in interpreting orders.</p><p><br/></p><p>This experience highlighted the importance of attention to detail, critical thinking, and teamwork in RCA investigations. Individuals conducting RCA regularly must be able to analyze data, collaborate across departments, and implement effective corrective actions. In a healthcare setting like SickKids, ensuring accurate root cause identification is essential for patient safety and operational efficiency.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:48:25 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350122134</guid>
      </item>
      <item>
         <title>Christadi Edvina Vinoth (301378681)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350127963</link>
         <description><![CDATA[<p>One time, at a previous job, our team noticed a recurring issue where customer orders were getting delayed, leading to complaints. My manager asked me to help investigate why this was happening. At first, some people assumed the issue was with the kitchen being too slow, but after observing the workflow and talking to staff, I realized that the real problem was incorrect order entry at the cash register. Some orders were not printing properly in the kitchen due to a system glitch. Once we identified this, we reported it to IT, and after fixing the software issue, the delays significantly decreased.</p><p>If the wrong root cause had been identified—blaming the kitchen instead of the ordering system—this could have led to unfair criticism of staff and possibly unnecessary changes in kitchen operations. Another possible outcome of a misidentified RCA could be wasted resources, where time and money are spent fixing the wrong problem while the real issue continues to cause disruptions.</p><p>For effective RCA, I think strong <strong>analytical skills, attention to detail, and communication</strong> are essential. Being able to ask the right questions, observe patterns, and work with different teams helps ensure that the correct root cause is found, leading to meaningful solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 04:53:10 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350127963</guid>
      </item>
      <item>
         <title>aayushi bhomia 301275661</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3350161930</link>
         <description><![CDATA[<p>During my microbiology project, I conducted a Root Cause Analysis (RCA) when unexpected microbial growth patterns appeared in my experiment. Initially, I suspected lab contamination, but after thorough investigation, I found that inconsistent sterilization of equipment was the real issue. Correcting this ensured accurate results. Identifying the wrong root cause in an investigation can have serious consequences; for example, in food production, misdiagnosing a contamination source can lead to foodborne illness risks and recalls, while in manufacturing, wrongly attributing a machine failure to operator error instead of a mechanical defect can cause repeated breakdowns and financial losses. Key transferable skills for effective RCA include analytical thinking to identify true root causes, attention to detail to catch overlooked factors, and strong communication to document findings and collaborate on corrective actions. Conducting RCA correctly prevents recurring issues, enhances efficiency, and improves overall safety.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 05:22:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3350161930</guid>
      </item>
      <item>
         <title>Vandana (301349195)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3351253074</link>
         <description><![CDATA[<p>Root Cause Analysis (RCA) is essential for identifying underlying issues rather than just addressing symptoms. During my MSc in Zoology, I investigated a sudden decline in fish survival rates. Using the "5 Whys" method, we traced the issue to fluctuating oxygen levels caused by an undetected clog in the aeration system due to irregular maintenance. Implementing routine checks resolved the problem and prevented further losses. Misidentifying root causes can lead to wasted resources and compromised research outcomes. Effective RCA requires critical thinking, attention to detail, communication, and problem-solving—key skills for scientific research and real-world applications</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-04 19:38:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3351253074</guid>
      </item>
      <item>
         <title>Damanpreet Kaur(301379455)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3351545847</link>
         <description><![CDATA[<p>One time at my job as a QA Manager in a dairy facility, I was asked to investigate why some batches of yogurt had excessive whey separation, making the texture unstable. Using Root Cause Analysis (RCA), I reviewed production data, ingredient logs, and equipment records, applying the “5 Whys” method to trace the issue. I discovered that the pasteurization heat exchanger had temperature fluctuations, which weakened the bacterial cultures and led to inconsistent fermentation. If we had wrongly blamed the bacterial cultures, we would have wasted time and money replacing them without fixing the real issue. Worse, if the problem continued, customers might have lost trust in the brand. This experience showed me the importance of critical thinking, attention to detail, communication, and data analysis—essential skills for effective RCA.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-05 00:53:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3351545847</guid>
      </item>
      <item>
         <title>Smit Patel (301382797)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3351793279</link>
         <description><![CDATA[<p>A while ago, I was working with Tea manufacturing company back in my country as QA/QC Executive and I took part in an RCA inquiry after we discovered variations in the flavor and scent of tea. We identified the problem as differences in drying temperatures rather than the suspected raw material quality using techniques like the Fishbone Diagram and the 5 Whys. An adjustment to the drying procedure fixed the issue.<br><br>Finding the incorrect root cause might be expensive. First, if suppliers were mistakenly held responsible for the problem, we might have changed providers needlessly, which would have disrupted supply chains. Secondly, incorrectly diagnosing machine defects may result in costly equipment replacements while the true problem persists.<br><br>RCA experts need to be able to think critically in order to analyze problems, pay close attention to details in order to identify minor elements, and communicate well in order to work as a team. Good problem-solving abilities guarantee long-lasting gains.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-05 03:24:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3351793279</guid>
      </item>
      <item>
         <title>ANJALI ANNA JOE ( 301396245)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3351843576</link>
         <description><![CDATA[<p>While working at Walmart as an OMNI Customer Fulfillment Associate, I was part of a Root Cause Analysis (RCA) to fix an issue where customer orders were delayed due to out-of-stock items, even though our system showed the products were available. At first, we thought the problem was caused by a software glitch in the inventory system. But after looking closely at the data and working with the team, we found that the real issue was with the way we were updating stock during busy hours.</p><p>If we had figured out the wrong cause, we would have wasted time and money trying to fix the wrong thing. The replenishment process would have continued to cause stock issues, leading to more delays and unhappy customers. This could have hurt Walmart’s sales and reputation if customers kept canceling orders or having problems.</p><p>From this experience, I learned that solving these issues requires paying attention to details, working well with others, and being able to think quickly. It’s important to understand the data and communicate clearly to find the right solution, especially in a busy work environment like Walmart.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-05 04:08:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3351843576</guid>
      </item>
      <item>
         <title>Nistha Gandhi (301298887)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3353094965</link>
         <description><![CDATA[<p>As a Quality Systems Technician at a manufacturing plant, I was responsible for ensuring that all products met the required quality standards. One day, we noticed that a batch of products did not meet the desired specifications and had to be discarded. I was assigned to participate in a Root Cause Analysis (RCA) to determine the underlying cause of the issue.</p><p>We started by gathering data from the production line, examining machine logs, and reviewing the product specifications. After a detailed investigation, we identified that the problem stemmed from a malfunction in one of the machines used to assemble the products. The machine had been calibrated incorrectly, which led to deviations in the final product.</p><p>By addressing the calibration issue and implementing more stringent machine checks, we were able to prevent future defects. This experience helped improve the overall quality control process and reinforced the importance of regular equipment maintenance and checks.</p><p>Identifying the wrong root cause can lead to wasted resources, such as addressing the wrong issue, like retraining employees instead of fixing faulty equipment. It can also cause ongoing problems and customer dissatisfaction if the real issue, like a product defect, isn’t resolved. Key skills for conducting effective RCAs include critical thinking to analyze data, attention to detail, communication for collaborating with teams, and problem-solving to implement lasting solutions. These skills ensure that RCAs are accurate and lead to effective resolutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-05 21:26:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3353094965</guid>
      </item>
      <item>
         <title>Padlet by Komal(301348170)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3356252901</link>
         <description><![CDATA[<p><strong>Root Cause Analysis at Harvey’s</strong></p><p>While working at Harvey’s, once we had repeated customer complaints about undercooked burgers. The management gathered a small team, including myself as a shift supervisor, the kitchen lead, to investigate the root cause. At first, we thought it was due to employees rushing orders. However, after a deeper investigation, we found the real issue: a faulty thermostat on the grill, which wasn’t reaching the right temperature. Once fixed, the problem was resolved.</p><p><strong>Impact of Incorrect Root Cause</strong></p><p>If we had misidentified the cause, it could have led to:</p><ol><li><p><strong>Unfairly Blaming Employees</strong> – This would have hurt morale and caused unnecessary retraining.</p></li><li><p><strong>Ongoing Food Safety Risks</strong> – The issue would have continued, potentially causing health issues and damaging the restaurant’s reputation.</p></li></ol><p><strong>Skills for Effective RCA</strong></p><p>Key skills for conducting RCA include:</p><ul><li><p><strong>Attention to Detail</strong> – Identifying small issues like uneven heating.</p></li><li><p><strong>Critical Thinking</strong> – Digging deeper to find the true cause.</p></li><li><p><strong>Teamwork</strong> – Collaborating with different departments to fix the problem.</p></li><li><p><strong>Problem-Solving</strong> – Addressing the issue and preventing it from happening again.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-07 17:42:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3356252901</guid>
      </item>
      <item>
         <title>Ana Vargas (301270481)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3357030829</link>
         <description><![CDATA[<p><strong>RCA experience:</strong></p><p>In my independent research project to develop clove oil-encapsulated nanoparticles for oral pathogen treatment, the initial formulation failed to show expected antimicrobial activity. To start the investigation, I first confirmed that pure clove oil had the antimicrobial properties expected, which ruled out the oil as the problem.</p><p>Next, I reviewed the formulation and realized that the concentration of clove oil in the nanoparticle solution was too low. After the problem was found, I reformulated the solution, retested it, and then the nanoparticles showed the expected antimicrobial activity.</p><p><br/></p><p><strong>Wrong Root Cause impact:</strong></p><p>For example, if a pharmaceutical company mistakenly blames a formulation problem when the real issue is poor quality control during production, they could keep making faulty drugs, leading to harm, recalls, and legal issues.</p><p>If a food company wrongly blames a supplier for contamination but the real cause is poor hygiene in the factory, they might continue the problem by not fixing the actual issue, leading to more recalls and a damaged reputation.</p><p><br/></p><p><strong>Important transferable skills for RCA:</strong></p><ul><li><p>Problem-solving skills</p></li><li><p>Communication skills </p></li><li><p>Attention to detail</p></li></ul><p><br/></p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-08 23:05:42 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3357030829</guid>
      </item>
      <item>
         <title>Xiaofei Wang (301366322)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3357139024</link>
         <description><![CDATA[<p>During my time working in a laboratory setting, I was involved in a <strong>Root Cause Analysis (RCA)</strong> investigation after a series of unexpected equipment failures affected experimental results. The issue initially appeared to be related to a faulty reagent, leading the team to halt testing and request a new batch. However, after a more thorough investigation, we discovered that the actual root cause was a calibration error in the equipment, which had caused inconsistent readings rather than reagent contamination. If we had stopped at the initial assumption, we would have wasted valuable resources replacing perfectly functional reagents while the problem persisted. Instead, recalibrating the equipment resolved the issue, allowing experiments to continue smoothly.</p><p>Identifying the wrong root cause in an RCA can have significant consequences for a company. For example, in a manufacturing setting, if a company misidentifies a defective material as the root cause of a product failure instead of a design flaw,<strong> </strong>they may continue to produce faulty products, leading to recalls and financial losses. Similarly, in healthcare or pharmaceuticals, if an RCA incorrectly attributes contamination to one step in the process when it is actually occurring at another stage, it could result in continued quality issues, regulatory non-compliance, and potential harm to consumers. These examples highlight the importance of conducting a thorough and unbiased RCA to ensure corrective actions truly resolve the underlying issue.</p><p>4o</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-09 05:13:38 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3357139024</guid>
      </item>
      <item>
         <title>Alisha Dodhiya (301347397)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3357489192</link>
         <description><![CDATA[<p>While working in a laboratory setting, we encountered an issue where bacterial culture plates were showing inconsistent growth patterns. Some plates had significantly reduced colony formation, while others had excessive contamination. Initially, the assumption was that the agar media had been improperly prepared or contaminated during storage. However, we conducted a <strong>Root Cause Analysis (RCA)</strong> to investigate the true source of the problem.</p><p>Using tools like <strong>the 5 Whys and Process Mapping</strong>, we traced the issue back to the autoclave sterilization cycle. We discovered that an intermittent pressure fluctuation during sterilization was causing incomplete decontamination of materials. Some batches of media were not being fully sterilized, leading to contamination, while others were exposed to excessive heat, altering the nutrient composition and affecting bacterial growth.</p><p>To resolve this, we recalibrated the autoclave, introduced a monitoring system for pressure consistency, and added a validation step before use. These corrective actions helped restore consistency in our results and prevented future occurrences.</p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><p>If we had misidentified the root cause, the consequences could have been severe:</p><ol><li><p><strong>Wasted Time and Resources</strong> – If we had focused on changing the media supplier instead of fixing the sterilization process, we would have incurred unnecessary costs and delays without actually solving the issue.</p></li><li><p><strong>Compromised Research and Product Quality</strong> – Incorrect results due to inconsistent bacterial growth could have led to unreliable data, affecting experiments and product testing outcomes.</p></li></ol><p><strong>Key Transferable Skills for RCA</strong></p><ol><li><p><strong>Analytical Thinking</strong> – To break down complex problems and identify hidden variables.</p></li><li><p><strong>Technical Knowledge</strong> – To understand processes and evaluate equipment functionality.</p></li><li><p><strong>Collaboration</strong> – To gather insights from different team members and verify findings.</p></li><li><p><strong>Adaptability</strong> – To reassess conclusions and pivot when new data emerges.</p></li></ol><p>This experience reinforced the importance of a <strong>methodical approach to problem-solving</strong> and highlighted how RCA plays a critical role in preventing ongoing issues in any work environment.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-09 16:28:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3357489192</guid>
      </item>
      <item>
         <title>RCA Experience</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3358688805</link>
         <description><![CDATA[<p><strong>Verlaine Ascencion Nervi Verueco 301344267</strong></p><p><br/></p><p>In my previous role as a medical technologist proficient in HIV, I have been involved in several Root Cause Analysis (RCA) investigations during my tenure. While maintaining confidentiality, I will answer the questions based on general experiences within my role.</p><p><br/></p><p><strong>Experience with a Root Cause Analysis Investigation:</strong></p><p>In one instance, we identified a deviation in a laboratory process, specifically related to a false-positive result in HIV testing. The RCA was initiated to determine the underlying cause. The investigation involved a thorough review of the laboratory procedures, from sample collection to result reporting. We examined potential issues such as improper sample handling, reagent quality, and operator error. During the investigation, it was discovered that a subtle yet significant error occurred in the storage of one batch of reagents, which led to faulty test results. This was not immediately obvious because the reagents seemed to function properly in most cases. After identifying this root cause, we implemented corrective actions such as improving storage conditions and performing more rigorous quality checks. The RCA helped prevent further similar errors and enhanced the overall accuracy of our HIV testing process.</p><p><br/></p><p><strong>Impact of Wrong Root Cause Identification:</strong></p><p>When the wrong root cause is identified in an RCA, it can have serious consequences for a company or organization. Here are two potential outcomes:</p><ul><li><p><strong>Ineffective Corrective Actions:</strong> If the wrong root cause is identified, the corrective actions implemented will not effectively address the underlying issue. For example, if a laboratory investigation incorrectly concludes that operator error caused an issue with HIV testing when the actual cause is reagent degradation, the corrective actions (such as retraining staff) would not prevent future errors. This could lead to recurring issues and loss of credibility with patients and regulatory bodies.</p></li><li><p><strong>Financial and Reputational Damage:</strong> Identifying the wrong root cause can lead to unnecessary costs and further operational inefficiencies. For example, a company might invest in upgrading machinery or tools when the actual cause was related to human error or process flaws. This not only wastes company resources but can also damage the company’s reputation if the issue reoccurs, as stakeholders may question the company’s ability to resolve problems effectively.</p></li></ul><p>3. <strong>Transferable Skills for Individuals Conducting RCA's:</strong></p><p>Conducting RCAs regularly requires a diverse set of skills that go beyond technical expertise. Some of the most important transferable skills include:</p><ul><li><p>Critical Thinking</p></li><li><p>Attention to Detail</p></li><li><p>Communication Skills</p></li><li><p>Problem-Solving</p></li><li><p>Teamwork</p></li></ul>]]></description>
         <enclosure url="https://upload.wikimedia.org/wikipedia/commons/0/01/202405_Thinking_young_female_researcher.svg" />
         <pubDate>2025-03-10 11:32:40 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3358688805</guid>
      </item>
      <item>
         <title>Lorrae Venise Diez</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3359179021</link>
         <description><![CDATA[<ol><li><p><strong>My Experience with Root Cause Analysis:</strong> While I was still working as a Pharmacist back in my home country, we noticed that a specific medication was frequently running out of stock earlier than expected. To investigate, we conducted an RCA by reviewing our inventory records, observing dispensing practices, and speaking with staff. We found out that incorrect data entry in the system was the reason that the stock levels appear higher than they actually were. After identifying the issue, we implemented a double-check process for inventory updates, which helped prevent future miscounts.</p></li><li><p><strong>Impact of Identifying the Wrong Root Cause: </strong>If the real issue isn't addressed, the company might invest in unnecessary changes, like increasing orders when the real problem is a system error. The issue will also keep happening if it wasn't fixed.</p></li><li><p><strong>Important Transferable Skills for RCA: </strong></p><p>Attention to detail.</p><p>Critical thinking</p><p>Communication</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-10 16:25:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3359179021</guid>
      </item>
      <item>
         <title>Karen Joy Manalili 301333436</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3359824193</link>
         <description><![CDATA[<p>My experience with a Root Cause Analysis investigation that I have participated in.</p><p><br/></p><p>While I was working as a licensed Pharmacist in one of the most significant community pharmacies in the Philippines, we conducted a regular inventory to monitor the fast-moving medications. As I was doing the inventory, I noticed a considerable discrepancy in the quantity available on the shelf, which was less than the inventory count in the system. We checked all the transactions that week and noticed a mistake with the quantity encoded by the person in charge. After finding the root cause of the discrepancy, we corrected it immediately and implemented a triple-check of the amount we received and encoded in the system to avoid any shorter supply of medications needed by the customers or patients.</p><p><br/></p><p>How do you think the wrong Root Cause being identified from an investigation will impact a company?</p><p><br/></p><p>   </p><ol><li><p>If the wrong root cause is identified, resources will be wasted because the time, money, and effort invested in finding the root cause of the problem were not resolved correctly.</p></li><li><p>If the wrong root cause is identified, the problem will likely recur, leading to operational disruptions due to stock shortages.</p></li></ol><p><br/></p><p>What transferable skills do you think are most important to individuals who conduct RCA's regularly </p><p><br/></p><ol><li><p>Teamwork- helping and collaborating to identify the root cause of the problem.</p></li></ol><ol start="2"><li><p>Critical Thinking- identifying the possible root scenarios of why the problem happens.</p></li><li><p>Communication- being open to suggestions and listening to what the team suggests.</p></li></ol><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-11 01:30:05 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3359824193</guid>
      </item>
      <item>
         <title>Cristine Joy Pimentel (301310356)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3361604118</link>
         <description><![CDATA[<p>When I was working as a Pharmacist in a hospital setting, I participated in a Root Cause Analysis (RCA) investigation after a patient experienced an adverse drug event (ADE). This case stood out to me because it highlighted the critical role RCA plays in ensuring patient safety.</p><p>The patient, who was on multiple medications, experienced an adverse reaction. Upon noticing the symptoms, our team immediately reviewed all aspects of the patient’s treatment. We checked each medication, the timing of doses, and the IV fluids administered. After a thorough review of the patient’s chart, we identified that the infusion rate of an antibiotic exceeded the recommended rate based on the patient's age.</p><p>We recommended decreasing the infusion rate to the attending physician, which resolved the issue. An ADE form was completed, and we continued monitoring the patient to prevent further complications.</p><p><strong>Impact of Incorrect Root Cause Identification:</strong></p><ol><li><p>The real issue may remain unresolved, leading to recurring adverse events and can cause damage to the Hospital and healthcare team. </p></li><li><p>Resources could be misdirected, causing inefficiencies and potential harm to other patients.</p></li></ol><p><br></p><p><strong>Transferable Skills for RCA Practitioners:</strong></p><ol><li><p><strong>Attention to detail</strong> ensures that no critical information is overlooked.</p></li><li><p><strong>Effective teamwork</strong> fosters collaboration across healthcare professionals to solve complex issues.</p></li></ol><p>This experience reaffirmed the value of RCA in healthcare. By identifying the correct root cause, we were able to implement corrective actions, improving patient safety and reducing risks for others on similar treatments.</p><p><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-11 23:09:51 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3361604118</guid>
      </item>
      <item>
         <title>Shraddha Parmar (301427036)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3361613109</link>
         <description><![CDATA[<p><strong>Experience with a Root Cause Analysis (RCA) </strong><br></p><p>As a product assembly worker, I participated in a Root Cause Analysis when a recurring defect was identified in assembled units. The issue involved a misalignment in a critical component, which initially caused performance failures. My role in the investigation included providing insights into the assembly process, identifying variations in procedures, and documenting observations. Through a detailed analysis, the root cause was traced back to inconsistent torque application on fasteners, leading to misalignment. The corrective action involved updating assembly guidelines and retraining staff to ensure uniform torque application.</p><p><br/></p><ul><li><p><strong>Impact of Identifying the Wrong Root Cause:</strong></p><ul><li><p><strong>Increased Costs &amp; Wasted Resources:</strong> If the wrong cause is identified, the company may invest time and money in fixing a non-existent issue. For example, if a defect is wrongly attributed to faulty raw materials rather than an assembly error, resources may be wasted on replacing perfectly good materials instead of improving the assembly process.</p></li><li><p><strong>Repeated Failures &amp; Customer Dissatisfaction:</strong> Misdiagnosing the issue can lead to recurring defects, damaging the company’s reputation. For instance, if a product’s failure is mistakenly linked to a minor component rather than a design flaw, customers may continue to receive defective products, leading to recalls, warranty claims, and loss of trust.</p><p><br/></p><p><strong>Important Transferable Skills for RCA Investigators:</strong></p><p><br/></p></li><li><p><strong>Critical Thinking:</strong> The ability to analyze data, ask the right questions, and logically connect cause and effect is essential.</p></li><li><p><strong>Attention to Detail:</strong> Identifying subtle variations in processes and equipment that may contribute to failures is crucial.</p></li><li><p><strong>Problem-Solving Skills:</strong> Finding effective, long-term solutions rather than temporary fixes ensures sustained improvements.</p></li></ul></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-11 23:21:30 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3361613109</guid>
      </item>
      <item>
         <title>Mandeep Kaur (301295079)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3361796461</link>
         <description><![CDATA[<p>My experience with a root cause analysis (RCA):<br>I work as a security guard, and one day a resident approached me to report that the sanitizer wipes were finished, which could be a safety concern. I decided to investigate the issue. After looking into it, I discovered that while management kept records of supplies, the cleaning staff didn’t have a system in place to track the usage and restocking of essential items. As a result, the wipes had run out without anyone noticing in time.To address this, I suggested that the cleaning staff begin keeping their own records of supplies, particularly the sanitizer wipes, so that they could notify management in advance when supplies were low. Additionally, management decided to increase the amount of supplies kept on hand to prevent this from happening in the future.</p><ol start="2"><li><p>Impact of incorrect root cause analysis</p></li></ol><p>The main issue will remain unsolved and the residents will become more angry and annoyed. </p><ol start="3"><li><p>Tranferable skills include team work, problem-solving mind and analytical thinking.</p></li></ol><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-12 01:21:54 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3361796461</guid>
      </item>
      <item>
         <title>Vaibhav Kumar (301430352)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3365063142</link>
         <description><![CDATA[<p>During our <strong>Development of Advanced Antifogging Formulations for Optical Lenses</strong> project at Centennial College, we encountered an unexpected issue that required us to conduct a <strong>Root Cause Analysis (RCA)</strong>.</p><p>Our goal was to create an effective antifogging solution for eyeglasses, and early tests showed promising results. However, at one stage, our formulation was not performing consistently—some samples worked perfectly, while others allowed fogging within minutes. Since our final evaluation involved a real-world simulation with prescription glasses users, we needed to find the root cause quickly.</p><p><strong>The Investigation Process</strong></p><p>To identify the issue, we systematically examined each factor that could have influenced the results:</p><ol><li><p><strong>Chemical Composition:</strong> We checked whether any variation in ingredient concentrations affected the antifogging performance.</p></li><li><p><strong>Application Method:</strong> We reviewed whether differences in coating thickness or drying time led to inconsistent results.</p></li><li><p><strong>Testing Conditions:</strong> We ensured the water bath, light intensity, and humidifier methods were applied uniformly across all samples.</p></li></ol><p>After careful analysis, we discovered that <strong>inconsistent drying times</strong> were the root cause. Some samples were air-dried at different temperatures, leading to variations in the nanoparticle layer formation. Once we standardized the drying conditions, the formulation performed consistently and even outperformed a leading commercial product. </p><p><strong>Key Takeaways</strong></p><p>Through this RCA experience, I learned that <strong>attention to detail, problem-solving, and systematic testing</strong> are crucial for troubleshooting issues in product development. It also reinforced the importance of keeping thorough records, as having well-documented procedures helped us pinpoint the exact step that needed correction.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-13 17:10:11 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3365063142</guid>
      </item>
      <item>
         <title>Basarathussain Mahida 301415686</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3366672916</link>
         <description><![CDATA[<p>Hi, I’m Basarathussain Mahida, and I’d like to share my experience with Root Cause Analysis (RCA).</p><p><strong>1. My Experience with RCA:</strong></p><p>During a microbiology project, we faced inconsistent results in Pseudomonas aeruginosa bioremediation. Using RCA, we identified that pH fluctuations in our media were affecting bacterial growth. Once corrected, our results stabilized.</p><p><strong>2. Impact of Identifying the Wrong Root Cause:</strong></p><p>	•	Increased Costs: Misdiagnosing an issue leads to wasted resources, like replacing equipment unnecessarily.</p><p>	•	Reputational Damage: Persistent quality issues can result in recalls and loss of consumer trust.</p><p><strong>3. Key Skills for RCA:</strong></p><p>	•	Analytical Thinking – Breaking down complex problems.</p><p>	•	Attention to Detail – Identifying small but critical factors.</p><p>	•	Communication &amp; Collaboration – Gathering accurate information.</p><p>	•	Problem-Solving – Implementing effective solutions.</p><p><strong>Conclusion:</strong></p><p>RCA is essential in science and industry, helping prevent recurring issues. </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-14 16:41:41 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3366672916</guid>
      </item>
      <item>
         <title>Kevin Gandhi 301380222</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3366673536</link>
         <description><![CDATA[<p>During a lab project, we encountered inconsistent microbial test results. At first, we assumed contamination was the issue. However, after conducting a root cause analysis (RCA), we discovered that the real problem was improper dilution techniques and the use of an incorrect agar medium. Once we corrected these mistakes, our results became reliable, emphasizing the importance of a structured approach to problem-solving.</p><p>Misidentifying the root cause of an issue can have serious consequences. For example, a company might waste resources on excessive sanitation efforts instead of addressing a contaminated ingredient. Similarly, incorrectly attributing the problem to equipment failure rather than inadequate employee training could lead to audit failures, product recalls, and a loss of consumer trust.</p><p>RCA involves both technical and soft skills. Critical thinking and attention to detail help pinpoint the actual causes of an issue, while effective communication and teamwork ensure that corrective actions are properly implemented. Structured problem-solving methods, like the "5 Whys," help avoid assumptions and lead to accurate conclusions.</p><p>When done correctly, RCA prevents recurring problems, reduces costs, and improves overall efficiency across various industries.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-14 16:42:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3366673536</guid>
      </item>
      <item>
         <title>Tanvi Panchal</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3367391810</link>
         <description><![CDATA[<p>During my experience with Root Cause Analysis, I remember participating in an investigation within my previous role, where we were trying to understand the cause of a recurring issue with our production process. The team was composed of various departments, including quality control, engineering, and operations. We gathered data from different shifts, reviewed machine logs, and interviewed operators. After performing a fishbone diagram analysis, we identified a malfunctioning sensor as the primary cause of the issue. The investigation process was thorough and collaborative, ensuring we looked at all potential causes before zeroing in on the real problem.</p><p><br/></p><p><strong>How Identifying the Wrong Root Cause Can Impact a Company:</strong></p><p>Identifying the wrong root cause during an investigation can have significant consequences for a company. For example:</p><ul><li><p><strong>Wasted Resources</strong>: If the root cause is misidentified, the company may spend time and resources implementing a solution that doesn’t address the real issue. This can lead to continued problems, as the solution doesn’t solve the underlying cause.</p></li><li><p><strong>Loss of Credibility and Trust</strong>: When a company fails to solve problems due to incorrect RCA, it can erode trust with customers or stakeholders. If clients see recurring issues, they may lose confidence in the company’s ability to resolve challenges, which could affect business relationships and revenue.</p><p><br/></p><p><strong>Transferable Skills Important for Conducting RCAs Regularly:</strong></p><p>Some of the most important transferable skills for individuals who conduct RCAs regularly include:</p><ul><li><p><strong>Critical Thinking</strong>: Being able to assess the situation objectively, analyze all possible causes, and apply logic to draw conclusions is key.</p></li><li><p><strong>Communication</strong>: RCA requires collaboration across different teams, so being able to effectively communicate findings, share ideas, and understand diverse perspectives is essential.</p></li><li><p><strong>Attention to Detail</strong>: Investigating complex problems often involves digging into data, processes, and workflows. A keen eye for detail ensures that no stone is left unturned.</p></li><li><p><strong>Problem-Solving</strong>: RCA is ultimately about finding solutions. Strong problem-solving skills are necessary to address the root cause efficiently and effectively.</p></li></ul></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-15 17:21:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3367391810</guid>
      </item>
      <item>
         <title>Arman Kachwala 301273103</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3367584434</link>
         <description><![CDATA[<p>In my independent research project at Centennial College, I worked on enhancing the shelf life of strawberries by using<strong> </strong>chitosan nanoparticles and UV-C treatment. During the coating process, I noticed that the chitosan nanoparticles solidified into a gelatinous form instead of remaining in liquid. After conducting a Root Cause Analysis, I discovered that the pH of the chitosan solution had not been adjusted properly. The optimal pH for maintaining the liquid form of nanoparticles is 5.6, but it was either too high or too low. Once I corrected the pH level, the nanoparticles remained in liquid form, and the coating process was successful, leading to better shelf life and reduced microbial decay in the strawberries.</p><ul><li><p><strong>Impact of Identifying the Wrong Root Cause</strong>: If the wrong root cause had been identified, the following outcomes could have occurred:</p><ul><li><p>If I had focused on the chitosan concentration or mixing technique, I would have spent unnecessary time adjusting these parameters, which would not have solved the real issue, delaying the progress of the project.</p></li><li><p>If I had assumed that the problem was related to the UV-C treatment process, I might have changed the UV dosage or exposure time, which would not have addressed the pH imbalance, resulting in continued nanoparticle inconsistencies and ineffective coating.</p></li></ul></li><li><p><strong>Transferable Skills for Root Cause Analysis</strong>: The RCA process in this experiment helped me develop several important transferable skills:</p><ul><li><p><strong>Attention to Detail</strong>: Carefully monitoring the pH levels and preparation steps to ensure the correct consistency of the nanoparticles.</p></li><li><p><strong>Analytical Thinking</strong>: Methodically analyzing all potential causes and narrowing down to the true issue, which was the pH imbalance.</p></li><li><p><strong>Problem-Solving</strong>: Quickly identifying and adjusting the pH level to fix the issue, allowing the experiment to proceed successfully and meet its objectives.</p></li></ul></li></ul>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/3543356024/fedfb12d962196a613590d0a0ebc53d6/root_cause_analysis.webp" />
         <pubDate>2025-03-16 03:38:28 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3367584434</guid>
      </item>
      <item>
         <title>Sharfaa Sanaa K S (301310265)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3368671755</link>
         <description><![CDATA[<p><em>In my previous experience, I was involved in an RCA investigation where we identified a recurring issue related to [general problem – e.g., product quality, food safety, equipment failure, or process inefficiency]."</em></p><p><em>"The issue was impacting [mention the consequence – e.g., production delays, customer complaints, safety risks]."</em></p><p><em>"To identify the root cause, we followed a structured approach using tools like [mention any tools used – 5 Whys, Fishbone Diagram, process mapping, or data analysis]. Through this, we discovered that the real issue was [explain the true root cause]."</em></p><p><em>"Once we had a clear understanding, we implemented [mention corrective actions – e.g., process improvements, employee training, equipment maintenance]. As a result, we saw [mention the impact – e.g., fewer defects, improved safety, increased efficiency]."</em></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-17 05:02:41 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3368671755</guid>
      </item>
      <item>
         <title>Jonathan Saldanha 301302600</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3370283508</link>
         <description><![CDATA[<p>One example of an RCA I participated in was during a microbiology experiment. We were testing the antimicrobial properties of essential oils, and our results were inconsistent. Instead of assuming a simple error, we conducted an RCA to identify the root cause. We examined our methodology, environmental conditions, and sample preparations. After thorough investigation, we found that cross-contamination during pipetting was the issue, leading to unreliable results. By addressing this, we improved our experimental accuracy. The impact of identifying the wrong root cause : </p><ul><li><p><strong>Wasted Resources</strong><em>:</em></p><ul><li><p>If a company misidentifies the cause of a product defect and invests in fixing the wrong process, they waste time and money without solving the actual issue.</p></li></ul></li></ul><ul><li><p><strong>Reputation Damage:</strong></p><ul><li><p>If a business incorrectly blames user error for a safety issue instead of a design flaw, it could lead to product recalls, lawsuits, and loss of customer trust.</p></li></ul><p>Some transferable skills would be:</p></li><li><p><strong>Critical Thinking:</strong> The ability to ask "why" multiple times and analyze data logically to uncover the real issue.</p></li><li><p><strong>Attention to Detail:</strong> Small oversights can lead to incorrect conclusions, so being thorough is crucial.</p></li><li><p><strong>Communication Skills:</strong> Clearly presenting findings and ensuring corrective actions are implemented effectively is key to successful RCA.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-18 01:36:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3370283508</guid>
      </item>
      <item>
         <title>Colyn Depositario (301370577)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3371394311</link>
         <description><![CDATA[<p>I once conducted an investigation to determine why students were not obtaining the expected results in an experiment. I followed all the protocols outlined in the Standard Operating Procedure (SOP) and discovered that the procedure itself wasn’t the issue. However, when I repeated the experiment using fresh reagents, it worked perfectly.</p><p>Upon further investigation, I found that students had mixed the chemicals incorrectly and failed to return them to their proper order. As a result, the experiment failed to produce the expected outcome. Some groups achieved the correct result, while others—who unknowingly used the altered chemicals—obtained unexpected results. Since they didn’t witness the improper mixing, they couldn’t identify why the chemical reaction changed.</p><p>If the wrong Root Cause is identified in an investigation, it can significantly impact a company. For example:</p><ol><li><p><strong>Wasted Resources</strong> – If a company addresses the wrong cause, they may invest time and money into solutions that don’t actually fix the problem.</p></li><li><p><strong>Compromised Product Quality</strong> – If the true issue remains unresolved, defective or inconsistent products could reach consumers, damaging the company’s reputation and leading to financial losses.</p></li></ol><p>The most important transferable skill for individuals conducting Root Cause Analysis is <strong>attention to detail</strong>. RCA investigators must carefully analyze every factor to ensure they identify the true cause of an issue. Additionally, <strong>critical thinking</strong> is essential to question assumptions and systematically eliminate possible causes.</p>]]></description>
         <enclosure url="https://media2.giphy.com/media/l378rhA6c1QhJDgbu/giphy.gif?cid=cabc9918z8mc2695klrqbfomu1c4cnqybybbsgo5yj5e67l7&amp;ep=v1_gifs_search&amp;rid=giphy.gif&amp;ct=g" />
         <pubDate>2025-03-18 14:34:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3371394311</guid>
      </item>
      <item>
         <title>Sukhmanpreet Singh (301349102)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3371741893</link>
         <description><![CDATA[<p><strong>My RCA Experience:</strong><br>As a supervisor at Swiss Chalet and Harveys, I oversee daily operations, ensuring everything runs smoothly. One incident required an RCA when we noticed an increase in incorrect orders going out to customers. At first, it seemed like a simple case of human error, so we focused on retraining staff. However, mistakes kept happening.</p><p>To find the real issue, we conducted an RCA. We observed order preparation, checked the POS system, and spoke with employees. We discovered that the root cause was a misalignment between the digital order screen and printed tickets, causing confusion in the kitchen. By fixing the system error and clarifying order-checking procedures, we significantly reduced mistakes and improved accuracy.</p><p><strong>Impact of Identifying the Wrong Root Cause:</strong><br>If an RCA identifies the wrong cause, it can harm a company in different ways. Here are two examples:</p><ol><li><p><strong>Increased Costs:</strong> If we had only focused on retraining staff without fixing the real problem, we would have wasted time and resources while errors continued.</p></li><li><p><strong>Loss of Customer Trust:</strong> Repeated mistakes in orders lead to negative reviews, complaints, and potential loss of regular customers.</p></li></ol><p><strong>Important Transferable Skills for RCA:</strong><br>For individuals who conduct RCA regularly, key skills include:</p><ul><li><p><strong>Problem-Solving:</strong> Identifying patterns and digging deeper into issues.</p></li><li><p><strong>Communication &amp; Collaboration:</strong> Working with different departments to find solutions.</p></li><li><p><strong>Attention to Detail:</strong> Noticing small but critical factors that contribute to problems.</p></li><li><p><strong>Adaptability:</strong> Adjusting processes based on findings to prevent future issues.</p></li></ul><p><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-18 18:30:15 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3371741893</guid>
      </item>
      <item>
         <title>Komal Basra (301414273)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3371889171</link>
         <description><![CDATA[<p>During my undergraduate research project, I encountered an issue with Gram staining where my results showed excess debris on the glass slide. At first, I suspected the problem might be with my washing step. To resolve this, I adjusted the washing procedure multiple times, but the issue persisted.</p><p><strong>Task:</strong> I decided to perform a Root Cause Analysis (RCA) to identify the true source of the problem and address it systematically.</p><p><strong>Action:</strong> Through RCA, I systematically investigated the process by considering each step involved in the Gram staining procedure. I reviewed the reagents and equipment in use. Upon inspecting the Gram staining reagents, I discovered that they contained an unusual amount of debris. Realizing that the issue lay with the reagents, I used syringe filters to clean them and remove the debris. After cleaning the reagents, the staining process worked as expected, and the excess debris on the slides was eliminated.</p><p><strong>Result:</strong> If I had not performed RCA, I would have continued adjusting my washing step and potentially other parts of the technique, never addressing the core problem. By identifying and solving the issue with the reagents, I saved time and effort, allowing me to successfully complete the experiment. This also helped me avoid unnecessary changes to other parts of the protocol that were functioning correctly.</p><p><strong>Impact of RCA:</strong></p><ol><li><p><strong>Problem Resolution:</strong> RCA led me to the root cause (contaminated reagents) rather than addressing symptoms (adjusting washing steps), resulting in a more effective solution.</p></li><li><p><strong>Efficiency Improvement:</strong> The RCA process helped me pinpoint the issue quickly, saving time and preventing frustration from repeated trial and error with the washing technique.</p></li><li><p><strong>Enhanced Critical Thinking:</strong> By following RCA, I learned to look beyond the obvious and focus on every detail of the process, improving my ability to troubleshoot complex problems.</p></li></ol><p><strong>Transferable Skills Learned:</strong></p><ol><li><p><strong>Problem-Solving:</strong> I developed the ability to break down problems into smaller, manageable parts, making it easier to identify the true cause of an issue.</p></li><li><p><strong>Analytical Thinking:</strong> I enhanced my skills in analyzing each step of a process and evaluating potential sources of error, which can be applied to future research and work settings.</p></li><li><p><strong>Attention to Detail:</strong> I learned to thoroughly inspect all variables involved in a process, which is crucial for avoiding overlooked issues in any field of work.</p></li><li><p><strong>Adaptability:</strong> While troubleshooting the issue, I learned the importance of adapting and being open to changing my approach when the situation calls for it.</p></li><li><p><strong>Project Management:</strong> By systematically approaching the issue and keeping track of changes, I gained skills in managing and documenting problem-solving processes, which is valuable in any team or project context.</p></li></ol><p>This experience demonstrated the importance of RCA in problem-solving and how it can be applied to a wide range of challenges beyond just laboratory work.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-18 20:57:27 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3371889171</guid>
      </item>
      <item>
         <title>Urvi Joshi (301272847)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3373668298</link>
         <description><![CDATA[<p>One of my most memorable experiences as a QA Technician was conducting a Root Cause Analysis (RCA) for a recurring packaging defect in a food production facility. Customers reported pouches bursting during transport, leading us to suspect a packaging machine issue. The maintenance team adjusted sealing temperatures, QA checked seals, and production monitored the process—but complaints persisted.</p><p>Digging deeper, we reviewed batch records, tested seal strength, and had suppliers inspect materials. Everything seemed fine until a full-line walkthrough revealed the real culprit: excess product occasionally interfering with the sealing process. A minor adjustment in the filling process—not the packaging machine—was needed.</p><p>Had we misidentified the root cause, the company could have wasted money on unnecessary machine repairs while the issue remained unresolved, damaging customer trust. Identifying the correct cause prevented future complaints and ensured product quality.</p><p>This experience reinforced why accurate RCA is critical. Misdiagnosing issues can lead to:</p><ol><li><p><strong>Wasted Resources</strong> – Rejecting raw materials due to a misidentified contamination source can result in financial losses while the real issue persists.</p></li><li><p><strong>Regulatory &amp; Customer Impact</strong> – Failing to resolve a food safety issue correctly can lead to recalls, legal trouble, and reputational damage.</p></li></ol><p>Successful RCA requires <strong>critical thinking</strong>, <strong>attention to detail</strong>, and <strong>teamwork</strong>. It’s not just about fixing problems—it’s about preventing them. And when you finally uncover the real cause, it’s one of the most satisfying moments in QA!</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-19 20:08:23 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3373668298</guid>
      </item>
      <item>
         <title>Erica Mae Gacutan (301389500)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3374095081</link>
         <description><![CDATA[<p>In my previous role as a chemist, I regularly conducted root cause analysis (RCA) whenever deviations occurred in the quality control samples during analysis. These control samples were tested alongside the actual samples to ensure the reliability of results. On one occasion, the recovery of an analyte in a quality control sample repeatedly failed, causing delays in the release of test results. As a result, I received a nonconformity report from the quality management head and initiated an investigation.</p><p><br/></p><p>Through an extensive RCA process, including the Five Whys technique, I discovered that an expired stock solution had been used in preparing the quality control sample. However, I determined that this was not the true root cause. The fundamental issue was the absence of a procedure for updating chemical inventories. To address this, I implemented a corrective action plan by drafting and obtaining approval for a standardized procedure to ensure proper chemical inventory management across the laboratory. Simply replacing the expired stock solution would have been a temporary fix, but addressing the systemic issue helped prevent future occurrences.</p><p><br/></p><p>I believe that misidentifying the root cause leads to recurring problems, resulting in wasted laboratory resources and delays in test result releases. Key transferable skills in effective RCA include attention to detail, which allows for identifying small yet critical factors, and strong communication skills, which are essential for clearly presenting findings and collaborating with colleagues to implement corrective actions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-20 02:27:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3374095081</guid>
      </item>
      <item>
         <title>DEVANSHI SHAH (301413938)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3374214281</link>
         <description><![CDATA[<p>Root Cause Analysis (RCA) is a structured approach to identifying the underlying cause of a problem to prevent it from recurring. While I haven’t conducted a formal RCA in a technical setting, I have applied similar problem-solving techniques in previous roles. <strong>As a cashier</strong>, if a customer disputes a price, I don't just correct it—I investigate whether the issue stems from a mislabeled shelf, a system error, or a misunderstanding of a promotion. <strong>For example, </strong>I once discovered that a higher-than-advertised price was due to an outdated shelf label. Reporting this to the supervisor ensured the issue was corrected, preventing further customer complaints.</p><p><br/></p><p>Identifying the wrong root cause in an investigation can lead to significant consequences, such as financial loss and customer dissatisfaction. If pricing errors are incorrectly blamed on employee mistakes rather than a system issue, time and resources may be wasted on unnecessary retraining instead of fixing the real problem. Similarly, if long checkout times are attributed solely to slow cashiers instead of understaffing, employees may be pressured to work faster, leading to mistakes and unhappy customers. Addressing the true cause of problems is essential for efficiency and customer satisfaction.</p><p><br/></p><p>To effectively conduct RCA, certain transferable skills are crucial. Critical thinking helps analyze patterns, while attention to detail ensures small but important factors are not overlooked. Strong communication skills are necessary to share findings with supervisors, and problem-solving abilities help implement practical solutions. These skills are valuable even in a cashier role, contributing to smoother store operations and opening opportunities for advancement into leadership positions.</p>]]></description>
         <enclosure url="https://www.adaptiveus.com/hubfs/chub_backup/Remote%20Data%20Analyst.jpg" />
         <pubDate>2025-03-20 03:40:57 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3374214281</guid>
      </item>
      <item>
         <title>Siddhiben Patel(301398234) </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3375361090</link>
         <description><![CDATA[<p><strong>My Experience with Root Cause Analysis (RCA)</strong></p><p>During my research on isolating <em>Lactobacillus</em> from cucumber and carrot for antibacterial studies, I encountered an issue where my bacterial cultures were not growing consistently on selective media. Initially, I assumed the media preparation was faulty, so I remade it, but the problem persisted. To pinpoint the root cause, I systematically analyzed each step of my process—media sterilization, sample handling, and incubation conditions. Eventually, I discovered that fluctuations in the incubator’s temperature and inadequate sterilization of my workspace were affecting my results. Once I addressed these issues, the bacterial growth became more consistent, demonstrating how RCA helped me troubleshoot effectively.</p><p><br/></p><p>Identifying the wrong root cause in an investigation can significantly impact a company. One major consequence is wasted resources and time—if a company mistakenly attributes a production failure to the wrong factor, it may invest in unnecessary fixes while the real problem remains unresolved. For example, if a pharmaceutical company misidentifies the cause of bacterial contamination in its product line, it might reformulate ingredients instead of addressing improper sterilization, leading to continued production issues. Another outcome is compromised product quality and safety. If an incorrect RCA conclusion is applied in food manufacturing, the actual cause of spoilage might persist, leading to recalls, reputational damage, and potential health risks for consumers.</p><p><br/></p><p>To conduct RCA effectively, several transferable skills are essential. <strong>Critical thinking</strong> is crucial, as it allows individuals to systematically evaluate multiple possible causes and identify the true issue. <strong>Attention to detail </strong>is also important because minor deviations in processes, such as slight temperature fluctuations or improper sterilization techniques, can have significant effects. Additionally,<strong> problem-solving skills</strong> help in developing effective corrective actions to prevent recurrence. Lastly, <strong>strong communication</strong> and collaboration skills are vital, as RCA often involves working with a team to gather information, analyze data, and implement solutions efficiently.          </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-20 17:44:00 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3375361090</guid>
      </item>
      <item>
         <title>AKHIL AKBARI (SN# 301319266)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3375436058</link>
         <description><![CDATA[<p>Hey everyone! I wanted to share an experience related to a Root Cause Analysis (RCA) I participated in while working as a Bakery Associate at Walmart. This might not have been a formal investigation with all the technical details, but it was definitely an example of RCA in action.</p><p>One day, we noticed that certain baked goods weren’t being sold as fast as usual. It was a slow sales day, but even with the rest of the bakery products flying off the shelves, a few items were just sitting there. It wasn't a huge deal at first, but when this pattern continued for a few days, our supervisor asked us to look into it and figure out what was going on.</p><p>The first thing we did was think about the possible causes. Was it a product quality issue? Were customers not seeing the items on the shelf? Did we miss a step in the baking process? It could’ve been any number of things. After a quick team huddle, we realized the problem: the items weren’t being placed in the best locations. They were on the top shelf where people couldn’t easily see them. When we moved them to eye level, sales picked up immediately.</p><p>This experience got me thinking about how important it is to identify the <em>real</em> root cause. If we hadn’t done a quick investigation, we might have blamed the quality of the products or assumed that customers just weren’t interested, when the actual issue was just the placement.</p><p>In terms of impact, if a company identifies the wrong root cause, it can waste time and resources. For example, if we’d assumed the products were bad, we could’ve thrown out perfectly good stock, which would’ve been wasteful. Or, if we didn’t adjust the placement and just kept pushing for higher sales, we might’ve continued to miss opportunities and not addressed the real issue. Identifying the wrong root cause can also lead to employee frustration—like if you try to make changes that don’t actually improve things, people can lose motivation.</p><p>For anyone doing RCAs, I think the most important skills are observation, critical thinking, and communication. You need to observe the situation closely, think through all possible causes, and communicate with others to make sure you're seeing the bigger picture. It’s not just about fixing the immediate problem but about looking at the whole process to make sure the solution is sustainable.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-20 18:47:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3375436058</guid>
      </item>
      <item>
         <title>Parthvi Patel (301398219)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3375918347</link>
         <description><![CDATA[<p>My Experience with a Root Cause Analysis Investigation</p><ul><li><p>Recently, I participated in an RCA investigation to address an ongoing product quality issue.</p></li><li><p>Routine inspections showed that multiple batches were failing to meet specifications, leading to production delays and material waste.</p></li></ul><p><strong>Initial Assumptions &amp; Investigation:</strong></p><ul><li><p>The team initially suspected equipment malfunction as the root cause.</p></li><li><p>Spent significant time troubleshooting and performing maintenance, but the issue persisted.</p></li><li><p>To take a more structured approach, we applied the <strong>"5 Whys" method</strong> and a <strong>Fishbone Diagram</strong> to systematically analyze potential factors.</p></li></ul><p><strong>Findings &amp; Root Cause:</strong></p><ul><li><p>Further investigation confirmed that the issue was not due to equipment failure.</p></li><li><p>The real cause was <strong>inconsistencies in raw materials</strong> from a new supplier.</p></li><li><p>By reviewing production data and comparing supplier batches, we identified variations in raw material quality impacting product consistency.</p></li></ul><p><strong>Key Takeaways:</strong></p><ul><li><p>Relying on assumptions would have resulted in wasted time and resources without resolving the actual issue.</p></li><li><p>This experience highlighted the importance of conducting a <strong>thorough RCA</strong> instead of addressing surface-level symptoms.</p></li><li><p>Gained valuable skills in <strong>critical thinking, teamwork, and persistence in problem-solving</strong>.</p></li><li><p>Moving forward, I ensure a <strong>structured and analytical approach</strong> to identifying the true root cause before taking corrective actions.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 02:18:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3375918347</guid>
      </item>
      <item>
         <title>Cecilia Ricci Tria (301328908)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3375922926</link>
         <description><![CDATA[<p><strong>RCA Experience </strong></p><p>During my CO-OP experience as a Quality Assurance Technician, I had the opportunity to be involved in a Root Cause Analysis (RCA) investigation. One specific instance that stands out was when we identified an increased presence of bones in chicken tenders due to a malfunctioning X-ray machine.</p><p><br></p><p>With the X-ray machine not functioning correctly, it was unable to detect and reject bone fragments in the tender’s area. As a result, the QA team had to thoroughly check the tenders every hour to ensure product quality and safety. This manual inspection process was time-consuming but necessary to prevent defective products from reaching consumers while maintenance worked on fixing the machine.</p><p><br></p><p>Reflecting on this experience, I realize how critical it is to identify the correct root cause. If we had assumed that the issue stemmed from supplier quality instead of equipment failure, we might have imposed unnecessary restrictions on raw material providers while the real problem remained unresolved. This could have led to continued product defects, inefficiencies, and potential consumer safety risks.</p><p><br></p><p><strong>Impact of Wrong Root Cause Identification</strong></p><ol><li><p><strong>Wasted Resources</strong>: If a company misdiagnoses a problem and implements incorrect corrective actions, it may invest time and money in unnecessary solutions while the real issue remains unresolved. For example, if a food manufacturer mistakenly blames a supplier for a microbial contamination issue instead of identifying an internal hygiene lapse, they could end up severing valuable supplier relationships while failing to fix the actual problem.</p><p><br></p></li><li><p><strong>Damage to Reputation</strong>: If the true issue is not addressed, recurring problems can lead to customer complaints, recalls, or regulatory actions. A company that repeatedly faces quality issues due to improper investigations may lose consumer trust, which can be difficult to regain.</p></li></ol><p><br></p><p><strong>Transferable Skills for RCA Practitioners</strong></p><ul><li><p><strong>Critical Thinking</strong>: Being able to analyze data objectively and avoid jumping to conclusions ensures a thorough investigation.</p><p><br></p></li><li><p><strong>Collaboration</strong>: RCA requires input from various departments, and effective communication with cross-functional teams helps in gathering accurate information and developing sustainable solutions.</p></li></ul><p><br></p><p>Overall, participating in an RCA investigation gave me valuable insights into problem-solving in a real-world setting. It reinforced the importance of patience, thorough investigation, and teamwork in ensuring product quality and safety. I look forward to applying these lessons in future roles, knowing that a well-executed RCA can make a significant difference in preventing recurring issues and improving overall processes.</p><p><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 02:20:41 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3375922926</guid>
      </item>
      <item>
         <title>Frenzy Mae Soriano 301381017</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3376006298</link>
         <description><![CDATA[<p>I worked as a laboratory assistant in a microbiology lab. There was an incident where a batch of samples got contaminated, and we had to figure out why. We started a Root Cause Analysis (RCA) to investigate. The team looked into possible causes like equipment failure, incorrect procedures, or contamination from the environment.</p><p>After gathering all the data, we mistakenly concluded that it was due to equipment malfunction. But after more checks, we realized it was actually because of improper sample handling during preparation. By jumping to conclusions, we wasted time and resources on fixing the wrong thing. This delayed the resolution and caused more contamination issues later on.</p><p>If the wrong root cause is identified in an RCA, it can really hurt a company. For example, one outcome is wasting time and resources fixing the wrong issue, which could lead to more problems down the line. Another outcome could be the same issue recurring because the actual cause wasn’t addressed, affecting product quality or customer trust.</p><p>For someone conducting RCA regularly, I think critical thinking and attention to detail are key. You have to stay focused, question assumptions, and make sure you're looking at all the evidence before jumping to conclusions. Communication skills are also important because you need to keep the team on the same page and ensure everyone's input is considered.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 03:10:10 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3376006298</guid>
      </item>
      <item>
         <title>Jan Alicia David (301372951)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3376020209</link>
         <description><![CDATA[<p><strong>RCA Experience: </strong>During the course of <em>Microbiology Project III</em>, I was able to utilize RCA methods to investigate the reason as to why the formulated herbal spray using guava leaf extract was lacking its film factor. Within 7 weeks time, we then learned that we were adding excess beeswax and lacking a substantial amount of emulsifying wax. RCA was used in getting the correct composition since formulating a film-forming spray requires first-hand observation and numerous amounts of trial-and-error processes. Later on, the group was able to create a film-forming spray under standard conditions.</p><p><br/></p><p>Taking this example into reflection, it was fortunate that the film-forming spray was done before the deadline. In the event that the formulation is taken into the industry, wrong root causes can affect the financial aspect of the company. It will take a lot of cost for the ingredients to be extracted and formulated in repetitions. Moreover, a wrong RCA can also affect the company's reputation in committing to consumer deadlines. Provided a standard timeline for the formulation, a setback can cost a lot of time; hence delaying the company's potential to market.</p><p><br/></p><p>Ultimately, the technical skills of being keen to details and consistent curiosity are essential to being a RCA key person since they will be in charge of ensuring that all the items or formulations passed are of standard.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 03:20:16 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3376020209</guid>
      </item>
      <item>
         <title>Albert Lorenz Orodio (301379154)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3376021472</link>
         <description><![CDATA[<p>In one of my previous job as a Junior Medical Technologist back in the Philippines, I was part of an investigation into recurring issues with test results not matching expectations. Through the Root Cause Analysis (RCA), we discovered the issue was due to a calibration error in the lab equipment, which had been overlooked due to oversight in the expiry date. By identifying this root cause, we were able to implement new procedures to prevent it from happening again, showing how important it is to dig deeper into problems to find the true cause, rather than just addressing symptoms.</p><p><br>If the wrong root cause is identified, it can lead to ongoing problems. For example, continuing to treat a problem as a staffing issue when the real cause is faulty equipment can waste resources and time. Additionally, in sensitive fields like healthcare, misidentifying the root cause can harm a company’s reputation and cause a loss of trust from patients or clients, especially if inaccurate results or diagnoses occur.</p><p><br/></p><p>With that, key skills include analytical thinking to break down problems, attention to detail to ensure all information is correct, communication skills to collaborate with others, and problem-solving abilities to find effective solutions. These skills are essential in any industry, especially healthcare, where thorough investigations and accurate solutions can make a significant difference in outcomes.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 03:21:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3376021472</guid>
      </item>
      <item>
         <title>Rajat Sah (301361059)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3376052430</link>
         <description><![CDATA[<p>I will share a recent situation from my workplace, which is an Italian restaurent. Recently, I had to investigate in the kitchen while working as a cook. One evening, we got complained from several customer that the tortino (a small Italian cake filled with chocolate) was undercooked. This was a serious issue because an improperly baked tortino would not have the right texture, potentially ruining the dining experience and affecting the restaurant’s reputation. As I was working in dessert department, I was assigned to investigate the issue.</p><p>To determine the root cause, I started by retracing my steps. I realized that I had relied on visual inspection rather than using a timer and checking the consistency properly. When I went to verify the oven temperature, I noticed it was set lower than required. After asking my coworkers, I found out that as oven from main course area was full, my co-workers used tortino oven for main course dish, which is cooked at a lower temperature, and unfortunately the setting had not been adjusted back for the tortino. This moment made me realize that a miscommunication in the kitchen and my carelessness to ensure the temperature of oven were the underlying causes of the problem.</p><p>To prevent this from happening again, I took the initiative to suggest some corrective actions. First, I ensured that every cook, including myself, in the kitchen double-checks the oven temperature before using . Second, I suggested implementing clear protocols for adjusting settings between different dishes. Lastly, I also encouraged the team to follow proper quality control procedures, such as using proper timers and checking doneness.</p><p>A wrongly identified root cause can have serious consequences for a business. For example, if a quality issue is not properly addressed, it could lead to repeated customer complaints, negative reviews, and a decline in trust. Additionally, failing to recognize deeper operational inefficiencies can result in increased waste, additional costs, and lower staff efficiency.</p><p>From this experience, I also learned that certain transferable skills are crucial for conducting Root Cause Analyses effectively. Attention to detail is most essential to identify problems accurately, while problem-solving skills help in creating effective solutions. Communication is also key because discussing findings with coworkers and managers ensures everyone is aware of necessary changes.</p><p>Looking back, this RCA not only helped prevent future mistakes in the kitchen but also improved my problem-solving skills. It showed me that addressing the root cause rather than just the surface issue leads to long-term improvements and better outcomes for both customers and the business.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 03:45:54 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3376052430</guid>
      </item>
      <item>
         <title>Gurkirt Kaur (301392484)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3376099811</link>
         <description><![CDATA[<p>During my research project, I encountered unexpected variations in microbial growth inhibition while testing the antimicrobial properties of essential oil-based nanoparticles. Initially, I assumed the inconsistency stemmed from differences in nanoparticle concentrations. To investigate, we conducted a Root Cause Analysis (RCA) using a systematic approach. First, we gathered data from all trials to identify patterns. Next, We performed controlled experiments, altering one factor at a time, and discovered that the variation was due to uneven dispersion of the nanoparticles in the testing medium. By refining the mixing technique and ensuring uniform distribution, the issue was resolved, leading to more consistent and reliable results.</p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><p>If the wrong root cause is identified in an investigation, it can lead to wasted resources and recurring problems. For example, in a biotech company producing pharmaceutical products, misidentifying contamination as a raw material issue rather than a sterilization failure could result in unnecessary supplier changes while the actual problem persists. </p><p><strong>Transferable Skills </strong></p><p>Individuals who regularly conduct RCA investigations must possess strong analytical and problem-solving skills to systematically identify the true cause of an issue. Attention to detail is crucial to recognize patterns and subtle deviations that may indicate underlying problems. </p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-21 04:34:34 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3376099811</guid>
      </item>
      <item>
         <title>Taylor Ellison (301395021)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3377205445</link>
         <description><![CDATA[<p>A time I had to use Root Cause Analysis was during my time working at a community center. There was a time where a room was double-booked. Because there was two different age groups doing two very different activities, the room couldn't just be shared. This led to one of the group's activities being cancelled. To find the root cause, I started by speaking with the camp coordinators for the two groups. They both told me that there was a miscommunication and that they thought they were the only one who had registered to use that room. Next, I went to the supervisor and asked if I could see the booking records which did indeed show that they had both booked that room at the same time. After showing the coordinators this, they explained that there was a new system and that they had misunderstood how to use it. Finally, I went back to the supervisor to ask why the staff were unaware of this issue and she informed me that the recreational staff had not gotten the appropriate training for this new system yet. </p><p>The wrong root cause being identified will cause the company to put resources into trying to fix a problem using a solution that won't work because it is not aimed at the root cause of the issue. This causes the issue to never be solved, and for resources to be lost.  The wrong root cause can also cause the wrong people to be held accountable for an issue while the actual source of the issue is never corrected. </p><p>The transferable skills that are most important for those conducting RCA are communication skills, problem-solving skills, and critical thinking.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-22 01:16:38 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3377205445</guid>
      </item>
      <item>
         <title>Seth ANIM [301281052] RCA </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3377904755</link>
         <description><![CDATA[<p>About a month ago at the food production company where I work as a manager, we began noticing early expiries in our key citrus products — lemon, lime, orange, and grapefruit. These are foundational SKUs for us, so I immediately initiated a Root Cause Analysis (RCA) to identify the issue.</p><p>The investigation centered on the juice press machine’s sanitation process. I interviewed several press operators, asking about their sanitation procedures, end-of-day routines, and even their phone usage during shifts. We discovered that the team was often rushing to finish their shifts and skipping the required sanitation wait times. On top of that, our sanitation SOP hadn’t been updated in over six years. We took quick action — updating the SOP, retraining staff, and limiting phone usage in the production box. Since then, shelf-life issues have significantly improved.</p><p>Misidentifying the root cause in a case like this could have serious consequences. For instance, if we had assumed the issue was with raw material quality instead, we might have spent unnecessary resources on supplier audits or changing fruit sources. Or worse, ignoring the real issue could have led to product recalls and damaged customer trust.</p><p>From this experience, I believe the most important transferable skills for RCA are critical thinking, active listening, and the ability to ask the right questions without jumping to conclusions. RCA is more than fixing a surface issue — it’s about tracing problems to their true source and implementing solutions that prevent them from recurring.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-23 08:27:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3377904755</guid>
      </item>
      <item>
         <title>Maria Barco (301263119)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3378316826</link>
         <description><![CDATA[<p><strong>RCA Experience:</strong></p><ul><li><p>During my Quality Assurance Technician Co-Op work term in a food company, I experienced an issue related to the flavor and quality of the product being made. For one of the products being processed daily at the company, the sauce used to coat this product showed an unusual bitter taste and darker colour than regular, which led to a change in the final product's taste and visual appearance that did not meet with the quality standards set for this specific product. Thereby, a<strong> Root Cause Analysis (RCA)</strong> investigation took place, with the QA team from the company, we checked how the processing employees were handling the sauce, if there was any deviation in the regular process during the mixing of the sauce for the batches of product, or if there was any difference in the sauce containers. After asking multiple employees and individually checking the taste, colour and viscosity of the sauce we were able to narrow down the quality issue of the sauce into one specific lot. This lot was separated and new SOPs were implemented for the employees to do a quick quality check of every new lot of sauce used to avoid any further similar issue. Also, the sauce presenting these defects was returned to the supplier and they were&nbsp; advised to inform our company why this lot presented this quality issue. The suppliers did their part and sent out a new lot of sauce presenting the usual quality along with proper explanations of the root of the issue and with the corrective actions they implemented in their facility to detect this deviation effectively.&nbsp;</p></li></ul><p><strong>Effects of wrong RCA being identified in a company:</strong></p><ol><li><p><strong>Wrong implementation of resources</strong> in solving an issue that would not completely fix the original issue and would most likely work temporarily but not for the long run. Wasting time, money and labour.</p></li><li><p><strong>Reputation of the company - the customers of the company would most likely gain distrust with the company practices if there is a recurring issue that is not being addressed well. Leading to the company’s reputation being hindered along with a loss in business opportunities and relationships.&nbsp;</strong></p></li></ol><p><br></p><p><strong>Transferable skills essential for individuals conducting RCA’s:</strong></p><ul><li><p>I consider that skills such as <strong>critical thinking </strong>and <strong>problem solving</strong> are mainly useful for any employee, manager, supervisor, among others, to conduct a proper RCA. Being able to analyze in depth all the factors involved in the cause of an issue by asking adequate questions with the help of the <strong>5 Whys</strong> or by making a <strong>Fishbone diagram</strong> is fundamental to identify patterns of the issue and know how and where to start addressing it. However, skills such as: <strong>attention to detail, decision-making</strong> and<strong> communication</strong> skills are also key to conduct effective RCAs in any industry.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-23 21:08:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3378316826</guid>
      </item>
      <item>
         <title>Charmy Patel (301386106)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3378637549</link>
         <description><![CDATA[<p><strong>My RCA Reflection </strong></p><p>While working as a pharmacist at a pharmacy in India, I noticed that our physical inventory wasn’t matching the digital stock records. This was a serious concern because it could affect both inventory control and patient service. I reported the issue to my supervisor, and together we began a Root Cause Analysis. After checking stock logs and contacting the software company, we discovered the issue: a newly hired pharmacy assistant had been entering new stock without updating the quantity field in the system. As a result, only one item was logged instead of two, creating ongoing discrepancies. The situation was resolved through retraining and closer supervision of data entry.</p><p><br></p><p>If the wrong root cause had been identified, such as blaming a software glitch or even suspecting theft, it could have led to poor decisions. For example, unnecessary software updates or disciplinary actions might have wasted resources and damaged team morale. Misidentifying the cause could also leave the real issue unresolved, allowing inventory errors to continue and potentially affect medication availability for patients.</p><p><br></p><p>For those conducting RCA investigations regularly, I think some of the most important transferable skills include <strong>attention to detail</strong>, since even small errors can have big impacts, and <strong>strong communication</strong>, as gathering accurate information and collaborating with others is key to finding the real root cause. Patience and critical thinking also play a big role in making sure no step is overlooked.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-24 02:15:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3378637549</guid>
      </item>
      <item>
         <title>Coleen Mae Dumol (301335303)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3378740148</link>
         <description><![CDATA[<p><strong>Unexpected Machine Failure: A Root Cause Analysis Experience</strong></p><p><br/></p><p>It was a busy morning in the lab, and I was in the middle of running a batch of critical patient samples through the hematology analyzer. Everything seemed routine, until suddenly, the machine stopped mid-run, flashing an error code I had never seen before.</p><p><br/></p><p><strong>Step 1: Identifying the Problem</strong></p><p>At first, I assumed it was a minor issue—a simple jam or a temporary sensor glitch. But after restarting the machine, the same error reappeared. My supervisor, noticing my frustration, came over, and we both realized this wasn’t a quick fix. The analyzer was one of the only functional units that day, meaning any delay could impact patient diagnoses.</p><p><br/></p><p><strong>Step 2: Investigating Possible Causes</strong></p><p>Since I had worked with this analyzer for a while, I knew the usual suspects:<br>✅ Reagents &amp; Consumables: I checked reagent levels and replaced the sample probe, but the error persisted.<br>✅ Mechanical Issues: I ran a manual cleaning cycle to rule out clogs—still no luck.<br>✅ Software or Calibration Problems: A quick check of the system logs showed no failed calibrations or overdue maintenance.</p><p>At this point, my supervisor suggested we escalate the issue to technical support while continuing our investigation.</p><p><br/></p><p><strong>Step 3: Finding the Root Cause</strong></p><p>After speaking with the manufacturer’s support team, we discovered that the issue was due to a faulty internal temperature sensor. The machine had misread the internal temperature as too high, causing an automatic safety shutdown. This was something I wouldn’t have thought of on my own!</p><p><br/></p><p><strong>Step 4: Preventing Future Issues</strong></p><p>The solution involved replacing the sensor, but we also made preventative changes:<br>🔹 Added a daily sensor check to our maintenance routine<br>🔹 Implemented a troubleshooting guide for similar errors<br>🔹 Ensured we had a backup analyzer available at all times</p><p>Lessons Learned &amp; Transferable Skills</p><p>This experience showed me how important problem-solving and teamwork are in RCA.<br>🔹 Critical Thinking – I had to systematically eliminate possible causes.<br>🔹 Attention to Detail – Small details, like an internal sensor, can have big impacts.<br>🔹 Communication – Working with my supervisor and the manufacturer’s team helped us resolve the issue quickly.</p><p>The Impact of Identifying the Wrong Root Cause</p><p>Had we assumed the issue was just a clogged sample probe, we might have wasted time replacing parts unnecessarily or delaying urgent samples. In a medical setting, a misdiagnosed machine failure could lead to:<br>1️⃣ Delayed Patient Care – Doctors relying on test results might not get them in time.<br>2️⃣ Increased Costs – Ordering unnecessary repairs or even replacing the entire machine when only a small part needed fixing.</p><p><br/></p><p>This experience reinforced that a structured approach to RCA is crucial in any industry, not just healthcare. Whether investigating a machine failure or a missing snack from the fridge, the key is to ask the right questions and not jump to conclusions!</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-24 03:16:11 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3378740148</guid>
      </item>
      <item>
         <title>Khushbu Patel(301380216)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3378743026</link>
         <description><![CDATA[<p><strong>RCA experience:</strong></p><p>I participated in a Root Cause Analysis (RCA) while I was a trainee at Bosonic Nutraceutical Company in response to consumer concerns regarding the strength of our vitamin supplements. We initially thought that the manufacturing machinery was broken, but after more research, we found that the potency problems were caused by lower-than-expected purity in the raw materials that were provided to us. A careful examination of supplier communications and batch data allowed for the identification of this main cause.</p><p>If we had mistaken the underlying cause, we might have kept wasting time and money trying to fix equipment that wasn't the problem. Additional customer unhappiness and possible financial losses could have resulted from this. We were able to collaborate with the supplier to enhance the quality of the raw material by determining the true cause, which helped avert further complaints and guaranteed product consistency.</p><p>I learned the value of thorough data analysis and efficient team communication from this experience. It also reaffirmed the importance of an organized method of problem-solving, which is crucial for anyone who frequently performs RCAs. Critical thinking, teamwork, and attention to detail are all essential for RCA inquiry success.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-24 03:17:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3378743026</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3380621087</link>
         <description><![CDATA[<p>Athul Sakthi( 301346945)</p><p>At one point, our pizzeria started receiving multiple customer complaints about pizzas being undercooked in the center. Initially, the team assumed it was a problem with the dough recipe, and we tried adjusting the hydration levels. However, the issue persisted.</p><p>Using RCA, I broke down the process and checked each factor:<br> .Oven temperature and cooking time<br> .Dough preparation and thickness<br> .Placement of pizzas in the oven</p><p>After testing, we discovered that a faulty oven heating element was causing uneven heat distribution. The center of the pizza wasn’t getting enough direct heat, leading to undercooked dough. Once we repaired the heating element, the problem was resolved, and pizzas were consistently baked to perfection.</p><p><br/></p><p>If we had identified the wrong root cause, it could have negatively impacted the business in two ways:</p><p>Increased Waste &amp; Costs – If we had continued tweaking the dough recipe unnecessarily, we would have wasted ingredients and time, without actually fixing the problem.</p><p>Loss of Customer Trust – Customers expect high-quality pizza every time. If the issue persisted, repeat customers might stop ordering, and bad reviews could hurt the restaurant’s reputation.</p><p>People who perform RCA regularly need:</p><p>Attention to Detail – Identifying small changes, like slight temperature variations in an oven, can make a big difference.<br>Critical Thinking – Evaluating multiple potential causes before jumping to conclusions.<br><strong> </strong>Communication Skills – RCA often involves discussing issues with coworkers to gather insights and prevent future mistakes.</p><p>For example, another time, I had to investigate why pizza dough was rising inconsistently. By going step by step, I found that one batch of yeast had expired, causing weak fermentation. This showed me how important it is to check ingredient freshness regularly.</p><p>RCA isn’t just for high-tech industries—it’s useful in any job, even as a pizza chef! By finding the real cause of a problem, businesses can improve efficiency, maintain quality, and keep customers happy</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-25 03:07:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3380621087</guid>
      </item>
      <item>
         <title>Aldywn Danielle Daya 301375802</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3387071413</link>
         <description><![CDATA[<p>I participated in a Root Cause Analysis (RCA) investigation in a laboratory setting after repeated calibration failures. Using the 5 Why technique, we traced the issue back to inconsistent cleaning of calibration tools—something initially overlooked in favor of equipment malfunction. This led to updated SOPs and retraining, ultimately improving the reliability of the process and preventing future issues.</p><p>Identifying the wrong root cause can seriously impact a company. For example, if recurring delays are wrongly blamed on staff error instead of aging equipment, the problem will persist. Similarly, implementing the wrong corrective action—like retraining staff instead of fixing a process flaw—can waste resources and lower employee morale.</p><p>To conduct RCAs effectively, key transferable skills include critical thinking to dig beyond surface issues, strong communication to gather accurate information across teams, and attention to detail to catch small but important clues. These skills help ensure the root cause is accurately identified and addressed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-28 18:33:15 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3387071413</guid>
      </item>
      <item>
         <title>Mansi Darji (301401508)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3387181280</link>
         <description><![CDATA[<p>In my previous job role in the QC department, I have participated in several Root Cause Analysis (RCA) investigations, particularly related to HPLC analysis. One example involved inconsistencies in peak retention times for impurities during a routine HPLC test of a drug product. After conducting a thorough investigation, we identified that the mobile phase solvent preparation was incorrect, causing variations in the results. By correcting the solvent preparation process, we were able to resolve the issue and ensure accurate and reliable analysis in subsequent tests.</p><p>Identifying the wrong root cause in an RCA can have significant consequences. For example, if we had mistakenly blamed the sample preparation process instead of the mobile phase, the problem would have persisted, leading to unreliable HPLC results and potentially affecting product quality. Additionally, incorrect identification of the root cause can waste time and resources, such as unnecessary equipment replacements or labor on issues that do not resolve the actual problem. This not only increases costs but also prolongs the problem, impacting production timelines.</p><p>Key transferable skills for those conducting RCAs, especially in a QC environment, include strong analytical thinking, attention to detail, and effective collaboration. In HPLC analysis, understanding data patterns and pinpointing discrepancies in chromatograms are crucial for identifying the root cause. Communication skills are essential when working with cross-functional teams to gather all relevant information. Problem-solving abilities are necessary to develop appropriate corrective actions once the root cause is identified, and time management ensures that RCA investigations are completed efficiently without compromising quality.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-28 21:45:48 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3387181280</guid>
      </item>
      <item>
         <title>Reyna Elaine Isidro</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3387317241</link>
         <description><![CDATA[<p><strong>Problem:</strong></p><p>Patient A's medications were encoded in patient B's record.</p><p><br/></p><p><strong>RCA Investigation:</strong></p><p>We  investigated and found out that their names were switched, and it was his brother's (patient B) name instead of patient A's name.</p><p><br/></p><p><strong>How did it happen?</strong></p><p><strong>One of the key factors that led to this incident was poor communication.</strong> The encoder might have been confused since the patients were twins and had almost identical and rhyming names. This highlights the need for improved communication protocols to prevent such errors in the future.</p><p><strong>Environmental Factor: </strong>Since it was a busy day, many patients entered the pharmacy, which added to the encoder's confusion.</p><p><br/></p><p><strong>Solution:</strong></p><ul><li><p>Verify the identity of the patient by asking for a valid ID.</p></li><li><p>sort and fix the records so as not to mix the medications</p></li><li><p>Confirm the patient's date of birth and name before submitting the encoded medications.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-29 04:01:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3387317241</guid>
      </item>
      <item>
         <title>The Importance of Identifying the Right Root Cause: A Lesson from the Lab - Harsimran Kaur 301293939</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3387724711</link>
         <description><![CDATA[<p>It was a typical Monday morning when our lab received a customer complaint about a recurring issue in one of our products. The defect was subtle but significant—something was causing an unexpected degradation in product quality over time. Given the potential regulatory implications, we immediately launched a <strong>Root Cause Analysis (RCA)</strong> to determine what went wrong.</p><p>Our cross-functional team, consisting of quality engineers, manufacturing specialists, and scientists, gathered in a conference room. We applied the <strong>5 Whys method</strong>, systematically working backward from the defect to uncover its origin. Initially, it seemed like a <strong>contamination issue</strong>—perhaps a raw material batch was compromised. We conducted a full material traceability review and found nothing unusual.</p><p>Then, we considered <strong>equipment failure</strong>. We checked calibration logs, maintenance records, and operator notes—everything was in spec. The process parameters hadn’t changed. Frustration was growing, and pressure from upper management mounted to resolve the issue quickly.</p><p>Finally, one of my colleagues suggested looking into <strong>storage conditions</strong>. That wasn’t the most obvious cause, but as we reviewed historical temperature and humidity data, we found subtle fluctuations that exceeded ideal conditions for short periods during transportation. Further testing confirmed that these fluctuations were enough to accelerate product degradation.</p><p>Had we stopped at the first assumption (contamination), the company could have taken <strong>incorrect corrective actions</strong>, such as rejecting a perfectly good batch of raw materials, leading to unnecessary costs and production delays. Worse, if the problem persisted, it could have damaged customer trust and even led to regulatory scrutiny.</p><p>This experience reinforced a key lesson: <strong>Rushing to identify a root cause without thorough investigation can have serious consequences.</strong> A proper RCA requires critical thinking, teamwork, and persistence—without these, companies risk treating symptoms instead of solving the actual problem.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-29 22:42:08 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3387724711</guid>
      </item>
      <item>
         <title>Alexandrea Joyce Martin (301381036)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3387759062</link>
         <description><![CDATA[<p>When I was working in a hospital laboratory, I encountered an issue with one of the machines while running quality control. The control results were consistently out of range despite multiple re-runs. Initially, I suspected a reagent issue, but after further investigation and consulting with the technician, we discovered that the system had an incorrect reference range input. The root cause was a discrepancy in the configured range, which required updating to match the correct values. Once corrected, the control results fell within the expected range, ensuring accurate patient testing.</p><p>Their are impacts  for wrong RCA, First, Continued Operational Issues: If the wrong root cause is identified, the actual problem remains unresolved, leading to repeated errors. For example, in a laboratory setting, misidentifying the cause of out-of-range quality control results could result in continued reporting of incorrect patient results, compromising patient safety. Second, Unnecessary Costs and Wasted Resources: Addressing an incorrect root cause can lead to wasted time, effort, and financial resources. For instance, replacing an entire instrument when the real issue is a calibration error would result in unnecessary expenses without resolving the underlying problem.</p><p>The transferable skills that most important are: Analytical Thinking: The ability to systematically assess a problem, identify potential causes, and evaluate evidence is crucial for accurate root cause identification. Attention to Detail: Small discrepancies, such as incorrect reference ranges or minor calibration errors, can have significant impacts. A keen eye for detail ensures that such issues are caught early. Communication and Collaboration: RCA often involves consulting with different stakeholders, such as technicians, engineers, or quality assurance teams. Clear communication ensures that information is accurately conveyed and solutions are effectively implemented. Problem-Solving Skills: The ability to think critically and develop corrective actions prevents recurrence of the issue and improves overall system reliability.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-30 01:13:07 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3387759062</guid>
      </item>
      <item>
         <title>Elyssa Gargallano (301259955)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3388618523</link>
         <description><![CDATA[<p>During our Project 2 experiment, we were attempting to cultivate <em>Lactobacillus plantarum </em>for growth and metabolic activity experiments. However, after several attempts, the bacteria consistently did not grow at all or at the minimum required density even in our controls. This was a critical setback, as our experiments relied on it as our organism of interest. My partner and I then systematically investigated what might have caused this.  We started by meticulously reviewing the growth requirements, including media preparation, incubation parameters, and inoculation techniques. We then examined the equipment used, such as the incubator and spectrophotometer to rule out any malfunctions. Through the right questions, careful observation, and data analysis, we discovered that the MSG we added in the media interfered with the bacteria's growth. The MSG was originally added as a substrate for GABA utilization measurement in preparation for the metabolic activity experiment and ensure that the project would finish in time. This was confirmed when a batch of media without the MSG was incubated and growth was observed. The root cause was identified as a media preparation error, leading to less than optimal growth conditions, and consequently failed bacterial growth.</p><p><br/></p><p>If we had misidentified the root cause, the consequences could have been significant. For instance, if we incorrectly assumed incubation conditions, we might have wasted time and resources adjusting to different incubation environments without getting substantial information on what went wrong and failed to address the media problem. If we suspected a faulty bacterial strain, we might have discarded a viable culture and delayed our experiments. This highlights the importance of rigorous process review, meticulous equipment checks, and a systematic approach to troubleshooting in a lab setting, especially when dealing with sensitive biological processes.</p><p><br/></p><p>When dealing with these situations, it is important that the individual possesses transferable skills such as critical thinking and problem solving as well as communication and collaboration. The ability to understand the process and analytically identify the root cause through the process of deduction and critical evaluation is essential to provide an appropriate solution to the problem at hand. Moreover, it is crucial that the individual also possesses communication and collaboration skills so that they are able to efficiently and effectively gather information, facilitate discussions and brainstorming sessions, and convey findings clearly so that the issue can be resolved appropriately.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-31 03:48:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3388618523</guid>
      </item>
      <item>
         <title>Thilakshan Sandrasekaran (301377623)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3389486330</link>
         <description><![CDATA[<p>During one of my shifts at the lab, I was involved in a Root Cause Analysis (RCA) investigation when we noticed that our testing equipment was producing inconsistent results. The lab team and I gathered data, reviewed equipment logs, and conducted interviews with technicians who used the machine. After careful analysis, we identified that the issue wasn't with the software, as we initially suspected, but rather with a faulty calibration mechanism that had gone unnoticed during regular maintenance. Had we focused on the software glitch, we could have wasted time troubleshooting code, leading to delays and missed deadlines. The real issue might have continued to cause inaccurate results, affecting our overall research accuracy. I believe that attention to detail, problem-solving, and clear communication are essential skills when conducting RCAs. These skills ensure that the problem is understood correctly, the team stays aligned, and corrective actions are effectively implemented.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-31 15:15:16 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3389486330</guid>
      </item>
      <item>
         <title>Hafsa Shaikh (301415918)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3389614199</link>
         <description><![CDATA[<p>One day, I participated in root cause analysis. I am cashier and I observed that many customers were not satisfying with prices and they were returning items. So, I was worried about what was the reasons behind this. I also talked with my supervisor about this issues. I spoke with customers and I got information that there was different price tag and in system there was different prices. So, I thought that why and what was the reasons. For getting root , I visited the each spot and I took items and scanned ,and I found some different prices. For getting solution , I spoke with workers who were doing facing items and managing price tags. After speaking with them I got information that in my company there is rule to change price of all products every year. while applying this rule, they forgot to change some price tags and removed old tags. I told them removed old tags and placed new tags. After doing this , now customers are satisfying with prices.</p><p>If I did not involve in this situation, so customers are returning items  continuously. As a result, company is facing loss in selling items and it affects company's profit and reputations. </p><p>I think that it is good experience and I believe that RCA is playing most importance part in any failed situation.</p><p>Thank you.</p><p><br/></p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-03-31 16:57:47 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3389614199</guid>
      </item>
      <item>
         <title>Sruthi Sapare (301376857)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3389919420</link>
         <description><![CDATA[<p><strong>My Experience with a Root Cause Analysis (RCA) at Home</strong></p><p>Hi classmates,</p><p>I want to share a personal story about a Root Cause Analysis (RCA) I did in my everyday life — nothing too formal, but it definitely taught me how RCA works even outside of a professional setting.</p><p><strong><mark>The Case of the Disappearing Cheesecake</mark></strong></p><p>A few months ago, I was living with three roommates. One Friday night, I bought myself a slice of cheesecake from my favorite bakery and put it in the fridge with my name clearly written on the container. I was saving it for Saturday after work you know, as a reward for surviving the week. </p><p>But when I came home the next evening… it was<strong> </strong>gone.</p><p>At first, I was just annoyed. But then I thought — okay, let’s treat this like a little investigation. I decided to dig into it like a Root Cause Analysis (RCA).</p><p><strong>How I Investigated It (Like an RCA)</strong></p><p>I asked each of my roommates if they’d seen the cheesecake. All of them denied touching it. But I noticed one of them (I'll call him R) seemed really nervous and avoided eye contact.</p><p>So I started asking questions like:</p><ul><li><p>"Did anyone move it to make space in the fridge?"</p></li><li><p>"Did anyone throw something out yesterday?"</p></li><li><p>I even checked the sink and found a spoon with cheesecake residue. </p></li></ul><p>Eventually, R admitted that he ate it, thinking it was his — even though my name was on it! He said he didn’t even look at the label.</p><p><strong>Root Cause Identified: Lack of Communication and Clear Shared Rules</strong></p><p>We realized we never really discussed rules about labeling or respecting each other's food. So the real issue wasn’t just R being careless — it was that we had <strong>no </strong>system in place. That’s the root cause.</p><p>We fixed it by creating a simple house rule:<br>1) If it’s not yours and it has a name on it, don’t touch it.</p><p>2)If you’re not sure, ask before eating.</p><p><strong>Why the Right Root Cause Matters</strong></p><p>If I had just blamed R and left it at that, the same issue might’ve happened again —maybe with someone else’s food. By finding the real reason (no house rules), we were able to <strong>prevent it from happening </strong>again. That’s the power of identifying the correct root cause, it leads to real, lasting solutions.</p><p><strong>Transferable Skills I Used:</strong></p><ol><li><p><strong>Critical Thinking</strong> – Asking questions, observing behavior, connecting clues.</p></li><li><p><strong>Communication</strong> – Talking with others calmly, without starting a fight.</p></li><li><p><strong>Problem-solving</strong> – Finding a solution everyone could agree to.</p></li></ol><p>These are all skills that can be used not just at home, but in any job where RCA is required.</p><p>This may have started as a "cheesecake mystery," but it taught me that investigations — big or small — follow the same logic. Ask the right questions, observe carefully, and solve the <strong>real</strong> issue, not just the surface one.</p><p>Thanks for reading!</p><p><br/></p><p><br></p>]]></description>
         <enclosure url="https://live.staticflickr.com/2152/2219761405_3d764749fe_b.jpg" />
         <pubDate>2025-03-31 22:49:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3389919420</guid>
      </item>
      <item>
         <title>Peiyi Xian (301328610)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3390345414</link>
         <description><![CDATA[<p><strong>My RCA experience in a chemistry experiment in middle school</strong></p><p><br/></p><p>It happened when I was in middle school, my groupmate and I were conducting a standard heat reaction with potassium permanganate (KMnO4) to observe its decomposition in a chemistry lab. The goal was to heat the KMnO4 in a big, tilted test tube, which would decompose and release oxygen and bring the embers in the attached tube back to life. However, during the experiment, something unusual occurred: when we applied heat, the KMnO4 powder in the test tube suddenly ignited with a visible flame. Luckily, by swiftly removing the heat source, the flame was extinguished quickly, and no injuries occurred. </p><p><br/></p><p>After reported to the instructor and some closer investigation, I found that the cause of the problem was not the reaction itself, but a storage error: The glass bottle containing the KMnO4 powder still had a label named "carbon powder", which means this container used to store carbon powder. Carbon, when heated in an oxygen-rich environment, can undergo an exothermic reaction, igniting and producing flames. The oxygen released during the decomposition of KMnO4 likely accelerated the oxidation of the carbon powder, causing the combustion. Once the mistake was discovered, it became clear that the residual carbon powder had led to a highly reactive situation, turning a routine experiment into an unanticipated hazard.</p><p><br/></p><p>The root cause of the incident was traced back to the improper storage of different chemicals in the same container without cleaning. Following the incident, the lab instituted stricter procedures for chemical labeling and verification to prevent similar mishaps, ensuring that safety protocols were always followed and reducing the risk of future accidents.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-01 04:13:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3390345414</guid>
      </item>
      <item>
         <title>BINNY PAULSON 30145630</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3395277177</link>
         <description><![CDATA[<p>Back when I was working as a cashier, I had a situation where my manager asked me to help figure out why our cash register was short by a significant amount at the end of multiple shifts. At first, I thought it was just a miscount or a simple mistake, but after reviewing the records, the issue kept happening over and over again.</p><p>To investigate, I started by double-checking my own cash handling to make sure I wasn’t making mistakes. Then, I noticed that a few other cashiers also had shortages. We reviewed the security footage and found that one of the self-checkout registers had a glitch where it wasn’t registering some transactions properly, particularly when customers used gift cards. Instead of stealing or human error, the actual problem was a technical issue in the system.</p><p>The fix? The management team reported the issue to IT, and in the meantime, we manually cross-checked gift card transactions to prevent further losses.</p><p><br/></p><p>From this experience, I realized that people who conduct RCA regularly need:</p><ul><li><p><strong>Problem-Solving Skills</strong> – It’s important to approach an issue logically and not jump to conclusions too quickly.</p></li><li><p><strong>Observation Skills</strong> – Paying attention to patterns and details can help uncover the real issue.</p></li><li><p><strong>Teamwork and Communication</strong> – Since I had to talk with managers, IT staff, and other cashiers, it showed me how crucial it is to work together to solve problems.</p></li></ul><p>This experience made me realize that investigations don’t always mean something suspicious—sometimes, they’re just about finding small technical issues before they turn into big problems!</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-04 01:24:48 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3395277177</guid>
      </item>
      <item>
         <title>My RCA experience</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3396516921</link>
         <description><![CDATA[<p>Tanvi Panchal (301380569)</p><p>During my time working in a lab, I was asked to help with an investigation into why our cultures were frequently showing signs of microbial contamination, even though we followed all standard sterile procedures. At first, it seemed like a small issue, but as it persisted, the team became more concerned, as the contamination was affecting our results.</p><p>We decided to perform a Root Cause Analysis (RCA) to identify the source of the contamination. We started by collecting data on the conditions under which the contamination occurred. I reviewed the procedures we followed, the equipment we used, and even the environment where we stored our cultures. We also interviewed lab personnel to see if there had been any deviations from protocols.</p><p>The first thing we noticed was that contamination was most common with samples that were left out for extended periods during the day. This led us to suspect that it might be an issue with the environment or equipment. We checked the autoclave and sterilization techniques, but everything seemed in order. However, when we examined the air filtration system, we found that it wasn’t functioning properly, and the lab wasn’t as sterile as it should have been.</p><p>Upon further investigation, we realized that the root cause of the contamination was actually the malfunctioning air filtration system. It had been allowing airborne microbes to enter the lab during open work periods, which explained the persistent contamination in certain cultures.</p><p>Once we identified this root cause, we immediately had the air filtration system repaired. After that, the contamination issue was resolved, and our cultures remained sterile, allowing us to continue our work without any issues.</p><p>Looking back, I learned that RCA isn’t just about finding problems, but about questioning everything,even the things you think are already in place and functioning well. The wrong root cause could have led to wasted time on other potential issues, like the sterilization process or contamination during sample handling. This experience taught me the value of thorough investigation and the importance of looking at every part of the process to find the real cause.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-04 21:18:56 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3396516921</guid>
      </item>
      <item>
         <title>Yashkumar Patel   301414247</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3399267524</link>
         <description><![CDATA[<p><strong>Root Cause Analysis (RCA) Reflection as a Lab Assistant</strong></p><p><strong>Event:</strong><br>As a Lab Assistant, I was tasked with investigating repeated failures in DNA extraction experiments, despite using high-quality reagents.</p><p><strong>RCA Investigation:</strong></p><ul><li><p><strong>Why were the experiments failing?</strong><br>The results were inconsistent.</p></li><li><p><strong>Why were the results inconsistent?</strong><br>A crucial step in the protocol was skipped, leading to incorrect buffer preparation.</p></li><li><p><strong>Why was the step skipped?</strong><br>The team was rushing and didn’t double-check the procedure.</p></li><li><p><strong>Why were they rushing?</strong><br>Due to poor time management and lack of attention to detail.</p></li></ul><p><strong>Root Cause:</strong><br>The root cause was not following the protocol properly, caused by poor time management and rushing through the process.</p><p><strong>Resolution:</strong><br>We corrected the buffer preparation, emphasized strict adherence to the protocol, and focused on better time management.</p><p><strong>Outcome:</strong><br>The experiments were successful after these changes. This experience taught me the importance of addressing root causes and thoroughly investigating issues to prevent future problems.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-07 17:55:45 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3399267524</guid>
      </item>
      <item>
         <title>Krishna Babariya 301428675</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3399274129</link>
         <description><![CDATA[<p><strong>Root Cause Analysis (RCA) Reflection as a Lab Assistant</strong></p><p><strong>Event:</strong><br>As a Lab Assistant, we faced repeated failures in DNA extraction experiments, despite using high-quality reagents. I was asked to investigate the issue.</p><p><strong>RCA Investigation:</strong></p><ul><li><p><strong>Q1: Why were the experiments failing?</strong><br><strong>A1:</strong> Because the results were inconsistent.</p></li><li><p><strong>Q2: Why were the results inconsistent?</strong><br><strong>A2:</strong> Because a crucial step in the protocol was skipped, leading to incorrect buffer preparation.</p></li><li><p><strong>Q3: Why was the step skipped?</strong><br><strong>A3:</strong> The team was rushing and didn’t double-check the procedure.</p></li><li><p><strong>Q4: Why were they rushing?</strong><br><strong>A4:</strong> Due to poor time management and lack of attention to detail.</p></li></ul><p><strong>Root Cause:</strong><br>The root cause was not following the protocol due to poor time management and rushing through the process.</p><p><strong>Resolution:</strong><br>We corrected the buffer preparation, emphasized protocol adherence, and improved time management.</p><p><strong>Outcome:</strong><br>The experiments were successful after these changes, and the experience taught me the importance of addressing root causes and thoroughly investigating issues to prevent future problems.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-07 18:00:31 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3399274129</guid>
      </item>
      <item>
         <title>Sidney Marrie Lee Leong 301383106</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3399278318</link>
         <description><![CDATA[<p><strong>Root Cause Analysis (RCA) Reflection – Walk-in Retail Pharmacy Store (Philippines)</strong></p><p><strong>Event:</strong><br>While working in a walk-in retail pharmacy store in the Philippines, a customer complained that her maintenance medication, which she claimed to have reserved over the phone earlier that day, was not set aside. The stock had run low by the time she arrived.</p><p><strong>RCA Investigation:</strong></p><p><strong>Q1: Why wasn’t the medicine reserved?</strong><br><strong>A1:</strong> Because there was no record of the reservation in the logbook or on the shelf.</p><p><strong>Q2: Why was there no record?</strong><br><strong>A2:</strong> The staff who received the call forgot to log the reservation.</p><p><strong>Q3: Why did the staff forget to log it?</strong><br><strong>A3:</strong> Because there was no formal system in place to track phone reservations.</p><p><strong>Q4: Why was there no system?</strong><br><strong>A4:</strong> Because phone reservations were not consistently managed or monitored.</p><p><strong>Root Cause:</strong><br>Lack of a proper system to track and confirm phone reservations led to missed or forgotten orders.</p><p><strong>Resolution:</strong><br>We introduced a simple reservation tracking system using a logbook with reservation slip numbers, and attached labels to reserved medicines to ensure visibility and accountability.</p><p><strong>Outcome:</strong><br>The new system prevented missed reservations, improved customer satisfaction, and helped build trust. This experience taught me that even small process gaps can have a big impact, and that solving the root cause helps prevent repeat issues in a busy retail setting.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-07 18:03:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3399278318</guid>
      </item>
      <item>
         <title>Amrin Rangrez - 301343052</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3399574957</link>
         <description><![CDATA[<p><strong>Event:</strong> A researcher was stuck with a needle containing a potentially pathogenic organism, requiring antibiotics.</p><p><strong>RCA Steps:</strong></p><ol><li><p><strong>Q:</strong> Why did the researcher get stuck with a needle?<br><strong>A:</strong> The researcher wasn’t familiar with using the device.</p></li><li><p><strong>Q:</strong> Why wasn’t the researcher familiar with it?<br><strong>A:</strong> The researcher normally used a pipette, but it wasn’t available.</p></li><li><p><strong>Q:</strong> Why wasn’t the pipette available?<br><strong>A:</strong> It was broken and not replaced.</p></li><li><p><strong>Q:</strong> Why wasn’t it replaced?<br><strong>A:</strong> The lab manager didn’t know it was broken.</p></li><li><p><strong>Q:</strong> Why didn’t the manager know?<br><strong>A:</strong> The lab had no system to track equipment.</p></li></ol><p><strong>Root Cause:</strong> The lab lacked an equipment tracking system, which led to the broken pipette not being replaced.</p><p><strong>Reflection:</strong> This analysis shows how a simple event can reveal deeper issues. By identifying and addressing the root cause lack of equipment tracking future incidents can be prevented.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-07 23:41:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3399574957</guid>
      </item>
      <item>
         <title>Harshini Rao-301355660</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3406700594</link>
         <description><![CDATA[<p>At work, I participated in a Root Cause Analysis (RCA) after a piece of equipment repeatedly breaking down, leading to delays. We initially believed that the power supply was the problem, but after conducting additional research and applying techniques such as the Five Whys, we found that the true cause was a lack of routine maintenance. Parts of the equipment were wearing out too soon because it wasn't getting enough maintenance.<br><br>We would have wasted money changing things that weren't the problem if we had misinterpreted the issue, for example, by concentrating on the power supply. The issue would have persisted, resulting in time wastage and frustration. I learned from this experience how crucial it is to determine the accurate underlying reason.<br><br><br>Additionally, it emphasized the importance of critical thinking, effective communication, and patience as RCA abilities. Finding a rapid cure isn't the only goal of root cause analysis (RCA); it also aims to fully comprehend the issue and address its root cause.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-11 22:25:00 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3406700594</guid>
      </item>
      <item>
         <title>Yujin Kim</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3407361366</link>
         <description><![CDATA[<p>While working at a vaccination center, our team often struggled with staying on schedule. Although we had enough staff and supplies, long wait times were common, and it affected both visitor satisfaction and staff performance.</p><p>To understand the issue, we used a Root Cause Analysis approach by repeatedly asking “why” to uncover the real problem.</p><p>First, why were there delays? We noticed backups were happening after registration.</p><p>Why was that? The vaccination team was receiving too many people at once.</p><p>Why were they being sent all at once? Because the registration staff had no way of knowing how busy the vaccination area was.</p><p>Why was there no coordination? There was<strong> </strong>no communication system between the two teams.</p><p>This led us to the root cause: a lack of a structured communication protocol between the registration and vaccination stations. It wasn’t just a people problem—it was a system issue.</p><p>As a solution, we introduced a simple real-time coordination system using a tracking sheet and appointed one staff member to oversee patient flow. This helped balance the workload between stations and significantly reduced wait times.</p><p>This experience helped me understand how RCA goes beyond identifying symptoms—it helps reveal the underlying cause. By working step by step, we found a sustainable solution instead of just reacting to surface-level issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-12 23:03:40 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3407361366</guid>
      </item>
      <item>
         <title>Priyanshu Sharma (301349112)  My RCA experience</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3407821675</link>
         <description><![CDATA[<p>In a previous lab setting, I participated in a Root Cause Analysis (RCA) after we observed inconsistent results during a routine quality control test. Initially, we suspected user error, but through a structured RCA process—including reviewing documentation, equipment logs, and interviewing staff—we discovered the actual root cause was improper storage conditions that affected reagent stability. Identifying the wrong root cause in such investigations can significantly impact a company; for example, it can lead to repeated failures and wasted resources if the real issue remains unresolved, or result in regulatory non-compliance, especially in highly regulated industries, potentially leading to fines or product recalls. To conduct RCAs effectively, transferable skills such as critical thinking, strong communication, attention to detail, and the ability to work collaboratively are essential, as they help ensure thorough investigations and the implementation of sustainable corrective actions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-13 17:05:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3407821675</guid>
      </item>
      <item>
         <title>Pragya Sapkota (301377629)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3407853826</link>
         <description><![CDATA[<p>For the Root Cause Analysis experience, I would like to recall my project on phage characterization against Pseudomonas aeruginosa during my master's. I encountered an issue during the pH sensitivity assessment where the phage failed to lyse the bacterial host even under standard temperature and pH conditions. No plaques were formed, and I noticed an unusual change in the bacterial lawn: the typical green pigmentation of P. aeruginosa turned whitish, raising concerns about possible contamination.</p><p>To troubleshoot, I repeated the experiment using fresh media, adjusted the incubation condition, and ensured I used a log phase host and proper concentration of phage stocks. Despite this, lysis still did not occur. I then performed a spot assay using freshly streaked bacteria from my lyophilized stock cultures. This time, clear plaques were formed, confirming successful lysis. The root cause was identified as contamination or degradation of the original bacterial stock. This might have happened due to improper aseptic handling or repeated use of stock culture making it non-viable or incompatible with the phage.</p><p>Misidentifying the root cause can lead to wasted resources and delays. In our case, if I had blamed pH or temperature instead of contaminated bacterial stock, I might have discarded a good phage and lost valuable time as I had to repeat the whole project. This type of error might have impacted my project quality and also my project deadline.</p><p>Key skills for effective RCA include critical thinking, attention to detail, problem solving capability and clear communication skills. These characteristics help to identify the real issue, and prevent similar problems in the future.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-13 18:03:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3407853826</guid>
      </item>
      <item>
         <title>Kavya Sharma (301413900)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409560800</link>
         <description><![CDATA[<p>Got it! Here's the revised version without mentioning PCR:</p><p>---</p><p>During a lab project focused on detecting <em>Listeria monocytogenes</em> in romaine and iceberg lettuce, we encountered inconsistent results during the detection process. We conducted a Root Cause Analysis using the 5 Whys method and discovered the issue was due to uneven sample homogenization, not contamination as we initially thought. By standardizing our blending process, we improved consistency across samples. Identifying the wrong root cause would have led to wasted resources and delayed progress. This experience emphasized the importance of critical thinking, clear communication, and attention to detail—key skills for anyone conducting RCA investigations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 20:28:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409560800</guid>
      </item>
      <item>
         <title>Krupa Kataria (301358853)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409615797</link>
         <description><![CDATA[<p><strong>Learning the Value of Identifying the Correct Root Cause: A Lab-Based Experience</strong></p><p>One Monday morning, our laboratory received a customer complaint regarding a recurring issue with one of our products. The defect was subtle yet impactful—it seemed to cause an unexpected decline in product quality over time. Recognizing the potential regulatory risks, we promptly initiated a Root Cause Analysis (RCA) to investigate the problem.</p><p>Our cross-functional team, composed of quality engineers, manufacturing experts, and scientists, gathered to tackle the issue. Using the 5 Whys method, we methodically traced the issue backward to identify its source. Initially, contamination appeared to be the most likely culprit, possibly linked to a compromised batch of raw materials. However, after a full traceability review, we found no anomalies.</p><p>Next, we turned our attention to equipment functionality. By examining calibration logs, maintenance records, and operator reports, we confirmed that all systems were operating within their specifications, and no process parameters had been altered. With no clear answers, frustration grew, and the urgency from upper management to find a resolution intensified.</p><p>Eventually, a team member suggested investigating storage conditions—a less obvious factor. Reviewing historical data on temperature and humidity during transportation revealed occasional fluctuations that exceeded the ideal conditions for the product. Subsequent testing confirmed that these variations were enough to accelerate product degradation.</p><p>Had we stopped at our initial hypothesis of contamination, the company might have taken unnecessary corrective measures, such as rejecting a perfectly good batch of raw materials. This misstep could have resulted in wasted resources and production delays. Even worse, if the true issue remained unresolved, customer trust might have been eroded, and regulatory complications could have arisen.</p><p>This experience underscored the importance of thorough investigation in RCAs. Rushing to conclusions without critical thinking, collaboration, and perseverance can lead to treating symptoms rather than addressing the root cause itself.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 21:51:54 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409615797</guid>
      </item>
      <item>
         <title>Arpitaben Chauhan (301398226)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409617884</link>
         <description><![CDATA[<p>During my time as a Production Supervisor and Quality Control lead in a plant tissue culture laboratory, I was involved in a Root Cause Analysis (RCA) investigation following a sudden spike in contamination across multiple culture batches. Despite strict aseptic practices, the issue was widespread and initially attributed to human error, with plans to retrain the entire team. However, I initiated a structured RCA using tools like the Fishbone Diagram and 5 Whys, analyzing potential causes across Environment, Methods, Materials, Machines, and People. This led to the discovery that autoclave validation logs had not been reviewed for weeks, and further inspection revealed a faulty temperature sensor causing incomplete sterilization. Had we accepted the initial assumption of personnel error, we would have wasted valuable time and resources while the real issue persisted, potentially compromising large volumes of product and damaging team morale.      How the wrong Root Cause can impact a company (2 examples):</p><ol><li><p><strong>Wasted Resources and Time</strong>: Acting on incorrect assumptions can lead to misdirected corrective actions. In our case, retraining staff would not have solved the real issue. Valuable time would have been lost, and contamination would continue—affecting production schedules and deliveries.</p></li><li><p><strong>Loss of Trust and Morale</strong>: Incorrectly blaming individuals without evidence can hurt team morale. In environments like plant tissue culture labs, where precision and teamwork are essential, trust is key. Repeated failures due to misdiagnosed issues also erode confidence in leadership and the QA process.             Transferable Skills Essential for RCA:</p><ol><li><p><strong>Critical Thinking and Attention to Detail</strong> – Not accepting the first visible cause as the final answer and questioning deeper.</p></li><li><p><strong>Communication Skills</strong> – Facilitating discussions with teams across production, QC, and maintenance without placing blame, focusing instead on collaboration.</p></li><li><p><strong>Documentation and Data Analysis</strong> – Accurately reviewing logs, SOPs, and equipment records to find hidden patterns.</p></li><li><p><strong>Decision-Making Under Pressure</strong> – Root cause investigations often happen under tight deadlines; staying calm and objective is vital.</p></li><li><p><strong>Understanding of Systems and Processes</strong> – A good RCA investigator must understand the technical flow and dependencies within the lab or facility.</p></li></ol></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 21:55:48 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409617884</guid>
      </item>
      <item>
         <title>Jahanvi Mavani (301396669)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409618197</link>
         <description><![CDATA[<p><strong>Experience with a Root Cause Analysis (RCA) Investigation</strong></p><p>During my time in the microbiology lab, I participated in a Root Cause Analysis after we consistently observed contamination in a batch of culture plates used for bacterial sensitivity testing. Our goal was to identify the underlying issue causing the contamination. The RCA team used a fishbone diagram and the “5 Whys” method to systematically analyze potential factors such as equipment, environment, personnel practices, and materials.</p><p>After reviewing SOPs, environmental logs, and speaking with the lab staff, we found that one of the water baths used in media preparation hadn’t been calibrated in several months. The temperature was lower than required, resulting in incomplete sterilization. Once recalibrated and validated, contamination levels returned to normal.</p><ol start="2"><li><p><strong>Impact of Incorrect Root Cause Identification</strong></p></li></ol><p><strong>a. Recurring Issues and Increased Costs:</strong><br>If the wrong root cause is identified, the actual problem remains unresolved. For example, if we had incorrectly blamed human error instead of equipment failure in our case, unnecessary retraining might have been enforced while contamination continued, leading to repeated test failures, wasted resources, and higher costs.</p><p><strong>b. Regulatory and Quality Consequences:</strong><br>In industries like pharmaceuticals or food production, incorrect RCA can result in non-compliance with quality standards. This may lead to product recalls, regulatory penalties, or loss of customer trust. A misdiagnosed contamination issue, for instance, could cause unsafe products to reach the market, endangering public health.</p><p><strong>3. Most Important Transferable Skills for Conducting RCAs</strong></p><p><strong>a. Analytical Thinking:</strong><br>Professionals must be able to critically evaluate data, connect patterns, and distinguish symptoms from true causes.</p><p><strong>b. Communication and Collaboration:</strong><br>Effective RCAs require input from multiple departments. Clear communication ensures all perspectives are considered, and findings are understood and acted upon.</p><p><strong>c. Attention to Detail:</strong><br>Subtle oversights can derail investigations. Observing minor deviations and thoroughly checking documentation is key to accuracy.</p><p><strong>d. Problem-Solving:</strong><br>RCA is solution-oriented. The ability to propose and assess corrective/preventive actions is crucial to long-term success.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 21:56:29 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409618197</guid>
      </item>
      <item>
         <title>krishna patel 301396716</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409626266</link>
         <description><![CDATA[<p>once participated in a Root Cause Analysis (RCA) investigation to resolve a recurring equipment malfunction in a production setting. Initially, the issue was blamed on operator error, but through a structured RCA using the "5 Whys" method and reviewing maintenance logs, we discovered the real cause was a faulty sensor giving inconsistent readings. Replacing the sensor resolved the issue completely. </p><p>Identifying the wrong root cause can lead to wasted resources—for example, unnecessary retraining—or worse, repeated failures that damage a company’s reputation or lead to safety risks. To conduct effective RCAs, key transferable skills include critical thinking, attention to detail, strong communication, and teamwork, all of which help uncover the true root cause and implement lasting solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 22:11:34 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409626266</guid>
      </item>
      <item>
         <title>Amankhan Rana</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409631668</link>
         <description><![CDATA[<p><strong>Root Cause Analysis – My Experience</strong></p><p>I once participated in an RCA during a quality investigation in a lab setting. We noticed inconsistent results from a piece of equipment, and the initial assumption was that the machine was malfunctioning. However, after applying tools like the 5 Whys and reviewing procedures, we found the real issue: an incorrect setting used during sample preparation by the technician. As a result, we revised the SOPs and provided proper retraining to prevent it from happening again.</p><p><strong>Why finding the right root cause is important:</strong><br>If the wrong cause is identified, it can lead to wasted time and resources—like repairing or replacing equipment that wasn’t the issue. Even worse, the actual problem might go unaddressed, leading to repeated errors and possibly affecting product quality or safety.</p><p><strong>Key skills for effective RCA:</strong><br>I believe strong attention to detail, critical thinking, and the ability to communicate clearly across teams are essential for anyone regularly conducting RCAs. These skills help ensure that problems are accurately identified and permanently resolved.</p><p>RCA is not just about fixing a problem—it's about understanding it deeply and preventing it from happening again.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 22:21:19 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409631668</guid>
      </item>
      <item>
         <title>Brijesh Bhindora (301349188)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409634612</link>
         <description><![CDATA[<p>🔍 <strong>My Experience with Root Cause Analysis</strong></p><p>Hi everyone,</p><p>I’d like to share a small but memorable RCA experience from when I lived with roommates during university.</p><p>One day, I noticed half my leftover pizza was missing from the fridge. Instead of jumping to conclusions, I asked around and checked things carefully. Eventually, I found it in the freezer—someone had accidentally moved it while reorganizing the fridge. The issue wasn’t theft—it was a misunderstanding. This taught me how useful RCA can be, even in daily life, when we ask the right questions and stay objective.</p><p>⚠️ <strong>Why Identifying the Wrong Root Cause Matters</strong></p><p>In a professional setting, finding the wrong root cause can lead to:</p><ol><li><p><strong>Wasted time and money</strong>—fixing the wrong thing won’t solve the real issue.</p></li><li><p><strong>Low team morale</strong>—blaming the wrong person or department creates frustration and mistrust.</p></li></ol><p>💡 <strong>Key Skills for RCA</strong></p><p>The most important skills for RCA are:</p><ul><li><p><strong>Critical thinking</strong></p></li><li><p><strong>Good communication</strong></p></li><li><p><strong>Attention to detail</strong></p></li></ul><p><br></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 22:27:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409634612</guid>
      </item>
      <item>
         <title>Habiburheman Shekh</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409649001</link>
         <description><![CDATA[<p>During my time as a Production Supervisor and Quality Control lead in a plant tissue culture lab, I participated in an RCA after a spike in contamination across batches. Initially blamed on human error, I led a structured investigation using the 5 Whys and Fishbone Diagram. We discovered the real issue—a faulty autoclave sensor causing incomplete sterilization. Revising SOPs and validating equipment resolved the problem and avoided unnecessary staff retraining.</p><p>Identifying the wrong root cause can waste time and resources, like replacing machines or retraining staff without solving the real issue. It can also damage morale and trust if individuals are wrongly blamed.</p><p>Key skills for RCA include critical thinking, communication, data analysis, and understanding processes—helping ensure problems are solved effectively and don’t reoccur.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 22:57:08 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409649001</guid>
      </item>
      <item>
         <title>Priya Rathod (301347404)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409650872</link>
         <description><![CDATA[<p>During my second year, I participated in a group presentation that did not meet our expectations. Although we had strong content, our delivery was hindered by disorganization, repetitive points, and the absence of one team member.</p><p>Initially, we attributed our shortcomings to the missing teammate. However, following the class, we convened to discuss the situation and recognized that the primary issue was a lack of planning. We had not clearly defined roles, established deadlines, or conducted proper check-ins. Consequently, the absent member was unaware of the final presentation date, which was our responsibility.</p><p>The fundamental issue was not the absence of one individual, but rather inadequate communication and absence of structure. Following this experience, we implemented the use of shared documents, group communication channels, and assigned specific tasks early in the process. As a result, our subsequent project proceeded much more smoothly.</p><p>This experience highlighted for me that misidentifying the root cause can lead to blame rather than solutions. I learned that effective teamwork, honest reflection, and clear communication are essential skills in any collaborative effort.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-14 23:00:52 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409650872</guid>
      </item>
      <item>
         <title>Erica Fernandes (301379937)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409719633</link>
         <description><![CDATA[<p>While working on my thesis in Life Science, I encountered a situation where one of our key experiments consistently failed to yield reproducible results. The experiment involved protein expression in bacterial cultures, and despite following the protocol carefully, the protein yield was significantly lower than expected in several trials.</p><p>To identify the issue, I conducted a Root Cause Analysis. I started by collecting data from each trial: recording conditions such as temperature, pH, culture time, reagent batches, and equipment used. I created a fishbone diagram to map out possible causes, which helped us visualize the different contributing factors (e.g., human error, equipment malfunction, materials, and environment).</p><p>After systematically testing each possibility, I discovered that a recent change in the buffer preparation process introduced a pH variation, which in turn affected the efficiency of protein folding. Once the buffer preparation method was standardized and recalibrated, the protein yield returned to expected levels. This experience emphasized the importance of thorough data analysis and collaboration in identifying the true root cause.</p><p><br/></p><p><strong>Impact of Identifying the Wrong Root Cause</strong></p><p>Identifying the wrong root cause in an RCA investigation can have serious consequences for a company. Here are two examples:</p><ul><li><p><strong>Increased Costs and Wasted Resources</strong>: If a company misidentifies the root cause of a production issue and invests in fixing the wrong part of the process (e.g., replacing machinery when the real issue is in raw material quality), it can lead to significant financial losses, delays, and wasted effort.</p></li><li><p><strong>Reputation and Compliance Risks</strong>: In regulated industries like pharmaceuticals or food production, failing to identify the correct root cause of a quality defect can result in continued product failures, leading to regulatory penalties, product recalls, or loss of consumer trust.</p></li></ul><p><br/></p><p><strong>Transferable Skills Important for RCA Investigators</strong></p><p>Individuals who regularly conduct Root Cause Analyses need a variety of transferable skills, including:</p><ul><li><p><strong>Critical Thinking and Problem-Solving</strong>: The ability to objectively evaluate evidence and consider multiple hypotheses is essential to accurately pinpoint root causes.</p></li><li><p><strong>Attention to Detail</strong>: Small oversights in data or procedure can lead to incorrect conclusions. Precision and thoroughness are crucial.</p></li><li><p><strong>Communication and Team Collaboration</strong>: RCA often involves cross-functional teams. Clear communication helps ensure that all perspectives are considered and that findings are well-documented and actionable.</p></li><li><p><strong>Analytical and Data Interpretation Skills</strong>: Being able to analyze trends, correlate variables, and understand technical data plays a huge role in successful investigations.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 00:16:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409719633</guid>
      </item>
      <item>
         <title>RCA Experience - Israel Oyebanji (310280929)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409757924</link>
         <description><![CDATA[<p>During a lab project, we tested disinfectants' effectiveness against Pseudomonas aeruginosa by varying exposure times. Contrary to our expectations, shorter exposure times led to better bacterial kill results, while longer exposures resulted in unexpected bacterial growth. This prompted us to conduct a Root Cause Analysis (RCA) to rule out contamination in our materials and processes. We meticulously checked and remade reagents and components to identify potential sources of error. This experience highlighted the importance of thorough investigation when results contradict expectations and the significant impact of contamination on experimental outcomes. </p><p><br/></p><p>Identifying the wrong root cause in an investigation can have serious consequences, such as ongoing issues if the actual problem isn’t resolved. For instance, misattributing contamination to a supplier issue could lead to wasted resources while the underlying problem persists. Additionally, incorrect root cause identification can harm a company's reputation, resulting in customer distrust and financial losses.</p><p><br/></p><p>In my opinion, the most important transferable skills for individuals who regularly conduct RCAs are attention to detail and critical thinking. RCA requires people to look beyond the obvious and consider all possible factors that could contribute to a problem. Patience is also important because the process often involves going back through multiple steps and testing different possibilities before finding the true cause. Finally, good communication skills are essential because the findings need to be shared clearly with the team or management to prevent future issues and ensure everyone understands what went wrong and how to fix it.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 00:39:20 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409757924</guid>
      </item>
      <item>
         <title>RCA experience - Sloka Desai (301342763)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409762255</link>
         <description><![CDATA[<p>As a lab technician, I encountered recurring contamination in our agar plates. I joined the RCA team to investigate. After checking sterilization logs and aseptic practices, we discovered a small crack in the Petri dish storage container. This allowed air exposure post-autoclaving. Replacing the container and improving storage checks solved the issue. It taught me how small errors can lead to big problems in lab environments.</p><p><strong>2. Impact of Wrong Root Cause:</strong><br>Identifying the wrong root cause can harm both productivity and safety. For example:</p><ul><li><p>Blaming the autoclave instead might lead to media damage and wasted resources.</p></li><li><p>In a clinical setting, unresolved contamination could delay patient results or drug testing, risking compliance and health outcomes.</p></li></ul><p><strong>3. Key Skills for RCA:</strong></p><ul><li><p><strong>Attention to detail</strong> – spotting small but critical issues.</p></li><li><p><strong>Analytical thinking</strong> – connecting symptoms to root problems.</p></li><li><p><strong>Team communication</strong> – working with cross-functional teams to find accurate solutions.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 00:41:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409762255</guid>
      </item>
      <item>
         <title>RCA Experience- Neha (301346938)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409813458</link>
         <description><![CDATA[<p>During a lab-based project in my biotechnology program, I was involved in a Root Cause Analysis (RCA) after a repeated issue with bacterial contamination in one of our media preparation exercises. The same contamination appeared in multiple groups’ culture plates, even though all procedures were followed according to the lab manual.</p><p>At first, our instructor suspected a problem with the autoclave cycle not reaching the correct sterilization temperature. However, our RCA process encouraged us to consider all possible contributing factors instead of jumping to conclusions. We formed small investigation teams and used tools like the "Fishbone Diagram" and "5 Whys" to examine all aspects—equipment, materials, methods, environment, and people.</p><p>After analyzing the situation carefully, we traced the problem back to a shared bottle of distilled water used to prepare media. Someone had unknowingly touched the inside of the bottle cap with their glove, and the contaminated cap led to the spread of microbes across multiple batches of media. The issue wasn’t due to faulty equipment, but rather a small lapse in aseptic technique.</p><p>As a result, we updated our lab practices to include more rigorous handling procedures for shared reagents and added a visual reminder near the media prep station about avoiding contact with bottle openings. This experience showed me how easily the real cause can be missed if assumptions are made too early.</p><p>It also emphasized how valuable transferable skills like critical thinking, attention to detail, communication, and teamwork are during RCA. Without a structured approach and group collaboration, we might have misidentified the root cause and continued facing the same issue.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:10:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409813458</guid>
      </item>
      <item>
         <title>Jay Patel ( 301429020 )Workplace Mix-Up - “The Printer Panic”</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409816057</link>
         <description><![CDATA[<p>Hey everyone,</p><p>I want to share a quick story from my part-time office job. A few months ago, there was this big panic because a batch of invoices went out with incorrect totals. People were confused, customers were calling, and management thought the billing software had glitched.</p><p>They asked a few of us to help figure out what happened. I went through the files and noticed that the issue was only in the ones processed on one specific afternoon. Turns out, someone had updated the formula in an Excel sheet but forgot to lock the cells, so every time someone edited something, the totals would get messed up.</p><p>So, the real root cause wasn’t the software—it was human error and a lack of proper file management. We fixed it by locking the cells, and now we have a checklist for file formatting before anything goes out.</p><p>That experience taught me how important it is to look past assumptions and dig into the details. If we had just blamed the software and moved on, the same mistake could have happened again.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:11:43 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409816057</guid>
      </item>
      <item>
         <title> Anjali Bharadwaj (301380229)Home Life Detective — “The Disappearing Laundry”</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409819884</link>
         <description><![CDATA[<p>Hi everyone,</p><p>This might sound funny, but one time I had to do a full-blown investigation at home. My clothes kept going missing from the laundry room—like, shirts just gone. I live with family, so at first I figured someone was just grabbing the wrong stuff by accident. But it kept happening.</p><p>So, I started asking questions and checking laundry days. I even wrote down when I did each load. Eventually, I realized that the dryer vent wasn’t attached properly, and lighter clothes were literally getting sucked into the space behind the machine. I found three socks, two shirts, and a towel back there.</p><p>That was the real root cause—not a careless family member, but a maintenance issue. If I hadn’t looked into it, we would’ve kept blaming each other and losing clothes.</p><p>It made me realize that in RCA, jumping to conclusions usually leads you in the wrong direction. You have to stay objective and gather facts.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:13:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409819884</guid>
      </item>
      <item>
         <title>Thilakshan S. ( 301377623 )School Project Chaos -“The Broken Presentation File”</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409823226</link>
         <description><![CDATA[<p>Hey folks,</p><p>Here’s one that happened during a group project in college. We were using Google Slides to put together a presentation, and the night before it was due, the entire file glitched out—slides were missing, formatting was gone, and animations were out of control. It was a mess.</p><p>We all freaked out, thinking someone must have deleted stuff by accident. There was a bit of arguing, honestly. But then we checked the version history and saw that one of the group members had opened the file in PowerPoint to “make it look better,” then reuploaded it to Google Slides.</p><p>Turns out, some of the formatting and animations from PowerPoint didn’t translate properly back into Google Slides, and that was what caused the issue. We didn’t know the platforms weren’t fully compatible.</p><p>So we set a rule after that: only edit the file in Google Slides, and no one uses outside software. It was a tough situation, but we learned to focus on fixing the system instead of blaming people.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:15:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409823226</guid>
      </item>
      <item>
         <title>Sreenath Edakkudi (301419939) Root Cause Analysis in the Biotech Lab: The Case of the Invisible Bands</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409828169</link>
         <description><![CDATA[<p>During a biotechnology lab, we were running gel electrophoresis to visualize PCR products, but when I checked my gel, there were no visible bands—just a faint smear. I retraced my steps and realized I had accidentally used an expired loading dye that wasn’t properly labeled. This simple mistake led me to conduct a mini Root Cause Analysis, which revealed that poor labeling and not double-checking reagents were the main issues. It taught me how important attention to detail, communication, and proper lab practices are in preventing errors. Identifying the correct root cause saved time and helped ensure others didn’t make the same mistake.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:17:47 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409828169</guid>
      </item>
      <item>
         <title>RCA Experience- Sakshi Patel(301432861)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409831999</link>
         <description><![CDATA[<p>I’d like to share a quick experience I had with Root Cause Analysis in customer service.</p><p>I was involved in an RCA when we noticed a rise in delayed responses to customer inquiries. After analyzing data and using tools like the 5 Whys, we found the issue was a system update that misrouted tickets. Fixing the routing logic and retraining staff resolved the delays.</p><p>Identifying the wrong root cause can lead to recurring problems—like blaming staff instead of the system—and waste time and resources fixing the wrong issue.</p><p>To do RCA effectively, critical thinking, good communication, and attention to detail are key skills. They help ensure issues are solved at the source and don’t repeat.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:19:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409831999</guid>
      </item>
      <item>
         <title>Divya Patel (301355906)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409837556</link>
         <description><![CDATA[<p>During a lab project, I participated in a Root Cause Analysis after we noticed unexpected bacterial growth on our control plates, which shouldn’t have happened. Our first assumption was that it was a simple handling error—maybe someone accidentally contaminated the plate during the experiment. We documented that as the root cause and repeated the test, only to find the same issue again. That’s when we took a deeper look and discovered the actual problem: the autoclave cycle hadn’t completed properly, so the media used wasn’t fully sterilized. This experience made me realize how damaging it can be to identify the wrong root cause. In a company setting, that kind of mistake could lead to repeated production failures, wasted resources, or worse—sending out unsafe or defective products that damage a brand’s reputation. People who regularly conduct RCAs need strong critical thinking, attention to detail, and the ability to communicate findings clearly, especially when working across teams with different areas of expertise.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 01:21:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409837556</guid>
      </item>
      <item>
         <title>VISHNUMAYA ERUVAT(301380249)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409923990</link>
         <description><![CDATA[<p>Hey everyone,</p><p>I want to share a story from one of my past part-time jobs when I worked in a kitchen. It wasn’t anything fancy—just a busy place with a lot of moving parts. One weekend, we had a major issue. The refrigerator in the prep area stopped working overnight, and when the morning staff came in, a huge amount of perishable food had spoiled. It caused a lot of stress since we had to toss ingredients and delay food prep, which threw off the whole day.</p><p>The supervisor asked a few of us if we’d noticed anything unusual or if we had any ideas about what happened. I remembered hearing the fridge make some weird clicking sounds the night before but didn’t think much of it at the time. That little observation helped kick off what turned into a small Root Cause Analysis.</p><p>We looked into it and found out that the plug had been loosely connected to an outlet that wasn’t fully secure. Vibration over time caused the plug to shift just enough to cut off power. So the real issue wasn’t the fridge itself—it was the electrical outlet.</p><p>What I took away from that was how small details matter. If I hadn’t mentioned that sound, we might have assumed the fridge was faulty and replaced it, which would have cost more and not fixed the actual problem. That’s the whole point of RCA, right? Getting to the real cause so it doesn’t happen again.</p><p>Now, I always try to be more observant and speak up when something doesn’t seem right—because even something small can prevent a bigger issue.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 02:06:55 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409923990</guid>
      </item>
      <item>
         <title>MUHAMMED ASIF (301413409)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3409969287</link>
         <description><![CDATA[<p>Hi everyone , my experience with the root cause analyis was during the part time at our convention center, the coffee machine was malfunctioning during high-traffic events, producing weak coffee or failing to brew. This was affecting both staff and guest satisfaction. We initially thought the coffee machine was broken, so we checked its internal components and power supply. After continued issues, we inspected the filter system and reviewed the maintenance log. It turned out that the coffee filter being used was too large for the machine, causing water to bypass the filter and resulting in weak coffee. The incorrect filter size caused the brewing failure. The wrong filter didn’t fit properly, leading to improper water flow and overheating. We replaced the filters with the correct size and set up a checklist to ensure filters are checked regularly. If the wrong root cause was identified, we might have spent unnecessary resources on repairing the coffee machine and continued to face guest dissatisfaction.</p><p>This experience highlighted the importance of attention to detail and clear communication when identifying issues. Even small mistakes, like the wrong filter, can cause significant disruptions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 02:29:15 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3409969287</guid>
      </item>
      <item>
         <title>Kavita kshatriya (301396242)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3410000585</link>
         <description><![CDATA[<p>Hey everyone, I once took part in a Root Cause Analysis when a significant issue arose during a group project in college. Our experiment kept failing, and we initially thought it was because of a problem with the materials. After retracing our steps and delving into deeper inquiries, we realized that the actual problem stemmed from a simple misinterpretation of the procedure—one team member had misunderstood a step in the protocol, leading to the inconsistency. This experience highlighted for me the importance of investigating thoroughly rather than jumping to conclusions. In a work environment, misidentifying the actual root cause can result in serious repercussions. For instance, if a company wrongly attributes a malfunction to equipment failure rather than user error, they could end up spending a fortune replacing machines that are actually functioning well. Even worse, if contamination in a laboratory is wrongly assigned to the incorrect process, the true issue might remain unaddressed and continue to recur—threatening safety and product quality. Individuals who routinely conduct RCAs require strong transferable skills such as attention to detail, analytical thinking, and effective communication. They need to maintain objectivity, ask insightful follow-up questions, and meticulously analyze data to prevent assumptions. RCA is not merely about resolving issues—it’s about addressing the correct issue, and that distinction is crucial.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 02:45:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3410000585</guid>
      </item>
      <item>
         <title>Praachi singla (301429038)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3410007824</link>
         <description><![CDATA[<p>Back when I was working part-time at a local café, we kept getting customer complaints about drinks tasting “off”—especially the iced coffees. The manager thought it was the beans and ordered a new batch, but the problem continued. Then we blamed the ice machine, cleaned it thoroughly, still no change. I was curious and decided to dig a little deeper. One slow afternoon, I did a mini RCA just out of habit—started tracing each step of the drink-making process. That’s when I noticed the milk frothing jug being washed but never fully dried before going back into use. Moisture left in the jug, especially after sitting near the espresso machine, was causing a slight sourness in the drinks. No one had considered that. Once we started properly drying the equipment, the complaints disappeared. That small investigation made me realize how easy it is to jump to conclusions and how powerful it is to slow down, ask questions, and look at the full picture. It also earned me a free latte and some respect from my manager</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 02:49:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3410007824</guid>
      </item>
      <item>
         <title>Ming Yiu Lam (301390789)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3411105901</link>
         <description><![CDATA[<p>During my time working as a high school lab technician, I had to perform an experiment showing the photoelectric effect and stopping current. The teacher and I tried on the experiment during recess time before class and it worked well. However, no effect was shown during the class demonstration, and we ended up showing the video instead. </p><p><br/></p><p>After the class, I tried the experiment again and examined the power supply, the photoelectric cell, the multimeters and wires and all functioned well. At last I found that it was because of not having enough light intensity to generate the current as the teacher switched off some of the lights in the lab.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 16:57:39 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3411105901</guid>
      </item>
      <item>
         <title>Laxmi Poudel (301360471)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3411260549</link>
         <description><![CDATA[<p>In a previous laboratory position, I was involved in a Root Cause Analysis (RCA) when our quality control tests began consistently failing. We did not reflexively blame reagents but considered procedures, equipment history, and environmental conditions attentively. Long story short, we eventually figured out that the root cause lay in a very minor change to temperature calibration in maintenance. That experience showed me how important RCA is in identifying and addressing fundamental issues effectively. If an incorrect root cause is determined, it can have serious repercussions—e.g., a business can waste money on fixing the wrong problem or have reputational exposure if safety issues are not addressed. The essential transferable skills to successful RCA are critical thinking, thoroughness, and superior communication, all of which are vital to determining the problem and preventing future failure.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-15 19:27:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3411260549</guid>
      </item>
      <item>
         <title>Handeep Singh-301431619</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3415328078</link>
         <description><![CDATA[<p>During my Microbiology Project-2 at Centennial College, I conducted an experiment to evaluate the antimicrobial effects of medicinal plant extracts—specifically ginger, basil, and aloe vera—on common pathogenic bacteria. In one of the initial trials, none of the plant extracts showed any zones of inhibition, which was unexpected given prior successful results. This outcome required a detailed Root Cause Analysis (RCA) to determine what went wrong.</p><p>Upon reviewing the materials, methods, and environmental conditions, I discovered that the ethanol used in the extraction process had not been completely evaporated. The presence of residual ethanol likely disrupted the natural antimicrobial compounds in the extracts, rendering them ineffective in the test. After repeating the experiment with properly evaporated extracts, clear zones of inhibition were observed, confirming that the plant extracts were indeed effective.</p><p>Impact of Identifying the Wrong Root Cause:</p><p>If the incorrect root cause had been identified during this process, it could have had the following negative outcomes:</p><ol><li><p><strong>Wasted Resources and Time</strong>: I might have altered other variables like extract concentration or bacterial strain, which were not the true source of the problem, leading to unnecessary repetition and delays.</p></li><li><p><strong>Inaccurate Conclusions</strong>: Had I reported the extracts as ineffective without identifying the true issue, it would have compromised the credibility of my data and potentially affected further related research.</p></li></ol><p>Transferable Skills Gained:</p><p>This experience helped me build several transferable skills essential for effective RCA:</p><ul><li><p><strong>Attention to Detail</strong>: Carefully analyzing each procedural step allowed me to identify subtle but crucial errors like incomplete solvent evaporation.</p></li><li><p><strong>Analytical Thinking</strong>: I systematically examined all possible causes, ruling out each one based on scientific reasoning and observations.</p></li><li><p><strong>Problem-Solving</strong>: I was able to correct the issue and successfully repeat the experiment, demonstrating adaptability and technical troubleshooting.</p></li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2025-04-18 21:00:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3415328078</guid>
      </item>
      <item>
         <title>Cecilia Del Rosario-301423789</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3471816329</link>
         <description><![CDATA[<p><strong>Root Cause Analysis</strong></p><p>We often think investigations only happen at work, but in reality, they can occur in our everyday lives—even at home. One personal experience I had with a Root Cause Analysis (RCA) involved my 2-year-old son. One day, while I was preparing his milk, he suddenly cried loudly. I found him on the floor, but since he couldn’t yet speak clearly, I had no idea what had really happened. To understand the situation better, I reviewed our CCTV footage at home.</p><p>After watching closely, I discovered that he had slipped because there was spilled liquid on the floor. This incident taught me how important it is to take time to observe carefully and find the true cause of a problem. Jumping to conclusions without evidence can lead to wrong assumptions. Just like in RCA, we need to gather all the facts before deciding what went wrong.</p><p>If the wrong root cause is identified in an investigation, the problem can happen again—and sometimes with worse consequences. For example, if I had assumed that my son slipped just because of the floor itself and didn’t clean the spilled liquid, the same thing could have happened again. In a company, this kind of mistake could result in wasted resources and repeated accidents, affecting both safety and productivity.</p><p>For those who do RCA regularly, I believe some of the most important transferable skills are critical thinking, attention to detail, effective communication, and patience. These skills help make sure that the investigation leads to a real solution—not just a temporary fix.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-05-29 02:30:40 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3471816329</guid>
      </item>
      <item>
         <title>Rachel Claire Cuevas (301346312)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3471883417</link>
         <description><![CDATA[<p>I was involved in a Root Cause Analysis (RCA) to find out why some specimen tubes were labeled wrongly in a busy medical laboratory. This happened because there were many patients at the same time, and the process for labeling was not clear or double-checked. Through the RCA, we discovered that the real cause was the lack of a second check during labeling and a poor setup for handling patient flow. If the wrong cause is found in an RCA, the same mistake can happen again, which may put patients at risk, or the company might waste time and money fixing the wrong problem. To carry out a good RCA, important skills include clear thinking, attention to detail, good communication, understanding how the steps in a process work together, and staying fair and focused on solving the problem, not blaming people.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-05-29 03:03:07 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3471883417</guid>
      </item>
      <item>
         <title>Mariyah Gangat (301259957)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3474725973</link>
         <description><![CDATA[<p>In a previous role in food production, I was involved in a Root Cause Analysis (RCA) after foreign plastic material was found in a finished product. I helped inspect the production area and review equipment maintenance logs, where we discovered a damaged conveyor belt was shedding plastic pieces. The issue was resolved by replacing the belt and updating inspection procedures. Identifying the wrong root cause—like blaming employee error instead of equipment failure—can lead to repeated contamination and product recalls. Strong skills in problem-solving, attention to detail, and communication are essential for conducting effective RCAs and preventing future issues.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-05-31 22:56:08 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3474725973</guid>
      </item>
      <item>
         <title>Onyeka Ajuwa 301289649</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3475293874</link>
         <description><![CDATA[<p>When I was working in a food testing lab, I got pulled into a root cause analysis (RCA) after we discovered that expired media had been used in microbial testing, which threw off our results and delayed a product batch release. It was frustrating because the issue popped up during a routine quality check when we noticed inconsistent results, and we had to act fast to figure out what went wrong. Using the "5 Whys" and a causal tree, we started by pinpointing that a technician had grabbed expired media. Digging deeper, I helped uncover some real systemic problems: our inventory system didn’t flag expiring media, expired stock wasn’t separated from the good stuff, and the technician, who was pretty new, hadn’t been trained on checking expiration dates. Our standard operating procedures (SOPs) also didn’t require a double-check for media before testing. At first, some team members got defensive, worried they’d be blamed, but I made it a point to stress that we were focusing on fixing the system, not pointing fingers, which really helped everyone open up and share what they knew.</p><p>The RCA process was eye-opening and led to changes I’m proud we pushed through. We updated the inventory system to send alerts for expiring media, set up a clear separation for expired materials, and rewrote the SOPs to include a mandatory expiration date check before any testing. We also made sure new staff, like our technician, get thorough training with a checklist to follow. When we checked back later, there were no repeat issues, and the team felt more connected, like we were all in it together to make the lab better. This experience really hit home for me—focusing on the system, not the person, made all the difference in preventing errors and keeping our food safety testing on point.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-02 00:37:38 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3475293874</guid>
      </item>
      <item>
         <title>Nina Reign Xyrelle Daculug- 30139311</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3478409870</link>
         <description><![CDATA[<p>During my work in a laboratory setting, I participated in a Root Cause Analysis following an incident where a batch of test results was delayed, leading to workflow disruption. The goal of the RCA was to determine why the delays occurred and how to prevent them in the future.</p><p>We used tools like the <strong>5 Whys</strong> and <strong>Fishbone (Ishikawa) diagram</strong> to guide the investigation. Initially, the assumption was that the problem stemmed from equipment malfunction. However, after deeper probing, we discovered the actual root cause was a miscommunication in scheduling due to recent changes in the software interface, which staff were not fully trained on. Addressing this helped us implement a targeted training plan and update our protocols to avoid recurrence.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-04 05:21:35 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3478409870</guid>
      </item>
      <item>
         <title>Mikka Celine Abril (301416919)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3482585283</link>
         <description><![CDATA[<p>In my previous role as a medical technologist, I was involved in a Root Cause Analysis after we discovered a specimen mix-up between two patients—a husband and wife—when one of the test results didn’t match the patient’s medical history. After looking into it, we found that the issue happened because the blood tubes were labeled before the actual collection, and with so many patients arriving at once, the samples were accidentally switched. If the wrong root cause had been identified, the same error could’ve easily happened again, or time and resources might’ve been wasted on fixing the wrong part of the process. From this experience, I learned how important skills like attention to detail, clear communication, and the ability to analyze a situation calmly are when conducting an RCA and making sure the right changes are put in place.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-08 23:11:11 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3482585283</guid>
      </item>
      <item>
         <title>Gopika Krishnan (301379450)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3490876283</link>
         <description><![CDATA[<p>In a previous role as a QA technician at a food manufacturing facility, I was involved in a Root Cause Analysis after we noticed several batches of a confectionery product showing inconsistent coloring and texture. At first, the blame was placed on a raw material issue, but after checking supplier records and batch data, everything appeared normal.</p><p>Digging deeper, I found the real issue was due to room temperature fluctuations during the coating process, caused by a malfunctioning cooling unit. The environmental conditions affected how the coating adhered, which led to visible quality defects. Once we fixed the unit and updated monitoring procedures, the issue was resolved.</p><p>This made me realize how damaging it can be to identify the wrong root cause. First, it wastes time and resources chasing the wrong solution. Second, it can strain relationships with suppliers or teams who were wrongly blamed — which damages internal trust.</p><p>For me, the most important transferable skills in RCA are critical thinking, attention to detail, and communication. You need to ask the right questions, interpret data carefully, and work collaboratively to get to the true cause — not just the obvious one.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-16 00:00:24 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3490876283</guid>
      </item>
      <item>
         <title>Zeel Shah (301280761)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3492116105</link>
         <description><![CDATA[<p>One of the first times I did a Root Cause Analysis wasn’t even at work—it was at home. I had some takeout leftovers in the fridge that mysteriously disappeared. I asked my roommates, and of course, no one admitted to eating it. So, I checked the trash, narrowed down who was home at the time, and eventually found out one roommate ate it by mistake, thinking it was theirs. It was a small thing, but it made me realize how helpful it is to step back and actually <em>investigate</em> instead of assuming.</p><p>Later at work, I helped a manager figure out why a certain process kept getting delayed. Everyone thought it was a tech issue, but after asking around and breaking things down, we found out it was actually a communication gap between two teams. Fixing that made a real difference.</p><p>If you get the wrong root cause, it can waste time and money—and even hurt trust if people feel unfairly blamed. That’s why I think active listening and critical thinking are super important skills for anyone doing RCA. Whether it’s about food or workflow, getting to the real “why” matters.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-16 18:50:40 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3492116105</guid>
      </item>
      <item>
         <title>Ana Pichardo Ramos 301383881</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3492182051</link>
         <description><![CDATA[<p><br/></p><ol><li><p>When I was working in the Quality Assurance team at a food company, I had the opportunity to collaborate in a root cause analysis investigation after found that a raw material was allegedly  contaminated with a piece of a plastic tag. Through the investigation we were able to find in which stage of the process the ingredient was in contact with the plastic tag, the complete batch was put on hold till the department verify the quality and safety usage of the ingredient. After the investigation, the missing plastic tag was founded and the ingredient was release for further usage.  </p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-16 21:07:48 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3492182051</guid>
      </item>
      <item>
         <title>hellay-301422060</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3492214879</link>
         <description><![CDATA[<p>During my co-op, I was involved in a situation where one of our batch tests consistently failed quality control. I assisted in an RCA investigation to identify the source of the issue. We followed a structured process—starting with documenting the problem, then collecting data on equipment, reagents, and procedures.</p><p>We discovered that the buffer solution used during sample prep had incorrect pH due to a miscalibrated pH meter. After recalibrating the equipment and retraining staff, the test results returned to normal. This experience taught me how systematic troubleshooting and asking "why" multiple times can uncover the real issue behind a problem.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-16 22:28:51 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3492214879</guid>
      </item>
      <item>
         <title>Nidabanu Pathan</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3492299117</link>
         <description><![CDATA[<p>During my co-op at Golden Boy Foods as a Quality Assurance Technician, I was involved in addressing a recurring issue with inconsistent product quality in one of our packaged food lines. To resolve this, our team conducted a Root Cause Analysis (RCA) to identify the fundamental reasons behind the problem. We collected production data, reviewed quality control records, and interviewed operators on the floor. The RCA revealed that the main cause was a variation in temperature settings during processing, which affected the product’s texture and shelf life.</p><p>Based on these findings, we standardized the temperature controls and implemented stricter monitoring procedures during production. Additionally, we provided refresher training to the operators to ensure they understood the critical parameters that must be maintained. After applying these corrective actions, we noticed a marked improvement in product consistency and a reduction in customer complaints. This experience reinforced for me how important RCA is in pinpointing true causes and implementing effective solutions in food quality assurance.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-17 00:25:00 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3492299117</guid>
      </item>
      <item>
         <title>Krishi Patel (301280750)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3492608685</link>
         <description><![CDATA[<p>While working in event security, I was once asked to help figure out why a key storage area was left unlocked after an event. I wasn’t directly involved, but I had seen a lot of people around that area. At first, it seemed like someone just forgot, but after asking around, we realized a temporary staff member had used a copied key that wasn’t tracked. That discovery led to a better key sign-out process. If we had blamed the wrong person, it could’ve caused unfair consequences and not fixed the real issue. In a company, identifying the wrong root cause can lead to wasted money—like replacing equipment that isn’t broken—or failing to solve real problems, like confusing poor shipping with bad customer service. To do RCA well, I think the most important skills are being observant, asking the right questions, and staying neutral. Clear communication is also key to making sure the real issue is understood and addressed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2025-06-17 03:10:02 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3492608685</guid>
      </item>
      <item>
         <title>Ewu David (301350756)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3791637482</link>
         <description><![CDATA[<p>During my work in a food production environment, I participated in a Root Cause Analysis (RCA) after a product failed routine quality inspection due to inconsistent consistency. The team reviewed production records, checked equipment settings, and interviewed staff involved in the process. Using the 5 Whys method, we investigated possible causes to identify where the problem occurred.</p><p>The investigation found that the root cause was poor temperature monitoring during processing, which affected product quality. Corrective actions included retraining staff, improving monitoring procedures, and updating standard operating procedures. As a result, the issue did not occur again, and overall production quality and process control improved.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-16 19:10:01 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3791637482</guid>
      </item>
      <item>
         <title>Chen-Fu Jack Chen (300829897)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3791731464</link>
         <description><![CDATA[<p>1.  To identify the fundamental, underlying cause of a problem or event to prevent recurrence.</p><p>2.  Recurring problems and wasted resources; Escalating issues and safety risks.</p><p>3.: Critical thinking, communication, and problem-solving.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-16 21:39:44 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3791731464</guid>
      </item>
      <item>
         <title>Nidhi(301486893)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3794149526</link>
         <description><![CDATA[<p>I would like to briefly share my experience with a Root Cause Analysis investigation. While working in a food service environment, we identified recurring inconsistencies in the texture and taste of a prepared food item. A Root Cause Analysis was conducted using the 5 Whys method. The investigation revealed that the issue was not related to ingredients or equipment, but rather the absence of a documented standard operating procedure. Preparation methods varied because training was provided verbally and lacked standardization. Once a formal SOP and structured training process were implemented, the issue was successfully resolved.</p><p>Identifying the wrong root cause can significantly impact a company. First, it can result in financial losses if resources are allocated to incorrect corrective actions. Second, the problem may persist, leading to repeated incidents and potential damage to the company’s reputation and customer trust.</p><p>The most important transferable skills for conducting Root Cause Analyses include critical thinking, analytical reasoning, attention to detail, effective communication, objectivity, and strong problem-solving abilities.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-18 23:39:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3794149526</guid>
      </item>
      <item>
         <title>Paras (301485729)</title>
         <author>shaklaparas001</author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3796462045</link>
         <description><![CDATA[<p>I would like to share an experience from my Food Science Project 2 where we were using Oxford agar to prepare culture plates for microbial analysis.</p><p>We followed the entire media preparation procedure correctly, including weighing the Oxford agar, diluting it on the hot plate, and pouring the plates under proper conditions. All the preparation steps were performed accurately according to the standard protocol.</p><p>However, after plating the samples, we did not observe any microbial colonies on the plates, which was unexpected. Instead of immediately repeating the experiment, we decided to perform a simple Root Cause Analysis.</p><p>We reviewed each step of the process, including weighing accuracy, dilution, incubation conditions, and sterilization procedures. After asking “why” multiple times and checking the materials used, we found that the Oxford agar we had used had actually expired a long time ago.</p><p>Once we replaced the expired agar with a fresh batch and repeated the experiment, we were able to observe proper microbial growth on the plates. This experience helped me understand the importance of verifying materials before assuming procedural errors.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-20 20:57:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3796462045</guid>
      </item>
      <item>
         <title>Timothy Gelacio (301343419)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3797015479</link>
         <description><![CDATA[<p>I had been involved in a root cause analysis when our chef noticed that the kitchen has been left dirty from last night's dinner service. An investigation was conducted and the team was interviewed using the 5 whys method to determine the main cause. The investigation determined that the problem was in the staff schedule. The schedule was done in a way where there was only one person to clean and close the entire kitchen since the last hour of service seldomly got customers. A big group came in late that previous night and the employee did not have time to finish all the cleaning and closing tasks before their shift was over. As a result, the scheduling was changed where start times are now staggered in a different way so there is now always 2 people left to close the kitchen and prevent such an event from happening again.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-21 20:04:13 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3797015479</guid>
      </item>
      <item>
         <title>Barbara Guimaraes - 301189510</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3797075805</link>
         <description><![CDATA[<p>I've participated in an RCA meeting to discuss a clumping issue one of the gravies was having when going through screening to be packed. It was a combined effort of plant personnel, the quality department, and the scientist at the time who formulated the gravy. With 3 points of view on the problem, the meeting yielded a list of possible causes and what could be done to change it. It had been an ongoing problem for the past few months, and after this interdepartmental meeting, we resolved the clumping issue. If the wrong root cause is identified, it can damage the company's equipment, incur financial losses, and, because the wrong cause was identified, the problem persists, causing production downtime. I think that attention to detail is an important transferable skill when conducting an RCA.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-21 23:37:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3797075805</guid>
      </item>
      <item>
         <title>Akhil Raj Chand Sithara 301404846</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3797337580</link>
         <description><![CDATA[<p>I would like to share an experience from my Food Science laboratory course during a microbial analysis experiment.</p><p>We were preparing XLD agar plates to isolate <em>Salmonella</em> from a food sample. We carefully followed the standard protocol, including accurate weighing of the dehydrated media, proper heating and mixing, sterilization, and pouring plates under aseptic conditions. After inoculation and incubation at 37°C, we expected to observe characteristic colonies. However, no growth appeared on the plates, including the positive control.</p><p>Instead of immediately repeating the experiment, we conducted a simple Root Cause Analysis. We reviewed each step: balance calibration, autoclave cycle, incubation temperature, and plating technique. After systematically checking the materials used, we discovered that the dehydrated agar powder had expired several months earlier, which likely affected its performance.</p><p>Once we replaced it with a fresh batch and repeated the procedure, we observed proper microbial growth. This experience reinforced the importance of verifying reagent quality and expiration dates before assuming procedural errors and strengthened my understanding of Good Laboratory Practices.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-02-22 11:48:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3797337580</guid>
      </item>
      <item>
         <title>Palak (301485161)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3808876825</link>
         <description><![CDATA[<p>I would like to share an experience from one of my chemistry experiments. In my earlier studies, me and my lab partner were supposed to use sodium nitrate, but our reaction completely failed because no precipitation formed and we could not continue with the derivative steps. To understand what went wrong, we applied an RCA approach and kept questioning each part of our process. We reviewed the procedure, retraced every step we had done, and checked whether our method, measurements, or conditions were followed correctly. When everything still seemed correct on paper, we looked deeper and inspected all the reagent bottles one by one we used. That is when we discovered the true root cause, we had accidentally used sodium nitrite instead of sodium nitrate. Both chemicals started with the same letter, had very similar names, and were stored right next to each other on the same shelf, so it was easy to pick up the wrong bottle without realizing it. Once we repeated the experiment with the correct reagent, the reaction worked normally and the expected product formed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-02 23:28:23 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3808876825</guid>
      </item>
      <item>
         <title>Ashna (301484972)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3808948065</link>
         <description><![CDATA[<p>I was involved in a root cause analysis after a security incident occurred during a night shift when an unauthorized person entered a restricted area. We conducted an investigation using the 5 Whys method, reviewed access logs, and interviewed the officer on duty. At first, it seemed like the officer failed to follow procedure. However, we discovered the real issue was inadequate staffing during peak hours. One officer was assigned to monitor multiple entry points, and while responding to another situation, the access point was left unattended. As a result, schedules were adjusted to ensure proper coverage, and an additional verification step was added.</p><p>If the wrong root cause is identified, two major impacts can occur. First, the issue may happen again because the real problem was not fixed. Second, unfairly blaming employees can lower morale and reduce trust, which weakens the overall security culture.</p><p>The most important transferable skills for conducting RCAs are critical thinking, attention to detail, strong communication, and objectivity. These skills help ensure investigations focus on facts and lead to effective, long-term solutions rather than temporary fixes.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-03 00:44:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3808948065</guid>
      </item>
      <item>
         <title>Aarat (301489580)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3810575239</link>
         <description><![CDATA[<p>During one of my college lab projects, our experiment kept giving wrong results, so our team did a Root Cause Analysis, or RCA, to find out why. We checked every step, looked at the materials and equipment, and finally realized the problem was a thermometer giving wrong readings, not the experiment itself. This showed us that finding the real cause is really important. If a company finds the wrong cause, it can waste money fixing the wrong thing or let the real problem continue, which can cause delays or complaints. Important skills for RCA are thinking carefully, noticing small details, and explaining your findings clearly. Doing this RCA taught me that solving problems properly means figuring out the real reason behind them.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-03 23:58:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3810575239</guid>
      </item>
      <item>
         <title>Ananthakrishnan K (301470503)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3811576026</link>
         <description><![CDATA[<p>During my previous academic lab experience, I was part of a small investigation when our microbial plate count results were inconsistent over several trials. Some plates showed unusually high counts, while others from the same dilution series showed almost no growth. At first, we thought the media might have been contaminated. However, instead of jumping to conclusions, we decided to step back and go through a simple Root Cause Analysis process.</p><p>We reviewed each step: media preparation, autoclave records, incubation temperature logs, and our aseptic techniques. After checking the autoclave log and temperature records, everything seemed normal. Finally, while observing one of the repeat trials, we noticed that the vortexing step before serial dilution was not being done consistently. Some tubes were not mixed thoroughly before transferring to the next dilution. That small inconsistency turned out to be the root cause of the variation in plate counts.</p><p>This experience showed me how easy it is to assume the problem is equipment or materials when sometimes it is human process variation. It also taught me the importance of observing the process directly instead of relying only on assumptions.</p><p>If the wrong root cause is identified in an investigation, it can seriously impact a company. First, the same problem will likely happen again because the actual issue was never fixed. This can lead to repeated product defects or safety concerns. Second, the company may waste money and time fixing the wrong issue—for example, replacing equipment when the real problem is a training gap. That not only increases costs but can also reduce employee confidence in management decisions.</p><p>I believe the most important transferable skills for conducting RCAs are critical thinking, attention to detail, and open-mindedness. Communication is also very important because investigations usually involve multiple people and departments. Finally, emotional control matters—especially in high-pressure situations—so that blame does not interfere with finding the real cause.</p><p>Overall, that experience helped me understand that RCA is less about finding someone to blame and more about understanding systems and improving processes. It changed the way I look at problems—not just in labs, but in daily life as well.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-04 13:15:19 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3811576026</guid>
      </item>
      <item>
         <title>Aleena Jaison (301482397)</title>
         <author>12aleenajaison</author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3812286478</link>
         <description><![CDATA[<p>During a lab session, our group noticed that our microbial plate counts were much higher than expected. This meant our food sample appeared contaminated, and we had to repeat the experiment.</p><p>Instead of assuming someone handled the sample incorrectly, our instructor guided us through a Root Cause Analysis using the 5 Whys technique.</p><p>Why were the microbial counts too high?<br>Because contamination occurred during sample preparation.</p><p>Why did contamination occur?<br>Because sterile technique was not fully maintained.</p><p>Why was sterile technique not maintained?<br>Because students were rushing and the disinfectant spray was not readily available at each station.</p><p>Why wasn’t it available?<br>Because supplies were not restocked before the lab began.</p><p>We realized the root cause was not just student error, but a system issue — lack of preparation and organization of materials. After implementing a checklist to restock supplies before each lab and reinforcing sterile technique procedures, the issue improved significantly.</p><p>This experience showed me that RCA helps identify system weaknesses rather than blaming individuals.</p><p>If the wrong root cause is identified, it can negatively impact a company or lab.</p><p>The most important transferable skills for conducting RCA include:</p><p>Critical thinking, Attention to detail, Communication skills, Problem-solving skills.</p><p>In conclusion, RCA in a food science lab is essential because food safety depends on accuracy and proper procedures. </p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-05 00:02:18 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3812286478</guid>
      </item>
      <item>
         <title>Jasleen (301490095)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3813029933</link>
         <description><![CDATA[<p>During my work experience at a restaurant, I participated in a Root Cause Analysis after customer complaints about delayed orders during peak hours. Our team reviewed the workflow, observed staff movements, and analyzed order timing. Initially, it was assumed that employees were working slowly, but after investigation we found the real issue was poor task allocation and lack of clear communication during rush periods. Once roles were reassigned and a clearer system was implemented, service time improved significantly. If the wrong root cause had been identified, it could have led to unfairly blaming staff and lowering morale, or investing in unnecessary equipment while the real problem continued. The most important transferable skills for conducting RCAs include critical thinking, observation skills, teamwork, communication, and the ability to analyze situations objectively without assumptions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-05 09:00:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3813029933</guid>
      </item>
      <item>
         <title>Daniel Jaya (301472770)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3814429424</link>
         <description><![CDATA[<p>During my microbiology lab, I realized that my Gram stain was incorrect. It’s supposed to come out purple, but when I look through the microscope, it’s bright pink. So, I decided to do a Root Cause Analysis instead.</p><p>My professor helped me with the 5 Whys technique:</p><p>Why was my sample pink instead of purple? Because the primary Crystal Violet stain didn't stay locked inside the cell walls during the procedure.</p><p>Why didn't the stain stay inside the cell walls? Because the decolorizer was left on the slide for too long, which stripped the purple dye out of everything.</p><p>Why did I leave the decolorizer on for so long? Because I was strictly following the lab manual, which told me to wait exactly 30 seconds before rinsing.</p><p>Why was 30 seconds too long for this specific slide? Because the bacterial smear I prepared was extremely thin. A thin layer of cells gets cleared by alcohol in about 5 seconds, whereas 30 seconds is only meant for a very thick, chunky smear.</p><p>Why didn't I know to adjust the timing based on the smear thickness? Because the lab protocol is written as a rigid one time rather than teaching us to watch for the visual endpoint, which is when the blue runoff from the slide turns clear.</p><p>So, the root cause isn't just that I'm clumsy; it's that the lab manual gave me one time instead of teaching me to look for a visual cue. Instead of just feeling bad about a student error, I can actually suggest a fix that we should update the manual to say stop when the liquid runs clear. That way, I'm not just fixing my mistake.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-06 05:01:07 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3814429424</guid>
      </item>
      <item>
         <title>Shreya(301493928)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3815581582</link>
         <description><![CDATA[<p>In my college life, I experienced something similar to a Root Cause Analysis during a group lab project. Our experiment results were completely different from what we expected, and at first we thought the chemicals were wrong. Instead of guessing, our group started checking each step of the procedure carefully. We reviewed the measurements, equipment setup, and timing of each step. After discussing it together, we realized the real root cause was that the incubator temperature had been set incorrectly, which affected the microbial growth in our samples. This experience showed me how important it is to find the real cause instead of just assuming the problem. If the wrong root cause is identified in a company, it can lead to serious problems. For example, the company might fix the wrong process, so the problem keeps happening again, which wastes time and money. Another outcome is that it could affect product quality or safety, which can damage the company’s reputation and customer trust. Some important transferable skills for people who conduct RCAs regularly include critical thinking, attention to detail, and good communication skills. These skills help teams analyze problems properly, discuss possible causes, and find the correct solution.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-07 06:58:46 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3815581582</guid>
      </item>
      <item>
         <title>Cassandra Sisto (301504927)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3815947276</link>
         <description><![CDATA[<p>While working as a junior chemist for a cosmetic company, I participated in a Root Cause Analysis (RCA) related to textural inconsistencies in a lipstick formulation. Some batches were reported to be grainy and less smooth during application. The investigation involved reviewing batch records, raw material specifications, and processing conditions. Using the 5 Whys approach, the team determined that the issue was linked to inconsistent cooling during the manufacturing process, which caused improper crystallization of wax components. Adjustments were made to the cooling step and process controls were implemented to ensure more consistent product texture.</p><p><br/></p><p>If the wrong root cause is identified during an investigation, the company may implement corrective actions that fail to resolve the underlying issue. For example, the organization might replace raw materials or change suppliers when the real problem lies in processing conditions. This can lead to continued product defects, customer complaints, and potential damage to the company’s reputation. Another possible outcome is wasted resources, including time, labour, and financial investment in unnecessary process changes while the actual problem persists.</p><p><br/></p><p>Several transferable skills are important for individuals who conduct RCAs on a regular basis. Analytical thinking is absolutely essential for systematically evaluating data, identifying patterns, and narrowing down possible causes. Attention to detail is also critical because small variations in procedures, documentation, or environmental conditions can contribute to quality issues. </p><p><br/></p><p>As well as this, I believe strong communication skills are necessary for gathering accurate information from team members, asking effective questions during investigations, and clearly presenting conclusions and corrective actions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-07 21:20:00 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3815947276</guid>
      </item>
      <item>
         <title>Simrandeep kaur 301490891 </title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816025116</link>
         <description><![CDATA[<p>Last month, I noticed my houseplants kept dying despite my careful watering. At first, I blamed myself for not having a "green thumb," but I decided to dig deeper using Root Cause Analysis. I asked "why" repeatedly and discovered the real issue: my pots had no drainage holes, so water collected at the bottom and rotted the roots. Once I transferred the plants to better pots, they thrived. </p><p>This experience showed me how identifying the wrong root cause can impact a company—for example, a bakery might retrain bakers for burnt cookies when the real issue is a broken oven, wasting money without solving the problem. Similarly, a restaurant could lose customers over salty food without realizing a new ingredient is the cause. T</p><p>he most important skills for conducting RCA are curiosity to keep asking "why," observation to look beyond the obvious, and open-mindedness to accept that the first answer is rarely the right one.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 02:28:03 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816025116</guid>
      </item>
      <item>
         <title>viral solanki (301494867)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816309748</link>
         <description><![CDATA[<p>During my work experience in a restaurant, I was once part of a small investigation when customers started receiving the wrong orders during a very busy shift. My supervisor asked the team what might have gone wrong. From my side, I explained that during rush hours we were handling many orders at the same time, and sometimes the order tickets were placed in the wrong order on the rack between the front counter and the kitchen. After discussing the situation with everyone, we realized that the main issue was miscommunication and poor organization of the order tickets. To fix the problem, we started double-checking order numbers before handing food to customers and made sure the tickets were arranged properly during busy periods.</p><p>If the wrong root cause is identified in an investigation, it can cause serious problems for a company. First, the real issue will continue to happen because the actual cause was never solved. This could lead to repeated mistakes and unhappy customers. Second, the company might waste time and money by implementing solutions that do not actually fix the problem, which can affect productivity and trust in the workplace.</p><p>I believe some of the most important transferable skills for people who regularly conduct Root Cause Analysis are critical thinking, communication, and attention to detail. These skills help someone carefully analyze what happened, ask the right questions, and work with others to find the real cause of the problem. These skills are very useful in many workplaces, especially in areas like quality control and food safety.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 13:06:58 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816309748</guid>
      </item>
      <item>
         <title>Sooyeon Kwak</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816393727</link>
         <description><![CDATA[<p>During my part-time job at a cafe, I participated in a Root Cause Analysis when we had to dispose of a large amount of milk foam because it spoiled faster than usual during the hot summer. Initially, we thought the milk itself was the problem, but through an RCA, we discovered that the frequent opening of the refrigerator during the humid summer was preventing the milk from staying at the required storage temperature. This experience taught me that identifying the wrong root cause can lead to financial waste by repeatedly replacing ingredients while the actual environmental issue remains. Furthermore, if the true cause of a quality drop is not found, it could lead to serious food safety risks and a loss of consumer trust if a spoiled product is accidentally served. Since then, even if the expiration date hasn't passed, I always check the freshness of the foam before preparing a menu item to ensure quality. To prevent such issues, I believe critical thinking and attention to detail are the most important transferable skills for anyone conducting an RCA.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 15:37:38 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816393727</guid>
      </item>
      <item>
         <title>Sreevee Narammagari ( 301498463)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816445740</link>
         <description><![CDATA[<p>During a busy shift at work, our team noticed that customer orders were taking longer than usual. At first, it seemed like the delay was because people were working slowly. However, instead of blaming anyone, we talked as a team to understand what was really causing the problem.</p><p>After discussing the situation, we realized that the main issue was poor communication and unclear task assignments during busy hours. Some team members were doing the same tasks while other tasks were being missed. Once we understood this, we decided to divide responsibilities more clearly and communicate better during busy times.</p><p>After making these changes, the workflow improved and customer orders were prepared faster. The team worked more smoothly, and the work environment became less stressful. This experience helped me understand how important it is to find the real cause of a problem before trying to fix it.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 17:21:14 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816445740</guid>
      </item>
      <item>
         <title>Kirandeep Kaur (301502603)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816464773</link>
         <description><![CDATA[<p>In one of my previous jobs in a food preparation area, our team noticed that some packaged items had the wrong expiry date printed on their labels, due to this they had to be discarded to avoid any food safety risk. The supervisor asked us to review the issue using a simple Root Cause Analysis to understand why the error happened. Our task was to find the real reason of the problem without blaming anyone. We carefully looked at the labeling process step by step and used questions similar to the “5 Whys” method. During the investigation, we found that the label printer had reset the previous evening and the date setting was not updated, so the machine printed the wrong expiry date. Because staff trusted the machine settings, no one double-checked the date before printing. After identifying the root cause, a checklist was added requiring employees to verify the machine date at the start of each shift, which prevented the issue from happening again. If the wrong root cause were identified in an investigation, it could negatively impact a company because management might blame employees and provide unnecessary training while the real problem (such as equipment malfunction) continues, or the company could lose money by fixing the wrong issue while product waste or safety risks keep occurring. People who regularly conduct Root Cause Analysis need strong transferable skills such as critical thinking to analyze problems logically, communication to gather information from different team members, and attention to detail so small process errors are not missed.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 17:59:26 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816464773</guid>
      </item>
      <item>
         <title>Rodrigo (301424952)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816473826</link>
         <description><![CDATA[<ol><li><p>While working on egg wholesale, one restaurant reported to us, that part of the product was being crushed, easing the spoilage of a fraction of the product. We conduct a RCA as we always promise our customer the best quality possible, we found that the person responsible for the poor quality of the product was the truck driver that was always throwing heavy stuf on top of the egg boxes, so the fine or penalty wasn´t on our side.</p></li><li><p>RCA is pretty important for a company because it is a way to find all the possible paths that may be causing a problem, ensuring a quick solution by avoiding losing time on unrelated stuff. While also lead to a documentation of the problem in order to track it faster or prevent it from happening again.</p></li><li><p>Critical thinking, document control, data analysis.</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 18:20:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816473826</guid>
      </item>
      <item>
         <title>Aaron Abdool 301316583</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816489766</link>
         <description><![CDATA[<p>When I was first promoted to supervisor at my retail job, one of my first tasks was to examine why associates were seemingly dumping items in the warehouse, where they did not belong. We asked associates why they tended to leave items on carts in the back, and the answer was they were unclear as to where items went. Looking into why it was unclear, it was evident that the current signage for storage was not impactful enough, as well as the warehouse in general being very crowded. New signage and training for associates were provided to mitigate this issue. </p><p><br/></p><p>Identifying the wrong root causes the problem to reoccur. Secondly, this costs the company time and effort, which in business is money.</p><p><br/></p><p>Critical thinking, attention to detail, and communication are vital for those who conduct RCA's. They must first look deeper into the problem as well as circumstances around the issue, as well as communicate effectively with those it affects.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 18:55:19 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816489766</guid>
      </item>
      <item>
         <title>Andrea Collado (301133286)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816501234</link>
         <description><![CDATA[<p>During my time working as a QA technician, I participated in a Root Cause Analysis investigation after noticing a documentation issue during a routine review of metal detection records. I saw that one of the labels attached to the record used an outdated company logo instead of the current approved version. Our team wanted to determine why this happened and whether it affected any products. We reviewed the process and spoke with the employees involved, and we discovered that older label stock had been left at the workstation and was accidentally still being used. Once we identified the cause, the outdated labels were removed and replaced, and the team improved workstation checks to prevent it from happening again.</p><p><br/></p><p>If the wrong root cause is identified during an investigation, it can create several problems for a company. One outcome is that the real issue may continue to occur because the corrective actions are targeting the wrong problem. For example, a company might retrain employees when the real issue was actually outdated materials or equipment being used. Another outcome is wasted time and resources. Companies might spend time implementing unnecessary procedures or changes that do not actually solve the problem, which can affect productivity and trust in the quality system.</p><p><br/></p><p>Some important transferable skills for conducting RCAs include critical thinking, attention to detail, and strong communication. These skills help investigators carefully analyze situations, gather accurate information from team members, and identify the true cause of a problem so effective solutions can be implemented.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 19:21:28 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816501234</guid>
      </item>
      <item>
         <title>Khang Lieu (301146717)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816547936</link>
         <description><![CDATA[<p>During one of my food analysis lab our team noticed that the results from a food sample test were inconsistent compared with previous trials. Accurate results are important for evaluating product quality, we decided to review the procedure and conduct a simple Root Cause Analysis. The purpose to understand why the variation happened without assuming the cause. We carefully checked each step of the method, including sample preparation, equipment setup, and measurement procedures. After reviewing the process, we discovered that the analytical balance had not been calibrated properly before weighing the sample, which affected the accuracy of the measurements. Once the balance was calibrated and the equipment not fully clean before using and the test was repeated, the results became consistent and reliable.</p><p>If the wrong root cause is identified during an investigation, it can create serious problems for a company. For example, management might blame employees and provide additional training when the real issue is equipment malfunction or a process failure. As a result, the problem will continue to occur. Another outcome is that the company may spend time and money fixing the wrong issue, which can lead to product waste, production delays, or even food safety risks.</p><p>Individuals who conduct Root Cause Analysis regularly need several important transferable skills. Critical thinking helps them analyze problems logically and identify the real cause instead of assumptions. Attention to detail is important to detect small process errors that may lead to larger problems. Communication and teamwork are also essential because investigators often need to collect information from different employees and departments to understand what happened.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 21:12:22 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816547936</guid>
      </item>
      <item>
         <title>Harshdeep Kaur (301502835)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816558107</link>
         <description><![CDATA[<p>One of the times I engaged in an informal Root Cause Analysis (RCA) at a former place of work was whenever we realized that there was a common problem with food waste. The team initially believed that the root cause of the issue was that of over-ordering, however, following the investigation into the fridge, we quickly found out that the actual root cause of the problem was the absence of an appropriate rotation system. Older items in the back were expiring undetected as new deliveries were being pushed to the front. Immediately, as soon as we introduced a rule of First-In, First-Out (FIFO) and relocated older inventory to the front, all the waste was eliminated.</p><p>Detecting the false root cause can have drastic effects on a company. As an illustration of this, when the manager wrongly faults a slow process on lazy employees, he will spend money on unwarranted training yet the actual issue will be the faulty equipment. Second, it results in low morale since employees feel frustrated when they are coerced to employ solutions that will not exactly solve the problem at hand.</p><p>In my opinion, the critical thinking and effective communication are the most significant transferable skills in conducting RCA. You have to be capable of seeing beyond the surface states of the symptoms of the problem and you have to be capable of communicating with other people without causing them to feel accused of something so that they are willing to tell you the truth.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 21:38:09 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816558107</guid>
      </item>
      <item>
         <title>Ayomide Olaegbon (301313995)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816583179</link>
         <description><![CDATA[<ol><li><p>While working as kitchen staff, I once took part in a situation that required a root cause analysis. During a busy service period, several food orders were coming out late and customers were waiting longer than usual. Instead of immediately blaming any staff member, the team decided to look deeper into what was causing the issue. We asked questions about the process and tried to understand where the delay was really happening. After discussing it as a team, we realized the main problem was that some ingredients were not fully prepared before service started. The storage area was also disorganized, which made it harder to quickly find what we needed. Once we identified the real cause, we improved our preparation routine before each shift and organized the storage space better. This helped the kitchen run more smoothly and reduced delays during busy hours.</p></li><li><p>If the wrong root cause is identified, it can create several problems for a company. One impact is that the real issue will continue because the company is trying to fix the wrong problem. For example, management might think employees need more training when the actual issue is a problem with equipment or workflow. Another impact is wasted time and resources. A company might invest money or effort into solutions that do not actually solve the problem, which can lower productivity and cause frustration among employees.</p></li><li><p>People who regularly conduct root cause analyses need strong problem-solving skills, good communication, and attention to detail. These skills help them gather the right information, ask useful questions, and understand what is really happening in a process. For example, while working in the kitchen, attention to detail is important when checking food preparation steps, storage, and timing. If something goes wrong, such as food being delayed, good communication and problem-solving skills help the team discuss what happened and figure out the real cause so the same problem can be prevented in the future.</p></li></ol>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-08 22:41:33 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816583179</guid>
      </item>
      <item>
         <title>APARNA SAJIMON(301412779)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816641146</link>
         <description><![CDATA[<p>A few years ago, I had an experience at home that felt a lot like a mini Root Cause Analysis. Someone had eaten the leftover dessert I was saving in the fridge, and I had to figure out who it was. I asked questions, looked at who had been in the kitchen recently, and noticed a few crumbs in one of my roommate’s dishes. By piecing together the evidence, I realized it wasn’t intentional they just didn’t know it was mine. The outcome was that we started labeling our food, which solved the problem going forward. It was a small example, but it really showed me how gathering facts and analyzing them carefully can solve a problem efficiently.</p><p>I think if the wrong root cause is identified in a professional setting, it can have serious consequences. For example, a company might spend resources fixing the wrong problem, which wastes time and money. Or a safety issue might go unresolved, putting employees or customers at risk. Both outcomes could have been prevented with a proper investigation.</p><p>From this experience, I realized that some key transferable skills for RCA are attention to detail, critical thinking, and effective communication. You need to gather accurate information, analyze it without jumping to conclusions, and then clearly explain your findings so the right corrective actions can be taken. Even though my “investigation” was small and personal, it really gave me insight into how root cause analysis works in larger, more complex situations.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 00:14:52 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816641146</guid>
      </item>
      <item>
         <title>Norberto Chinchillas Ponce (301336026)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816701294</link>
         <description><![CDATA[<p>One time during our food science project 2 class we had found unexpected mould growth in our product, something which was the opposite of what was supposed to happen, so after looking at all the possibilities in an RCA we realized that the solution hadn't been autoclaved and that led to the growth of microorganisms.</p><p>If a company makes a mistake during their RCA, this could lead to them only addressing the symptoms of the real problem or not addressing it at all, which can lead to a loss of capital, time, and effort.</p><p>I would say that the main transferable skills needed for RCAs are attention to detail and good problem-solving skills, as these skills are what make narowing down the root cause of problems possible.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 00:59:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816701294</guid>
      </item>
      <item>
         <title>AKHIL REDDY 301434064</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816854858</link>
         <description><![CDATA[<p>1.At Domino’s, we once had an issue where customer orders were being delayed during peak hours. I participated in a Root Cause Analysis to find out why. By observing the workflow, checking order prep times, and talking to team members, we discovered that the real issue was a bottleneck at the pizza assembly station, not the oven as initially assumed.</p><p><strong>2. </strong><br>If the wrong root cause is identified, the store might waste time and resources fixing something that isn’t the real problem, like replacing ovens unnecessarily. It could also lead to repeated delays, unhappy customers, and decreased team efficiency.</p><p><strong>3. </strong><br>Important skills include critical thinking, attention to detail, problem-solving, teamwork, and clear communication to explain findings and implement the correct solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 02:54:53 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816854858</guid>
      </item>
      <item>
         <title>YASHRAJSINH ADMAR (301495082)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816873057</link>
         <description><![CDATA[<p>One experience I had with a Root Cause Analysis was during a laboratory activity in my biotechnology program. During one experiment, our results were inconsistent compared to other groups. Instead of repeating the experiment immediately, we discussed possible causes and reviewed each step of the procedure. After checking the materials and techniques used, we realized the issue was caused by improper aseptic technique that allowed contamination. Identifying the root cause helped us correct the procedure and obtain accurate results in the next trial.</p><p>If the wrong root cause is identified in an investigation, it can negatively impact a company. First, the real problem will remain unresolved, which can lead to repeated errors or product defects. Second, it can waste time and resources because the company may implement solutions that do not actually fix the problem.</p><p>The most important transferable skills for individuals who conduct Root Cause Analysis include critical thinking, attention to detail, and problem-solving. Communication skills are also important because team members must clearly discuss observations and possible causes to reach the correct conclusion.</p><p><br/></p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 03:08:49 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816873057</guid>
      </item>
      <item>
         <title>SHONE PETER (301484047)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816904549</link>
         <description><![CDATA[<p>One situation where I experienced a Root Cause Analysis was during a food preparation setting where a quality issue happened. Some food items were not stored at the correct temperature, which could have affected food safety. During the investigation, the team reviewed the storage procedures, checked the equipment, and looked at how the temperature was being monitored. After reviewing everything, it was found that the main cause of the problem was that the refrigerator temperature was not being checked regularly. To solve this, better monitoring practices and staff reminders were put in place to prevent the issue from happening again.</p><p>If the wrong root cause is identified, it can create problems for a company. For example, the company might take the wrong corrective action, which means the original problem will continue to occur. Another possible outcome is financial loss, because the company may spend time and money fixing something that is not actually causing the issue.</p><p>In my opinion, some important skills needed for people who conduct Root Cause Analysis are critical thinking, attention to detail, and good communication. These skills help people carefully analyze a situation, identify the real problem, and work with others to find the right solution.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 03:29:05 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816904549</guid>
      </item>
      <item>
         <title>Taniya Salaria (301478723)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3816977213</link>
         <description><![CDATA[<p>·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In a previous role, I participated in a Root Cause Analysis after a recurring operational issue caused delays in a routine workflow. To maintain confidentiality, I won’t mention any company or product names, but the investigation involved mapping the process, gathering data, and using tools like the 5 Whys to understand why the issue kept happening. Although some people initially assumed the problem was due to human error, the RCA revealed that the true cause was a missing verification step in the process design. Once that gap was fixed, the delays decreased significantly, showing how valuable a structured RCA can be.</p><p>·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Identifying the wrong root cause can have serious consequences for a company. One major impact is wasted resources—time, money, and labour may be spent fixing the wrong thing, retraining staff unnecessarily, or replacing equipment that isn’t actually the problem. Another impact is that the issue will continue to recur, which can damage internal trust, reduce productivity, and even harm customer confidence if the problem affects product quality or service reliability.</p><p>·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Individuals who conduct RCAs regularly rely on several important transferable skills. Critical thinking is essential because they must separate assumptions from evidence and analyze problems objectively. Strong communication skills are also crucial, as RCA investigators need to ask clear questions, collaborate with different teams, and present findings in a way that others can understand. Attention to detail, data interpretation, and systems thinking also play key roles in identifying how different parts of a process interact and where failures originate.</p><p>&nbsp;</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 04:36:48 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3816977213</guid>
      </item>
      <item>
         <title>Joyal Poulose (301358834)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3817795476</link>
         <description><![CDATA[<p>In one of courses, my group had mixed results in one of the experiments. As a way of investigating the issue, we inspected the whole process, examined the materials that were employed and examined the manner in which the equipment was being handled. We had a discussion on the steps after which we found the measuring equipment has not been calibrated appropriately. After calibration was done again, we performed the experiment and got valid results. When the root cause is determined incorrectly, this may have a bad impact on an enterprise. As an example, the firm can use the incorrect corrective action and the problem will persist. It is also associated with end up wasting time and resources in attempts to correct an issue that was not the cause. Other vital skills in the implementation of the Root Cause Analysis are critical thinking, attention to details and effective communication. The skills assist the teams to explore issues and locate the right cause. </p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-09 15:00:59 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3817795476</guid>
      </item>
      <item>
         <title>Akhil Raj Chand Sithara 301404846</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3818587342</link>
         <description><![CDATA[<p><br>During a class activity in my Food Science Technology program, I participated in a Root Cause Analysis for a food safety issue in a simulated production process. Our team reviewed process steps, checked records, and used the <strong>5 Whys</strong> method to identify possible causes. We found that improper handling at one stage of the process was the main issue. We then suggested corrective actions such as improving procedures and strengthening employee training.</p><p>If the wrong root cause is identified, the real problem may continue and happen again. For example, a company may fix equipment when the real issue is poor handling practices. Another outcome could be financial loss and damage to the company’s reputation due to repeated product issues or recalls.</p><p>Important skills include critical thinking, attention to detail, problem solving, and clear communication. These skills help investigators properly analyze problems and explain their findings and solutions.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-10 02:46:21 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3818587342</guid>
      </item>
      <item>
         <title>Nikhil Kunnath Shaji(301280978)</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3819823679</link>
         <description><![CDATA[<p>During my co-op as a QA technician in a food production facility, I was involved in a root cause analysis after a foreign material was detected during my routine line check. The material was small and black, and it was observed at the baking stage. Since there were no ingredients in the product formulation that matched this material, the investigation began by checking the entire production process starting from mixing, proofing, and baking. We inspected equipment surfaces and components to determine whether the foreign material came from equipment wear or damage.</p><p>During the investigation, we noticed a piece of black rubber under a roller in the proofer conveyor, but after inspection it was determined that it could not enter the product path. Maintenance also inspected other equipment, including the divider, where some black material was present, but it did not match the foreign material found in the product. After continuing the investigation and observing the surrounding area, we identified a damaged plastic pallet used in the mixing area that had fraying pieces. The material matched the foreign material detected in the product, confirming it as the root cause.</p><p>If the wrong root cause had been identified, the company might have implemented incorrect corrective actions. For example, unnecessary repairs could have been made to production equipment, leading to downtime and financial loss, while the actual issue would remain unresolved. Additionally, the foreign material contamination could have continued to occur, potentially leading to product recalls or damage to the company's reputation. From this experience, I believe the most important transferable skills for conducting root cause analysis include attention to detail, systematic investigation, critical thinking, and effective communication with cross-functional teams such as maintenance and production.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-10 17:38:05 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3819823679</guid>
      </item>
      <item>
         <title>Abinaiyaah 301364066</title>
         <author></author>
         <link>https://padlet.com/yhenry1/BI321YourRCA/wish/3822161226</link>
         <description><![CDATA[<p>I have participated in a Root Cause Analysis investigation during my work experience in a food service environment when there was an issue related to temperature monitoring in food storage. Some temperature logs were not being recorded consistently, which could potentially affect food safety. During the investigation, the team reviewed the procedures, checked the equipment, and discussed the process with staff members. The root cause was identified as a lack of clear understanding and training regarding the importance of temperature logging, so additional training and clearer instructions were provided to improve compliance. If the wrong root cause is identified during an investigation, it can negatively impact a company in several ways. First, the actual problem will remain unresolved, which may lead to repeated issues such as food safety incidents or product defects. Second, the company may waste time, money, and resources implementing corrective actions that do not solve the real problem. To conduct Root Cause Analysis effectively, several transferable skills are important, including critical thinking, attention to detail, and strong problem-solving abilities. Communication and teamwork skills are also essential because investigations often require collaboration between different departments, while organizational and analytical skills help ensure the investigation process is accurate and well-structured.</p>]]></description>
         <enclosure url="" />
         <pubDate>2026-03-12 03:13:12 UTC</pubDate>
         <guid>https://padlet.com/yhenry1/BI321YourRCA/wish/3822161226</guid>
      </item>
   </channel>
</rss>
