| Course | DBAX 9103 Business Research Project Stage 3 |
|---|---|
| Week | Week 5 |
| Paper type | Analysis walkthrough |
| Length | About 770 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 9103 Week 5
The Forks the Finished Analysis Hides: An Analysis Walkthrough for a Caregiver Retention Study, Showing Each Point Where the Analysis Could Have Gone Another Way and What the Result Would Have Been
Student Name
Walden University
DBAX 9103: Business Research Project Stage 3
Instructor Name
Month Day, Year
The Forks the Finished Analysis Hides: An Analysis Walkthrough for a Caregiver Retention Study, Showing Each Point Where the Analysis Could Have Gone Another Way and What the Result Would Have Been
Why Show the Forks
A finished analysis seldom shows the points where it could have gone another way. The reader sees one model, one sample and one estimate, as if no other choice was available. Gelman and Loken (2014) call these hidden decision points a garden of forking paths and warn that results can depend on them even when no one is fishing for significance. Steegen et al. (2016) recommend showing how results change across reasonable alternatives. This walkthrough traces the main analysis of the home care retention data, stopping at each fork to show the road not taken.
The Main Analysis
The main analysis was a logistic regression predicting employment at day 90 from the number of supervisor check-ins in the first 14 days, completion of all onboarding modules within 14 days and their interaction, controlling for starting pay, prior caregiving experience and log travel miles. Its sample was the 531 caregivers who were still on staff two weeks after hire.
The Forks
Table 1
Analysis Forks and Their Consequences for the Check-In Estimate
| Fork | Path taken | Alternative | Odds ratio per check-in under the alternative | Why the path taken | |
|---|---|---|---|---|
| Check-in window | First 14 days, among those employed at day 14 | First 30 days, all 576 caregivers | 1.41 | The alternative builds tenure into the predictor | |
| Check-in coding | Excluding scheduling-only contacts | Counting all contacts | 1.24 | Scheduling calls are not check-ins as defined | |
| Check-in form | Count as a continuous predictor | Any check-in versus none | 1.62 for any versus none | Count used the full information; the binary form is reported descriptively | |
| Controls | Pay, experience, travel | No controls | 1.37 | Controls address known differences between caregivers | |
| Supervisor clustering | Standard errors clustered by supervisor | Unclustered | Same estimate, narrower interval | Caregivers sharing a supervisor are not independent | |
On the path taken, the check-in estimate settled at 1.33, and its 95 percent interval spanned 1.10 to 1.61.
Reading the Forks
Across every reasonable path, the check-in estimate stayed above 1, ranging from 1.24 to 1.41 for the count. The conclusion that more check-ins go with higher retention does not depend on any single choice. Its size does: the 30-day window inflates it, and counting scheduling calls dilutes it. That pattern is what one would expect if the 30-day window partly measures tenure and if scheduling calls add noise.
The onboarding estimate behaved differently. It ranged from an odds ratio of 0.96 to 1.18 across the same forks, never with an interval excluding 1. The interaction estimate was unstable in sign, which reinforces the decision to report it as inconclusive.
Forks Not Taken and Not Tried
Some alternatives were not run because they could not be justified before seeing results, such as dropping caregivers with very long travel distances. Running them would only add paths, which Simmons et al. (2011) warn increases the chance of a spurious finding. They are listed in an appendix as forks considered and set aside, each with the reason it was not pursued and the date it was set aside.
The Supervisor Fork in Detail
Clustering deserves a closer look because it changes the interval rather than the estimate. The 531 caregivers were supervised by 22 field supervisors, and caregivers who share a supervisor share that supervisor's habits, including how often and how carefully check-ins are logged. Treating them as independent overstates how much information the data hold. With clustering, the interval for the check-in estimate widened from 1.15 to 1.54 unclustered to 1.10 to 1.61 clustered. The conclusion held, but the clustered interval is the honest one, and it is the one the results chapter reports.
What the Walkthrough Adds to the Report
The results chapter reports the main estimate. The walkthrough lets a reader see that the direction of the check-in association survives every reasonable alternative while its size depends on the window, and that the onboarding and interaction results are fragile. That is more useful than a single number presented as if no other number were possible.
How the Forks Were Chosen
The forks listed are those where I had a genuine choice before the analysis, recorded in the analysis plan. I did not search for forks after seeing results. That distinction, between forks planned in advance and forks discovered afterward, is what keeps a walkthrough from becoming a search for the most favorable path. A reader who doubts this can compare the forks listed here with the dated analysis plan held by my chair.
References
Gelman, A., & Loken, E. (2014). The statistical crisis in science. American Scientist, 102(6), 460-465. https://doi.org/10.1511/2014.111.460
Simmons, J. P., Nelson, L. D., & Simonsohn, U. (2011). False-positive psychology: Undisclosed flexibility in data collection and analysis allows presenting anything as significant. Psychological Science, 22(11), 1359-1366. https://doi.org/10.1177/0956797611417632
Steegen, S., Tuerlinckx, F., Gelman, A., & Vanpaemel, W. (2016). Increasing transparency through a multiverse analysis. Perspectives on Psychological Science, 11(5), 702-712. https://doi.org/10.1177/1745691616658637
The Walden DBAX 9103 Week 5 instructions
Week 5 asks you to walk through your main analysis and show the points where it could have gone differently. Explain why alternative paths belong in the report. Describe the main analysis. In a table, list each fork, the path taken, the alternative, the result under the alternative and why you chose your path. Read the forks for whether they change the conclusion, not only the number. Examine one fork in detail if it matters for interpretation. Explain which forks you did not try and why. Close by stating how the forks were chosen, distinguishing those planned before analysis from any discovered afterward.
How the DBAX 9103 Week 5 example is put together
The paper opens with Gelman and Loken and Steegen and colleagues. A section describes the logistic regression on 531 caregivers. A table lists five forks with alternative estimates: 1.41 for the 30-day window, 1.24 counting all contacts, 1.62 for any check-in, 1.37 without controls and a narrower interval unclustered. A section shows that direction holds while size depends on the window, and that onboarding and interaction estimates are fragile. A section examines clustering by 22 supervisors. A section explains untried forks, citing Simmons and colleagues. A closing section notes that all forks were planned in advance. The table reports one number per fork so the range is visible at a glance, and the text names the fork that moves the estimate most.
Reading the DBAX 9103 Week 5 rubric
Walkthroughs earn credit for showing alternatives honestly. A table with the estimate under each alternative carries the most weight. Reading forks for whether the conclusion changes, not just the number, shows judgment. Separating robust from fragile results demonstrates care. Examining a consequential fork in detail shows depth. Explaining untried forks shows restraint. Distinguishing planned from post hoc forks shows integrity. Walkthroughs that show only forks favorable to the main result, run alternatives after seeing results or omit the effect on secondary results earn lower scores. Showing which results survive every reasonable path and which do not gives readers a far better sense of confidence than any single estimate. Keeping secondary results in view, not only the headline, shows balance. A note on the date each fork was fixed strengthens the account.
DBAX 9103 Week 5 help: mistakes that cost marks
List every decision in your analysis where you had a real alternative: time windows, coding rules, transformations, controls, standard errors. Before running anything new, check whether each alternative was in your analysis plan. Run those and record the main estimate under each. Then ask whether any alternative changes the direction or only the size. Report both robust and fragile results. Many students present a single model as if it were inevitable, which invites suspicion. Others run dozens of alternatives after the fact and report the best. Plan the forks first. Our writers can help you identify the forks in your own analysis.
Get a DBAX 9103 Week 5 example written to your instructions
Upload the Week 5 prompt and rubric and name the analysis your study uses, qualitative or statistical. A phase-by-phase walkthrough with dated decision entries follows inside 24-48h, and there is no charge for the first. Your transcripts and codebook stay where they are; the decisions described were made for an interview set that exists only in the sample.
More DBAX 9103 papers and DBA samples
- DBAX 9103 Week 1: Results Paragraph Discussion
- DBAX 9103 Week 2: Research Procedure Account
- DBAX 9103 Week 3: Proposal Deviation Record
- DBAX 9103 Week 4: Data Preparation Note
- DBAX 9103 Week 6: Results Section Paper
- DBAX 9103 Week 7: Results Display Build
- DBAX 9103 Week 8: Results Number Audit
- DBAX 9103 Week 9: Results Limits Statement
- DBAX 9103 Week 10: Reproducibility Peer Read
- DBAX 9103 Week 11: Stage 3 Report Paper
- DBAX 9103C Week 5: Supplied Records Appraisal
- DBAX 9102C Week 5: Local Transfer Verdict
- DBAX 9102 Week 5: Settled Findings Statement
- DBAX 9101C Week 5: Client Stakeholder Map
DBAX 9103 Week 5 questions, answered
Where can I find a free DBAX 9103 Week 5 sample paper?
The walkthrough and its forks table are posted below without charge.
How many forks does the DBAX 9103 Week 5 walkthrough examine?
Five.
How much does the check-in estimate vary across forks?
From 1.24 to 1.41, always above 1.
Which results are fragile?
The onboarding and interaction estimates.
Why were some forks not tried?
They could not be justified before seeing results.