| Course | GB560 Designing, Improving, and Implementing Processes |
|---|---|
| Unit | Unit 10 |
| Paper type | Implementation report |
| Length | About 1,150 words, 7 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for GB560 Unit 10
From 3.34 Days to 1.1: A Unit 10 Implementation Report and Handover for a Redesigned Returns Process
[Student Name]
Purdue University Global
GB560: Designing, Improving, and Implementing Processes
Unit 10 Implementation Report
[Instructor Name]
[Date]
The seller, its returns center and every result are composite and illustrative; the methods and sources cited are real.
Summary
The redesigned process, piloted on blenders and food processors in Unit 8, was rolled out to every product family over three weeks and has now run at full volume for eight weeks. Results against the Unit 2 requirements:
Refund timing. Median dock-to-refund time fell from 3.34 days to 1.1, and the 90th percentile from 7.05 days to 2.6. The share of refunds posted within three business days rose to 97 percent, meeting the 95 percent requirement.
Refund accuracy. 99.6 percent correct to the cent, against a 99.5 percent tolerance.
Sellable units restocked within 48 hours. 93 percent of A-grade units, short of the required 95 percent. The cause is the carton wait before unpacking, which the design reduced but did not remove; it is the first open problem below.
Fast-lane losses. 0.45 percent of fast-lane refunds, above the 0.35 percent estimate in Unit 7 but well under the 0.6 percent limit set in Unit 8. At that rate the added loss is about $17,100 a year, still far less than the avoided cost.
Refund-status contacts. Down 61 percent against the baseline, slightly below the 64 percent assumed in Unit 7.
Handling time. Down from 11.4 to 10.1 minutes per return, as the internal label and refund keying disappeared.
A missed requirement reported with its cause and an owner reads as management; the same figure rounded up would read as spin.
Rollout
The rollout ran in three waves, one a week, ordered by how closely each family resembled the pilot.
Wave 1: small kitchen appliances similar to blenders, such as toasters and kettles.
Wave 2: air fryers, slow cookers and multicookers.
Wave 3: espresso machines and other high-value items.
The reversal. Two days into wave three, espresso machines were switched back to the old path for four days. Many espresso returns fall above the $400 inspection threshold, and the inspection lane, staffed for about 4 percent of volume, received more than twice that once espresso machines joined it. Loss prevention fell a day behind. The rollback switch tested in Unit 8 returned the family to the old path within an hour. During the four days, a second loss prevention inspector was scheduled for the inspection lane on peak days, and espresso machines then rejoined the new process without further problems.
Kotter (1996) argues that change efforts often stall when early problems are hidden rather than addressed, and the reversal was reported to staff the day it happened, along with what would change before espresso machines returned.
Control Charts at Full Volume
After twenty working days at full volume, the control limits from Unit 9 were recalculated as planned. The daily median chart now centers at 26.4 hours, with limits of 19.0 and 33.8. The weekly refund correction chart centers at 0.40 percent. Exception-lane aging exceeded the ceiling of five items twice, both on Mondays after weekend volume.
What the Change Cost and Saved
Direct spending on the change was modest: systems work to connect grading to refunds and to match tracking numbers, about $38,000; training time for about 60 staff, about $9,000; and the second loss prevention inspector on peak days, about $21,000 a year. Against them, the Unit 5 failure costs have fallen. Refund-status contacts cost about $33,000 a year now against $84,631 before, chargebacks before refund have nearly disappeared, and returns without a usable authorization have fallen by about four-fifths since the tracking-number match replaced the barcode. Together those three changes save about $140,000 a year, and the shorter handling time, 1.3 minutes on each of about 75,400 returns at $48 an hour, frees about $78,000 of staff time. Allowing for the higher fast-lane loss and the added inspector, the net annual saving is roughly $180,000, and the one-time costs of about $47,000 were recovered within about three months. These figures are estimates from eight weeks of data and should be confirmed at the six-month review.
Open Problems
1. A-grade restocking at 93 percent. Owner: inventory control lead. Due: within six weeks. Cause: returns still wait in bulk cartons before unpacking because the dock and unpacking bench are separate crews. Planned response: a trial of unpacking at the dock for fast-lane returns during the day shift, measured against the 48-hour requirement.
2. Monday exception backlog. Owner: exception lead. Due: within four weeks. Cause: weekend returns arrive together on Monday, and incomplete bundles waiting for shopper replies pile up. Planned response: a second person assigned to the exception lane on Mondays, and an automated message to shoppers on the day an incomplete bundle is found.
What Changed for Staff
Dock staff now scan tracking numbers instead of authorization barcodes. Graders no longer hold finished grades for the 16:00 export. Customer service agents no longer key refunds each morning, and the time saved has gone to answering the remaining contacts faster. One named exception lead now owns the exception lane, a role that did not exist before. Training records for each change are in the handover appendix.
Handover
The handover is written for the returns center supervisor, who will run the process after the project team leaves, and is meant to let the supervisor operate, measure and correct it without calling anyone from the project.
Appendix A: the rewritten procedure, with the five lanes and the exception branches, replacing the nine-step document.
Appendix B: training records for dock, bench, grading, customer service and the exception lead.
Appendix C: control charts and instructions, including how to update the charts, the response table from Unit 9 and when to recalculate limits.
Appendix D: escalation contacts for systems, loss prevention and customer service.
Appendix E: the open problem log, with owners and dates.
Juran and Godfrey (1999) describe sustainment as the stage where improvement efforts most often fail, because the project team leaves before the people running the process can maintain the gains. The handover is designed against that risk: the supervisor holds the charts, the procedure and the open problems, and the monthly review with the operations director continues.
Lessons for the Next Redesign
Three lessons carry forward. Pilot the most unusual family, not only the most typical one, since the espresso reversal came from a volume pattern the pilot never saw. Measure staff time as well as elapsed time, since the exception count in Unit 6 changed the design more than any timing result. And name owners for open problems before the project ends, so nothing waits for a team that has disbanded. Wheeler and Chambers (1992) note that a process under control can still be improved, and the two open problems are where improvement continues.
References
Juran, J. M., & Godfrey, A. B. (Eds.). (1999). Juran's quality handbook (5th ed.). McGraw-Hill.
Kotter, J. P. (1996). Leading change. Harvard Business School Press.
Wheeler, D. J., & Chambers, D. S. (1992). Understanding statistical process control (2nd ed.). SPC Press.
What the GB560 Unit 10 assignment asks for
GB560 Unit 10 asks you to report on implementing your redesigned process and hand it over. Lead with a one-page summary of results against each requirement, including any you missed and why. Describe how the rollout was sequenced and any reversal, with what was learned. Report control chart results at full volume. Estimate costs and savings, labeled as estimates. List open problems, each with an owner, a cause, a response and a date. Explain what changed for staff. Write the handover for the person who will run the process, listing the procedure, training records, chart instructions and escalation contacts. Close with lessons for the next redesign. Expect about twelve pages with appendices, citing sources in APA 7.
How this GB560 Unit 10 example is built
The summary reports each requirement, including restocking at 93 percent and the carton wait behind it, while the highlighted line argues for reporting shortfalls plainly. The rollout runs in three waves, and the espresso reversal is explained by an inspection lane receiving twice its planned volume, resolved with a second inspector, with Kotter on surfacing early problems. Recalculated limits center at 26.4 hours, with Monday exception backlogs noted. A costs section estimates a net saving near $180,000 a year. Two open problems carry owners and dates. Staff changes are listed, and the handover lists five appendices for the supervisor, with Juran and Godfrey on sustainment and Wheeler and Chambers on continued improvement.
GB560 Unit 10 rubric: what earns full points
A strong GB560 implementation report is graded on whether results are reported honestly against the original requirements and whether the person inheriting the process could run it. A summary covering every requirement earns points. Reporting a missed requirement with its cause shows integrity. Describing rollout sequencing and a reversal shows candor about what happened. Recalculated control limits show the plan was followed. Labeled cost estimates show financial care. Open problems with owners and dates show accountability. A handover written for the supervisor shows attention to sustainment. Lessons for the next project show reflection. Juran and Godfrey, Kotter, and Wheeler and Chambers are cited in APA 7.
Common GB560 Unit 10 mistakes, and how to avoid them
Many GB560 Unit 10 reports present results that met targets and quietly omit those that did not, which graders tend to notice. Others describe the rollout as smooth when a reversal or delay taught the most useful lesson. A frequent gap is sustainment: a report that ends with results, without a handover, leaves the supervisor unable to maintain the gains once the project team leaves. Some writers list open problems without owners. Summarize results against every requirement, explain shortfalls, describe the rollout honestly, report charts, estimate costs, assign open problems, write the handover for its actual reader and record lessons. A planned implementation is acceptable if labeled clearly.
Get a GB560 Unit 10 example written to your instructions
Send what you have on your process's implementation, whether results, rollout notes or open issues, together with the Unit 10 prompt and rubric. The report measures results against your requirements, tells the rollout honestly, assigns open problems and ends with a handover section the new process owner can work from. A first custom sample is free and generally takes 24-48h. 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 GB560 papers and MBA samples
- GB560 Unit 1: Discussion Board Post
- GB560 Unit 2: Process Requirements Memo
- GB560 Unit 3: Current State Map
- GB560 Unit 4: Cycle Time Analysis
- GB560 Unit 5: Failure Mode Review
- GB560 Unit 6: Seminar Reflection
- GB560 Unit 7: Process Design Proposal
- GB560 Unit 8: Pilot Plan
- GB560 Unit 9: Control Plan
- GB550 Unit 10: Financing Recommendation
- GB546 Unit 10: Staffing Business Case
- GB545 Unit 10: Rewards Business Case
- GB542 Unit 10: Talent Strategy Report
GB560 Unit 10 questions, answered
What if my implementation has not actually happened?
Many students write this report for a process they could not change themselves, and most sections accept a planned or simulated implementation clearly labeled as such. The sample describes a completed rollout with composite figures. A projected version would present expected results with their assumptions and describe the handover as planned rather than done.
Should the report admit that a requirement was missed?
Yes. A missed requirement reported with its cause and an owner reads as competent management; one hidden or rounded away reads as spin, and graders tend to notice. The sample's stocking result, 93 percent against 95, appears on the summary page with its explanation. Honest reporting of shortfalls is usually part of what the rubric rewards.
Who is the handover section written for?
The person who will run the process after the project team leaves, usually a supervisor or manager. It should let that person operate, measure and correct the process without calling anyone from the project. The sample gathers the procedure, training records, chart instructions and escalation contacts in one appendix, which is what most rubrics mean by sustainment.
Where can I find a free GB560 Unit 10 sample paper?
This page carries a full GB560 Unit 10 implementation report for a redesigned returns process, with results against requirements, a rollout reversal, open problems, a handover and APA 7 references.
Why were espresso machines switched back for four days?
Many fall above the $400 inspection threshold, and the inspection lane received more than twice its planned volume. A second loss prevention inspector on peak days fixed it, and the family rejoined the new process.