WGU C721: Change Management

Change Management at WGU: What C721 Really Asks of You

C721 Change Management is a 3-competency-unit course in WGU's School of Business, and it shows up most often for students working through the Bachelor of Science in Business Administration – Management. If you have been bracing yourself for another proctored multiple-choice marathon, you can exhale: C721 is assessed by a written performance assessment. There is no proctored exam to schedule, no testing window to survive. Instead, you read an organizational scenario supplied by the course, apply named change management models to it, and write a paper that an evaluator scores against a rubric.

Direct answer: Pass C721 by treating the rubric as your outline, not as an afterthought. Read the scenario closely, answer every lettered prompt in its own clearly labeled section using the specific model the prompt names, and support each claim with a citation from the course materials. Most students who get a "revision requested" missed a sub-part or substituted a model they liked better than the one the rubric asked for.

The course itself is about how organizations actually change — why the pressure to change appears, what has to shift structurally and culturally, and how a leader sequences that shift so it survives contact with real employees. That makes it an unusually practical course. The models are not academic decoration; they are the vocabulary the assessment expects you to use precisely. If you can say why a given company sits at a particular point in its life cycle, and what kind of change is therefore required, you already have the core skill this course is testing.

The Change Frameworks the C721 Task Is Built On

The assessment scenario is deliberately written so that several classic frameworks apply. You will not need all of them in every section, but you need to recognize them on sight and know which one a prompt is fishing for. Topic areas that consistently appear in C721 course materials and task prompts include:

• The systems contingency model — the idea that an organization's internal design has to fit the external environment it operates in, and that misfit is what creates the need for change.
• The organizational life cycle — the stages a company passes through (start-up, growth, maturity, and beyond) and the different pressures each stage produces.
• Traditional versus learning organizations — the structural, cultural, and communication differences between a command-and-control organization and one built to learn continuously.
• Senge's five disciplines — systems thinking, personal mastery, mental models, shared vision, and team learning, and how each one gets built in practice.
• Woolner's five-stage model — a staged view of how an organization progresses toward becoming a learning organization, useful for diagnosing where a company currently sits.
• Balogun and Hope-Hailey's change characterization — classifying change by its end result (realignment versus transformation) and its nature (incremental versus big bang).
• The action research model — a cyclical diagnose, act, evaluate approach to organizational intervention.
• Kotter's eight-step model — sequencing a change effort from establishing urgency through anchoring the change in the culture.

Your Course of Study is the authoritative source for the current learning resources and the exact task wording; WGU updates courseware over time, so work from what your course links to rather than from an old study set. The WGU institutional catalog confirms how C721 sits inside your specific program.

How Hard Is C721, and How Long Should You Budget?

Many students report that C721 is one of the gentler courses in the management sequence — not because the material is shallow, but because a written task with a published rubric removes most of the uncertainty. You can see exactly what is being asked. Several students describe finishing the task inside a single focused week. Others take three or four weeks, usually because they are balancing it against a heavier course or because a first submission came back for revision.

The honest way to plan is this: assume roughly ten to fifteen hours of real work, spread across a week, plus buffer for one round of evaluator feedback. A returned task is not a failure; it is normal, and the feedback is usually specific enough that a revision takes an hour or two. What derails people is submitting on the last day of the term and having no room left to respond.

A Rubric-First Plan for Writing the C721 Task

Here is a sequence that works well for a task-based course like this one:

1. Day one — read the scenario twice and build a fact sheet. Before you open any model, write down what you actually know about the company: its size, its stage, its industry pressures, its culture, its stated problem. Half of the analysis writes itself once these facts are on one page.
2. Day one — turn the rubric into headings. Copy each rubric aspect into your document as its own heading, in the same order and with the same labels. If a prompt has three sub-parts, give it three sub-headings. This single move prevents the most common cause of returned submissions.
3. Day two — learn the models by retrieval, not rereading. After you read the section on, say, Balogun and Hope-Hailey, close the material and write from memory what the two axes are and what each quadrant means. Check yourself. That retrieval attempt is what makes the model stick well enough to apply it under your own steam.
4. Day three — apply, do not summarize. Under each heading, write one sentence naming the model, then spend the rest of the section connecting it to specifics from the scenario. Evaluators are looking for the bridge between concept and company. A paragraph that explains Kotter's eight steps in general terms and never mentions the scenario company earns nothing.
5. Day four — cite as you go, then rest. Add in-text citations to the course materials for every model you name, in the format your task requires. Then step away for a day.
6. Day five — audit against the rubric line by line. Read one rubric line, find the exact sentence in your paper that satisfies it, and highlight it. Anything you cannot highlight is a gap. Fix the gaps and submit.

Spacing the work over several short sessions rather than one long one genuinely helps retention here, and the two-pass audit at the end is worth more than another hour of drafting. If you enjoy this kind of applied writing, you will find similar rhythms in C204 Management Communication and later in the C210 Management and Leadership Capstone.

Where C721 Submissions Usually Get Sent Back

• Answering with the wrong model. If a prompt says to use the systems contingency model or the organizational life cycle model, those are your only two options. Substituting a framework you find more interesting is the single fastest route to a revision request.
• Missing a sub-part. A prompt that asks you to identify something and justify it is two requirements. Papers routinely nail the first and skip the second.
• Describing instead of applying. Textbook summaries of Senge or Kotter without the scenario company's name in the paragraph read as filler to an evaluator.
• Covering only some items in a set. If the prompt asks about Senge's disciplines, address all five. Partial coverage of an enumerated set is an easy, avoidable gap.
• Thin or missing citations. Naming a model without attributing it to a source is treated as an academic integrity issue, not a style preference. Cite the course materials.
• Writing to a page count. There is no length target that earns points. Thoroughness against the rubric is the only measure that matters; a tight paper that hits every aspect beats a long one that wanders.
• Ignoring the provided template. If your course supplies a template, use it. It is organized to match the rubric, and abandoning it makes the evaluator hunt for your answers.

C721 Readiness Checklist

• Can you explain, in your own words, why the scenario company needs to change — using either the systems contingency model or the organizational life cycle?
• Can you name the stage of the life cycle the company occupies and defend that placement with two specific details from the scenario?
• Can you list the practical differences between a traditional organization and a learning organization without looking them up?
• Can you state all five of Senge's disciplines and give one concrete action that would build each one at the scenario company?
• Can you classify the required change by both end result and nature using Balogun and Hope-Hailey, and explain why that quadrant fits?
• Can you walk through Kotter's eight steps and attach a specific, scenario-grounded action to each?
• Have you mapped every rubric line to a highlighted sentence in your draft, with no line left unmatched?
• Is every named model backed by an in-text citation and a matching reference entry?
• Have you left yourself at least a week of term before the deadline in case the task comes back for revision?

C721 FAQ

Is WGU C721 an OA or a PA?

C721 is assessed by a performance assessment — a written task submitted to an evaluator and scored against a published rubric. There is no proctored objective assessment to schedule. Your course page is the final word on the current task format, so confirm there before you plan your term.

How many competency units is C721 worth?

C721 Change Management carries 3 competency units. It typically appears within the School of Business management sequence, most commonly in the Bachelor of Science in Business Administration – Management program.

How long does C721 usually take?

Many students report finishing the task within one to two focused weeks, and some complete it faster. Budget roughly ten to fifteen hours of genuine work plus buffer for one round of evaluator feedback, which is common and easily addressed.

Do I need management experience to do well in C721?

No. Prior experience makes the scenario feel more familiar, but the assessment rewards accurate use of named frameworks, not workplace war stories. A student with no management background who follows the rubric closely will outperform an experienced manager who improvises.

What should I study first if I only have a few days?

Start with the organizational life cycle and the systems contingency model, since those usually anchor the opening section, then work through traditional versus learning organizations and Senge's disciplines. Save Kotter's eight steps for last — it is the most intuitive of the set and the easiest to apply once you understand the company's situation.

Which courses pair well with C721 in the same term?

Because C721 has no proctored exam, it pairs comfortably with a heavier course. Students often run it alongside C717 Business Ethics or D253A Values-Based Leadership, since the leadership and organizational-culture concepts reinforce one another. You can browse the rest of our course guides to plan a term around it.