RES 6302 Module 5 Final Defense Script and Reflection Example

The Final Defense Script and a Reflection on Becoming a Scholar-Practitioner: Closing a DBA Study of Why Revenue Cycle Staff Raise Problems

Student Name

American College of Education

RES6302: Defending the Dissertation

Module 5 Assignment

Instructor Name

November 9, 2026

Introduction

This paper contains the script I will speak at my dissertation defense, followed by a reflection on the doctoral process. The script is written to be heard rather than read: short sentences, numbers rounded and repeated where they matter and transitions that tell the committee where we are. Slide numbers in brackets mark when each slide appears. The reflection that follows looks back at what the study taught me as a researcher and as a revenue cycle leader. The script runs to about eighteen minutes at a calm speaking pace, leaving room for a slow start.

Script: Opening

[Slide 1] Good afternoon, and thank you for being here. Three years ago, a coder in a department like mine noticed that one payer had quietly changed how it wanted a certain modifier billed. She said nothing for three weeks. By the time someone else caught it, hundreds of claims had been denied. When I asked her later why she had waited, she told me that a colleague who had once challenged a workflow was reminded to keep her numbers up. That story is a composite, but every revenue cycle leader in this room has heard a version of it. My study asks what makes people like her speak up.

Script: The Problem and the Approach

[Slides 2 and 3] Revenue cycle staff sit closest to the problems that cost hospitals money: registration mistakes, coding errors, payer changes and denial trends. When they report those problems early, the hospital saves rework and recovers cash. When they stay silent, it pays. Yet we know little about what leads these employees, rather than nurses or physicians, to speak up.

[Slides 4 to 6] I drew on two ideas. One is that transformational leaders, who model, inspire, challenge and attend to their people, encourage contribution. The other is psychological safety, the shared feeling in a team that owning up to a mistake will not be punished (Edmondson, 1999). Put together, they suggest that leaders may encourage voice mostly by making it safe. I tested that idea by surveying 221 billing, coding, access and denials staff across three hospital systems, using established scales and a regression approach that estimates indirect effects with bootstrapped intervals.

Script: What I Found

[Slide 7] Respondents covered every main role in the department, and close to half did their work at home for at least part of the week.

[Slides 8 and 9] First, the better staff rated their supervisor's leadership, the more often they said they spoke up. Second, and more strongly, they felt safer in their teams.

[Slide 10] Third, and this is the main finding, when I looked at leadership and safety together, about sixty percent of the connection between leadership and voice ran through safety. The interval around that estimate stayed well above zero. Put simply, supervisors seemed to influence speaking up mostly by making it feel safe to speak.

[Slide 11] What remained of the direct connection was small, and I cannot rule it out. [Slide 12] These results held under three different checks, and remote staff looked no different from on-site staff.

Script: What It Means and Its Limits

[Slide 13] These results line up with studies in restaurants, health care teams and meta-analyses; for example, safety also helped account for the leader-voice link in a large restaurant chain (Detert & Burris, 2007). What is new is the setting: administrative hospital work, much of it done away from the office.

[Slides 14 and 15] I want to be direct about the limits. Because I surveyed people once, I cannot show which came first, and estimates of indirect effects from one time point can mislead (Maxwell & Cole, 2007). The data came from employees' own reports, and I could not model the fact that people share supervisors.

[Slides 16 and 17] For leaders, I suggest five practical steps, starting with how supervisors respond to audit errors. For researchers, I suggest five studies, starting with one that follows these relationships over time.

Script: Closing

[Slide 18] Let me go back to the coder who waited three weeks. My results point to something other than a more inspiring supervisor as what would have changed her mind; it was a team where raising a problem felt safe. In revenue cycle work, that safety is not a soft extra. It protects patients from wrong bills and protects hospitals from losses they never see coming. Thank you. I welcome your questions.

Changes After the Final Rehearsal

The final rehearsal for my chair ran nineteen minutes, close to the target, but it exposed three problems. The method section used the phrase indirect effect before explaining it, so a plain-language sentence now comes first. I had been saying statistically significant repeatedly; most instances were replaced with descriptions of size and certainty. And the closing originally ended on recommendations, which made the last minute feel like a list; it now returns to the opening story. My chair also suggested pausing for two seconds after the main finding, which felt awkward in practice but noticeably helped colleagues who were watching remember it. Finally, I cut one sentence from the limitations passage that apologized for the design; my chair pointed out that explaining a choice is different from apologizing for it, and the committee needs the first.

Reflection

I entered the program believing I already knew what made revenue cycle teams work, and in broad terms the study confirmed some of what I believed. What it changed was how I hold that belief. I now distinguish between what the data show, what they are consistent with and what I would like them to show, and I hear the same distinctions missing in leadership meetings where a single good quarter is credited to a new supervisor. The hardest moment was writing honestly about remote work: I had expected it to weaken safety and voice, it did not, and I had to resist the urge to explain the non-finding away. Recruitment taught a quieter lesson. Building a survey in which no employee could be traced showed me, in practical terms, how much a person's willingness to talk rests on trust, which is the subject of the study itself.

As a leader, I will take two habits back to my department. The first is to ask, when someone raises a problem, what it cost them to say it. The second is to treat my own explanations of team performance as hypotheses, with evidence I can name. Those habits, more than any single finding, are what I take from becoming a scholar-practitioner.

Conclusion

The script presents the study in four acts and about eighteen minutes of speech, opening and closing on the same story and stating its limits plainly. Rehearsal changed how statistics are described and how the talk ends. The reflection names what the doctoral process changed: a more careful relationship with evidence and two habits to carry into leadership practice.

References

Detert, J. R., & Burris, E. R. (2007). Leadership behavior and employee voice: Is the door really open? Academy of Management Journal, 50(4), 869-884. https://doi.org/10.5465/amj.2007.26279183

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999

Maxwell, S. E., & Cole, D. A. (2007). Bias in cross-sectional analyses of longitudinal mediation. Psychological Methods, 12(1), 23-44. https://doi.org/10.1037/1082-989X.12.1.23