Leaderboard

Interesting answers to a seemingly easy question. The best answer is from R Rajesh. Well done. Answers from Sargun, Sachin and Mark are also an interesting read. Do check them out as well.

The role of a Master black belt in a company is to evaluate and investigate the processes in a company and then further direct the course of action in processes where there is defect. The MBBs have a deep knowledge of the processes of a company and dictate the strategy for the direction to be taken. AI team’s approach is more data driven and they would want to look for automation of the processes. They would want to analyze the data and identify patterns and give insights which the MBBs might have missed. If they work together, they will lead to more optimized processes, better decision making and a more optimized process. MBBs can contribute by: · Sharing Process expertise: They have deep knowledge of processes. · Guiding strategically: They can guide the AI team with organizational goals. · By Handling Change Management: By helping the teams to adapt to AI driven processes. · Understanding of context: Ensuring that AI solutions are practical and relevant. AI Teams can contribute by: · Automation: They are experts in Automation. It can help to automate repetitive tasks. · Predictive modelling: They can use the Predictive models to forecast the potential issues. · Simulation and optimization: they can simulate the new processes for MBBs to test before implementing them actually. · Data Analysis: They can use data analysis tools to identify patterns and anomalies that the MBBs might have missed. How MBBs and AI Team can work together: 1. MBBs and AI teams should try to learn from each other and always stay updated on the latest technologies, trends and best practices. 2. They should use and iterative approach where the solutions are continuously improved based on the feedback. 3. They should clearly understand each others’ roles and responsibilities so that there is no conflict and each team can contribute effectively.

Traditionally MBBs improve efficiency, quality and reduce waste but in AI powered transformation - we can redesign the workflows where AI does part of decision making and automation. Below are the points for MBBs role in AI powered solution * Bridge the gap between business stake holders, operations and AI architects, translates the organizational priorities and customer value drivers into technical requirements. * Mention the critical and pain points * Establish control mechanisms and KPIs to monitor the performance. * Train and coach teams on how to interpret AI outputs. It can be ensured by applying lean six sigma, Strategic priorities, Design for customer and employee experience, and Governance framework.

Role of MBBs in AI Projects MBBs are uniquely positioned to drive value in AI-powered transformations due to their systemic view of operations, deep expertise in process improvement, and proven ability to align cross-functional stakeholders around measurable business outcomes. While AI teams often focus on model development, data science, and technological execution, MBBs contribute by ensuring that AI initiatives: Are business problem-driven, not technology-driven. Target critical process performance gaps aligned with Voice of the Customer (VOC). Are embedded in repeatable, sustainable, and value-creating workflows. The specific value-add of the Master Black Belt can be categorized into four key areas: Capability Contribution to AI Projects Process Architecture and Problem Framing Identifies where AI can reduce waste, variation, and complexity by deconstructing complex business challenges into well-defined problems that are suitable for an AI solution. Using tools like SIPOC and VSM, MBB can identify the precise process steps with the most significant bottlenecks, waste, or variation Data Integrity and Bus. Context AI models are entirely dependent on the quality and relevance of the data they are trained on. The MBB acts as the bridge between raw data and business reality. By conducting an MSA on the data collection process itself MBBs ensure accuracy and reliability, by asking critical questions like “Does this data represent the VOC? Are there known process shifts that would skew this historical data?” This understanding prevents the “garbage in, garbage out” pitfall that affects many AI projects. Stakeholder Engagement Bridges executive vision with operational execution through facilitation and influence. Advanced Data Analysis Offers statistical modeling and hypothesis testing skills to validate AI outcomes. Benefits realization and control MBB ensures that the AI solutions delivers measurable improvement against a KPI. MBBs are responsible for ensuring these benefits are not only achieved but sustained. The MBB designs the Control plan for the new AI enhanced process, for monitoring Critical Business KPI’s (the “Y”), and the key process inputs (the “x’s”) incl. the AI model’s output, to ensure incase the model’s performance degrades or the process deviates, there is a clear response plan. Collaboration Strategies with AI Teams Effective collaboration hinges on bridging the gap between the process-centric language of Lean Six Sigma and the technology-centric language of AI development. The MBB must proactively facilitate this alignment. - Establishing a Common Language: Misunderstandings often arise from differing terminology for similar concepts. The MBB can create a "translation matrix" to foster clear communication. Lean Six Sigma Term AI/Data Science Term Collaborative Interpretation Voice of the Customer (VoC) Training Data Labels / Target Variable The desired outcome or classification that the AI model needs to predict, defined by customer value. Critical to Quality (CTQ) Key Features / Predictors The measurable process inputs that are hypothesized to have the greatest impact on the outcome. Root Cause Analysis Feature Importance / Exploratory Data Analysis The joint exercise of using process knowledge and data science to identify the true drivers of a problem. Process Control Plan Model Monitoring / MLOps A system to ensure the AI-powered process continues to perform as expected and trigger alerts for retraining or intervention. - Align Project Objectives and Success Criteria: Begin AI initiatives with Define and Measure phases from DMAIC - What problem is AI solving? What is the current baseline performance? What process KPIs and customer metrics will define success? Use CTQ Trees to connect AI model outputs to business-critical outcomes. - Integrate AI Capabilities into Existing Processes: Use FMEA + Process Mapping to identify - Where automation can replace manual judgment. Where human oversight remains essential. Support pilot programs with structured experiments (e.g., Design of Experiments for comparing human-only vs. AI-augmented processes). Example: In a sales forecasting process, use control charts to validate AI-predicted vs. actual demand across different market segments. Bridging the Mindset and Skill Gap Long-term success requires a cultural and educational commitment to bridge the gap between process excellence and AI. Fostering a Culture of Continuous Experimentation/Innovation: The MBB can help shift the organizational mindset from large, monolithic projects to a more agile approach of continuous improvement. This aligns perfectly with the iterative nature of AI model development (build - measure - learn). By promoting a culture where it is safe to assess hypotheses and learn from failures, the organization can innovate more rapidly. Promoting Cross-Functional Training Initiatives: For Master Black Belts: MBBs must become "AI Literate." Organizations should invest in training for MBBs that covers: Foundations of AI/ML: Understanding the difference between supervised, unsupervised, and reinforcement learning. AI Project Lifecycle: Learning the key stages of data acquisition, model training, and deployment. Asking the Right Questions: Knowing how to probe an AI team on data sources, potential biases, model explainability, and scalability. For AI Teams: AI and data scientists often lack deep context on the business processes they are trying to impact. MBBs can lead "Process Immersion" workshops that cover: Gemba Walks: Taking the AI team to the "real place" where the work happens. Value Stream Mapping Sessions: Helping the AI team visualize the end-to-end process and understand its complexities and constraints. Voice of the Customer Reviews: Sharing customer feedback and pain points to ground the technical work in real-world value. Creating Integrated, Cross-Functional Teams: Instead of having a separate "Process Excellence" team and "AI Team," organizations should form cross-functional "teams" or "pods" dedicated to solving a specific business problem and break down organizational silos entirely. An MBB should be a core, embedded member of such a team, working alongside the AI Architect, data scientists, and business stakeholders from project inception to completion.

In this AI world, the role of a MBB should be like a coach guiding the team that builds the AI-powered solution for a critical business process Imagine you want to go from city A to city B which is a considerable distance and now you are go in this combination - an Express Highway and a F1 race car. So how quick that would be. The combination of MBB and AI Solution Architect is akin to this!! The MBB letting know what her thought process/ideas on doing a transformation and the AI Solution Architect complementing that thought process/ideas with concrete implementations I personally saw the power of this in my AI enabled Business Excellence MBB program organised by BenchmarkSixSigma.com. There were many modules in that program. When there was a discussion on a Monte-Carlo Simulation problem, while doing in a conventional manner, the outcome took some time to arrive at for all of our batch mates in the program. With the help of AI prompts (as part of the program), when the same problem was fed to an AI model (say ChatGPT), it threw good suggestive approaches which expedited us to get the right set of parameters (necessary for Monte-Carlo simulation) which can result in the right solution. This was a classic case of a MBB and an AI system working together. Imagine that AI system being engineered by an AI Solution Architect!! This is just a proof of how a MBB and an AI Solutions Architect can work together and achieve great results Imagine the MBB picks a transformation project that talks about cost reduction for the customer in one of its critical process. The work demands a typical Black belt project. By conventional means, the Six Sigma Black Belt project would take quite some time. Shrewdly the MBB decides to leverage her colleague an AI Solution Architect. She tells him about the project needs and customer expectation. He hears out the problem and comes up with a solution which is relevant to the ask. How he does that solutioning? By providing an AI solution that focuses on - Data driven insights - Automation of process With the above focus, he (AI Solution Architect) is able to - innovate the organization, - making the leaders/MBB (in this context) arrive at informed strategic decisions that can impact business outcome, - reduce the operational costs involved - Also, in general, the costs, as we improve the overall efficiency & productivity of the system - help the customer organisation to outperform its competitors through quick adaptation to changing market needs - extracting valuable insights from data turning into actionable strategies which drives business success This really helps her (MBB). During this transformation journey, there may be several touchpoints for both of them. For instance, if there is an insightful data (Coming out from the AI solution) that can bring a new perspective to the MBB. Then she may have a discussion with the AI Solution Architect. To have some clear-cut strategy for a good discussion with an AI Solution Architect or to an AI based team would be - It would be always good to have a cadence setup between the MBB and the AI Solution Architect. - Have good discussions with the AI team which can help the team to write better prompts for a better solution By reducing the costs associated with the project, we can showcase the value that can be provided to the customer and also focus on satisfying customer needs and expectations, as part of our organisational priorities There are few things as a MBB should do, to improve upon his/her AI knowledge. 1. Learn basics of AI and also Gen AI which is good enough to explain your problem statement that you want to convert into an AI based system 2. Learn basics of Prompt Engineering and 3. Understand fundamentals of ethical AI Governance and understand how it impacts organisational standards and Data Privacy compliance As an AI Solution Architect (other than AI specific skills), you need to know 1. The vision/idea (intended purpose) of the problem statement and what is the expected outcome so that the solution can be more contextual and precise 2. Development of skills in preparing comprehensive System Requirements or Business Requirements document that will map the objectives of the AI based project with the business needs Thus, you can see how a MBB and AI Solution Architect can get in sync with a transformation and can really speeden up the transformation and bring benefits to the customer. So does this mean that you need a MBB and an AI Solution Architect together. Is it possible that a MBB also becomes an AI Solution Architect? Well, you can be a MBB and also be skilled with AI Solution Architect just like how I plan to be now (thanks to the CAISA program). This is similar to a Tennis player being the captain (of the squad) and also being a player while playing Davis/Fed cup. He/she will be knowing whom to select as player and also understand the strength and weakness of each player and also the playing conditions. Same way, the MBB with AI skilled would be able to understand which transformation to do and what to do and how to do it through AI. This is where these sort of programs – AI Enabled Business Excellence MBB and CAISA programs when leveraged effectively can be game changers. Reference Material Source for AI: Benchmark Six Sigma CAISA Course program

The ways in which AI Team and MBB can create a better solutions are: 1. There should be clear roles and responsibilities divided between AI Team and MBB's so that they can work in a synergy and can contribute more. This can often prevent from conflicts between two and overall help in utilizing skills from both of the teams or individuals. Following are the Role and Responsibilities of a MBB and AI Teams are: MBB Focus should be on improving and analyzing process for optimization and value generation. Customer value should be on priority. To align AI solutions with organization's goals. Focus on structured problem solving. Value generation for business in terms of financial success as well as customer outlook. AI Team Focus mainly on solution architecture. Overall technicality of the solution. Idea generation for problems in brainstorming sessions. Implementing AI solutions. 2. Proper Communication between both the sides by means of workshops, brainstorming sessions, so that they can have an idea of each others zone and the gap can be bridged between two. This will create a synergy between two and help the organization to be more efficient. 3. Focus on each others strength, As MBB's are more skilled in mapping the process, defining problem statements or analyzing process and identifying hidden problems and bottlenecks from the process. Using data for creating meaningful inferences and validating benefits for value realization and on other hand AI team is skilled for generating idea for automations and creating AI solution architecture for problems. They are skilled in implementation of solutions and providing technical support wherever required. So both the skill sets are important for organization to carry a sustained and a profitable business.

An MBB act as intermediary between the business requirement and AI capability. they act as a translator between the customer need and technology capability to deliver the same. MBBs role is important to ensure that applied AI solution is not just technically well but operationally apt as well and based on customer’s verbatim and requirement and strategically aligned. They understand the business problem statement, articulate it well. They validate that developed AI solution fulfil user’s requirement and apt for their usage and not only technical They help in getting adoption of the new solution and ensure the AI solution is aligned with existing standards They take care of risk assessment and plan risk mitigation for the developed new solution. they ensure to deploy the relevant control plan for the sustainable solution and do not introduce any new risk in the process In order to ensure that AI initiatives are aligned with process excellence, customer and company’s priorities, MBB should follow below mentioned points:- 1. It should start with process and it’s core problem. the project that donot target the business problem improvement should be challenged and questioned 2. Include process owner and AI technology folks and end users from the beginning to incorporate all view points and calibrations. 3. Use these lean six sigma method to carve the structure for AI project by reflecting the clear problem statement, accuracy in measurement of KPI, root cause analysis and sustainable control plan 4. Reflect AI solution as an ongoing and continuous improvement enabler and not as one time invention. Reflect the progress in daily calls/huddles and dashboard

AI adoption is a key focus area for most companies today if not all. In this scenario it has become very common that MBBs and AI Solution Architects often end up working on the same transformation initiative. Although both the teams have different approach to the same problem, here are a few strategies which MBBs can follow to ensure that AI initiatives are aligned with process excellence, customer value, and organizational priorities – 1.) Business Case – Ensure every AI initiative is has a clearly defined business problem and is aligned with the strategic objectives of the organization. 2.) Embed Process Excellence Methodologies – a. Apply established methodologies like DMAIC (Define, Measure, Analyze, Improve, Control) or DMADV (Define, Measure, Analyze, Design, Verify) to the AI development lifecycle. b. Utilize Value Stream Mapping (VSM) to identify areas of the process where AI can be applied. 3.) Customer Journey Mapping - Create a map of the customer experience and pinpoint the precise points of contact where AI may enhance communication, lower barriers, or provide tailored value. 4.) Establish a robust governance and collaboration framework with shared goals regular review/tollgates 5.) Benefits Realization Management- Establish a structured procedure to monitor and document the true advantages of AI projects, guaranteeing responsibility and proving their worth.

The AI teams Co-Create and Business Excellence Experts (MBBs) must collaborate from the beginning (not in silos or as hand-off partners) in order to provide better solutions for today's complex organizational issues. MBBs are aware of how tasks are completed. They concentrate on enhancing the functioning of people, systems, and procedures in order to address real-world issues. They pose the appropriate queries: What is the objective? What's causing the delays? What is generating confusion or waste? AI teams, on the other hand, provide the means to address these issues in novel ways by automating repetitive processes, accelerating decision-making, and predicting potential outcomes using data. However, AI is most effective when it is directed towards the correct issue, which leads to the discovery of quicker and more intelligent solutions. They may create solutions that are both inventive and practical, based on actual demands and supported by cutting-edge tools, if they collaborate from the start. How they can work better together? 1. Begin with a common objective: MBBs and AI teams should jointly and concisely characterize the issue. 'Why' it matters is as important as 'what' has to be fixed. 2. Make use of actual facts, not conjecture: MBBs are able to identify process gaps and discrepancies. Data from such domains may then be used by AI teams to create clever solutions. 3. Build gradually rather than all at once: Begin modestly. Put the concept to the test in actual settings. While AI teams modify the model or tool to match what is effective, MBBs assist with feedback and outcome tracking. 4. Pay attention to people rather than simply technology: The best solutions are those that people use. MBBs are adept at leading change, developing teams, and ensuring that novel concepts are retained. 5. Continue learning along the way: Co-creation is a continuous process. It's important for MBBs and AI teams to maintain communication, continuously refining the solution, and facilitate scaling. The true benefit occurs when the astute powers of AI combine with the practical expertise of MBBs to transform business challenges into significant, long-lasting advancements. What Does Co-Creation Look Like? 1.Identifying the true issue should come first. MBBs are able to pinpoint instances in which a process is inefficient, inconsistent, or sluggish. In addition to solving technical problems, they also assist the team address the 'right' problem. 2. Utilize the appropriate data to comprehend the situation: AI teams may examine the data to identify trends, and MBBs assist in interpreting the data's meaning in the context of the actual world. 3. Test and collaborate to improve: Take little actions to build solutions. Pilots or trials are led by MBBs, who also assess the results and make adjustments depending on what is effective. In response, AI teams improve models or tools. 4. Design with humans in mind, not just machines: If no one uses an AI tool, even the most intelligent one will fail. MBBs make ensuring that the solution works with people's actual workflows. 5. Continue to learn and adjust: Over time, both business procedures and AI models require fine-tuning. Co-creation is a continuous collaboration that continues after a project is launched. Real-World Example: Cutting Down on Manufacturing Plant Delays The problem: The production line of a sizable manufacturing business had regular delays. Delivery deadlines were being missed as a result of machines halting suddenly. MBB's Role: During a process analysis, an MBB discovered that equipment failures were occurring more frequently during particular shifts, but the maintenance team lacked a discernible pattern to follow. The MBB also found that planned maintenance did not correspond with the real patterns of wear and tear. Role of AI Team: Using data from machine sensors, the AI team developed a predictive maintenance model. Before a failure happened, it detected early warning indicators and sent out notifications as necessary, minimizing unscheduled downtime. The Result: Together, they revamped the maintenance procedure, - Replacing set timetables with predictive warnings - The signs for the maintenance crew were clearer and earlier - Delivery on time increased by 25% and downtime decreased by 40% This achievement was a result of both the AI model and the cooperation of the MBB, which made sure the solution was workable and in line with operations, and the AI team, which provided the technical understanding. Conclusion: When AI teams' potent tools are paired with MBBs' extensive process understanding, great solutions are produced. It's about collaborating to create something better, quicker, and more beneficial than either could achieve on their own, not about picking one over the other.

Introduction – One of six sigma's key objectives is to reduce variation, and comprehending these variations can be aided by using Multi-Vari charts. Leonard Seder first described Multi-Vari charts in 1950. Later, it was widely used to comprehend stock market fluctuations. Then, Dorian Shainin began utilising it as a root cause analysis tool, which he referred to as Red X. Definition – Multi-Vari charts analyse various sources of variation or classes of variation, according to their definition. It is useful for early root cause analysis and helps us focus on the inputs that are producing issues. These are sometimes referred to as multiattribute utility theory charts, and they assist people in comparing numerous options by outlining the advantages and disadvantages of each other. This is just an another way to narrow down our inputs by analysing the process Xs or the inputs. Especially in the early stages of data analysis, use a Multi-Vari chart to visually portray Analysis of Variance (ANOVA) data to analyse data, understand potential relationships, and root causes for variation. Multivariate graphs are particularly helpful for comprehending interactions. Sources of Variation as we have in ANOVA: Interaction Within Variables – This source let us understand the reasons for variation within a batch. This is also called positional variation. For instance, it is comparing within the variables if we observe variation within a batch on a given day. Interaction Between Variables – This source explains the causes of the change between batches. Additionally known as cyclical variation. For instance, if we are seeing variation between Batch 1 and Batch 2, it is comparing between the variables. Time-to-time Interaction – This provides the reasons between weeks or days or any time frame we want to analyse. This is also called temporal or shift-to-shift variation. For instance, if we are looking to find our variation across the Day 1 and Day 2, then the time factor comes into picture and it is Time-to-Time variation. A Multi-Vari chart is a two-axis plot. These graphs are used to examine a process's consistency or stability. Time is represented on the chart's horizontal, or X-axis while the process output or reaction measurement is depicted on the vertical, or Y-axis. The multiple measurements of each unit are plotted together. Consecutive measurements are plotted from left to right over time. A break in the horizontal groupings indicates a break in time during the sampling process. Advantages – Ø It gives us access to several sources of variation, such as within, between, and over time, and is comparable to the reproducibility and repeatability of ANOVA. Ø Despite the need for additional statistical analysis, it points us in the right path for determining the reasons of variations. Ø This is easily illustrable without the aid of any graphic programme. Disadvantages – Ø As was already said, Multi-Vari only provides preliminary sources of variations. Ø Given that it is merely a graphical tool, a thorough interpretation is not feasible. ANOVA can be used to undertake statical procedures and uncover the underlying causes of sources of variation. Ø With discrete data, it is ineffective. To measure the variances, we can only use continuously data. Let's look at one of the industry examples of Quality scores broken down by week that was taken from various clients below. Interpretation – · Client 5: The Multi-Variance chart shows that Client-5 demonstrated strong Quality performance over the course of all four weeks, with very little variations in their weekly results. · Client 2: The Multi-Variance chart shows that Client 2 has higher weekly variations and is also going lower than 90%. · Client 1 is performing similarly to Clients 2 and 4 in terms of quality, however there is more variance between the weeks. · Client 3: When compared to other clients, this client's quality is inconsistent and shows significant fluctuations.