D372 Introduction to Systems Thinking, catalog number PHIL 1030, is a three-CU general education course teaching a holistic, systems-based approach to analysing complex problems and the solutions people propose for them. It is the base course in a family of three: D372 is the general version, D458 Introduction to Systems Thinking for Health Professionals carries PHIL 1031, and D459 Introduction to Systems Thinking and Applications carries PHIL 1032. Check your Degree Plan before you borrow anyone's notes, because the three codes are not interchangeable. If your plan says D372, this page is the one you want.
What PHIL 1030 is actually training you to do
Systems thinking is one of the few general education subjects that changes how you argue rather than what you know. The whole course is built on a single move: stop asking what caused this, and start asking what structure keeps producing this. Those are different questions with different answers. A linear question about a hospital's readmission rate produces a list of blameable parties. A systems question about the same rate produces a set of connections that would keep producing readmissions even if you replaced every person in the building.
Most courses in this area teach three layers of seeing. The surface layer is events, which is what the news reports. Below it are patterns, what the same events look like plotted over time. Below that is structure, the arrangement of parts and rules that makes those patterns close to inevitable. Writing at the event layer produces a summary. Writing at the pattern layer produces a report. Only the structure layer produces analysis, and analysis is what a systems course scores.
The working vocabulary is small and you should learn it early because everything else rests on it. Elements and connections and purpose. Boundaries, which is the decision about what your analysis will treat as inside the system and what it will treat as outside. Interdependence, which is why a change in one place surfaces somewhere unrelated. Feedback, both the reinforcing kind that amplifies whatever is already happening and the balancing kind that pulls a value back toward a target. Delay, which is why sensible interventions look like failures for a while and get abandoned just before they work. And leverage, the observation that the spots where a small change produces a large effect are rarely the spots people instinctively push. Your course materials will have their own phrasing, so use the wording your Course of Study uses rather than mine.
Turning scored aspects into a section plan
WGU publishes the scoring detail for a course inside your Course of Study rather than in the public catalog, so the first thing to do in D372 is open yours and count what is actually being judged. Each aspect is scored on its own against a three-point scale, and a score of 2 in each aspect passes the task. Nothing averages out, which is why a beautifully written analysis with one missing element still comes back.
Where there is written work, the aspect list is your outline. Give each scored aspect a heading in the rubric's own words rather than in a heading you invented, so that the evaluator can score by reading down the page instead of hunting.
The word budget, worked. Systems papers should be budgeted by loop rather than by section, because a feedback loop that is only half described is worth nothing at all. Say the directions ask for roughly 2,000 words and your analysis rests on three feedback structures. Every loop needs four moves to count: the variables in it, the direction of each link between them, the behaviour that loop produces over time, and the evidence that the loop is real rather than assumed. Four moves at around sixty words each is 240 words per loop, so three loops is 720 words that cannot be compressed. Add roughly 200 words for the boundary statement, because an analysis that never says what it excluded is an analysis nobody can check. Add 250 for the leverage discussion, which is the section evaluators read hardest. That is 1,170 words of load-bearing content inside a 2,000-word budget, leaving about 830 for the problem description, transitions and the closing.
Run that arithmetic before drafting and something usually becomes obvious: most students planning a 2,000-word systems paper have planned roughly 1,400 words of problem description and 600 of analysis, which is backwards. The problem statement is context, and 250 words is generous for it. If your account of the situation runs longer than your account of the structure producing it, cut the description.
A structure that fits a systems analysis
Where your task directions set out their own arrangement, those directions win. Where they do not, this order matches the way systems work is usually judged.
| Section | What belongs in it | How it gets scored |
|---|---|---|
| The problem, stated as behaviour | What is happening, to what measure, over what period, expressed as a trend rather than an incident | Scored for framing a system problem rather than an event; a single anecdote here undercuts everything after it |
| Boundary | What you are counting as inside the system, what is outside, and why you drew the line there | Scored wherever scope appears in the aspect wording, and read as rigour even where it is not |
| Elements and connections | The actors, resources and rules in play and how each one touches the others | Scored for completeness; a missing actor who obviously matters is the easiest return an evaluator can write |
| Feedback structure | Each loop named, with its variables, link directions and the behaviour it produces | The core aspect in most systems tasks; half-described loops score as unmet |
| Delays and unintended effects | Where response lags behind action, and what a plausible fix would break elsewhere | Scored for foresight; this is where a competent paper separates from a tidy one |
| Leverage and proposed change | Where to intervene, why there rather than the obvious place, and what evidence would show it worked | Scored for being specific and testable; a general call for better communication scores nothing |
| Sources | Data for the trend, sources for the claims, APA formatted | Scored wherever citation is named; unsourced numbers in a systems paper read as invented |
Where the directions allow a diagram, draw one, then write the prose so it stands alone without the diagram. A causal loop diagram earns nothing on its own if the reader has to infer the argument from arrows, and an evaluator scoring an aspect needs the claim in sentences.
Evidence craft when your evidence is a real situation
The evidence problem in a systems course is that the interesting claims are about behaviour over time, and that is exactly what people report as opinion. Strong submissions stay strict about the difference between what was measured, what was reported, and what the writer inferred.
- Give the trend a source and a period. Rising complaints is an impression. A complaint count for six consecutive quarters with a citation is evidence, and it is what makes a pattern claim defensible.
- Mark inference as inference. Write plainly that the data shows one thing and that you are inferring a connection from it. Evaluators penalise unmarked leaps far more often than they penalise cautious ones.
- Use anecdote for illustration only. One story can show a reader what a loop feels like from inside. It cannot establish that the loop exists.
- Cite the systems concepts you borrow. If you are using an established idea about leverage or archetypes, attribute it. General education courses score citation, and unattributed frameworks are easy to spot.
- Prefer public, checkable sources over internal ones nobody can verify. If you use workplace knowledge, label it as your own observation.
- Keep identifying detail out. A systems analysis of your employer does not need named colleagues, and a paper about a real service does not need a real patient in it.
One move separates the strongest gen-ed systems writing: stating what would falsify your own analysis. Naming the observation that would show your proposed loop is not really operating reads as intellectual honesty and, more practically, it shows an evaluator that you understand a model is a claim rather than a description.
What separates Competent from a submission sent back
WGU work is judged Competent or Not Competent rather than by letter grade, and because every aspect is scored independently the returns are specific. A D372-style paper that comes back is rarely wrong. It is incomplete in one predictable way: it identified a system and then analysed it linearly.
What passes on the first read tends to share these features:
- Every loop in the paper is closed. If you can trace the arrows and end up back where you started, it is a loop. If the trail ends, you have written a causal chain and labelled it feedback.
- The boundary is stated once, early, and honoured afterwards. Papers that quietly expand their scope halfway through lose the completeness aspect.
- The proposed intervention is somewhere a reader would not have guessed. Recommending more training or better communication is the default answer that the entire course exists to move you past.
- Unintended consequences are named for your own proposal, not only for other people's. A recommendation with no discussed downside reads as unexamined.
- Every claim about behaviour over time has a source, and every source in the list is used in the text.
Performance-assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs time rather than standing. In a six-month flat-rate term, though, time is the only budget there is: courses closed inside a term you have already paid for are what pull the effective cost per course down. A three-CU general education course that sits open for two months is quietly one of the most expensive things in a degree plan.
Where a course in this family closes with a proctored objective assessment, the line is absolute. Proctored exams are yours to sit. We prepare you for them with concept drills, worked examples and an honest readiness call, and that is all. We do not sit assessments, we do not assist during one, and we never ask for portal credentials.
Six mistakes that cost time in D372
- Picking a problem that is not a system. A one-off incident with a single cause has no loops in it. Choose a situation that has persisted despite people trying to fix it, because persistence is the signature of structure.
- Choosing a topic too large to bound. Climate and poverty are systems, but a 2,000-word paper cannot bound them. One clinic, one supply chain, one team's workload gives you a boundary you can defend.
- Describing loops without directions. A list of connected variables is a diagram of a mess. Saying whether each link moves the next variable up or down is what turns it into an argument.
- Forgetting delay. Most failed interventions in the real world failed because someone measured too early. A paper that ignores lag will propose a fix and then predict an impossible timeline for it.
- Working from the wrong code's materials. D372, D458 and D459 are separate courses with separate catalog numbers. Study guides written for one variant will miss what another variant asks for.
- Writing the recommendation last and fast. Leverage is the aspect with the highest return rate and the one that most needs thinking time. Draft it early, in rough, then build the analysis that earns it.
How support works on this course
D372 is a general education course, which usually means it sits alongside three or four heavier courses and gets whatever attention is left over. That is why it drifts. Send the task directions and the rubric from your Course of Study and the work comes back aspect-mapped: the boundary stated, each loop written out with its variables and link directions, the delays named, and a leverage argument a reader could actually disagree with. A walkthrough comes with it, because the systems habit shows up again in capstone work.
If you are unsure whether your Degree Plan lists D372, D458 or D459, send the plan line and we will confirm it before any work starts. Building against the wrong variant is the most avoidable delay in this part of the catalog.
Questions students ask about D372
Is D372 the same course as PHIL 1030?
What is the difference between D372, D458 and D459?
Do I need to finish a math course before D372?
Systems paper due and the loops will not close?
Send the task directions and your rubric. You get a bounded analysis with every loop written out, the delays named and a leverage argument worth defending.
Where D372 sits in WGU's programs
The July 2026 catalog places this code in 4 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.