| Course | BUS 721 Issues in Optimizing Operations (BUS/721) |
|---|---|
| Week | 8 |
| Paper type | Doctoral recommendations paper |
| Length | about 1,158 words, 4 double-spaced pages plus title page and references |
| Format | APA 7 student paper |
| School | University of Phoenix |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for BUS 721 Week 8
Quality First, Then Visibility, Then Speed: Integrated Recommendations for Optimizing Operations at Tri-State Cabinet
[Student Name]
University of Phoenix
BUS/721: Issues in Optimizing Operations
Week 8 Assignment
[Instructor Name]
[Date]
Tri-State Cabinet Company and all figures are composites written for a model paper.
Two years ago, the composite cabinet maker Tri-State set out to win home builders by delivering complete orders quickly and dependably, but its operations were designed for low cost. Only 73 of every 100 builder orders arrive complete and on time, and average lead time is 41 days against a 21-day goal. Over seven weeks, analysis traced the gap to finishing rework, fragmented planning, poor visibility, high utilization at the bottleneck, misaligned incentives and a history of fading initiatives. A list of good ideas is not a plan; a plan says which idea comes first and why the others depend on it. This paper presents integrated recommendations.
Executive Summary
Tri-State should optimize operations in three phases over three years: build quality at the finishing lines, create visibility and integrated planning across plants and then increase speed through priority rules and targeted capacity. Supporting changes to scorecards, leadership and implementation practices will sustain the gains. The plan costs about $8.2 million and is expected to raise on-time complete delivery above 92 percent and cut lead time to about 21 days.
The Logic of the Sequence
Research on cumulative capabilities proposes that lasting improvement builds quality first, then dependability, then speed and cost (Ferdows & De Meyer, 1990). Tri-State's data support this order: rework causes nearly half of late orders, so speeding up first would multiply disruptions and frustrate the crews asked to move faster.
Recommendation One: Fix Finishing Quality
Run the Six Sigma project on color variation and lean maintenance practices on dust, aiming to cut rework by more than half in the first six months and to about 2 percent by year end. Cost: about $600,000, including a trained specialist, measurement equipment and operator time.
Recommendation Two: Protect Improvement Time
Give every finishing crew a fixed weekly block of improvement time that survives peak season, avoiding the capability trap in which pressure to produce crowds out improvement (Repenning & Sterman, 2002).
Recommendation Three: Build Order Visibility
Implement production scanning and the order visibility dashboard, with data definitions and governance, within nine months. Cost: about $1.4 million, most of it for integration and scanning hardware.
Recommendation Four: Implement ERP in Phases
Implement a cloud ERP beginning with York in winter, then Hagerstown and Winchester, standardizing processes and cleaning data first. Cost: about $5.4 million including internal time, the largest single investment in the plan.
Recommendation Five: Adopt Due-Date Priority Rules
Use the hybrid due-date and style rule tested in simulation, reducing late orders with modest changeover increases. Cost: minimal, though schedulers will need two days of training and a month of coaching.
Recommendation Six: Add Peak Finishing Capacity
Staff finishing for part of a second shift in the busiest months, bringing utilization down toward 80 percent and shortening queues. Cost: about $420,000 a year when used.
Recommendation Seven: Align Scorecards
Replace cost-per-unit scorecards with balanced measures including on-time complete delivery, first-pass yield and data accuracy, so managers are rewarded for the strategy rather than penalized for supporting it.
Recommendation Eight: Sustain Leadership and Implementation Climate
Create an implementation climate in which using new systems and practices is expected, supported and rewarded, through training, super-users and visible leadership (Klein et al., 2001). Share ownership among several leaders so progress does not depend on one champion.
How the Recommendations Reinforce Each Other
Quality improvements make schedules reliable, which makes visibility data meaningful and priority rules effective. ERP supports integrated planning and data. Aligned scorecards and leadership sustain all of it. Powell (1995) found that tacit, cultural features drove quality management results more than tools, a reminder that recommendations seven and eight underpin the rest.
Timeline and Owners
Year one covers recommendations one, two and three and ERP preparation, owned by the York plant manager, the quality director and the IT director. Year two covers ERP rollout at York and Hagerstown, due-date rules and the first peak-season capacity shift, owned by the operations director. Year three completes ERP at Winchester and stabilizes measures, owned by the chief operating officer. Scorecard changes take effect at the start of year one so incentives support every phase.
What Leaders Must Do Differently
The plan requires leaders to change habits as well as approve spending. Plant managers must accept short-term cost increases from smaller batches and protected improvement time. Executives must keep reviewing delivery and quality measures through the long middle of the ERP project, when attention typically drifts. The chief operating officer must resolve disputes between plants about standard processes rather than letting each plant keep its own methods.
If Early Results Disappoint
If rework does not fall below 4 percent within nine months, the team will review the Six Sigma project's findings with outside experts before proceeding to speed-focused changes. If the ERP go-live at York produces a deeper dip than expected, rollout to Hagerstown will be delayed until York stabilizes. If builders begin leaving before improvements appear, Tri-State will offer its largest builders dedicated order coordinators as a bridge.
Communicating the Plan
Employees will hear the plan from plant managers in shift meetings, with the reasons for the sequence explained in plain terms: fix quality first, then see every order, then speed up. Builders will receive a summary of improvements and the timeline, building confidence that delivery will improve.
Costs and Benefits
Total cost over three years is about $8.2 million, spread unevenly with the ERP concentrated in year two. Expected annual benefits by year three include about $900,000 in reduced rework, $500,000 in fewer expedited shipments and retained or new builder business estimated at $3 to $5 million in gross margin a year.
Risks and Governance
Risks include ERP delays, a deeper post-implementation dip, leadership attention fading and data problems. A steering group led by the chief operating officer will review progress monthly, with early warning measures and contingency plans.
Lessons From Earlier Initiatives Applied
The plan reflects lessons from Tri-State's failed scheduling system and lean program. Users help design new processes, data is cleaned before systems go live, training is hands-on and repeated, measures reward the new practices and ownership is shared among leaders. Each lesson addresses a specific cause of earlier failure identified in the implementation analysis.
Measures
The monthly report will track on-time complete delivery, lead time, rework rate, finishing queue time, system use rates, data accuracy and builder satisfaction, reported monthly.
Contribution to Research
Tri-State's experience can test whether the cumulative capability sequence holds in semi-custom multi-plant manufacturing and whether protected improvement time prevents capability traps. Documenting results before and after each phase would provide useful evidence for other mid-size manufacturers facing similar choices.
Conclusion
Tri-State can align operations with its delivery strategy by building quality first, then visibility and integrated planning, then speed, supported by aligned scorecards and sustained leadership. Research and the company's data justify the sequence, and careful governance and measurement will show whether the plan works and what it teaches.
References
Ferdows, K., & De Meyer, A. (1990). Lasting improvements in manufacturing performance: In search of a new theory. Journal of Operations Management, 9(2), 168-184. https://doi.org/10.1016/0272-6963(90)90094-T
Klein, K. J., Conn, A. B., & Sorra, J. S. (2001). Implementing computerized technology: An organizational analysis. Journal of Applied Psychology, 86(5), 811-824. https://doi.org/10.1037/0021-9010.86.5.811
Powell, T. C. (1995). Total quality management as competitive advantage: A review and empirical study. Strategic Management Journal, 16(1), 15-37. https://doi.org/10.1002/smj.4250160105
Repenning, N. P., & Sterman, J. D. (2002). Capability traps and self-confirming attribution errors in the dynamics of process improvement. Administrative Science Quarterly, 47(2), 265-295. https://doi.org/10.2307/3094806
What the BUS 721 Week 8 instructions ask
BUS 721 closes with a request for integrated recommendations that would optimize an organization's operations. Common requirements include summarizing the analysis, presenting prioritized and sequenced recommendations, grounding each in research and organizational evidence, estimating resources and benefits, addressing implementation risks and governance, defining measures and reflecting on contributions to theory and practice. Many prompts ask for an executive summary. Integrate rather than repeat earlier weeks, justify sequence, show numbers and cite sources in APA format. Make the logic of the sequence explicit, so readers see why each step depends on the one before. Include a short executive summary that a busy leader could read in two minutes.
How this BUS 721 Week 8 example is built
Seven weeks of analysis at a cabinet manufacturer converge on a plan, and the paper presents it. The sequence follows research on cumulative capabilities: quality first, then visibility and integrated planning, then speed. Eight recommendations include a finishing improvement project, protected improvement time, order visibility dashboards, a phased ERP, due-date priority rules, peak-season finishing capacity, aligned scorecards and sustained leadership. Costs total about $8.2 million over three years, with expected gains from retained builders, lower rework and fewer expedites. Risks, governance and measures follow, along with owners, a timeline and fallback plans, and the paper proposes how Tri-State's results could inform research.
BUS 721 Week 8 grading rubric: where the points go
Strong recommendation papers are integrated, sequenced and evidence-based. Faculty credit a concise summary of the problem, recommendations that follow from the analysis, a sequence justified by research and dependencies, realistic costs and benefits, attention to implementation risk and governance, clear measures and reflection on contributions to knowledge. Showing how recommendations reinforce one another demonstrates systems thinking. An executive summary and accurate APA style finish the work. Faculty also look for a candid section on what could go wrong and what the organization would do if early results disappoint, since recommendations that assume everything will go to plan are less useful to leaders than ones that anticipate setbacks. Assigning owners and dates to each recommendation shows the plan is ready to act on.
BUS 721 Week 8 help: mistakes to avoid
Students often list recommendations from each week without integrating them or explaining which depends on which. Show how they connect and why the order matters. Another frequent gap is omitting costs and benefits. Estimate them, even roughly. Students also forget implementation risks identified earlier. Address them. Avoid introducing new analysis at the end; the final paper should draw on what earlier weeks established. Keep recommendations specific, with owners and dates, and limit them to those the analysis actually supports. Define measures. Finally, reflect on what the organization's experience could add to research, since a DBA connects practice to scholarship. Plan what the organization will do if the first phase disappoints. Name the person accountable for each recommendation.
Related BUS 721 sample papers
Other BUS 721 week samples
- BUS 721 Week 1: Operations and Corporate Strategy
- BUS 721 Week 2: Business Intelligence
- BUS 721 Week 3: Enterprise Resource Planning
- BUS 721 Week 4: Implementation Success and Failure
- BUS 721 Week 5: Process Improvement
- BUS 721 Week 6: Data and Decision Making
- BUS 721 Week 7: Research on Operations Excellence
More DBA sample papers
- BUS 700 Week 8: A Plan for Doctoral Study
- BUS 733 Week 8: Transformation Strategy Paper
- FIN 711 Week 8: Research on Entrepreneurial Finance
- MGT 711 Week 8: Recommendations for Global E-Business
BUS 721 Week 8 questions, answered
What does BUS 721 Week 8 usually cover?
It usually covers integrated recommendations for optimizing operations: a summary of analysis, sequenced recommendations grounded in research, costs and benefits, risks, governance, measures and contributions.
Where can I find a free BUS 721 Week 8 sample paper?
This page presents the complete integrated recommendations for a cabinet manufacturer, with sequencing and notes. Request a complimentary draft of your own final paper.
Why does the sequence of operational improvements matter?
Because capabilities build on one another; for example, speeding up a process with high defect rates tends to multiply disruptions, so quality improvements often need to come first.
How should operations recommendations be justified?
With evidence from the organization's data, research on similar practices, estimates of costs and benefits and a clear explanation of how each recommendation addresses an identified problem.
What makes operations improvements last?
Aligned measures and incentives, standard work, sustained leadership attention, protected improvement time and routines that review data and act on it.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Request this one custom, free · All BUS 721 week samples · All courses