D639 Technology for Instruction and Online Pedagogy, catalog number EDUC 5079, is the two-CU graduate technology course in the WGU Master of Arts in Teaching sequence. It covers integrating technology into teaching along with online pedagogy, feedback and collaborative learning, and it is the graduate counterpart to the undergraduate D660 (EDUC 2222). Every scored aspect in it turns on one question: what does this tool make possible that was not possible without it.
The question EDUC 5079 keeps asking
Technology coursework produces a recognisable weak submission: a competent tour of three applications, what each does, and a claim that students will find them motivating. Nothing in it is false and none of it can score well, because the aspects are not about the tools. They are about the instructional gain.
The useful framing is substitution against transformation. A document shared instead of printed is substitution: the task is unchanged and the benefit is logistical. A shared document where four students draft simultaneously and see each other's reasoning as it forms is a different task, and the technology is now doing something no paper version could. Graduate work is expected to say which of the two a given tool choice is, and to be honest when the answer is substitution, because substitution is often the right call and hiding it is what costs points.
Online pedagogy is the second strand and it has its own content. Asynchronous discussion is not classroom discussion moved online; it needs a prompt that cannot be answered in one sentence, a required interaction pattern and a moderation plan. Feedback at distance loses tone, so it needs specificity that in-person feedback can leave implicit. Collaborative work without a shared physical space needs role assignment and a visible artifact, or it collapses into one student doing the work.
The third strand, and the one candidates skip, is access. A tool that requires a personal device, a reliable connection, an account with an age minimum or an unsupported screen reader is a tool that excludes someone. Graduate plans are expected to name the barrier and say what the alternative path is.
Feedback is where the online strand becomes most technical, and it is worth planning rather than promising. Digital tools make several things possible that a paper cycle cannot: comments attached to the exact sentence they concern, a first response within minutes rather than days, automatic checks on the mechanical layer so your attention goes to the reasoning layer, and a visible revision history that lets a student see their own change over time. Each of those is a design decision with a cost attached, since faster feedback usually means shorter feedback and automated checks reward what they can measure. Saying which trade you made, and why it suits this assignment, is the difference between a feedback aspect that scores and one that restates the word timely.
Building the document from the scored aspects
Your rubric is in the Course of Study rather than the public catalog. Count the aspects first, because each is scored alone against a three-point scale with a 2 needed in each. Technology aspects often pair a selection obligation with a justification obligation, and the justification is where a tour of features fails.
Where D639 uses a performance assessment, use the rubric's nouns as headings and answer in its order. If an aspect asks how a tool supports a specific instructional goal, name the goal in the first sentence of that section. Sections that open by describing the tool tend to run out of room before reaching the instruction.
A worked word budget. Take five scored aspects and directions pointing at roughly 1,500 words. Set aside 100 words for context naming the grade, subject and delivery mode, and 80 for a close. That leaves 1,320 across five aspects, or 264 words each.
Reweight for argument. The aspect asking you to justify tool selection against a learning goal deserves 360, and the aspect on feedback or collaboration deserves 320. Descriptive aspects naming platforms or listing functions can hold at 180. Two CUs means a tight allowance, so the fastest saving is to delete every sentence describing what a well-known application does. Evaluators know what a shared document is; they want to know why yours is in this lesson.
A shape that fits a technology integration plan
Where the directions name sections, use theirs. Where they do not, this order keeps the instructional argument in front of the tool description.
| Section | What it must show | How it goes wrong |
|---|---|---|
| Instructional goal | The learning outcome the technology is meant to serve | A goal invented after the tool was chosen |
| Current limitation | What is hard or impossible without the tool | Skipped, which leaves the tool unjustified by construction |
| Tool selection | The choice, with the alternative you rejected and why | One tool presented as though no alternative existed |
| Instructional gain | Whether this is efficiency or a task that changes in kind | Efficiency claimed as transformation, which reads as overselling |
| Interaction design | Prompts, roles, timing and required outputs for online work | Post once and reply twice, with no reason behind the pattern |
| Feedback plan | What feedback is given, by whom, how quickly, in what form | Feedback described as timely without saying when |
| Access and safety | Barriers, alternatives, privacy and age or account requirements | Accessibility asserted rather than examined against the actual tool |
Write the current limitation row before naming any product. It is the row that makes every later paragraph arguable, and plans built without it read as advocacy for software.
Evidence craft when the subject is a moving target
Technology sources age quickly and vary enormously in quality, which makes selection part of the scored work.
- Prefer research on the practice over material from the vendor. A study of peer feedback quality supports your design; a product page does not.
- Cite the standards framework you are working against, quoted rather than paraphrased.
- Check the date on anything you cite about a platform, since features and privacy terms change and a stale claim reads as carelessness.
- Treat accessibility claims as checkable. If you assert a tool works with a screen reader, that assertion needs a source or a hedge.
- Keep student data considerations concrete: what the tool collects, what an account requires, and what you would use instead if a family declines.
- APA throughout, including for documentation and standards pages.
One paragraph reliably strengthens these papers: what you would do the day the technology fails. A plan with a stated fallback demonstrates that the instruction, rather than the tool, is the thing you were designing.
What separates Competent from a returned technology plan
Because each aspect is scored on its own, returns tend to name the tool that was never connected to a goal or the online activity with no interaction design.
- Every tool is preceded by the instructional limitation it addresses.
- Every claim of transformation would survive someone asking what changed about the task.
- Every online activity has a prompt, a required output and a moderation plan.
- Feedback has a stated turnaround and a stated form.
- Every access barrier has a named alternative path.
Results are recorded as Competent or Not Competent, with no letter grades and no conventional grade point average, and a performance assessment can be revised and resubmitted with nothing deducted for the revision. The cost of a return is time inside a six-month flat-rate term, where closing more courses is what lowers the effective cost per course, so a two-CU technology course is one you want to clear in days rather than weeks.
If your D639 includes a proctored objective assessment, our role is preparation only: terminology drills, scenario practice and a straight readiness answer. We do not sit assessments and never handle portal credentials.
Five mistakes that cost time in D639
- Leading with the tool. Any section that opens by describing an application has already spent its best words on the least valuable content.
- Overclaiming transformation. Substitution is legitimate. Calling it transformation invites a return that says the task did not change.
- Designing discussion without an interaction pattern. Reply to two peers is a rule, not a design, and graduate work is expected to say what the replies are for.
- Ignoring the access question. Devices, connectivity, accounts and assistive compatibility are the real constraints, and skipping them is visible.
- Citing vendor material as evidence. Marketing copy cannot support a claim about learning, and using it undercuts everything around it.
How support works on D639
Send the rubric out of your Course of Study and the task directions, with the grade, subject and delivery mode you want the plan built for. The draft comes back aspect-mapped, with each tool preceded by the limitation it addresses, an interaction design for anything asynchronous, and access barriers named with alternatives.
The undergraduate version of this material is covered on our D660 page. If your Degree Plan lists that code instead, work from there, since the expectations for citation and for the depth of the justification differ between the two levels, and building to the wrong standard wastes effort in both directions.
Three questions MAT candidates ask about D639
Is D639 the same course as EDUC 5079?
How does D639 relate to D660?
Do I need to use a specific platform for this course?
Justifying tool choices for D639?
Send the rubric and directions with your grade and subject. You get an aspect-mapped draft where every tool answers a stated instructional limitation, with interaction design and access alternatives included.
Where D639 sits in WGU's programs
The July 2026 catalog places this code in 9 current WGU programs. 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.