C208 Change Management and Innovation is MGMT 6040 in the WGU catalog and carries 3 competency units. It covers change theories, innovation practices, and the leader's role in managing change. The course reads easy and assesses hard, because the models are memorable and the scored work asks for something models cannot supply: a change effort attached to a named organization, with a resistance analysis honest enough to be uncomfortable and a rollout sequence somebody could actually be scheduled into. Every rubric aspect needs a 2 on its own. C208 and MGMT 6040 are one course.
What C208 builds toward
Change management sits at the point where the graduate business plan stops being about analysis and starts being about consequences. Earlier courses ask what an organization is like. This one asks what happens when you try to make it different, and it treats resistance as information rather than as an obstacle. Innovation is bolted to the same frame deliberately: an innovation nobody adopts is indistinguishable from an innovation nobody had, so the course keeps pulling the creative half back toward implementation.
Expect the assessed work to want a real change with a real before and after. The undergraduate version of this territory is C721 Change Management, which covers the same theory at a lower altitude, and the strategic frame that usually surrounds a change effort belongs to C209 Strategic Management. Where those courses ask what should happen, C208 asks who will object and what you will do about it on the day.
The innovation half deserves its own note because students tend to read it as the fun part. It is not treated that way in assessment. Innovation in a management course means a specific new practice, product or process introduced into an organization that had a working alternative, which means every innovation is also a change, with the same losers and the same adoption problem. The useful mental move is to stop asking whether the idea is good and start asking what has to be true about the organization for the idea to survive its first bad month. That question generates the analysis rubric aspects are looking for, and it is why an innovation section written as enthusiasm scores worse than one written as risk assessment.
Turning the aspect list into a build order
WGU does not publish assessment types or task requirements in its catalog; those live in the Course of Study inside your portal. If a performance assessment carries your version of the course, treat the rubric as the specification and build in aspect order, because change documents have a natural narrative pull that will quietly reorganize your sections if you let it. The narrative wants to run problem, solution, happy ending. The rubric usually wants theory, diagnosis, plan, resistance, measurement, and it wants each of those findable on its own.
Then budget by verb depth rather than by enthusiasm. Change writing is unusually prone to spending 600 words describing the problem and 200 on the intervention, which is exactly backwards for scoring purposes.
A worked example. Ten scored aspects, a 2,500 word target. Take 200 off the top for the organizational setup and 100 for the close, leaving 2,200 scored words. Sort the ten: two aspects are theory definition, four are diagnostic, three are design, one is measurement. Theory at 150 each is 300. Diagnosis at 220 each is 880. Design at 290 each is 870. Measurement takes the remaining 150. Add them, 300 plus 880 plus 870 plus 150, and you have 2,200. The diagnostic pressure test: if your design sections come in under your diagnostic sections, you have written a report about a problem rather than a change plan, and the design aspects will score accordingly.
Laying out a change and innovation submission
The layout below keeps the theory honest by forcing it to earn its place, and it puts resistance in the middle rather than at the end where it usually gets three defensive sentences.
| Section | Job | Failure signal |
|---|---|---|
| The change itself | State exactly what will be different, for whom, by when | A goal rather than a change: becoming more agile is not a change anyone can be scheduled into |
| Model selected | One named change model, defined, with the reason it fits this case | Two models described and neither applied |
| Current state diagnosis | Evidence of why the current state persists | Blame language: the culture is resistant, staff are set in their ways |
| Stakeholder and resistance map | Named groups, what each loses, what each gains | Every group listed as either supportive or neutral |
| Innovation component | What is genuinely new here and how adoption is engineered | New technology named with no adoption mechanism |
| Rollout sequence | Phases with dates, owners and a stop condition | A three phase plan where phase two is implementation |
| Measurement and reinforcement | Indicators, review cadence, and what makes the change stick | Success declared at launch rather than at adoption |
Evidence for a change argument
Three sources carry this work. Change and innovation literature supplies the models, cited in APA, and one model applied thoroughly beats three surveyed. Organizational evidence supplies the diagnosis, and the strongest version is operational rather than attitudinal: cycle times, error rates, turnover in the affected group, the number of workarounds people have invented. Attitudinal evidence, meaning what people say about the change, belongs in the resistance section, where it is the actual subject rather than a proxy for facts.
The third source is the one graduate students skip: comparable cases. A change effort of the same type at another organization, cited properly, lets you say what usually goes wrong and design against it. Aspects asking you to justify a rollout choice are much easier to satisfy when the justification points at a documented precedent rather than at your preference. All submitted work runs through WGU's Similarity Checker, so case material must be paraphrased genuinely and attributed, and any framework table you build should be your own construction rather than a reproduced figure.
What separates a passing change plan
WGU posts Competent or Not Competent with no letter grades and no GPA, and each aspect is judged alone at a required score of 2. Change submissions fail in two characteristic places. The first is the resistance section, where writers name resistance and then dissolve it with communication, as though explaining the change harder is a strategy. The second is measurement, where the indicators chosen measure activity rather than adoption: sessions delivered, emails sent, attendance at the launch.
Work that clears on the first pass tends to include at least one uncomfortable admission. Someone loses status. A team's workload rises before it falls. A capable person may leave. Naming that and designing for it is what an evaluator reads as analysis rather than advocacy, and it is the single most reliable way to lift diagnostic and design aspects at once. Returned tasks come back with aspect-level comments and cost nothing but the queue, since WGU allows revision and resubmission without penalty; the revision guide covers how to answer those comments cleanly.
Six mistakes that cost time in this course
- A change with no losers. If nobody is worse off, there is no resistance to analyze and half the rubric has nothing to score.
- The model as decoration. Naming a change model in the introduction and then writing a plan that follows a different logic leaves the theory aspects unmet.
- Communication as the whole intervention. Explaining, town halls and newsletters are one lever among several, and a plan built only from them reads as thin design.
- Innovation without adoption. Introducing a new tool is procurement. The scored part is how usage becomes normal after the enthusiasm fades.
- Phases without stop conditions. A rollout that cannot be paused has no risk management in it, and aspects on implementation risk go unanswered.
- Measuring the launch. Attendance and awareness are launch metrics. Adoption, sustained behavior and the operational number you set out to move are change metrics.
Change plan due, resistance section empty?
Send the rubric and the change you have in mind. The model draft comes back with the diagnosis, resistance map and rollout all built, plus an aspect map.
Three questions C208 students ask
Should I write about a change that succeeded or one that failed?
How many change models should I use?
What can you actually do for me on this course?
Where change work fits in a six month term
Terms at WGU run six months at a flat rate, so the useful question is throughput rather than difficulty. Change courses reward a split schedule: gather the organizational evidence in week one, draft while a second course's reading runs alongside, then submit and start the next course rather than waiting for the evaluation. Because performance assessment work can be revised without penalty, the evaluation return is a task to slot in, not a wall to sit against. That habit is what separates a three course term from a five course term, and the arithmetic is on the tuition page.
Where C208 sits in WGU's programs
The July 2026 catalog places this code in 2 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.