WGU D473 Task 1 Guide: How to Identify Root Cause Variables Using Data Analysis

WGU D473 Task 1

D473 Task 1 asks you to analyze operational data, identify the variables contributing to supply chain service and cost problems, determine their root causes, and communicate evidence-based recommendations. This guide explains the analytical process behind the task so you can confidently complete it using your own data.

Task Overview

Part A

Analyze the Endothon case and supporting data to identify variables affecting supply chain performance and explain their root causes using evidence.

Part B

Develop an executive presentation that includes:

• Project charter
• Findings
• Recommended solutions
• Implementation tasks
• KPIs
• Monitoring strategy

Understanding the Capstone

D473 simulates real operations-management work: you’re handed a business case and a data workbook, and asked to figure out what’s actually driving a company’s service and cost problems — not to guess, but to prove it with data.

This task exists because WGU wants to see whether you can do what an operations manager actually does: take messy, real-world data, find the variables that matter, and justify your conclusions well enough that a skeptical executive would sign off on them. That’s a different skill than memorizing a formula — it’s judgment under ambiguity, backed by evidence.

Why Operations Managers Use Root Cause Analysis

Root cause analysis helps organizations solve recurring operational problems instead of repeatedly treating symptoms. Companies use it to reduce costs, improve customer service, optimize logistics, and make better strategic decisions.

Examples include:

• Reducing shipping delays.
• Improving warehouse efficiency.
• Lowering inventory costs.
• Increasing customer satisfaction.

What the Evaluators Are Looking For

Task 1 isn’t graded on whether you picked the “right” variable in some abstract sense — it’s graded on whether your chosen variable is measurable, data-backed, and directly tied to the specific problem (service performance in one sub-task, cost in another).

Concretely, evaluators are checking:

• Did you identify a variable with a clear, quantifiable effect — not a vague theme like “communication issues”?
• Did you pull the actual numbers from the workbook to support it, rather than asserting it?
• Does your cause-effect table trace a logical chain from root cause to the variable, rather than restating the symptom?

Understanding the Business Problem — Before You Touch the Spreadsheet

The single most common mistake in Task 1 is opening the data file first and hunting for something that looks interesting. That produces scattered, hard-to-defend conclusions. Instead, read the business case first and get clear on a few concepts:

• Supply chain network — the sequence of suppliers, facilities, and transportation that gets a product from raw material to customer
• Lead time — the time between an order being placed and it being fulfilled; longer lead times usually show up as a service problem
• Network efficiency — how well the system uses its resources (transportation, warehousing, labor) relative to output
• Operational cost — the ongoing cost of running the network, separate from one-time investments
• Root cause vs. symptom — a symptom is what you observe (late deliveries); a root cause is what’s actually producing it (a single distribution hub serving too wide a region, for example)

Only once these are clear should you open the workbook — you’ll know what you’re looking for instead of scrolling for something that “seems off.”

How to Analyze the Data — A Repeatable Process

Use this sequence on any operations-analysis workbook, not just this one:

1. Understand every worksheet. Skim each tab before analyzing anything — know what data exists before deciding what’s relevant.
2. Identify available variables. List every measurable field: delivery times, order volumes, costs by category, location, dates.
3. Calculate descriptive statistics. Averages, ranges, and totals per category reveal patterns a single number can’t.
4. Look for unusual values. Outliers often point directly at the source of a problem.
5. Compare across locations or categories. If one facility, region, or product line looks different from the rest, that’s a lead worth chasing.
6. Identify trends over time. A problem that’s worsening month over month tells a different story than one that’s been constant.
7. Validate your conclusion. Before finalizing, ask whether the data could support a different explanation — a defensible answer survives that question.

Questions Every Operations Manager Should Ask

• • Which metric changed the most?
  • Is the change consistent over time?
  • Does the pattern appear across multiple locations?
  • Is correlation enough, or should I investigate further?
  • Could another variable explain the same outcome?

Understanding Variables

Task 1 expects you to work with these distinctions cleanly:

• Independent variable — the factor you believe is driving the outcome (e.g., distance from distribution hub)
• Dependent variable — the outcome being affected (e.g., delivery time)
• Operational metric — measures of process performance (throughput, cycle time)
• Service metric — measures of customer-facing outcomes (on-time delivery rate, fulfillment accuracy)
• Cost metric — measures of financial impact (transportation cost per unit, inventory holding cost)

How to Identify the Service Problem

Rather than scanning for “the answer,” ask targeted questions of the data:

• Which variable correlates most consistently with longer customer wait times?
• Which variable shows the widest gap between best- and worst-performing locations?
• Which variable, if it changed, would most plausibly move the service metric?

Identifying Cost Drivers

Common categories worth checking systematically in any supply-chain cost analysis:

• Transportation (fuel, freight, distance)
• Inventory (holding costs, stockouts, overstock)
• Warehousing (facility costs, utilization)
• Labor (overtime, staffing levels)
• Packaging
• Order frequency and batch size

Cause-and-Effect Analysis — Worked Example (Fictitious Company)

To demonstrate the technique without reusing any real assignment data, here’s a walkthrough using a fictitious company, Solace Sealants, a mid-size manufacturer of adhesive and sealant products distributed through regional hardware retailers.

Symptom observed: Solace Sealants’ western region shows a 22% longer average delivery time than its eastern region, based on fictitious order data.

Applying the 5 Whys:

1. Why are western deliveries slower? → Orders route through a single regional warehouse before reaching retailers.
2. Why does routing through one warehouse slow things down? → That warehouse serves a larger geographic area than any other in the network.
3. Why does it serve a larger area? → No second warehouse was added when the western customer base grew.
4. Why wasn’t a second warehouse added? → Network capacity planning hasn’t been revisited in several years.
5. Why hasn’t it been revisited? → No recurring process exists to reassess network design against demand growth.

Root cause identified: Outdated network design relative to current regional demand; not, for example, “poor warehouse staff performance,” which would only address a symptom.

Cause-effect table structure:

This structure — symptom, root cause, and the logical chain connecting them — is what your own Task 1 table needs, built from your actual assigned data rather than these fictitious figures.

Notice that each “Why?” moved one level deeper into the organization’s processes rather than blaming people. Effective root cause analysis focuses on systems and processes because those are the areas managers can improve sustainably.

Common Mistakes to Avoid

• Using opinions or assumptions instead of data pulled directly from the workbook
• Confusing a symptom (late deliveries) with a root cause (network design)
• Choosing a variable that’s interesting but not clearly tied to the specific problem (service vs. cost)
• Weak or missing quantitative justification — a claim without a number attached won’t hold up

Key Takeaways

Before moving to Task 2, make sure you can:

✓ Explain why your chosen variables influence the business problem.

✓ Support every conclusion with quantitative evidence.

✓ Distinguish symptoms from underlying causes.

✓ Communicate recommendations as if presenting to senior leadership.

Remember, successful managers don’t simply identify problems—they explain why those problems exist and recommend practical solutions supported by evidence.

References & Further Reading

• ASQ (American Society for Quality) — the Fishbone (Ishikawa) Diagram overview and root cause analysis / problem-solving resources explain the origins and structured use of cause-and-effect analysis referenced above.
• ASCM (Association for Supply Chain Management) — their supply chain management overview is a widely cited industry source for the supply-chain terminology used in this guide.
• CSCMP (Council of Supply Chain Management Professionals) — maintains a glossary of standard supply chain and logistics definitions, useful for cross-checking terminology.
• PMI (Project Management Institute) — the authoritative body behind the PMBOK Guide, whose project charter guidance informs the components covered in the Task 2 companion guide.