You already know the organization. That is the advantage and the problem
DBA candidates usually arrive with deep knowledge of a real business problem and no obvious way to turn it into research. The gap is rarely about business understanding. It is about converting something you know practically into a question with a method attached.
Get your free quote
We reply within 1 business hour, no delays.
No card details required · 100% confidential · On time, or it's free
From a management problem to a research question
Our retention in the regional offices is poor is a management problem. It is real, it matters, and it is not yet researchable. There is no stated question, no unit of analysis, and nothing that could turn out to be false. Getting from there to a question a committee will approve is the first and often the longest piece of work.
The second conversion is theoretical. A DBA is applied, but it is still a doctorate, and committees expect the problem to be connected to a body of management thinking rather than treated as unique. Practitioners often resist this because the theory feels distant from the situation, and the resistance is usually what holds the proposal up.
The third is about your position. Studying your own organization gives you access nobody else has, and it creates obligations: confidentiality, consent from people who may report to you, and what happens if the findings are unwelcome. All three need answering in the proposal rather than discovering later.
- An organizational problem converted into a researchable question
- Theory connected to the problem rather than bolted on
- Insider access, confidentiality and consent handled explicitly
- A design that fits the time a senior role actually leaves
What we work through
On your own organizational problem
- Narrowing the problem until a single study can address it
- Finding the literature your problem actually sits in
- Choosing between case study, mixed methods and evaluation designs
- Confidentiality where the organization is identifiable
- What happens to the study if you change employer partway through
Four issues specific to doing research inside your own business
Anonymity that does not hold
Describing a company as a mid-sized regional logistics firm in the Southeast with three named competitors identifies it. Committees and IRBs check this, and it is easier to solve at design stage.
Consent from subordinates
If participants report to you, voluntary consent is genuinely harder to establish. There are workable approaches, and they have to be designed in rather than asserted.
Findings the organization dislikes
Worth deciding in advance who has approval rights over what. A sponsor expecting a veto over conclusions is a problem for the doctorate, and it surfaces late unless it is raised early.
Generalizability questions
Committees ask what a single-organization study contributes beyond that organization. There are good answers, and they need to be built into the design rather than improvised at the defense.
Your research, your organization, your doctorate
- We do not write your dissertation or any section of it.
- We do not design your study or choose your research question.
- We do not analyze your data for you.
- We do not contact your employer, your committee or your institution.
- We teach the method, work through your problem with you, and review your writing.
We also do not consult on the business problem itself. We help you research it, which is a different job from solving it, and mixing the two is a common way for a DBA to lose its footing as research. Read the full policy.
Frequently Asked Questions
A DBA is normally organized around a problem in a real organization and assessed partly on contribution to practice. A PhD is organized around a gap in the literature and assessed on contribution to knowledge. Both are doctorates with comparable standards, and the difference is what the work has to demonstrate.
Usually yes, and it is common. You will need organizational permission alongside IRB approval, a workable answer on confidentiality, and explicit handling of consent where participants report to you. Start the permission conversation early, because it frequently takes longer than the ethics review.
Usually they are asking you to connect your specific problem to a body of thinking that would explain it, rather than treating the organization as unique. It is normally findable, and it usually improves the study, because theory suggests what to look at that experience alone would not.
It happens often and it is survivable, though it can be disruptive if the study depends on access you lose. Where possible, design so the study is not wholly dependent on one employer, and talk to your supervisor as soon as a move is likely rather than after it.
It can be, and many DBAs are exactly that. What makes it work is being clear about what the case is a case of, so the contribution is about a phenomenon rather than only about one firm. That framing is what answers the generalizability question.
It is done routinely, and the candidates who finish are generally not the ones with the most time. They are the ones with a design that fits their constraints and a regular writing pattern. Both are worth setting up deliberately at the start.
Tell us the organizational problem
We will tell you what it would take to turn it into a researchable question, which design fits, and what your committee will ask about studying your own employer.
Talk About My Research