| Course | DBAX 9102 Business Research Project Stage 2 |
|---|---|
| Week | Week 7 |
| Paper type | Design options |
| Length | About 750 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Business Administration (DBA) |
| Updated | October 2026 |
Free sample paper for DBAX 9102 Week 7
Four Designs Against One Remainder: Lining Up an Experiment, a Branch Comparison, a Multilevel Records Study and a Case Study for Testing Whether Mandated Coaching Frequency Relates to Quota Attainment
Student Name
Walden University
DBAX 9102: Business Research Project Stage 2
Instructor Name
Month Day, Year
Four Designs Against One Remainder: Lining Up an Experiment, a Branch Comparison, a Multilevel Records Study and a Case Study for Testing Whether Mandated Coaching Frequency Relates to Quota Attainment
What the Review Has Already Decided
Once the review has spoken, most designs are already out of the running. The open remainder from last week requires four things: branch sales managers in industrial distribution, coaching frequency logged in company systems, coaching skill rated by salespeople, and several quarters of quota results drawn from company systems, all under a policy that sets a frequency target. Any design that cannot deliver those four is ruled out before its other merits are considered. This paper sets four candidate designs against those requirements, at the regional distributor where I work, with fourteen branches, eleven sales managers and sixty-four outside salespeople.
The Four Candidates
Table 1
Candidate Designs Against the Remainder's Requirements
| Design | Managers in distribution | Logged frequency | Rated skill | Recorded quota over quarters | Causal reach | Feasibility | |
|---|---|---|---|---|---|---|
| Field experiment: randomly assign some managers to coach twice monthly and others as needed | Yes | Yes | Yes | Yes | Strongest | Low; the policy already applies to all, and leadership will not suspend it | |
| Branch comparison before and after the policy began | Yes | Partly; logging began with the policy | Only after | Yes | Moderate | Moderate; only one change point and many other changes that year | |
| Multilevel records study: salespeople nested within managers, frequency from logs, skill from a survey, quota from records | Yes | Yes | Yes | Yes | Associational, with controls | High | |
| Qualitative case study of how managers carry out the policy | Yes | Not measured | Described | Not measured | Explains mechanisms; no estimate of relationship | High | |
Feasibility judged from conversations with the vice president of sales and the sales operations team.
Weighing the Candidates
The field experiment would give the clearest answer. Antonakis et al. (2010) argue that randomized designs are the most reliable way to support causal claims in leadership research. But leadership will not exempt any manager from the coaching policy, so random assignment is not available. A design that cannot be run cannot be chosen.
The branch comparison has appeal because the policy began at a known date. However, coaching sessions were not logged before the policy, so frequency before the change cannot be measured, and the same year saw a price increase and two new product lines. Shadish et al. (2002) describe how such concurrent events, which they call history threats, undermine simple before-and-after comparisons.
The multilevel records study meets all four requirements. It can relate each salesperson's logged coaching frequency and rated coaching skill to recorded quota attainment, accounting for the fact that salespeople share managers. Dahling et al. (2016) used a multilevel design of this general kind in a sales organization. Its weakness is causal reach: it can show association and control for measured differences between territories, but not rule out unmeasured ones.
The case study would explain how managers turn a frequency target into actual coaching, which matters for interpreting any result. But it cannot estimate the relationship the remainder asks about.
The Likely Choice
The multilevel records study is the only design that meets every requirement and can be run. The case study's strength, explaining mechanisms, could be added in a limited form, through a few follow-up interviews with managers, without changing the main design. Next week's commitment paper will settle the choice and state what it gives up.
Designs Considered and Not Listed
Two other designs were considered briefly. A survey-only study, asking salespeople to rate both their manager's coaching and their own performance, would be cheap and fast, but it would repeat the ratings-based design that the disagreement analysis identified as the likely source of inflated results. A study across several distributors would improve generalizability, but I have no access to other firms' coaching logs or quota records, and their coaching policies would differ. Neither meets the remainder's requirements, so neither appears in the table. Recording them here shows that the four candidates were chosen from a wider field rather than assembled to make one design look inevitable, which a committee is entitled to ask about.
What the Comparison Shows About the Remainder
Laying the designs side by side also tests the remainder itself. If no design could have met all its requirements, the remainder would be too ambitious. One can, which suggests the remainder is both specific and studyable. It also confirms that the remainder was not written to fit a design chosen in advance, since the comparison could have ruled every design out.
References
Antonakis, J., Bendahan, S., Jacquart, P., & Lalive, R. (2010). On making causal claims: A review and recommendations. Leadership Quarterly, 21(6), 1086-1120. https://doi.org/10.1016/j.leaqua.2010.10.010
Dahling, J. J., Taylor, S. R., Chau, S. L., & Dwight, S. A. (2016). Does coaching matter? A multilevel model linking managerial coaching skill and frequency to sales goal attainment. Personnel Psychology, 69(4), 863-894. https://doi.org/10.1111/peps.12123
Shadish, W. R., Cook, T. D., & Campbell, D. T. (2002). Experimental and quasi-experimental designs for generalized causal inference. Houghton Mifflin.
DBAX 9102 Week 7 instructions, in plain terms
Week 7 asks you to compare design options against the requirements of your open remainder. Restate those requirements. Identify at least four candidate designs, including at least one stronger design that may not be feasible. In a table, rate each on whether it meets each requirement, its causal reach and its feasibility. Weigh the candidates in a stated order, such as requirements first, then causal reach, then feasibility. Explain any designs you considered but did not list. Identify the likely choice and any element of a rejected design worth borrowing. Close by explaining what the comparison reveals about the remainder itself.
How the DBAX 9102 Week 7 example is put together
The paper restates four requirements from the remainder. A table rates four designs. A section rules out the experiment despite its causal strength, citing Antonakis and colleagues. A section rules out the branch comparison because coaching was not logged earlier and other changes coincided, citing Shadish and colleagues. A section shows the multilevel records study meets every requirement, citing Dahling and colleagues, while admitting its limited causal reach. A section keeps part of the case study as follow-up interviews. A section explains why a survey-only design and a multi-firm study were not listed. A closing section notes that the remainder proved studyable. Feasibility ratings come from conversations with the vice president of sales and the operations team, and the paper says so.
DBAX 9102 Week 7 rubric: what earns full marks
The core expectation is that the review determines the design, so rating candidates against the remainder's requirements carries the most weight. Including a stronger but infeasible design, and explaining why it was dropped, shows honesty about trade-offs. Citing design literature for each threat demonstrates methodological grounding. A stated order of criteria shows disciplined choice. Explaining designs not listed shows the comparison was not stacked. Borrowing elements from rejected designs shows creativity. Comparisons that list designs without criteria, ignore feasibility or choose a design that misses a requirement lose credit at this stage. Showing that the remainder could have ruled every design out, but did not, demonstrates that the remainder was written honestly. Talking with the people who control access before rating feasibility is a step faculty value.
DBAX 9102 Week 7 help from the desk
Copy your remainder's requirements into the columns of a table, then add causal reach and feasibility. List every design you can think of in the rows, including one you know you cannot run. Fill in each cell honestly. Rule out designs that miss a requirement first, then compare the rest on causal reach, then feasibility. Ask whether a rejected design has one element worth keeping. Many students choose a design first and then describe alternatives to justify it. Others pick the strongest design on paper without checking whether the organization will allow it. Talk to the people who control access before you rate feasibility. Our writers can help you build the table and weigh the rows.
Get a DBAX 9102 Week 7 example written to your instructions
Forward the remainder your review reached, together with the Week 7 prompt and rubric. An options paper with verdict-derived criteria, a fit table and costed survivors follows in 24-48h, and the first one is free. Designs are compared on logic alone at this stage, so no site, sponsor or approval details are needed.
More DBAX 9102 papers and DBA samples
- DBAX 9102 Week 1: Burden of Proof Discussion
- DBAX 9102 Week 2: Literature Search Protocol
- DBAX 9102 Week 3: Literature Claim Sort
- DBAX 9102 Week 4: Literature Disagreement Analysis
- DBAX 9102 Week 5: Settled Findings Statement
- DBAX 9102 Week 6: Open Remainder Statement
- DBAX 9102 Week 8: Research Design Commitment
- DBAX 9102 Week 9: Research Evidence Plan
- DBAX 9102 Week 10: Design Peer Challenge
- DBAX 9102 Week 11: Stage 2 Assembly Document
- DBAX 9101C Week 7: Consulting Scope Boundary
- DBAX 9101 Week 7: Research Question Draft
- DBAX 8151 Week 7: Applied Theory Analysis
- DBAX 8101 Week 7: Study Alignment Check
DBAX 9102 Week 7 questions, answered
Where can I find a free DBAX 9102 Week 7 sample paper?
Anyone can read the design comparison, table included, below; it is free.
Which designs does the DBAX 9102 Week 7 paper compare?
A field experiment, a branch comparison, a multilevel records study and a case study.
Why is the experiment ruled out?
Leadership will not suspend the coaching policy for some managers.
Why is the branch comparison ruled out?
Coaching was not logged before the policy and other changes coincided.
Which design meets every requirement?
The multilevel records study.