RD RD

Break-even analysis is commonly used to determine the minimum sales required to cover costs. One thing break-even analysis is not limited to revenue-generate activities; it can be applied in all cases. An example of this is when Lean Six Sigma approach is applied in support functions where nothing comes in terms of revenue but nevertheless, break-even analysis can be conducted to measure cost savings related to process improvements. Below is a practical example of how break-even analysis can be used in a call center automation project. Break-Even Calculation Table Category Value Total Employees (Before RPA) 150 employees Total Employees (After RPA) 100 employees Initial Cost of RPA Implementation ₹4,50,000 Annual Maintenance Cost ₹25,000 per year Total RPA Cost (Over 3 Years) ₹5,25,000 Average Salary Per Employee (Annually) ₹2,00,000 Reduction in Headcount 50 employees Total Annual Cost Savings ₹1,00,00,000 Break-Even Point Calculation ₹5,25,000 ÷ ₹1,00,00,000 Time to Break Even 6.3 months

Risk management is a vital part of any organization’s success, and two popular methods in this field are ISO 31000 and FMEA (Failure Modes and Effects Analysis). While ISO 31000 takes a broad look at potential threats facing the entire business—like financial, operational, or compliance risks—FMEA digs into specific processes to find weaknesses before they become major problems. When these two approaches are used together, they form a more comprehensive and practical system for keeping risks in check. ISO 31000 lays out a structured way to identify and handle all sorts of risks, ensuring that important decisions line up with the company’s overall objectives. In contrast, FMEA zeroes in on particular points of failure, ranking them by severity, likelihood, and how easily they can be detected. This ranking helps teams tackle the most critical issues first and fix them quickly. To see how this works in real life, consider an automotive manufacturer. Using ISO 31000, the company keeps an eye on large-scale risks, such as product recalls or quality-control failures. At the same time, by applying FMEA, it spots a problem in the engine’s cooling system early on—well before it leads to costly recalls or damage to the brand. In a banking scenario, ISO 31000 might guide the bank’s overall strategies for managing credit risk, while FMEA focuses on catching errors in loan approvals, like incorrect data entry or incomplete documentation. By fixing those errors upfront, the bank reduces both financial losses and customer dissatisfaction. Ultimately, ISO 31000 and FMEA work best hand-in-hand. ISO 31000 provides the high-level structure that keeps an organization aware of its major threats, and FMEA gives a detailed roadmap for preventing smaller issues from ballooning into significant setbacks. Using both methods together allows a business to prioritize, plan, and act more effectively, resulting in stronger overall risk management.

Nemawashi, a Japanese term meaning "laying the groundwork" or "building consensus," originates from traditional gardening, where a tree’s roots are carefully prepared before transplanting. In business, it refers to engaging key stakeholders through informal discussions before making formal decisions. This approach ensures smoother transitions, reduces resistance, and fosters collaboration. How can the Japanese practice of 'Nemawashi' be used to align stakeholders and ensure the successful deployment of strategic initiatives Early Engagement: Bringing stakeholders into the conversation early allows their concerns and ideas to be acknowledged and addressed before formal decision-making. Building Consensus: By involving people beforehand, decisions become more widely accepted, minimizing pushback. Inclusive Decision-Making: When stakeholders feel heard and valued, they develop a sense of ownership, increasing their commitment to the initiative. Real-World Example Suppose a company is introducing a new software system. Instead of announcing it in a formal meeting, the leadership team first consults key stakeholders—developers, IT staff, and end-users. Through informal discussions, they gather feedback, address concerns, and refine the plan based on this input. By the time the formal rollout happens, there’s already widespread support, making the implementation process smoother and more successful. Nemawashi is a mindset that encourages collaboration, ensuring changes are well-received and effectively executed.

Boundary spanning means reaching out to people or organizations beyond your usual network to gain new ideas, knowledge, and resources. It brings several important benefits. First, it encourages innovation by introducing fresh ideas and technologies that can drive growth and creativity. Second, it improves collaboration by helping teams from different areas work together more effectively, breaking down barriers that often limit teamwork. Finally, it enhances adaptability, allowing organizations to quickly respond to changes in the market and stay competitive in a fast-changing world Boundary spanning is essential for driving collaboration and innovation in the industry by connecting teams and organizations across traditional boundaries. A great service industry example is how Citibank has integrated fintech partnerships to enhance its digital banking services. By working closely with payment solution providers and data analytics firms, the bank has been able to offer more personalized and efficient experiences for its customers, adapting quickly to the evolving expectations of a tech-savvy audience. Boundary spanning breaks down silos and encourages the exchange of knowledge and resources, enabling businesses to adapt to changing customer needs and remain competitive. By fostering connections across departments, industries, or regions, it helps organizations innovate, grow, and build resilience in dynamic markets.

Blockchain can be a game-changer for Lean Six Sigma (LSS) initiatives like sales commission management, offering better transparency, data accuracy, and streamlined processes. In many tele sales scenarios, the issue arises when the final executive who closes the deal gets full credit and commission, even though earlier team members played vital roles in moving the sale forward. This not only causes unfairness but also demotivates team members and impacts overall efficiency. Using blockchain, each interaction in the sales journey—starting from the initial pitch to follow-ups and the final closure—can be securely logged on an unchangeable ledger. This ensures every team member's contribution is tracked and visible. Smart contracts can be programmed to distribute commissions fairly by assigning weighted percentages to different stages of the sales process. For instance, the initial outreach could account for 50%, follow-ups for 30%, and the final closure for 20%. This approach resolves disputes, ensures fairness, and motivates teams to collaborate effectively. However, implementing blockchain isn’t without challenges. Integrating it with existing LSS frameworks can be technically complex and costly, especially for organizations with large volumes of sales data. Additionally, introducing a new system often faces resistance from employees unfamiliar with the technology, making training and change management essential. For example, in industries like real estate or high-value corporate sales, deals often take months or even years to finalize. Blockchain can ensure that early contributions, such as prospecting or relationship-building, are fairly recognized when commissions are distributed. A bank, for instance, can implement blockchain to manage sales commissions for their tele sales team handling premium loan products which can reduce disputes significantly & improve teams morale while aligning with LSS principles of process efficiency and fairness.

During the improve Phase of project to negate effects like 'Cobra effect' a tool that can come handy is 'FMEA or PFMEA'. PFMEA helps to pinpoint where and how a process might fail and the effects of those failures with a proper mitigation plan. Here is an example where a solution to a problem made the problem worse due & had unintended consequences A Banking call center implemented a Six Sigma project to reduce customer wait times. Project Team identified that long wait times were due to high call volumes and insufficient staffing during peak hours. During the brainstorming session, a short-term solution was identified where the team decided to incentivize agents with bonuses for handling more calls per hour as hiring new staff & onboarding would take at least 120 Days. As a result two Unintended Consequences occurred A) Call center agents started rushing through calls to handle more calls quickly, leading to decreased call quality and customer satisfaction. B ) Some agents started hanging up on customers without using the call clouser script and checking if the customer had any additional concerns and this was to start new calls leading to reduced client satisfaction.

Organizations, teams and people often emphasize and only report the measure of central tendency and ignore the measure of dispersion primarily due to two reasons a) Low Statistical literacy and b) Unethical behaviour A person in the organisation with low or no Statistical literacy would not know that ‘Standard deviation’ all alone is meaningless without context, and it must be considered relative to the mean (For instance, a standard deviation of 100 could be large if the mean is 100 but small if the mean is 1 billion). Similarly, such individuals may may not recognise that the simplest numerical measure of dispersion in a data set that he/she is dealing with is the range. Instead, a range would be looked at potential capability of the team or the process. For example: Assuming every employee can match the performance of the best 1 out of 1000 employees (e.g., Mr. ABC with 5% errors, minimum or Mr. XYZ with INR 1M sales, maximum). Average is looked at the ‘favourite number’ as its easier to understand and communicate to a broader audience, compared to dispersion measures like standard deviation or interquartile range. Unethical behaviour can be the second reason, where people wilfully choose an inappropriate summary measure (for example, reporting the mean for a very skewed set of data without any measures of dispersion) to distort the facts to support a particular position. Here is an example of reporting the measure of central tendency and ignoring the measure of dispersion and how did it adversely impact decision making In Banking, Tele sales executives are responsible for generating revenue overphone,they are given tele calling data base in spreadsheets, while data analytics team would have segmented the clients basis various criteria. However, client allocations are rarely random. In most tele calling teams, the average is looked at as a metric and the highest among the tele calling executives are rewarded . From the below table it looks like Agent B has the highest revenue average and also the total but the standard deviation is the highest fo B .Upon closer inspection, it becomes evident that Agent B is capitalizing on a loophole by focusing excessively on affluent clients, who tend to have higher credit card limits and larger loan eligibility amounts. Had measures of dispersion like standard deviation been reported alongside the mean, these suspicions would have been triggered earlier & such unethical practises may not have continued to distort the facts to support a particular position which in this example is about the loophole of calling & engaging with Affluent clinets disproportionately. This highlights the importance of considering measures of dispersion like standard deviation alongside central tendency metrics. Failure to do so can lead to poor decision-making, unfair rewards, and overlooked systemic issues Category Agent A Revenue (INR) Agent B Revenue (INR) Avg 498.85 525.85 Stdev 6.682853157 36.64664126 Total 9977 10517 Count of General clients engaged 16 6 Count of Affluent clients engaged 4 14 Daily performance of A and B Day Agent A Revenue (INR) Agent B Revenue (INR) Agent A Client Type Agent B Client Type 1 503 592 General Affluent 2 499 527 Affluent General 3 505 539 General Affluent 4 511 482 General Affluent 5 498 515 General Affluent 6 498 540 General Affluent 7 511 492 General General 8 505 550 Affluent Affluent 9 497 513 General Affluent 10 504 525 General General 11 497 513 General Affluent 12 497 606 Affluent General 13 502 535 Affluent General 14 487 496 General Affluent 15 488 567 General Affluent 16 496 490 General Affluent 17 493 544 General Affluent 18 502 462 General General 19 494 486 General Affluent 20 490 543 General Affluent

Below are the are the potential pitfalls or errors that could occur during the analysis when wevuse an LLM like ChatGPT to analyze whether there is a significant difference between two sets of continuous data 1. Firstly, LLMs may not understand which statistical characteristic is being analysed if it’s the mean, median ..etc 2. Direct analysis may be performed by LLMs without considering the Prechecks prior to analysis such as detecting outliers or handling missing values, may not be performed automatically leading to misleading results 3. LLMs may lack context and there are chances of choosing inappropriate alpha value. Choosing a smaller alpha value is critical specially in high-stakes scenarios an example can be of drug testing, where the continuous data might require a smaller alpha value to minimize Type I Errors 4. LLMs may also fail to differentiate between statistical tests required to be performed whether a paired t-test (used for comparing the means of two related groups) or an independent t-test (used for comparing the means of two independent groups) is appropriate for the given data. 5. Validating assumptions before performing any statistical test, such as checking for normality or equal variance, is another area where LLMs may fall short. While they may provide numerical summaries in response, they often do not generate the graphical summaries necessary for a thorough validation 6. Additionally, LLMs might proceed with a non-parametric test without verifying whether the data actually requires it. applying them unnecessarily can result in less powerful or less meaningful analysis, particularly when parametric tests are suitable for the data.

As a project leader, I would primarily focus on the resisting forces because effectively managing resistance is often the key to successfully implementing change. Most resistance from the team would be unspoken, so effectively communicating with various key stakeholders becomes the key which can be as follows Step 0 : list down the resisting forces and driving forces and assess the scores both quantitatively and qualitatively Step 1: understand the root cause of resistance which could be mostly due to individual fears or misunderstanding about project outcomes Step 2 : focus on concerns actively and build trust to minimise the retesting forces Step 3 : once the resisting forces are possibly reduced re-evaluate the scores and seamlessly implement change Step 4 : continue to connect and evaluate the potential resisting forces if any as through out the end of initiative life cycle.