D822 Technology Governance appears under banner number ITEC 3011 and is worth 3 competency units. It follows the full lifecycle of governance: establishing structures, evaluating the models available, and the leadership techniques that make governance stick once it exists. D822 and ITEC 3011 identify one requirement. The course is about a question most technical people avoid, which is who has the authority to decide, and what happens when the decision is ignored.
Governance is about decision rights, not documents
Students often arrive expecting a course about policy writing. Policies are an output; the subject is who decides what, within what limits, accountable to whom. A governance structure answers questions like which decisions a project team can make alone, which need a steering group, and which reach the board. If you can express any governance arrangement as a set of decision rights and escalation thresholds, you can analyse structures you have never seen.
The distinction between governance and management is the one that shows up in scored aspects most reliably. Governance sets direction, defines what good looks like, and evaluates whether it is being achieved. Management operates within that direction. A committee that reviews whether the technology portfolio matches strategy is governing; a manager who assigns work to deliver a project is managing. Answers that blur the two look plausible and score poorly, because the aspect is usually testing exactly that boundary.
Enforcement is the third strand and the most practical. A governance model with no consequence is advisory, and advisory governance is what organizations have when they say they have governance and do not. The leadership techniques in this course, from setting expectations to making compliance visible to escalating deliberately, are what convert a structure on paper into behaviour. An assessment that asks how you would ensure adherence wants those mechanisms named specifically.
WGU assesses this as Competent or Not Competent, with no letter grades and no ordinary grade point average, and the 3 competency units size the course within a flat-priced six month term. A governance course closed in a month leaves room for something heavier in the same term at no extra cost.
Building the outline from scored aspects
If your version of D822 uses a performance assessment, the aspects are the sections and the scenario organization is your material. WGU requires a score of 2 in each aspect for a task to pass and judges each aspect on its own, so an elegant analysis of governance models will not carry an unaddressed enforcement aspect.
Do the budgeting arithmetic first. Suppose the rubric has five scored aspects and the deliverable targets about 1,900 words. Take 150 words to describe the organization, its current decision-making and the trigger for reviewing it, and 110 for a close, leaving 1,640 across five aspects, or 328 each. Weight by argument: two aspects that ask you to evaluate or recommend a model deserve 430 each, since each needs criteria, options and a decision. The three remaining aspects, which ask you to define, apply or describe, take 260. Two at 430 plus three at 260 is 1,640 exactly.
Inside each evaluation block, use a fixed order: the criterion, the option measured against it, and the consequence for this organization. Governance writing drifts into abstraction faster than almost any other subject, and forcing every paragraph to end with a consequence for the named organization is the most effective anchor available.
One further planning note. Governance aspects often include a stakeholder dimension, because a structure that ignores who has to live with it will not survive. Reserve part of your budget for naming the affected groups and what each one gains or loses, even when no aspect says the word stakeholder explicitly.
Shape for a governance assessment or proposal
D822 deliverables generally evaluate current governance and propose a structure. These proportions fit that document.
| Section | Content | Share |
|---|---|---|
| Organization and drivers | The business, its regulatory or strategic pressures, and why governance is being examined now. | 10 percent |
| Current decision rights | Who currently decides what, described as observed practice rather than as the org chart claims. | 15 percent |
| Model evaluation | Candidate governance models against stated criteria, with what each one assumes about the organization. | 21 percent |
| Proposed structure | Bodies, membership, decision rights, escalation thresholds and meeting rhythm. | 19 percent |
| Policy and standards | What must be written down, at what level of detail, and who owns each document. | 12 percent |
| Enforcement and leadership | How adherence is made visible, what happens when it is not met, and how leaders model it. | 15 percent |
| Close | Adoption sequence, the first decision the new structure should take, and how success is measured. | 8 percent |
Sourcing governance claims
Governance has published frameworks and standards, and they are the correct authority for structural claims, control objectives and maturity concepts. Cite the framework itself rather than a consultancy summary of it, and quote defined terms precisely, because governance vocabulary is exact in ways that paraphrase destroys. Where regulation is in play, the regulation or its official guidance is the source, not commentary about compliance.
Claims about behaviour and effectiveness need research rather than frameworks. If you assert that a particular structure improves alignment or reduces duplicated spending, that is an empirical claim, and it should be supported by published study or survey data with a date attached. Framework documents describe what good practice looks like; they do not by themselves prove that adopting it produced an outcome.
Be deliberate about the difference between a source and an example. Describing how a well known organization structures its technology decisions can be illustrative, but a single public example is not evidence that an approach generalises. Present examples as examples and keep the weight of the argument on criteria applied to the scenario.
Cite in whatever style your task sets out and attach every source to the sentence that depends on it. Where you propose an escalation threshold or a spending limit, mark clearly whether the number came from the scenario or whether you are proposing it, because an invented threshold presented as an existing fact is the sort of detail that unravels a section under scrutiny.
Competent governance writing and returned work
Competent submissions read as though the structure could be stood up next quarter. Decision rights are stated as who decides what within what limit, bodies have named membership rather than job families, escalation has a trigger, and enforcement has a consequence. The governance and management boundary is respected throughout.
Returns cluster into four shapes. The proposal is a set of committees with no decision rights attached, so nothing is actually governed. Enforcement is described as communication and training, which is awareness rather than enforcement. The evaluation section describes models without criteria, making the choice look arbitrary. Or the document confuses governing with managing, most often by giving a governance body operational tasks.
A second signal separates strong governance writing from adequate writing, and it costs almost nothing to add: say what your structure will feel like to someone junior. Governance is experienced from below as either a set of clear rules that make decisions faster, or as a queue that makes everything slower. Naming which one you are building, and what you did to avoid the second, tells an evaluator you understand that structures have costs as well as benefits.
The fastest self-check is to read your proposed structure and ask, for each body, what decision it can make that nobody else can. If you cannot answer for a body, it is a meeting rather than a governance mechanism and should either gain authority or be removed from the proposal.
Performance assessment work can be revised and resubmitted at WGU with no grade penalty, so submit once every aspect has a real answer. If your section carries an objective assessment as well, WGU objective assessments are proctored and our boundary does not move: we prepare with framework drills, terminology practice and a straight read on your preassessment result, and we take no part during any assessment. We never ask for or handle portal credentials.
Governance proposal all committees, no authority?
Send the D822 rubric and scenario. We convert it into decision rights, thresholds and enforcement, with word targets per aspect.
Seven mistakes that cost time in D822
- Confusing governance with management. Direction and evaluation on one side, operation on the other. Aspects test this boundary constantly.
- Committees without decision rights. If a body cannot decide something nobody else can, it is not part of a governance structure.
- Enforcement described as training. Awareness helps adoption. Enforcement needs visibility of compliance and a consequence for its absence.
- Models compared without criteria. State what a good model must do here before naming any, or the recommendation reads as preference.
- Citing summaries of frameworks. Governance vocabulary is defined precisely. Go to the framework and quote it.
- Invented thresholds presented as facts. Proposing a spending limit is fine. Presenting it as an existing policy when the scenario never said so is not.
- Ignoring who loses. Every governance change removes someone's discretion. Naming that is realism, and it is usually rewarded.
Three questions students ask about D822
Do I need to know a specific governance framework by heart?
Is D822 a policy writing course?
What does ITEC 3011 refer to?
Where D822 sits in WGU's programs
The July 2026 catalog places this code in 2 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.