D468 Discovering Data is BUS 2780 in the WGU catalog and carries 3 competency units, covering the analytical concepts, processes and tools of business analytics, beginning with how to ask effective questions. It is the conceptual entry point to the analytics sequence and the one students most often underrate, because its subject matter is thinking rather than tooling. Rubric aspects here score the framing of a problem, and each aspect requires a 2. D468 and BUS 2780 are the same course.
What D468 builds toward
Analytics fails at the start more often than in the middle. An analyst is asked why sales are down, spends two weeks building a report, and delivers something nobody can act on, because the real question was which of four things we control is worth changing. The course exists to prevent that: it teaches the analytics process end to end and puts most of its weight on the first step, translating a business concern into a question that data could actually answer.
The rest of the process follows: identifying what data would be required, choosing an approach, interpreting a result and communicating it to a decision-maker. That framing makes D468 the natural first course in the sequence, ahead of D467 Exploring Data on preparation, D466 Analyzing and Visualizing Data on analysis, and D465 Data Applications on scripting.
Aspects that score framing rather than output
WGU does not publish assessment types or task requirements in its catalog; the Course of Study inside your portal does. If a performance assessment carries your version, expect aspects that ask you to justify a question, identify required data, or explain a choice of approach, and note that these are answered in prose rather than in output. A student who arrives from a tooling course looking for something to compute will underwrite them.
A worked example. Seven aspects, a 1,850 word target. Reserve 150 for the business situation and 90 for the close, leaving 1,610. Two aspects on question formulation take 290 each, giving 580. Two on data requirements take 240 each, giving 480. One on selecting an analytical approach takes 280. One on limitations or ethics takes 160. One on communicating results takes 110. Sum: 580 plus 480 plus 280 plus 160 plus 110 equals 1,610. The proportion tells the story: more than a third of the document is about the question and the data needed to answer it, before any analysis is described.
Turning a business concern into an answerable question
| Stage | What you produce | The test it must pass |
|---|---|---|
| Concern as stated | The question as the business asked it, verbatim | Recorded honestly, including its vagueness |
| Decision behind it | What someone will do differently depending on the answer | If no decision changes, the question is not worth answering |
| Refined question | A specific question with a population, a measure and a period | Two analysts would interpret it identically |
| Data required | Fields, sources, granularity and time span needed | Each field is tied to a part of the question |
| Availability check | What exists, what does not, and the workaround | Names the gap rather than assuming the data is there |
| Approach | Descriptive, comparative, predictive or diagnostic | Matches what the decision actually needs |
| Answer format | What the deliverable looks like and who reads it | Designed for the decision-maker, not for the analyst |
Evidence for a conceptual course
Because the deliverable is reasoning rather than output, evidence comes from two directions. Analytics literature supports claims about process, approach selection and interpretation, cited in APA, and it should be applied rather than summarized. The business situation supplies the specifics, and its evidentiary standard is concreteness: a real or realistic scenario with actual constraints produces a question worth refining, while a generic company produces a generic question that any refinement leaves unchanged.
The most valuable evidence of all is the availability check. Stating what data the organization plausibly holds, at what granularity, and what it does not, demonstrates the practical judgment the course is teaching. An analysis plan that assumes perfect data reads as naive, and an aspect asking about data requirements is usually scored on whether you noticed the gaps. Submitted work runs through WGU's Similarity Checker, so process descriptions must be written in your own words.
What passes in this course
WGU marks work Competent or Not Competent, with no letter grades and no GPA, and every aspect needs its own 2. D468 tasks return most often for questions that are still not answerable. Why are customers leaving reads like a question and is not one, because it names no population, no measure and no period. Which customer segments had the highest cancellation rate in the last four quarters, and which of the three factors we record predicts it best, is a question a data set can address.
Passing submissions also connect the question to a decision explicitly. Somewhere in the document there is a sentence saying what the business will do differently if the answer is one thing rather than another, and that sentence justifies the whole analysis. They acknowledge what the approach cannot establish, particularly the difference between association and cause. And they describe a deliverable sized for its audience, since an executive question answered with a forty page appendix has not been answered. Where a task comes back, the evaluator names the aspects and the resubmission costs only queue time.
Six mistakes that stretch this course
- A question with no population or period. Without both, two people would answer it differently and neither would be wrong.
- Skipping the decision. An analysis nobody will act on is the most expensive kind, and rubrics ask about it directly.
- Assuming the data exists. The availability check is a scored aspect in most versions and the fastest one to forget.
- Approach chosen by familiarity. Running the analysis you know rather than the one the decision needs is visible to an evaluator.
- Confusing correlation with cause. The interpretation error that appears in nearly every weak analytics submission.
- Deliverable designed for an analyst. The communication aspect asks who reads it and what they need, not how thorough you were.
Analytics plan due before any data arrives
Send the rubric and the business situation. The model draft refines the question, specifies the data, selects an approach and names the decision, aspect-mapped.
Four kinds of question, and why the difference matters
Analytics questions fall into four families, and naming which family you are in resolves most later decisions about approach, data and deliverable.
Descriptive questions ask what happened. How many, how much, in which segments, over what period. They need accurate data and clean aggregation, and their honest deliverable is a small set of numbers with context. Diagnostic questions ask why it happened, and they are harder than they look because they require comparison: why sales fell is unanswerable without something to compare against, whether that is a prior period, a control group or a segment that did not fall. Predictive questions ask what will happen, and they need history long enough to contain the pattern plus an honest statement of what could break it. Prescriptive questions ask what should we do, and they are the only family that requires a judgment about cost and feasibility rather than only about data.
The common failure is asking a prescriptive question and answering it descriptively. A manager asks which product line to invest in, and receives a report on last year's sales by line, which describes the past accurately and says nothing about where investment would pay. Naming the family in the document, and saying what each family would require, is a straightforward way to satisfy aspects on approach selection, and it usually improves the question itself: many vague business concerns turn out to be prescriptive questions that nobody had stated as such.
Three questions D468 students ask
Do I need to run an actual analysis for this course?
How do I refine a vague question without inventing requirements?
What does support look like on a conceptual course?
Three CUs and the six month term
D468 is the course to take first in the analytics sequence and the one most often taken third, because tooling courses feel more urgent. Taking it early pays, since the framing habit makes every later analysis shorter and more directed. WGU terms run six months at one flat rate, so the ordering of courses inside a term is free to optimize, and this is one of the few places where sequence genuinely changes total effort. The plan page shows the sequence.
Where D468 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.