D367 Innovation in Finance, catalog number FINC 3104, is a three-CU course on the emerging financial technologies and product solutions disrupting financial services. Payments, lending, advice, insurance and market infrastructure are all being rebuilt by firms that were not banks a decade ago, and the course asks you to evaluate those changes rather than to admire them. It is the least numerical course in the finance sequence and the one where uncritical writing is punished hardest.
Evaluation, not enthusiasm
Every technology in this course arrives wrapped in marketing, and the competency being assessed is your ability to unwrap it. That means asking, of any innovation, four unglamorous questions: what problem does it solve, who currently solves that problem and how, what does the new approach actually cost including the costs it moves somewhere else, and what has to be true for it to work at scale.
Applied to payments, the first question exposes that many innovations solve speed and cost problems created by legacy settlement arrangements rather than by any law of nature. Applied to lending platforms, it exposes that the underwriting risk does not vanish, it relocates to whoever holds the loan. Applied to automated advice, it exposes that the value being delivered is often low-cost allocation rather than genuine planning, which is a real service with a narrower remit than the marketing suggests.
Regulation is not a side topic here either. Financial services are regulated because they hold other people's money, and a new entrant that avoids a rule usually does so because the rule was written for a structure it does not have, not because the underlying risk went away. Strong submissions in this course say that plainly and identify which protections a customer keeps and which they trade away.
Aspects into a technology evaluation
Aspects in your Course of Study are scored independently and each needs a 2. In a course of this kind the aspects usually split between description and evaluation, and description is the easy half that swallows the word count if you let it.
Worked example with a description trap. Suppose your rubric shows four scored aspects and the directions ask for about 1,800 words. Reserve 120 for framing, leaving 1,680, or 420 per aspect. Now impose a rule on yourself: no aspect gets more than 150 words of description before evaluation begins. Four aspects at 150 is 600 words of description across the whole document, leaving 1,080 for analysis, which is the correct ratio for a course that assesses judgment.
If you find an aspect where you cannot write 270 words of evaluation, you have not researched it enough. That gap is diagnostic and it is worth catching two days before submission rather than the night before, because filling it requires reading rather than writing.
A framework for assessing any financial innovation
The same evaluation grid works across payments, lending, advice, insurance and infrastructure. Use your task directions where they set a structure; otherwise this keeps every technology assessed on comparable terms.
| Dimension | What to establish | Where weak submissions stop |
|---|---|---|
| Problem | The specific friction, cost or exclusion being addressed | Describing the technology instead of the problem it exists to solve |
| Incumbent approach | How the need is met today, and what that costs whom | Assuming the existing system is simply bad rather than understanding its constraints |
| Mechanism | How the innovation actually works, in plain words | Repeating vendor language that explains nothing |
| Economics | Who pays, who is subsidized, and where the margin comes from | Accepting a free service at face value without asking how it is funded |
| Risk transfer | Which risks moved, and onto whom | Treating relocated risk as eliminated risk |
| Regulatory position | Which protections apply, which do not, and why | Ignoring regulation entirely, which is the most common gap in this course |
| Adoption barriers | Trust, network effects, switching costs, infrastructure | Predicting adoption without naming what would slow it |
| Assessment | Whether this displaces, supplements or fails, and on what timeline | Concluding that the future is uncertain, which is not a conclusion |
The risk transfer row is the one that separates a business evaluation from a technology summary. Innovations in finance rarely delete risk; they move it to a different party who may be less equipped to bear it, and naming that party is often the sharpest sentence in the paper.
Sourcing a subject that moves quickly
This course has the hardest sourcing problem in the finance sequence, because the field changes faster than textbooks are revised and most of the writing about it is promotional.
- Date every source and prefer recent material, since a claim about adoption or capability can be two years stale and simply wrong.
- Separate vendor material from independent analysis, and say which you are using. Company statements are evidence of positioning, not of performance.
- Prefer regulators, central banks and industry bodies for structural claims, since they have no product to sell.
- Distinguish pilot from production. A great deal of published enthusiasm concerns trials that never scaled.
- Cite in APA, paraphrase rather than quote, and keep quotation minimal because submissions are similarity-checked.
Historical perspective is unexpectedly useful evidence in this subject. Financial services have absorbed several waves of technology already, and each one produced predictions that the existing institutions would disappear. Some functions genuinely moved, some incumbents bought the entrants, and a good deal of the promised change arrived a decade later and in a different shape. A paragraph placing the current wave against that record is not padding; it is the context that lets a reader judge whether your assessment is calibrated or merely enthusiastic, and it is easy to source because the earlier waves are thoroughly documented.
Be careful with figures. Transaction volumes, user counts and market sizes circulate widely with no traceable origin, and a number you cannot attribute to a named source with a date is a liability in a paper that is otherwise arguing carefully. Where the only available figure is unreliable, say so and argue without it. An argument that stands on mechanism and economics rather than on a contested statistic is the more durable one anyway, and evaluators tend to read the caution as confidence rather than as a gap in the research.
What a Competent evaluation contains
Each aspect is judged on its own against the competency standard, and the standard rewards skepticism supported by evidence rather than either enthusiasm or dismissal.
- Each technology is explained in plain language, without vendor terminology left undefined.
- The incumbent approach is described fairly, including why it works the way it does.
- Economics and risk transfer are addressed explicitly rather than assumed away.
- Regulatory implications are named, including where consumer protections differ.
- The assessment reaches a position and states the condition that would change it.
WGU records Competent or Not Competent with no letter grade and no ordinary grade point average behind it, and performance assessment work can be revised and resubmitted with no penalty. A return costs queue days inside a six-month flat-rate term. Where your version of the course includes a proctored objective assessment, our support is preparation only: concept review, comparison drills and a readiness verdict. We never sit an assessment and never ask for portal credentials.
Five mistakes that make this course harder to pass
- Writing a technology summary instead of an evaluation. Explaining how something works is the setup; judging whether it should be adopted is the assessed part.
- Accepting marketing claims as findings. Vendor material tells you what a company wants believed, which is useful evidence about positioning and nothing else.
- Ignoring regulation. Financial services rules exist because of past failures, and an innovation that sidesteps them has usually moved a risk rather than solved it.
- Predicting adoption with no barriers named. Trust and switching costs slow financial change more than technical capability does.
- Concluding that time will tell. That is a refusal to answer, and the assessment aspect will read it as one.
Support on a fast-moving subject
Send the rubric, the directions and the technology or firm the task names. The draft comes back on the evaluation grid: the problem stated before the product, the incumbent approach described fairly, the mechanism explained without jargon, economics and risk transfer traced, regulatory position named and an assessment that commits with a stated condition. Sources are dated and separated by type, so a reader can see which claims rest on independent analysis.
D367 sits alongside D368 Enterprise Risk Management in most finance plans, and the two reinforce each other: one asks what new risks are entering the system, the other asks how an organization would govern them.
Questions students ask about D367
Is D367 the same as FINC 3104?
Is D367 a technical course?
How current do my sources need to be?
Evaluating a financial technology?
Send the rubric and the technology named in your task. You get an evaluation, not a summary, with sources dated and separated by type.
Where D367 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. 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.