WGU D428: Design Thinking for Business

Why D428 Shows Up in So Many WGU Degree Plans

WGU D428, Design Thinking for Business, is a short course with an outsized effect on how you approach problems for the rest of your degree. WGU's published description sets the course up as a study of how the design thinking method attacks complex problems. The framing is deliberately human-centered: you start from the people affected and work forward with empathy and creativity instead of analysis alone. The course walks you through the principles and the stages, then asks you to apply them to realistic scenarios.

Direct answer: D428 is not a proctored multiple-choice test — you pass it by submitting a written performance assessment that walks an assigned business scenario through the design thinking process. Read the rubric prompt by prompt, answer every lettered requirement in its own clearly labeled section using specifics from the scenario rather than generic theory, and support your reasoning with the course material wherever the rubric asks for it.

The course turns up across a wide slice of WGU's catalog. Business Management, Marketing, Project Management, and the B.S. Data Analytics program all list it, and on each of those program pages it sits in the general education portion of the plan rather than the business core. That placement tells you how WGU sees it: not a specialist elective for future product designers, but a way of thinking the university wants every graduate to carry into whatever they do next. Design thinking is a general-purpose method for handling problems where the requirements are fuzzy, the stakeholders disagree, and the obvious solution has already failed once. Whether you end up in operations, marketing, analytics, or product work, you will be handed problems shaped exactly like that.

If you are anxious about D428, it is usually for one of two reasons. Either you are a quantitative thinker who finds an open-ended creative process unnervingly vague, or you are a confident writer who assumes a writing-based course must be easy and so skims the rubric. Both students can pass comfortably. The first needs to see that design thinking has a rigid structure underneath the creativity; the second needs to slow down and treat the rubric as a checklist. Everything below is built around those two fixes. For related coursework in the same college, see the School of Business guides.

What the D428 Performance Assessment Actually Covers

Public course information and student discussion consistently point to a single written performance assessment built around a business scenario supplied by the course. The subject matter you need to control is narrow, but it has to be applied precisely:

• Design thinking as a mindset. What makes an approach human-centered, why empathy is treated as a discipline rather than a feeling, and how design thinking differs from conventional analytical problem solving.
• The stages of the process. The widely taught five-stage model — empathize, define, ideate, prototype, test — including what each stage produces and why the process is iterative rather than linear.
• Empathy methods. Identifying who the affected users and stakeholders are, what information you still lack, and where or from whom that information could realistically be gathered.
• Problem definition. Turning messy observations into a focused problem statement that describes a user's need rather than jumping straight to a preferred solution.
• Ideation. Generating a genuine range of options, deferring judgment, and explaining the reasoning behind the ideas you keep.
• Prototyping and testing. Building something cheap and rough enough to learn from, deciding what you are testing for, and describing how feedback would change the next iteration.
• Application to a business context. Connecting the process to organizational realities such as cost, feasibility, customer experience, and competing stakeholder priorities.

Because the assessment is scenario-based, the evaluator is not looking for a textbook summary. They are looking for evidence that you can run the method on the situation in front of you. Scenarios and rubric wording are revised over time, so treat your current course page and task instructions as the authority over anything you read elsewhere, including this guide.

How Hard D428 Is, and What to Budget

There is no proctored exam to schedule, no math, and the reading load is modest, which is why D428 tends to get treated as a quick course. That creates a specific trap: a student hears "easy," writes a fluent essay that never actually addresses the rubric's lettered prompts, and gets the task returned for revision. A revision cycle costs days of waiting, which is how a short course quietly turns into a slow one.

A realistic plan is a few focused sessions rather than one marathon. Spend the first reading the task instructions and rubric end to end and skimming the course material for the stage definitions. Spend the second working through the scenario stage by stage in rough notes. Spend the third writing, and a short fourth on formatting, citations, and a rubric audit. If you already work somewhere user research or process improvement is routine, you will move faster. If writing to a rubric is new to you, give the audit the extra time rather than the drafting.

Speed comes from structure, not from rushing. The students who finish fastest are the ones who built their document's headings directly from the rubric before writing a single paragraph. If you want the same discipline applied to a more strategy-heavy course, D081 Innovative and Strategic Thinking uses a similar submission-based structure.

A Study Plan Built for a Rubric-Graded Course

Reading the course material passively is the least efficient thing you can do here. Use retrieval and application instead.

Build a stage card set. Make one card per stage of the process with three prompts on the back: what is the purpose of this stage, what does it produce, and what does doing it badly look like. Test yourself from memory rather than rereading. Five well-understood stages beat forty vague flashcards.

Rehearse on a problem you already know. Before you touch the graded scenario, run the full process on something from your own life — a frustrating checkout experience, a broken process at work, a confusing form. Write half a page per stage. This turns the vocabulary into something you can actually use, and it costs about an hour.

Reverse-outline the rubric. Copy each rubric requirement into a blank document as its own heading, in the rubric's order and using its own letters, then write underneath each heading. This single habit prevents the most common cause of returned tasks: a requirement that was answered somewhere inside a paragraph but not visibly.

Quote the scenario back. For every claim you make, point to a detail in the scenario that supports it. An evaluator can tell the difference between "gather feedback from customers" and "survey the weekday afternoon visitors described in the scenario, because they are the group whose complaints triggered the review."

Space your revision. Draft, leave it overnight, then reread with the rubric beside you. A one-day gap catches errors an immediate reread will not, and it is far cheaper than an evaluator's revision cycle.

If your program also includes user-focused work, the habits you build here transfer directly to D479 User Experience Design and to D175 Consumer Behavior, both of which lean on the same empathize-then-define discipline.

Where D428 Submissions Usually Go Wrong

• Solving before empathizing. Announcing a solution in the first paragraph and reverse-engineering the process around it. The rubric rewards the sequence, not the answer.
• Generic answers. Prose that would apply to any company. If your paragraph would survive a find-and-replace of the scenario's name, it is too generic.
• Skipping the "what information do you still need" prompts. Design thinking rewards naming your unknowns and your sources. Students often assert facts the scenario never gave them.
• Collapsing define and ideate. A problem statement is not a solution list. Keep them in separate sections under separate headings.
• Thin prototyping and testing sections. These come last and get the least energy. Say what the prototype is, what question it answers, who tests it, and what you would do with the result.
• Citation and originality problems. Anything drawn from the course material or an outside source needs attribution in the required format. Submitted work is checked for originality, so build your own document from your own notes.
• Ignoring the format guidance. Follow the task's file type, headings, and length instructions exactly.

D428 Readiness Checklist

• Can you name each stage of the design thinking process and state, in one sentence, what it produces?
• Can you explain what makes an approach human-centered to someone who has never heard the phrase?
• Can you identify the users and stakeholders in your scenario and say what each one cares about?
• Can you list the information you still lack and name a realistic source for each piece?
• Can you write a problem statement that describes a need without naming a solution?
• Can you produce several genuinely different ideas rather than three versions of one idea?
• Can you describe a low-cost prototype and the specific question it is meant to answer?
• Can you point to a heading in your document for every lettered rubric requirement?
• Can you show a scenario detail behind every recommendation you make?

D428 FAQ

Is D428 an objective assessment or a performance assessment?

Public course information indicates D428 is assessed by a written performance assessment built around a business scenario, not by a proctored objective exam. Confirm on your own course page, since assessment structures are occasionally revised.

How many competency units is D428 worth?

WGU's public program pages list the course without a unit value, so check your official degree plan or your program's course listing on WGU's site rather than relying on a secondhand figure.

Do I need design experience or software to pass?

No. The assessment is written work about applying a problem-solving process. Sketching or diagramming tools can help you think, but polished visual design is not what is being graded.

What if my task comes back for revision?

A returned task is routine and is not a failure. Read the evaluator's comments against the specific rubric aspect that was marked, revise only what was flagged, and resubmit. Most revisions are narrow.

How should I structure the document?

Mirror the rubric. Use the task's own section letters and requirement wording as headings so an evaluator can find each answer without hunting, then write substantive content under each one.

Which courses pair well with D428?

It sits comfortably alongside strategy and analysis coursework such as D081 and systems-oriented material like D459 Introduction to Systems Thinking. Browse the full library of WGU course guides to plan your term.