HLTH 6111 Week 9 planning manual

1. Capture the live Week 9

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 Leadership and Organizational Change, the durable class question is: What outcome is being chosen, for whom, under which constraints and trade-offs? 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

Convert theory into criteria, compare options against evidence and constraints, quantify material effects where possible, then state implementation, ownership, and measurement.

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.

Assembling the close as one coherent change argument

Week 9 turns a collection of positions into one line of argument. Lay out what the course has asked you to produce so far and find the through-line: the outcome you have been arguing for, the population it serves, the constraints you have taken seriously, and the trade-off you have consistently accepted. Closing work is judged partly on coherence, and coherence is easier to build than to imitate. If the through-line does not exist yet, choose it now and let it decide what stays in the closing work and what is set aside.

Then sequence the argument for a reader who has not followed your quarter. Problem and stakes, criteria, options measured against those criteria, the choice, the implementation with a named owner, the measure, and the risks with what you would do about each. Draft the highest-risk section first regardless of where it appears in the finished document, because the sections that depend on evidence or calculation are the ones most likely to need a second pass. Leave the introduction until the argument is settled, since an introduction written early usually promises something the finished work no longer delivers. Your classroom rubric decides the required structure, and any posted template governs over the order suggested here.

4. Use evidence deliberately

Combine relevant scholarly literature with current market, organizational, or policy evidence while labeling assumptions and protecting confidential information.

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.

Consolidating the evidence base for the closing work

Before drafting a closing piece, consolidate rather than collect. Pull every source that has genuinely carried an argument this quarter into one list, group them by the part of the argument they support, and look for the thin places. In this subject the thin places are almost always at the same two joints: why the proposed change would actually alter behavior, and what measured effect similar changes have produced elsewhere. Fill those two before adding anything else, because they are the joints a careful reader tests first.

Then check the shape of the list as a whole. A closing argument here usually needs scholarly work for mechanism and effect, and current organizational or policy material for feasibility and context, and a list heavily weighted to one side will show it. Verify every reference against its in-text use one final time, since consolidated documents are exactly where mismatches accumulate. Retire anything that survived only because it was already in the file. Your classroom rubric decides minimum sources, permitted types, and citation style for the closing activity, and the posted instructions govern over any habit you built earlier in the quarter.

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 9 quality gate

Stress-test feasibility, incentives, ethics, risk, counterarguments, implementation ownership, and the metric that would show the decision worked.

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 across the remaining work

With several activities left, read the rubrics you can see as a set rather than one at a time. Note which criteria repeat, because those are where consistent practice pays across everything that remains. Note which appear only once and carry heavy weight, because those need dedicated preparation and are the ones students most often underestimate while attending to the familiar rows.

For the closing work specifically, map each rubric row to a section of the document before you write, and confirm that no row is homeless and no section is unscored. A section that answers nothing on the rubric is either misplaced effort or a sign that you have misread a row, and both are worth catching before drafting rather than after. Give the format, organization, and citation rows explicit time in the plan, since at the end of a quarter those are the rows most often lost to fatigue rather than to any gap in understanding. Your classroom rubric decides all criteria and weights for each remaining activity.

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 10. 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 9, 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 10.

Three assembly pitfalls and the fix for each

The first pitfall is assembling by stitching earlier submissions together. Beyond the originality problem it creates, each earlier piece answered an earlier prompt and carries that prompt's assumptions into a document built for a different question. The fix is to write the closing work from the closing prompt, treating your earlier reasoning as source material rather than as text to be moved.

The second pitfall is leaving dependencies until the final position. Approvals, group members, technical submission routes, and anything needing another person's response can stall for days without anyone being at fault. The fix is to open every dependency now, in writing, with a date on which you will follow up.

The third pitfall is planning by page count instead of by risk. Spreading effort evenly across sections leaves the hardest section drafted last and thinnest, which is the opposite of what a reader will notice. The fix is to rank sections by how likely they are to need a second pass, draft in that order, and protect the final stretch for verification rather than for writing.

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 9 activities. The registered syllabus, classroom, rubric, announcements, instructor directions, and official policies remain controlling.

Week 9 questions