| Course | MT236 Introduction to Supply Chain Management |
|---|---|
| Unit | Unit 8 |
| Paper type | Process improvement proposal |
| Length | About 890 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Business Administration |
| Updated | October 2026 |
Free sample paper for MT236 Unit 8
From 3.2 Days to 1.2: A Unit 8 Process Improvement Proposal for a Hot Sauce Maker's Order-to-Truck Time
[Student Name]
Purdue University Global
MT236: Introduction to Supply Chain Management
Unit 8 Process Improvement Proposal
[Instructor Name]
[Date]
Alamo Ridge Pepper Co., its orders, timings and every cost are composite and illustrative; bracketed figures stand where order records and quotes would supply the numbers; the sources cited are real.
The Problem
The Texas grocery chain's supplier rules require orders to ship within two business days of the purchase order. Alamo Ridge Pepper Co. averages about 3.2 days. Last year [81] of its [260] orders from the chain shipped late, and the chain charged [$125] for each, about [$10,125] in chargebacks. Late shipments also hurt the company's supplier rating, which the chain reviews twice a year.
How the Time Was Measured
Over six weeks, the operations coordinator timed [sixty] orders from the moment the purchase order arrived by email to the moment the truck left the dock, recording when each step started and ended. Rother and Shook (1999) recommend this kind of direct measurement when mapping a value stream, because the times people remember are usually shorter than the times the process actually takes.
Where the Days Go
The 3.2 days divide into four parts. About 0.9 days pass before the order is keyed, because the office enters all purchase orders in one batch at 2 p.m. each day, so a morning order waits most of a day and an afternoon order waits until the next. Picking and packing take about 0.5 days. About 1.4 days pass with the order staged on the dock, because the coordinator requests a carrier pickup only after picking is finished, and the chain's contracted carrier needs 24 to 48 hours of notice. Loading, paperwork and other steps take about 0.4 days.
Only the half day of picking and packing is work on the order. The other 2.7 days are waiting. Womack and Jones (2003) argued that most of the time products spend in a process is waiting rather than value-adding work, and that removing the waits usually gains more than speeding up the work.
Of the 3.2 days, the order is being worked on for half of one.
The Two Changes
The first change removes the keying wait. The chain can send purchase orders through electronic data interchange, which Alamo Ridge has never set up. An EDI translation service would import each order into the company's system as it arrives, with no manual keying. For orders still received by email, the office would key them within an hour of arrival rather than in a daily batch. The wait before keying would fall from about 0.9 days to about 0.2.
The second change removes most of the staging wait. The coordinator would request the carrier appointment at the moment the order is entered, not after picking. Because picking takes about half a day and the carrier needs 24 hours, the truck would arrive soon after the order is packed. Staging would fall from about 1.4 days to about 0.3.
With loading and paperwork trimmed slightly by preparing the bill of lading at order entry, the total falls to about 1.2 business days, well inside the chain's two-day rule.
Why Not Add a Picker
The owner's first idea was to hire a second warehouse worker so orders could be picked faster. The timing shows why that would not help. Picking and packing already take only half a day, and a second picker might cut that to a third of a day, saving perhaps 0.2 days. The order would still wait 0.9 days to be keyed and 1.4 days for a truck. Adding labor to the one step that is not the problem would cost about [$38,000] a year and leave the order late.
The timing also showed a pattern worth noting. Orders arriving on Thursday afternoon and Friday were the most often late, because the 2 p.m. batch and the carrier's notice period together pushed them past the weekend. Under the proposal, a Friday morning order would be keyed by midday, its appointment requested at once and its truck booked for Monday morning.
Cost and Savings
The EDI service costs about [$1,500] to set up and about [$200] a month, or [$2,400] a year. Requesting appointments earlier costs nothing but a change in routine. If late shipments fall from 81 to about [10] a year, chargebacks fall by about [$8,900]. The net saving in the first year is about [$5,000] after setup, rising to about [$6,500] a year after. Hopp and Spearman (2008) note that reducing the variability of waiting times also makes a process more predictable, which here would protect the company's supplier rating.
Risks
Two risks need attention. If picking takes longer than half a day on a large order, the truck could arrive before the order is ready; the coordinator should request appointments for large orders a half day later. And the EDI service will need testing with the chain's system before it goes live; a two-week trial running alongside email orders would catch errors.
Measures
The company will track purchase-order-to-truck time on every order, aiming for no more than a day and a half, the number of late shipments per quarter, with a target below three, and chargebacks per quarter.
References
Hopp, W. J., & Spearman, M. L. (2008). Factory physics (3rd ed.). McGraw-Hill.
Rother, M., & Shook, J. (1999). Learning to see: Value stream mapping to add value and eliminate muda. Lean Enterprise Institute.
Womack, J. P., & Jones, D. T. (2003). Lean thinking: Banish waste and create wealth in your corporation (Rev. ed.). Free Press.
What the MT236 Unit 8 assignment asks for
The eighth unit usually asks for a proposal to improve one process in a company's supply chain, built on measured evidence. Pick a process with a clear performance measure, such as order-to-ship time, and a stated target or customer rule. Measure the current process directly, step by step, and separate work time from waiting time, since most delay is usually waiting. Propose changes aimed at the largest waits and show the expected new time. Test at least one alternative fix, especially the one managers suggest first. Estimate costs and savings with their basis stated, name risks and set measures. A timeline or simple process map helps. Expect four to five pages with a before-and-after table in your own version, citing lean or process improvement sources in APA 7, and say how many orders or cycles were timed.
How this MT236 Unit 8 example is built
The proposal opens with the chain's two-day rule, the late shipments and the chargebacks. A method section explains timing sixty orders, with Rother and Shook on direct measurement. The time breakdown follows, and Womack and Jones explain why waiting dominates, while a margin note and the highlighted line show only half a day of work. A section tests the owner's idea of hiring a picker and finds it would save about 0.2 days, and notes that Thursday and Friday orders fail most, with a second note. The two changes are described, electronic order import and early appointment requests, with their effect on each wait. Costs and savings follow, with Hopp and Spearman on reducing variability. Risks cover large orders and testing the data link, and measures close the proposal.
Where the points sit in the MT236 Unit 8 rubric
Process improvement proposals in MT 236 are generally graded on measurement, diagnosis and fit of the solution. Timing the process directly, with a stated sample size, earns more than estimates from memory. Separating work from waiting shows the writer understands where delay comes from. Graders reward proposals that test the obvious alternative and explain why it fails. Each change should target a specific wait, with a new expected time. Costs and savings need a basis. Risks should come with responses, and measures should match the original problem. A clear before-and-after comparison makes the case easy to follow. Womack and Jones, Rother and Shook and Hopp and Spearman should be cited.
MT236 Unit 8 help: mistakes that cost points
Process proposals often go wrong by recommending more labor or new equipment without measuring where the time goes. Another frequent issue is timing only the work steps, which hides the waits. Some proposals list many small changes instead of fixing the largest delay. Others promise savings without saying how they were estimated. Alternatives are rarely tested. Risks are often missing, especially for technology changes that need testing with a customer. Watch the difference between business days and calendar days, which can make a process look better or worse than it is. With the process, its rule or target and any timing data you can collect, our writers can help separate work from waiting and design changes aimed at the largest delays.
Get an MT236 Unit 8 example written to your instructions
Describe the process your Unit 8 proposal should improve, with any timings or complaints you have, even rough ones, and attach the prompt and rubric. The first proposal is free, arrives within 24-48h, and separates work from waiting before any change is argued. Without real timings, it uses plausible ones and says where each came from. 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 MT236 papers and BS in Business Administration samples
- MT236 Unit 1: Discussion Board Post
- MT236 Unit 2: Supply Chain Map
- MT236 Unit 3: Supplier Evaluation
- MT236 Unit 4: Demand Forecast Exercise
- MT236 Unit 5: Inventory Analysis
- MT236 Unit 6: Transportation Comparison
- MT236 Unit 7: Distribution Network Memo
- MT236 Unit 9: Seminar Reflection
- MT236 Unit 10: Supply Chain Report
- MT221 Unit 8: Service Metrics Review
- MT220 Unit 8: International Staffing Plan
- MT219 Unit 8: Advertising Evaluation
- MT217 Unit 8: Risk and Return Analysis
MT236 Unit 8 questions, answered
What is the difference between work time and wait time?
Work time is when something is actually being done to the order or product: picking, packing, loading. Wait time is when it sits in a queue or holding area. In many processes waiting is most of the total, which is why removing a queue often shortens a process more than speeding up any single task. The example finds waiting is over two thirds of the total.
Does the proposal need a process map?
A simple one usually helps, and some sections require it. A timeline showing each step with its duration, labeled as work or waiting, serves the same purpose in less space. What instructors look for is that the proposed change attaches to a specific step; a map followed by a general recommendation misses the point of drawing it.
How precise do the savings need to be?
Precise enough to show the change is worth making, with the basis stated. A range is often better than a single figure: here, avoided chargebacks between about $6,000 and $8,100 depending on how many late orders remain. Savings claimed without any basis are the weakness, not savings that are estimated honestly and labeled as estimates.
Where can I find a free MT236 Unit 8 sample paper?
This page holds a full MT236 Unit 8 process improvement proposal for a hot sauce maker's order-to-truck time. It times sixty orders, separates work from waiting, rejects adding a picker, proposes two changes and includes margin notes.
Why would hiring another picker not fix the late shipments?
Picking and packing take only half a day of the 3.2. A second picker might save 0.2 days, while orders would still wait 0.9 days to be keyed and 1.4 days for a carrier appointment.