Assessment 2 of MBA-FPX5016 is the improvement case: a fix aimed at a proven constraint, its gain computed, its cost attached, its payback shown, and its rollout sequenced. Think of it as the proposal a plant manager would either fund or kill in one meeting, graded criterion by criterion the FlexPath way. This manual walks the method our tutors use, gives a structure keyed to the criteria, and annotates an excerpt at the scoring register. Rather skip the drafting? A premium original sample for this exact deliverable arrives in 24 to 48 hours, revised free until the guide is satisfied.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How Assessment 2 is scored
Each criterion on the guide resolves to one of four levels, and on an improvement case the levels separate on money and sequence:
| Level | What it means on an improvement case |
|---|---|
| Distinguished | The fix targets the constraint the analysis proved, the gain and cost are both computed, payback is stated, and the rollout carries steps, owners, and named barriers. Read each criterion's top cell for its particular extra demand; the guide always tells you. |
| Proficient | A supported, costed recommendation whose arithmetic stops at the gain. Fundable, but not yet the paper a CFO signs without questions. |
| Basic | A sensible suggestion carried by adjectives, faster, leaner, more efficient, where the criteria wanted numbers. |
| Non-performance | A required element absent, usually the cost figure or the implementation plan. Absence, not weakness, is what zeroes a criterion. |
Your scoring guide decides the exact deliverable, but across 5016 the second assessment typically builds on the first: the constraint you computed there is the target you fund here. If your Assessment 1 math was thin, fix it now, because a recommendation aimed at a step that was never proven to bind cannot reach the top column no matter how well it is costed.
The method, step by step
-
Rebuild the guide as a proposal skeleton
Before touching the case, lay the criteria out as the bones of a funding proposal: problem, remedy, cost, payback, plan, proof. Each criterion becomes a section heading with its Distinguished text pinned beneath it. Anything you feel like writing that has no heading to live under is cut before it costs you time.
-
Price the problem before proposing anything
An improvement only registers against a baseline, so compute what the current state costs: units not produced, hours paid for waiting, orders refunded, whatever your case's numbers support. Put a weekly or annual figure on it. That single number does two jobs, it justifies the spend later and it gives the evaluator the stakes up front.
-
Aim the fix at the constraint
Money spent anywhere except the binding step buys nothing, which is the most quietly tested idea in this course. State explicitly which step binds, cite the analysis that proved it, and show that your remedy adds capacity there. If two fixes compete, choose by computed effect on throughput, and say on the page why the loser lost.
-
Compute gain, then cost, then payback
Three numbers in a fixed order: the output or time the fix buys, what it costs installed, and how many weeks of gain repay the spend. Keep the arithmetic visible so the reader can rerun it, and where an input is uncertain, run the payback at a high and a low value. A range honestly shown beats a point estimate quietly hoped.
-
Sequence the rollout and name its barriers
An implementation plan is verbs with dates: who orders, who installs, who trains, in what order, over which weeks, with what disruption to current output. Then name what could stall it, a supplier lead time, an operator learning curve, a cash timing issue, and pair each barrier with its mitigation. Guides in this course tend to hold a criterion for exactly this, and generic risk language leaves it at Basic.
-
Grade your own proposal before the evaluator does
Walk the draft against the guide cell by cell and ask of each criterion: would a skeptical reader call this Distinguished using only what is on the page? Wherever the honest answer is no, the gap is almost always a missing number, not missing prose. Close it, then submit with enough week left to absorb a revision request.
A structure that maps to the criteria
Targets below are drafting guides from our files, nothing official; sections stretch wherever your criteria demand more coverage, and a guide's requirement always outranks a word count.
| Section | What it must do | Guide |
|---|---|---|
| Introduction and baseline | The operation, the constraint carried over from analysis, and the single number that says what standing still costs. | ~150 words |
| The problem, priced | The current state quantified: lost throughput, waiting time, defect cost, converted to a weekly or annual figure. | ~250 words |
| The recommendation | The fix described concretely, aimed at the binding step, with its capacity effect computed and alternatives dismissed by number. | ~300 words |
| Cost and payback | Installed cost, weekly gain, payback period, with sensitivity shown on the input that matters most. | ~250 words |
| Implementation and barriers | Steps with owners and rough dates, plus each realistic obstacle paired with its mitigation. | ~250 words |
| Metrics and verification | Baseline against target on named measures, and the cadence at which results get checked. | ~150 words |
| References | Data cited at the number, methods grounded in current operations sources, APA matched in both directions. | as needed |
Annotated sample excerpt
A passage from an original model in our files, chosen because it does the three moves this deliverable is graded on inside four sentences. Learn the pattern, then run it on your own case.
Millbrook Baking Company's oven is not the constraint; the proofing cabinet ahead of it is, and the oven sits idle roughly 90 minutes per shift waiting for dough that is not ready.1 A second cabinet costs 18,400 dollars installed and lifts output from 240 to 300 loaves per shift, which at a contribution margin of 1.40 dollars per loaf across twelve shifts a week returns 1,008 dollars weekly.2 The spend repays itself in nineteen weeks, comfortably ahead of the fall wholesale contracts now in negotiation, and if margin softens to 1.10 the payback stretches to 24 weeks and the case still clears.3
- 1Opens by correcting the obvious diagnosis with observed idle time, proof the fix targets the constraint rather than the loudest complaint.
- 2Gain and cost computed in the same breath, every input named so the reader can rerun the arithmetic. This is the sentence the funding criterion pays for.
- 3Payback stated, tied to a business deadline, and stress-tested at a worse margin. The sensitivity line is the Distinguished move most drafts skip.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Fixing the loudest problem. The complaint everyone mentions is rarely the step that binds; a remedy aimed off the constraint is money spent on nothing, and evaluators look for exactly that.
- An unpriced baseline. With no dollar figure on the current state, the gain has nothing to stand against, and the whole case floats.
- A gain with no invoice. Benefits computed while cost stays vague reads as a wish; the criterion wants both sides of the ledger.
- "Then implement the recommendation." A plan without steps, owners, and dates is a restatement, and the implementation criterion scores it as one.
- Metrics that cannot fail. Success measures like improved efficiency verify nothing; a named metric with a numeric target and a check date can actually be missed, which is what makes it credible.
Pre-submission checklist
- The current state priced in a weekly or annual figure the reader can recompute
- The fix explicitly tied to the constraint your analysis proved binding
- Gain, installed cost, and payback all shown, with sensitivity on the key input
- Rollout sequenced with steps, owners, and rough dates
- Every realistic barrier named and paired with a mitigation
- Draft graded against each criterion's top cell, submitted with revision room
Want the proposal built with backup?
Send the scoring guide, your Assessment 1 numbers if you have them, and the case data. Our eight-person pipeline, research analyst and two QA reviewers included, returns a premium original improvement case costed to the Distinguished column in 24 to 48 hours, with free revisions until it lands. This is the deliverable the course was pointed at all along; make it the strongest thing in your courseroom.