HLTH 6038 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 Health Behavior Theory, the durable class question is: Which population, determinant, stakeholder, and measurable outcome define the problem? 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 population and baseline, trace determinants and system constraints, compare interventions, and connect the recommendation to implementation and evaluation.

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.

Making the reasoning pass repeatable

Cadence is an order of operations, not a mood. Run the four slots of the class question in the same sequence every Week so the sequence stops costing attention: bound the population, fix the baseline measure, name the determinant and the level of influence it sits at, map the stakeholders to the levers they actually control, then define the outcome that would show change. Searching comes after all five, never before.

Most cadence failures happen because that order gets inverted. A student opens a database first, collects whatever is readable, and then tries to build a population definition that will accommodate the pile. The result is a set of sources that individually look respectable and collectively support no single claim. Reversing the order costs one working session and saves several. Time-box each step, note the actual minutes spent, and compare them across two Weeks so you can see which step keeps overrunning.

Write the finished sequence as a short checklist and keep it beside the ledger. What you are stabilizing is the reasoning routine, not a template of sentences, because the registered activity may demand a very different output shape from one Week to the next.

Reading the rubric row by row in Week 2

With one graded cycle behind you, read the current criteria beside the previous set rather than alone. Some rows recur across a course almost unchanged, and those are the rows worth building a permanent checking pass around. Others change verb, and the verb is the instruction. A row that asked you to describe a determinant and now asks you to analyze it has raised the demand from an accurate account to a decomposition that shows parts, relationships, and consequences.

Build the checking pass as a fixed list of questions derived from the recurring rows, and run it in the same order after every draft, so that quality control also becomes cadence rather than improvisation. Keep a note of which rows you had to reread to understand, because those are the rows most likely to be misread again under time pressure.

None of this substitutes for the live document. Your classroom rubric decides the criteria, the weights, and the version in force, and a criterion can be revised between Weeks without announcement, so open the current one every time rather than trusting the copy you saved.

4. Use evidence deliberately

Use current surveillance, policy, organizational, and peer-reviewed evidence at the same geographic and population level as 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.

Turning source work into a routine that compounds

The second Week is where a source habit either compounds or resets. Save the searches themselves, not only the results: the database, the terms, the filters, the date limits, and the number of records the search returned. A recorded search can be rerun, narrowed, or defended; a remembered one cannot. Keep the running log from the opening Week and add to it rather than starting a new list, so the shelf grows into an asset instead of being rebuilt from nothing each cycle.

Apply two different freshness rules, because this subject mixes two kinds of evidence. Data sources age quickly, so a baseline rate, a prevalence figure, or a policy status should be the most recent available and should carry its collection year in the sentence that uses it. Conceptual and theoretical sources age differently, and an older paper that established a construct can remain the correct citation for that construct while a current study is cited for current magnitude. Record which rule applies to each entry. Convert the log from a bibliography into a claims ledger by writing the usable finding and its limitation next to every item.

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

Test equity, feasibility, stakeholder effects, measurement validity, unintended consequences, and the boundary between association and causation.

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.

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

The first pitfall is rebuilding the workflow from scratch because the current activity looks unfamiliar. Output shape changes far more often than reasoning shape does. The fix is to keep the reasoning cadence fixed and let only the presentation layer vary, mapping the same population, determinant, stakeholder, and outcome work into whatever format the live instructions require.

The second pitfall is planning the discussion work as one block. An initial contribution and its replies have separate windows and separate expectations, and collapsing them means the replies are written last, fastest, and thinnest, which is exactly where the criteria for engagement usually sit. The fix is to schedule the initial contribution and each reply as separate calendar items with their own preparation time, then confirm the actual response window in the classroom rather than assuming it repeats.

The third pitfall is letting the source log drift into an alphabetical bibliography. A list of citations cannot tell you which claim is unsupported. The fix is to sort the log by claim rather than by author, so a claim with no entry beneath it becomes visible as a gap while there is still time to close it.

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