D428 Design Thinking for Business carries the catalog number PHIL 1110 and is worth three competency units. WGU describes it as a human-centered design thinking methodology that uses empathy and creativity to solve complex problems and drive innovation. The description sounds soft. The scored work is not. What an evaluator looks for is a documented trail: who you spoke to, what you learned that contradicted what you already believed, how the problem statement moved because of it, what you built cheaply, and what testing told you. A clever idea with no trail behind it scores worse than an ordinary idea with a complete one.
What PHIL 1110 rewards, and what it quietly ignores
Most students arrive at D428 with the answer already in their head. They know the problem at their workplace, they know what they would fix, and the course looks like paperwork wrapped around a decision they made months ago. That instinct is exactly what the course is built to disrupt, and it is the single largest cause of returned work here.
Design thinking is a sequence with a deliberate shape: understand the human situation before defining the problem, widen the option set before narrowing it, build something crude before building something good, and let a test change your mind. Each of those steps produces a visible artifact. An evaluator reading your submission is checking whether the artifacts exist and whether they influenced each other, not whether your final concept is impressive.
The tell for weak work is a submission where the ideation section contains three options and one of them is obviously the one the writer wanted from the start. Real divergence produces uncomfortable options: the expensive one, the one that removes a job, the one that solves the problem by not doing the activity at all. Listing those and explaining why you set them aside is what a convergence aspect is asking for. Listing two straw men next to your favourite is not.
What the course does not reward is business polish. A beautiful financial projection attached to an untested concept reads as a student who skipped the middle of the process. Save the numbers for the courses that ask for them.
Turning scored aspects into a section plan
WGU keeps the scoring detail for each course inside your Course of Study rather than the public catalog, so step one in D428 is to open your rubric and count the scored aspects. Each aspect is judged on its own, and a score of 2 in each one is what passes the task. Nothing averages. A strong empathy section will not carry a thin prototype section.
Give every scored aspect its own heading, and word the heading close to the rubric's own noun. Design thinking submissions are especially prone to burying an aspect inside a narrative, because the process is a story and students tell it as one. An evaluator scoring aspect by aspect should never have to hunt through your paragraphs for the point of view statement.
The word budget, worked. Say your rubric shows seven scored aspects and the directions ask for roughly 2,100 words. Take 150 for the opening context and 100 for the closing reflection, which leaves 1,850 across seven aspects, or about 265 words each. Now weight it. The empathy aspect and the testing aspect both need raw material quoted or described, so lift them to 350. The ideation aspect needs a list plus reasoning, so hold it at 300. Pull the difference out of the context and definition aspects, which are the ones students overwrite. The arithmetic still lands, and the length now sits where the evidence sits.
An aspect answered in under 120 words is nearly always an assertion with no artifact behind it. That is the most common return in this course, and it is fixable in an hour if you catch it before submitting rather than after.
A structure that fits a design thinking deliverable
Where your task directions specify headings, follow them exactly. Where they leave the shape open, this arrangement maps onto how design thinking aspects are usually written and keeps the artifacts visible.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| Context | The organization, the situation, and why it is unsettled rather than simply broken | Frames the work; rarely scored alone but a vague context weakens every later aspect |
| Empathy work | Who you engaged, how, and what they said, with observations separated from your interpretation | Scored on whether real people informed the work and whether their words appear |
| Problem definition | A point of view statement naming a user, a need and an insight, written after the empathy work | Scored on precision; a problem statement that could have been written on day one signals a skipped step |
| Ideation | The full option set generated, including options you rejected, with the method used to generate them | Scored on breadth first and reasoning second |
| Prototype | A described or depicted low fidelity build: a storyboard, a paper flow, a service script, a mock | Scored on fitness for testing, not on production quality |
| Test and iterate | Who tested it, what happened, and what specifically changed as a result | The aspect that fails most often; a test with no change recorded reads as a demonstration |
| Reflection | What the process taught you about the problem and about your own assumptions | Scored where the rubric names it; keep it concrete and tied to a moment in the work |
| Sources | Design thinking literature and any organizational documents, APA formatted | Scored where citation is named; an uncited framework is a common return |
Evidence craft when your data is people
D428 has an evidence problem that most gen ed courses avoid: much of your material comes from conversations rather than publications. That is legitimate evidence, and it needs handling that keeps it credible and keeps other people protected.
- Record method before content. Say how many people you engaged, in what setting, and what you asked. An insight with no method attached reads as invention.
- Quote sparingly but quote exactly. One sentence in a participant's own words does more for an empathy aspect than a page of paraphrase.
- Strip identifiers. Roles and tenure are useful, names and employers usually are not. Write participant A, a shift supervisor with four years on the line.
- Separate the observation from your reading of it. Two column notes work well: what happened on the left, what you think it means on the right.
- Cite the framework you used. Empathy mapping, journey mapping and the double diamond all have literature behind them, and naming the source is what turns a template into scholarship.
- Show the artifact, not a claim about the artifact. If you built a journey map, put it in the document as a table. Saying you built one earns nothing.
Strong submissions also state a limit on their own evidence. Four interviews inside one department is a narrow sample and you should say so, then explain what a wider sample would probably have added. Naming the boundary reads as judgment. Ignoring it reads as a gap the evaluator has to find.
What separates Competent from a submission sent back
Because aspects are scored independently, returns in D428 are usually local. One aspect asked for two things and the paper delivered one. The most frequent single cause is a testing section that reports satisfaction rather than change.
- The problem statement is visibly different from the one implied in your opening context, and you say what moved it.
- Every phase produces an artifact the reader can see: quotes, an option list, a described prototype, a test result.
- The rejected ideas are real. At least one of them should be something a reasonable person might have chosen.
- The iteration is specific. Version one did X, testers hit Y, version two changed Z. That sentence pattern satisfies most iteration aspects on its own.
- The reflection points at a particular moment rather than delivering general praise for the method.
Performance assessment work at WGU can be revised and resubmitted without a grade penalty, so a return costs time rather than standing. In a six month flat rate term, time is the entire budget. A three CU gen ed course that eats five weeks because the testing aspect came back twice is a course that pushed something else out of the term.
Six mistakes that cost time in D428
- Writing the process backwards from the solution. Evaluators recognise a paper where the empathy section conveniently produces the answer already chosen. Let the notes be a little inconvenient.
- Treating a survey as empathy work. A five question rating scale gives you numbers, not needs. Design thinking evidence is conversational, and the rubric language usually reflects that.
- Building a polished prototype. High fidelity work discourages honest feedback and burns time. Paper, storyboards and scripts test better.
- Skipping the reject list. Ideation aspects are scored on breadth. Three ideas is not a breadth demonstration no matter how good they are.
- Confusing the problem with the symptom. Long checkout queues are a symptom. The point of view statement has to name the human need underneath.
- Leaving the test until the night before. Testing needs another human being with a calendar. Book it in week one of the course, not week five.
How support works on this course
Send the rubric from your Course of Study, the task directions, and whatever raw material you already have: interview notes, a rough problem statement, photographs of a whiteboard. The work comes back aspect mapped, with each scored aspect under its own heading, your own evidence carried through rather than replaced, and a walkthrough explaining why each section is shaped the way it is.
Where D428 sits alongside a proctored objective assessment in your plan, the boundary is plain. Proctored exams are yours to sit. We build the study plan, drill the vocabulary of the method and give an honest readiness read. We never sit assessments and we never ask for portal credentials.
Questions students ask about D428
Is D428 the same course as PHIL 1110?
Do I need a real company to do the work about?
How many people do I actually need to interview?
Stuck on the empathy or testing section?
Send your rubric and your raw notes. You get an aspect mapped draft that keeps your own evidence and shows the process trail an evaluator is looking for.
Where D428 sits in WGU's programs
The July 2026 catalog places this code in 5 current WGU programs. 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.