BUS454 Week 2 planning manual

1. Capture the live Week 2 packet

Create one row for every visible activity. Record its exact name, type, complete instructions, rubric or grading criteria, points and course weight, due date with time zone, permitted and required resources, length and file format, discussion reply rules, group or supervisor dependencies, attempt limits, submission location, and instructor announcements. Save the rubric version with the working file.

2. Translate criteria into visible proof

Rewrite each criterion as a testable question: what must the reader see to award this row? Pair it with the concept, evidence, example or calculation, reasoning step, and location where the proof will appear. This prevents a polished response from missing a small but expensive instruction. When the Week contains several activities, map each separately before deciding the order of work.

3. Apply the policy and ethical reasoning method

For BUS454 Ethical Decision Making for Business, the working focus is this: Identify the controlling rule or principle, distinguish facts from assumptions, compare affected stakeholders, and defend an action while acknowledging constraints and competing obligations.

Verify authority and dates, test the recommendation against a plausible counter-position, and separate legal requirements from ethical judgment.

Use course materials first when the live instructions require them. Add outside evidence only when permitted, verify every source directly, and keep notes that distinguish the source's claim from the student's interpretation. For calculations or structured analyses, retain inputs, units, assumptions, intermediate steps, and an independent check.

4. Build a student-owned response

Draft from the evidence map rather than from a generic sample. Open each section with its purpose, make the claim proportional to the evidence, explain the relationship the rubric asks for, and close with the decision, implication, or transition the reader needs. A tutor may demonstrate a parallel problem, question the logic, or comment on a student draft; the student's own judgment, context, language, verification, and final version must remain visible.

5. Run the Week 2 quality gate

Compare the finished work line by line with the live instructions and rubric. Check factual support, evidence currency, calculations, citations, headings, file type, accessibility, confidentiality, originality, and the stated audience. Confirm that replies, approvals, group actions, proctored steps, or supervised requirements have actually been completed by the student where the registered Week requires them.

6. Submit and close the loop

The student performs the final upload or entry, opens the submitted artifact to confirm it is readable, and saves the receipt. When a grade or feedback arrives, record the criterion-level result, instructor comment, required correction, and lesson for Week 3. If an attempt is missing, late, or technically broken, use Aspen's official channel immediately rather than assuming the gradebook will repair itself.

Worked reasoning: building a stakeholder map that keeps working

Week 2 rewards routine, so build the analytical tool once and reuse it for the rest of the term. Take a hypothetical retailer replacing manual scheduling with a system that assigns shifts automatically from forecast demand. A weak map lists employees, managers, and customers. A working map adds three columns that force judgment: what each group stands to gain or lose in concrete terms, what obligation the organization owes that group and where the obligation comes from, and how much standing the group has in this particular decision.

Standing deserves its own thought. Groups differ in the power to affect an outcome, in the legitimacy of their claim, and in the urgency of their situation, and a group can rank high on one and low on another. Hourly staff whose income becomes unpredictable may hold a strong claim with almost no power, which is precisely the combination ethical analysis exists to surface. Investors may hold power and legitimacy without urgency.

Then convert the map into sentences. Each row should yield one claim the paper can defend, such as a statement that unpredictable scheduling shifts business risk onto the people least able to absorb it. A table that never becomes prose is decoration. Keep the finished template in your course file so the next week starts from a tool rather than a blank page. Whether a table belongs in the deliverable at all is settled by the activity posted in your registered course.

Reading the rubric row by row once the first score posts

The moment criterion-level marks are visible, the rubric stops being abstract. Put the criteria and the returned work side by side and, for every row, record three things: the level awarded, the exact words in the descriptor you did not satisfy, and the sentence in your own draft that was supposed to satisfy it. The third item is the diagnostic. Sometimes that sentence is missing entirely; more often it exists but sits in the wrong place, buried in a paragraph about something else where a reader scanning for that criterion will never find it.

Sort the rows by points lost rather than by how the feedback felt. A gentle comment on a light row deserves less of your attention than silence on a heavy one. Where an instructor left no comment and the level awarded was not the highest, the descriptor language itself is the feedback, so read it literally rather than generously.

Build a short correction list with one line per row: what the grader wanted to see, what you will do differently, and where in the next deliverable it will appear. Carry that list into every remaining week and check it before submitting instead of afterward. If the criteria posted for the current week differ from the last one, the current posting governs, and comparisons across weeks are for diagnosing your habits, never for predicting the next task.

Turning rubric verbs into searches, and moving a source into a paragraph

Search terms come from the criteria, not from the topic alone. If a row asks you to evaluate a practice against a standard, useful queries pair the subject with words such as framework, governance, compliance, or code of conduct, rather than repeating a company name. Work through the library collections your course points to before the open web, and prefer scholarship that reports how it reached its conclusion.

Currency rules differ by family. A theoretical framework can be decades old and still authoritative, because foundational work in ethics stays in use long after publication. An empirical finding about current practice, a regulation, or an enforcement posture ages quickly, and anything older than roughly five years should be checked against something current before it carries weight. Legal material must be checked for amendment, not merely for date.

Moving a source into a paragraph has a fixed shape. Write your own claim first, as a complete sentence in your own words. Place the evidence behind it with a signal phrase naming who found what. Then explain, in your voice, why that evidence supports this claim rather than a neighboring one. Skipping the third move produces a draft stitched together from other people's sentences. Permitted resources are set by the live instructions, so confirm outside sourcing is allowed before building on it.

Three pitfalls that surface once the routine begins

The first is copying the previous submission's structure onto a different task. Reusing a workflow is the entire point of this stage; reusing an outline is not, because a different set of criteria may reward a different sequence of moves. The fix is to rebuild the outline from the current criteria each time, then check whether your habitual structure happens to fit it.

The second is treating feedback as a comment on tone. A note that a paragraph is unclear is usually a note that a claim is unsupported, or that two ideas are competing for one paragraph. The fix is to translate each piece of feedback into a structural instruction before acting on it, and to write the translation down so you can tell later whether the change worked.

The third is discussion work written as agreement. Where a week includes participation, replies that restate a classmate's point and praise it earn very little, because they add no reasoning. The fix is to give every reply one identifiable job: introduce evidence the original post lacked, name an assumption it rests on, or apply its logic to a situation where the result flips. Whatever reply count, timing, and depth the registered week specifies is the requirement you actually have to meet.

Source boundary

Aspen University's official FAQ verifies that courses run eight weeks and that each Week's activities are organized in the online-classroom syllabus. The active catalog verifies this course code and title. Neither public source identifies the student's current Week 2 activity, so this manual never assigns it one.

Week 2 questions