WGU D372: Introduction to Systems Thinking

What D372 Actually Is, and Why It Trips People Up

D372 Introduction to Systems Thinking teaches you to look at a messy organizational problem and see the structure underneath it rather than the symptom on the surface. Instead of asking "who dropped the ball this quarter," systems thinking asks what feedback loops, delays, and unspoken assumptions keep producing the same result no matter who is in the chair. The course is built around case studies and finishes with a solution you design and defend yourself. If you see the code WMM1 attached to your assessments, that is the same course — it is the internal assessment code for D372.

Direct answer: There is no proctored test here — D372 is passed by submitting three written performance assessment tasks. Learn three tools well (the iceberg tool, systems archetypes, and the Four Steps Tool), then answer every single rubric prompt in its own clearly labeled section using one consistent case study. Students who get tasks returned almost always do so on incomplete rubric coverage, rarely on misunderstood theory.

Because the course is self-paced, your timeline is genuinely your own. The concepts themselves are approachable: causal loops, reinforcing versus balancing feedback, mental models, unintended consequences. What matters is that you can apply them to a specific case and write about them precisely. That gap — understanding a concept versus documenting it the way a rubric asks — is where nearly all the friction in this course lives.

Systems thinking earns its place in a degree plan because it is the antidote to firefighting. If you have ever watched an employer "fix" turnover with a bonus and then watched turnover return nine months later, you already have the intuition. D372 gives you vocabulary and diagrams for it, which is why it pairs naturally with courses like D081 Innovative and Strategic Thinking and D082 Emotional and Cultural Intelligence.

What the Three Performance Assessment Tasks Ask For

D372 is assessed entirely through performance assessment. Based on the published task descriptions, the three submissions break down like this:

• Task 1 — Iceberg and behavior-over-time analysis. You take a case study and work down the iceberg: the visible events, the patterns those events form over time, the underlying structures producing the patterns, and the mental models holding those structures in place. A behavior-over-time diagram accompanies the written analysis.
• Task 2 — Systems archetype analysis. You analyze the case using the systems archetypes tool and draw conclusions about the system's relationships, connections, properties, and subsystems. Identifying the archetype is only half the work; justifying the match with specific evidence from the case is the graded part.
• Task 3 — Four Steps Tool and proposed solution. You analyze a complex case study with WGU's Four Steps Tool — which is based on "Six Steps to Thinking Systemically" by Michael Goodman and Richard Karash, and which begins by completing an iceberg tool and behavior-over-time diagrams — then propose a solution and discuss its strengths, its challenges, why it beats the alternatives, and how it will affect the system. This is the culminating task and carries the most writing.

Across all three, evaluators are checking whether your diagram, your labels, and your narrative agree with each other. A beautiful causal loop diagram that your paragraphs never explain will come back for revision.

Realistic Difficulty and Time Investment

Many students report D372 as one of the lighter courses on their degree plan — commonly finished within about a week, with only a few hours of concentrated writing per task and most of the calendar time spent waiting on evaluation turnaround. That is a common pattern, not a promise, and it assumes you read the case study carefully and follow the rubric structure closely.

Plan your calendar around submission cycles rather than study hours. A practical rhythm many students describe: draft and submit Tasks 1 and 2 in the same sitting, then start Task 3 while those are in the queue. If the first evaluations come back clean, you already know your writing style matches what evaluators want, and Task 3 gets easier. If a task returns for revision, you learn exactly what is expected before you have sunk effort into the longest submission.

Budget more time than average if academic writing is uncomfortable for you, if English is your second language, or if you have never built a diagram before. The thinking is rarely the bottleneck; the precise, labeled, rubric-mapped writing is.

How to Prepare Without Wasting Days

Start with the official course material and your course instructor, not with third-party summaries. Work through the sections on the iceberg tool, causal loop diagramming, and the archetypes, then do this:

• Build the tools from memory. Close the material and sketch the iceberg's levels, then a reinforcing loop and a balancing loop, on blank paper. Active recall of a diagram is far more useful here than rereading it.
• Practice on your own life first. Apply the iceberg to something you know intimately — commute traffic, a chronically late team, credit card debt. Once you can name the mental model behind a familiar mess, the case studies stop feeling abstract.
• Space it out. Two or three short sessions across a few days beat one marathon night, particularly for the archetypes, which blur together when crammed. Revisit them briefly the morning before you draft Task 2.
• Turn the rubric into your outline. Copy each rubric prompt into your document as a heading and write beneath it. Headings that mirror rubric language make the evaluator's job obvious and your revisions rare.
• Attend a cohort or webinar if one is offered. Watching an instructor mark up a sample analysis is the fastest way to calibrate how much depth "explain" actually requires.
• Reuse one case study across tasks where the instructions permit it. Deep familiarity with a single scenario is worth more than shallow acquaintance with three.

If writing structure is your weak point generally, the habits taught in D339 Technical Communication transfer directly to these submissions.

Mistakes That Send D372 Tasks Back for Revision

The failure modes in this course are remarkably consistent:

• Staying at the event level. Describing what happened in the case without ever reaching structures and mental models is the single most common shortfall on Task 1.
• Naming an archetype without proving it. Asserting that a case is a particular archetype is not analysis; showing the short-term fix, the delay, and the returning symptom is.
• Diagrams without labels or direction. Loops need labeled variables and indicated polarity, and a reader should be able to follow the story around the loop without your help.
• Answering the prompt you remember instead of the one written. Rubric wording is specific, and skim-reading it costs a full revision cycle.
• Skipping half of Task 3's discussion. That task asks for strengths, challenges, comparison to alternatives, and system impact. Miss one and the submission is incomplete regardless of how good the solution is.
• Uncited or borrowed material. Every submission is originality-checked. Use the case study and the course text, cite properly, and write in your own words — recycled study-bank text is an academic integrity problem, not a shortcut.
• Switching cases mid-paper. Consistency across a task is part of coherence, and evaluators notice immediately.

D372 Readiness Checklist

• Can you draw the iceberg tool's levels from memory and give an example at each level for your case?
• Can you construct a behavior-over-time diagram and explain in words what its shape reveals?
• Can you distinguish a reinforcing loop from a balancing loop and label polarity correctly?
• Can you name several systems archetypes and describe the story shape of each?
• Can you justify your archetype choice using specific evidence from the case rather than assertion?
• Can you walk through the Four Steps Tool without looking at the template?
• Can you state a proposed solution that targets a structure or mental model, not just an event?
• Have you addressed your solution's strengths, challenges, advantages over alternatives, and system impact?
• Have you mapped every rubric prompt to a labeled section in your document?
• Have you checked citations and formatting against the task's stated requirements?

D372 FAQ: Questions Students Actually Ask

Is D372 an objective assessment or a performance assessment?

It is a performance assessment course. There is no proctored multiple-choice exam — you submit written tasks with diagrams, and an evaluator scores them against a rubric.

How long does D372 usually take?

Many students report finishing within about a week. Much of that elapsed time is waiting on evaluation results rather than working, so the number of hours you actually spend writing is typically far smaller than the calendar span suggests.

How hard is D372 compared with other courses?

Student consensus places it on the easier end. The concepts are intuitive; the effort goes into precise, rubric-aligned writing and properly labeled diagrams.

What is the Four Steps Tool based on?

WGU's Four Steps Tool draws on "Six Steps to Thinking Systemically" by Michael Goodman and Richard Karash. In practice you begin by completing an iceberg tool for the case and drawing behavior-over-time diagrams, then move through the remaining steps toward a proposed solution.

Why do my assessments say WMM1 instead of D372?

WMM1 is the assessment code attached to this course. If your portal shows WMM1 task pages while your degree plan shows D372, you are in the right place.

Can I submit all three tasks at once?

You can, but staggering is usually smarter: send Tasks 1 and 2 first, use the evaluator feedback to calibrate your depth and formatting, then finish Task 3 with that guidance in hand.

Browse more School of Business guides or the full study guide index to plan the rest of your term.