D500 Data Visualization, catalog number DTAN 3221, is a two competency unit course in the WGU School of Technology. The catalog describes it as applying design principles, human perception, colour theory and storytelling to presenting data with visualization tools. Notice the order. Perception comes before tools, and that ordering is the grading philosophy. A chart is a claim about numbers routed through an eye that has fixed limits, and the aspects in this course reward students who can explain their choices in terms of those limits rather than in terms of what a tool made easy.
Perception is the reason chart choice has right answers
Visualization feels subjective until you know the research, at which point most of it stops being a matter of taste. The eye judges some encodings accurately and others badly, and the ordering has been measured. Position along a common scale is read most accurately, which is why a bar chart or a dot plot beats nearly everything else for comparing values. Length comes next, then angle and slope, then area, then colour saturation and hue. Area and hue sit near the bottom, which is the technical reason a pie chart with seven slices and a heat map with an unordered colour scheme both underperform.
Preattentive processing is the other half of the mechanism. A small number of visual properties, colour, size, orientation, enclosure and a few more, are detected before conscious attention, which is why one red bar in a field of grey bars is found instantly and why a legend with twelve colours is found slowly. Designing with that in mind means spending your one attention grabbing property on the thing that matters and letting everything else recede.
Colour theory in this course is practical rather than artistic. Sequential schemes for ordered magnitude, diverging schemes for values around a meaningful midpoint, categorical schemes for unordered groups, and a hard cap on how many categorical colours a reader can hold, which is fewer than most students assume. Add accessibility on top: red and green together fail for a substantial share of readers, so encode with more than hue and check contrast rather than trusting the default palette.
Storytelling is the fourth strand and the one most likely to be graded as a separate aspect. A chart answers a question; a sequence of charts makes an argument. That means an order, a claim per figure, and a conclusion. Rubrics that mention narrative are asking whether your visuals lead somewhere.
Turning scored aspects into a section plan
WGU keeps scoring detail inside your Course of Study rather than in the public catalog, so open the rubric and count aspects before building anything. Each is scored independently and a score of 2 in each aspect passes the task. Nothing averages, so a striking dashboard will not carry a rationale aspect that never mentions the audience.
In visualization courses the written rationale is usually where marks are lost, because students spend their time in the tool. Budget the writing first, then build.
The word budget, worked. Assume six scored aspects and directions asking for about 1,600 words of rationale alongside the visuals. Reserve 100 for the audience and question and 100 for the close, leaving 1,400 across six aspects, or about 235 each. Then reweight. The aspect asking you to justify design choices needs a paragraph per major decision, so lift it to 400. The accessibility or colour aspect needs specifics rather than a sentence, so give it 250. Tool description and data source aspects compress to 150 each. The total holds near 1,400 and the rationale now covers the aspects rather than the software.
A quick self test before you submit: cover the title of each figure and ask whether a colleague could state its main point in one sentence. If they cannot, the encoding or the emphasis is wrong, not the data.
A structure that fits a visualization deliverable
Where the task directions specify a structure, follow theirs. Where the shape is open, this arrangement pairs each visual with the reasoning that earns the marks.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| Audience and question | Who reads this, what they decide, and how much time they will give it | Frames every design choice; an unnamed audience makes rationale impossible |
| Data and preparation | Source, period, aggregation level and any reshaping done for the visuals | Scored on transparency; an unexplained aggregation can distort a whole chart |
| Encoding choices | Chart type per figure, tied to variable types and to the accuracy of the encoding | The central aspect; taste is not a justification but perception is |
| Colour and accessibility | Palette type, number of categories, contrast, and a check that does not rely on hue alone | Scored where named; a specific check beats a general commitment |
| Layout and hierarchy | Reading order, what is emphasised, what is deliberately quiet | Scored on whether attention lands where the message is |
| Narrative | The sequence of figures and the claim each one carries | Scored on progression; a gallery of unrelated charts is not a story |
| Interactivity | Filters or drilldowns, each justified by a question a user would ask | Scored on purpose; interactivity added because the tool offers it reads as decoration |
| Limitations | What the visuals cannot show and where a reader could be misled | Scored where named; honest constraints strengthen the rationale |
| References | Data sources, perception and design literature, APA formatted | Scored where citation is named in the aspect |
Evidence craft when the artifact is a picture
Visualization work is judged twice: once on what the figure shows and once on whether the figure can be trusted. The second judgment is made from the details around the edges of the chart.
- Label axes with units and state the period. An unlabelled axis is the fastest way to lose an otherwise strong figure.
- Put the data source and extract date on or beside every figure, so the chart survives being copied into someone else's slide.
- Show the sample size. A percentage from twelve responses and one from twelve thousand look identical without it.
- Start bar axes at zero and say so if you deliberately truncate a line chart, because axis choice is a defensible decision only when it is stated.
- Order categories by value or by a natural sequence rather than alphabetically, unless the reader will look things up by name.
- Cite the perception and design principles you rely on. They come from named research, and citing them turns a preference into a justification.
The habit that separates a strong rationale is naming the alternative you rejected. Two sentences explaining that you considered a stacked bar and chose small multiples because comparing segments across stacks is unreliable will satisfy a design justification aspect more completely than a page of praise for your final choice.
What separates Competent from a submission sent back
Aspects are scored one at a time, so returns here are usually about the rationale rather than the artwork. The most common cause is a set of good looking charts with a write up that describes them instead of defending them.
- Every figure names its audience question and the decision it supports.
- Every encoding choice is justified against variable type and perceptual accuracy.
- The colour scheme is named as sequential, diverging or categorical and matched to the data it encodes.
- Accessibility is demonstrated with a specific check rather than asserted.
- The figures run in an order that builds toward a conclusion, and the conclusion is stated.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs time rather than standing. In a six month flat rate term that time is the only real currency, and a two CU course is meant to be a quick close. Writing the rationale as you build rather than afterwards is the single change that keeps it quick.
Six mistakes that cost time in D500
- Building first and justifying later. Reconstructed reasoning is vague reasoning, and the justification aspects are where this course is won.
- Using colour to encode quantity when position would do. Hue is read poorly for magnitude, so a heat map where a bar chart fits is a perceptual downgrade.
- Too many categories. Beyond a handful of colours the legend becomes a lookup table and the chart becomes a puzzle.
- Dual axes for unrelated units. They invite false comparisons, and any figure that suggests a relationship the data does not support is a defensible return.
- Adding interactivity for its own sake. Each control needs a user question behind it or it is noise with a click target.
- Forgetting the reader is not you. You know what the axes mean. The person who receives this in an email does not, and legibility aspects are scored from their position.
How support works on this course
Send the rubric from your Course of Study, the task directions and the dataset. The work comes back aspect mapped: an audience and question stated first, encodings chosen against variable types and perceptual accuracy, a colour scheme matched to the data with an accessibility check written out, a narrative order with a claim per figure, and a rationale that argues rather than describes. The walkthrough covers the perception rules behind each choice so the reasoning carries into later courses that require reporting.
If a proctored objective assessment sits on this course, the line is fixed. Proctored exams are yours to sit. We prepare only, with revision plans, practice critiques and an honest go or wait read. We never sit assessments and we never ask for portal credentials.
Questions students ask about D500
Is D500 the same course as DTAN 3221?
Which visualization tool should I use?
Do I need design or art experience to do well?
Charts built but the rationale is thin?
Send your rubric and your figures. You get an aspect mapped rationale that justifies every encoding on perception grounds, with the accessibility check written out.
Where D500 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.