NURS 8705 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 Doctoral Seminar, the durable class question is: What claim, question, method, evidence, or approval gate is this work advancing? 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.

Worked reasoning: building a cadence the seminar can absorb

A cadence is a written rule about when each kind of thinking happens, not a wish about starting earlier. Split the Week into four named blocks: locate and read, reason and outline, draft, and verify. Give each block a finish condition rather than a duration. Locate and read finishes when the evidence table holds one row per source with a usable finding and a limitation. Reason and outline finishes when every rubric row has a location in the outline. Draft finishes when no placeholder remains. Verify finishes when the response has been read once against the prompt and once against the rubric. Doctoral reading is slower than earlier coursework because a primary study has to be inspected rather than skimmed, so the first block usually needs the most room. Adjust the block sizes once the Week closes, using what actually ran long. Your registered classroom sets the deadlines this cadence has to respect.

3. Build the work in proof order

Keep problem, evidence, method, finding, limit, and implication aligned. Distinguish a course exercise from original research and never imply approval before the relevant reviewer grants it.

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: reading a study once and using it three times

In a research seminar the same article usually serves several purposes, and reopening it for each one is a large hidden cost. Read once with a fixed extraction sheet: purpose, design, population or setting, the key result with its magnitude, the stated limitation, and one sentence naming what the study can and cannot support. That sheet then answers a discussion contribution, supplies a synthesis paragraph, and later supports a methods comparison without the article being reopened. Take a neutral practice article on staffing and readmission: the design line tells you whether it can speak to causation, the population line tells you where transfer is arguable, and the limitation line supplies the qualifying clause your paragraph needs. Build the sheet in Week 2 while volume is still manageable. What each source must do in the current activity is set by the live instructions, not by the sheet.

Reading the rubric row by row as a weekly routine

Week 2 is where the rubric stops being a document you read and becomes a checklist you run. Convert the rows into a short standing list phrased as questions rather than nouns. Does the response answer the prompt in its first movement? Does each claim carry evidence or an explicit inference marker? Is the reasoning visible rather than implied? Are limitations stated rather than avoided? Is the format exactly as instructed? Run the list twice, once against the outline and once against the finished draft, and record which question failed on each pass. Two Weeks of that record will expose a personal pattern, and the pattern is what you practice against for the rest of the quarter. Rubrics differ between activities and can be revised mid-quarter, so re-read the live rubric each Week instead of trusting the standing list on its own.

4. Use evidence deliberately

Build a traceable evidence table with purpose, design, population or setting, result, limitation, and the exact sentence each source can support.

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.

Turning early reading into a source base you can defend

A defensible source base for doctoral nursing work is judged on fit and currency, not on count. Fit means the study population, setting, and measured outcome sit close enough to your question that the finding transfers without heavy qualification. Currency means the publication window matches the pace of the field and any date rule the activity states. Keep a running file in three sections: core studies that speak directly to the relationship, boundary studies that show where the finding does not hold, and context sources such as standards or data sets that define terms and scale. When drafting, pull from core first, use boundary studies to write the limitation sentence, and let context sources carry only definitional work. A reference list padded with sources that never perform analysis reads as volume, and readers notice. Assigned readings stay mandatory wherever the current activity requires them.

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

Audit alignment across the problem, question, method, analysis, conclusion, rubric, and current institutional milestone.

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.

Two Week 2 pitfalls and the fix for each

The first pitfall is repeating Week 1's approach without asking what the first returned comments actually said. Early feedback usually names a habit rather than a sentence, and a habit repeated in Week 2 hardens for the quarter. The fix is to write the habit in one line, write the corrective behavior next to it, and schedule that behavior inside the cadence rather than trusting recall. The second pitfall is letting discussion contributions drift into a separate, lower-effort track. In a doctoral seminar the exchange is where reasoning is rehearsed, and a reply that only agrees rehearses nothing. The fix is a standing reply frame: name the peer's claim, name the evidence it rests on, then add a comparison, a boundary, an application, or a supported question. Post inside the response window your classroom sets and follow its reply rules exactly.

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.

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