| Course | WMBA 6882 Initiating and Managing Change |
|---|---|
| Week | Week 1 |
| Paper type | Discussion post |
| Length | About 530 words, 3 pages |
| Format | Discussion post, APA 7 citations |
| School | Walden University |
| Program | Master of Business Administration (MBA) |
| Updated | October 2026 |
Free sample paper for WMBA 6882 Week 1
Week 1 Discussion: A Change Initiative That Quietly Ended
Announced in January, Mandatory From March 1, Gone by June: How an Engineering Firm's Timesheet App Lost to the Friday Paper Sheet, Dated by the Week the Reminder Emails Stopped
In January 2024, the civil engineering firm where I then worked, a composite practice of about 300 staff in Denver, announced a mobile timesheet app that would be mandatory from March 1 and would replace the paper timesheet every engineer handed in on Friday afternoons.
The paper process was slow but familiar. Each Friday, engineers wrote hours by project number on a printed sheet, their project manager initialed it on Monday, and two people in accounting keyed about 280 sheets into the billing system by Wednesday. Invoices to clients went out on the tenth of the following month, partly because of that delay. The app was supposed to put hours into billing the same day, so invoices could go out on the third.
For six weeks the app was used. Accounting reported in early April that 71 percent of hours had come through it. Then the signals faded. The weekly reminder email from the operations director, which named project teams with missing app entries, ran every Monday until May 17 and never again. The compliance report circulated at the April and May managers' meetings did not appear on the June agenda. By the end of June, accounting was keying paper sheets again, and the app license lapsed at renewal in December. I date the abandonment to the last week of May, when the reminder stopped, because that is when following the rule no longer mattered to anyone who could enforce it.
What replaced the app was the old method, not a decision. Project managers had never been asked to stop signing paper, so many kept accepting it, and engineers who disliked typing hours on a phone simply went back. Klein and Sorra (1996) argued that implementation succeeds when users experience a climate in which using the innovation is expected, supported and rewarded, and when it fits their values. Here, the expectation lasted exactly as long as the reminder emails. Repenning and Sterman (2001) describe how improvement efforts get dropped when workload pressure rises; May was the start of the firm's construction season.
When did the initiative you remember stop being enforced, and what signal told you?
Reply to Marcus
Marcus, your hospital's hand-off tool sounds like it faded the same way mine did, but you describe the ending as "gradually." Can you find the week? If the unit huddle checklist stopped including the hand-off item, the date of the first huddle sheet without it would be a good marker. Buchanan et al. (2005), reviewing research on sustaining change, noted that changes often decay after initial success, which makes finding the point of decay more useful than describing the decline.
Reply to Priya
Priya, you said the new expense policy failed because "people resisted." Your own post says the finance team kept approving the old form. That sounds less like resistance than an old path left open. If the old form had been removed from the intranet on the policy's start date, would anyone have needed to resist?
References
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
Klein, K. J., & Sorra, J. S. (1996). The challenge of innovation implementation. Academy of Management Review, 21(4), 1055-1080. https://doi.org/10.2307/259164
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 1 instructions ask for
The first discussion of the course asks for one change initiative you watched fade, told as a dated sequence rather than a reflection on change in general. Open by naming the initiative, the month it was announced and the month it became mandatory, so readers have the span before any argument. Describe the old way of working concretely: the form, the signature, the time it took. Then follow the initiative forward and find the point at which it stopped mattering, using a signal that faded, such as reminders, a report or an agenda item. Close by connecting the decline to one idea from the week's reading and asking classmates a question. Two replies are due later, and the strongest ones ask a classmate to date their own initiative's end or to name the path the old method used to return.
Inside the WMBA 6882 Week 1 example
The sample's first sentence carries the app, the firm and both dates. The next paragraph sets out the paper process: sheets on Friday, initials on Monday, two accounting clerks keying about 280 sheets by Wednesday, invoices on the tenth. Adoption is reported as a figure, 71 percent of hours through the app by early April. The decline is dated by two signals: the operations director's Monday reminder, which last ran on May 17, and a compliance report that vanished from the June agenda. A paragraph explains that managers were never told to stop signing paper, citing Klein and Sorra on implementation climate and Repenning and Sterman on improvement work dropped under pressure. The reply to Marcus asks for the date of the first huddle sheet without the hand-off item; the reply to Priya points to an old expense form still on the intranet.
WMBA 6882 Week 1 rubric: what earns full marks
Precision earns the marks in this opening discussion. A post that names an initiative, two dates and a fading signal gives the grader something to check, while a post about resistance in general offers nothing. The before-state matters because the replacement can only be judged against concrete work, so posts that describe culture instead of tasks lose ground. Finding a month for the abandonment, even an informal one, shows the analytic move the course builds on. The reading should explain why the decline happened, such as an expectation that lapsed, rather than define change. Replies earn their share by asking for something precise, such as a date or an open path, rather than by agreeing. A short, dated post usually outscores a long, general one here.
WMBA 6882 Week 1 help: mistakes that cost marks
Choose an initiative you saw from close enough to know the dates. Before writing, list the announcement, the mandatory date and any signal that later faded: emails, reports, meeting items, audits. Pick the last appearance of that signal as your end date and say why. Describe the old process in two or three sentences of concrete detail. Common problems include opening with a definition of change, blaming staff attitudes without evidence and never dating the end. Another is describing a failed launch rather than a fade, which is a different case. In replies, ask the classmate for one missing fact. If you need a model post about an initiative from your own workplace, share the dates you know and what replaced it, and a sample can be prepared.
Get a WMBA 6882 Week 1 example written to your instructions
Reply counts and citation minimums move around in Week 1, so the discussion instructions plus whatever rubric the classroom shows are worth sending; a finished post and the replies beside it return inside 24 to 48 hours, free the first time. Naming the initiative keeps the draft anchored to a real calendar instead of an imagined one.
More WMBA 6882 papers and MBA samples
- 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 10: Change Sustainment Plan
- WMBA 6882 Week 11: Change Proposal With Rebuttal
- WMBA 6695 Week 1: Misfired Message Discussion Post
- WMBA 6633 Week 1: Mentor Influence Discussion Post
- WMBA 6627 Week 1: Withheld Support Discussion Post
- WMBA 6623 Week 1: Named Risk Discussion Post
WMBA 6882 Week 1 questions, answered
Where can I find a free WMBA 6882 Week 1 sample paper?
The whole timesheet-app post and its two replies are reproduced here, notes included, and anyone can read them without paying.
What initiative does the WMBA 6882 Week 1 example trace?
A mobile timesheet app at a composite engineering firm, announced in January 2024, mandatory from March 1 and abandoned by late May.
How is the date of abandonment found?
By the last appearance of a signal: the weekly reminder email stopped after May 17 and the compliance report left the managers' agenda.
Why did the old paper process return?
Project managers were never told to stop signing paper sheets, so the old path stayed open when enforcement faded.
What do the replies ask?
One asks a classmate to date when a hospital tool faded, and the other suggests that an old expense form, not resistance, kept a policy from taking hold.