BUS499 Week 3 planning manual

1. Capture the live Week 3 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 research and synthesis method

For BUS499 Senior Capstone, the working focus is this: Turn a bounded question or practice problem into a traceable line from purpose through evidence and method to a conclusion no broader than the record supports.

Check alignment among problem, question, evidence, method, analysis, limitations, and recommendation; one changed element may require the rest of the chain to change.

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 3 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 4. 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: moving from framework labels to stated mechanisms

The middle of the term is where capstone analysis either becomes real or stalls at the level of labels. A named framework applied without reasoning produces a list, and a list scores as a list no matter how neatly it is formatted. If the registered work invites a structured industry or internal analysis, the deepening move is to convert each entry from a label into a causal sentence that reaches an endpoint.

Take a claim that buyer power is high in a given sector. As a label it contributes nothing. As reasoning it runs like this: the three largest purchasers account for most sector volume, switching between suppliers costs those purchasers almost nothing because the product is standardized, published price benchmarks let them compare offers directly, and the combined effect is sustained downward pressure on gross margin. Now the entry has a consequence, and the consequence can be carried into a recommendation. Apply the same conversion to internal analysis: a resource is not a strength because the firm owns it, but because buyers value it, competitors rarely hold it, imitation is hard, and the firm is organized to use it.

Comparative reasoning deepens the same way. When two options are weighed, state the criteria before the comparison, apply the same criteria to both options, and say plainly which criterion decided the outcome.

Reading the rubric row by row for relationship verbs

At this stage the criteria usually escalate in verb strength, and the rows that separate a competent submission from a strong one are those asking for relationships rather than inventory. Go through the posted rubric and mark every row whose verb implies a connection: analyze, compare, examine the relationship, assess the effect. For each marked row, write the unit of comparison the row implies. A row asking you to compare competitive positions implies at least two named firms and one shared set of criteria. A row asking you to analyze an effect implies a cause, an outcome, and a mechanism running between them.

Then test each marked row against your current draft with a blunt question: does the text contain a sentence stating the relationship explicitly, or does it merely place two facts near each other and hope the reader connects them? Proximity is not analysis, and a reader grading against criteria does not award the connection a writer left implicit.

Read the rows for scope signals as well. Some criteria reward breadth across several factors, others reward depth in a few. Answering a depth row with breadth produces thin coverage everywhere and full credit nowhere. The posted rubric in the live classroom is the authority on which of the two the current work expects.

Source work: matching the evidence type to the claim type

Deeper analysis fails most often because the class of evidence does not fit the class of claim. Sort your claims into four kinds and route each to the right kind of source. Claims about market structure, meaning size, concentration, growth, and segmentation, need industry data or government statistical series with an explicit reference period. Claims about a firm's own performance need that firm's reported financial statements rather than a secondary summary of them. Claims about how customers or employees behave need survey evidence or peer-reviewed studies rather than assertion. Claims that one thing caused another need either an empirical study or an argued mechanism accompanied by an honest statement of what the argument cannot establish.

Triangulate anything that matters. When two independent sources give different figures for the same quantity, do not silently pick the more convenient one. Report the range, name both sources, and explain which you rely on and why, usually on grounds of recency, methodology, or closeness to the original data.

Keep all figures inside a single comparison anchored to the same period. A margin from one year set beside a competitor's margin from three years earlier is not a comparison, and a reader who checks the citation dates will find the mismatch quickly.

Three Week 3 pitfalls and how to fix them

The first pitfall is using a framework as decoration. A four-quadrant table or a five-heading structure appears, gets populated with short phrases, and is never referred to again in the analysis that follows. The fix is to require every framework entry to produce at least one sentence elsewhere in the draft that uses it, then delete any entry that cannot.

The second pitfall is mixing reference periods inside a single argument. This usually happens innocently, because sources were gathered at different times and their dates were never recorded beside the numbers. The fix is to add a period column to the source register and to state the period in the text whenever a figure is quantitative.

The third pitfall is letting an undated secondary page supply a competitor's numbers. Aggregator sites and content marketing pages republish figures without provenance, and the figure often turns out to be several years old or an estimate presented as a measurement. The fix is to trace every competitor figure back to a filing, an official release, or a named research house, and to drop the claim when no such origin exists. A narrower claim that is fully supported is worth more against the criteria than a bold claim resting on a source nobody can verify.

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 3 activity, so this manual never assigns it one.

Week 3 questions