D160 Nursing Leadership and Management Field Experience, catalog number NURS 6503, is the three-CU applied course in the MSN Leadership and Management specialty where you implement the healthcare improvement project you have been building since D156. It is the point where the plan meets a real organisation. The practice hours, the site and the preceptor or mentor relationship are entirely yours, and the boundary on that is stated in full below.
What NURS 6503 is actually testing
Implementation is the phase where students discover the difference between a good plan and a plan that survives. Almost nothing runs as written. The scored question is not whether the project went smoothly, it is whether you led it competently while it did not.
Three things get assessed. The first is execution: did the work actually happen, in what form, and what did you do rather than what did the team do. The second is adaptation: when the plan met an obstacle, did you recognise it early, decide deliberately and document the reasoning. The third is influence, which is the leadership content proper. You are usually implementing without formal authority over the people whose behaviour has to change, so how you built agreement is the substance of what the course teaches.
The failure students least expect is deferring to the plan. A student who follows a schedule that has stopped making sense, because the schedule was approved, is demonstrating compliance rather than leadership. Documented deviation with a reason scores better than silent adherence to something that no longer fits.
The second common failure is a project that never quite starts. Access delays, a mentor whose availability changes, a committee that meets one week later than expected. Implementation shrinks to fit whatever time remains, so the students who finish comfortably are the ones who started the smallest viable version of the work in the first fortnight.
Turning scored aspects into a section plan
WGU keeps rubric detail in your Course of Study rather than in the catalog. Count the scored aspects before writing, since field courses tend to be scored on several narrow ones. Each is judged on its own against a three-point scale and each needs a 2.
The word budget, worked. Where a written component runs to about 1,900 words across five scored aspects, reserve 110 for an opening naming the site, your role and the project, and 90 for the close, leaving 1,700, or 340 per aspect. Then weight it. The adaptation aspect deserves 400, since each deviation needs the trigger, the decision and the reasoning. The influence aspect deserves 360, because building agreement without authority takes room to describe. That leaves 940 for three aspects at about 313 each.
Keep a dated implementation log from day one. What happened, what changed, who agreed to what. Reconstruction at the end always produces a smoother story than the truth, and the truth is what the adaptation aspect is scored on.
A structure that fits an implementation record
Program forms and task directions govern the deliverables. Where the internal shape is yours, this arrangement produces a defensible account.
| Element | What belongs in it | What makes it defensible |
|---|---|---|
| Site and authority | The organisation, your role and what you could and could not decide | Authority described honestly, since it frames every influence claim |
| What was implemented | The work as it actually happened, phase by phase, with dates | Actual dates rather than planned ones |
| Deviations | Each departure from the plan with its trigger, decision and reasoning | Decisions shown as choices with alternatives, not as events |
| Influence work | How agreement was built, with whom, and what changed their position | Specific conversations and what moved, not a claim of engagement |
| Resistance | Who objected, on what grounds, and how it was handled | Objections taken seriously, since most have reasons |
| Data collected | Measures gathered so far against the D159 specification | Collection problems reported rather than smoothed over |
| Interim findings | What the early data suggests, with appropriate caution | Restraint; early data rarely supports a strong claim |
| Leadership reflection | What the implementation revealed about your own practice | A specific competency gap with an action attached |
| References | APA list of change, implementation and measurement sources | Frameworks cited to their sources |
Separate your contribution from the team's plainly. Improvement work is collaborative, evaluators know it, and a record that claims sole authorship of a group effort damages the credibility of the parts that are genuinely yours.
Evidence craft during implementation
Field work generates real organisational information, and that brings obligations coursework does not.
- Anonymise the organisation and everyone in it. Role descriptors rather than names, no unit identifiers, and care with detail that would identify a site.
- Record decisions at the time, with dates. A decision log written contemporaneously is the strongest evidence a field submission can carry.
- Separate what you were told from what you observed and from what you measured. All three are evidence with different weights.
- Report collection problems honestly. Missing data, a measure that proved harder to gather than expected, a week where nobody recorded anything. Concealing those creates a capstone built on sand.
- Keep interim claims proportionate. A few weeks of data after an intervention rarely supports a conclusion, and overclaiming early is a return waiting to happen in the capstone.
- Quote sparingly. WGU runs submissions through a similarity check, and internal material should be described rather than reproduced.
There is also a boundary worth setting deliberately at the start of a field experience taken inside your own workplace, which is where most students do this course. The improvement project has to be distinguishable from your normal job, both for the integrity of the record and for your own protection when the two compete for the same hours. Agree with your mentor in writing which activities count toward the project, which are ordinary duties, and what happens when the unit is short and the project work is the first thing to be dropped. That conversation is awkward once and saves an ambiguous record later.
The practice that most improves an implementation record is documenting the conversations that changed something. Who you spoke to, what they were worried about and what you offered. Influence without authority is the core leadership skill this specialty is building, and it exists almost entirely in conversations that leave no trace unless you write them down within a day.
What separates Competent from a submission sent back
Aspects score on their own, and the adaptation and influence aspects are where returns concentrate.
- Every deviation has a trigger, a decision and a reason.
- Influence is evidenced by specific interactions and what changed as a result.
- Resistance is described with its reasons rather than dismissed.
- Measures follow the specification built in D159, and collection problems are reported.
- What you personally did is distinguishable from what the wider team did.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return costs time. In a field course the cost is heavier, because the placement has a calendar and a mentor whose availability is finite. Terms run six months at a flat rate, and D161 sits directly behind this course, so a delay here usually moves the capstone as well.
Six mistakes that cost time in D160
- Starting late. Implementation compresses to whatever time is left, and the last fortnight is where projects fail.
- Following a plan that stopped fitting. Documented deviation is leadership; silent compliance is not.
- Claiming engagement instead of showing it. Name the conversation and what moved.
- Dismissing resistance. Most objections contain information about a constraint you had not seen.
- Hiding data collection problems. They compound into a capstone that cannot report anything.
- Overclaiming from early numbers. A few weeks of data is a signal at best, and the capstone will have to defend whatever you assert now.
How support works on this course
The boundary comes first. We do not complete field or practice hours. We do not contact mentors, preceptors, placement sites or organisational staff. We do not sign, prepare or submit placement paperwork. We do not fill in, edit or reconstruct hour logs. The placement, the relationships and the record are yours alone.
Inside that line the written and planning work benefits from structure. Send the rubric out of your Course of Study with the task directions and you get a scope check against the time actually available, a decision log format that makes the adaptation aspect writeable, a framework for documenting influence work as it happens, review of anonymised drafts for privacy risk, and help keeping interim claims proportionate so the capstone is not left defending an early overstatement.
Objective assessments at WGU are proctored, so we prepare only, never sit them, and never ask for portal credentials.
Questions students ask about D160
Is D160 the same course as NURS 6503?
Can you help me arrange the field experience?
What if my project cannot be implemented at all?
Implementing in D160?
Send your Course of Study rubric and the task directions. You get a scope check, a decision log format and a way to document influence as it happens. Hours, mentors and logs stay entirely yours.
Where D160 sits in WGU's programs
The July 2026 catalog places this code in 3 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.