Initiating and Managing Change is Walden's WMBA 6882, three semester credits, carried in the WMBA catalog alongside the rest of the MBA electives. Its central writing problem is proof. Everybody in an organization has a story about why a change stalled, all the stories conflict, and a rubric asks you to show which account the record supports rather than which one you found most convincing at the time.
What WMBA 6882 actually grades
The catalog puts the course on situations that call for change, on getting an initiative started and then embedded in the systems that keep it alive, on change that was anticipated and change that arrived without warning, on culture and pushback and ambiguity as forces acting against you, on motivation and clear dialogue as the tools that reduce pushback, and on the difference between reacting to a shifting environment and moving ahead of it.
Graded output tends to follow that: diagnostic analyses of an organization facing a change, plans for launching and sustaining an initiative, readiness or stakeholder assessments, communication strategies built for a specific set of people, arguments about whether a given response was adaptive or planned, and threads with rows of their own.
The rows themselves reward diagnosis over description. Saying that a change failed because of resistance is the least useful sentence available to you, because resistance is the symptom every case displays. What scores is naming what people were protecting, tracing the mechanism by which that protection defeated the initiative, and proposing a move that addresses the mechanism rather than the mood. Add the rows up and you get a letter, and a smooth narrative with no diagnosis inside it lands in the middle of the range.
What counts as evidence in a change paper
Three claims run through almost every assignment in this course, and each one needs a different kind of proof. The first is that change was necessary. The second is that people pushed back. The third is that something did or did not improve. Students usually evidence the first, assert the second, and forget the third.
Necessity is evidenced by a trend, not by an anecdote. Something was moving in the wrong direction, or a competitor did something, or a regulation changed, and there is a number or a document that shows it. Pushback is evidenced by behavior rather than by attitude: workarounds that persisted, adoption that plateaued, meetings that ran long over one agenda item, turnover in a particular team, a policy quietly not enforced. Improvement is evidenced by a baseline and a later measure of the same thing, which means the baseline has to exist before the change, and a great many real initiatives have none, which is itself a finding you can write about.
Two cautions are worth carrying. Self-report from leadership is the weakest evidence in this field, because the people who launched an initiative are the people least able to see it fail. And correlation arrives constantly disguised as success; a number that improved during the same quarter as your change may have improved for a reason that has nothing to do with it. Naming an alternative explanation and then arguing against it is one of the fastest ways to lift an analysis row.
Keep the identifiers out while you gather. Describe roles, functions and sizes rather than named people or a named employer, and leave out anything an agreement covers. The mechanism is what the paper needs, and mechanisms survive anonymisation intact.
How we help in this course
Attach the assignment page, the guide your section is scored against, and the case or organization the week has put in front of you. What returns is a paper with a diagnosis at its center rather than a narrative, where each claim about resistance or result is attached to something a reader can check.
The terms attached are the ones this site runs everywhere. Expect the draft within two days. Expect each rubric row aimed at the highest band. Expect two separate reviews before anything reaches your inbox, one for row coverage and one for citation accuracy and originality. Expect revisions to keep coming, free, until the grade target is met.
Where the week wants a change you have lived through, send a few flat notes on what happened and in what order, with the names removed. Papers built from real sequences beat invented ones, because invented cases have no awkward middle and rubrics reward the awkward middle.
Weekly manuals for this course
No week-level pages exist for WMBA 6882 yet. Because Walden treats the syllabus as classroom property, any week grid published out here would be invention, and this site does not invent course schedules. Each manual appears after a student in the section confirms the deliverable in front of them. Paste your week into chat instead, and drafting begins from your own instructions the same day.
In WMBA 6882 right now?
Send the assignment and its scoring guide. First premium sample is free, back inside two days.
The semester shape of this course
Walden operates a semester calendar for business programs and a separate quarter calendar for nursing, and 6882 belongs to the first. The published Fall 2026 semester runs from September 7 to December 27. Measure that span and it comes to 111 days, a little under sixteen weeks and not quite the round number people quote. Walden posts the dates and leaves the week count to you, so present any total as your own arithmetic rather than as the university's figure.
Times are Central and immovable. A graded item closes at 10:59 p.m. Central, the same instant as 11:59 p.m. Eastern, and that boundary applies wherever you are working from.
The first week also carries an obligation that catches people who plan to start slowly. Walden requires attendance in that opening week, evidenced by a submitted assignment or a posted discussion contribution. It is a compliance matter rather than an academic one, and no amount of later effort undoes a missed one.
How many graded items sit in your section is a question for your syllabus alone. Walden acknowledges that posting requirements vary between courses and even within one, so read the schedule you were issued rather than assuming it matches the last class you took.
How to actually write WMBA 6882: where to begin
The first document to read is the scoring guide, not the case. Its rows are a promise about what will be looked for, so convert each one into a heading in an empty file before you form an opinion about the change you are analyzing. Then read the weights, because they govern proportion. A section that carries a fifth of the marks should occupy about a fifth of the paper, and no more, however interesting it is to write.
Choose the change next, and choose one with edges. A workable subject has a moment when it was announced, a set of people whose work actually altered, a visible obstacle, and an outcome you can describe. Broad transformations spanning three years and eleven departments are unwritable in eight pages, and the usual fix is to isolate a single site, a single team or a single system inside the larger program. If the week hands you a case study, apply the same narrowing to whichever part of it your argument needs.
Now separate diagnosis from treatment, because collapsing the two is the commonest structural fault in this course. Diagnosis asks what was actually happening: what forces pushed toward the change, what held it in place, who lost something, which routines had to be dismantled, and what the organization's culture rewarded before anyone tried to move it. Treatment asks what should be done about that. A paper that jumps to recommendations without a diagnosis reads as advice from somebody who has not looked, and rubrics score it accordingly.
Write a thesis with an edge on it. Try this shape: the rollout did not fail on communication, it failed because the new process removed the informal discretion supervisors relied on to protect their teams, and no formal substitute was ever built. That is arguable, testable, and it tells the reader what the rest of the paper will do. Compare it with an announcement that change management is essential for organizational success, which nobody could disagree with and which therefore earns nothing.
Pick one framework and run it properly. Staged models are useful when the change has a clear sequence you can date. Force field reasoning suits a stalled initiative where driving and restraining forces can be named and weighed. Sensemaking approaches fit ambiguous situations where people never agreed on what was happening. Systems and institutional framing suits a change that was defeated by structures nobody touched. Naming four models in an introduction and applying none of them is a habit graders recognize on sight.
Then put your sources in conversation instead of in a list. The literature on change genuinely disagrees, which is a gift: planned sequential approaches against emergent ones, resistance as an obstacle against resistance as useful information, culture as something leadership can alter against culture as the thing that alters leadership. Set two of those positions against your own evidence, say which one your case supports, and defend the ruling in a sentence. That single paragraph is usually the difference between a solid paper and a strong one.
Finish with recommendations that could actually be carried out. Each one needs an owner, a first step, a timeframe, and a signal that would show it is working, plus a note on what it costs and who will dislike it. Recommendations that ignore their own cost are the ones markers circle, because a plan nobody pays for is not a plan.
Draw the scholarship from the Walden Library rather than an open search. The management databases carry the peer reviewed change literature these rubrics assume, and a librarian will produce something defensible faster than an hour of scrolling will. Then treat APA 7 as mechanics rather than as craft: the Walden title page, heading levels applied where they belong, an author and a year sitting beside each borrowed idea, and a reference list nobody could accuse of drifting from the text. Where you cite an internal document nobody ever published, ask your instructor whether it should stay in the text alone, and pull formatting patterns from the Writing Center rather than inventing them after midnight.
| Section | What goes in it | The failure that costs points |
|---|---|---|
| The change, bounded | What was announced, when, to whom, and exactly whose daily work was supposed to alter. | A whole transformation program described at altitude, so no specific practice is ever examined. |
| Drivers and evidence of need | The trend, the regulation, the competitor move or the number that made standing still untenable. | Necessity asserted in the opening paragraph and never supported by anything a reader could check. |
| Diagnosis | Forces pushing and holding, what people stood to lose, and the routines the change had to dismantle. | Resistance named as the cause, which describes the symptom and explains nothing about it. |
| Framework applied | One named model, explained properly, then run over your evidence including where it fits badly. | Four models listed in the introduction, none of them touched again after page two. |
| Communication and motivation | Who needed to hear what, through which channel, and what each group was being asked to give up. | A recommendation to communicate the vision more effectively, with no audience and no message named. |
| Sustaining and measuring | What embeds the change into systems, plus a baseline and later measure that would show whether it held. | Success declared from the launch event, with nothing measured before the change to compare against. |
Discussion posts that earn their row
Threads here tend to set a scenario or a contested position going and ask where you would stand. Write the opening contribution as a compact diagnosis rather than a reaction: name what is really happening beneath the stated problem, attach the evidence you would look for, bring one source, and say what you would try first. Cite inside the post; a confident paragraph resting on nothing gets read as a personal view by a row that wanted published support.
Walden's policy defines strong participation as timely, substantive and repeated, and it favors a week in which your posts appear on two to four days rather than in one late sitting. Replies score on their own row, so agreement earns nothing at all. Give a classmate something to work with: the group in their scenario who loses something nobody mentioned, the alternative explanation for the result they treated as proof, or the model that would read their case in the opposite direction. Reply counts and closing days are decided inside your own section, so read the week rather than importing a rule.
Handling a case that happened to you
Many students in this course write about a change they lived through, and that is usually the right decision, because you can describe the sequence and the discomfort without inventing either. It comes with two obligations. The first is anonymity: roles rather than names, an industry rather than an employer, and nothing that a confidentiality clause covers. The second is distance. You were a participant, which means you have an account rather than a view from above, and a paper that reads as a grievance loses the analytical row no matter how justified it is.
The practical fix is to write the sequence flatly first, with no interpretation attached, then go looking for the version of events held by the group you found most difficult. Steelman that version in a paragraph before you argue against it. Doing so is disarming, it is better scholarship, and it makes the eventual judgment land harder.
The mistakes that cost points in WMBA 6882
- Naming resistance as the explanation, when resistance is the thing that still needs explaining.
- Recommendations with no owner, no first step and no cost, which read as opinions rather than plans.
- Claiming an initiative succeeded when no measurement existed before it started.
- Choosing a change so large that the paper never gets close to any actual practice.
- Treating the leadership account of events as fact because it was the only account that got written down.
- Ending at launch, so the sections on embedding the change into systems go unwritten and unscored.
- Naming colleagues, or leaving in employer detail the argument never needed.
WMBA 6882 questions students actually ask
Which change model should I use?
Whichever one your evidence can actually feed, and only one of them properly. A staged model suits an initiative with a clear before, middle and after that you can date. A force field analysis suits a stalled change where you can name what pushes and what holds. Sensemaking approaches suit ambiguous situations where nobody agreed on what was happening. Institutional or systems framing suits a change that failed because the surrounding structures never moved. Read your week first, since some assignments name the model, and where the choice is yours, pick the one whose parts you can populate rather than the one you have heard of most often.
How do I write about resistance without blaming my colleagues?
Treat resistance as information rather than as an obstacle, which is both kinder and better scholarship. People push back for reasons, and the reasons are usually rational from where they stand: the change costs them status, or expertise they spent years acquiring, or a routine that protected them from something. Write the reason, not the reaction. A sentence explaining that the new system moved scheduling authority from supervisors to a central team, and that supervisors lost the only lever they had for protecting their crews, explains far more than a paragraph about a difficult culture. Keep names out and describe roles instead.
Can I write about a change that is still in progress?
You can, and unfinished changes often make better papers than tidy ones, but you have to adjust what you claim. Do not argue that it worked, because you cannot know that yet. Argue instead about the design: whether the case for change was made to the people who had to carry it, whether the early moves matched the diagnosis, and what the leading indicators are showing so far. Then state plainly what remains open and what evidence would settle it. Rubrics reward that kind of honesty, and a paper that declares victory on three weeks of data invites the opposite.