BUS484 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 management and organizational decisions method

For BUS484 Entrepreneurship, the working focus is this: Define the business problem, affected stakeholders, alternatives, evidence, resource consequence, risk, recommendation, and measure of success.

Challenge the main assumption, compare at least one viable alternative, quantify where the record permits, and attach a realistic implementation and measurement plan.

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 an evidence routine that survives the rest of the term

The second Week rewards process more than insight. Whatever the registered activity turns out to be, the underlying job at this stage is converting a set of opening claims into a repeatable habit of checking them, because an entrepreneurship course compounds: what goes unverified now gets carried, unexamined, into every later deliverable. Set up two parallel tracks and run both on a fixed schedule rather than in bursts.

The first track is conversation. Structured talks with people who actually operate in the space produce the evidence no database holds, but only if the questions ask about past behavior instead of future intention. Asking an independent trades contractor whether they would pay for a scheduling tool invites politeness. Asking what they used last month, how many hours it took, what it cost, and what finally made them switch away from the previous method produces a fact. Record answers as observations with a date and a role, never as endorsements.

The second track is the record. Published pricing, licensing requirements, association surveys, and public filings establish the outer boundaries that conversation cannot. Run the two tracks against each other. When an operator reports a price and the published rate card disagrees, that gap is itself a finding worth a paragraph, not an error to quietly resolve in favor of whichever number is more convenient.

Close by promoting claims explicitly. Give every claim from the opening submission a status of assumed, partly supported, or supported, and record what moved it. A stabilized week produces a shorter list of live assumptions than it started with, and a written trail explaining why each one moved.

Reading the rubric row by row

By the second Week there may be a returned item with criterion-level marks on it, and that returned rubric is the most useful document available. Put it beside the current activity's criteria and read them together. Rows tend to recur across a course: the same expectations for evidence, organization, application of concepts, and mechanics reappear under slightly different wording each Week. A row lost once will be offered again, which means the correction is worth more than the individual points already gone.

Separate the instructor's comment from the criterion it sits against. A comment explains a judgment; the criterion defines it. Students frequently rewrite the exact sentence a comment flagged and leave the pattern that produced it untouched across the rest of the draft. Read each comment, then find the row it belongs to, then search the whole document for other instances of the same behavior. One comment about an unsupported claim usually means several unsupported claims went unmarked.

Then read the current rubric for the boundary between adjacent bands. The wording that separates one band from the next is where the grading decision actually happens, and it is usually a matter of consistency, specificity, or completeness rather than a different idea. Note which of the three each row emphasizes and build the draft to satisfy that emphasis. The criteria posted in the live classroom remain the only authority on how any of this is scored.

Source work: keeping market evidence and market opinion apart

In venture research the fastest way to lose credibility is to let opinion wear the clothing of data. A consultancy's projection of category growth is a forecast built on assumptions the reader cannot inspect. An association's member survey has a sample, a method, and a response rate that can be examined. A government statistical series has a defined population and a stated collection method. These are not interchangeable, and a strong draft signals which kind of thing it is leaning on inside the sentence rather than leaving the citation to imply authority.

Start a source log this Week and keep it current, because retrofitting one in the final Week is the single most expensive recovery in the course. Give each entry a row: author or issuing body, year, type, the exact claim borrowed, the location, the retrieval date, and the section of the project where it will be used. Sort the log by section, not alphabetically, so gaps become visible as blank cells rather than as an uneasy feeling.

When a source enters the draft, lead with the point and follow with the support. Name the issuing body in the sentence when the body's identity matters to how the reader should weigh the claim, and stay silent about it when it does not. Where a number is quoted, carry its unit, its year, and its geography with it. A figure stripped of those three things cannot be checked, and an unverifiable figure is worth less than no figure at all.

Three pitfalls at the stabilizing stage and their fixes

The first is the leading question. Discovery conversations conducted by someone who wants a particular answer will produce that answer, and the resulting write-up rests on nothing. The fix is to script the questions before the conversation, keep them open and retrospective, and have someone else read the script for embedded conclusions. Any question containing the name of the proposed solution should be moved to the end, after the useful material has already been collected.

The second is treating discussion work as filler. Reply requirements in a business course frequently carry criteria of their own about substance, use of course material, and engagement with a classmate's specific reasoning. A post that agrees pleasantly and adds an anecdote satisfies none of them. The fix is to treat each reply as a short analytical paragraph: name the specific point being engaged, add evidence or a counterexample the original post did not have, and close with a question that could actually be answered.

The third is patching instead of stabilizing. After a first graded item, the temptation is to fix what was marked and move on. The fix is to write a one-page working standard for yourself covering how paragraphs open, how evidence is introduced, how citations are formatted, and what the final check includes, then apply that standard to every remaining Week. A standard written once and reused beats good intentions repeated weekly.

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