NURS 8601 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 DNP Field Experience, the durable class question is: What does the prompt ask the student to understand, apply, compare, create, or evaluate? 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

Define the required concept precisely, apply it to the stated context, make the reasoning visible, and close with the implication the current rubric requests.

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: convert the first week's signals into a fixed production order

Cadence is a reasoning problem before it is a scheduling one. Take what the opening week actually returned, the instructor's announcements, any early feedback, the response window, and the format expectations, and derive a repeating order of operations rather than another list of due dates. A workable order for this class runs read and capture, state the claim, gather and appraise, draft the hardest section, run the checks, then post and reply. Fix that order once and let only the content change from week to week. When the order is stable, an unexpected week costs a few hours instead of the whole week.

Move from a topic to a stated practice problem

The second week is usually where doctoral writing has to stop naming topics. A topic is a subject area. A practice problem is a specific gap in a specific place, described precisely enough that someone could tell whether it closed. Climb the specificity ladder deliberately: subject area, population, setting, the observable gap, and the measure that would show movement. Write each rung as a phrase, then keep only the bottom rung in the draft. Whether the registered activity asks for a problem statement at all is a classroom fact, but writing at the bottom rung serves every activity that does.

4. Use evidence deliberately

Use the assigned readings first when required, then add current authoritative or peer-reviewed support matched to the claim.

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.

Assemble a standing source shelf for the course

Rebuilding an evidence base from zero every week is the most expensive habit available. Build a small standing shelf instead and keep it to a few slots: the assigned readings that recur, one or two guideline or standards documents that define expected practice in the area, two or three strong studies or reviews the student can appraise from memory, and one implementation or improvement reference for how change gets carried out and measured. Note the currency window each source lives in, because a guideline is superseded on a schedule while a landmark study is not. Add to the shelf only what a claim actually needed.

Give every evidence paragraph four parts

A stable weekly cadence needs a stable paragraph. Four parts do the work: the claim in the first sentence, the evidence that bears on it with its citation, the interpretation that says what the evidence establishes and how far it reaches, and the consequence that says what follows for the problem under discussion. Most weak paragraphs are missing the third or fourth part, which is why they read as a stack of correct information with nothing at stake. Draft the four parts as four short sentences before smoothing them, since a missing part is obvious while the sentences are still separate.

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 task completion, reasoning, evidence fit, examples, organization, citations, file rules, and the student's own explanation of the result.

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

By the second week a rubric can be sorted into machinery and content. Machinery rows repeat across a course and score the same behaviors every time: support for claims, organization, mechanics, and adherence to length or format. Content rows change with the activity and score what was actually understood or produced. Handle them differently. Machinery rows become a standing checklist the student runs unchanged every week, which frees attention for the content rows that shift. Compare this week's rubric against the previous one and mark only the differences, because that short list is the real work. The rubric in the registered classroom decides which rows exist and what each is worth.

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.

Pitfall: a schedule built on due dates rather than lead times

A due date is the last moment, not the plan. A cadence anchored on due dates collapses the first time a step has a queue in front of it, because responses, approvals, and file conversions consume calendar time the due date does not show. The fix is to work backward from each deadline through every step that must finish before it, record the lead time of each, and start from the earliest date the chain produces. Any step whose lead time is unknown gets asked about this week rather than discovered later.

Pitfall: sources chosen for availability

A source that appeared first is not a source that fits. In the second week this shows up as a reference list assembled from whatever opened without a login, which reads as thin the moment a grader checks whether the design or the population matches the claim. The fix is to write the claim and its required evidence type before searching, then search for that type specifically. If the required type cannot be found, the honest move is to narrow the claim rather than substitute a weaker source and hope the mismatch goes unnoticed.

Pitfall: replies that restate the original post

Agreement plus a summary is the most common low-value reply, and it is easy to produce while a cadence is still forming. A reply earns its place by doing one of four things: comparing the peer's evidence with different evidence, applying the peer's point to another setting or population, naming a boundary where the point stops holding, or asking a focused question grounded in the course material. Choose the move before writing, and write the sentence that performs it first. Reply requirements and response windows come from the registered classroom.

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