| Course | WMBA 6882 Initiating and Managing Change |
|---|---|
| Week | Week 10 |
| Paper type | Sustainment plan |
| Length | About 1,100 words, 7 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Business Administration (MBA) |
| Updated | October 2026 |
Free sample paper for WMBA 6882 Week 10
Keeping Computer-Generated Ordering Alive After the Project Team Disbands: A Sustainment Calendar for Prairie Line From March 2029 to February 2030, Six Old Paths Closed on Named Dates and Two Measures With a Slip Trigger
Student Name
Walden University
WMBA 6882: Initiating and Managing Change
Instructor Name
Month Day, Year
Keeping Computer-Generated Ordering Alive After the Project Team Disbands: A Sustainment Calendar for Prairie Line From March 2029 to February 2030, Six Old Paths Closed on Named Dates and Two Measures With a Slip Trigger
Handover Date and Owner
The team that ran the ordering project at Prairie Line Farm & Home, this course's composite rural retailer, holds its final steering meeting on February 27, 2029, and disbands the next day. From February 28, the ordering routine belongs to two standing positions: the inventory analytics manager, who owns the system settings and the chain-wide measures, and each store manager, who owns whether department leads review and release orders on time in that store. The director of store operations, who led the project, steps back to a quarterly review.
The project sponsor, the vice president of merchandising, remains in her role but will not attend weekly meetings after February. A review by Buchanan et al. (2005) observed that gains tend to erode once early attention and resources move elsewhere, and that sustaining them depends on many interacting factors rather than any single one. The handover is the moment attention will be withdrawn, so the plan starts there.
Old Paths Still Open, and the Dates They Close
In February 2029, six ways of ordering the old way still exist. Each will be used the first time something goes wrong unless it is closed.
Table 1
Legacy Paths and Their Closing Dates
| Legacy path | Still possible because | Closed by | Owner | |
|---|---|---|---|
| Paper order pads in store back rooms | Pads were never collected | March 9, 2029, pads collected and recycled | Store managers | |
| Manual store-order screen in the purchasing system | Buyers can key orders when a lead calls | March 30, 2029, store users lose access; buyers keep it for emergencies with a logged reason | Information technology manager | |
| "Order walk" line on the lead weekly task list | Old task template still in use | March 2, 2029, replaced by "review and release system orders" | Director of store operations | |
| Weekly order-walk completion report | Report still runs automatically | March 30, 2029, report retired | Inventory analytics manager | |
| Phone orders to vendor reps for lines the system now orders | Some reps still take calls from leads | April 13, 2029, letters to eleven vendors | Merchandising manager | |
| Counter rush-order form | Needed for genuine emergencies | Kept, but every use goes to the analyst and is reviewed monthly | Inventory analytics manager | |
Prairie Line Farm & Home and its suppliers are composite.
The last row is deliberately not closed. A farm store will always face a customer who needs fifty T-posts tomorrow, and banning the rush form would push that need into one of the closed paths. Instead, the plan watches it: a store whose rush orders rise above eight a month gets a visit from the analyst, because frequent rush orders usually mean the system's minimum quantities are wrong for that store.
Two Measures, One Owner, One Trigger
The plan watches two measures, both reported weekly by the inventory analytics manager to every store manager and quarterly to the director of store operations.
The first measures whether the routine is happening: the share of system orders each store's leads review and release on schedule. It comes from the ordering system's release log. The pilot and both waves ran at 96 to 98 percent in their first full cycles.
The second measures whether the routine is producing anything: the share of the 500 best-selling hardgoods items on the shelf, measured chain-wide and store by store. It comes from the daily on-hand file. The pilot stores rose from 93.1 to 96.4 percent.
The trigger that says the change has slipped is written in advance. If a store releases fewer than 90 percent of orders on schedule for two weeks in a row, or its in-stock rate falls below its pre-conversion level for three weeks, the analyst visits within five working days and the store manager reports what changed. If the chain-wide in-stock rate falls below 95 percent for three weeks, the director of store operations reconvenes a small review group, including two department leads, within two weeks. Bateman (2005), analyzing forty process improvement activities, identified enablers associated with improvements that lasted and stressed that they were things the people running the work area could act on themselves. Giving store managers and the analyst the measures, the trigger and the response puts sustainment in the hands of people who stay after the project team leaves.
The Calendar
Table 2
Sustainment Calendar, March 2029 to February 2030
| Month | What happens | Risk it addresses | |
|---|---|---|
| March | Four legacy paths closed; first monthly rush-order review | Leads falling back to paper when busy | |
| April | First spring season on the system; weekly measures reviewed in every district call | Spring demand outrunning the forecast | |
| May | Analyst visits every store with in-stock below its baseline | Stores where settings no longer fit | |
| July | Hours commitment to leads expires; any schedule change reviewed by the director first | Leads reading the change as a staffing cut | |
| August | Quarterly review; demand events for fall and hunting season entered | Seasonal items missed | |
| October | Training module for leads hired since the project ended | New leads who never learned the order walk or the review | |
| December | Annual settings review with two leads per district | Settings drifting from how stores sell | |
| February 2030 | Plan reviewed; measures and trigger kept, changed or retired | A plan that outlives its usefulness | |
Months refer to 2029 unless shown otherwise.
Two months carry the most risk. April is the first spring on the new method, when demand for fencing, seed starting and lawn equipment jumps and the system's forecasts will be tested hardest. July is when the written promise not to cut leads' hours because of the change expires. If any store reduces lead hours that month, leads will reasonably conclude the change was about cutting hours all along, and the routine will lose the people it depends on. Repenning and Sterman (2001) described how organizations under pressure cut the time that keeps an improvement working, and then blame the improvement when results fall. The July review is there to catch that before it happens.
What Ends the Plan
The sustainment plan itself ends in February 2030. At that point, the review screen will be part of the lead job description, in-stock rate will have been on the scorecard for more than a year, and every lead hired after the project will have learned only the new method. If the measures have stayed above their triggers for twelve months, the weekly report becomes monthly and the plan is closed.
References
Bateman, N. (2005). Sustainability: The elusive element of process improvement. International Journal of Operations & Production Management, 25(3), 261-276. https://doi.org/10.1108/01443570510581862
Buchanan, D., Fitzgerald, L., Ketley, D., Gollop, R., Jones, J. L., Lamont, S. S., Neath, A., & Whitby, E. (2005). No going back: A review of the literature on sustaining organizational change. International Journal of Management Reviews, 7(3), 189-205. https://doi.org/10.1111/j.1468-2370.2005.00111.x
Repenning, N. P., & Sterman, J. D. (2001). Nobody ever gets credit for fixing problems that never happened: Creating and sustaining process improvement. California Management Review, 43(4), 64-88. https://doi.org/10.2307/41166101
What the WMBA 6882 Week 10 instructions ask for
Week 10 asks for a plan covering the months after a change project closes. Fix the handover date and name who owns the new routine afterward, by role, choosing standing positions rather than the project team. List every old way of doing the work that is still possible, with the date each will close and who closes it; any path left open will be used the first week something goes wrong. Choose two measures, one showing the routine is happening and one showing it produces results, with a source and a reporting interval for each, and write a trigger that says the change has slipped and what happens next. Lay the plan out as a forward calendar by month. Three to five pages is common, supported by research on sustaining change.
How this WMBA 6882 Week 10 example is built
The plan opens on February 27, 2029, assigning the routine to the inventory analytics manager and store managers, and cites Buchanan and colleagues on decay after attention is withdrawn. A six-row table lists legacy paths: paper pads, the manual store-order screen, the old task line, the completion report, vendor phone orders and the rush form, each with a closing date and owner. A paragraph explains keeping the rush form and reviewing stores with more than eight rush orders a month. The measures section defines release-on-schedule and in-stock rate, with triggers at two and three weeks and named responses, citing Bateman. An eight-row calendar runs from March 2029 to February 2030, and the text explains the April and July risks, citing Repenning and Sterman. A final section states when the plan itself ends.
WMBA 6882 Week 10 rubric: what earns full marks
Sustainment plans are graded on whether the routine could survive without anyone protecting it. Ownership left with a project team that disbands is a common and costly flaw; standing positions with authority score well. The legacy path table is central, and each entry needs a date and a person, since unnamed closing actions rarely happen. Graders reward restraint in monitoring: two clear measures with sources and intervals outperform a long dashboard. A written trigger with a defined response shows the plan can act, not only observe. The calendar should name the months of highest risk and explain why. Research should support specific choices, and a stated end to the plan itself shows the writer understands that sustainment is a phase, not a permanent project.
WMBA 6882 Week 10 help from the desk
Start with the date the project closes and the role that owns the routine afterward. Walk through the old process and list every way someone could still use it: forms, screens, reports, phone calls, habits. Give each a closing date and an owner, or explain why it stays and how you will watch it. Pick one measure of activity and one of results, name where each comes from and decide what level would trigger action. Lay out the year by month and mark the risky ones. Weak plans list principles, leave ownership with the change team, track too many measures or never close the old paths. Others have triggers with no response attached. If you want a model sustainment plan for a change you have implemented, share the handover date and the old paths still open.
Get a WMBA 6882 Week 10 example written to your instructions
Send the Week 10 instructions with the rubric, and note how far beyond go-live the section expects coverage, since that ranges from six months to two years; decommission dates and drift triggers arrive in a finished plan inside 24-48h, the first at no charge. Name the change being sustained and the draft starts where that project stopped.
More WMBA 6882 papers and MBA samples
- WMBA 6882 Week 1: Abandoned Initiative Post
- WMBA 6882 Week 2: Failed Change Case Reconstruction
- WMBA 6882 Week 3: Change Readiness Assessment Memo
- WMBA 6882 Week 4: Change Resistance Register
- WMBA 6882 Week 5: Contrarian Peer Replies
- WMBA 6882 Week 6: Kotter Model Application
- WMBA 6882 Week 7: Timed Change Announcement Sequence
- WMBA 6882 Week 8: Change Implementation Plan
- WMBA 6882 Week 9: District Manager Change Brief
- WMBA 6882 Week 11: Change Proposal With Rebuttal
- WMBA 6695 Week 10: Failed Notice Case Analysis
- WMBA 6633 Week 10: Mentoring Reflective Memo
- WMBA 6627 Week 10: Stakeholder Briefing Note
- WMBA 6623 Week 10: Risk Escalation Protocol
WMBA 6882 Week 10 questions, answered
Where can I find a free WMBA 6882 Week 10 sample paper?
You can read the complete sustainment plan, legacy path table and calendar on this page for free.
When does the WMBA 6882 Week 10 plan begin?
On February 27, 2029, when the project team holds its final steering meeting and disbands.
Who owns the routine after handover?
The inventory analytics manager for settings and measures, and each store manager for on-time review in that store.
Why is the counter rush form kept?
Genuine emergencies will always occur, so the form stays but every use is reviewed and frequent use triggers an analyst visit.
What triggers action?
A store releasing under 90 percent of orders on time for two weeks or falling below its in-stock baseline for three, or a chain-wide in-stock rate under 95 percent for three weeks.