D491 Introduction to Analytics, catalog number DTAN 3100, is a two competency unit course in the WGU School of Technology and the front door of the data analytics sequence. The catalog describes it as an examination of data analytics as a discipline and the various roles within it, using data and statistical modeling to drive business value. Read that last phrase carefully, because it is the whole grading philosophy of the course. Analysis that does not end in value is a hobby. Every scored aspect here eventually asks the same question in a different costume: what decision does this change, and for whom?
A discipline course, not a tools course
Students who came to the degree for the technical work often treat D491 as an obstacle before the real courses start. That misreads it. The sequence that follows will teach you to wrangle, model and visualise, and every one of those courses assumes you already know what problem you are solving and who is waiting for the answer. This is the course where that gets installed.
Two frames carry most of the material. The first is the roles map. Data engineers move and shape data so it can be trusted. Data analysts answer defined questions from that data and communicate results. Data scientists build models that estimate or predict something not directly measured. Business intelligence developers turn recurring questions into products that answer themselves. Analytics managers and decision makers set the questions and act on answers. The boundaries blur in real organizations, and the honest version of the roles aspect says so while still being able to tell them apart by primary output.
The second frame is the value chain: a business question, the data that could inform it, the method, the analysis, the communication, and the decision. Every link can break. Most failed analytics work in industry breaks at the first link or the last, not in the middle. A submission that spends its length on method and treats the question and the audience as preamble has the weighting exactly backwards for this particular course.
Statistical modeling appears here at the level of purpose rather than mechanics. You are expected to know what a model is for, what descriptive, diagnostic, predictive and prescriptive work each answer, and when a simple summary is the right answer instead of a model. The mechanics arrive later in the sequence.
Turning scored aspects into a section plan
WGU keeps the scoring detail for each course inside your Course of Study rather than in the public catalog, so open the rubric and count aspects before drafting. Each aspect is scored on its own, and a score of 2 in each aspect passes the task. There is no averaging, so a thorough roles section will not carry a value section that never names a dollar, an hour or a rate.
Use the rubric's own nouns as headings. Introductory courses invite essay habits, and essay headings such as background and discussion make an evaluator hunt. Hunting is where aspects get scored as unmet.
The word budget, worked. Two CU courses usually carry shorter deliverables. Assume five scored aspects and directions asking for about 1,400 words. Reserve 100 for an opening that names the organization and the question, and 100 for a close, leaving 1,200 across five aspects, or 240 each. Then reweight. The aspect asking you to connect analytics to business value needs a concrete chain, so lift it to 350. The aspect asking about roles compresses well into a table plus 150 words of commentary. Definitions come down to 180. The sum still lands near 1,200 and the paper now spends its length where the marks concentrate.
A cheap pre submission test for this course: highlight every sentence that names a specific decision, person or number. If the highlighted text is under a tenth of the paper, the value aspects are probably thin.
A structure that fits an introductory analytics deliverable
Where your task directions specify headings, use theirs exactly. Where the shape is open, this arrangement keeps the discipline framing visible and each aspect easy to find.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| Organization and question | The setting and the business question stated as something a person must decide | Frames the paper; a vague question makes every later aspect vague |
| Analytics as a discipline | What analytics is, what distinguishes it from reporting, and the maturity levels | Scored on precision of the distinctions rather than length |
| Roles and responsibilities | The roles involved, their primary outputs, and who hands what to whom | Scored on handoffs; a role list with no interfaces is a glossary |
| Data and its sources | What data exists, where it lives, who owns it and how trustworthy it is | Scored on realism; invented perfect data reads as hypothetical |
| Method selection | Descriptive, diagnostic, predictive or prescriptive, and why that level fits the question | Scored on the fit argument, not on choosing the most advanced option |
| Business value | The decision that changes, who makes it, and the measure that would show benefit | The aspect that separates strong from average work in this course |
| Ethics and governance | Privacy, consent, access and the limits of the data for this use | Scored where named; keep it specific to your data rather than general |
| References | Scholarship, professional sources and any organizational documents, APA formatted | Scored where citation is named in the aspect |
Evidence craft in a field full of vendor writing
Analytics has more marketing prose written about it than almost any other technical subject, and much of that prose defines terms in whatever way suits a product. Academic work has to be stricter, and the strictness is visible in your citations.
- Cite research or a textbook for concepts and definitions. Save vendor material for claims about what a specific product does, and label it as a vendor claim.
- Use published labour market and industry sources for anything about roles or demand, and give the date, because role definitions in this field shift every few years.
- Attach a number to value wherever you can. Even a rough estimate with a stated basis beats a sentence about improved efficiency.
- Describe data provenance. Where it came from, who maintains it and how often it updates are all part of judging whether an analysis can be believed.
- Keep quotation minimal. Definitions are the most copied text in any analytics paper and WGU runs submissions through a similarity check.
- If a tool with generative capability helped you study, verify anything it produced against a real source and follow your course policy on tool use exactly.
What reads as professional rather than student work is naming the limits of the data before anyone asks. Coverage gaps, lag in updates, inconsistent definitions across systems: each is normal, and each belongs in one honest sentence rather than being discovered by the evaluator.
What separates Competent from a submission sent back
Aspects are scored independently, so a return is usually one aspect short rather than a failed paper. In D491 the usual culprit is a value section that describes benefits in the abstract.
- The business question is written as a decision, with a named decision maker.
- Every role mentioned has a primary output and at least one handoff described.
- The chosen level of analysis is justified against the question rather than by ambition.
- Value is expressed in something countable: time, cost, error rate, retention, conversion.
- The ethics section refers to this data and this use, not to data ethics as a topic.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs time and nothing else. In a six month flat rate term, though, time is the entire budget. A two CU opener is designed to close in a fortnight, and turning it into six weeks pushes a four CU course out of the term entirely.
Five mistakes that cost time in D491
- Answering with tools. Naming a platform is not a method selection, and this course is deliberately tool agnostic.
- Describing roles as job adverts. Salary and demand are context. What the rubric wants is the output each role produces and who consumes it.
- Choosing predictive analysis because it sounds advanced. If the question is what happened last quarter, descriptive is the correct answer and choosing otherwise loses the fit argument.
- Leaving value as a closing sentence. It is usually a scored aspect with its own weight, and it needs a chain rather than a claim.
- Writing about analytics in general. Every aspect gets easier when a specific organization and a specific question anchor the paper from the first line.
How support works on this course
Send the rubric from your Course of Study and the task directions. The work comes back aspect mapped, with the business question sharpened into a decision, roles described by their outputs, a method choice that argues for itself, and a value section with something countable in it. The walkthrough matters more than usual on this course, because the framing you learn here is reused in every later course in the analytics sequence.
If a proctored objective assessment sits on this course in your plan, the line is fixed. Proctored exams are yours to sit. We build the study plan, drill the definitions this material tests hardest and give an honest readiness read. We do not sit assessments and we never ask for portal credentials.
Questions students ask about D491
Is D491 the same course as DTAN 3100?
Do I need programming or statistics before D491?
Should I pick a real company for the assignment?
Starting the analytics sequence?
Send your rubric and the task directions. You get an aspect mapped draft with a real business question at the centre, plus a walkthrough that sets you up for the courses after this one.
Where D491 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.