| Course | BUS FPX 4993 Business Capstone Project |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Cross-functional analysis |
| Length | About 1,180 words, 6 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business |
| Updated | September 2026 |
Free sample paper for BUS FPX 4993 Assessment 2
Analyzing Late Deliveries Across Functions at a Wholesale Bakery: One Problem Through Each Lens, Collisions Made Explicit, Conflict Kept Apart From Time Horizon, Uneven Evidence Admitted, and Where the Problem Lives
Student Name
Capella University
BUS FPX 4993: Business Capstone Project
Instructor Name
Month Day, Year
The Problem Restated
Ridgeline Bread Company's on-time wholesale delivery rate fell from 94% to 81% in 12 months. The problem definition showed that lateness tracks the time the last oven load comes out, which moved from 4:50 a.m. to 5:40 a.m., and that the bakery's product count rose from 38 to 61. This analysis looks at the same problem through four functions to find out why production is finishing later.
The Same Problem Through Each Lens
Operations: the production manager's records show that the number of product changeovers per night, when the bakery switches mixers, dividers, and ovens from one product to another, rose from 26 to 44. Each changeover takes 8 to 15 minutes. A new sourdough line added a year ago needs a long proof that ties up proofing racks. Operations sees the problem as too many products for one night's capacity. Goldratt and Cox (1984) argue that a system's output is set by its constraint; at Ridgeline, the ovens and proofing racks between about 1:00 and 5:00 a.m. are the constraint, and every changeover spends that time without producing bread. Sales: the sales manager sees the problem as production failing to keep up with customer demand. Sales representatives have added products at customers' request, often custom items for a single café, and accept orders and changes until 6:00 p.m. the day before. About 12% of orders change after 3:00 p.m. Finance: the controller's analysis shows that the 15 lowest-volume products together make up 2.8% of wholesale volume but cause about 30% of nightly changeovers. Several have lower margins because of small batch sizes. Finance sees the problem as unprofitable complexity. Human resources: driver turnover reached 40% last year, and new drivers take about 20 minutes longer per route for their first two months. Human resources sees part of the problem as driver retention. Each function sees a real part of the problem, and each sees it as someone else's fault.
Collisions Identified Explicitly
The functions' goals collide in specific places. Sales and operations collide over the product list and the order cutoff: sales wins accounts by saying yes to custom products and late changes, while operations loses production time to each. Finance and operations collide over overtime: operations could start earlier to finish on time, but finance has pushed to cut overtime costs, which rose 18% last year. Finance and human resources collide over driver pay: raising pay might reduce turnover but adds cost. Naming the collisions makes clear that no single function can solve the problem alone.
Conflict Separated From Horizon
Some collisions are real conflicts of interest; others are differences in time horizon that disappear when both sides look at the same period. The overtime collision is mainly one of horizon: finance is measured on this year's costs, but losing Harvest Fresh would cost about 273,000 dollars of contribution a year, far more than the overtime needed to prevent it. Over a longer horizon, finance and operations want the same thing. The order cutoff collision is partly horizon too: sales fears losing orders this month if the cutoff moves earlier, but it is losing accounts this year because of lateness. The product list is a real conflict: some customers genuinely want custom items, and dropping them will cost some sales that no time horizon recovers.
Uneven Evidence Admitted
The evidence is uneven, and the analysis says so. Operations evidence is strong: oven logs, changeover counts, and scan times are recorded. Finance evidence is strong on volume and cost by product. Sales evidence is weaker: the claim that customers would leave if custom products were dropped comes from representatives' judgment, not from customer data, though interviews with 20 large customers found that only 3 considered any of the 15 low-volume products essential. Human resources evidence on the effect of driver turnover rests on a comparison of route times for new and experienced drivers over only four months. Conclusions that depend on the sales and human resources evidence carry more uncertainty. Strong evidence from one function and anecdote from another should not be weighed as equals.
Where the Problem Actually Lives
The problem lives between functions, not inside any one of them. No one at Ridgeline decides whether a new product should be added; sales representatives add products for customers, and production absorbs them. No one owns the order cutoff; it has stayed at 6:00 p.m. because it always has been. The result is that the product list grows one reasonable request at a time until the night's production no longer fits before the trucks leave. Operations cannot fix this, because it does not control what is sold; sales cannot fix it, because it does not see the production cost of each addition. The gap is a missing decision process at the interface of sales and production, with finance's product cost data never reaching the people who add products.
How Each Function Measures Itself
Part of the reason the problem sits between functions is that each function is measured on something different. Sales representatives earn commission on revenue, so every added product that wins an order helps them, and none of the production cost shows up in their numbers. The production manager is judged on labor cost per pound baked, which rises with every changeover but says nothing about delivery times. The controller reports overtime and margins monthly. No measure that anyone at Ridgeline is judged on includes on-time delivery, so the result that customers care about most is the one no function owns. Kaplan and Norton (1996) argue that measures should connect each unit's work to the outcomes the organization is trying to achieve; Ridgeline's measures do not.
Secondary Causes
Driver turnover and route changes contribute, but less. On days when the last load finished early, deliveries were on time 93% of the time even with new drivers, which suggests production timing explains most of the decline. Driver retention remains worth addressing separately.
Implications for Options
Options should address the decision gap as well as its effects. An option that only adds production capacity would relieve the symptom until the product list grows again. An option that changes how products are added and when orders close would address the cause but must be weighed against the sales it may cost. The next stage will price these options.
Conclusion
Operations sees too many products, sales sees demand outpacing production, finance sees unprofitable complexity, and human resources sees driver turnover. The collisions over overtime and order cutoff are largely differences in time horizon, while the product list is a real conflict. Evidence is strongest for operations and finance. The problem lives in the missing decision process between sales and production, where products are added without anyone weighing their cost to the night's schedule.
References
Goldratt, E. M., & Cox, J. (1984). The goal: A process of ongoing improvement. North River Press.
Kaplan, R. S., & Norton, D. P. (1996). Using the balanced scorecard as a strategic management system. Harvard Business Review, 74(1), 75-85.
Reading the BUS-FPX4993 Assessment 2 instructions
Assessment 2 in BUS FPX 4993 has you analyze the problem from Assessment 1 through each business function. For each one, such as operations, marketing, finance and human resources, you examine the problem with the evidence and reasoning that function would use and state what it would do about it. You then identify where the functions' views collide, distinguish true conflicts from differences in time horizon, admit where evidence is weaker for some functions than others and conclude where the problem is rooted. The analysis should lead toward the options in Assessment 3. Course material from each function and the organization's data support the analysis.
How this BUS FPX 4993 Assessment 2 example is built
Each function, then the collisions. The opening carries the problem forward from the definition in a short paragraph. Each functional block then analyzes the same problem with the evidence and reasoning that function actually uses, and each ends by stating what that function would do about it. A collision block follows and is the substance: it puts those answers side by side and identifies where they cannot all be satisfied, separating a genuine conflict from a difference in time horizon. An agreement block notes where two or more functions want the same thing, since that is what any recommendation can be built on cheaply. A root cause block asks which function's domain the problem actually lives in. The closing states what the analysis could not establish and why.
Reading the BUS FPX 4993 Assessment 2 scoring guide
The scoring guide weighs the functional analyses, the collisions, the treatment of evidence and the conclusion about where the problem lives. Each functional analysis reaches Distinguished when it uses that function's own evidence and reasoning, such as route times for operations and customer penalties for marketing. Collisions score higher when stated explicitly, like the sales team adding late orders that the bakery cannot bake in time. Separating conflict from horizon earns credit, since some disagreements are about short-term versus long-term rather than goals. Uneven evidence is judged on whether it is admitted. The conclusion should place the problem in a specific process. Implications for options should follow. Distinguished analyses show that the functions see different problems.
Common BUS FPX 4993 Assessment 2 mistakes, and how to avoid them
Cross-functional papers often write four separate summaries and never bring them together. Another weakness is analyzing each function with generic theory instead of this bakery's data. Collisions between functions are smoothed over, though they are usually where the problem lies. All disagreements are treated as conflicts, missing that some are about timing. Weak evidence for one function is hidden. The conclusion restates the problem instead of locating it. Ending each functional section with one line on what that function would do, then setting those lines side by side, reveals the collisions quickly and gives the paper a clear route to its conclusion about where the problem actually lives.
Get a BUS FPX 4993 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and your BUS FPX 4993 scoring guide, along with the problem definition your first assessment produced. We write a custom example against those criteria and return it in 24 to 48 hours. The first custom sample is free, and the collision section is what separates a capstone from a long course paper. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More BUS FPX 4993 papers and BS in Business samples
- BUS FPX 4993 Assessment 1: Problem Definition and Scope
- BUS FPX 4993 Assessment 3: Options Priced and Compared
- BUS FPX 4993 Assessment 4: Implementation and Presentation
- ECO FPX 1150 Assessment 2: Financial Decision Paper
- BUS FPX 4802 Assessment 2: Transition and Communication Plan
- BUS FPX 1011 Assessment 2: Planning Memo
- BUS FPX 4801 Assessment 2: Stakeholder and Responsibility Analysis
BUS FPX 4993 Assessment 2 questions, answered
Do all four functions have to be covered?
Where your instructions require it, yes, and depth beats coverage. If a function genuinely is not implicated, say so and argue why rather than manufacturing a paragraph. Forcing an operations analysis onto a purely commercial problem produces padding that a marker recognizes immediately. Depth is what the criteria weigh.
What if the functions all agree?
Then check whether you analyzed them independently. Genuine agreement happens and is worth reporting, since it makes the recommendation much easier to fund. But four functions agreeing on everything usually means one analysis was written and then rephrased three times. Independent analysis is the check worth running on yourself.
How do I analyze the people side with no HR data?
Use what is observable: turnover you can see, roles that are hard to fill, what the work actually demands of somebody doing it. Say how you know. A people analysis built from observation and described as such is legitimate evidence, while one built from assumption about morale is not.
Where can I find a free BUS FPX 4993 Assessment 2 sample paper?
This page presents the full cross-functional analysis of the late deliveries, with each lens applied, collisions made explicit, conflict kept apart from time horizon and the problem located. The options unit follows.
What is a collision between functions in BUS FPX 4993 Assessment 2?
A point where what one function does to meet its goals causes problems for another, such as sales accepting late orders that production cannot fill on time. Collisions often reveal the root of the problem.