Groundwork Before Fieldwork: The Methods Case a UK DBA Panel Must Hear

The judgement that precedes the interview

There is a tempting assumption among executive researchers that doctoral scrutiny begins in earnest once data collection is under way. Interviews are scheduled, transcripts accumulate, and the thesis is imagined to take shape through sheer volume of evidence. Examiners tend to see it differently. At an upgrade panel, and again at the viva, the first question is rarely about what was found. It is about whether the machinery that produced the findings can bear the weight placed upon it.

That is why the methods chapter attracts such concentrated attention. It is the point at which a UK DBA candidate demonstrates, in writing, that the study is not merely interesting but defensible. A polished chapter that describes activity without justifying it will be read as competence in project management rather than competence in research. The distinction matters, and it is drawn long before the first interview takes place.

A methods chapter is an argument, not a procedure

The most frequent weakness in draft methodology is a drift into the procedural. Candidates write that they will conduct eighteen semi-structured interviews, transcribe them, and analyse the material thematically. All of this may be true and none of it constitutes a methodological case. What examiners look for is a chain of reasoning in which each decision is traceable to the research question and to an articulated philosophical position.

A useful test is to read each paragraph and ask whether it could be transplanted into a different study without alteration. If it could, it is probably description. Justification is specific: it explains why this design, with these participants, over this period, produces evidence capable of supporting the claims the thesis intends to make.

Declaring a philosophical position — and then using it

Pragmatism has become a popular anchor for Doctor of Business Administration research, and with good reason: it accommodates the mixed methods and applied orientation that many executive projects require. The difficulty arises when pragmatism is asserted in a paragraph and then abandoned. If a position is claimed, it should visibly license certain choices and foreclose others. A critical realist framing, for instance, implies a different treatment of causation and mechanism than a purely interpretivist one, and a different attitude towards triangulation.

Examiners are less interested in which position is adopted than in whether the candidate can explain its consequences. Ontology, epistemology, methodology and methods should form a coherent sequence rather than a list of terms deployed for appearance.

Design logic: from question to claim

Case study, action research, longitudinal design and mixed methods all have legitimate places in executive doctoral work. What must be demonstrated is fit. A single-organisation case study invites questions about boundaries, unit of analysis and the limits of generalisation; an action research project invites scrutiny of the researcher's dual role and the possibility of co-option by organisational interests. Neither is disqualifying, but both require anticipation.

Strong chapters also state what would count as disconfirming evidence. A design that cannot, in principle, be surprised is not a design but a confirmation exercise.

Sampling, access and the politics of the field

Purposive sampling is standard in professional settings, but the rationale should be explicit: which characteristics make a participant informative, who has been excluded, and how access was negotiated through gatekeepers. Claims of saturation are frequently made and rarely evidenced. Examiners may reasonably ask how the candidate knew that further interviews would add nothing, and what analytical procedure supported that judgement.

There is also a relational dimension that executive researchers are well placed to address but often overlook. A senior leader interviewing subordinates or peers within their own sector is researching across a power gradient. The methods chapter should acknowledge this and explain how it was managed.

Rigour that can be audited

Where qualitative methods dominate, the trustworthiness criteria popularised by Lincoln and Guba — credibility, transferability, dependability and confirmability — remain a serviceable framework, provided they are operationalised rather than listed. An audit trail, a reflexive journal, systematic coding with a second coder, and a clear account of how themes were derived all give an examiner something to inspect.

Quantitative components demand their own vocabulary: construct validity, internal consistency, response bias, and the treatment of missing data. Piloting deserves a paragraph in its own right. So does a data management plan, which is increasingly expected by UK institutions as a matter of routine governance.

Ethics before the first conversation

Ethical approval is a milestone, not a conclusion. UK GDPR and the Data Protection Act 2018 frame how personal data may be collected, retained and destroyed, and institutional committees will expect a schedule rather than a promise. Consent should be informed in substance as well as form, particularly where participants are professionally identifiable.

Anonymisation is harder than it appears in small, senior samples; a role title plus a sector can be enough to identify an individual. Organisational confidentiality raises further questions, especially where the research touches on commercial sensitivity or public accountability. The dual role of employee and researcher should be addressed directly, with an account of how conflicts of interest were recognised and managed.

A pre-fieldwork checklist

• Research question stated in a form that the chosen design can actually answer.
• Philosophical position declared and its methodological consequences spelled out.
• Design justified against at least one credible alternative.
• Sampling criteria, access route and exclusions documented.
• Saturation or stopping rules defined in advance.
• Rigour procedures named and operationalised.
• Ethical approval obtained, with consent, retention and destruction schedules attached.
• Data management plan lodged with the institution.
• Reflexive position of the researcher articulated, including organisational seniority.
• Supervision record showing that the design has been challenged, not merely approved.

The difference between polished and defensible

A polished chapter reads smoothly. A defensible one anticipates objection. The gap between the two is rarely a matter of length; it is a matter of whether the candidate has thought like an examiner before sitting in front of one. Executive researchers bring an unusual advantage here, having spent careers defending decisions under scrutiny. The task is to apply that discipline to their own design — and to do so early, while the fieldwork is still ahead and the choices remain open.