BUSI 760 Week 5 Dissertation Prospectus Example

Reviewed by Thomas Kerrigan, MBA, CPA · Liberty University · Updated

This BUSI 760 Week 5 sample presents a full Dissertation Prospectus, the assignment Liberty University BUSI 760 places in Module 3, Week 5, as the DBA quality course turns from forums to research planning. The prospectus is a short plan for a dissertation: problem, purpose, questions, design, framework and significance. The composite study asks why continuous improvement programs in mid-sized U.S. food manufacturers so often stall after promising starts. It proposes a qualitative multiple-case study of four plants, two whose programs have lasted five years or more and two whose programs faded within two. Powell's resource-based study of quality management, Bortolotti and colleagues' work on soft lean practices and Netland's survey of success factors form the conceptual framework, and Keller's first chapters frame the study's view of work.

CourseBUSI 760 Quality Management and Productivity (BUSI760)
Module/Week5
AssignmentDissertation Prospectus
Paper typeDoctoral dissertation prospectus
Lengthabout 1,204 words, 4 double-spaced pages plus title page and references. Course guide: the course guide places the prospectus's template, length and rubric inside the course; this sample is about 1,250 words of body text in current APA format, covering the sections a DBA prospectus usually contains
FormatAPA 7 student paper
Points150
SchoolLiberty University Online
ProgramDBA
Where it sitsModule/Week 5 in Liberty's published BUSI 760 course guide; current sections can differ
UpdatedOctober 2026

Free sample paper for BUSI 760 Week 5

1

Why Continuous Improvement Programs Stall: A Qualitative Multiple-Case Study of Mid-Sized U.S. Food Manufacturers

 

[Student Name]

School of Business, Liberty University

BUSI 760: Quality Management and Productivity

Dissertation Prospectus

[Instructor Name]

[Date]

 

The topic, sites and plan are a composite standing in for a student's own; the books and published research are real; the week, points and readings follow Liberty's public course guide for BUSI 760, which places the prospectus's detailed instructions and template inside the course.

Why this part earns its pointsThe background states the business stakes and the pattern to be explained before the problem statement narrows to a gap in research.
2

Why Continuous Improvement Programs Stall: A Qualitative Multiple-Case Study of Mid-Sized U.S. Food Manufacturers

Background

Food manufacturers operate on thin margins and under close regulatory and customer scrutiny. Waste, rework and downtime cut directly into profit, and food safety failures can end a customer relationship. For these reasons, many manufacturers adopt continuous improvement programs, whether called lean, Six Sigma or simply operational excellence. Research supports the potential of such programs. Working from a large national survey of manufacturing plants, Shah and Ward (2003) linked groups of related lean practices to markedly better operating results, and in the comparison Hendricks and Singhal (1997) drew between quality award winners and similar firms, the winners' operating income pulled well ahead over a ten-year window.

Practitioners in the industry, however, describe a familiar pattern. A plant launches a program with training, visual boards and early projects, sees real gains in the first year and then watches participation decline until the program exists mainly on paper. The question is not whether continuous improvement can work but why it lasts in some plants and fades in others that adopted the same tools.

Problem Statement

The general problem is that many continuous improvement programs in manufacturing lose momentum after initial success, wasting the investment and leaving employees skeptical of future efforts. Netland (2016) observed that despite broad agreement about what needs to be done, companies still struggle to implement lean. The specific problem is that mid-sized U.S. food manufacturers, with 200 to 1,000 employees per plant, often lack the corporate support structures of large firms, and little research explains how such plants sustain improvement programs beyond the first two years.

Purpose Statement

This qualitative study, built on several cases, will explore why continuous improvement programs persist in some mid-sized U.S. food manufacturing plants and fade in others, by comparing the experiences of managers, supervisors and line employees in plants with sustained and unsustained programs.

Research Questions

RQ1. How do managers, supervisors and line employees describe the course of their plant's continuous improvement program from launch to the present?

RQ2. What organizational conditions do participants associate with the persistence or decline of the program?

RQ3. How do leaders' actions after the launch phase differ between plants with sustained and unsustained programs?

Why this part earns its pointsThe nature of the study section defends the design against the obvious alternative, a survey, which shows the committee that the choice was deliberate.
3

Nature of the Study

The study will use a flexible, qualitative design. A quantitative survey could measure which practices plants use, but it could not explain how and why programs changed over time, which is the heart of the problem. Yin (2018) treats case research as the natural fit for questions of process and cause in current organizational life, studied in place, where the investigator observes rather than intervenes. A multiple-case design allows comparison. Four plants will be selected purposively from the membership of a regional food processors association: two whose programs have remained active for at least five years and two whose programs were launched with similar tools but became inactive within two years, as judged by records of active projects and meetings.

At each plant, the researcher will conduct semi-structured interviews with the plant manager, two to three supervisors and four to six line employees involved in the program, about 32 to 40 interviews in all. Interviews will be supplemented by observation of improvement meetings where they still occur and review of documents such as project logs and performance reports. Data will be analyzed using reflexive thematic analysis (Braun & Clarke, 2006), first within each case and then across cases to compare sustained and unsustained programs. Trustworthiness will be supported by triangulation across sources, member checking with participants and an audit trail of coding decisions.

Conceptual Framework

Three bodies of work frame the study. Powell (1995), drawing on the resource-based view, found that the visible features of quality programs, such as training and process improvement tools, did not generally produce advantage, while harder-to-copy features, a culture open to bad news, operators with real authority and leaders who stay committed, could. Bortolotti et al. (2015) found that manufacturing plants that succeeded with lean differed from less successful plants more in soft, people-centered practices and organizational culture than in hard technical practices. Netland (2016) identified a broadly shared list of success factors, with differences depending on the stage of implementation. Together these sources suggest that persistence will depend less on the tools a plant adopted than on leadership behavior, employee involvement and culture after launch. The framework will guide interview questions and initial coding while leaving room for unexpected themes.

Definition of Terms

Continuous improvement program refers to a plant-wide, management-sponsored effort to involve employees in identifying and solving process problems using structured methods, whether called lean, Six Sigma or operational excellence. A sustained program is one with documented improvement projects and regular improvement meetings for at least five consecutive years. An unsustained program is one launched with similar tools in which projects and meetings ceased within two years. Mid-sized plant refers to a single food manufacturing site employing between 200 and 1,000 people. Soft practices are people-centered elements of improvement, for instance drawing operators into decisions, teaching them problem solving and letting small teams fix problems, as opposed to technical practices such as pull production or setup reduction.

Significance of the Study

For practice, the study will give leaders of mid-sized food plants an account, grounded in plants like their own, of what sustains improvement programs after the first year, which could reduce wasted investment and employee cynicism. For research, it adds case evidence on the persistence of improvement programs, a phase less studied than adoption, in a sector and size class underrepresented in operations research. The study fits Liberty's DBA emphasis on applied research that addresses problems leaders face in their own organizations.

Assumptions, Limitations and Delimitations

The study assumes that participants will describe their experiences honestly and that program records accurately reflect activity. Its main limitations are reliance on participants' recollections of events up to several years earlier and the small number of cases, which limits generalization to the analytic rather than statistical kind. The study is delimited to mid-sized food manufacturing plants in one region and to programs launched within the past eight years.

Why this part earns its pointsThe integration section ties the doctrine of work to the research problem itself, which is what Liberty's faculty look for.
4

Biblical Integration

Keller and Alsdorf (2012) open their account of work by describing God as a worker who made the world and then shared that work with human beings, whom he made to cultivate it. Work, in this view, is part of the original design for human life and has dignity because people bear the image of the one who designed it. That view bears directly on the problem. A continuous improvement program, at its best, invites line employees to use their judgment and creativity to improve the work they do every day, the kind of cultivation Keller describes. When a program fades, employees often learn that their ideas are not wanted. The study therefore matters not only for efficiency but because the persistence of these programs affects whether ordinary workers are treated as contributors to the work's design or only as performers of it.

Conclusion

This prospectus proposes a multiple-case study of why continuous improvement programs persist or fade in mid-sized food manufacturing plants. The questions concern how and why programs change after launch, the design compares plants with different outcomes, and the framework focuses attention on leadership behavior, involvement and culture. If the study proceeds, its findings could help plant leaders keep improvement alive beyond the first year, and could give employees reason to believe that their ideas will continue to count.

5

References

Bortolotti, T., Boscari, S., & Danese, P. (2015). Successful lean implementation: Organizational culture and soft lean practices. International Journal of Production Economics, 160, 182-201. https://doi.org/10.1016/j.ijpe.2014.10.013

Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. https://doi.org/10.1191/1478088706qp063oa

Hendricks, K. B., & Singhal, V. R. (1997). Does implementing an effective TQM program actually improve operating performance? Empirical evidence from firms that have won quality awards. Management Science, 43(9), 1258-1274. https://doi.org/10.1287/mnsc.43.9.1258

Keller, T., & Alsdorf, K. L. (2012). Every good endeavor: Connecting your work to God's work. Dutton.

Netland, T. H. (2016). Critical success factors for implementing lean production: The effect of contingencies. International Journal of Production Research, 54(8), 2433-2448. https://doi.org/10.1080/00207543.2015.1096976

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

Shah, R., & Ward, P. T. (2003). Lean manufacturing: Context, practice bundles, and performance. Journal of Operations Management, 21(2), 129-149. https://doi.org/10.1016/S0272-6963(02)00108-0

Yin, R. K. (2018). Case study research and applications: Design and methods (6th ed.). SAGE Publications.

What the BUSI 760 Week 5 instructions ask

The Dissertation Prospectus falls in Module 3, Week 5, alongside the third forum's thread, Plenert chapters 8 and 9, Keller chapters 1 through 3 and one presentation; in the published schedule the prospectus is worth 150 points. Liberty's course guide lists it as a single required prospectus and refers students to the course content for the template, length, rubric and due date. In a DBA program, a prospectus is the first formal statement of a possible dissertation, short enough to revise and specific enough for a committee to judge. Placing it in a quality management course invites students to choose a problem in quality or productivity that they could study in their own industry.

How this BUSI 760 Week 5 example is built

The prospectus opens with the background: food manufacturers face thin margins and frequent audits, and many launch continuous improvement programs that do well for a year and then decline. The problem statement narrows to the lack of research explaining why some programs persist in mid-sized plants. The purpose statement and three research questions follow. The nature of the study section defends a qualitative multiple-case design with interviews, observation and documents at four plants. The conceptual framework draws together the tacit resources Powell identified, the soft practices Bortolotti and colleagues studied and Netland's success factors. Sections on significance, assumptions and limitations, and integration with Keller's account of work complete it.

BUSI 760 Week 5 grading rubric: where the points go

A prospectus is judged on clarity and fit more than length. Readers will look for a problem that is specific, current and supported by citations; a purpose statement in which the reader can find the method, the people studied and what is being explored; research questions that the design can answer; and a framework that tells the researcher what to look for. A doctoral reader also checks feasibility: access to sites, a realistic sample and a method suited to the questions. Significance should address both practice and research. For Liberty, the faith integration should connect to the problem itself rather than appear as an appendix. The template and rubric posted in the course set the required headings, so follow them exactly.

BUSI 760 Week 5 help: mistakes that cost points

Students often write a prospectus as if it were a short literature review, with the problem buried on the third page. Lead with the problem in two or three sentences and support it with recent evidence. Make the purpose statement, the research questions and the design agree: a qualitative case study answers how and why questions, not how much. Choose a population you can actually reach, and say how you will gain access. Keep the framework to a few concepts drawn from named sources, and show how each will guide your interviews or analysis. Finally, read the prospectus as a committee member would and ask whether the study could be completed within a doctoral timeline.

Related BUSI 760 sample papers

Other BUSI 760 weeks

More DBA sample papers

BUSI 760 Week 5 questions, answered

What is the BUSI 760 Dissertation Prospectus?

A short plan for a possible dissertation, due in Module 3, Week 5 and worth 150 points in the published schedule; the course content supplies its template and rubric.

Where can I find a free BUSI 760 Week 5 sample paper?

This page carries a complete BUSI 760 Week 5 prospectus for a multiple-case study of why continuous improvement programs stall in mid-sized food manufacturing plants.

What sections does a DBA prospectus include?

Usually background, problem and purpose statements, research questions, the nature of the study, a conceptual framework, significance, assumptions and limitations, and for Liberty a link to a biblical view of work.

Why use a multiple-case study for a prospectus on quality programs?

Because the question is why some programs last and others fade, comparing cases with different outcomes lets the researcher see which conditions are present in lasting programs and absent in faded ones.

What else is due in BUSI 760 Module 3, Week 5?

The 100-point thread for Discussion Board Forum 3, along with Plenert chapters 8 and 9, Keller chapters 1 to 3 and one presentation.

Use it as a model, or ask for your own

This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.