NURS 8720 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 II, 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.

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: separating the problem, the purpose, and the question

A cadence stabilizes around three sentences that get rewritten rather than three topics that get replaced. Write the problem as a condition in the world that is documented and measurable by someone other than the student. Write the purpose as what this piece of work will do about it: describe, compare, explain, evaluate, synthesize, or propose. Write the question as the exact sentence the finished work must answer. Then test the joins. The purpose verb has to be capable of producing an answer to the question, and the question has to be about the problem rather than about the literature that discusses the problem.

A ten-minute check that catches most second-Week drift: read the three sentences aloud in reverse order. If the question can be answered without the purpose statement being true, the purpose is decoration. If the purpose could be carried out whether or not the problem exists, the problem is background rather than motivation. Repair the weakest join first and note which one moved, because graded comments about focus almost always point at one of these joins rather than at the prose.

Then build the working routine around the triad rather than around the calendar. Each session opens by rereading the three sentences, closes by recording whether any of them moved, and updates the evidence table in the same sitting. Length matters less than repeatability: a stable half hour that happens four times beats one long evening that cannot be repeated when the next Week arrives.

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.

Source work that repeats: a search routine and a running table

A cadence is stable when searching stops being an event. Fix the routine: name the concept, list the synonyms and the terms the literature itself uses, decide the date window, decide which designs are wanted, run the search in the library resources the registered classroom points to, and record the search string, the filters, the date range, and the yield before reading a single result. A search that cannot be repeated cannot be described, and in a doctoral seminar the ability to say how the evidence was found is part of the method rather than an administrative detail.

Screen by function, not by enthusiasm. For each candidate, fill the columns the course method names: purpose, design, population or setting, result, limitation, and the exact sentence the source can support. Any source that reaches the last column empty gets released back to the reading list. This keeps the table small and the reference list honest, and it makes the second and third searches faster, because the gaps are already written down as specific concepts and designs rather than as a vague instruction to find more.

Scholarly in this seminar means the reader can inspect the method. Prefer primary reports with a visible design over summaries of them, use reviews to map a field, and use methodological texts to justify a choice. Treat professional and regulatory documents as authority for expectations rather than as evidence of effect. Keep assigned readings inside the same table so required and chosen material are held to one standard.

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.

Reading the rubric row by row, and building a standing checklist

The registered classroom rubric decides, and this Week's may or may not repeat the last one's. Read it as two kinds of row. Recurring rows appear in most activities and cover things like evidence use, organization, and mechanics. Activity rows are written for this task alone. Separate them on paper. The recurring rows become a standing checklist that gets reused every Week, which is a large part of what makes a cadence stable; the activity rows get built into the outline as visible sections.

For each row, write the observable thing a grader could point to. Not the intention, the artifact: a sentence, a table cell, a citation, a heading, a calculation, a reply. If a row cannot be tied to something a reader can point at, that row is not yet planned. Then mark which rows can be satisfied early, before the reading is finished, and complete those first so the routine produces visible output from its first day rather than only at the deadline.

Finally, check the participation and reply rows if the live Week includes a discussion. Timing and substance are frequently scored separately, and the timing half is the easiest set of points in the course to lose to a routine that has not yet stabilized. Put those deadlines in the same ledger as the file deadlines rather than trusting them to memory.

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.

Three Week 2 pitfalls and the fix for each

First pitfall: a cadence built on due dates alone. Work blocks get scheduled backward from deadlines, which ignores the lead time that approvals, group replies, library requests, and format conversion actually need. The fix is to schedule from dependencies instead: write each dependency's own lead time in the ledger, find the longest one, and place the drafting around it rather than the other way around.

Second pitfall: a reference list growing faster than the argument. Twenty entries and no defended claims is the characteristic second-Week state, and it feels productive while producing nothing scoreable. The fix is a ratio the student sets and keeps: no new source enters the table until the previous one has a written use sentence naming the claim it will support.

Third pitfall: replies written in a single burst. Posting a strong initial contribution on time and then three replies in the last available hour produces agreement rather than analysis, and reply rows notice the difference immediately. The fix is to give each reply its own block in the routine and to choose the move in advance: compare evidence, apply the peer's idea to a different context, name a boundary, or ask a focused question the course material can answer.

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