BUSI 760 Week 3 DB Forum 2 Thread Example

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

Discussion Board Forum 2 opens Module 2 of Liberty University BUSI 760, and this BUSI 760 Week 3 sample is a complete 100-point thread for the DBA quality course, written after Plenert chapters 4 through 7. The composite prompt asks students to choose an improvement method for a real problem and defend the choice. The thread takes up an outpatient imaging network where patients wait an average of nine business days for an MRI appointment while scanners sit idle 18 percent of scheduled hours. It asks whether the problem is waste in the flow, which lean addresses, or variation in the process, which Six Sigma targets. Shah and Ward's study of lean practice bundles and Schroeder and colleagues' definition of Six Sigma frame the choice, and the thread recommends a sequenced approach.

CourseBUSI 760 Quality Management and Productivity (BUSI760)
Module/Week3
AssignmentDB Forum 2 Thread
Paper typeDoctoral discussion thread
Lengthabout 640 words (thread and replies). Course guide: the course guide keeps the thread's word count and rubric inside the course; this sample is a thread of about 650 words with current APA citations; replies to classmates follow in Module 2, Week 4
FormatAPA 7 citations and reference list
Points100
SchoolLiberty University Online
ProgramDBA
Where it sitsModule/Week 3 in Liberty's published BUSI 760 course guide; current sections can differ
UpdatedOctober 2026

Free sample paper for BUSI 760 Week 3

1

Discussion Board Forum 2: Thread

BUSI 760 Quality Management and Productivity, Discussion Board Forum 2 Thread

Thread by [Student Name]

The prompt and the imaging network are composites standing in for the course's own; the books and the published research are real; the week, points and readings follow Liberty's public course guide for BUSI 760, which keeps each forum's detailed instructions inside the course.

Why this part earns its pointsThe thread starts with two numbers that seem to contradict each other, which is what makes the method choice a real diagnostic question.
2

Our outpatient imaging network operates eleven MRI scanners in six centers. Patients referred for a non-urgent MRI wait an average of nine business days for an appointment, and referring physicians complain constantly. Yet our scanner logs show that scheduled scanner time goes unused 18 percent of the time, through late starts, gaps between patients and no-shows. Long waits and idle machines at the same time mean that our problem is not simply a shortage of scanners. The question this forum poses, which improvement method fits the problem, is therefore a real one for us.

Plenert (2012) argues that each improvement method is designed for a particular kind of problem and that managers should match the tool to the problem rather than adopt a program because it is fashionable. Two broad families are relevant. Lean methods aim at flow, removing waiting, rework, needless handoffs and any step a customer would not pay for. Six Sigma aims at variation and defects: results that differ unpredictably from one case to the next. Our two symptoms point to different families, which is why the choice requires diagnosis.

Lean has a strong evidence base. Shah and Ward (2003), using data from a large census of U.S. manufacturing plants, identified four bundles of lean practices, covering just-in-time flow, quality control routines, preventive care of machines and the people side of the system, including teams and workers trained across several jobs. They found that the bundles contributed substantially to operating performance and that plant size was strongly related to whether lean was implemented, while unionization and plant age mattered less than conventional wisdom held. Their work is a reminder that lean is a system of practices, not a single tool.

Six Sigma is often described as a set of statistical tools, but Schroeder et al. (2008) argue that its tools are similar to those of earlier quality programs. What is new, in their analysis, is an organizational structure: trained improvement specialists, projects selected and led in parallel to the line organization, specific metrics and a disciplined problem-solving method. That structure is suited to problems where the cause of variation is unknown and must be found with data. It is also expensive: belts must be trained, projects take months, and the method's value depends on having reliable data about the process, which our centers collect unevenly.

Why this part earns its pointsThe diagnosis sorts each symptom into waste or variation, which is what turns two method descriptions into a decision.
3

Mapping our case onto both families clarifies the choice. The gaps between patients and late starts are waste. A walk through our process showed that the scheduling call center books appointments without seeing whether prior authorization is complete, so patients arrive and wait while staff call insurers, and technologists then run behind all day. That is a handoff problem, and lean methods such as value stream mapping and standard work are designed for it. When a walk along the process reveals the waste, no statistical study is needed to locate it. No-shows, by contrast, are variation. Some centers lose 4 percent of appointments to no-shows and others 14 percent, and we do not know why. That is the kind of unexplained variation a Six Sigma project with data analysis is designed to explain.

I would therefore sequence the methods. First, a lean effort to redesign scheduling so authorization is confirmed before booking, with standard start times and a pull system that fills gaps from a short-notice list. Second, once the flow is stable, a Six Sigma project to find the causes of no-show variation across centers, examining reminder timing, travel distance and appointment time of day. We would measure success by days to next available appointment and by scanner utilization. Each center would post both numbers weekly, so the teams doing the work can see the effect of their changes. If waits fall and idle time drops without new scanners, the network will have bought capacity through better management rather than equipment.

4

References

Plenert, G. (2012). Strategic continuous process improvement: Which quality tools to use, and when to use them. McGraw-Hill.

Schroeder, R. G., Linderman, K., Liedtke, C., & Choo, A. S. (2008). Six Sigma: Definition and underlying theory. Journal of Operations Management, 26(4), 536-554. https://doi.org/10.1016/j.jom.2007.06.007

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

What the BUSI 760 Week 3 instructions ask

Module 2, Week 3 brings the second forum's thread, worth 100 points, together with Plenert chapters 4 through 7 and one presentation; the reply follows in Week 4 for 50 points. The public guide confirms three forums but prints none of their prompts; those, with the length rules and scoring rows, appear once the course opens. Plenert's book argues that improvement tools must be matched to problems and to an organization's maturity, so a forum built around choosing between methods tests whether students can apply that idea rather than list tools. A doctoral thread should defend a choice with evidence from research and the textbook, using a case the student can describe in numbers.

How this BUSI 760 Week 3 example is built

The thread starts with the imaging network's two numbers, long waits for appointments and idle scanner time, and argues that they cannot both be explained by too little capacity. It then sets out the difference Plenert draws between methods aimed at flow and waste and methods aimed at variation and defects. Shah and Ward's study shows how lean practices work as interrelated bundles rather than separate tools. Schroeder and colleagues describe what is distinctive about Six Sigma, its structure of trained specialists, metrics and a disciplined method. The thread maps the imaging problem onto both, finds waste in scheduling handoffs and variation in no-show rates, and recommends lean first, then a Six Sigma project on no-shows.

BUSI 760 Week 3 grading rubric: where the points go

The second thread is judged on the quality of the choice it defends. Readers will look for a problem described precisely enough to diagnose, an accurate account of what each method is designed to do, evidence from Plenert and peer-reviewed studies, and a recommendation that follows from the diagnosis. A thread that simply prefers one method because it is popular, or that recommends both without saying why or in what order, misses the point of the exercise. Doctoral graders also value awareness of each method's costs and limits. Accuracy about the research matters, especially when describing what Six Sigma adds beyond its tools. Check the rubric posted in the course before you post.

BUSI 760 Week 3 help: mistakes that cost points

Method-choice forums go wrong when a thread summarizes both approaches from a glossary and then simply announces a favorite. Start instead from the problem: what is the output, where is the delay or defect, and what do the numbers show? Ask whether the main issue is steps that add no value or results that vary too much, and look for evidence of each. Use Plenert's guidance on matching tools to problems, and cite at least one study for each method. If you recommend combining methods, give the sequence and the reason. Close by naming the measure that would prove or disprove your choice, so classmates have something concrete to discuss.

Related BUSI 760 sample papers

Other BUSI 760 weeks

More DBA sample papers

BUSI 760 Week 3 questions, answered

What is the BUSI 760 DB Forum 2 Thread?

The 100-point thread for the course's second forum, due in Module 2, Week 3 with Plenert chapters 4 to 7; replies to classmates follow in Week 4 for 50 points.

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

Here you will find a full BUSI 760 Week 3 thread on whether lean or Six Sigma fits an imaging network's MRI scheduling delays and idle scanner time.

What is the difference between lean and Six Sigma?

Lean concentrates on removing waste and improving flow through a process, while Six Sigma concentrates on reducing variation and defects through a structured method, specialists and statistical measures.

What are lean practice bundles?

Shah and Ward grouped 22 lean practices into four interrelated bundles covering flow, quality, machine maintenance and people practices, and found that the bundles contributed substantially to operating performance.

What makes Six Sigma different from earlier quality methods?

Schroeder and colleagues concluded that its tools resemble earlier quality management, but its organizational structure of trained specialists, project leaders and metrics is new.

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.