HLTH 6111 Week 6 planning manual

1. Capture the live Week 6

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.

Carrying earlier concepts into one integrated change argument

Integration is not a summary of what the course has covered. It is the use of an earlier concept to do work inside a current problem. The test is subtraction. Remove the earlier concept from your response, and if nothing about the argument weakens, the concept was decoration. In this subject integration usually means that an earlier idea about how organizations respond to direction, incentive, or constraint is what makes your current recommendation plausible rather than merely appealing.

Build it in one direction. Start from the current problem, find the point in your reasoning where you are least confident, and ask which earlier concept addresses exactly that point. Bring it in there, in its own sentence, doing a stated job. Resist the reverse move, where a list of course concepts is assembled first and a problem is then found to hang them on, because that produces coverage without argument and reads as a review rather than an analysis. Keep authorship current as well. A returning concept requires new reasoning and new evidence for the new prompt, not language carried over from an earlier submission. Your classroom rubric decides which concepts the current activity expects you to bring forward and how the connection should be shown.

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.

Reading older foundational work beside newer evidence

Integration positions are where foundational sources earn their place. An older, widely used work on organizational behavior or change leadership can be exactly right about a mechanism and exactly wrong as a claim about present conditions. The practical rule is to let older work carry the explanation and newer work carry the situation. When you cite something foundational, say what it explains. When you cite something current, say what it shows about now. Two sentences, two jobs, and the reader can see which is which.

Watch for the version of this that fails quietly, where an older source's context is silently assumed to still hold: a different sector, a different scale of organization, a different era of regulation or workforce. Name the difference in one clause and the citation becomes stronger rather than weaker. If the current activity restricts source dates, that restriction governs, and a foundational source may need to be replaced or supported by a recent review that carries the same mechanism. Keep the reference list honest by removing anything that survived only because it was already typed. Your classroom rubric decides date windows, acceptable source types, and how many sources the activity requires.

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 6 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 for integration language

Rubrics signal integration with quiet words: connect, relate, synthesize, draw on, apply course concepts, build on prior learning. Those rows are not satisfied by mentioning an earlier topic in passing. They are satisfied when a reader can watch one idea change what you do with another. Mark those rows, and for each of them point to the exact sentence in your draft where the connection performs work.

Then check the opposite failure, which integration positions invite. A response can become so busy connecting that it never answers the current prompt directly. Read the prompt's own verbs against your opening paragraphs and confirm that the direct answer arrives early rather than emerging late from a chain of associations. Integration should deepen an answer that is already present, not replace it. Rows about organization and clarity often catch this failure before the content rows do, which is a reason to read them first rather than last. Your classroom rubric decides how integration is weighted in this activity and what counts as evidence of it.

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 7. 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 6, 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 7.

Three integration pitfalls and the fix for each

The first pitfall is the concept parade, where several course ideas are named in sequence and none of them changes the analysis. It looks thorough and scores as coverage. The fix is the subtraction test applied to every named concept before submission: remove it, and if the argument does not weaken, remove it for good.

The second pitfall is reusing your own earlier submitted language because the concept has returned. Beyond the originality problem this creates, the recycled passage answers the older prompt while sitting inside the newer one. The fix is to keep the method and the lesson from the earlier work and write the new response from the new prompt.

The third pitfall is integrating upward into abstraction, where the response climbs from a concrete organizational problem into general statements about leadership that no reader could dispute or use. The fix is a closing rule for every integrated paragraph: end it with a sentence that returns to the specific situation, the specific constraint, and the specific person who would have to act.

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

Week 6 questions