D473 Solutions Design and Visualization Capstone is BUS 4910 in the WGU catalog and carries 3 competency units, synthesizing business analytics, operations and supply chain skills into a culminating deliverable. Capstones fail on assembly rather than on knowledge, and this one adds a second demand: the solution has to be presented visually and persuasively to someone who did not do the analysis. Aspects are judged one by one, and each needs a 2. D473 and BUS 4910 are the same course.
What the capstone is testing
Solutions design is a different activity from analysis. Analysis ends with a finding; design ends with something a business could implement, costed, sequenced and owned. The visualization requirement carries the same shift: charts in an analysis course exist to show what the data says, and charts in a solutions deliverable exist to make a decision-maker act.
The synthesis demand is what makes it a capstone. A problem that needs only data work, or only process work, is under-scoped for this course. The material that feeds it runs through D468 Discovering Data for framing, D467 Exploring Data and D466 Analyzing and Visualizing Data for the analysis, and D464 Managing Operations and D471 Global Supply Chain Management for the operations half.
Planning a capstone with a deliverable at the end
Assessment types and task requirements are not published in the WGU catalog; the Course of Study in your portal has them. If a performance assessment carries yours, plan in two tracks, because a capstone with a visual deliverable has a build phase that word counts do not capture, and the build always takes longer than expected.
A worked example. Twelve aspects with a 3,000 word written component plus visual deliverables. Reserve 250 for the problem and scope and 150 for the close, leaving 2,600. Three aspects on problem definition and data take 200 each, giving 600. Four analytical aspects take 300 each, giving 1,200. Three solution design aspects take 200 each, giving 600. Two aspects on the visual deliverable and its communication take 100 each, giving 200. Sum: 600 plus 1,200 plus 600 plus 200 equals 2,600. Then schedule separately: at 700 finished words a day the writing is roughly four working days, and the visual build is another two, so six working days plus revision, which is not a weekend.
A solutions deliverable that holds together
| Component | What it must do | The capstone-level requirement |
|---|---|---|
| Problem statement | Name the business problem and its cost | Quantified, so the solution's value can be judged against it |
| Scope | State what is included and excluded | Explicit exclusions, since capstones drift without them |
| Data and method | What was used and how, with limitations | Reproducible enough that another analyst could repeat it |
| Findings | What the analysis established | Each finding stated as a sentence, not as a chart |
| Solution design | The proposed change, in operational detail | Steps, owners, resources and a first milestone |
| Visual deliverable | The dashboard, model or presentation | Built for a decision-maker, with the finding as the headline |
| Value and evaluation | What it is worth and how that will be verified | An estimate with its assumptions, and a measurement plan |
Evidence at capstone scale
Capstone evidence has to survive scrutiny in two directions. The analytical direction needs traceability: which data, which population, which transformations, which measure. Keep the raw data untouched, record every transformation, and make sure any figure quoted in the written document can be found in the workbook or script that produced it.
The design direction needs feasibility evidence. A proposed solution should show that the resources it needs exist, that the change is compatible with constraints you have named, and ideally that something comparable has worked elsewhere, cited in APA. Estimating the value of the solution is where most students hedge, and hedging costs aspects: an estimate with clearly stated assumptions is stronger than a refusal to estimate. Submitted work runs through WGU's Similarity Checker, so all writing must be your own, and at capstone length the safest habit is to draft from notes rather than from open sources.
Where capstones pass and where they return
WGU records Competent or Not Competent, keeps no letter grades and no GPA, and every aspect needs its own 2. This capstone returns for coverage gaps far more often than for weak work. A mid-rubric aspect gets two sentences because the writer was tired. The visualization is built to display rather than to persuade. The value estimate is missing because it felt speculative. Or the evaluation plan is a promise to monitor.
Two mechanical habits prevent nearly all of it. Keep a coverage checklist and tick an aspect only when its section is finished, never when it is planned. And run a final pass where you read each rubric aspect and point at the paragraph, chart or table that satisfies it, since anything you cannot point to is not there. Because performance assessment work can be revised and resubmitted without penalty, a returned capstone costs time rather than standing, and the revision guide covers closing it in one pass.
Six mistakes that cost weeks here
- A topic that needs only one discipline. The synthesis requirement means a pure data problem or a pure process problem will leave aspects unfillable.
- Building the dashboard before the finding. Visuals designed before you know the message end up displaying everything and arguing nothing.
- Scope with no exclusions. Capstones expand until a deadline stops them unless a boundary is written down.
- No quantified problem. Without a cost of the current state, the solution's value cannot be assessed.
- Solution without owners. A design nobody is named to execute is an idea, and design aspects treat it as one.
- Submitting late in the term. A capstone with no revision window is a gamble against a queue you do not control.
Capstone with an analytical and an operational half
Send the rubric and your topic. You get a scope read, a two-track schedule, and a model deliverable built aspect by aspect with a walkthrough.
Building a visual deliverable a decision-maker would use
The visualization half of this capstone is scored on persuasion rather than on completeness, and the difference shows up in three design decisions.
The first is hierarchy. A decision-maker looking at your deliverable for ten seconds should see one thing: the headline number or the single comparison that carries the argument. Everything else is support and should look like support, smaller and lower. Dashboards that give six charts equal visual weight force the reader to do the prioritizing that was your job. The second is framing. Every number needs something to be judged against, whether that is a target, a prior period, a benchmark or a segment, because a figure alone tells a reader nothing about whether to act. The third is the call to action. Somewhere in the deliverable, in words, is the sentence saying what should be done and by whom, since a visual that leaves the conclusion implicit will be interpreted several different ways by several different readers.
A practical test before submission: show the deliverable to someone who knows nothing about the project and ask them what it is telling them to do. If they describe the data rather than the action, the hierarchy is wrong. If they cannot tell whether the situation is good or bad, the framing is missing. Both failures are common, both are quick to fix, and both are exactly what a communication aspect in a solutions capstone is scored on.
Three questions D473 students ask
How do I choose a capstone topic that satisfies the synthesis requirement?
Can I use data from my employer?
How early should I start?
Three CUs and the term boundary
Everywhere else in a WGU plan, flat-rate terms reward speed by lowering the effective cost per course. At the capstone the arithmetic inverts: a single unfinished course can require another six month term on its own. That asymmetry is why capstone planning deserves the most attention in the whole degree, and why early submission beats late perfection. The capstone help page covers the staged method we use.
Where D473 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.