D356 carries the banner number HRM 3540 and is worth 3 competency units. The WGU catalog frames it as human resource information systems, digital tools and the analytics that improve HR decision making. It sits at an unusual junction for a business course: half of it is systems thinking and half of it is data reasoning, and students who are comfortable with one half often assume the other half is optional. The assessments do not agree.
Two questions hiding inside one course
Every deliverable in this subject is a version of one of two questions. The first is a selection or implementation question: this organization needs a system, which one, on what criteria, integrated with what, at what risk. The second is an analytics question: here is HR data, what does it say, and what should a manager do about it.
Those questions need different skills. Selection is about requirements, evaluation criteria, weighting, vendor claims and change management. Analytics is about knowing which measure answers which question, what the measure hides, and how confidently a conclusion can be stated from the data you have. Read your task instructions with that split in mind and you will know immediately which half of your preparation matters.
There is also a third strand running under both: data governance. HR data is among the most sensitive an employer holds, so any system recommendation or analytics proposal that ignores access control, retention, consent and privacy obligation has left an aspect unaddressed. In a technology course, that section is not decorative.
WGU marks the outcome Competent or Not Competent, with no letter grades and no ordinary grade point average behind it. Performance assessment work can be revised and resubmitted without a penalty attached to the result, so a complete attempt that commits to a recommendation beats a cautious one that describes options without choosing.
Turning scored aspects into an evaluation document
If your course is assessed by a performance assessment, the aspects your evaluator scores are the plan. Each is judged alone and needs a score of 2, and in a technology deliverable the risk is that a matrix or dashboard swallows two aspects that then never appear in prose.
Run the arithmetic in a way that respects the artefacts. Suppose the rubric shows six scored aspects and the prompt asks for a recommendation of about 2,000 words including a comparison matrix. Give the matrix and its explanation 350 words, since a matrix with no interpretation cannot be scored, and hold 200 for the organizational context and 100 for the close. That leaves 1,350 across six aspects, or 225 words each.
Now check which of the six aspects the matrix is supposed to satisfy. If it covers two of them, those two still need their own prose paragraph pointing at the matrix and stating the conclusion drawn from it, at maybe 120 words each, and the 210 words you free up should go to the aspects asking you to justify the recommendation or address risk. Artefacts support aspects; they rarely satisfy them alone.
A structure for an HR technology deliverable
The dominant genre here is a system evaluation and recommendation written for an HR director or an executive sponsor. The order below is the one decision makers expect.
| Section | Its job | Form | Common gap |
|---|---|---|---|
| Problem statement | The HR process failing today and what it costs | Prose with a number | Buying technology to solve an unnamed problem |
| Requirements | Must have and nice to have capabilities, separated | Numbered list | Requirements written as product features rather than needs |
| Evaluation criteria | How options will be judged and how criteria are weighted | Weighted criteria table | Criteria invented after the preferred option was chosen |
| Option comparison | Two or three realistic options scored on the criteria | Comparison matrix | A straw option included only to lose |
| Recommendation | The choice and the reasoning that produced it | Prose | A recommendation the matrix does not support |
| Data governance | Access, retention, privacy obligation and security | Short structured section | Missing, which is a routine cause of returns |
| Implementation | Phases, data migration, training and cutover | Phased timeline | A timeline with no owners or dependencies |
| Measures of success | What will be true in six months if this worked | Metric table with baselines | Metrics with no baseline, so change cannot be shown |
Evidence craft when vendors write most of the literature
The sourcing problem in this subject is sharp: most published writing about HR technology is produced by companies selling HR technology. That does not make it useless, but it does make labelling compulsory. When you cite a vendor, say it is the vendor. When you cite an analyst firm, say the report is commercial research. When you cite a case study published by a supplier about its own customer, treat it as a claim rather than as evidence.
Balance that with independent material. Peer reviewed information systems research gives you the reasons technology implementations succeed or fail, which is the strongest possible support for the implementation and change management sections. Data protection regulators and standards bodies publish the actual obligations behind your governance section, and citing the source beats citing a summary. Government statistical sources give you workforce numbers when your analytics section needs a denominator.
Where your deliverable includes analysis of a dataset, describe the data before interpreting it: what it covers, what period, how many records, and what it cannot tell you. That paragraph is often the difference between an analytics aspect scored as competent reasoning and one scored as an overreach.
What earns Competent, and what comes back
Passing work is decided. It names a problem, sets criteria before comparing options, applies the criteria visibly, and recommends. It says what could go wrong and what would be done about it. It treats employee data as something with obligations attached.
Returns cluster in four places. Criteria that appear after the conclusion, which an evaluator can spot from the weighting. Analytics that state a correlation as a cause. A governance section that says data will be kept secure without naming a control or an obligation. And the perennial one, an implementation plan with no sequence, no owner and no dependency, which cannot be assessed for feasibility however good the product choice was.
There is a fifth pattern peculiar to technology writing, which is the paper that describes capability instead of fit. A submission can spend two pages accurately explaining what an applicant tracking system does, what a learning management platform does and what a payroll integration does, and still score badly, because none of that describes this organization. The aspects in a selection task are almost always written around suitability: why this capability matters to an employer of this size, in this sector, with this problem, and what it would cost them not to have it. Rewriting a capability paragraph into a fit paragraph is usually a matter of adding two sentences, one naming the organizational condition and one naming the consequence, and it converts descriptive text into scoreable analysis without lengthening the document.
Watch the requirements section for the same reason. Requirements written as product features, single sign on, mobile app, custom reporting, tell an evaluator what you have seen advertised. Requirements written as needs, managers must approve time off from a phone because half the workforce has no desk, tell an evaluator that you understood the organization first and shopped second. The second version also makes the comparison matrix write itself, because each criterion already carries the reason it exists.
Five mistakes that cost time in D356
Choosing the system first. Requirements written to fit a favourite product are visible immediately in the criteria weights.
Confusing a metric with an insight. Time to fill is a number. Time to fill rising because one team stopped using structured interviews is an insight.
Ignoring integration. HR systems live beside payroll, finance and identity management, and a recommendation that never mentions the interfaces is incomplete.
Treating privacy as a footnote. Access control, retention and lawful basis belong in the recommendation itself, not in a closing sentence.
Presenting a dashboard with no question. Every chart should answer a question a manager actually asked, and saying which one is usually worth its own aspect.
What we do, and what we will not do
Our work is the written deliverable and the reasoning behind it: rubric mapping, aspect budgeting, drafting a model evaluation or analytics report you can study and rewrite in your own voice, and turning a returned evaluation into a specific edit list. We do not access any employer system, and we do not want your organization's real HR data; where a task needs data, we work with what your prompt supplies or with public sources. If D356 carries an objective assessment for you, that exam is proctored and our role is preparation only. We are never present during an assessment, never take one for a student, and never ask for or handle WGU portal credentials.
Comparing systems for D356?
Send the scenario, the task instructions and the rubric. We come back with the criteria set, the matrix shape and a straight read on whether your recommendation follows from your own analysis.
Three questions students ask about D356
Do I need technical skills to pass an HR technology course?
Can I name real vendors in my recommendation?
How do I write the analytics part without a statistics background?
Where D356 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.