E021 Leading a Technology Transformation is listed under banner number ITEC 6420 and is worth 3 competency units. It puts you in the technology leader's position: assessing what the organization actually needs, roadmapping the change, and developing a change management strategy for a digital transformation. E021 and ITEC 6420 are one requirement. The recurring lesson is that transformations fail for human reasons far more often than technical ones.
The technical plan is the easy half
Technology transformations rarely fail because the technology could not do the job. They fail because the people who had to change their work were not persuaded, were not equipped, or were not consulted about constraints they understood better than anyone. This course is built around that asymmetry, which is why change management sits beside roadmapping rather than after it.
Needs assessment is the diagnostic that keeps a transformation honest. What is genuinely inadequate about the current state, expressed in what it costs the organization, is a different question from what is old or unfashionable. Systems that are unglamorous and working are frequently replaced at great expense because they were unpleasant to look at, and a needs assessment exists to prevent that.
Resistance deserves a serious and unsentimental treatment. Resistance is usually rational: someone stands to lose autonomy, status, competence they spent years building, or simply the ability to do their job while a half-finished system is in place. Treating resistance as ignorance to be corrected by communication is the most reliable way to entrench it. The better move is to name what each group actually loses and decide what to do about that.
Sequencing and the trough between old and new is the practical heart. Every transformation has a period where the organization runs both systems, does more work than before, and sees none of the benefit. Planning for that period explicitly, resourcing it, and telling people how long it will last is what separates transformations that finish from those that stall at sixty percent and stay there.
Outcomes are logged as Competent or Not Competent, because letter grades and an ordinary grade point average do not exist here, and the 3 competency units measure course size within a six month term sold at one price.
Turning aspects into a transformation plan
If your version of E021 uses a performance assessment, the aspects usually cover assessment, roadmap and change strategy. WGU requires a score of 2 in each aspect for a task to pass and judges each aspect alone, so a detailed roadmap will not carry an unaddressed change management aspect.
Budget before drafting. Take a rubric with seven scored aspects and a target near 2,500 words. Reserve 160 words for the organization and the transformation driver, and 120 for the close, leaving 2,220 across seven aspects, or roughly 317 each. Weight by demand: three aspects requiring analysis and strategy take 420 each, which is 1,260; the four remaining aspects, covering assessment, roadmap detail, stakeholders and measurement, take 240 each, which is 960. Together that is 2,220.
Do the stakeholder work before the roadmap. Who gains, who loses, who holds influence and who has to do the extra work during transition are the facts that decide sequencing, and a roadmap built without them will be reordered by reality within a quarter.
Reserve budget for the sponsorship question. Transformations need a sponsor with authority to resolve conflicts between departments, and naming who that is in the scenario, and what happens when they are unavailable, is a practical detail that graduate marking rewards.
Shape for a transformation strategy
E021 deliverables usually plan and justify an organizational technology change. These proportions fit that document.
| Section | Content | Share |
|---|---|---|
| Driver and current state | Why change now, and what the current state costs in terms someone can weigh. | 13 percent |
| Needs assessment | What is genuinely required, separated from what is merely dated or unfashionable. | 16 percent |
| Target state | What the organization looks like afterwards, described in how work is done rather than in products. | 14 percent |
| Roadmap | Phases, dependencies, the coexistence period and what is deliberately deferred. | 18 percent |
| Stakeholders and resistance | Each group with what it gains, what it loses and how that is addressed. | 18 percent |
| Change management | Sponsorship, communication, capability building and the support during transition. | 15 percent |
| Close | Measures of adoption rather than delivery, and the review point. | 6 percent |
Evidence for a transformation case
Change management models belong to the published literature, cited properly, and the useful ones give you structure for the resistance and capability sections rather than a script to follow. Claims about transformation success rates and failure causes are empirical and belong to research or industry data with a year and a method, because the widely quoted figures in this area are frequently untraceable.
Needs assessment claims should rest on the scenario's own facts wherever possible. Support ticket volumes, manual handoffs, elapsed times and staff turnover in a particular function are the kind of evidence that makes a case for change concrete, and using them stops the assessment from reading as an assertion that the current systems are old.
Be honest about cost. Transformations cost the visible programme budget plus the invisible cost of everyone doing two jobs during coexistence, and a plan that counts only the first will be exceeded. Naming both, even with rough figures, is more credible than a precise number that covers half the reality.
Adoption measures are the evidence that matters afterwards. Delivery measures tell you the project shipped; adoption measures tell you whether anyone uses it and whether the old way has actually stopped. Proposing the second kind, with a target and a date, is what closes the loop the course is teaching.
Follow the citation style named in your task and put the citation where the assertion actually appears.
Competent transformation work and returned work
Competent submissions establish need from evidence, describe a target state in terms of how work changes, sequence with dependencies and a resourced coexistence period, treat resistance as rational, and measure adoption rather than delivery.
Returns follow four shapes. The case for change rests on the current systems being old. Resistance is addressed with communication alone. The roadmap has no coexistence period, implying an instantaneous switch that never happens. Or success is measured by delivery milestones, so nothing tells the organization whether the transformation actually took.
Capability building is the part of change management that gets promised and underfunded. People are asked to work in a new way and given a two hour session three weeks before go-live, after which support is a help desk that does not yet understand the new system either. Saying specifically how competence is built, who provides help during the first weeks, and what happens to the people whose existing expertise is being retired is where a change strategy either becomes real or stays aspirational.
A useful test: pick the group in the scenario that loses most from your plan and write their objection in their own words. If you can answer it, the plan is stronger; if you cannot, you have found the risk that will surface in month four.
Revision and resubmission carry no grade consequence at WGU, so completeness beats polish when you are deciding whether to submit, and treat the first submission as a way of buying exact feedback. If your section also carries an objective assessment, WGU objective assessments are proctored and our boundary is fixed: preparation only, with change model drills, scenario practice and a candid read on your preassessment result. Nobody here sits an assessment, stay out of the room entirely, and we neither ask for nor accept portal credentials.
Roadmap solid, change strategy thin?
Send the E021 rubric and scenario. We build the stakeholder table, plan the coexistence period and set adoption measures, with word targets per aspect.
One closing thought worth including: transformations are judged afterwards on whether the old way actually stopped. Systems that were supposed to be retired and quietly remain in use are the clearest sign that the change was delivered but never adopted, and naming the decommissioning date for each replaced system is how a plan commits to finishing.
Eight mistakes that cost time in E021
- Change justified by age. Old and working is not a case. State what the current state costs.
- Resistance treated as ignorance. Name what each group actually loses, then decide what to do about it.
- No coexistence period. Every transformation has a trough where both systems run. Resource it and say how long.
- Target state described as products. Describe how work is done afterwards, not which platform was purchased.
- Delivery measures only. Adoption is the outcome. Measure whether the old way stopped.
- No named sponsor. Cross-department conflicts need someone with authority to settle them.
- Untraceable failure statistics. The famous figures in this field are widely repeated and rarely sourced. Trace or drop them.
- Roadmap built before stakeholder analysis. Who loses what decides sequencing, so do that work first.
Three questions students ask about E021
Which change management model should I use?
How does E021 differ from E006?
Can I write about a transformation I lived through?
Where E021 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. 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.