TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Education

    The SafetyPro Podcast

    No management theory, platitudes, or guru speak – just actionable workplace safety and health info you can use right now.

    Advertise

    Copyright: © 2014-2021

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    082: SMS Pt 3 - What is Root Cause Analysis (RCA)? Oct 25, 2019
    Show notes

    Powered by iReportSource As mentioned in episode 81 - What is "Systems Thinking," I will talk about root cause analysis or RCA - another aspect of a systems approach, Let's define it and talk about how it can be applied. In episode 33: Lean Safety, I recommended some excellent books to help you out. TapRoot® is another great resource as well as the book Pre-Accident Investigation by Todd Conklin - I have this one and contains great insight. But remember, whatever books you read or concepts you follow, if all you get is a strategic overview of these principals, then you will need to follow that up with tactical training to be able to use the right tools and techniques for a given situation. For example, I went through HOP training, was a H.O.P. coach for a former employer, so jump on Linkedin and ask your network how they are applying these concepts, ask for help. One thing I want to share about Conklin's book that has stuck with me (there is a lot, but this one is a favorite); "Safety is not the absence of events; it is the presence of defenses." So true! So Let's get into a definition of RCA. First, I want to reference TapRoot®. Over 30 years ago, they started with research into human performance and the best incident investigation and root cause analysis systems available. They put this knowledge to use to build a systematic investigation process with a coherent investigation philosophy. Then, they used and refined the system in the field. In 1991, they wrote the first TapRoot® Manual that put all of this experience together into an incident investigation system called TapRoot®. According to TapRoot®, a definition of Root Cause Analysis is as follows: "The systematic process of finding the knowledge or best practice needed to prevent a problem." What root cause analysis tools or methods should you use? Here is guidance to help you pick the root cause analysis system you should use: You need to understand what happened. Because you can't understand WHY an incident occurred if you don't understand HOW it happened, and before that, you need to know what happened. You need to identify the multiple Causal Factors (this is the HOW) that caused the problem (the incident). Your root cause analysis system should have tools to help you identify these points that will be the start of finding root causes. You will need to dig deeper and find each of the Causal Factor's root causes. These are the causes of human performance and equipment reliability issues. TapRoot, with many years of experience, has found that investigators (even experienced investigators) need guidance – an expert system – to help them consistently identify the root causes of human performance and equipment reliability issues. This guidance should be part of the root cause analysis system. Plus, the root cause analysis tool must find fixable causes of human error without placing blame. Blame is a major cause of failed root cause analysis. If this is a major issue, you should go beyond the specific root causes of this particular incident. For major investigations, you should look one level deeper for the Generic (systemic) Cause of each root cause. Not every root cause will have a Generic Cause. But, if you can identify the Generic Cause of a root cause, you may be able to develop corrective action that will eliminate a whole class of problems. Thus, your systematic process should guide you to find Generic Causes for major investigations. Root cause analysis is useless if you don't develop effective corrective actions (fixes) that will prevent repeat incidents. TapRoot has seen that investigators may not be able to develop effective fixes for problems they haven't seen fixed before. Therefore, your root cause analysis system should have guidance for developing effective fixes. Finally, you will need to get management approval to make the changes (the fixes) to prevent repeat problems. Thus, your root cause analysis system should include tools to effectively present what you have found and the corrective actions to management so they can approve the resources needed to make the changes happen. Another take on this is that RCA involves investigating the patterns of adverse effects, finding hidden flaws in the system, and discovering specific actions that could have contributed directly and indirectly to the problem. Which often means that RCA reveals more than one root cause. And thus the title lends itself to criticism by some folks - it implies one root cause when we know that isn't the intent. I call these folks word nerds, and these are the Gurus I refer to when I point this out - not the ones I mentioned earlier that understand this. They take the literal meaning instead of using their brains a little and understanding that it is just a catchphrase, and the purpose or spirit of the phrase is what is essential. The second example of an organization focused on this topic; ASQ. The American Society for Quality (ASQ), formerly the American Society for Quality Control (ASQC), they are a knowledge-based global community of quality professionals, with nearly 80,000 members dedicated to promoting and advancing quality tools, principles, and practices in their workplaces and communities. According to an ASQ article published back in 2004: "Simply stated, RCA is a tool designed to help identify not only what and how an event occurred, but also why it happened. Only when investigators can determine why an event or failure occurred will they be able to specify workable corrective measures that prevent future events of the type observed. Understanding why an event occurred is the key to developing effective recommendations. Imagine an occurrence during which an operator is instructed to close valve A; instead, the operator closes valve B. The typical investigation would probably conclude operator error was the cause. This is an accurate description of what happened and how it happened. However, if the analysts stop here, they have not probed deeply enough to understand the reasons for the mistake. Therefore, they do not know what to do to prevent it from occurring again. In the case of the operator who turned the wrong valve, we are likely to see recommendations such as retrain the operator on the procedure, remind all operators to be alert when manipulating valves, or emphasize to all personnel that careful attention to the job should be maintained at all times. Such recommendations do little to prevent future occurrences. Generally, mistakes do not just happen but can be traced to some well-defined causes. In the case of the valve error, we might ask, "Was the procedure confusing? Were the valves clearly labeled? Was the operator familiar with this particular task?" The answers to these and other questions will help determine why the error took place and what the organization can do to prevent a recurrence. In the case of the valve error, recommendations might include revising the procedure or performing procedure validation to ensure references to valves match the valve labels found in the field. Identifying root causes is the key to preventing similar recurrences. An added benefit of an effective RCA is that, over time, the root causes identified across the population of occurrences can be used to target major opportunities for improvement." So this is why the battle against the word "why" confuses me (see, I cannot even avoid using the word in that statement!) - I mean, I get that it can be used negatively, as in "why did you do that?" Tone and inflection play into this a lot, as well. But we know that it isn't the reason for asking, nor is it how we should ask the question. I mean, if you have ever heard a child ask "why" (and repeats it 25 times!), then you probably know that it is merely an attempt to understand the world around them. We don't discourage children from learning more about the world around them by asking "why," but we do as adults for some reason, and as adults, we are supposed to be smarter than that; able to use logic and reason - you think we would have figured that out. So instead of hating on the word why, then shouldn't we spend more time training and education on the proper use of it? Let me illustrate the use of "why" with an example not related to workplace safety. Simon Sinek, best known for popularizing the concept of WHY (and wrote the book "Start with Why") in his first TED Talk in 2009, the third most popular TED video of all time. He talked about the importance of why, before the how or what. He gave an example of Apple; why is it they are so much more successful than other tech companies? They have access to the same talent pool, same consultants, same media. So what makes them so special? You wouldn't explain this by describing what they make, or how they make those items - but the why gets to their core purpose, which then determines how they make what they make. Remember the TapRoot® or ASQ approach? Sound familiar? Ok, so you might be saying that the context of the Ted Talk is completely different when it comes to workplace incidents or accidents. Maybe, but in both cases, asking why is meant to seek a deeper understanding of potential drivers or root causes, rather than explaining how something happened or even simply describing what happened in a single word or phrase. For example: What happened: There was a fire in the furnace room. How it happened: Combustible materials were stored too close to the furnace. Why it happened: We have not established a fire prevention program or an effective housekeeping program, updated roles/responsibilities, assigned accountability, conducted/tracked training, developed a tracking system, inspected/audited, and reviewed to ensure it was being followed/maintained. So use the word why, don't use the word - as long as you seek to get a deeper understanding as to all of the potential contributors to an incident. It is important to define this topic accurately because it is crucial to continuous process improvement - the foundation of a safety management system, which kicked this whole series off a few episodes ago. Final Thoughts Before I wrap this up, let me say for those criticizing traditional RCA, claiming it doesn't get it done, likely do not fully understand root cause analysis, or they are peddling something - their book or training course. Or they could just be taking the term literally when most of us are using it to describe ALL of the things we need to do to "root out" all of the potential contributors (causal factors) to failure. See, everyone gets hung up on the words. I mean yes, they matter to an extent. But someone with a high EQ, incredibly self-aware will be able to understand the context. And we should expect that in our profession. I have even read posts saying things like, "don't start at the end of the event and work back because there will be bias. Start at the beginning and work forward" - but if this approach is based on the fact that humans are flawed and will bring bias into the investigation (since we already know what happened), don't you think those same flaws (biases) will be present regardless of where you start? Of course, they will. So we must focus on how we go about investigations - in this case, objectivity is the critical component. Besides, we were likely trained this way - for recordable injuries look at the old OSHA 301 form; the very first question is NOT "What happened, starting with the event." It is "What was the employee doing just before the incident occurred? Describe the activity, as well as the tools, equipment, or material the employee was using. Be specific." So yeah, start BEFORE the event. Oh, and by the way, starting at the beginning is but ONE technique, ONE approach, it still gets to potential root causes and is, therefore, a root cause analysis tool. There are other types of incidents where you may need to start with the current-state and walk backward. I am reminded of my old fire days. If there were a fire and no one was around, are you going to ask the fire how it started its day? If you happen to have video available, guess where you are going to start - the point at which you see the first sign of smoke or flames. Working backward, in this case, might be needed to establish a timeline - from there, you can determine at what point in the process it started, what stage of the cycle the process was in, time of day, environmental conditions or temperature at the time, etc. The reason you are investigating will also drive how you approach the investigation, as well as the tools and techniques you use, in the case of criminal investigations, insurance, fraud or liability investigations, for example. In the 1988 edition of Modern Accident Investigation Analysis, Ted S. Ferry has several chapters breaking down various aspects of accidents that need to be investigated. Among them are Chapter 4: Human Aspects; Chapter 7: Systems Investigation; Chapter 14: Where Did Management Fail? - and all along the way, discussing the relationship between people, environment, and systems. We have come a long way in many areas, but one thing is sure; we have known for a long time that this approach - a systems approach, looking at all aspects, is the best way to truly root out all potential contributors so that we may make smarter decisions moving forward. Ferry writes: "Mishaps are a sign of inefficient operations and poor operating practices. We can conclude that a good investigation will uncover, among other things, management practices or oversights that have contributed to the mishap." We can even go way back to the 1960s, to the MORT Process, which defines a mishap as "the unwanted transfer of energy that produces injury to persons, damage to property, degradation of an ongoing process, and other unwanted losses." MORT is based on the concept that all accidental losses arise from two sources: (1) specific job oversights and omissions, and (2) the management systems factors that control the job. It is frequently used to solve other management problems, as well. I could go on, but I think you get my point. Become a student of these approaches. Learn about the history of these topics. Our industry will continue to adapt as we learn more about the interactions humans have with systems and organizations. But I wanted to tackle this topic since it is so critical to supporting a safety management system and how we execute this, Root Cause Analysis, will drive every improvement we make to our people, processes, policies/procedures and how leaders continue to develop the sense through which they view their businesses. I want to hear your take - how do you use continuous process improvement and RCA to support your safety management system? Have you struggled with any of the tools? Are you confused about which tools are ideal for which situations or problems for which you are trying to solve? Let me know - reach out via LinkedIn or shoot me an email. Send emails to info@thesafetypropodcast.com. You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter

    Full show notes at the publisher

    081: SMS Pt 2 - Systems Thinking, Continuous Process Improvement, PDCA Oct 22, 2019
    Show notes

    Powered by iReportSource

    In this episode, I continue my series breaking down Safety Management Systems (SMS) and will talk about Continuous Process Improvement. Before I can do that, we need to understand something else about SMS - In episode 80 of The SafetyPro Podcast, Safety Management System (SMS) Defined, I talked about how you need to move away from individual programs and toward a systems approach to safety management. Well, there is something called systems thinking, and we are going to get into what that is and how you can shift not only the way you look at managing safety but also how your organization can make the shift from managing programs to integrating safety within the rest of the business by using systems thinking.

    I recently came across an interesting article over at The Systems Thinker written by Micheal Goodman, and I thought it would help safety pros better understand what system thinking is all about. Michael is an internationally recognized speaker, author, and practitioner in the fields of Systems Thinking, Organizational Learning, and Leadership. The article is called SYSTEMS THINKING: WHAT, WHY, WHEN, WHERE, AND HOW? He writes:

    "The discipline of systems thinking is more than just a collection of tools and methods – it's also an underlying philosophy. Many beginners are attracted to the tools, such as causal loop diagrams, in hopes that these tools will help them deal with persistent business problems. But systems thinking is also a sensitivity to the circular nature of the world we live in; an awareness of the role of structure in creating the conditions we face; a recognition that there are powerful laws of systems operating that we are unaware of; a realization that there are consequences to our actions to which we are oblivious.

    Systems thinking is also a diagnostic tool. As in the medical field, effective treatment follows a thorough diagnosis. In this sense, systems thinking is a disciplined approach for examining problems more completely and accurately before acting. It allows us to ask better questions before jumping to conclusions.

    Systems thinking involves moving from observing events or data, to identifying patterns of behavior over time, to surfacing the underlying structures that drive those events and patterns."

    So you can see how this sets us up for moving away from merely managing programs toward a systems approach to safety. We need to understand the relationships the individual safety programs have with other areas of the business - how people think, feel, and behave when interacting with them.

    It is also essential to understand that when we use the term system, it implies that the entire business is a single system and composed of many related subsystems. An accident occurs when a human or a mechanical part or multiple parts of the system fails or even just malfunctions. The system safety approach reviews the accident to determine how and why it occurred and what steps could be taken to prevent a recurrence. The goal of a systems approach is to produce, you guessed it, a safer system.

    Therefore, at a minimum, a safety system is a formal approach to eliminate or control hazardous events through engineering, design, education, management policy, and supervisory oversight and control of conditions (environment) and practices, the organizational policies, practices, and overall organizational culture, etc. Notice I included the human and organizational aspects? Yes, traditional systems safety does address these areas.

    In episode 80 of this podcast, I also talked about how SMS is a continuous improvement process that reduces hazards and prevents accidents. So what is a Continuous Improvement Process exactly? And how does it help us improve safety? Simply put, it is an ongoing effort to improve products, services, or processes. Or put another way; a recurring activity or activities to enhance performance. Typically, the goal is for "incremental" improvement over time and, in some cases, significant improvements all at once.

    So once again, I will use Lean principles to explain this concept. First, I want to start with some structure, which will lead to this concept of continuous improvement. There is a term known to Lean practitioners; Kaizen. The Japanese word kaizen simply means "change for better" and refers to any improvement, either a one-time deal or a continuous process, either large or small, in the same sense as the English word "improvement." So when you hear the phrase "Kaizen Event" - that simply means an improvement event.

    The most well-known example of a Kaizen approach is the Toyota Production System, or TPS, where everyone is expected to stop their moving production line in case of any abnormality and, along with their supervisor, suggest an improvement to resolve the abnormal issue. This will initiate a cycle of activity aimed at not merely fixing that one issue, but instead improving the overall process to prevent the issues from repeating. This cycle can be defined as: "Plan → Do → Check → Act."

    PDCA (Plan-Do-Check-Act) is a scientific method of problem-solving and involves a 4-stage, iterative cycle for improving processes, products or services, and for resolving problems. It involves systematically testing possible solutions, assessing the results, and implementing the ones that have shown to work. It is a rather simple and effective approach for solving problems as well as for managing change.

    This is because it enables businesses to develop hypotheses about what needs to change, test these hypotheses in a continuous feedback loop, and gain valuable learning and knowledge. Again, the value here is that you are testing improvements on a small scale before trying to apply them company-wide. The PDCA cycle consists of four components and can be applied to safety management systems as follows:

    Plan – Identify and assess risks and opportunities to establish objectives and processes needed to solve them. There are 3 steps to this part:

    1. Problem Identification - verify you identified the right problem, determine its impact, who will it benefit?
    2. Problem Analysis - what information is needed to understand the problem and its root cause fully? What do we already know about the problem? What do we need to collect to understand the problem further? Who needs to be involved in this process? Once we get a full understanding, is it even feasible to solve the problem?
    3. Run Experiments - What are all possible solutions (think of 3 options)? Who will "own" which options to test? How will we measure expected outcomes? Can we run a small test? Will the small-scale results scale up?

    Do – Here is where we develop and implement our tests and gauge their effectiveness. Again, this should be done on a small-scale to allow us to learn quickly, adjust as needed, and are typically less expensive to undertake. It also lessens any potential negative impact on the business. Think of the phrase, "fail small." It also will have a less negative impact on the culture as a large-scale test, and failure might make workers feel defeated or that no solutions are coming. And be sure to collect all data needed so you can objectively decide which ones are best.

    Check – Here is where we confirm the results through before-and-after data comparison. What worked? How can you tell? Also, look at what did NOT work - this may help you look back at your planning stage to see what you missed or did not consider. Remember, this is a cycle, even between the stages. So try not to think of this linearly. You may discover that the solution is no longer viable, or that there are simpler ones you had not considered.

    Act – Here is where you will document the results and make recommendations for future PDCA cycles. If the solution was successful, implement it. If not, tackle the next problem and repeat the PDCA cycle. Remember, you can always stop and back up a step or go to the beginning. Learning is the objective here. So now you can start to ask what resources are needed to blow up the solutions company-wide? What impact will there be on production? Things like retraining, replacing equipment, parts, etc. Closing a part of a building, or the area will all need to be considered as well.

    This PDCA process is critical to safety management systems for obvious reasons. Kaizen focuses on applying small, everyday changes that result in significant improvements over the long run if done correctly. The PDCA Cycle gives you the framework and structure needed for identifying improvement opportunities and evaluating them objectively. So when you hear folks talk about a systems approach to safety management, and the need to apply a process of continuous improvement, this is it.

    In doing so you will be able to create this culture of problem-solvers, critical thinkers and folks that step up to tackle issues; willing to take on the accountability because the process to do it is easy and yields results by taking the focus off the person and on the process when it comes to problems that arise. Improvement ideas can be tested on a small scale, analyzed, tweaked, and repeated until solved.

    By going through this process, and understanding systems thinking, you can start to see that you need to look at both individual components of your safety program and also the interactions with other areas of the business - the system as a whole. You cannot just do one. What I am saying is that yes, you need to find root causes to mechanical failures, "why" it occurred, but you also cannot ignore the "how" it was able to occur organizationally as well. If you reverse this thinking, start with "how" as some of these gurus want you to believe, it will still require you to find out the "why." You need to be able to both.

    So, in the next episode, I will continue to break down safety management systems by answering the question; What is Root Cause Analysis or RCA? I will explain how it is critical to support systems thinking, a systems approach to safety, and even talk about how it has been redefined by some in our industry to sell books, training courses and prop themselves up as thought leaders when in reality, it's all the same stuff.

    Send emails to info@thesafetypropodcast.com. You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter


    080: SMS Pt 1 - Safety Management System Defined Oct 15, 2019
    Show notes

    Powered by iReportSource

    A safety management system (SMS) is a continuous improvement process that reduces hazards and prevents incidents. It protects the health and safety of your employees and should be integrated into everyday processes throughout the organization. Investing in an SMS makes a measurable impact on your bottom line and can be viewed as a competitive advantage.

    The adoption of an SMS framework and thoughtful implementation of the various pieces can have a significant impact on protecting employees and enhancing your organization's performance and profitability. Now, safety requirements may differ across industries; the best performing organizations focus on continuous improvement that achieves the ongoing reduction of risk with a goal of zero incidents. Yes, we do sometimes have to say that. And yes, just because you have zero incidents in a given reporting period does not mean the organization is risk-free. Like I always say, no injury doesn't indicate a lack of risk. But the best companies know this so they look at the individual components of the SMS that designed to achieve just that - lowered risk which nets us lower (or none) injuries — so focusing on the how gets us to the big aspirational goal.

    Ok, so let's talk about the recent history of SMS and how it may impact the general industry and eventually construction over the years. According to the FAA, SMS is the formal, top-down, organization-wide approach to managing safety risk and assuring the effectiveness of safety risk controls. It includes systematic procedures, practices, and policies for the management of safety risks.

    Since requiring it in March 2015, the FAA says Safety Management System is becoming a standard throughout the aviation industry worldwide. It is recognized by the Joint Planning and Development Office (JPDO), International Civil Aviation Organization (ICAO), and Civil Aviation Authorities (CAA) and product/service providers as the next step in the evolution of safety in aviation. SMS is also becoming a standard for the management of safety beyond aviation. Similar management systems are used in the management of other critical areas such as quality, occupational safety, and health, security, environment, etc.

    Safety Management Systems for product/service providers (certificate holders) and regulators will integrate modern safety risk management and safety assurance concepts into repeatable, proactive systems. SMSs emphasize safety management as a fundamental business process to be considered in the same manner as other aspects of business management.

    By recognizing the organization's role in accident prevention, SMSs provide to both certificate holders and FAA:

    • A structured means of safety risk management decision making
    • A method of demonstrating safety management capability before system failures occur
    • Increased confidence in risk controls though structured safety assurance processes
    • An effective interface for knowledge sharing between regulator and certificate holder
    • A safety promotion framework to support a sound safety culture

    The Public Transportation Agency Safety Plan (PTASP) Final Rule in 2018 requires individual operators of public transportation systems that receive federal funds to develop safety plans that include the processes and procedures necessary for implementing SMS. Among other requirements, the rule calls on agencies to report their Safety Management Policy and processes for safety risk management, safety assurance, and safety promotion.

    And as many safety pros know, ISO has developed a standard that will help organizations to improve employee safety, reduce workplace risks, and create better, safer working conditions, all over the world. Participants in the new ISO 45001 development process used other standards such as ANSI Z10 as well as British OHSAS 18001, Canada's CSA Z1000, and the ILO's OHSMS guidelines. There is even talk of OSHA's VPP getting more aligned to the ISO 45001 Standard. So you can see a definite trend emerging when it comes to SMS.

    So, in 2018, knowing ISO 45001 was coming, the National Safety Council (NSC) started investigating all the common SMS frameworks and identifying all of the things they had in common. They recognized many companies were getting bogged down with questions such as: What is a safety management system? How can it help me? Which framework is right for my business? How do I go about implementing an SMS? They knew the research supported the benefits of SMS implementation, but they wanted clarity on what that looked like and a simple way to illustrate what elements constitute a successful SMS.

    So let's break down what the core features or functions look like - an effective safety management system has the following features or functions:

    • People – nothing gets implemented without people who are committed, engaged, and motivated; real safety change can't happen without a competent, skilled workforce. You need the RIGHT people in the RIGHT position within the organization. It isn't enough to have an incredibly motivated and engaged front-line if all or most of middle to upper management is not engaged or supportive. So you need to put the right people in the right places in the organization from top to bottom.
    • Planning – thinking ahead is half the battle of implementation; planning for foreseeable risks and the administrative parts of a management system will produce smoother rollouts and better measurement of SMS success. You need to be able to break down the individual elements necessary, assess your current state, and measure any gaps. These gaps are the space in which you will work. You have to be good at evaluating current-state - I cannot stress that enough.
    • Programs – most companies have EHS programs that identify and control most hazards, monitor and measure operational impacts to EHS performance, and eliminate deviations from the management system; individual programs must operate as part of the entire system, not independently. So think about machine safety; you will need a robust maintenance management program to fully achieve the level of machine safety required. This means measuring preventative maintenance work orders that are past due, identifying maintenance items that are not just critical to up-time, but also to safety, such as sensors, overflow preventers, valves that are identified as safety measures preventing disaster. So integrating safety with other areas of the business is critical.
    • Progress – to avoid complacency, companies need to periodically measure compliance with regulatory and legal requirements, audit their SMS system, and review SMS performance with upper management. So you need to be able to break down all the pieces of the SMS into logical parts. Like Electrical, Confined Spaces, PPE, and even roles and responsibilities as well as frequent inspections required. I recommend identifying champions for each element and have them "own" that part of the audit. They need to objectively score the organization's effectiveness of the execution of each element. Get folks from outside the safety function to drive buy-in and accountability and should be an annual thing, but you can break out each element and cover some monthly. Whatever works for your organization.
    • Performance – measures of performance need to be set and include both lagging indicators and leading indicators and moving toward predictive measures; adopting these and evaluating safety metrics among the entire business performance landscape helps companies solidify safety on equal footing with other critical operational practices – adopting a mindset of "safe operations" versus viewing safety apart from operations. So instead of asking how safety performance is doing, measure overall business performance with safety as a part of the overall measurement score. So if production was up, but incidents were as well, then there should be an adjustment made to the productivity score as a result - make sense? Again, this gets us past the whole conversation of looking at WIP, deliveries, and sales together and safety separately - safety performance impacts the others.

    The challenge for many safety pros is identifying the tools one can use to manage all of these moving parts. I will tell you that you need to look into a digital safety management system, like iReportSource.

    Whatever you tool you use, you have to make sure you can efficiently stay on top of all of these different elements; be able to report, and have others report, the necessary information so the organization can work to reduce hazards; record and track all of the activities associated with those efforts - that make them work; have access to all of the data when needed to make smarter decisions; be able to look back so you can assess your progress objectively and plan for future improvements. I call these the 4 R's:

    1. Report: Hazards, concerns, incidents, suggestions, etc.
    2. Record: Training/qualifications, observations, inspections/audits, injuries/illnesses, environmental data, etc.
    3. Retrieve: Be able to produce reports and records when needed promptly.
    4. Review: Have the ability to look at all relevant data, so it tells the story of where you have been, what is taking place, and where you need to go in real-time and as efficiently as possible.

    It gets difficult to impossible to do this manually in most organizations of considerable size or with complex processes. So again, consider looking into a system to help you manage safety more efficiently and pays you back in time and frustration so you can get out from behind the desk and spend it where it matters most; out with your people where the work happens. Visit iReportSource for more information.

    Once again, a safety management system is a continuous improvement process that reduces hazards and prevents incidents. It protects the health and safety of your employees and is integrated into everyday processes throughout the organization. Investing in an SMS makes a measurable impact on your bottom line and can be viewed as a competitive advantage.

    Send emails to info@thesafetypropodcast.com. You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter


    079: 4 Types of Root Cause Evidence According to TapRooT Oct 11, 2019
    Show notes

    Powered by iReportSource

    When an incident occurs it is the investigator's main function to gather all relevant evidence in order to discover root causes and ultimately prevent a recurrence. The tricky part is that evidence isn't always what it seems. Witnesses accounts can be spotty, inconsistent, they may tell conflicting stories about the same incident, etc. Physical or even environmental conditions can change before the investigation process begins. Paperwork, such as a work instruction or JSA, may be misplaced or even changed in some way. With all of these variables and more, you want to make sure you collect the right types of evidence during your investigation.

    I want to share with you some information from TapRooT®, which is a systematic process and training for finding the real root causes and precursor incidents, for not only major accidents but minor mishaps and even near misses. According to TapRooT®, there are four types (or categories) of evidence to be evaluated. TapRooT® calls these categories 3 Ps and an R. This stands for:

    • People evidence
    • Paper evidence
    • Physical evidence
    • Recording evidence

    People Evidence

    Often, evidence collection starts with people evidence (a witness statement), and that evidence guides the investigator to collect paper, physical and recording evidence.

    Examples of people evidence include:

    • Interviews
    • Fatigue-related information
    • Evidence of injuries, including cuts and scrapes, bruises, fractures, or sprains
    • Information about medical conditions that may have influenced performance (refer to HR or corporate counsel for guidance on HIPPA)

    Where do you begin? First, determine who was involved. This includes those who planned the work, supervised the work and performed the work. Other considerations include a worker's capability, capacity, training, and qualification to perform his or her role.

    Inquire into the background of those involved. Determine if they have been involved in any previous incidents or if they have any related performance or conduct issues. Find out if those involved had any work restrictions such as an impairment, physical capability, or lapsed accreditation.

    Understand how the employees worked together. What were the dynamics of the team including supervision and team performance? Determine the context (such as environmental conditions, distractions or perspectives).

    Paper Evidence

    Paper evidence may include all sorts of things including:

    • Regulatory paperwork
    • Activity-specific paperwork
    • Personnel paperwork
    • Policy and procedure paperwork
    • Equipment manuals

    What do you think the biggest mistake is when it comes to collecting paper evidence… given all of the paper that we have in our workplaces? Collecting too much paper not relevant to the investigation!

    You don't need to collect every piece of paper at your facility. How do you know what you don't need? By looking at the timeline of events that led to the incident. You need all the paper that supports your timeline of events and supports the facts. If you use TapRooT®, you can easily upload digital copies of this paperwork, and highlight relevant pages in your report to management.

    Don't make the mistake of collecting so much paper that what you need for evidence is somewhere at the bottom of the stack.

    Physical Evidence

    Physical evidence can range from a very large piece of machinery to a very small tool. It includes hardware and solid material related to the incident. You will gather physical evidence in one of two ways. You will collect it or you will record/document evidence that can't be collected (for example, it is too large to collect, or it is still in use).

    Types of physical evidence to collect:

    • Broken equipment/parts
    • Residue/debris
    • Fluid samples
    • Paint samples
    • Fiber
    • Hair, bloodstains, tissue or other DNA

    Types of physical evidence to record/document

    Evidence is recorded when it is impossible to collect or when it is still in use by the workforce. Following is a list of possible evidence to collect by recordings:

    • Burn marks and flame patterns
    • Tracks
    • Indentations
    • Handprints, Footprints, Fingerprints
    • Tools
    • Equipment
    • Products in use
    • Equipment status (fixed, portable or temporary?)
    • Lights, noise, and temperature
    • Confined space
    • Obstructions
    • Surface hazards
    • Housekeeping
    • Clarity of signs and labels
    • Instructions

    Following are additional pieces of information you may want to collect:

    • Failure history
    • Modification/change of use
    • Operator interface
    • Maintenance records
    • Installing/commissioning
    • Storage/transportation
    • Procurement
    • Design/fabrication

    Recording Evidence

    Recording evidence, such as photography and video, should be captured as soon as possible after an incident to preserve the scene in images before it is altered in any way. It provides a documented overview of the entire scene. This may occur as soon as you or a qualified team member can obtain access to the scene.

    In addition to video and photography recorded by the investigator, recordings include:

    • Video footage (examples: site security cameras, control room cameras, traffic cameras, etc.)
    • Audio recordings (examples: audio of the noise level, voicemail recordings, videos - check State Laws; many prohibit the recording of sound by security cameras in the workplace and there may be restrictions around recording conversations by phone or other devices as well, so always consult an attorney)
    • Photos (examples: wide shots, up-close shots, any pics taken by others, security pics, etc.)
    • Computer data (example: magnetic swipe card system security data for entry doors, data logs from machines/vehicles, inspections completed in the past, previous hazards reported, etc.)
    • Sketches of an incident scene, such as with traffic accidents. Side note, iReportSource has a cool feature that allows you to create a road diagram with different streets, intersections, add multiple vehicles, lights, signs, etc. A pretty cool feature for capturing this stuff accurately without relying on your artistic skills (or lack of)

    As you record the scene, ask "Am I recording the scene as it was in its original state or has it changed in any way?" If the scene has changed, make a note about what has changed including those involved and WHY! Be sure to capture that information. Identify fragile, perishable evidence and immediately document, photograph and collect it. Environmental conditions are a good example. Such as in the case of ice/snow and as the day progresses it melts, compounds, etc. Also, make a note of any transient evidence that can't be captured by a camera or video like steam, smoke/vapors, smells, and temperature, etc.

    Remember, the best way to collect unbiased evidence is to gather evidence from each of these four categories: people, physical, paper, and recordings. Each piece of evidence collected will help lead you to the root causes of the incident so that you can properly analyze them for effective corrective and preventative actions. Nothing is more frustrating than going through this process and determining what to fix only to learn that not only were you fixing the wrong things, but another incident has occurred that could have been prevented.

    Let me know what you think. Send an email to info@thesafetypropodcast.com and share with me the tools and techniques you use!

    If you think of it, find me on LinkedIn! Post a LinkedIn update letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter!


    078: How to Interview for a Safety Mindset Sep 24, 2019
    Show notes

    Powered by iReportSource

    When a company is looking to hire its next safety leader they must be sure to select the right person for the job. But hiring a safety leader goes well beyond their safety and health credentials and experience. You want to have someone with the right safety mindset, not just safety background and experience. The same thing goes for hiring production or other team leaders.

    Everyone knows the importance that teams play in organizational success. However, let's not forget that teams are made up of individual players, each with strengths and weaknesses. In his book, The Ideal Team Player, Patrick Lencioni reveals the three indispensable virtues that make some people better team players than others, and this speaks to their mindset (1).

    According to Lencioni:

    Ideal team players are humble. This is a person who lacks excessive ego or concerns about status. Humble people are quick to point out the contributions of others. They are slow to seek attention for their own, explains Lencioni. They share credit, emphasize team over self, and define success collectively rather than individually. They also recognize and are well-aware of their own strengths, and they can easily share those strengths when asked (1).

    Ideal team players are hungry. They are always looking for more. Hungry people rarely have to be pushed by a manager to work harder because they are self-motivated and diligent; at the same time, they aren't so hungry that they are entirely consumed by work. They are continually thinking about the next step and the next opportunity. They have just the right amount of drive you want to see (1).

    Ideal team players are smart. By "smart," Lencioni means they have common sense about people - or high EQ (emotional quotient). You may have heard of this referred to as emotional intelligence or being highly self-aware. Smart team members tend to know what is happening in a group situation and how to deal with others in the most effective way. You may think of them as tactful or good at "dealing with people." They have good judgment, a great perception of what's happening a group, and can apply intuition well on teams (1).

    So, how can organizational leaders interview for these virtues?

    Ask the right open-ended questions designed to get them sharing their thoughts and beliefs. Sure, you need to find out a little more about their professional background as it pertains to the technical aspects of safety.

    However, if the pre-screening process went as designed, hiring managers should only be interviewing technically qualified candidates at this point. So here is an opportunity to ask questions designed to determine if the candidate is going to be an asset to the team.

    Here are some examples of the right questions and what they are designed to uncover:

    1. How did you get into safety? Or whatever line of work they happen to fall into.

    This question helps to uncover someone's back story and helps someone to share what drives them and motivates them.

    At this point, you can start to see if they are able to articulate the "why" about their career choice. This question can also encourage them to become more comfortable during the interview, too.

    2. Has there ever been a situation or incident in your work that changed or shifted your approach to safety?

    Are they able to learn from situations? How have they adapted in the past to improve their life and work for the better? This question, once again, starts to dig deeper and helps you know more about how humble someone is, and their degree of self-awareness, too.

    3. What is something you would do to show senior leaders how safety can be a profit center?

    This question helps to indicate more about their capacity for critical thinking. After all, you want a candidate to be able to make a connection between safety and other aspects of the business, and this can help you know more about how savvy they are in this arena.

    4. What would you do if you saw a hazard or if you saw someone doing something unsafe at work? Has this ever happened—if so, how did you handle it? Was there anything you wish you could have done differently? (2)

    The answer helps you know more about how a candidate chooses to approach others, especially when that situation is uncomfortable or can involve conflict.

    5. How do you approach incident investigations?

    Once again, this helps us to frame someone's motivation and mindset and helps us know more about how they deal with others (smart), their ability to be forward-thinking (hungry), and their degree of self-awareness as it relates to their own ego (humble).

    As you talk to the person, see: do they seek to put blame on people, or do they think in terms of fixing and improving processes? Do they start with "what someone did" or "what did we miss in this process"? Both responses are telling.

    6. What are the most important accomplishments of your career?

    This question, fundamentally, is another way of seeing what someone values. Look for more mentions of "we" rather than "I" to see how team-oriented they are. Of course, it isn't about being so simplistic as to count the responses. In the event that someone refers to himself or herself individually more than as a member of a team, probe for whether he or she was working alone or with others.

    7. What was the most embarrassing moment in your career? Or what was the biggest failure?

    Look for whether the candidate celebrates that embarrassment or is mortified by it. Humble people generally aren't afraid to tell their unflattering stories because they're comfortable with being imperfect. And, they know their strengths and are confident in those strengths so failure isn't seen as taking away from their self-worth, necessarily. Also, look for specifics and real references to the candidate's own culpability.

    Look for specifics about how the candidate accepted responsibility for that failure, what they learned from it, and if they actually acted on what was learned. The ideal time player isn't arrogant when looking back, but they aren't lacking confidence, either. They were motivated to grow and learn from the event, and are happy to share that fact, too.

    8. How do you define success in safety? How would you measure it? (2)

    This is another example of a critical thinking question. Can the candidate define what success looks like, how to tell, and more importantly, how to achieve that success?

    9. What is the hardest you've ever worked on something in your life?

    Look for specific examples of real, but joyful sacrifice. In other words, the candidate isn't complaining but is grateful for the experience. Once again, this helps you to know more about what they really value, too.

    10. Have you ever worked with a difficult colleague or boss? How did you handle the situation?

    By asking the candidate about a difficult work relationship, you will learn if he or she can read situations and people and handle them skillfully.
    This question gives you another chance to see if they have people smarts (not the same as intellectual smarts) and how much hunger they have. It's one more chance to get insight into their overall ability to fit into your existing culture.

    Let me know what you think - email me at info@thesafetypropodcast.com. Also, let's connect on LinkedIn so we can continue to collaborate on workplace safety. You can post a comment on LinkedIn about this episode as well - be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast onFacebook, Instagram, and Twitter!

    Questions in this blog post were taken directly from Terra Carbert's post, "Interview Questions for Safety" which can be found here and The Ideal Team Player interview guide by Patrick Lencioni.

    Link to sources:

    1. https://www.tablegroup.com/books/ideal-team-player
    2. https://www.linkedin.com/pulse/interview-questions-safety-terra-carbert/

    077: A Breakdown of Job Safety Analysis Sep 19, 2019
    Show notes

    Powered by iReportSource

    Get the JSA template HERE. OSHA has a great page for this topic HERE.

    Many companies rely on a super-simple tool to define appropriate safe work practices for specific jobs. The Job Safety Analysis Process (also referred to as a JSA, or Job Hazard Analysis - JHA). The JSA is a very effective means of helping to identify and manage hazards associated with task thus reducing incidents, accidents, and injuries in the workplace. It is also an excellent tool to use during new employee orientations and operator training and can also be used to investigate "near misses" and accidents.

    Job Safety Analysis (JSA) is based on the following ideas:

    • That a specific job or work assignment can be separated into a series of relatively simple steps.
    • Hazards associated with each step can be identified.
    • Solutions can be developed to control each hazard.

    To start the JSA Process, select the job or task to be performed. Any job that has hazards or potential hazards is a candidate for a JSA. An uncommon or seldom-performed job is also a candidate for a JSA.

    Forms or worksheets (see sample worksheet) may vary from company to company but the idea remains the same. Identify all steps, hazards, and safe work procedures before starting the job. I have a template you can download to follow along. It is filled out with a hypothetical job. So grab that and follow along for more context. The JSA process is a multi-step process and goes something like this:

    • Basic Job Steps: Break the job into a sequence of steps. Each of the steps should accompany some major task. That task will consist of a series of movements. Look at each series of movements within that basic task.
    • Potential Hazards: To complete a JSA effectively, you must identify the hazards or potential hazards associated with each step. Every possible source of energy must be identified. It is very important to look at the entire environment to determine every conceivable hazard that might exist. Hazards contribute to accidents and injuries.
    • Recommended Safe Job Procedures: Using the Sequence of Basic Job Steps and Potential Hazards, decide what actions are necessary to eliminate, control, or minimize hazards that could lead to accidents, injuries, damage to the environment, or possible occupational illness. Each safe job procedure or action must correspond to the job steps and identified hazards.

    Through this process, you can determine the safest, most efficient way of performing a given job. Thus JSA systematically carries out the basic strategy of accident prevention: The recognition, evaluation, and control of hazards.

    Now, how do we document this process and capture the results? It is prepared in a 3-column chart form, either portrait or landscape - I have seen both and listing the basic job steps on the left-hand column and the corresponding hazards in the middle column, with safe procedures for each step on the right-hand column. The right-hand column will essentially become your safe work instructions.

    A completed JSA chart can then be used as a training guide for employees; it provides a logical introduction to the work, it's associated hazards, and the proper and safe procedures to be followed.

    For experienced workers, a JSA is reviewed periodically to maintain a safety-awareness on the job and to keep abreast of current safety procedures. The review is also useful for employees assigned to new or infrequent tasks.

    Let's talk about how to fill out the JSA. First, there is an art and science to breaking down a job or task into steps. If the steps are too detailed, the JSA will be complicated and difficult to follow. If they are not detailed enough, you may miss important steps and associated hazards. For example, let's say you are planting a tree, and you need a JSA on how to unload the tree from the truck. You don't want to say:

    Step 1. Remove latch pin from the tailgate

    Step 2. Release tailgate latch

    Step 3. Lower tailgate to open position

    Now you move to plant the tree, let's say by hand:

    Step 1: Retrieve shovel from the back of the truck

    Step 2: Place shovel on the ground at the specified degree

    Step 3: Place dominate foot onto the back of shovel at the mid-sole

    This is tedious, no one will read that document. Instead, it may be enough to simply say, "open tailgate" as the job step and move to the second part of creating the SJA - listing all the hazards associated with that step. On the flip side, don't over-simplify it either. For example, when planting the tree:

    Step 1: Put tree in ground…that's it. No step 2.

    Ok, an extreme example of over-simplification. But be sure to walk through the job steps and look for opportunities to break it down into steps. If you already have job steps laid out, such as in the case of OEM operating instructions or manual this makes it a bit easier.

    To make sure I illustrate this point, let's talk about another example; let's say you need to operate a 3D metal printer - you wouldn't just state, "place build plate inside the print chamber, close door and start print operation." There is obviously more to this process. This brings me to my next point; understand the difference between a job/task and a process.

    A process is a series of physical, mechanical, or even chemical operations, often made up of several different jobs/tasks. On the other hand, a job/task is a single activity - either on its own or in support of a larger process, like 3D metal printing. In this example, there will be the storage, handling, and loading of metal powder. Then there is the build set up - like installing the build plate, and even post-printing work, like removing the printed part from the build plate, any grinding or buffing work on the part, hardening of parts in an oven, just to name a few.

    Each job/task will have its own JSA form that, when combined will make up everything that goes into the overall process of 3D Printing. And the steps and hazards could be different for different types of print jobs - the print media could be different, the print machine models could be different, inserting gases, removal process, etc.

    A good tip as you complete your JSA, make sure each job/task step starts with action - use verbs, like pull lever, push door, place ladder, etc. Steps that do not present a potential hazard should be left off. The exception would be if you intend to use this as a multi-purpose job aid covering other job steps (like for quality or production).

    This layered approach may work well, as employees will see there is ONE way to perform the job. That brings up a great point, you may already have a work instruction that breaks down the steps. Maybe there is a machine operating manual. Be sure to review these with operators to ensure they are actually still relevant and cover all the steps they need to take.

    Whether you have existing jobs needing to be reviewed or are implementing a new job or task, employee involvement is critical. So be sure to do a couple of walk-throughs of the process with operators before publishing the document. The JSA should be reviewed, approved, and signed by the supervisor before the task is started. Understanding every job step is very important! Whenever a job step changes or a new step is introduced, the JSA must be reviewed and updated.

    Remember, the key reasons for completing a JSA are to encourage teamwork (especially with new employees), to involve everyone performing the job in the process, to increase awareness of potential hazards, and communicate safe operating procedures!

    I have a JSA template download link in the show notes. Be sure to practice a few times and review it with others to make sure you get the hang of it. Make sure you do not overlook a job step/task that introduces a hazard! This is the whole point of this exercise - to identify and control hazards associated with performing a job.

    Let me know what you think - email me at info@thesafetypropodcast.com. Also, let's connect on LinkedIn so we can continue to collaborate on workplace safety. You can post a comment on LinkedIn about this episode as well - be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast onFacebook, Instagram, and Twitter!


    076: Leading Safety Excellence an Interview with J.A. Rodriguez, Jr. Aug 30, 2019
    Show notes

    Powered by iReportSource

    As I continue my podcast interviews in New Orleans from the 2019 VPPPA Safety+ Symposium I had the honor of interviewing some Association Board members. They shared some sound advice for anyone looking to improve their safety and health management system as well as some insights for safety pros struggling with challenges along the way.

    Visit www.vpppa.org for more information about this amazing organization!

    You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter.

    #vpppa2019


    075: Near Death Safety Lesson with Kelly Pitts Aug 29, 2019
    Show notes

    Powered by iReportSource

    Here at the 2019 VPPPA National Safety Symposium where everyone you meet has a story to tell. Kelly Pitts shares his message of a near-death experience and what you can learn and take back to your organization.

    You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter.

    #vpppa2019


    074: PPE Safety for Women in the Workforce with Abby Ferri Aug 29, 2019
    Show notes

    Powered by iReportSource

    As I continue my podcasting interview marathon from the 2019 VPPPA National Safety Symposium, I had the absolute pleasure of sitting down with Abby Ferri to discuss the issues that women in the workforce continue to experience with PPE - which is in large part designed for men.

    Abby has over 15 years of experience in the field of safety and health in diverse industries, including construction, manufacturing, healthcare, hospitality, beverage, and retail. Abby has become well-known in this industry as a practical and creative safety professional.

    Learn more about Abby by visiting www.theferrigroup.co

    You can find me on LinkedIn! Post a LinkedIn update, letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter.

    #vpppa2019


    073: Leading Safety From the Heart with Diana Paredes Aug 29, 2019
    Show notes

    Powered by iReportSource

    Diana Paredes is an experienced bilingual safety manager in the tough yet rewarding food & beverage industry. She is a SafetyPro podcast listener joining me at the 2019 VPPPA National Safety Symposium and shares some words of wisdom and strategies to help drive employee engagement, ownership and stresses the simple act of recognizing the many small victories our workers achieve every day.

    It was an absolute pleasure to meet Diana and hear about her experiences in safety. I am such a fan!

    You can find me on LinkedIn! Post a LinkedIn update letting me know what you think of the podcast. Be sure to @ mention Blaine J. Hoffmann or The SafetyPro Podcast LinkedIn page. You can also find the podcast on Facebook, Instagram, and Twitter


    Previous 1 11 12 13 14 15 21 Next

    Related Podcasts

    Making Sense with Sam Harris

    1

    Making Sense with Sam Harris Education
    Grammar Girl

    2

    Grammar Girl Education
    Good Life Project

    3

    Good Life Project Education
    Explain It to Me

    4

    Explain It to Me Education
    Team Never Quit

    5

    Team Never Quit Comedy
    Optimal Living Daily – Personal Development and Self-Improvement

    6

    Optimal Living Daily – Personal Development and Self-Improvement Alternative Health
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights