| Course | GM504 Organizational Excellence and Change |
|---|---|
| Unit | Unit 7 |
| Paper type | Improvement proposal |
| Length | About 1,120 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Management |
| Updated | October 2026 |
Free sample paper for GM504 Unit 7
Make the Record Change When the Stock Does: A Unit 7 Improvement Proposal for Scan-Confirmed Picking
[Student Name]
Purdue University Global
GM504: Organizational Excellence and Change
Unit 7 Improvement Proposal
[Instructor Name]
[Date]
Ridgeway Building Supply, its staff, the vendor quotes and every figure are composite and illustrative; the methods and sources cited are real.
Summary
Ridgeway's wrong-item deliveries come mainly from bin records that no longer match what is in the bin. This proposal recommends three changes: a directed-moves module that requires yard staff to scan stock out of one bin and into another whenever they move it; pick confirmation that requires pickers to scan each item and rejects a barcode that does not match the ticket; and a cleanup of unit-of-measure errors in the item master for fasteners sold by the box. A six-week pilot in the main yard will test the package before it is extended to the branches. The predicted effect is a reduction of about 44 corrections a month, bringing the correction rate from 5.8 percent to about 4.0 percent.
Problem Statement
Stock moves in the yard are never recorded in the inventory system. As a result, 15.5 percent of audited bins hold something other than what the system lists, and 38 of the 52 wrong-item corrections in the baseline month came from such bins. Pickers follow the ticket to the bin the system names, and when that bin holds a similar product, the wrong item goes on the truck.
Three Alternatives
A second staging checker. One employee per shift reviews each staged load line by line before departure. This would catch most wrong items before delivery and could start next week. It costs about $42,000 a year in wages for two shifts. But it removes no cause. Errors would still be made and then caught, and the Unit 1 experience showed that a checker is the first person pulled away when volume rises. Shigeo Shingo distinguished judgment inspection, which finds defects after they occur, from source inspection, which prevents them at the point where they arise; a checker is judgment inspection (Shingo, 1986).
Retraining pickers. A refresher on careful picking and look-alike products would cost little and might reduce errors among new pickers. But the root cause analysis found that pickers followed the tickets correctly; the records were wrong. Retraining would ask pickers to second-guess the system, which slows picking and still depends on attention.
System-enforced scanning. Directed moves and pick confirmation change the process so that the record updates when stock moves and the system refuses a mismatched pick. This removes the cause of most wrong-item corrections and catches the remainder at the point of picking. It costs more at the start and takes several weeks to implement.
A checker finds the wrong underlayment after it is staged; a scan at the bin stops it from leaving the bin, and a scan at every move keeps the bin record true in the first place.
Weighing the Alternatives
Compared on cost, speed and whether each removes the cause or only catches its effects, the second checker is fastest but removes nothing, retraining is cheapest but misreads the cause, and scanning is the only option that addresses it. Deming warned that quality cannot be inspected into a product; it has to be built into the process that makes it (Deming, 1986). Scanning builds the check into the process.
The Recommended Package
Directed moves. The inventory system's directed-moves module lets a yard employee scan a product's barcode, scan the bin it is leaving and scan the bin it is entering, using the handheld scanners pickers already carry. The system updates the location immediately. Receiving crews will be required to record every move, including moves to overflow.
Pick confirmation. When a picker scans an item, the system checks it against the ticket. A mismatch triggers an alert, and the picker must scan the correct item before the line is marked picked. Overrides require the yard lead's code and are logged.
Item master cleanup. Fasteners are sold in boxes of 100, 250 and 1,000, and several items have the wrong unit of measure in the system, which causes short-quantity errors when a picker pulls one box of 100 for an order of 1,000. A one-time review of about 600 fastener items will correct units of measure.
Pilot Plan
The pilot runs for six weeks in the main yard, which handles about 60 percent of delivery orders. The first week is configuration and training. Weeks two through six run with full scanning. The yard operations manager owns the pilot, the inventory control lead owns the item master cleanup and the bin audit, and the project lead tracks the measures defined in Unit 5. The pilot succeeds if the main yard's wrong-item corrections fall by at least half and bin-location accuracy rises above 95 percent.
Predicted Effect
If scanning eliminates most corrections caused by mismatched bins, wrong-item corrections should fall from about 52 to about 16 a month, since some wrong items come from look-alike products in correct bins and from order-entry mistakes, which scanning cannot fix. The item master cleanup should reduce short-quantity corrections from about 41 to about 33. Together that is about 44 fewer corrections a month. The charter's goal of 3.5 percent would require further reductions in damage and missing add-ons, which this proposal does not address.
Why Start With the Largest Bar
Wrong items are not the only correction category, but they are the largest and the one with the clearest cause. Quality improvement works best when a team concentrates on the few categories that carry most of the problem and on causes it can verify, rather than spreading effort across every source of error at once (Juran & Godfrey, 1999). Damage in transit and missing add-ons have different causes, such as load securing and phone-order handling, and deserve their own projects once this one is stable. Combining them here would delay the pilot and make it harder to tell which change produced which result.
Risks
Pickers may find scanning slower at first. The pilot will measure pick times and adjust. Overrides could become routine if the yard lead approves them freely; the override log will be reviewed weekly. And directed moves depend on receiving crews scanning every move, which the control plan in Unit 9 must protect.
Conclusion
The proposal rejects a second checker because it catches errors without removing their cause. It recommends scan-confirmed moves and picks and an item master cleanup, tested in a six-week pilot with named owners. The predicted reduction of about 44 corrections a month addresses the largest category of errors at its source, and the cost and benefit analysis in Unit 8 tests whether it pays.
References
Deming, W. E. (1986). Out of the crisis. MIT Press.
Juran, J. M., & Godfrey, A. B. (Eds.). (1999). Juran's quality handbook (5th ed.). McGraw-Hill.
Shingo, S. (1986). Zero quality control: Source inspection and the poka-yoke system. Productivity Press.
What the GM504 Unit 7 assignment asks for
GM504's seventh unit asks for an improvement proposal grounded in the verified cause. Open with a short summary a decision maker could act on. Restate the problem and its cause in a sentence or two. Then weigh at least three alternatives against the same criteria, such as cost, speed and whether each removes the cause or only catches its effects; inspection-based options deserve a fair hearing and a clear reason if rejected. Describe the recommended package in enough detail that the people implementing it understand what changes. Plan a pilot with a defined scope, duration, owners and success criteria. Predict the effect with reasoning tied to the root cause analysis, and say honestly if it falls short of the project goal. Explain why the proposal targets the categories it does. Name the risks and how each will be watched. Expect about eight pages in APA 7, citing sources on mistake-proofing and quality management.
How this GM504 Unit 7 example is built
The summary names the three changes, the six-week pilot and the predicted move from 5.8 to about 4.0 percent. The problem statement repeats the audit result and the 38 wrong-item orders traced to mismatched bins. Three alternatives follow: a staging checker costing about $42,000 a year, framed with Shingo's distinction between judgment and source inspection; retraining, which misreads the cause; and scanning. The highlighted sentence contrasts a checker with a scan at the bin, and Deming supports building quality into the process. The package describes directed moves on existing handhelds, pick confirmation with logged overrides and a review of about 600 fastener items. The pilot names the yard operations manager and inventory control lead as owners, with success defined as halving wrong items and passing 95 percent bin accuracy. The prediction and its gap from the 3.5 percent goal, Juran on focusing on the vital few and three risks complete the proposal.
Reading the GM504 Unit 7 grading rubric
The rubric for this GM504 proposal rewards a recommendation that follows from the root cause. Instructors check that alternatives are compared on the same criteria and that inspection-based options are rejected for stated reasons rather than ignored. The recommended package should be specific enough to implement, and each part should address a verified cause. A pilot with scope, duration, owners and success criteria earns significant credit, since it lets the organization test the change before committing. Predictions should be reasoned from the analysis, and admitting a shortfall against the goal shows integrity. Risks should come with monitoring. Shingo's work on source inspection and poka-yoke, Deming's Out of the Crisis and Juran's Quality Handbook provide the conceptual support in APA 7 for preventing rather than catching errors.
Common GM504 Unit 7 mistakes, and how to avoid them
GM504 Unit 7 proposals often recommend the change the writer favored from the start and treat alternatives as an afterthought. Others bundle many unrelated fixes, which makes it impossible to tell later which one worked. A common mistake is choosing an inspection-based fix because it is fast, without acknowledging that it leaves the cause in place. Some writers promise to reach the project goal without showing how. Pilots are frequently described vaguely, with no success criteria. Restate the verified cause, compare at least three options on cost, speed and whether they remove the cause, recommend the package that does, describe it in implementable detail, plan a pilot with owners and a clear test, predict the effect from your data, admit any shortfall and list the risks along with how each will be tracked.
Get a GM504 Unit 7 example written to your instructions
Send the cause your analysis established, even roughly, the fix you currently favor, and any budget or technology limits your organization works under, along with the Unit 7 prompt and rubric. Within 24-48h a first proposal comes back free, matched to your section's instructions, with alternatives weighed and the predicted effect stated in numbers. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More GM504 papers and MS in Management samples
- GM504 Unit 1: Faded Improvement Discussion Post
- GM504 Unit 2: Baldrige Fit for a Distributor Analysis
- GM504 Unit 3: Delivery Order Process Map
- GM504 Unit 4: Wrong-Item Delivery Root Cause Analysis
- GM504 Unit 5: Delivery Correction Measurement Plan
- GM504 Unit 6: 5S Decay Seminar Reflection
- GM504 Unit 8: Cost and Benefit Analysis
- GM504 Unit 9: Sustainment Plan
- GM504 Unit 10: Excellence Project Report
- GM503 Unit 7: School Bus Servant Leadership Paper
- GM502 Unit 7: Two Sales Managers Path-Goal Case
- GM501 Unit 7: Four-Day Week Pilot Decision Memo
- GM500 Unit 7: Per-Stop Pay Motivation Theory Case
GM504 Unit 7 questions, answered
Should the proposal include more than one change?
Only where each change addresses a separate verified cause. Bundling unrelated fixes makes it impossible to tell later which one worked, and graders often read a long list as a sign that the analysis did not settle anything. The example proposes three linked changes because the analysis found two causes, and it says which change is expected to move which error type.
What if my organization cannot afford the ideal fix?
Propose what it can afford and be honest about the difference. A cheaper change that still removes the cause, such as a manual move log kept at each aisle, is better than an unfunded ideal. State the tradeoff: the manual version depends on people remembering, so it needs a stronger sustainment plan than a system-enforced one would.
Is mistake-proofing the same as poka-yoke?
Yes. Poka-yoke is the Japanese term associated with Shigeo Shingo and the Toyota Production System, and it covers devices or process designs that make an error impossible or immediately obvious. A barcode scan that refuses the wrong product is a common modern example. Citing Shingo, or a Lean text that discusses his work, strengthens a proposal built on the idea.
Where can I find a free GM504 Unit 7 sample paper?
This page carries a full GM504 Unit 7 improvement proposal for scan-confirmed stock moves and picking at a building-supply distributor, weighing three alternatives, with a pilot plan, a predicted effect and APA 7 references.
Why reject a second checker?
A checker finds wrong items after they are picked and removes no cause. It costs about $42,000 a year, and the earlier staging check showed that a checker is the first person reassigned when volume rises, after which the errors return.