Leavitt School of Health

WGU D161: Nursing Leadership and Management Capstone

D161 Nursing Leadership and Management Capstone is the final course in WGU's MSN Leadership and Management program — a 2-CU performance assessment with no proctored exam. This guide covers what the final report and presentation require, how to evaluate your healthcare improvement project against your own KPIs, and the mistakes that send submissions back for revision.

D161Leavitt School of Health2 CUsMediumPerformance Assessment
WhatsApp us Coaching & tutoring — original prep support, never exam content
WGU D161 Nursing Leadership and Management Capstone exam guide cover

The Course That Closes Out Your MSN

WGU's D161 Nursing Leadership and Management Capstone is the final course in the Master of Science, Nursing – Leadership and Management program, housed in WGU's Leavitt School of Health. It is worth 2 competency units, and its entire purpose is to help you evaluate and close the healthcare improvement project (HIP) you have been building through the specialty courses. You do not start something new here. You finish what you already began.

Direct answer: There is no proctored exam in D161 — you pass by submitting a performance assessment. Analyze your healthcare improvement project's results against the key performance indicators and metrics you defined during the planning phase, then present those results in a final report and presentation with an honest lessons-learned account of each project phase. Write directly to the rubric, use your own project data, and revise until every requirement is fully addressed.

Students reach D161 after completing D160 Nursing Leadership and Management Field Experience, which the program guide names as the prerequisite. In D160 you implemented the project: you kicked it off with stakeholders, ran the training plan, problem-solved the risks that surfaced, and led status meetings. In D161 you turn around and ask the harder question — did any of it work, and how do you know?

That shift matters more than it sounds. Nurses who are excellent at doing the work often struggle to step back and evaluate it dispassionately. WGU's own course description says reflective and analytic thinking are essential aspects of the capstone — meaning those are the graded skills, not project execution. If you can read your own metrics honestly, name what went wrong without defensiveness, and connect the whole arc back to the competencies you built across the program, you will do well.

What the D161 Performance Assessment Actually Asks For

Per WGU's official MSN Leadership and Management program guide, the capstone centers on evaluating and closing your HIP. The verified scope covers:

  • Results analysis against your own KPIs. You evaluate the success of the healthcare improvement project by analyzing outcomes using the key performance indicators and metrics identified while you were planning the evaluation phase — not new measures invented after the fact.
  • A final report. A written presentation of the improvement project's results.
  • A presentation. The results delivered in presentation form, which means your findings must survive being spoken aloud to an audience, not just read.
  • Lessons learned by phase. The report focuses on lessons drawn from each phase of the project: initiation, planning, implementation, and evaluation.
  • Reflective and analytic reporting. You report on the successes and the challenges encountered in each phase. Both halves are expected.
  • Program-wide synthesis. The single listed competency is about integrating and synthesizing competencies from across the degree program, demonstrating you can contribute value in your professional field.

One practical note: WGU lists this course as eligible for an "In Progress" grade. That is normal for capstones and means the term boundary is less of a cliff than it is in a standard objective-assessment course — but it is not a reason to drift. Ask your course instructor how the grading scale policy applies to your term.

How Hard Is D161, and How Long Should You Budget?

Difficulty in D161 is unusual because it is almost entirely inherited. The course is short at 2 competency units, and the writing is not conceptually difficult for someone who has made it through an MSN core. What makes it hard or easy is the state of your project when you arrive.

Students who arrive with clean data, complete documentation, and a cooperative preceptor generally describe the capstone as fast-moving. The ones who describe it dragging usually hit the same wall: the implementation ran late, the post-intervention data was thin, or the evaluation plan was written vaguely enough that nothing can be measured against it now. The writing is rarely the bottleneck. The data reality is. We have not found a reliable public source for a typical completion time, so treat any number you see quoted online with suspicion and plan against your own data instead.

Plan on two parallel tracks. Track one is administrative: confirm your documentation from the field experience is complete and accessible. Track two is analytic: assemble your baseline numbers, your post-implementation numbers, and the gap between what you promised to measure and what you can actually measure. Do track one in your first few days so it is never the thing holding you up at the end.

A Working Plan for the Final Report and Presentation

Capstones reward disciplined process far more than talent. Try this sequence.

  1. Turn the rubric into your outline. Before writing a sentence, copy each rubric aspect into a document as its own heading. Draft underneath the headings. This single habit prevents the most common revision request, which is a section that reads beautifully but never explicitly answers the prompt.
  2. Rebuild your KPI table first. Lay out each indicator, its target, your baseline, your result, and the variance. Do this before you write prose. Once the numbers sit in a table, the narrative practically writes itself — and gaps become obvious while you still have time to address them.
  3. Use retrieval practice on your own project. Close your files and write from memory what happened in initiation, planning, implementation, and evaluation. Then open the documents and compare. The places where your memory is fuzzy are exactly where your report will be thin, and this active-recall pass finds them in twenty minutes.
  4. Write challenges before successes. Most students instinctively lead with what worked and then tack on a token limitation. Reverse it. Draft the honest problems first — staffing changes, low survey response, scope creep, a metric that turned out to be unmeasurable — then explain what you did about them. Graders read this as analytic maturity, not failure.
  5. Space the work across sittings. Draft, sleep, revise, sleep, submit. Spacing your revision passes over several days catches far more inconsistency between your numbers and your narrative than one long session ever will.
  6. Rehearse the presentation out loud. Record yourself once. Anywhere you stumble is a slide where your logic is not actually connected. Fix the logic, not the wording.
  7. Tie back to the program. In your lessons-learned section, explicitly connect what you did to the leadership, quality, and evidence-based concepts from earlier courses. If the case you built in D156 Business Case Analysis for Healthcare Improvement shaped a decision later in the project, say so plainly.

Where D161 Submissions Usually Get Sent Back

  • Reporting activity instead of outcomes. "We trained forty-two staff members" is implementation. The capstone asks what changed as a result.
  • Swapping in new metrics. If a KPI did not pan out, say so and analyze why. Quietly substituting a friendlier measure reads as an unaddressed requirement.
  • Sanitizing the challenges. A project with no reported difficulties looks under-examined, not successful.
  • Skipping a phase. Lessons learned are expected from initiation, planning, implementation, and evaluation — all four. Initiation is the one people forget.
  • A report and presentation that disagree. Update both when you revise a number. Mismatched figures between deliverables are an easy catch for an evaluator.
  • Unsupported claims. Every assertion about impact needs a data point or a clearly labeled qualitative source behind it.
  • Leaving documentation for last. Chasing a preceptor signature during your final week is an avoidable delay.

D161 Readiness Checklist

  • Can you state your project's aim in one sentence, without jargon?
  • Can you list every KPI you committed to during evaluation planning, and produce a result for each?
  • Can you show baseline and post-implementation figures side by side?
  • Can you explain one metric that did not work out and why?
  • Can you name a specific lesson learned from each of the four phases?
  • Can you defend your conclusions if someone asks "how do you know?" three times in a row?
  • Is all required field experience documentation complete and in hand?
  • Have you checked your draft against every rubric aspect by name?
  • Can you deliver the presentation once through without reading your slides?

D161 FAQ

Is D161 an OA or a PA?

It is a performance assessment. There is no proctored objective assessment for this course — you are graded on submitted work evaluating and closing your healthcare improvement project, including a final report and presentation.

How many competency units is D161 worth?

Two competency units, according to WGU's official MSN Leadership and Management program guide. It sits in the final term of the standard path alongside the field experience course.

Do I need to finish D160 first?

Yes. The program guide states that Nursing Leadership and Management Field Experience is a prerequisite for the capstone. The capstone evaluates the project you implemented in that course, so the sequence is not negotiable.

What if my improvement project did not produce the results I hoped for?

That is a normal capstone outcome and it is not a failing condition. The course grades your ability to analyze results honestly and reflect on successes and challenges. A well-evaluated project that underperformed is stronger work than an overstated success.

Is D161 hard compared to other MSN courses?

Most students find the conceptual load lighter than the MSN core courses, since the material is your own project. The difficulty is logistical and analytical — having usable data and writing precisely to the rubric — rather than academic.

Where can I confirm the official course details?

Check your Degree Plan in the WGU student portal and the current MSN Nursing Leadership and Management program page on wgu.edu. Program requirements change between catalog versions, so your own Degree Plan is always the authority.

Keep Going

If you are mapping out the rest of your MSN coursework, browse the Leavitt School of Health guides — including D028 Advanced Health Assessment for Patients and Populations, another course in this same program. You can also see every course we cover on the full study guide index.

Want a human in your corner for D161?

Book 1-on-1 OA prep coaching, a tutoring session or a study-plan review with our team.

Prefer WhatsApp? Message us on +1 646 980 4914.

Related Health & Nursing guides