NURS 8514 Week 2 planning manual

1. Capture the live Week 2

Open the registered classroom and create one row for every visible activity. Record its exact name and type, complete action verbs and questions, rubric or scoring criteria, points and course weight, due date and time zone, required and permitted resources, length and format, discussion reply rules, dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version beside the working file.

2. State the Week's reasoning question

For Executive Leadership DNP Project and Practicum I, the durable class question is: What evidence supports the judgment, what alternatives matter, and what remains outside the student's authority? Translate the live activity into one sentence that names the decision or explanation, the required evidence, the audience, and the expected output. If that sentence cannot be written, return to the prompt instead of guessing from a prior Week or third-party example.

3. Build the work in proof order

Move from cue to mechanism or standard, then to prioritized judgment, action, monitoring, and escalation. Use only de-identified authorized context.

Make a rubric-to-evidence matrix before prose: one row per criterion, the evidence or reasoning needed, where it will appear, what the student must personally do, and the test that will prove completion. Draft the highest-risk row first, not necessarily the introduction. Protect time for replies, calculations, format conversion, approvals, and the final upload.

Worked reasoning: building a cadence the course can sustain

A project and practicum course fails on rhythm more often than on intellect. Week 2 is where a rhythm becomes visible, so build it deliberately rather than discovering it in Week 7. Run two lanes on the same calendar. The classroom lane holds every graded activity the registered Week displays. The preparation lane holds the written and administrative groundwork that a project sequence accumulates, including anything the program requires to be requested, reviewed, or approved through its official process.

Then schedule backwards. Take the file deadline shown in the classroom, subtract the time the student actually needs to verify and upload, subtract a checking block, subtract a drafting block, and subtract a search and appraisal block. The remaining start date is the true start date, and if it has already passed the scope of the intended output is too large for the Week rather than the student being behind. Apply the course reasoning order to the schedule itself: the cue is the deadline, the standard is the rubric, the judgment is what fits, the action is the calendar entry, and the monitoring is a mid-Week check on whether the plan survived contact with the rest of the week. Escalation means contacting the instructor early through the official channel rather than late. The live classroom still decides what belongs in Week 2, and its rubric decides how the result is scored.

4. Use evidence deliberately

Prefer current authoritative clinical guidance and peer-reviewed evidence appropriate to the question; distinguish guideline recommendations from patient-specific facts.

For every source, write a one-line use note before drafting. Distinguish direct evidence from interpretation and local observation. Quote sparingly, paraphrase from understanding, and cite the claim actually supported. If the activity requires current evidence, confirm publication dates and whether an older foundational source is still appropriate.

What counts as scholarly when the search protocol is written

Cadence applies to searching too. Write the search protocol down in Week 2 rather than searching by memory for the rest of the term. A usable protocol records the databases consulted, the controlled vocabulary and free-text terms tried, the date limits applied, the language and setting limits, and the reason for each inclusion or exclusion decision. Scholarly at this stage means retrievable and appraisable: a source another reader could find from the record kept, and judge on its design rather than its tone. Recency limits deserve a stated rationale, because a five-year window is a convention rather than a rule, and a foundational work that defines a construct may be older than the window and still correct to use. Guidance documents carry both a publication date and a review date, and the review date is often the one that matters.

Turning search results into a table that later becomes prose

Log each retained source in a running table with fixed columns: citation, design or document type, setting and population, the finding in the student's own words, the stated limitation, and the exact claim the source will support. That last column is the one that prevents a reference list padded with sources doing no analytical work. Appraise while logging, because a summary written now and a judgment written in Week 6 rarely agree. When the table is populated, prose can be drafted by reading down a column instead of re-opening every file, and the argument inherits the discipline of the table. Any source whose claim column stays empty after two passes should be released rather than carried.

5. Complete discussions and collaborative work

When the live Week contains a discussion, schedule the initial post by its own deadline and each reply by the response window. A useful reply does more than agree: compare evidence, apply the peer's idea to a different context, identify a boundary, or ask a focused question supported by the course material. The student writes and posts every contribution; a tutor may critique clarity and reasoning before submission.

6. Protect identity, practice, and research boundaries

Do not share protected health information, employer secrets, client identities, private peer content, assessment security material, or unauthorized research data. Clinical encounters, field hours, simulations, observations, interviews, group participation, proctored work, residencies, approvals, attestations, and original data collection must be completed and recorded by the student under the applicable Walden process.

7. Run the Week 2 quality gate

Check safety, scope, differential logic, contraindications, documentation, confidentiality, and every student-performed clinical requirement.

Then perform a literal instruction audit: every prompt part answered, rubric row visible, calculation reproducible, citation matched, heading and format correct, accessibility checked, file opened successfully, and confidential material removed. Compare against the current rubric, not a saved rubric from another section or term.

Reading the rubric row by row in Week 2

With a second live rubric available, read the two side by side and mark the rows that recur. Recurring rows are the course's standing expectations, and they are where a repeated small deduction becomes a pattern. For each recurring row, write one line describing what a full-credit response to that row looked like last Week and what it would take this Week, phrased as an action rather than an adjective. Then look for the rows that are new, because a new row usually signals the skill the Week is actually teaching. Check whether any row carries a threshold or a penalty attached to length, timing, reply count, or format, since those rows are scored mechanically and are the cheapest points in the course to protect. Record the weight of every row in the control ledger so drafting time can be allocated in proportion. The registered rubric governs, and nothing on this page changes what it requires.

8. Submit and close the loop

The student performs the final upload or entry, opens the submitted artifact, confirms the timestamp and file, and saves the receipt. When feedback arrives, record each criterion result, instructor comment, correction, and lesson for Week 3. Contact the instructor or official support channel promptly for a missing, late, or technically failed submission.

9. Defend the learning before moving on

Before closing Week 2, the student should explain the live task, central claim or decision, strongest evidence, method or calculation, important limitation, and next action aloud without reading the submitted artifact. For a discussion, explain what the peer exchanges changed. For clinical, field, research, group, or proctored work, identify which parts the student personally performed and how they were verified. Any point that cannot be explained becomes the first short practice item for the next study session. This oral defense tests understanding more honestly than another formatting pass and turns the finished Week into preparation for Week 3.

Two Week 2 pitfalls and the fix for each

The first pitfall is a search so broad that appraisal never starts. Hundreds of results feel productive and produce nothing usable, and the student arrives at the drafting block with a folder rather than an argument. The fix is a stopping rule set in advance: define the number of retained sources the current activity actually needs, screen against the inclusion criteria written in the protocol, and stop searching when the retained set stops changing rather than when the search feels complete. The second pitfall is letting the preparation lane fall behind the classroom lane. Graded activities are visible and loud, while the groundwork a project sequence needs is quiet until it becomes urgent, and any step that depends on another person's review has a queue the student does not control. The fix is a standing weekly appointment for the preparation lane that is protected exactly like a graded deadline, with the next required step written as a dated line item rather than an intention.

Source boundary

Walden's current catalog verifies this Course-Based class context, and the quarter calendar supports positional Weeks. The public catalog does not identify the student's Week 2 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 2 questions