Learning Objectives<\/p>\n\n<\/header>\n
By the end of this chapter, students will be able to:<\/p>\n\n
- \n \t
- \n
Interpret a throughput and on-time trend against explicit targets and call out meaningful patterns.<\/p>\n<\/li>\n \t
- \n
Compare periods (week-over-week or month-over-month) to avoid mistaking seasonality or day-of-week effects for true change.<\/p>\n<\/li>\n \t
- \n
Build and read a Pareto view that identifies the few categories contributing most to defects or late units.<\/p>\n<\/li>\n \t
- \n
Translate findings into one specific operational action (what, where, when, who) for the next review.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\nThis chapter sharpens the dashboard you built in Chapter 7 into a decision tool. The aim isn\u2019t more charts; it\u2019s better judgment. We\u2019ll read the pulse<\/em> of throughput and service against targets, compare performance across periods so we don\u2019t chase noise, and use a Pareto to focus on the few issues that cause most of the pain. You\u2019ll see how to frame a finding (\u201cwhat changed, by how much, and where?\u201d), and how to turn it into a concrete action for the coming week. Everything runs in Power BI using the datasets you already loaded.\n
8.1 What \u201cadvanced\u201d means here<\/strong><\/h2>\n
Advanced performance work is not about more sophisticated formulas; it\u2019s about separating signal from noise so managers intervene where it matters. In operations, random day-to-day bumps are normal. We care about runs<\/em> (several days below target), shifts<\/em> (a new level), and where<\/em> the misses concentrate (by region, route, line, or blend). The rest of this chapter teaches you to see those patterns quickly and defend your interpretation with simple, honest visuals.<\/p>\n\n
8.2 The pulse: throughput and on-time vs. target<\/strong><\/h2>\n
Start with the pulse: two compact visuals that answer \u201cAre we on pace?\u201d and \u201cAre we meeting service?\u201d Place On-Time % as a daily line filtered to the last 28 days, and a companion visual for Throughput Units over the same window. Add the target as a constant line (Analytics pane) so the eye knows immediately whether we\u2019re where we should be.<\/p>\n
How to read the pulse:<\/p>\n\n
- \n \t
- \n
Look for runs<\/em> below the target (e.g., two or more consecutive days). That\u2019s an operational event, not random noise.<\/p>\n<\/li>\n \t
- \n
Scan for day-of-week rhythm. If Fridays and Saturdays dip, that\u2019s a capacity or sequencing issue during a predictable peak.<\/p>\n<\/li>\n \t
- \n
Pair the story: if throughput spikes on promo days while on-time drops, the likely cause is load, not a carrier failure.<\/p>\n<\/li>\n<\/ul>\n
Make the visuals carry the story. Titles state the takeaway (\u201cOn-time below 95% for two of the last five days\u201d), axes include units\/percent, and one short annotation calls out an exception (\u201cPromo 8\/15\u201d). If labels crowd, reduce detail rather than shrinking text\u2014managers should be able to read this on a laptop or projector without squinting.<\/p>\n\n
8.3 Rolling comparisons: week-over-week and month-over-month<\/strong><\/h2>\n
A pulse can look alarming until you compare it with the prior period. Rolling comparisons keep us from overreacting to seasonality.<\/p>\n
Use week-over-week for daily dashboards and month-over-month for monthly reviews. In Power BI, you can duplicate the pulse visuals and switch the page\u2019s date range to the previous<\/em> period, or add a paired card showing the change (e.g., On-Time % \u0394 vs last week) using Quick Measures \u2192 Time intelligence (percentage difference from previous period). The important part is interpretation: are we trending up or down relative to a comparable window, and is that movement operationally meaningful?<\/p>\n
Reading the comparison:<\/p>\n\n
- \n \t
- \n
If On-Time % is down vs last week and the deficit clusters on the same weekdays, the fix is likely staffing or sequencing rather than a random blip.<\/p>\n<\/li>\n \t
- \n
If throughput is higher but service held steady, celebrate: that\u2019s evidence your process absorbed a surge.<\/p>\n<\/li>\n \t
- \n
If both worsened, link back to the slice that explains it (region, blend, route, or line).<\/p>\n<\/li>\n<\/ul>\n
Keep the display simple: one \u0394 card per KPI, green when better than last period, red when worse. You\u2019re teaching managers to expect context, not just a snapshot.<\/p>\n
(Clicks only: Quick Measure \u2192 Time intelligence \u2192 \u201cMonth over month change\u201d or \u201cPrevious period\u201d requires marking Calendar as the Date table, which you already did in Ch. 7.)<\/em><\/p>\n\n
8.4 Pareto: focus on the biggest few<\/strong><\/h2>\n
Once you know performance moved, the next question is where to intervene<\/em>. The Pareto principle says a small number of categories often account for most of the problem. Build a sorted bar chart (descending) of your chosen driver\u2014defect type, region, route, or line\u2014using the adverse metric (Defects, or Late Units). Add a Top N filter (e.g., Top 5) so the eye lands on the levers first. If you\u2019d like to emphasize proportion, show data labels as percentages of the total.<\/p>\n
How to read it:<\/p>\n\n
- \n \t
- \n
Name the concentration: \u201cTwo routes account for 57% of late units this month.\u201d<\/p>\n<\/li>\n \t
- \n
Ask for plausibility: does this match what supervisors see on the floor or in the field?<\/p>\n<\/li>\n \t
- \n
Propose the smallest action that could move the needle (reroute, add a shift, recheck a line).<\/p>\n<\/li>\n<\/ul>\n
The aim isn\u2019t a perfect 80\/20 curve; it\u2019s a ranked list that credibly points to where action will help most.<\/p>\n\n
8.5 Stability check: simple rules without full SPC<\/strong><\/h2>\n
You don\u2019t need a full control chart to avoid knee-jerk reactions. Two simple heuristics catch most meaningful shifts:<\/p>\n\n
- \n \t
- \n
Two-day rule: two or more consecutive days below target merits a look.<\/p>\n<\/li>\n \t
- \n
Four-of-five rule: if four of five recent days are below target\u2014even if not consecutive\u2014flag it.<\/p>\n<\/li>\n<\/ol>\n
Use these as review triggers<\/em>, not conclusions. Triggers send you back to the slice or process step that explains the miss. On the page, a small text box labeled \u201cTriggers this week\u201d lists which rule fired and on which dates. That makes your thresholding explicit and repeatable<\/p>\n\n
8.6 Applied assignment \u2014 Performance Pulse (Power BI)<\/strong><\/h2>\n
What you submit (lightweight):<\/strong><\/p>\n\n
- \n \t
- \n
One Power BI page that extends your Chapter 7 dashboard with:<\/p>\n\n
- \n \t
- \n
a 28-day On-Time % pulse (target line, one annotation),<\/p>\n<\/li>\n \t
- \n
a Throughput Units pulse aligned to the same dates, and<\/p>\n<\/li>\n \t
- \n
a Pareto (sorted bars with Top N) for the driver you choose (defect type, region, route, or line).
Add two small \u0394 cards (week-over-week or month-over-month) for On-Time % and Throughput.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n \t - \n
One paragraph memo (5\u20136 sentences) that states the question, summarizes the pulse and the comparison, names the top contributor from the Pareto, and commits to one action with owner and timing.<\/p>\n<\/li>\n<\/ul>\n
How it\u2019s graded:<\/strong><\/p>\n\n
- \n \t
- \n
The page makes the status clear (targets visible, \u0394 cards readable, labels meaningful).<\/p>\n<\/li>\n \t
- \n
The Pareto is sorted and focused (Top N).<\/p>\n<\/li>\n \t
- \n
The memo proposes a realistic action for the next week.<\/p>\n<\/li>\n<\/ul>\n
\n Key Takeaways<\/p>\n\n<\/header>\n
\n- \n \t
- \n
Focus on separating signal from noise rather than reacting to daily variation.<\/p>\n<\/li>\n \t
- \n
Pulse visuals track throughput and on-time performance against targets.<\/p>\n<\/li>\n \t
- \n
Rolling comparisons (week-over-week, month-over-month) add essential context.<\/p>\n<\/li>\n \t
- \n
Pareto charts reveal the small number of drivers causing most issues.<\/p>\n<\/li>\n \t
- \n
Simple stability rules (two-day, four-of-five) flag meaningful shifts.<\/p>\n<\/li>\n \t
- \n
Dashboards are decision tools when visuals link directly to actions.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
Chapter 8 References<\/h2>\nAmerican Society for Quality. (n.d.). What is a Pareto chart? Analysis & diagram<\/em>. ASQ. https:\/\/asq.org\/quality-resources\/pareto<\/a>\n\nMicrosoft. (2024, March 15). Use quick measures for common and powerful calculations<\/em>. Microsoft Learn. https:\/\/learn.microsoft.com\/en-us\/power-bi\/transform-model\/desktop-quick-measures<\/a>\n\nMicrosoft. (n.d.). What is Power BI?<\/em> Microsoft. https:\/\/learn.microsoft.com\/en-us\/power-bi\/fundamentals\/power-bi-overview<\/a>\n\nOpenStax. (2019). Principles of management.<\/em> OpenStax, Rice University. https:\/\/openstax.org\/books\/principles-management\/pages\/6-introduction<\/a>","rendered":"
![\"image\"](\"https:\/\/openbooks.spmvv.ac.in\/app\/uploads\/sites\/3\/2025\/08\/Chapter-8-Header.png\")
<\/p>\n\n\n Learning Objectives<\/p>\n<\/header>\n
\nBy the end of this chapter, students will be able to:<\/p>\n
- \n
- \n
Interpret a throughput and on-time trend against explicit targets and call out meaningful patterns.<\/p>\n<\/li>\n
- \n
Compare periods (week-over-week or month-over-month) to avoid mistaking seasonality or day-of-week effects for true change.<\/p>\n<\/li>\n
- \n
Build and read a Pareto view that identifies the few categories contributing most to defects or late units.<\/p>\n<\/li>\n
- \n
Translate findings into one specific operational action (what, where, when, who) for the next review.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
This chapter sharpens the dashboard you built in Chapter 7 into a decision tool. The aim isn\u2019t more charts; it\u2019s better judgment. We\u2019ll read the pulse<\/em> of throughput and service against targets, compare performance across periods so we don\u2019t chase noise, and use a Pareto to focus on the few issues that cause most of the pain. You\u2019ll see how to frame a finding (\u201cwhat changed, by how much, and where?\u201d), and how to turn it into a concrete action for the coming week. Everything runs in Power BI using the datasets you already loaded.<\/p>\n
8.1 What \u201cadvanced\u201d means here<\/strong><\/h2>\n
Advanced performance work is not about more sophisticated formulas; it\u2019s about separating signal from noise so managers intervene where it matters. In operations, random day-to-day bumps are normal. We care about runs<\/em> (several days below target), shifts<\/em> (a new level), and where<\/em> the misses concentrate (by region, route, line, or blend). The rest of this chapter teaches you to see those patterns quickly and defend your interpretation with simple, honest visuals.<\/p>\n
8.2 The pulse: throughput and on-time vs. target<\/strong><\/h2>\n
Start with the pulse: two compact visuals that answer \u201cAre we on pace?\u201d and \u201cAre we meeting service?\u201d Place On-Time % as a daily line filtered to the last 28 days, and a companion visual for Throughput Units over the same window. Add the target as a constant line (Analytics pane) so the eye knows immediately whether we\u2019re where we should be.<\/p>\n
How to read the pulse:<\/p>\n
- \n
- \n
Look for runs<\/em> below the target (e.g., two or more consecutive days). That\u2019s an operational event, not random noise.<\/p>\n<\/li>\n
- \n
Scan for day-of-week rhythm. If Fridays and Saturdays dip, that\u2019s a capacity or sequencing issue during a predictable peak.<\/p>\n<\/li>\n
- \n
Pair the story: if throughput spikes on promo days while on-time drops, the likely cause is load, not a carrier failure.<\/p>\n<\/li>\n<\/ul>\n
Make the visuals carry the story. Titles state the takeaway (\u201cOn-time below 95% for two of the last five days\u201d), axes include units\/percent, and one short annotation calls out an exception (\u201cPromo 8\/15\u201d). If labels crowd, reduce detail rather than shrinking text\u2014managers should be able to read this on a laptop or projector without squinting.<\/p>\n
8.3 Rolling comparisons: week-over-week and month-over-month<\/strong><\/h2>\n
A pulse can look alarming until you compare it with the prior period. Rolling comparisons keep us from overreacting to seasonality.<\/p>\n
Use week-over-week for daily dashboards and month-over-month for monthly reviews. In Power BI, you can duplicate the pulse visuals and switch the page\u2019s date range to the previous<\/em> period, or add a paired card showing the change (e.g., On-Time % \u0394 vs last week) using Quick Measures \u2192 Time intelligence (percentage difference from previous period). The important part is interpretation: are we trending up or down relative to a comparable window, and is that movement operationally meaningful?<\/p>\n
Reading the comparison:<\/p>\n
- \n
- \n
If On-Time % is down vs last week and the deficit clusters on the same weekdays, the fix is likely staffing or sequencing rather than a random blip.<\/p>\n<\/li>\n
- \n
If throughput is higher but service held steady, celebrate: that\u2019s evidence your process absorbed a surge.<\/p>\n<\/li>\n
- \n
If both worsened, link back to the slice that explains it (region, blend, route, or line).<\/p>\n<\/li>\n<\/ul>\n
Keep the display simple: one \u0394 card per KPI, green when better than last period, red when worse. You\u2019re teaching managers to expect context, not just a snapshot.<\/p>\n
(Clicks only: Quick Measure \u2192 Time intelligence \u2192 \u201cMonth over month change\u201d or \u201cPrevious period\u201d requires marking Calendar as the Date table, which you already did in Ch. 7.)<\/em><\/p>\n
8.4 Pareto: focus on the biggest few<\/strong><\/h2>\n
Once you know performance moved, the next question is where to intervene<\/em>. The Pareto principle says a small number of categories often account for most of the problem. Build a sorted bar chart (descending) of your chosen driver\u2014defect type, region, route, or line\u2014using the adverse metric (Defects, or Late Units). Add a Top N filter (e.g., Top 5) so the eye lands on the levers first. If you\u2019d like to emphasize proportion, show data labels as percentages of the total.<\/p>\n
How to read it:<\/p>\n
- \n
- \n
Name the concentration: \u201cTwo routes account for 57% of late units this month.\u201d<\/p>\n<\/li>\n
- \n
Ask for plausibility: does this match what supervisors see on the floor or in the field?<\/p>\n<\/li>\n
- \n
Propose the smallest action that could move the needle (reroute, add a shift, recheck a line).<\/p>\n<\/li>\n<\/ul>\n
The aim isn\u2019t a perfect 80\/20 curve; it\u2019s a ranked list that credibly points to where action will help most.<\/p>\n
8.5 Stability check: simple rules without full SPC<\/strong><\/h2>\n
You don\u2019t need a full control chart to avoid knee-jerk reactions. Two simple heuristics catch most meaningful shifts:<\/p>\n
- \n
- \n
Two-day rule: two or more consecutive days below target merits a look.<\/p>\n<\/li>\n
- \n
Four-of-five rule: if four of five recent days are below target\u2014even if not consecutive\u2014flag it.<\/p>\n<\/li>\n<\/ol>\n
Use these as review triggers<\/em>, not conclusions. Triggers send you back to the slice or process step that explains the miss. On the page, a small text box labeled \u201cTriggers this week\u201d lists which rule fired and on which dates. That makes your thresholding explicit and repeatable<\/p>\n
8.6 Applied assignment \u2014 Performance Pulse (Power BI)<\/strong><\/h2>\n
What you submit (lightweight):<\/strong><\/p>\n
- \n
- \n
One Power BI page that extends your Chapter 7 dashboard with:<\/p>\n
- \n
- \n
a 28-day On-Time % pulse (target line, one annotation),<\/p>\n<\/li>\n
- \n
a Throughput Units pulse aligned to the same dates, and<\/p>\n<\/li>\n
- \n
a Pareto (sorted bars with Top N) for the driver you choose (defect type, region, route, or line).
Add two small \u0394 cards (week-over-week or month-over-month) for On-Time % and Throughput.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n - \n
One paragraph memo (5\u20136 sentences) that states the question, summarizes the pulse and the comparison, names the top contributor from the Pareto, and commits to one action with owner and timing.<\/p>\n<\/li>\n<\/ul>\n
How it\u2019s graded:<\/strong><\/p>\n
- \n
- \n
The page makes the status clear (targets visible, \u0394 cards readable, labels meaningful).<\/p>\n<\/li>\n
- \n
The Pareto is sorted and focused (Top N).<\/p>\n<\/li>\n
- \n
The memo proposes a realistic action for the next week.<\/p>\n<\/li>\n<\/ul>\n
\n\n Key Takeaways<\/p>\n<\/header>\n
\n- \n
- \n
Focus on separating signal from noise rather than reacting to daily variation.<\/p>\n<\/li>\n
- \n
Pulse visuals track throughput and on-time performance against targets.<\/p>\n<\/li>\n
- \n
Rolling comparisons (week-over-week, month-over-month) add essential context.<\/p>\n<\/li>\n
- \n
Pareto charts reveal the small number of drivers causing most issues.<\/p>\n<\/li>\n
- \n
Simple stability rules (two-day, four-of-five) flag meaningful shifts.<\/p>\n<\/li>\n
- \n
Dashboards are decision tools when visuals link directly to actions.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n
Chapter 8 References<\/h2>\n
American Society for Quality. (n.d.). What is a Pareto chart? Analysis & diagram<\/em>. ASQ. https:\/\/asq.org\/quality-resources\/pareto<\/a><\/p>\n
Microsoft. (2024, March 15). Use quick measures for common and powerful calculations<\/em>. Microsoft Learn. https:\/\/learn.microsoft.com\/en-us\/power-bi\/transform-model\/desktop-quick-measures<\/a><\/p>\n
Microsoft. (n.d.). What is Power BI?<\/em> Microsoft. https:\/\/learn.microsoft.com\/en-us\/power-bi\/fundamentals\/power-bi-overview<\/a><\/p>\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n