D601 Data Storytelling for Varied Audiences, catalog number DTAN 5221, is the three CU course in the WGU Master of Science, Data Analytics that develops the communication side of the degree: taking observations and patterns you have already found and conveying them to stakeholders who differ in what they know, what they need and what they will do with the answer. The analysis is assumed here. The audience is the problem.
Why this is the hardest easy course in the MSDA
D601 has almost no technical difficulty and a return rate that surprises people. The reason is that everything it asks for runs against the habits the rest of the degree builds. Analytics training teaches you to qualify, to show working, to lead with method. Storytelling requires you to lead with the finding, drop the method into an appendix, and accept that a director reading your slide has four seconds of attention before deciding whether to keep reading.
The scored skill is audience differentiation, and it is differentiation in substance rather than in tone. Writing the same content twice with shorter sentences for the executive version is the single most common way this course goes wrong. A technical audience needs to know how you controlled for confounding. An operations audience needs to know what changes on Monday. A board needs the number that moves and the decision it forces. Those are three different documents that happen to share a dataset.
The other thing under examination is restraint with visuals. A chart in this course is an argument, not a decoration, and evaluators notice when a submission includes a plot that supports nothing. One well chosen chart with a sentence naming what it proves outscores four that are merely present.
Turning scored aspects into a section plan
The scoring detail lives in your Course of Study, not the public catalog, so start by opening the rubric and counting scored aspects. Each is judged on its own against a three point scale and each needs a score of 2 for the task to pass. There is no averaging, which in a communication course means a beautifully designed deliverable can still be returned for a thin paragraph about audience analysis.
Because this course tends to produce artefacts rather than essays, the mapping needs one extra step. Where a scored aspect is satisfied by something inside a deck or a dashboard, say so explicitly in the written portion, and point to the slide or panel by name. An evaluator should never have to guess which visual answers which aspect.
The word budget, worked. Assume six scored aspects and roughly 1,800 words of narrative alongside your artefact. Reserve 150 for an opening that names the finding and the audiences, and 100 for a close. That leaves about 1,550, or 260 words per aspect. Then rebalance: the aspects covering audience analysis and design justification deserve 350 each, taken from the descriptive aspects, because those two are where an evaluator can actually distinguish reasoning from assertion. Saying a chart type suits an audience is not justification. Saying it because that audience reads volume rather than rate, and a stacked bar would hide the very trend the decision turns on, is.
A structure that fits a storytelling deliverable
Task directions win where they specify a shape. Where they do not, this arrangement matches how storytelling aspects are usually written.
| Section | What belongs in it | How it gets read |
|---|---|---|
| The finding | One sentence stating what the data shows and what it means for the organisation | If it takes more than one sentence, the analysis has not been resolved yet |
| Audience analysis | Each audience named, with prior knowledge, decision authority and the question they will actually ask | Scored for specificity; generic personas read as filler |
| Message per audience | What each group is told, what is deliberately withheld and why | Withholding with a reason is a strength, not an omission |
| Visual choices | Each chart named with the comparison it makes and the alternative you rejected | The section where design becomes defensible instead of decorative |
| Delivery plan | Channel, sequence, length and what happens in the room after the reveal | Often under written; it is where the practical grasp shows |
| Ethics and limits | What the visual could mislead about, and what you did to prevent it | Truncated axes and cherry picked ranges are the standard examples |
Build the artefact after the audience analysis, never before. Deciding what a chart looks like before deciding who reads it is the reason most returned submissions in this course have to be rebuilt rather than patched.
Evidence craft in a communication course
The evidence in D601 is unusual: partly your own analysis, partly published work on how people read data. Both need handling.
- Cite the source of every figure that appears in a visual, including your own earlier analysis, so a reader can trace the number back.
- Support design claims with literature rather than taste. Claims about colour, chart type, preattentive attributes and cognitive load all have published backing, and using it converts opinion into evidence.
- Label axes and units on every exhibit. An unlabelled axis costs an accuracy aspect faster than a genuinely poor chart choice does.
- Keep the underlying data reachable. If a figure is aggregated, say what it was aggregated from.
- Use APA for external sources and stay consistent. Communication courses attract citation slips because the sources are unfamiliar.
- Where you simplify for an audience, name the simplification in the written portion so the evaluator sees a decision rather than an error.
One line separates strong submissions: an explicit statement of what the audience is not being told, and why that omission is defensible. It shows you understand the difference between simplifying and misleading, which is the ethical core of the whole course.
What separates Competent from a submission sent back
Because each aspect is scored on its own, returns here tend to hit the reasoning sections while the artefact itself passes.
- Each audience is described in terms of decisions they hold, not job titles they hold.
- Each visual has a stated purpose and at least one rejected alternative.
- The finding stated at the top is the same finding the last slide supports. Drift between them is common and obvious.
- Every claim about how people perceive a visual is sourced rather than asserted.
- The written portion points to the artefact by slide or panel name, so scoring is reading rather than searching.
Performance assessment work can be revised and resubmitted with no grade penalty, so the real cost of a return is queue time. In a six month flat rate term that time is the budget, and a communication course is a poor place to spend it twice.
Six mistakes that cost time in D601
- Changing tone instead of changing content. The executive version is not the technical version with shorter words. It answers a different question.
- Leading with method. A story that opens with how the data was cleaned has already lost the audience it was written for.
- Charts that carry no argument. If you cannot write the sentence the chart proves, the chart does not belong.
- Personas with no decision authority attached. Naming an audience without naming what they can approve makes the message unaimed.
- Ignoring the ethics aspect until the end. Axis truncation and selective ranges are the standard examples, and a submission that never mentions them looks unaware.
- Building the deck first. Design decided before audience analysis cannot be justified afterwards without visible reverse engineering.
Writing the same finding three ways
The clearest way to see what D601 wants is to take one finding and write it out for three readers. Suppose the analysis shows that customers acquired through one channel churn at nearly twice the rate of the rest within ninety days.
For the analytics team, the honest version leads with method: the cohort definition, the survival curve, the confounders you controlled for, the sample size in the affected segment, and the reason you are confident the difference is not an artefact of when those customers joined. This version earns trust by exposing its own weak points.
For the operations manager who owns onboarding, none of that belongs in the first paragraph. The version they need leads with the ninety day window, names the two touchpoints inside it that the team actually controls, and ends with a specific change to test next month. Method appears only as a single line establishing that the difference is real.
For the executive committee, the version is shorter again and denominated in money. The churn gap becomes an annual revenue figure, sitting beside the cost of the channel that produced it, and the ask is a decision: keep spending, reduce spending, or fund a fix. One chart, one number, one question.
Three documents, one analysis, and almost no shared sentences. When a submission is returned in this course, the usual diagnosis is that all three versions came out looking like the first one with the technical words removed. Writing them from three different opening sentences, rather than editing one down twice, is the habit that prevents it.
How support works on this course
Send the rubric from your Course of Study and the task directions. You get an aspect mapped draft of the written portion, an audience analysis that names decisions rather than titles, design justifications with rejected alternatives attached, and a walkthrough of why each choice was made so you can defend it in your own words.
D601 is short on technical load and long on rework risk, which makes it one of the better courses to clear early in a term. Terms run six months at a flat rate, so closing a communication course in week two rather than week twenty is a straightforward gain on cost per course.
Questions students ask about D601
Is D601 the same course as DTAN 5221?
Do I need a specific visualisation tool for D601?
Can you build my deck and dashboard?
Where D601 sits in WGU's programs
The July 2026 catalog places this code in 3 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.