Western Governors University

E008: Technology Management

A guide to WGU's course on managing and troubleshooting technology systems by diagnosing, prioritizing and resolving technical issues.

Updated October 2026 · 5 min read

E008, Technology Management, is a course in WGU's Information Technology degree. WGU's description says it provides the knowledge and skills needed to manage and troubleshoot technology systems within an organization, and to diagnose, prioritize and resolve technical issues.

WGU's public materials give limited detail beyond that summary, so check your course page for the current competencies and assessment. Students generally find that the course rewards a disciplined method: clear problem statements, evidence for a cause, sensible priorities and documented resolution.

Course at a Glance

ItemDetails
UniversityWestern Governors University (WGU)
Course codeE008 (codes may be updated; guides list titles)
LevelUndergraduate
Competency units3 in the program guide
PrerequisitesNone stated in WGU's description
FormatCompetency-based

What the Course Covers

Skill (from WGU's description)What it means in practice
Manage technology systemsKeeping systems running, documented and aligned with needs
Troubleshoot technology systemsFinding the cause of faults in a structured way
Diagnose issuesGathering evidence and narrowing possible causes
Prioritize issuesDeciding what to fix first based on impact and urgency
Resolve issuesApplying, testing and recording the fix

Key Concepts Explained

A Troubleshooting Method

A reliable approach: identify the problem, gather information, form a theory, test it, plan and apply a fix, verify the system works and document what you did. Following the same steps every time makes your reasoning easy to assess.

Example: Staff report they cannot reach a shared drive. Evidence: only one office is affected, other services work, and a switch was replaced yesterday. Theory: a configuration error on the new switch. Test: compare its settings with the working one. Fix: correct the setting. Verify: staff can connect. Document: cause, fix and a note to check configuration after hardware changes.

Prioritizing with Impact and Urgency

Many organizations rank incidents by how many people are affected (impact) and how soon harm grows (urgency). A system outage for all customers outranks a cosmetic fault for one user.

Documentation

Records let others reproduce a fix and spot patterns. Include time, symptoms, steps, outcome and follow-up actions.

Typical Assessment Tasks and How to Approach Them

The exact assessment depends on your course version. Tasks in this area commonly ask for the following:

Task typeWhat it testsHow to approach it
Diagnose a scenarioMethod and evidenceState symptoms, causes considered and why you chose one
Prioritize a set of issuesImpact and urgency judgmentUse a simple matrix and justify the order
Resolution planPractical stepsList the fix, test, rollback and communication
DocumentationClear recordsUse a consistent template

A Priority Matrix

ImpactUrgency highUrgency low
HighFix immediatelySchedule soon
LowFix when practicalLog and review

Linking to Service Management Ideas

Technology management in organizations is often shaped by service management practice. You may meet terms such as incident, problem and change. Check whether your course uses them.

TermMeaning
IncidentAn unplanned interruption or drop in service quality
ProblemThe underlying cause of one or more incidents
ChangeA planned modification to a system
WorkaroundA temporary way to keep working until the cause is fixed

Separating the quick fix from the root-cause fix is a point many rubrics reward.

A Simple Incident Record

  1. Date, time and who reported it.
  2. Symptoms and systems affected.
  3. Impact and urgency rating.
  4. Steps taken and results.
  5. Resolution, verification and follow-up.

Worked Prioritization

Three tickets arrive together: the email system is down for the whole company, one user's monitor flickers, and the finance team's report tool is slow before month-end close.

The email outage has high impact and high urgency, so it comes first. The finance tool is high urgency for a smaller group, so it is next. The monitor is low impact and can be scheduled. Writing the order and the reasons in a table is exactly the kind of evidence a rubric rewards.

Where Students Get Stuck

Study Tips for E008

How We Help with E008

Send the task, rubric and evaluator comments. A writer can prepare a custom answer, explain the method or review your draft.

GradeEssays is independent and not affiliated with Western Governors University. Our work is a study and reference aid; you complete and submit your own work under WGU's academic integrity policy, and we never take assessments or access student accounts.

Orders are written from scratch, include free revisions within the scope of your original request and are refunded in full if late.

Get Clear on Your E008 Task

Share the instructions, rubric and feedback. We prepare a custom answer that shows your reasoning step by step.

Start My E008 Help

Free revisions · Full refund if late · Written from scratch for your order

Frequently Asked Questions

What is E008 about?

WGU describes Technology Management as providing the knowledge and skills to manage and troubleshoot technology systems, diagnosing, prioritizing and resolving technical issues.

Are there prerequisites?

WGU's public description does not state any. Check your degree plan.

How is it assessed?

The format depends on your course version. Check your course page for the current assessment and rubric.

What is a good troubleshooting method?

Identify the problem, gather information, form and test a theory, apply a fix, verify and document.

How do I prioritize issues?

Weigh impact and urgency, and explain the order.

Will you complete my assessment?

No. We never take assessments or access accounts. We provide custom answers and feedback.