E022 is a three-unit graduate course in WGU's Master of Science, Information Technology, Product Management. WGU lists no prerequisites, and it is the first of three product courses, followed by Product Design and Product Launch.
The guidebook says the course prepares students to plan a new product's development. You strategise the needs, requirements, costs and metrics that determine a successful design, drawing on new product development, product management, user research, planning, business requirements and team leadership.
The difficulty is turning vague ideas into clear requirements that connect a business case with real customer needs, and then showing how you would know the product is succeeding.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course | E022, Product Strategy |
| Competency units | 3 |
| Level | Graduate |
| Program | MS Information Technology, Product Management |
| Prerequisites | None listed |
What E022 Covers
| Competency (WGU wording, summarized) | What it asks of you |
|---|---|
| Create a product requirements document addressing the business case and customer needs | Define what the product must do and why |
| Develop a product strategy that anticipates and mitigates problems or changes | Plan for risks and shifts in the market or requirements |
| Develop metrics to determine the effectiveness of the product strategy | Decide how success will be measured |
Key Concepts Explained
The Product Requirements Document
A requirements document states the problem, the users, the goals and the features or capabilities needed, usually ranked by importance. Each requirement should trace to a customer need or business objective.
Illustration: A company wants a scheduling app for home-care workers. Research shows workers lose time to last-minute changes. A requirement reads: the app must notify workers of schedule changes within one minute. It traces to the need to cut wasted travel, and it can be tested. A weaker requirement, the app should be fast, does neither.
Strategy That Anticipates Change
A strategy states who the product is for, how it will differ from alternatives and what could go wrong. Anticipating change means naming risks, such as a competitor launch or shifting regulation, and describing your response.
Metrics
Good metrics connect to goals. Adoption, retention, task completion time and customer satisfaction can all work, provided you say how each is measured and what target counts as success.
Typical Assignments and How to Approach Them
| Task element | What it tests | How to approach it |
|---|---|---|
| Requirements document | Clarity and traceability | Write testable requirements and link each to a need |
| Product strategy | Foresight | Describe positioning, risks and responses |
| Metrics | Measurement | Choose a few meaningful measures and set targets |
From Customer Need to Metric
A useful habit is to follow a single thread through the whole submission. Start with one customer need, turn it into a requirement, show how the strategy protects it, and name the metric that proves it is being met.
| Need | Requirement | Metric |
|---|---|---|
| Less wasted travel | Instant schedule-change alerts | Share of changes acknowledged within five minutes |
| Simple use on a phone | Core tasks in three taps | Task completion time |
Repeating this thread for two or three needs shows the reader that your document is coherent.
A Study Approach for Each Competency
For the requirements document, begin with the customer. Write down who they are, what they are trying to do and what gets in their way. Then draft requirements that remove those obstacles and rank them so that the reader can see what matters most.
For the strategy competency, ask what could change: competitors, costs, regulation or user behavior. Write a short response for each. For the metrics competency, choose measures that are linked to your goals and say how each will be collected. Keep the final set small enough that a team could realistically track it.
Final Review Before You Submit
Read your requirements document as a developer would. Could someone build from it without asking what you meant? Then read the strategy as an executive. Does it explain why the product deserves investment and what could go wrong?
- Each requirement can be tested and traces to a need.
- Risks and changes are named, with a planned response.
- Metrics have targets and a way of being measured.
- The business case and customer needs are both visible in the document.
Where Students Get Stuck
- Features without needs. Every requirement should explain who benefits and why.
- Untestable wording. Replace words such as easy and fast with measurable statements.
- Strategy without risks. The competency asks you to anticipate problems.
- Vanity metrics. Choose measures that show the strategy is working, not just activity.
Study Tips for E022
- Practice rewriting vague statements as measurable requirements.
- Keep the business case and customer needs on one page while you work.
- Limit metrics to a handful you can justify.
- Align your headings with the rubric lines.
How We Help with E022
Send the case, task instructions and rubric. A writer can prepare a model requirements document and strategy, explain how to write testable requirements, or review your draft. The work is study support; submit your own work under WGU's academic integrity policy.
GradeEssays is independent of Western Governors University. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late. See also our business paper help guide.
Get Your Product Strategy Sharp
Share the case, your draft and feedback. We explain how to connect needs, strategy and metrics.
Start My E022 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
WGU lists none.
The guidebook lists 3.
The MS Information Technology, Product Management program.
It is the first of three product courses. Product Design requires Product Strategy first, and Product Launch recommends both.
A document that states the problem, users, goals and requirements for a product, tied to the business case and customer needs.
Yes. We check clarity, traceability to needs and rubric match, and explain what to change.