C721 Change Management appears in the WGU catalog as MGMT 4400, carries 3 competency units, and covers recognizing and implementing change using change theories, methods and tools. Undergraduate change work has one dominant failure mode: writing about change in general when the aspect asked about a change in particular. Each rubric aspect stands alone and needs a 2, so a document full of sound theory can still return. C721 and MGMT 4400 are the same course.
What C721 builds toward
The word recognizing in the catalog description is doing more work than it looks. Before an organization can be changed, someone has to notice that the current arrangement has stopped fitting, and most organizations are much better at implementing than at noticing. The course therefore runs two skills together: diagnosing the need for change from evidence, and then sequencing an intervention that people will actually go along with.
Undergraduate change work sits downstream of C715 Organizational Behavior, which explains why people behave as they do, and upstream of the graduate treatment in C208 Change Management and Innovation. Operations students meet the same material from the process side in D469 Quality, Continuous Improvement, and Lean Six Sigma, where the change is a process improvement and the resistance is identical.
From the rubric to a change document
WGU publishes no assessment-type field per course, and your requirements live in the Course of Study inside the portal. If a performance assessment carries your version, build the outline from the aspect list rather than from the story you want to tell. Change narratives naturally run in a smooth arc, and rubrics rarely do; a document organized as narrative will bury two or three aspects inside paragraphs that were about something else.
A worked example. Say there are eight scored aspects and you are aiming at 2,100 words. Take 150 for the organizational setup and 100 for the close, leaving 1,850. Sort them: two are theory aspects at 175 each, so 350; three are diagnostic at 245 each, so 735; two are implementation design at 300 each, so 600; one is evaluation at 165. Total 350 plus 735 plus 600 plus 165 equals 1,850. The diagnostic that follows is worth running on every draft: divide implementation words by diagnostic words. If the answer is below about 0.7, you have written a case study rather than a change plan, and the design aspects will be the ones that come back.
Structuring a change document
| Section | The question it settles | Evidence it needs |
|---|---|---|
| Trigger | What made change necessary now? | A dated event, a trend, or a measured decline |
| Current state | What exactly is being changed from? | The existing process or arrangement described concretely |
| Future state | What will be different, observably? | A description someone could check against reality later |
| Theory and method | By what model is this change being run? | A named model, cited, with its stages mapped to your plan |
| Stakeholders | Who gains, who loses, who decides? | Named groups with interests, not a generic list of employees |
| Implementation steps | What happens in what order? | Phases with dates, owners, and dependencies |
| Evaluation | How will anyone know it worked? | Indicators tied to the trigger you opened with |
Evidence for a change case
The literature stream is straightforward: a named change model, defined and cited in APA, plus supporting sources for any claim about how people respond to change. One model applied end to end is worth more than three described, and the mapping matters more than the description. If your model has stages, your implementation section should be visibly organized by them, so that an aspect asking whether the theory was applied can be answered by looking at the headings.
The organizational stream needs specificity above all. A change case built on remembered impressions produces sentences like morale was low, which no aspect can score. A change case built on artifacts produces sentences like the process required three approvals and took eleven days on average, which every aspect can use. Where the organization is your employer, anonymize identity and keep the mechanics. Submitted work is scanned through WGU's Similarity Checker, so a change model diagram should be your own rendering with the source attributed.
Competent change work
WGU marks work Competent or Not Competent, keeps no letter grades and no GPA, and requires a 2 in every aspect. Undergraduate change documents return for three reasons above all others. The change is described as a goal rather than as a specific difference in what people do. The resistance section lists categories of resistance from the textbook instead of the actual objections this change will meet. And the evaluation section measures whether the change happened rather than whether it worked.
The strongest correction is to write one paragraph early, before anything else, describing a Tuesday after the change: who does what differently, what they had to stop doing, and what it costs them. That paragraph will not necessarily appear in the final document, but every section written afterward becomes concrete because of it. Returned tasks come back with named aspects, resubmission carries no penalty at WGU, and supported drafts are revised until the evaluation reads Competent.
Five mistakes that stretch this course
- Change described as an outcome. Improving customer satisfaction is a result. Changing the escalation rule so that any complaint older than two days routes to a named supervisor is a change.
- Textbook resistance. Listing fear of the unknown as the resistance in your case leaves the diagnostic aspects unmet. Who objects, and what do they lose?
- A model chosen after the plan was written. It shows, because the plan's steps do not line up with the model's stages.
- No sponsor. Change plans that never identify who has authority to enforce the change are treated by evaluators as incomplete design.
- Evaluation that measures activity. Training sessions delivered is not evidence of change. Behavior sustained ninety days later is.
Change plan with real resistance in it
Send the rubric and the situation. The model draft comes back with the diagnosis, the stakeholder map and the implementation sequence built and aspect-mapped.
Three questions C721 students ask
Can I write about a change that has already happened?
How specific do the implementation dates need to be?
What does help look like on this course?
Sponsorship, authority, and who actually signs off
Undergraduate change plans are often written as though the writer had unlimited authority, which produces a document that no evaluator finds credible and that leaves several aspects thin. Real change has a sponsor, a set of people whose agreement is required, and a longer set whose cooperation is required but whose agreement is not. Separating those three groups sharpens the whole plan.
The sponsor is whoever can allocate the resources and absorb the political cost. Name them by role. The approvers are whoever must formally agree, and each has a specific concern: finance wants the cost profile, legal or compliance wants the risk, the affected department head wants to know what happens to their targets while the change is underway. Writing one sentence per approver, naming the concern and how the plan addresses it, converts a generic stakeholder list into the kind of analysis a stakeholder aspect rewards.
The cooperators are the largest group and the one most often flattened into employees. They do not need to agree; they need the change to be less painful than the alternative for long enough that the new way becomes normal. Design for that specifically: what makes the old path harder, what makes the new path easier, and who notices if someone quietly keeps doing it the old way. Change plans that answer those three questions almost never fail an implementation aspect, because they have described a mechanism rather than an intention.
Three CUs in a six month term
Flat-rate terms reward finishing, so the practical question with a change course is how quickly you can settle on a case. Students who spend two weeks choosing an organization lose more time than they would have lost writing a slightly imperfect case well. Pick in the first few days, gather the artifacts, and let the drafting overlap with another course's exam preparation. The competency-based method page covers why parallel work suits this model, and C722 Project Management is the usual companion in the management concentration.
Where C721 sits in WGU's programs
The July 2026 catalog places this code in 10 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.