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 06/01/2025 in Posts

  1. I will take as an example of the procurement report (weekly/monthly). Why I can say that report is efficient because of the following reasons mentioned below: It is an auto-generated report that pulls the data from the system and sends an automatic email to the team (weekly). The report comprises the vendor details, item description, category or section, cost (material, freight & duties), order status, and timeline to reach the factory, etc. This allows team to track the purchase list and plan the work (maintenance) at the factory. The report is generated monthly in a standardized format with consistent charts and tables, which makes it easy to visualize at a glance. The report will give real-time visibility to the report because it is integrated with Power BI, so anyone can access and view the report. From a business excellence perspective, this seems ineffective because it focuses on reporting data rather than driving strategic actions and value optimization. Lack of Actionable Insights: While the shows you that what was spent and where, it rarely explains why the purchase occurred or what opportunities exist for optimization. For example, it might show a high spend in the "machine category or particular machine section," but it won't show if that purchase was strategic, redundant, or if there were better alternative options. Hiding Inefficiencies and Poor Practices: A high expense shown for "emergency breakdown machine parts that we bought and also items shipped by air cargo (air freight cost higher than sea freight)" in the report, but the report doesn't give an idea why these purchases occur and what the manufacturing loss will be if these items do not arrive on time to the stakeholders (e.g., poor planning, lead time, vendor issues, etc.). Supplier Performance Valuation: The report focuses on items bought in different "categories and section" and how much the "supplier contributes in overall purchases", not on supplier performance or contract compliance. It won't highlight if a low-cost supplier is consistently delivering the material late or with quality issues, which leads to manufacturing downtime & production loss. Focus on Cost, Not on Value: The report highlights the expenses, it doesn't show what value was received for that purchase. Higher expenses in a certain category might be justified to the stakeholders if they lead to significant improvements in productivity and quality.
  2. PRACTICE: Daily Automated OEE Reports (Overall Equipment Effectiveness) PORTRAYED Efficiency: In this scenario, my organization automated the daily Overall Equipment Effectiveness (OEE) report. The automated generation of the daily Overall Equipment Effectiveness (OEE) reports was seen as a lean best practice. These reports were derived from data gotten directly from machines and were displayed and used as real-time performance metrics showing availability, performance, and quality across the various production lines. Stakeholders thought it was an example of the industry 4.0-driven efficiency which is known to be fast, data-driven, and standardized. Why It’s Actually Ineffective: Though this practice looked effective from a business excellence point of view, it actually masked significant inefficiencies like: Over dependent on surface level metrics: In depth analysis could not be gotten with surface level data. Even though OEE is a valuable KPI, it should not be used to drive primary performance decisions. For example, lines with high OEE scores may sometimes experience frequent stoppages or unforeseen quality issues that wouldn’t be flagged clearly in the summary metric. Instead of investigating underlying problems, operators would only be concerned about “protecting the numbers” Lack of Contextual Interpretation: Because reports were auto generated and shared, they lacked frontline insights and narrative context. This in turn gave room for doubts regarding the data provided in meetings because the integrity of the data was not trusted. Illusion of Continuous Improvement: The automation portrayed a false sense of control and progress because the data could not be depended on. Without accurate data for RCAs, stakeholders could not use the report to drive real improvement. The organization tracked problems but could not manage them, this act violates a core principle of business excellence. Business Excellence Lens: In a framework like lean six sigma, excellence requires not just the collection of data, but the usage of data for learning and innovation. The OEE reports that were automated lacked feedback loops and cross-functional engagements with other teams like shopfloor teams, thereby limiting organizational learning. Conclusion: What seems efficient will not always be effective. In this scenario, the automation of reporting replaced human insight with speed, optimizing for data delivery, but did not give data value. Business Excellence calls us to go deeper: using metrics as tools for engagement, improvement, and aligned decision-making, and not just dashboards for compliance’s sake.
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.