Skip to content
View in the app

A better way to browse. Learn more.

Benchmark Six Sigma Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Topics

Leaderboard

Popular Content

Showing content with the highest reputation on 12/10/2024 in Posts

  1. Self-serving bias is the human tendency to attributes success to internal factors and failures to external factors. For Example: A Manager may attribute the success of the project to his skills of management but will attribute the failure of the project to the team’s skill or situation that were not conducive to complete the project successfully. In Six Sigma, Self-serving bias can have a very significant impact on identification of root causes. It will lead to inaccurate root cause analysis where reasons may be flawed, poor judgement will arise and ultimately leading to ineffective problem solving. Team members may refuse to accept accountability for the mistake contributed by them which will impact the solution. Attributing possible root causes to external factors like market conditions rather than key internal factors like process inefficiencies. Selective data interpretation can also lead to bias. Strategies to mitigate self-serving bias: 1. Training & Awareness: Six Sigma practitioners should be trained to recognize and address bias. They should be encouraged to build a culture of data integrity, objectivity and critical thinking 2. Data Transparency: Ensure that all data collected is transparent and documented and report anomalies 3. Diverse Teamwork: Ensure that cross functional teams are be enabled to provide root cause analysis, challenge assumption and biases in the project via calibration sessions 4. Data Driven Decision Making: Ensure all decisions made are based on data. No assumptions are to be made, Discussions should be done on factual data. 5. Declare Assumption: All assumptions should be avoided. But if assumption is necessary then it must be well documented. 6. Usage of Proper tools and Statistical approach: 5 why, Ishikawa diagram and affinity diagrams should be used to systematically explore root causes. Sensitivity analysis can be performed to weigh in the impact of assumptions. 7. Independent or Peer review: Use project enthusiasts to review the analysis and findings. Six Sigma certified peers can be used to question the usage of assumptions Hence during analysis phase, a clear plan needs to be developed so that we can check the effectiveness of process improvement. We should also be able to identify and mitigate such bias. Using the above-mentioned strategies will help us enhance the integrity of the project and deliver proper results.
  2. With the evolution of human race, Self prioritization tactics and techniques have also evolved manifold. In earlier times it was often used to align with a concept, which was later coined as Darwin Theory of Survival OR Survival of the Fittest. It was first drafted keeping living organisms at center of it and various skills they require to prove their credibility within a ecosystem for superior sustainability. As time passed by, human knowledge, emotions, intellect and this rigor for sustainability grew too and various forms and shapes, which includes resorting to negative and positive means and ways. Till the time positive, meaningful and logical routes are used, it gives proportionate results. But resorting to negative, deceitful and maligning routes, leads to dis proportionate outcomes. Above analogy hold true not only for a household, a class of kindergarten kids, a highly acclaimed academic institution, a highly competitive sports arena but also in the immensely competitive corporate culture too, wherein sustainability depends on the ability of an individual to convince oneself that he is apt to survive in any situation. Adherence to the above tactic, at times results to a phenomenon called as SELF - SERVING BIAS, wherein, a person, for any positive outcome of an activity, takes the credit himself BUT if things go negative, he makes others factors responsible for it, with zero acceptance of his failure. In a typical DMAIC project, wherein decisions are taken basis the data, presence of Self-Service Bias, may lead to major blunders, potentially impacting the outcome of the project. Impact of Self - Service Bias in RCA – - It could result in un-uniformed causes identification, based on self-assurance thoughts of a person or group of persons - Unidirectional brainstorming sessions, led by team members who have a say in the system either because of experience or superiority - Probability of losing on insights through data is more, as decisions are more based on self-conviction - Reliability of identified root causes is less, as they are based on limited cognitive thinking - High solutioning cost, as often they are developed basis output collected from few individuals and not the entire group - Low sustainability of solutions developed to mitigate root causes, as they are result of ‘bracketed cognitive thinking’ Avoiding Self Service Bias – - Building and sustaining healthy corporate culture, wherein employees doesn’t feel ‘judged’ if a failure occurs and for successes credit goes to the entire team - Coaching people on how making mistakes and learning from them is actually a sign of strength - Acceptance of certain degree of Self - service bias, so that correct cautions can be bought in - Before any RCA session, letting members know, the expectations from outcome and the objective - Rewards and recognition for the team members who are most active in challenging the status quo, so as to motivate them for logical decisions - Striving for Data Driven Analysis, instead of opinionated ones
  3. Self-serving bias is this sneaky neural trick where we usually tend to steal credit for our successes and blame something or someone else when things go haywire. In LSS projects, this can be a critical issue in the area where we're trying to figure out what is or who is actually causing issues in a process or during RCA. Let's say you are working with a team of 15-20 and something went wrong, you want to protect your ego now, right? That's natural and basic instinct, that's where you might unconsciously: Ignore your own role in the process Point fingers Minimize your contribution to actually create solutions, just hover How does it impact during Root Cause Analysis? Disregard your personal contributions where you may tend to downplay their involvement in the creation of the issue. However, overemphasize personal contributions to solutions can also occur; you might overestimate your significance in resolving the problem which is basically stealing credit of your teammate who actually came up with a solution. The natural instinct to blame others for failures is another usual behavior; where you will shift responsibilities to other factors or other people, although others may play a role in the situation as well. Strategies to Mitigate the bias and ensure objective decision making: Establish a blame-free environment: Create a blame-free workplace by emphasising that the goal is problem solving rather than attributing blame to people. When people feel comfortable admitting their mistakes, they are more likely to be transparent. Data Driven Analysis: Data-driven analysis prioritises objective data over subjective feelings. Numbers are objective and do not lie; consequently, using analytical tools such as fishbone diagrams and statistical studies forces one to evaluate tangible data rather than relying on instinct or personal experiences. Rotate Team Perspective: Rotating team perspectives can help find ignored features by analysing the same issue from various angles, equivalent to engaging a variety observer. Bring In Outside Perspective: Bringing in an outside opinion is also worthwhile. Occasionally, a new perspective—perhaps from someone who is not emotionally committed in the project—can reveal features that the inside team may ignore. Finally, practicing radical honesty is vital. When potential biases occur, team members should be encouraged to identify them; it is okay to express concerns, such as saying, "Hey, I think we might be avoiding looking at our own roles here." This method promotes an environment of transparency and responsibility, which leads to more effective issue solving. What's the bottom line? Stay curious, humble, and remember that in LSS, the process reigns supreme. Your main responsibility is to improve the system, not to protect your ego.
This leaderboard is set to Kolkata/GMT+05:30

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.