E024 Product Launch carries the banner number ITIM 6620 and is worth 3 competency units. You play a product manager overseeing the launch of a technical product: developing the launch plan, solving an urgent threat that appears against it, and evaluating the marketing plan attached to it. E024 and ITIM 6620 are one requirement. It closes the product sequence that began with strategy and passed through design, and the skill it tests is decision making under time pressure with incomplete information.
A launch is a sequence with dependencies and a date
The mental shift this course requires is from designing a thing to shipping it. A launch plan is not a description of a product, it is an ordered set of activities with owners, dependencies, dates and a definition of readiness. Students who write beautifully about the product and vaguely about the sequence lose exactly the aspects the course cares about, because the sequence is the deliverable.
Readiness criteria deserve particular attention. Someone has to be able to say, on the morning of the launch date, whether the product goes out. That decision needs criteria agreed in advance: what must be true technically, operationally, commercially and legally. Plans that lack readiness criteria are plans with no way to stop, and stopping is one of the decisions the course wants you to be capable of making.
The urgent threat is the part students underprepare. A late defect, a competitor announcement, a supply problem, a security disclosure, a key person unavailable: whatever form it takes in your scenario, the response is judged as a decision, not as a description of concern. That means naming your options, choosing one, saying what it costs, saying who you tell and when, and saying what you will monitor to know whether it worked.
Evaluating the marketing plan means assessing it, not admiring it. Does the message match the value the strategy claimed? Do the channels reach the users the research identified? Do the timing and the technical readiness line up? An evaluation that finds nothing wrong is almost always an evaluation that did not test the plan against the product.
Results at WGU read Competent or Not Competent, letter grades and an ordinary grade point average do not exist, and these 3 competency units sit within a flat rate six month term.
Turning scored aspects into a launch document plan
If your version of E024 is assessed by a performance assessment, the aspects your evaluator scores are the sections, and a launch scenario tends to generate a lot of them because it covers planning, response and evaluation in one deliverable. WGU requires a score of 2 in each aspect to pass a task and scores each one alone, so an excellent plan does not carry a weak threat response.
Budget before writing. Work from a rubric of eight scored aspects against a target near 2,400 words. Reserve 200 words to set the product, the market and the launch date, and 120 for the close, leaving 2,080 words to distribute. Two aspects carry the most weight, typically the launch plan itself and the response to the threat, and they take 380 words each, which is 760, because each needs options, a decision and a consequence. The six remaining aspects, covering readiness, stakeholders, communications, metrics, marketing evaluation and risk, take 220 each for 1,320. The two totals add to 2,080 exactly.
Use a table for anything with a date, an owner or a dependency, and prose for anything requiring judgment. A launch plan written entirely in paragraphs hides the sequence, and a launch plan written entirely in tables hides the reasoning. The aspects usually want both, in different places.
Keep budget in reserve for the decision under pressure. The threat aspect is where graduate level judgment shows, and it is the section students shorten when the word count gets tight. Cut background instead.
Shape for a launch plan with an incident response
E024 deliverables usually combine a plan, a response and an evaluation in one document. These proportions hold all three.
| Section | What belongs there | Share |
|---|---|---|
| Product and market | What ships, to whom, and what the launch is meant to achieve. | 8 percent |
| Launch sequence | Activities, owners, dates and dependencies, in order, with the critical path visible. | 20 percent |
| Readiness criteria | What must be true to go, by function, and who makes the call. | 11 percent |
| Stakeholders and communications | Who hears what, when, through which channel, before and after launch. | 12 percent |
| Threat response | The problem, the options, the decision, the cost of the decision, and who is told. | 20 percent |
| Marketing evaluation | Message, channel, timing and audience tested against the product and the research. | 16 percent |
| Metrics and monitoring | What is watched in the first days and what would trigger a rollback. | 9 percent |
| Close | The largest remaining risk and the contingency that covers it. | 4 percent |
Evidence and sourcing under a scenario
Scenario driven courses invite a specific error: treating the scenario as a prompt to be embellished rather than as the evidence base. Facts about the situation come from the scenario and nowhere else. If the scenario does not say how many support staff are available, you cannot know, and the professional move is to state the assumption you are making and note how a different figure would change your plan.
Claims about how launches, channels or communications generally work come from published sources: product management and marketing literature, professional bodies, industry research. This is where citations belong, and it is where most students under cite because the material feels like common sense. If your response to the threat rests on a principle, name the principle and cite it.
Where you reference the technical product, keep the detail proportionate. A launch document mentions technical readiness, dependencies and defect thresholds. It does not re specify the system, and words spent doing so come out of aspects that needed them.
Use the citation style your task names, cite at the point of the claim, and keep the reference list aligned with the text. In a document mixing tables and prose it is easy to lose a citation inside a table cell, so check that any sourced figure in a table has its citation visible.
What earns Competent, and what comes back
Competent submissions read like a plan somebody could execute. Activities have owners and dates. Dependencies are explicit. Readiness has criteria rather than an intention. The threat response chooses, and admits what the choice costs. The marketing evaluation finds at least one real weakness and says how to fix it.
Returns cluster in five places. The plan is a list of activities with no sequence or ownership. Readiness is asserted rather than defined. The threat section describes the threat and its implications without deciding anything. The marketing evaluation praises the plan. Or communications are missing entirely, which in a launch document is the omission an experienced evaluator notices first.
A worthwhile final pass: hand your plan to someone who has not read the scenario and ask them who does the first three activities and what would stop the launch. If they cannot answer from the document, the aspects on ownership and readiness are not yet answered either.
Since performance assessment work at WGU can go back for revision with no grade penalty, submit when every aspect has a genuine answer instead of waiting to feel finished. If your section carries an objective assessment as well, that exam is proctored and our boundary is absolute: we prepare you beforehand with concept work, scenario drills and a candid read of your preassessment. We will not sit an assessment for you, we contribute nothing while one is running, and we neither request nor hold portal credentials.
Plan reads like a description?
Send the E024 rubric and your scenario. We rebuild it as a sequence with owners, readiness criteria and a threat response that actually decides.
Six mistakes that cost time in E024
- A plan with no owners. Every activity needs a role attached. Unowned work is the definition of a plan that will not run.
- Readiness without criteria. Say what must be true to go live, by function, and who has the authority to stop it.
- Describing the threat instead of deciding. Options, choice, cost, communication, monitoring. All five, in that order.
- Flattering the marketing plan. Test message, channel, timing and audience against the product and the research, and report what fails.
- No communications plan. Customers, support, sales and executives each need something different, before and after the date.
- Inventing scenario facts. If the scenario is silent, state your assumption and say how a different figure would change the plan.
Three questions students ask about E024
How detailed should the launch timeline be?
What if I have never worked on a product launch?
Is E024 the same course as ITIM 6620?
Where E024 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.