| Course | DBA 955 Dissertation I |
|---|---|
| Topic | Topic 6 |
| Paper type | Design choice justification |
| Length | About 960 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for DBA 955 Topic 6
Why a Multiple-Case Design and Not a Customer Survey: Justifying How a Study Will Explain Restaurant Owners' Switching Between Distributors
[Author Name]
College of Doctoral Studies, Grand Canyon University
DBA-955: Dissertation I
Topic 6 Design Choice Justification
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Why a Multiple-Case Design and Not a Customer Survey: Justifying How a Study Will Explain Restaurant Owners' Switching Between Distributors
The Question and the Kind of Claim It Seeks
A doctoral candidate who manages sales for a composite foodservice distributor proposes to study how independent restaurant owners come to switch distributors. The research question is: how do owners of independent restaurants move from dissatisfaction with a distributor to the decision to switch, and what events and relationships shape that movement? The claim the study seeks is an explanation of a process, how switching unfolds and why at particular moments, not an estimate of how common switching is or how much each factor contributes. That distinction governs every design choice below, because designs suited to estimating frequency or effect size are poorly suited to explaining process, and the reverse.
Why Case Study Fits
Yin (2018) argued that case study research is suited to how and why questions about contemporary events over which the researcher has little or no control, examined in their real-world context, especially when the boundary between the phenomenon and its context is not clear. All three conditions hold. The question asks how and why. Switching decisions are happening now, in restaurants the candidate does not run. And the boundary is blurred: a switch may be triggered by a late delivery, a new chef, a menu change, a sales representative's departure or a competitor's introductory price, and these cannot be separated from the restaurant's operations in which they occur.
Two Alternatives, Set Out Fairly
The candidate's first plan was a survey of the employer's customers, asking about satisfaction and reasons for considering a switch. The survey had real strengths. It could reach several hundred restaurants, measure stated reasons consistently and support comparisons by restaurant type. But it had two problems the design could not overcome. It would reach only restaurants still buying from the employer, the ones that had not switched, so it would study the absence of the event rather than the event. And respondents would know the candidate as a distributor's sales manager, possibly as their own representative's manager, and would answer accordingly.
The second alternative was a single in-depth case of the candidate's own firm, tracing restaurants that had left it. That design would offer depth and easy access to records. It would offer no contrast: every case would be a departure from one distributor, with one set of practices, seen through the eyes of the firm that lost the customer. It could not distinguish what drives switching in general from what drives switching away from this particular company.
The Chosen Design
The chosen design is a multiple-case study of restaurants that switched distributors within the past eighteen months, in either direction, including some that left the candidate's employer, some that moved to it and some that moved between two other distributors. Eisenhardt (1989) argued that multiple cases allow replication logic, in which each case serves as an independent test of emerging explanations, and that cases should be chosen for theoretical reasons, such as to fill categories or to provide contrast, rather than at random.
Table 1
Designs Considered and What Each Could Claim
| Design | What it could claim | Main weakness | Decision |
|---|---|---|---|
| Survey of employer's customers | Frequency of stated reasons among current customers | Misses restaurants that switched; respondents see a sales manager | Set aside |
| Single case of the employer | Detailed account of departures from one firm | No contrast; one firm's view | Set aside |
| Multiple cases recruited through an association | Explanation of how switching unfolds, with contrast | Limited breadth; owners' recall | Chosen |
Recruitment will run through a regional restaurant association, not through the employer's accounts, so that participants are approached as association members by a researcher rather than as customers by a supplier. The association has agreed in principle to circulate an invitation. Sources for each case will include interviews with the owner and, where possible, the chef or kitchen manager; invoices the owners volunteer, which show the timing and size of orders before and after the switch; and menu changes, which can reveal shifts in what the restaurant needed from a distributor.
Keeping Research and Sales Apart
The design raises one problem the survey would have hidden: owners may tell the candidate what competing distributors charge and how they win accounts, information a sales manager could use. The proposal handles this in three ways. Invoices and pricing details will be seen only in anonymized form, with distributor names replaced by letters, and they will be stored outside the employer's systems. The candidate will not use anything learned in the study in a sales role, an undertaking written into the consent form and agreed with the employer in advance. And restaurants that are current customers of the candidate's own sales team will be excluded, even if they volunteer, because no consent process can fully separate the researcher from the person who sets their prices.
How Many Cases
Eisenhardt and Graebner (2007) noted that theory-building from cases depends on theoretical sampling and on cases that illuminate relationships among constructs, and that the number of cases is a judgment rather than a formula. The proposal plans for eight to ten cases, enough to include restaurants of different types and switches in different directions, with the final number set by when additional cases stop adding new elements to the emerging explanation.
What the Design Gives Up
The design gives up breadth. It cannot say how common each trigger is across all independent restaurants, and its findings will rest partly on owners' recall of decisions made months earlier, supported where possible by invoices. The proposal states these limits plainly and suggests that a survey, designed after the case study has identified the process and its triggers, would be the natural next study for estimating frequency.
References
Eisenhardt, K. M. (1989). Building theories from case study research. Academy of Management Review, 14(4), 532-550. https://doi.org/10.5465/amr.1989.4308385
Eisenhardt, K. M., & Graebner, M. E. (2007). Theory building from cases: Opportunities and challenges. Academy of Management Journal, 50(1), 25-32. https://doi.org/10.5465/amj.2007.24160888
Yin, R. K. (2018). Case study research and applications: Design and methods (6th ed.). SAGE.
DBA 955 Topic 6 instructions, in plain terms
Topic 6 in DBA-955 asks doctoral students to justify a research design against its alternatives. Strong justifications state the research question and the kind of claim it seeks, then show why the chosen design suits that claim, citing established methodological sources. Students should set out each alternative fairly, including its real strengths, and explain precisely why it falls short. The paper should describe the chosen design's recruitment, sources and number of cases, address any conflict between the candidate's job and the research, and state plainly what the design gives up.
How this DBA 955 Topic 6 example is built
The research question comes first in the finished justification, along with the kind of claim it seeks: an explanation of how independent restaurant owners come to switch distributors, not an estimate of how common switching is or how much each factor contributes. Following Yin, it argues that case study suits how and why questions about contemporary events the researcher cannot control. Two alternatives are then set out fairly. A survey of the employer's customers would measure stated reasons across many restaurants but would reach only those who stayed, and respondents would treat the candidate as their sales representative. A single case of his own firm would offer depth and no contrast. The chosen design studies several restaurants that switched in either direction, recruited through a regional restaurant association, with interviews, invoices the owners volunteer and menu changes as sources.
Reading the DBA 955 Topic 6 rubric
Faculty reward a design matched to the claim it seeks. An Excellent justification frames the study as explaining a process, then applies Yin's conditions for case study. Credit goes to giving the customer survey and the single case their strengths before showing why each fails, summarized in a table. The rubric values replication logic and theoretical sampling from Eisenhardt and from Eisenhardt and Graebner. Strong papers recruit through an association and keep competitor pricing out of sales use. Top marks go to conceding breadth and proposing a later survey.
Common DBA 955 Topic 6 mistakes, and how to avoid them
The costliest pattern here is a design chosen first and justified afterward, which committees detect because claim and method never quite meet. A common version names qualitative design and cites Yin without explaining why this particular question is a how or why question, turning a methodological argument into a citation. Rejected alternatives dismissed in a line signal that nothing was really compared. Insider candidates often propose to sample their employer's customers because the list is at hand, and graders expect the sales relationship to be recognized as a threat to candor before it becomes a finding. Designs that promise to identify the most important factor from a handful of cases claim a quantitative result from qualitative data. A justification silent on what the design cannot conclude leaves the committee to draw that line, usually more tightly.
Get a DBA-955 Topic 6 example written to your instructions
Send the DBA-955 Topic 6 instructions and your classroom rubric. We write a custom structural example to them, showing a design matched to its claim and alternatives weighed, in 24 to 48 hours, and the first one is free. Your dissertation is your own work: chapters are never written for a reader, and your IRB application, site permission letters, committee correspondence and signatures remain yours.
More DBA 955 papers and DBA samples
- DBA 955 Topic 1: Dissertation Problem Statement
- DBA 955 Topic 2: Insider Positionality Statement
- DBA 955 Topic 3: Literature Review Blueprint
- DBA 955 Topic 4: Gap Verification Memo
- DBA 955 Topic 5: Inconvenient Finding Dq Post
- DBA 955 Topic 7: Access Feasibility Plan
- DBA 955 Topic 8: Proposal Method Defense Brief
- DBA 960 Topic 6: Decliner Profile Analysis
- DBA 839 Topic 6: Architecture Commitment Analysis
- DBA 965 Topic 6: Pilot-scale Recommendation Set
- DBA 835 Topic 6: Supplier Influence Map
DBA 955 Topic 6 questions, answered
When is a case study the right dissertation design?
Case study fits a question about how or why events unfold in a live setting the researcher cannot control, where context is part of the answer. Yin's work on case study research is the standard reference for that position. It suits the restaurant question because switching unfolds through relationships and events over time, and it fits poorly when a question concerns frequency or the size of one factor's effect.
Why not survey my company's own customers?
Because the list reaches only the customers who stayed, and each respondent would be answering someone they know as a salesperson. Both problems bias what the study can find. The example routes recruitment through an outside association so current accounts are excluded and the research role stays separate from the sales role, a choice the committee is likely to ask about.
Where can I find a free DBA 955 Topic 6 sample paper?
Every part of the justification appears here: the question and claim, why case study fits, two alternatives, the chosen design, keeping research and sales apart, how many cases and what the design gives up. A paper written to your DBA 955 Topic 6 prompt costs nothing.
Why recruit through a restaurant association in DBA 955 Topic 6?
Owners approached as association members by a researcher answer differently from customers approached by a supplier. It also reaches restaurants that left the employer or never bought from it.
How many cases does the design plan in DBA 955 Topic 6?
Eight to ten, enough to include different restaurant types and switches in each direction. The final number is set when additional cases stop adding new elements to the explanation, not by a formula.