D435 HR Technology and People Analytics, catalog number MHRM 6020, is worth three competency units in the WGU School of Business. The catalog describes it as human resource information systems and people analytics used for HR insight and support. Those are two disciplines sharing a course, and they fail in opposite directions. Technology work fails by describing software instead of requirements. Analytics work fails by producing a chart instead of a decision. Graduate scoring in this course is mostly a test of whether you can stay on the decision side of both.
Two disciplines, one rubric
The technology half of MHRM 6020 is not a product review. Vendor comparison tables are easy to build and easy to score low, because a table of features says nothing about whether the organization needs them. What earns marks is requirements work: what processes exist today, where the data lives, which handoffs break, what has to integrate with payroll and finance, who administers the system after go live, and what the organization is willing to change about itself to fit a package.
The analytics half has its own trap, and it is the chart. A dashboard with eight tiles of turnover data is descriptive work, which is the lowest rung of the analytics ladder and the one most submissions stop on. The ladder runs from description, meaning what happened, to diagnosis, meaning why it happened, to prediction, meaning what is likely next, to prescription, meaning what to do. Graduate rubrics in this space usually want you at least at diagnosis and often at prescription, and they want the reasoning that got you there.
The third thing the course tests, and the one students underestimate, is restraint. People analytics operates on data about human beings who did not volunteer to be studied. Every serious treatment of the field includes consent, minimisation, retention limits, access control and the question of which decisions should never be automated. An analysis that is technically sound and ethically silent will lose an aspect in almost any graduate rubric that mentions ethics or governance.
Turning scored aspects into a section plan
WGU keeps the scoring detail inside your Course of Study rather than the public catalog, so open the rubric and count aspects before you draft. Each is scored on its own and a score of 2 in each aspect passes the task. Nothing averages, which in a two subject course means a strong systems section cannot rescue an analytics section that stops at a bar chart.
Use the rubric's own nouns as headings, and resist the urge to write one flowing narrative about a project. Systems requirements, vendor evaluation, implementation, data quality, analysis and ethics are usually separate aspects, and each needs a heading an evaluator can land on directly.
The word budget, worked. Suppose the rubric shows six scored aspects and the directions ask for about 2,200 words. Reserve 150 for a problem statement and 100 for a close, leaving 1,950 across six aspects, or about 325 each. Then rebalance. The analysis aspect needs a method description plus results plus interpretation, so lift it to 500. The ethics and governance aspect needs specifics rather than sentiment, so give it 350. Requirements and vendor evaluation both compress to 250 when they are written as criteria rather than as prose. The arithmetic still holds.
A quick pre submission check that catches most thin work: for every chart or table in the document, find the sentence that says what decision it supports. If there is no such sentence, the visual is decoration and the aspect is at risk.
A structure that fits an HR technology and analytics deliverable
Where the task directions give headings, use theirs without adjustment. Where they leave the shape open, this arrangement keeps the two halves distinct and keeps every aspect findable.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| Problem statement | The HR question or process pain that started this, stated as a decision someone needs to make | Frames everything; a technology paper with no decision in it drifts into product description |
| Current state | Processes, systems, data sources, owners and the breaks between them | Scored on specificity; generic process description earns little |
| Requirements | Functional and non functional needs, prioritised, with the reason each exists | Scored on traceability back to the current state problems |
| Solution evaluation | Options compared against your own criteria, including the option of changing process instead of software | Scored on consistent criteria, not on the number of vendors |
| Data foundation | What data exists, its quality, its definitions, and what would have to be fixed first | Scored where the rubric names data quality; the section students skip |
| Analysis | The question, the method, the result, and what it means in plain language | Scored on reasoning; a result with no interpretation is an unmet aspect |
| Ethics and governance | Consent, access, retention, bias risk and the decisions that stay human | Scored on specificity to your analysis rather than general principles |
| Implementation and adoption | Sequence, owners, training and how you will know it worked | Scored on plausibility given the organization you described |
| References | Scholarship, vendor documentation and regulatory material, APA formatted | Scored where citation is named in the aspect |
Evidence craft when the subject is data about people
This course has a source hierarchy worth learning once. Peer reviewed research supports claims about what analytics can predict. Vendor documentation supports claims about what a product does. Neither supports the other, and swapping them is a frequent cause of lost citation aspects.
- Define every metric before you use it. Turnover, headcount, tenure and absence all have several defensible definitions, and comparisons across definitions are meaningless.
- Name the population and the period for every figure. An analysis of turnover without a denominator and a window is not an analysis.
- Separate correlation from cause explicitly. Engagement scores and retention move together for many reasons, and a prescriptive recommendation built on correlation alone needs that caveat in writing.
- State data quality honestly. Missing records, inconsistent job codes and manual entry errors are normal, and describing them strengthens rather than weakens the paper.
- Use aggregate figures and suppress small cells. Reporting a metric for a group of three people identifies those three people.
- Cite vendor claims as claims. Write that the vendor states a capability, with the documentation cited, rather than asserting the capability yourself.
What reads as graduate work here is naming the limit of your own analysis. Sample size, single site data, a period distorted by one reorganisation: each of these is a real constraint, and stating it plus what a better dataset would change is the difference between an analyst and a person with a spreadsheet.
What separates Competent from a submission sent back
Aspects are scored one at a time, so returns are usually narrow. In this course the most frequent single cause is an analysis that reports a figure and never says what the organization should do differently because of it.
- Every requirement traces to a specific problem in the current state description.
- The evaluation criteria are stated before the options, and every option is judged against all of them.
- Each metric has a written definition and a named source system.
- The analysis ends in a recommendation someone could act on this quarter.
- The ethics section names the specific risk in this specific analysis rather than reciting principles.
Performance assessment work at WGU can be revised and resubmitted without a grade penalty, so a return costs time only. In a six month flat rate term, though, a two week rework is two weeks not spent on the next course, and this is a course where a single missing definition can trigger that rework.
Six mistakes that cost time in D435
- Comparing vendors before writing requirements. Criteria chosen after seeing the options are criteria shaped by the options, and evaluators notice.
- Reporting descriptive statistics and calling it analytics. Description is where analysis starts, not where it stops.
- Treating a dashboard as a deliverable. A dashboard is a tool for a recurring question. Say what question and how often it is asked.
- Ignoring data quality. Every real HR dataset is messy, and a paper that implies otherwise reads as hypothetical.
- Recommending predictive scoring of individuals with no governance. Flight risk scoring is a serious intervention, and any recommendation to use it needs access rules and a human decision point attached.
- Writing an implementation plan with no owners. Tasks without names are intentions, and adoption aspects are scored on realism.
How support works on this course
Send the rubric from your Course of Study, the task directions and any dataset or scenario you have been given. The work comes back aspect mapped: requirements traced to problems, options judged against stated criteria, metrics defined before they are used, an analysis that reaches a decision, and a governance section written about your specific analysis rather than about ethics in general.
If a proctored objective assessment sits on this course, the boundary does not move. Proctored exams are yours to sit. We prepare only: revision plans, drilled metric definitions, practice interpretation and an honest go or wait read. We never sit assessments and we never ask for portal credentials.
Questions students ask about D435
Is D435 the same course as MHRM 6020?
Do I need to know statistics or a programming language?
Can I use my employer's real HR data?
Stuck between the systems half and the analytics half?
Send your rubric and your dataset or scenario. You get an aspect mapped draft where the analysis reaches a decision and the governance section is about your actual analysis.
Where D435 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.