E-Library Logo
Research Ethics & Computer Applications
Research Ethics & Computer Applications
Research Ethics & Computer Applications illustration

Research Ethics & Computer Applications

Program: Doctorate in Business Administration
Program Level: Doctorate
Language: English
Subject Syllabus

Subject Overview

An advanced doctoral syllabus integrating research integrity, ethical theory, regulatory governance, data stewardship, computer-assisted research, analytics, reproducibility and responsible artificial intelligence in business research. It prepares scholars to design, conduct, evaluate and govern rigorous, transparent and socially responsible research in academic and industry settings.

Learning Goal

Students will critically evaluate ethical problems, secure appropriate research approvals, protect participants and data, use contemporary computer applications throughout the research lifecycle, conduct reproducible analyses, govern AI-assisted research and make defensible scholarly and managerial decisions.

Syllabus

1. Foundations of Research Ethics and Integrity

Learning Objective: Examine research ethics terminology, epistemic responsibility, professional integrity and normative theories including deontology, consequentialism, virtue ethics, rights, justice and care ethics; distinguish legal compliance from ethical scholarship.

Category: foundation

2. Ethical Governance, Codes and Regulatory Systems

Learning Objective: Critically compare research ethics committees, institutional review boards, professional codes, institutional policies and international regulations; analyze accountability, conflicts of interest, risk classification, compliance and cross-border research governance.

Category: core

3. Ethics-by-Design and Review Processes

Learning Objective: Embed proportionality, beneficence, non-maleficence, justice and respect into research questions, designs and protocols; prepare ethics applications, risk–benefit assessments, mitigation plans, amendments, monitoring and adverse-event responses.

Category: core

4. Human Participants, Consent and Vulnerability

Learning Objective: Evaluate informed, dynamic and digital consent; confidentiality, anonymity, deception, incentives, power asymmetry and withdrawal; design safeguards for employees, customers, communities and vulnerable populations.

Category: core

5. Ethical Business, Organizational and Digital Research

Learning Objective: Address gatekeeper access, workplace surveillance, covert observation, online communities, social-media research, platform data, stakeholder harm and sponsor influence in field experiments, case studies and organizational research.

Category: application

6. Misconduct, Authorship and Responsible Publication

Learning Objective: Analyze fabrication, falsification, plagiarism, questionable research practices, selective reporting and paper mills; apply authorship, contributorship, peer-review, citation, disclosure, correction and retraction standards.

Category: core

7. Research Data Ethics and Lifecycle Governance

Learning Objective: Develop data management plans covering collection, documentation, quality, ownership, provenance, retention, sharing and disposal; apply FAIR and CARE principles, metadata standards and stewardship responsibilities.

Category: strategic

8. Privacy, Cybersecurity and Intellectual Property

Learning Objective: Apply privacy-by-design, data minimization, anonymization, pseudonymization, access controls, encryption and incident response; evaluate data protection law, confidentiality agreements, copyright, licensing, patents and database rights.

Category: core

9. Digital Research Environments and Reproducible Workflows

Learning Objective: Use operating systems, cloud platforms, collaborative workspaces, version control, electronic notebooks, scripting and containers to create auditable, secure and reproducible doctoral research workflows.

Category: application

10. Digital Literature Review and Knowledge Management

Learning Objective: Conduct systematic and bibliometric searches using scholarly databases; manage references, screening, coding, research notes and evidence maps while critically evaluating source credibility, predatory publishing and algorithmic search bias.

Category: application

11. Computer-Assisted Data Collection and Database Management

Learning Objective: Design ethical surveys, experiments, APIs, web-scraping and sensor-based collection processes; construct relational and non-relational datasets using validation, data dictionaries, SQL, interoperability and quality-control procedures.

Category: application

12. Quantitative Analytics and Computational Research

Learning Objective: Use statistical software and programming environments for data cleaning, visualization, inference, causal analysis, simulation and machine learning; evaluate assumptions, uncertainty, robustness, model risk and reproducibility for scholarly and managerial decisions.

Category: advanced

13. Qualitative and Mixed-Methods Computer Applications

Learning Objective: Apply computer-assisted qualitative and mixed-methods tools for transcription, coding, thematic analysis, content analysis, integration and visualization; preserve reflexivity, context, audit trails and interpretive integrity.

Category: advanced

14. Artificial Intelligence in Research

Learning Objective: Critically govern generative AI, machine learning and automated decision tools across literature review, coding, analysis and writing; address hallucination, bias, explainability, privacy, attribution, disclosure, human oversight and research validity.

Category: contemporary

15. Open Science, Digital Transformation and Future Research Governance

Learning Objective: Evaluate preregistration, registered reports, open data, open code and replication alongside commercialization and confidentiality constraints; anticipate synthetic data, autonomous research agents, federated analytics and evolving governance through audits and responsible-innovation frameworks.

Category: strategic

Research Ethics & Computer Applications
Doctorate in Business Administration

Research Ethics & Computer Applications

Chapter 1
Foundations of Research Ethics and Integrity

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

1. Foundations of Research Ethics and Integrity

Introduction and Context

Research is a social practice through which knowledge is produced, challenged, communicated, and applied. In business administration, research may influence corporate strategy, employment conditions, consumer welfare, public policy, investment decisions, and the allocation of organizational resources. Because research findings can affect people and institutions beyond the researcher, the production of knowledge is not merely a technical activity. It is also a moral, professional, and governance practice.

Research ethics concerns the principles and processes used to determine whether research is morally acceptable. Research integrity concerns the commitment to honesty, rigor, transparency, accountability, and responsible conduct throughout the research lifecycle. Ethics asks questions such as: Who may be harmed? Whose interests are represented? Is consent meaningful? Is the distribution of benefits and burdens fair? Integrity asks whether the researcher has represented evidence truthfully, acknowledged contributions accurately, managed conflicts responsibly, and preserved an auditable record of inquiry.

For doctoral researchers, these matters are especially important. A doctoral project is expected to make an original contribution to knowledge, but originality does not excuse carelessness or misconduct. The authority of scholarship depends on the reliability of its methods and the trustworthiness of its claims. Ethical research therefore requires more than compliance with institutional forms. It requires epistemic responsibility: a duty to form, test, interpret, and communicate beliefs in ways proportionate to the evidence.

This chapter establishes the conceptual foundation for later study of research design, data management, computer applications, artificial intelligence, and publication practice. It distinguishes ethical scholarship from legal compliance and introduces the principal normative theories used to analyze difficult research decisions.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Define research ethics, research integrity, misconduct, epistemic responsibility, and related terminology.

2. Explain why ethical research is central to the credibility and social value of doctoral scholarship.

3. Apply deontological, consequentialist, virtue-ethical, rights-based, justice-based, and care-ethical reasoning to research problems.

4. Distinguish legal or regulatory compliance from ethically responsible scholarship.

5. Identify professional, organizational, and technological risks in business research.

6. Analyze an ethically complex research situation and justify a defensible course of action.

7. Recommend practices that strengthen integrity across the research lifecycle.

Research Ethics, Integrity, and Epistemic Responsibility

Research ethics is the systematic examination of values, duties, rights, and consequences in research. It applies to the selection of a topic, relationships with participants and sponsors, data collection, analysis, authorship, publication, dissemination, and the use of findings. Ethics is not confined to studies involving vulnerable people or sensitive data. A misleading graph, undisclosed sponsor, inappropriate use of artificial intelligence, or unjustified exclusion of a population can also be an ethical failure.

Research integrity is the consistent alignment of research conduct with standards of honesty, accuracy, fairness, openness, and accountability. Integrity is both individual and institutional. Individual researchers must make responsible decisions, while universities, journals, funders, and organizations must create environments in which truthful reporting is rewarded rather than suppressed. A culture that values rapid publication above reliable knowledge can encourage questionable practices even when formal policies are adequate.

Epistemic responsibility refers to responsibility for the quality and justification of knowledge claims. Researchers are not morally responsible only for what they intend; they are also responsible for whether their methods reasonably support their conclusions. For example, a researcher who reports a strong causal conclusion from a small, biased, correlational sample may not have fabricated data, but has nevertheless failed in epistemic responsibility. Responsible inquiry involves intellectual humility, recognition of uncertainty, openness to criticism, and willingness to revise conclusions.

Several distinctions are useful. Research misconduct generally refers to fabrication, falsification, or plagiarism. Fabrication is making up data or results. Falsification is manipulating materials, processes, images, or data so that the research record is misleading. Plagiarism is presenting another person’s words, ideas, structure, or work as one’s own without appropriate acknowledgment. These categories are serious, but ethical problems are broader than misconduct. Questionable research practices may include selective reporting, p-hacking, undisclosed changes to hypotheses, inappropriate exclusion of observations, honorary authorship, inadequate data security, and failure to disclose conflicts of interest.

An error is not automatically misconduct. Research is fallible, and honest mistakes can occur despite reasonable care. The ethical response to an error is prompt correction, transparent documentation, and assessment of its effect on the conclusions. Deliberate concealment or reckless disregard for accuracy changes the moral character of the conduct.

The Normative Frameworks of Research Ethics

No single ethical theory resolves every research dilemma. Normative theories provide different lenses for identifying what matters and for justifying decisions. Doctoral researchers should use them as complementary analytical resources rather than as mechanical formulas.

Deontology: Duties and Rules

Deontological ethics evaluates conduct by reference to duties, principles, and rules rather than only by its consequences. In research, duties may include telling the truth, obtaining valid consent, protecting confidentiality, honoring agreements, acknowledging sources, and reporting findings accurately. A researcher cannot normally justify fabricating a result by claiming that it might lead to a beneficial policy. The act violates a fundamental duty of honesty and undermines the conditions of trustworthy inquiry.

Deontology is particularly valuable where persons might be treated merely as instruments. Participants should not be deceived, exposed to unreasonable risks, or pressured into participation simply because their data are useful. Institutional rules, professional codes, and approved protocols express important duties, although ethical judgment is still required when rules conflict or leave gaps.

A limitation of strict rule-based reasoning is that duties may conflict. A researcher may owe confidentiality to participants while also having a responsibility to report serious threats to safety. Deontological analysis must therefore examine the scope of duties, legitimate exceptions, and the possibility of minimizing violations.

Consequentialism: Outcomes and Public Value

Consequentialism assesses actions by their foreseeable consequences. Research decisions should be evaluated in terms of benefits, harms, risks, opportunity costs, and effects on public trust. A survey may generate valuable knowledge, for example, but its benefits must be weighed against privacy risks, emotional distress, or the possibility that identifiable responses will affect employment.

Consequentialist reasoning supports proportionality. More intrusive procedures require stronger justification and safeguards. It also encourages attention to indirect consequences, such as stigmatizing a community, enabling discriminatory algorithms, or weakening confidence in science. However, predicted benefits can be uncertain and may be exaggerated by sponsors or researchers. Consequences should not be used to excuse violations of basic rights or duties merely because a favorable outcome is hoped for.

Virtue Ethics: Character and Scholarly Habits

Virtue ethics focuses on the character and practical judgment of the researcher. Relevant virtues include honesty, courage, fairness, humility, patience, intellectual curiosity, prudence, and responsibility. A virtuous researcher does not ask only, “Is this permitted?” but also, “What would a trustworthy scholar do in this situation?”

Virtue is expressed through habits: checking source data, seeking criticism, documenting decisions, disclosing uncertainty, resisting pressure to overclaim, and giving credit generously. Courage may be required to challenge a senior colleague or sponsor. Humility is needed when findings contradict a favored theory. Prudence helps the researcher distinguish a legitimate exploratory analysis from an unsupported post hoc story.

Virtue ethics highlights the importance of research culture. Individuals develop scholarly character within communities that model or discourage integrity. Yet appeals to character alone can be insufficient; good intentions must be supported by procedures, records, independent review, and accountability.

Rights-Based Ethics

Rights-based ethics emphasizes the legitimate claims of persons. Research participants may have rights to informed consent, privacy, confidentiality, bodily and psychological integrity, and withdrawal where applicable. Researchers and collaborators may have rights to intellectual credit, fair treatment, and due process.

A rights perspective is especially important in digital research. Information that is technically accessible is not necessarily ethically free for unrestricted use. Publicly visible social-media content may have been posted for a limited social context, not for analysis by employers, governments, or researchers. Rights-based reasoning asks whether the proposed use respects reasonable expectations and whether individuals can be identified or harmed.

Rights can conflict. A sponsor’s interest in proprietary information may conflict with the scholarly duty to disclose enough methodological detail for evaluation. Such conflicts require careful interpretation of agreements and, where necessary, negotiation of safeguards or refusal to proceed.

Justice: Fairness in the Distribution of Burdens and Benefits

Justice concerns who bears research burdens, who receives benefits, and whose experiences are represented. A study may be unjust if it repeatedly recruits groups with limited power because they are convenient, while the benefits accrue primarily to more privileged groups. Justice also concerns fair access to participation, equitable treatment, and avoidance of discriminatory exclusion.

In business research, sampling decisions can reproduce organizational inequalities. For example, studying leadership only through senior executives may make the experiences of temporary, remote, disabled, or low-paid workers invisible. Justice does not require identical treatment in every circumstance; it requires defensible treatment that recognizes relevant differences and avoids exploitation.

Justice also applies to data-driven systems. If a predictive model is trained on historically biased organizational data, deploying it may distribute opportunities unfairly even if its statistical accuracy appears acceptable. Researchers must therefore examine not only average performance but also group-level effects and the social meaning of classifications.

Care Ethics: Relationships, Dependence, and Context

Care ethics emphasizes relationships, vulnerability, empathy, attentiveness, and the responsibilities created by dependence. It challenges the image of research as a detached transaction between autonomous individuals. Participants may be employees, students, patients, subordinates, or community members whose ability to refuse is constrained by relationships of power.

A care perspective encourages researchers to listen to participants’ concerns, design respectful communication, and remain attentive to consequences that formal consent procedures may not reveal. It is particularly useful in qualitative and participatory research, where trust and continuing relationships are central. Care does not mean abandoning rigor or allowing participants to dictate findings. Rather, it requires combining methodological discipline with sensitivity to human circumstances.

Legal Compliance Is Necessary but Not Sufficient

Law establishes enforceable minimum standards, while ethics evaluates what ought to be done, including conduct that may not be legally required. A research practice can be legal yet ethically questionable. A company may lawfully provide a researcher with employee data, but the secondary use may violate employees’ reasonable expectations of privacy. A contract may permit a sponsor to review a report, but suppressing unfavorable findings would compromise scholarly independence.

Compliance typically asks whether a rule, regulation, contract, or institutional procedure has been followed. Ethical scholarship asks broader questions: Is the purpose legitimate? Are risks proportionate? Are affected persons respected? Is the distribution of benefits fair? Are claims supported by evidence? Would the decision remain defensible if publicly disclosed?

The distinction does not make law irrelevant. Regulations often embody hard-won protections and provide essential procedures for review, consent, security, and accountability. Compliance is a floor, not a ceiling. Researchers should identify the applicable legal and institutional requirements, but should also conduct independent ethical reasoning when the rules are silent, ambiguous, or less protective than responsible scholarship requires.

Ethical Reasoning Across the Research Lifecycle

Ethical responsibility begins before data collection. Topic selection should consider social value, feasibility, duplication, and potential harm. Research questions should not be framed to predetermine a desired conclusion. A proposal should explain who may be affected and how risks will be reduced.

During design, researchers should select methods capable of answering the question without unnecessary intrusion. Sampling should be justified, consent procedures should be intelligible, and vulnerable participants should receive additional protection where needed. In organizational settings, researchers must distinguish voluntary participation from participation influenced by supervisors or incentives.

During data management, access should be limited to authorized users, identifiers should be separated where possible, and retention and deletion procedures should be documented. Researchers should preserve an accurate audit trail of transformations, exclusions, coding decisions, and analytical choices. Encryption, access controls, version histories, and secure backups are technical measures that support—not replace—ethical judgment.

During analysis, researchers should examine alternative explanations, missing data, outliers, and limitations. Statistical significance does not automatically indicate practical importance or causal validity. Researchers should avoid changing hypotheses after viewing results without clearly identifying the analysis as exploratory. Negative or inconclusive findings should not be hidden merely because they are less publishable.

During reporting, methods and limitations should be described sufficiently for critical evaluation. Authorship should reflect substantial intellectual or scholarly contribution, while administrative support or funding alone should not automatically confer authorship. Conflicts of interest must be disclosed. When research is corrected or retracted, the purpose is to repair the scholarly record, not merely to protect reputation.

Professional and Organizational Applications

In organizations, research ethics is connected to governance, risk management, compliance, and stakeholder trust. A doctoral researcher working with a firm may face pressure to produce commercially attractive findings, protect confidential information, or accelerate data collection. The researcher must clarify independence, publication rights, data ownership, and reporting expectations before the project begins.

Managers commissioning research should not manipulate instruments, restrict access to inconvenient participants, or demand deletion of unfavorable results. Human-resources analytics requires particular caution because data may affect recruitment, promotion, performance evaluation, or dismissal. Employees should not be treated as merely data points, and models should be tested for discriminatory effects.

Consultants and academic researchers also have duties to clients. Confidentiality is important, but it does not justify concealing fraud, serious harm, or invalid findings where disclosure is ethically or legally required. Professional integrity requires clear communication about the limits of evidence and avoidance of exaggerated claims in executive presentations.

Technology, Computer Applications, and Emerging Issues

Computer applications expand the scale and speed of research while creating new ethical risks. Cloud platforms facilitate collaboration but raise questions about jurisdiction, vendor access, retention, and breach response. Web scraping can collect large datasets without direct interaction, yet the absence of direct contact does not remove privacy, consent, or contextual integrity concerns.

Artificial intelligence introduces additional challenges. Generative systems may produce fabricated citations, inaccurate summaries, biased classifications, or text that conceals the researcher’s contribution. Researchers who use such systems should verify outputs against authoritative sources, protect confidential data, disclose material assistance where required, and retain responsibility for the final work. An AI tool cannot be treated as an accountable author or as a substitute for scholarly judgment.

Reproducible workflows can strengthen integrity through documented code, version control, preregistration where appropriate, and clearly labeled datasets. Open science practices improve transparency, but openness must be balanced with privacy, intellectual property, security, and the risk of re-identification. “Open” does not mean that every dataset should be publicly released.

Illustrative Case: The Workforce Prediction Project

Background

This illustrative case concerns Meridian Retail, a fictional organization that commissions a doctoral researcher to evaluate an employee-retention model. The model predicts which employees are likely to resign within six months. Meridian intends to use the predictions to target training and retention incentives.

Situation and Problem

The researcher receives historical human-resources data containing job title, salary, work location, absence records, performance ratings, and resignation outcomes. The sponsor asks for a rapid report and requests that the researcher exclude employees with incomplete records because their inclusion “will weaken the model.” During preliminary analysis, the researcher finds that part-time and contract employees have more missing data and that the model predicts higher resignation risk for workers from several locations. A senior manager suggests presenting the results without discussing group differences, arguing that the model is only an internal management tool. The researcher also considers using a generative AI service to write the report by uploading the raw dataset.

Analysis

A deontological analysis identifies duties to protect confidential information, report methods accurately, and avoid misleading omissions. Uploading identifiable employee data to an external AI service may violate confidentiality and data-governance obligations. A consequentialist analysis considers possible benefits of targeted support but also risks of discriminatory treatment, self-fulfilling predictions, and loss of employee trust. A justice analysis asks whether excluding workers with incomplete records disproportionately removes groups from the analysis and whether the resulting model distributes opportunities unfairly. A care perspective highlights the vulnerability of employees who may not know how predictions affect them. Virtue ethics calls for courage and intellectual honesty in resisting pressure to conceal limitations.

The researcher should also distinguish prediction from causation. A high-risk score does not establish that an employee will resign or explain why. Using the score to deny promotion or reduce investment could create the very outcome the model predicts. The researcher should investigate missingness, conduct subgroup performance and fairness analyses, and clarify acceptable uses of the model.

Approach and Solution

The researcher proposes a revised governance plan. Identifiers are removed or replaced, access is restricted, and no raw data are uploaded to an external AI platform. Missing data are analyzed rather than automatically discarded; alternative specifications are reported. The researcher evaluates calibration, error rates, and consequences across relevant employee groups. The report distinguishes exploratory findings from validated conclusions and recommends that the model be used, if at all, only to offer voluntary support rather than to impose penalties.

The sponsor is informed that the report will include limitations and group-level results. A review panel involving human resources, legal counsel, data protection staff, and employee representatives considers the proposal. Employees receive a plain-language explanation of the project and a channel for questions or concerns.

Outcome

Meridian delays operational deployment until additional validation is completed. The final report finds that the model’s apparent accuracy was partly driven by historical patterns of managerial treatment rather than stable predictors of resignation. The organization redesigns its retention program around broader working-condition improvements instead of individualized risk labels.

Learning Points

The case demonstrates that technical performance is not equivalent to ethical acceptability. Responsible research requires attention to data provenance, power, fairness, confidentiality, transparency, and downstream use. It also shows that an ethical objection can improve organizational decision-making rather than obstruct it.

Challenges and Common Mistakes

Researchers commonly mistake approval for ethical completion. An ethics committee may approve a protocol, but circumstances can change and new risks may emerge. Continuing review and responsible judgment remain necessary.

Another mistake is treating consent as a signature rather than a process of comprehension and voluntariness. Long forms written in technical language may satisfy documentation requirements while failing to support meaningful choice. Researchers may also overestimate anonymization, especially when multiple datasets can be linked.

Selective reporting is a further risk. Presenting only favorable outcomes, removing inconvenient observations without justification, or emphasizing statistical significance can produce a persuasive but unreliable account. Citation practices can fail through careless paraphrase, self-plagiarism, or attribution that obscures the actual source of an idea.

Power relationships create distinctive risks. Employees may feel unable to refuse a supervisor; junior researchers may fear challenging a principal investigator; and doctoral candidates may experience pressure from sponsors or publication expectations. Institutions should provide confidential reporting channels, protect whistleblowers, and ensure that authorship, supervision, and evaluation processes are fair.

Best Practices for Responsible Scholarship

A robust integrity practice includes the following commitments:

  • Define the social and scholarly value of the project before collecting data.
  • Map stakeholders, power relationships, foreseeable harms, and affected groups.
  • Obtain meaningful consent and communicate participation conditions clearly.
  • Use data minimization, secure storage, controlled access, and documented retention practices.
  • Keep an auditable record of preprocessing, analytical decisions, software versions, and changes to the protocol.
  • Separate exploratory from confirmatory analyses and report limitations honestly.
  • Disclose funding, conflicts of interest, use of external tools, and material contributions.
  • Use independent review or peer challenge for high-risk decisions.
  • Correct the record promptly when errors are discovered.
  • Treat legal compliance as a minimum requirement and apply broader ethical reasoning where necessary.

Current Developments and Emerging Directions

Research ethics is increasingly concerned with algorithmic accountability, privacy-preserving analytics, data sovereignty, open research, and responsible artificial intelligence. Automated systems can make decisions at a scale that exceeds individual oversight, increasing the importance of impact assessments, documentation, human review, and contestability.

There is also growing attention to whose knowledge counts. Decolonial and participatory approaches challenge extractive research relationships in which communities provide data but receive little influence or benefit. These approaches do not eliminate the need for methodological rigor; they broaden the conception of rigor to include context, reciprocity, and accountability.

The future of research integrity will depend not only on individual virtue but also on institutional design. Incentive systems, doctoral training, journal policies, data infrastructures, and evaluation criteria must reward careful, transparent, and socially responsible work rather than publication volume alone.

Chapter Summary

Research ethics governs the moral acceptability of research, while research integrity concerns honesty, rigor, transparency, and accountability across the research lifecycle. Epistemic responsibility requires researchers to ensure that conclusions are proportionate to evidence and to acknowledge uncertainty and error. Misconduct includes fabrication, falsification, and plagiarism, but ethical failures also arise through selective reporting, inadequate privacy protection, conflicts of interest, and unfair treatment.

Deontology emphasizes duties; consequentialism examines benefits and harms; virtue ethics focuses on scholarly character; rights-based ethics protects legitimate claims; justice examines the distribution of burdens and benefits; and care ethics emphasizes relationships, vulnerability, and context. These frameworks are complementary tools for analyzing complex decisions. Legal compliance provides an essential minimum but does not guarantee ethical scholarship. Responsible researchers integrate ethical reasoning with secure technology, sound methods, transparent reporting, and organizational accountability.

Key Terms

Research ethics: The systematic examination of moral values, duties, rights, risks, and benefits in research.

Research integrity: Honest, rigorous, transparent, fair, and accountable conduct throughout research.

Epistemic responsibility: The duty to form and communicate knowledge claims in proportion to the evidence.

Research misconduct: Serious violations such as fabrication, falsification, or plagiarism.

Fabrication: Inventing data, observations, or results.

Falsification: Manipulating research materials, processes, or data to misrepresent findings.

Plagiarism: Presenting another person’s words, ideas, or work without appropriate acknowledgment.

Questionable research practice: Conduct that undermines reliability without necessarily meeting the formal definition of misconduct.

Informed consent: Voluntary agreement based on adequate understanding of the research and its implications.

Confidentiality: The researcher’s obligation to protect information entrusted under restricted conditions.

Privacy: An individual’s interest in controlling access to personal information or activities.

Conflict of interest: A situation in which secondary interests could improperly influence professional judgment.

Deontology: An ethical approach centered on duties, rules, and principles.

Consequentialism: An ethical approach that evaluates conduct by its foreseeable outcomes.

Virtue ethics: An approach emphasizing moral character and practical judgment.

Justice: The ethical concern with fairness in the distribution of burdens, benefits, and recognition.

Care ethics: An approach emphasizing relationships, vulnerability, attentiveness, and responsibility.

Legal compliance: Conformity with applicable laws, regulations, contracts, and institutional rules.

Open science: Practices that increase transparency and accessibility while respecting privacy, security, and rights.

Algorithmic accountability: Responsibility for the design, effects, transparency, and contestability of automated systems.

Review Questions

Short Answer Questions

1. Distinguish research ethics from research integrity.

2. What is epistemic responsibility, and why is it important in doctoral research?

3. Define fabrication, falsification, and plagiarism.

4. Why is legal compliance considered a minimum rather than a complete ethical standard?

5. State two ethical risks associated with artificial intelligence in research.

Long Answer Questions

1. Compare deontological, consequentialist, and virtue-ethical approaches to research ethics.

2. Explain how rights and justice provide different but complementary perspectives on participant protection.

3. Discuss ethical responsibilities at the design, data-management, analysis, and reporting stages of research.

4. Analyze the relationship between research culture, institutional incentives, and research integrity.

5. Explain why technical accuracy does not by itself establish the ethical acceptability of an organizational prediction model.

Analytical / Application Questions

1. A sponsor asks a doctoral researcher to remove unfavorable findings from a report while claiming that the contract permits editorial review. Analyze the situation using at least three ethical frameworks and recommend a response.

2. A researcher plans to scrape publicly visible employee comments from an online forum and use them to assess managerial quality. What ethical, legal, privacy, and methodological questions should be addressed before proceeding?

3. An AI-based recruitment model has high overall predictive accuracy but rejects applicants from one demographic group at a substantially higher rate. Develop an ethically defensible evaluation and governance plan.

22. Multiple Choice Questions with Answers

Question 1

Which statement best captures epistemic responsibility in research?

A. Following every institutional rule without further judgment

B. Ensuring that knowledge claims are justified and proportionate to the evidence

C. Maximizing the number of publications produced from a dataset

D. Allowing sponsors to determine which findings are credible

Correct Answer: B. Ensuring that knowledge claims are justified and proportionate to the evidence

Question 2

A researcher invents survey responses that were never collected. This is primarily an example of:

A. Falsification

B. Fabrication

C. Plagiarism

D. An unavoidable research error

Correct Answer: B. Fabrication

Question 3

Which ethical framework focuses most directly on duties such as truthfulness and honoring consent?

A. Consequentialism

B. Care ethics

C. Deontology

D. Justice ethics

Correct Answer: C. Deontology

Question 4

A company legally provides employee data to a researcher, but employees were not informed that the data would be used for a new predictive system. What does this most clearly illustrate?

A. Legal compliance always establishes ethical acceptability

B. The distinction between legal compliance and ethical responsibility

C. That confidentiality is irrelevant when data are accurate

D. That research involving employees cannot be ethical

Correct Answer: B. The distinction between legal compliance and ethical responsibility

Question 5

Which response best reflects justice-based reasoning?

A. Selecting participants only because they are easiest to contact

B. Distributing research burdens and benefits fairly across affected groups

C. Reporting only results that benefit the funding organization

D. Avoiding all research involving unequal populations

Correct Answer: B. Distributing research burdens and benefits fairly across affected groups

Question 6

In the workforce prediction case, why was excluding employees with incomplete records ethically problematic?

A. Incomplete records can never be used in any analysis

B. The exclusion could disproportionately remove particular groups and distort conclusions

C. Statistical models require every employee to have identical data

D. Missing data automatically prove that the model is fabricated

Correct Answer: B. The exclusion could disproportionately remove particular groups and distort conclusions

Question 7

Which practice most directly strengthens the auditability of a computer-assisted research workflow?

A. Deleting intermediate files after obtaining the desired result

B. Keeping undocumented manual changes to the dataset

C. Maintaining version histories and records of preprocessing decisions

D. Uploading identifiable data to a public repository

Correct Answer: C. Maintaining version histories and records of preprocessing decisions

Question 8

A researcher discovers an honest coding error that changes a published conclusion. What is the most ethically responsible action?

A. Conceal it because the error was unintentional

B. Delete the underlying data

C. Promptly disclose and correct the scholarly record

D. Blame the software used for analysis

Correct Answer: C. Promptly disclose and correct the scholarly record

Question 9

Which statement about generative AI in research is most defensible?

A. AI-generated text is automatically accurate if it is fluent

B. Uploading confidential raw data is acceptable because the tool is automated

C. Researchers remain responsible for verifying outputs and protecting data

D. AI systems can assume authorship and accountability for a paper

Correct Answer: C. Researchers remain responsible for verifying outputs and protecting data

Question 10

Care ethics would draw particular attention to which feature of an employee research study?

A. Only whether the sample reaches statistical power

B. The relational vulnerability and pressure employees may experience when invited to participate

C. Whether the sponsor’s preferred hypothesis is confirmed

D. Whether the study produces a significant p-value

Correct Answer: B. The relational vulnerability and pressure employees may experience when invited to participate

Research Ethics & Computer Applications
Chapter 1 of 15

Research Ethics & Computer Applications

Chapter 2
Ethical Governance, Codes and Regulatory Systems

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

2. Ethical Governance, Codes and Regulatory Systems

Introduction and Context

Research ethics is not limited to obtaining a signed consent form or completing an institutional application. It is a system of governance through which an organisation decides whether research is permissible, how risks will be controlled, who is accountable for decisions, and what remedies are available when standards are breached. In doctoral business research, this system may involve universities, corporations, consultants, data custodians, regulators, professional associations, funders, technology providers and research participants located in several jurisdictions.

The governance problem becomes particularly complex when research uses employee records, customer analytics, digital trace data, artificial intelligence, sensitive commercial information or cross-border cloud platforms. A project may be legally permissible but ethically questionable; it may satisfy a professional code yet violate an institutional policy; or it may receive committee approval while remaining poorly governed during implementation. Ethical governance therefore requires more than compliance. It requires reasoned judgment, transparency, accountability and continuous oversight.

This chapter examines the relationship among research ethics committees (RECs), institutional review boards (IRBs), professional codes, institutional policies and international regulatory systems. It also analyses risk classification, conflicts of interest, accountability and cross-border governance. The central argument is that these instruments are complementary rather than interchangeable. Each answers different questions, operates at a different level and carries different forms of authority.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish among RECs, IRBs, professional codes, institutional policies and regulatory systems.

2. Explain major principles used in ethical review and research governance.

3. Classify research risk and determine proportionate review requirements.

4. Analyse conflicts of interest, accountability and compliance failures.

5. Evaluate ethical governance arrangements for cross-border and digitally enabled research.

6. Apply governance frameworks to complex organisational research decisions.

7. Critically assess the limitations of committee-based and compliance-oriented approaches.

The Architecture of Ethical Governance

Ethical governance can be understood as the interaction of five layers. The first is law and regulation, which establishes enforceable minimum obligations. The second is institutional governance, including policies, procedures, delegations and sanctions. The third is independent ethical review, normally undertaken by an REC or IRB. The fourth is professional self-regulation, expressed through disciplinary codes and standards. The fifth is project-level practice, including protocols, consent procedures, data controls, monitoring and reporting.

These layers overlap but should not be confused. A law may require protection of personal data, while an institutional policy may specify how data-management plans are approved. An REC may assess whether a proposed interview study exposes participants to unreasonable harm. A professional code may require researchers to avoid deception or disclose conflicts. The principal investigator must then translate these requirements into recruitment scripts, access controls, retention schedules and reporting procedures.

A useful governance test asks four questions:

  • Authority: Who has the power to approve, restrict or stop the research?
  • Standard: Which ethical or legal rule is being applied?
  • Evidence: What information supports the decision?
  • Accountability: Who is answerable if the decision or implementation causes harm?

Weak governance often occurs when responsibility is diffused. For example, a university may assume that an external data provider has obtained valid consent, while the provider assumes that the university has completed ethical review. Effective governance assigns responsibilities explicitly and creates an auditable record of decisions.

Research Ethics Committees and Institutional Review Boards

An REC is a body established to review the ethical acceptability of research involving human participants, human data or human biological materials. The term is widely used in many jurisdictions. An IRB performs a closely related function, particularly within systems influenced by United States research regulation. Although terminology and legal powers differ, both bodies generally examine risks, potential benefits, participant selection, consent, privacy, confidentiality, safeguards and the qualifications of the research team.

The committee is not merely a quality-control office. Its distinctive value lies in independent, multidisciplinary judgment. A committee may include researchers, legal or policy specialists, community representatives and members who are not affiliated with the institution. Independence is essential because the institution may have financial, reputational or strategic interests in the research being approved.

Ethical review normally considers:

1. Whether the research question justifies involving human participants.

2. Whether participant selection is fair and avoids exploiting vulnerable groups.

3. Whether risks are minimised through appropriate design.

4. Whether consent is voluntary, informed and comprehensible.

5. Whether privacy, confidentiality and data security are adequate.

6. Whether compensation is appropriate and not coercive.

7. Whether monitoring, adverse-event reporting and withdrawal procedures are credible.

8. Whether the investigators have the competence and resources to conduct the study.

Approval is not a guarantee that research is ethical. It is a conditional authorisation based on the information available at the time of review. Researchers remain responsible for conducting the approved protocol, reporting deviations and seeking approval for substantive changes. Committees also have a continuing oversight role, which may include progress reports, amendments, serious adverse-event notifications and final reports.

The terms REC and IRB should not be treated as universally identical. Their composition, jurisdiction, registration requirements and enforcement powers depend on national law and institutional arrangements. A doctoral researcher must therefore examine the relevant local framework rather than rely on terminology alone.

Professional Codes and Institutional Policies

Professional codes translate broad values into expectations for members of a discipline. Codes commonly address integrity, competence, honesty, respect, confidentiality, conflicts of interest, authorship, data management, publication and responsible communication. Their authority may be moral, contractual, disciplinary or reputational. A professional association may investigate complaints or impose sanctions, but its powers are not necessarily equivalent to those of a public regulator.

Codes are especially important in business research because the researcher may simultaneously be an employee, consultant, manager, evaluator or adviser. A management researcher can possess legitimate access to organisational data while still lacking ethical authority to use it for a different purpose. Professional codes help identify duties that may not be fully specified by law or an institutional form.

Institutional policies are the organisation's operational expression of ethical and regulatory commitments. They may govern human research, data protection, information security, research misconduct, authorship, intellectual property, records retention, export controls and use of artificial intelligence. Policies clarify who must apply for review, which projects qualify for exemption or expedited review, how records are maintained and what happens after non-compliance.

A policy is not automatically ethical merely because it is institutional. Policies may be outdated, designed primarily for administrative convenience or inconsistent with the legitimate interests of participants. Researchers must interpret policies in light of underlying principles and applicable law. Where standards conflict, the more protective and legally valid requirement should normally guide conduct, subject to specialist advice.

International Regulatory Systems and Cross-Border Research

International research raises questions of jurisdiction, applicable law, data transfer, participant protection and institutional responsibility. The location of the researcher is only one relevant factor. Governance may be affected by the location of participants, the institution sponsoring the study, the servers processing the data, the place where an intervention occurs and the contractual terms governing data access.

International instruments often provide principles rather than a single uniform code. Important themes include respect for persons, scientific and social value, favourable risk–benefit assessment, fair selection, privacy, transparency, accountability and protection of vulnerable populations. National systems implement these principles differently. Some emphasise institutional review; others rely more heavily on governmental authorisation, data-protection regulators or sector-specific rules.

Cross-border governance should address at least the following matters:

  • Which jurisdictions' laws apply to collection, storage, analysis and publication?
  • Which committee or committees must review the project?
  • Is approval in one country recognised in another?
  • How will consent, withdrawal and participant complaints operate across languages and institutions?
  • Are international data transfers lawful and secure?
  • Who is the data controller, processor or equivalent responsible party?
  • What happens if one jurisdiction permits a practice that another prohibits?
  • How will local researchers and communities share authority, credit and benefits?

A single approval is not necessarily sufficient. Dual or joint review may be appropriate where a host-country institution has contextual knowledge and the sponsoring institution has legal or funding responsibilities. However, multiple reviews can create duplication, inconsistent conditions and uncertainty over who has final authority. A written reliance or cooperation agreement should define roles, reporting duties, amendment procedures and responses to incidents.

Risk Classification and Proportionate Review

Risk classification is a central governance technique. Minimal risk generally refers to the probability and magnitude of harm that are no greater than those ordinarily encountered in everyday life or routine examinations, though its exact meaning varies by jurisdiction. More-than-minimal-risk research may involve sensitive questions, deception, psychological distress, employment consequences, reputational damage, discrimination, financial loss, physical danger or misuse of personal data.

Risk is not determined only by the research method. An anonymous survey about ordinary consumer preferences may be low risk, while a seemingly simple interview about workplace harassment may be high risk because disclosure could affect employment and safety. Risk is contextual and includes the possibility of group harms, social harms and harms arising after publication.

A proportionate risk assessment should consider:

Probability: How likely is harm to occur?

Magnitude: How serious would the harm be?

Reversibility: Can the harm be corrected, or is it permanent?

Identifiability: Could an individual or small group be re-identified?

Vulnerability: Do participants have reduced autonomy or increased exposure to coercion?

Control capacity: Can the research team prevent, detect and respond to harm?

Risk classification should be revisited when the protocol changes, unexpected information emerges or new technologies are introduced. For example, combining apparently harmless datasets through machine learning may create new identification risks. Ethical review should therefore examine the whole data lifecycle rather than only the moment of collection.

Accountability, Responsibility and Conflicts of Interest

Accountability means being answerable for decisions, actions and omissions. Responsibility may be distributed among the principal investigator, supervisors, sponsors, institutional officers, data custodians, vendors and committee members. Distribution does not eliminate accountability; it requires clear allocation and documentation.

A sound accountability system includes named decision owners, approval records, training evidence, version-controlled protocols, secure research records, incident reporting and mechanisms for participant complaints. It also distinguishes individual error from organisational failure. A researcher who makes an honest mistake after following a defective institutional procedure should not be treated in the same way as someone who deliberately conceals misconduct.

A conflict of interest exists when a secondary interest could improperly influence professional judgment or could reasonably appear to do so. Financial interests are only one form. Other conflicts include a supervisor recruiting their own employees, a researcher evaluating a programme they designed, a sponsor controlling publication, personal relationships with participants and institutional pressure to produce favourable results.

Conflicts should be disclosed, assessed and managed rather than merely declared. Management options include independent recruitment, separation of data access from managerial authority, independent analysis, disclosure in publications, recusal from decisions, limits on sponsor influence and appointment of an external monitor. A disclosed conflict remains ethically significant if safeguards are inadequate.

Compliance and Its Limits

Compliance refers to adherence to applicable laws, regulations, policies, approvals and contractual requirements. It is necessary because research depends on predictable standards and enforceable protections. Yet compliance is not equivalent to ethicality. A consent form may satisfy a formal requirement while remaining incomprehensible. An institution may comply with a retention policy that keeps data longer than participants reasonably expected. A project may be approved but implemented in a way that creates unanticipated coercion.

The distinction can be expressed as follows:

  • Compliance asks: Have required rules and procedures been followed?
  • Ethical governance asks: Are the purposes, means and consequences justifiable, and are affected people treated with respect?

A mature organisation combines rule-based controls with deliberation, professional judgment and learning. It encourages reporting of near misses, protects good-faith whistleblowers and investigates patterns rather than only individual violations.

Digital Research, Data Governance and Artificial Intelligence

Computer applications have changed both the opportunities and the risks of business research. Online platforms enable large-scale surveys, behavioural observation, automated recruitment, text mining, sentiment analysis and experimentation. These methods can reduce cost and increase reach, but they may obscure how data are collected, inferred and used.

Digital governance should cover data provenance, lawful access, data minimisation, encryption, authentication, role-based permissions, secure transfer, retention and deletion. Researchers should distinguish identifiable, pseudonymised and anonymised data. Pseudonymisation reduces direct identifiers but does not necessarily remove re-identification risk. Anonymisation is a contextual claim, not simply the removal of names.

Artificial intelligence introduces additional concerns. Models may infer sensitive attributes, reproduce historical bias, generate fabricated citations or make opaque decisions about inclusion and exclusion. If an AI system is used for coding interviews, screening applicants or analysing employee data, the researcher must document the tool, validation process, human oversight and limitations. Confidential data should not be entered into public systems without authorisation. Participants should not be misled about significant automated processing where transparency is ethically relevant.

An Illustrative Case: The Global Employee Analytics Project

Background

A fictional multinational consultancy, Meridian Advisory, commissions a doctoral researcher to investigate employee burnout across six countries. The project proposes an online survey linked to absence records, performance ratings and anonymised chat metadata. The sponsor wants a predictive model that identifies employees likely to resign.

Situation and Problem

The company promises confidentiality, but local managers will receive team-level reports. Employees may fear that participation or negative responses will affect promotion. The data will be stored on cloud servers in a third country. The sponsor also requests the right to review manuscripts before publication and to remove commercially sensitive findings.

Analysis

The project is not automatically low risk merely because the survey is online. Employment dependence creates a power imbalance. Linking survey data to performance records increases identifiability and may generate adverse employment consequences. Chat metadata may reveal sensitive information not reasonably expected by employees. Predictive modelling creates a risk that an inaccurate classification will stigmatise individuals or influence managerial decisions.

The project also presents several governance layers. The university REC must assess participant welfare and consent. The company must apply its employment and information-security policies. Data-protection requirements may differ across the six countries and the cloud-storage location. The researcher has a conflict because the sponsor funds the project and may influence publication.

Approach and Strategy

The researcher redesigns the project. Participation is recruited by an independent research office rather than line managers. Individual-level predictions are prohibited; only sufficiently large aggregated groups are reported. Performance and absence records are not linked unless a separate, justified consent process is approved. Chat content is excluded, and only narrowly defined, aggregated metadata are considered. A data-protection impact assessment, access-control plan and deletion schedule are prepared.

The sponsor may review manuscripts for factual accuracy and legitimate confidentiality concerns but cannot suppress results or alter conclusions. A disclosure statement identifies the funding relationship. Local partners advise on language, workplace norms and complaint procedures. The university and host organisations sign an agreement allocating incident reporting and oversight responsibilities.

Outcome

The revised study produces less commercially attractive predictions but stronger participant protection and more credible findings. The project demonstrates that ethical governance can alter the research question itself rather than merely add paperwork. It also shows that anonymity claims must be tested against organisational context and available datasets.

Learning Points

The case illustrates that consent is weakened by employment dependency, risk increases through data linkage, cross-border storage requires explicit governance, and conflict management must address sponsor influence. It further demonstrates that the most ethical solution may involve reducing analytical ambition in order to protect autonomy and fairness.

Challenges and Common Governance Failures

Several recurring failures deserve critical attention. First, researchers may treat committee approval as a one-time event and fail to report protocol changes. Second, institutions may use generic forms that do not capture algorithmic inference, group harms or workplace coercion. Third, committees may lack expertise in cybersecurity, data science or local culture. Fourth, risk assessment may focus on physical harm while underestimating reputational, economic and psychological harms.

Other failures include inadequate records, unclear ownership of data, excessive retention, weak vendor contracts, inappropriate reliance on foreign approval, conflicts hidden behind broad disclosure statements and failure to provide accessible complaint channels. Cross-border studies may also become ethically extractive when local researchers provide access but have little influence over research questions, authorship or benefits.

Committees themselves have limitations. They may be overburdened, conservative, inconsistent or influenced by institutional risk aversion. Standardised forms can encourage procedural thinking. Independent review is therefore necessary but not sufficient. Ethical capacity must also exist within research teams and throughout the organisation.

Best Practices for Doctoral Researchers and Institutions

A robust governance process begins before data collection. Researchers should map all stakeholders, jurisdictions, data flows, risks and decision points. They should prepare a protocol that explains not only what will be done, but why the design is proportionate and how foreseeable harms will be controlled.

Practical good practice includes:

  • Identify the legal, institutional, professional and contractual standards that apply.
  • Seek review before recruitment or data access, and obtain amendment approval when the protocol changes.
  • Use plain-language consent and test whether participants understand material risks.
  • Separate participation from managerial authority wherever power imbalances exist.
  • Minimise data collection and avoid retaining information without a defensible purpose.
  • Maintain a current data map, access register and incident-response procedure.
  • Disclose and actively manage conflicts of interest.
  • Include local expertise in cross-border research and share benefits fairly.
  • Document decisions, assumptions, exceptions and reasons for rejecting alternatives.
  • Treat ethical review as continuing oversight rather than an administrative hurdle.

Emerging governance practice is moving toward privacy by design, algorithmic impact assessment, responsible innovation, open research documentation and greater participation by affected communities. These approaches do not replace legal compliance or committee review; they extend governance into design, procurement, deployment and post-study evaluation.

Chapter Summary

Ethical governance is a layered system involving law, institutional policies, independent ethical review, professional codes and project-level practice. RECs and IRBs assess the ethical acceptability of research, while professional codes express disciplinary duties and institutional policies operationalise organisational requirements. International research requires analysis of jurisdictions, data flows, local authority, consent and accountability rather than reliance on one approval.

Risk is contextual and proportionate review must consider probability, severity, reversibility, identifiability, vulnerability and control capacity. Conflicts of interest require active management, not merely disclosure. Compliance is essential but cannot substitute for ethical judgment. Digital research and artificial intelligence intensify concerns about privacy, inference, bias, security and explainability. Effective governance is continuous, documented, independent where necessary and responsive to the people and communities affected by research.

Key Terms

Accountability: The obligation to explain and justify decisions and to accept consequences for actions or omissions.

Anonymisation: Processing data so that individuals are not reasonably identifiable in the relevant context.

Conflict of interest: A situation in which a secondary interest could improperly influence, or appear to influence, professional judgment.

Consent: A voluntary and informed agreement to participate in research or permit specified data use.

Data controller: The person or organisation determining the purposes and means of processing personal data.

Data minimisation: Collecting and retaining only data necessary for a legitimate research purpose.

Institutional policy: An organisation’s formal rule or procedure governing research conduct and administration.

Institutional Review Board: A committee that independently reviews research involving human participants, especially in systems using that terminology.

Minimal risk: Risk no greater than that ordinarily encountered in everyday life or routine activities, subject to applicable law.

Professional code: A disciplinary statement of ethical duties, standards and expected conduct.

Proportionate review: An assessment process whose depth and oversight correspond to the research’s risks and complexity.

Pseudonymisation: Replacing direct identifiers with codes while retaining a possible means of re-identification.

Research Ethics Committee: An independent or institutionally authorised body reviewing the ethical acceptability of research.

Risk classification: Systematic categorisation of potential harms and the controls required to manage them.

Scientific and social value: The justification that research can produce worthwhile knowledge or public benefit.

Stakeholder: An individual or group affected by, involved in or able to influence research.

Vulnerability: A condition that may reduce autonomy or increase exposure to harm or exploitation.

Whistleblower protection: Safeguards for persons who report suspected wrongdoing in good faith.

Review Questions

Short Answer Questions

1. Distinguish between an REC and a professional code.

2. What is meant by proportionate ethical review?

3. Why is committee approval not a guarantee that research will remain ethical?

4. Define conflict of interest and give one example from business research.

5. Explain the difference between pseudonymisation and anonymisation.

Long Answer Questions

1. Critically compare the authority and functions of RECs, IRBs, institutional policies and professional codes.

2. Explain how risk should be classified in a study involving employee data and predictive analytics.

3. Analyse why compliance may be necessary but insufficient for ethical research governance.

4. Discuss the principal governance challenges in cross-border research involving cloud-based data storage.

5. Evaluate the role of accountability and independent oversight in preventing research misconduct.

Analytical / Application Questions

1. A university researcher plans to analyse public social-media posts and combine them with customer records obtained from a commercial partner. Design a governance plan addressing consent, privacy, risk, conflicts and data security.

2. An international sponsor requires the right to approve all publications arising from a doctoral project. Analyse the ethical and governance implications and propose safeguards.

3. A company wants to use an AI model to identify employees at risk of resignation. Apply the chapter’s risk and accountability framework to determine whether, and under what conditions, the project should proceed.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes ethical governance from simple compliance?

A. Ethical governance requires following only professional association rules.

B. Ethical governance asks whether purposes, methods and consequences are justifiable in addition to meeting formal requirements.

C. Compliance is broader because it includes participant welfare and moral judgment.

D. Ethical governance eliminates the need for institutional approval.

Correct Answer: B. Ethical governance asks whether purposes, methods and consequences are justifiable in addition to meeting formal requirements.

Question 2

What is the primary reason for multidisciplinary and independent membership of an REC or IRB?

A. To ensure that every committee member conducts part of the study.

B. To allow the sponsor to control the approval process.

C. To provide varied expertise and reduce institutional or investigator bias.

D. To replace the researcher’s responsibility for implementation.

Correct Answer: C. To provide varied expertise and reduce institutional or investigator bias.

Question 3

Which feature most clearly increases the risk of an otherwise ordinary employee survey?

A. The survey uses an online questionnaire.

B. The survey concerns general consumer preferences.

C. Responses are linked to performance ratings and may affect employment decisions.

D. The survey is completed during working hours.

Correct Answer: C. Responses are linked to performance ratings and may affect employment decisions.

Question 4

A researcher discloses that a sponsor funds the study but allows the sponsor to remove unfavourable findings. What is the main governance failure?

A. The study lacks any possible social value.

B. Disclosure alone has not managed the sponsor’s conflict of interest.

C. Funding automatically invalidates all research.

D. The researcher has used pseudonymisation incorrectly.

Correct Answer: B. Disclosure alone has not managed the sponsor’s conflict of interest.

Question 5

Which arrangement is most appropriate for a cross-border study involving institutions in two countries?

A. Assume that approval in the researcher’s country applies everywhere.

B. Ignore the location of cloud servers because storage is technical rather than ethical.

C. Define applicable jurisdictions, review responsibilities, data transfers and incident reporting in a written agreement.

D. Permit each institution to change the protocol independently without notification.

Correct Answer: C. Define applicable jurisdictions, review responsibilities, data transfers and incident reporting in a written agreement.

Question 6

Why may pseudonymised data remain ethically sensitive?

A. Pseudonymisation always makes data publicly identifiable.

B. A separate key or linked dataset may permit re-identification.

C. Pseudonymised data cannot be encrypted.

D. Pseudonymisation removes the need for access controls.

Correct Answer: B. A separate key or linked dataset may permit re-identification.

Question 7

In the Meridian Advisory case, which redesign most directly addressed employment-related coercion?

A. Allowing line managers to recruit their own employees.

B. Increasing the financial reward for participation.

C. Using an independent research office for recruitment and reporting only aggregated results.

D. Giving the sponsor access to individual predictions.

Correct Answer: C. Using an independent research office for recruitment and reporting only aggregated results.

Question 8

Which statement about conflicts of interest is most accurate?

A. Only financial interests qualify as conflicts.

B. A conflict disappears once it is disclosed.

C. Conflicts should be assessed and managed through safeguards such as recusal or independent analysis.

D. Conflicts are relevant only after publication.

Correct Answer: C. Conflicts should be assessed and managed through safeguards such as recusal or independent analysis.

Question 9

What is a central limitation of committee-based ethical review?

A. Committees make all researchers legally immune from misconduct claims.

B. Committees may be overburdened or lack expertise in areas such as cybersecurity and artificial intelligence.

C. Committees cannot review research involving human participants.

D. Committees are designed to maximise commercial returns.

Correct Answer: B. Committees may be overburdened or lack expertise in areas such as cybersecurity and artificial intelligence.

Question 10

Which practice best reflects data minimisation?

A. Collecting all potentially useful data for indefinite future research.

B. Retaining direct identifiers because they may improve publication quality.

C. Collecting and retaining only information necessary for the approved research purpose.

D. Transferring data to a vendor before determining the research purpose.

Correct Answer: C. Collecting and retaining only information necessary for the approved research purpose.

Research Ethics & Computer Applications
Chapter 2 of 15

Research Ethics & Computer Applications

Chapter 3
Ethics-by-Design and Review Processes

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

3. Ethics-by-Design and Review Processes

Introduction and Context

Research ethics is often treated as an approval requirement completed shortly before data collection. That view is inadequate for doctoral research. Ethical quality is not added after a study has been designed; it is built into the study’s questions, theoretical assumptions, methods, technologies, relationships, and plans for dissemination. This approach is known as ethics-by-design.

Ethics-by-design requires the researcher to ask, from the earliest stage: Who may be affected by this research? What benefits are reasonably foreseeable? What harms might occur, including harms that are indirect, cumulative, informational, reputational, or organizational? Who bears the burdens of participation, and who is likely to benefit from the findings? How will autonomy, privacy, dignity, and fairness be protected?

In business administration research, these questions are especially important because studies frequently involve employees, managers, customers, entrepreneurs, organizations, commercially sensitive data, digital platforms, and artificial intelligence. A seemingly low-risk survey may expose an employee to workplace retaliation. An interview about organizational misconduct may create professional or legal risks. Algorithmic analysis may reproduce discrimination or infer sensitive characteristics without participants’ knowledge.

Ethical review therefore serves two related purposes. First, it protects participants, researchers, institutions, communities, and other affected parties. Second, it improves the validity and legitimacy of research by requiring clarity about purpose, population, procedures, data, risks, and accountability. Ethical review is not a substitute for scholarly judgment, nor is approval a guarantee that a study is ethically perfect. Rather, it is a structured process of critical scrutiny that should continue throughout the research lifecycle.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Explain ethics-by-design and relate it to proportionality, beneficence, non-maleficence, justice, and respect for persons.

2. Identify ethical issues in research questions, sampling, recruitment, data collection, analysis, storage, and dissemination.

3. Prepare a coherent ethics application and a defensible risk–benefit assessment.

4. Design proportionate mitigation, monitoring, amendment, and adverse-event response procedures.

5. Evaluate the ethical implications of digital tools, organizational data, analytics, and artificial intelligence.

6. Critically assess common weaknesses in ethics review and develop professionally responsible research practices.

From Ethical Principles to Research Design

Ethical principles become meaningful only when translated into design decisions. Five principles provide a useful foundation, although their interpretation may vary across legal systems, disciplines, and institutional policies.

Respect for persons recognizes autonomy, dignity, privacy, and the right to make an informed and voluntary decision about participation. It also requires attention to people whose autonomy may be constrained, such as employees recruited by supervisors, economically dependent workers, minors, or individuals with limited digital literacy. Respect is not satisfied by obtaining a signature. Participants must receive understandable information, have a genuine opportunity to decline, and be able to withdraw within the practical limits explained to them.

Beneficence requires researchers to seek meaningful benefits. Benefits may include improved organizational practices, knowledge, policy development, or participant learning, but they must not be exaggerated. A study should have sufficient scientific and social value to justify the resources and burdens it imposes.

Non-maleficence requires avoiding or minimizing harm. Harm may be physical, psychological, social, economic, legal, professional, cultural, or informational. In business research, professional harm is particularly significant. Disclosure of dissatisfaction with a manager, evidence of fraud, or participation in a union-related study may affect employment, promotion, reputation, or workplace relationships.

Justice concerns the fair distribution of research burdens and benefits. Researchers should not recruit a population merely because it is accessible, powerless, or unlikely to challenge the study. Nor should potentially beneficial research systematically exclude groups whose experiences are relevant. Justice also requires fair inclusion, accessible procedures, and attention to digital and organizational inequalities.

Proportionality links ethical scrutiny to the level and type of risk. A confidential anonymous survey on non-sensitive preferences may require fewer safeguards than an interview about workplace harassment or an analysis of identifiable health and employment records. Proportionality does not mean that low-risk studies receive no review. It means that the intensity of review, documentation, monitoring, and protection should be commensurate with foreseeable risks and the study’s social value.

These principles may conflict. For example, a study may promise substantial public benefit but expose a small group to reputational risk. A researcher may wish to preserve raw data for future analyses, while respect for participants requires limiting secondary use. Ethical reasoning involves identifying such tensions, making them explicit, and providing a defensible justification for the chosen balance.

Ethics-by-Design Across the Research Lifecycle

Ethical reasoning begins with the research question. A question that assumes a stigmatizing or deficit-based characterization of a population may produce ethical problems before sampling begins. Researchers should consider whether the question is necessary, whether it can be framed without stereotyping, and whether the expected knowledge justifies involving the proposed participants. Questions concerning organizational misconduct, inequality, surveillance, or vulnerable workers require particular care because their consequences may extend beyond the sample.

The design should then specify what evidence is necessary. Collecting more data than required increases exposure without necessarily improving inference. Data minimization is therefore both a privacy practice and a methodological discipline. If age bands are adequate, exact birth dates may be unnecessary. If a study only needs organizational level, names and employee numbers should not be collected.

Sampling and recruitment also have ethical dimensions. A gatekeeper may facilitate access but can unintentionally pressure people to participate. Employees should not be led to believe that participation is mandatory or visible to management. Recruitment materials should state who is conducting the research, why the person is being invited, what participation involves, what risks may exist, and how non-participation will affect the individual. Incentives should compensate time and inconvenience without becoming so large that they undermine voluntariness.

Consent is a process of communication rather than a formality. A sound consent process explains the study’s purpose, procedures, duration, risks, benefits, confidentiality arrangements, data uses, withdrawal rights, and contact arrangements. Consent must be specific enough for participants to understand the proposed use of their data. Broad consent for future research may be permissible in some settings, but it should not become a vague authorization for unlimited use. Digital consent requires additional attention to identity, accessibility, comprehension, and the possibility that participants are agreeing through a platform whose data practices they do not understand.

Data collection protocols should anticipate distress, disclosure, and unexpected events. An interviewer studying workplace bullying should know how to pause an interview, offer a break, provide support information, and respond if a participant discloses imminent danger. A researcher studying illegal conduct must understand applicable confidentiality limits and avoid promising absolute secrecy when disclosure may be legally or ethically required.

Data management should be designed before collection. A data management plan normally identifies the categories of data, access permissions, encryption, transfer procedures, retention period, destruction method, backup arrangements, and procedures for correcting or withdrawing data. Pseudonymization replaces direct identifiers with codes, but it does not make data anonymous if the code key or combinations of variables permit re-identification. Small organizational samples are especially vulnerable to deductive disclosure, in which a person can be identified from contextual details even when a name is removed.

Analysis and reporting can create new risks. Researchers should avoid presenting small subgroups in ways that reveal identities, should disclose limitations honestly, and should not alter results to satisfy a sponsor. Confidentiality obligations continue during presentations, publications, teaching, and data sharing. Quotations should be checked for identifying details, not merely names.

Preparing an Ethics Application

An ethics application should function as an operational account of the study, not as promotional writing. Reviewers need enough information to evaluate necessity, feasibility, risk, safeguards, and researcher competence. A well-prepared application commonly includes:

  • the research purpose, questions, theoretical rationale, and social or scholarly value;
  • study design, setting, duration, sample, inclusion and exclusion criteria;
  • recruitment routes, gatekeeper roles, incentives, and consent procedures;
  • data collection instruments and participant-facing materials;
  • foreseeable risks, benefits, burdens, and vulnerable circumstances;
  • privacy, confidentiality, security, retention, destruction, and access arrangements;
  • plans for monitoring, complaints, withdrawal, adverse events, and protocol deviations;
  • researcher qualifications, supervision, conflicts of interest, and relevant training;
  • dissemination, data sharing, secondary use, and communication of findings.

The application should distinguish between a risk inherent in the topic and a risk created by the research procedure. Discussing organizational stress may be emotionally difficult, but linking responses to identifiable employees may create an additional and avoidable risk. This distinction helps researchers design mitigations rather than merely describe dangers.

A useful application uses consistent terminology. “Anonymous” should be used only when identification is not reasonably possible. “Confidential” means that identifying information may be known to the research team but is protected from unauthorized disclosure. “Voluntary” means that refusal does not produce inappropriate disadvantage. “Minimal risk” should not be used casually; it requires a reasoned comparison with the ordinary risks encountered in everyday life or the relevant regulatory standard.

Risk–Benefit Assessment and Mitigation

Risk assessment is an analytical judgment, not a numerical exercise alone. Researchers should consider the probability of an adverse outcome, its severity, who may experience it, how long it may last, whether it is reversible, and whether participants can reasonably anticipate it. A low-probability event may still require strong safeguards if its consequences are severe.

A practical risk register can contain five columns: risk, affected parties, likelihood and severity, mitigation, and residual risk. For example, the risk of employer identification from interview quotations may be mitigated by removing contextual details, using composite quotations, restricting access, and allowing participants to review quotations where appropriate. Residual risk remains if the organizational setting is distinctive; this should be acknowledged rather than concealed.

The preferred order of mitigation is to eliminate unnecessary risk, redesign the procedure, reduce exposure, protect data, prepare support and response mechanisms, and monitor outcomes. Researchers should not rely exclusively on participant warnings. Telling participants that a survey is sensitive does not compensate for weak security or coercive recruitment.

Benefits must be assessed with equal discipline. Direct benefits to participants may be absent, uncertain, or limited to the opportunity to reflect on an experience. General claims such as “society will benefit” are insufficient unless the pathway from findings to use is plausible. A fair assessment distinguishes direct benefit, indirect organizational benefit, broader social value, and benefits to future research.

Review Pathways and Decision Processes

Institutions commonly use a research ethics committee, institutional review board, or equivalent body. Review pathways may include exempt or delegated review for genuinely low-risk projects, expedited review for specified categories, and full committee review for higher-risk or complex studies. The names and legal powers of these pathways vary, so researchers must follow the requirements of the institution and jurisdiction in which the research occurs.

Reviewers generally assess scientific necessity, participant selection, consent, risk–benefit balance, privacy, data security, researcher competence, and fairness. They may approve the study, approve it with conditions, request modifications, defer a decision pending clarification, or reject it. Approval is usually limited to the submitted protocol and time period. It does not authorize substantial changes without review.

The relationship between ethics review and methodological review deserves attention. A poorly designed study may be unethical because it exposes participants to burdens without a reasonable prospect of producing useful knowledge. Conversely, an ethically acceptable method may be rejected if the research question is inadequately specified. Doctoral researchers should therefore seek methodological and ethics advice early rather than treating the ethics committee as the first substantive evaluator.

Amendments, Monitoring, and Adverse Events

An amendment is a proposed change to an approved protocol. Changes to the sample, recruitment route, data categories, consent language, instruments, study duration, personnel, location, or data-sharing arrangements may require approval before implementation. The urgency and type of review depend on the change and institutional rules. Changes necessary to eliminate an immediate hazard may be implemented promptly, but they should be documented and reported as soon as possible.

Monitoring is proportionate oversight during the study. It may involve checking consent records, access logs, data-security controls, recruitment patterns, participant complaints, withdrawal rates, distress indicators, and protocol deviations. Monitoring should not become surveillance of participants. Its purpose is to verify that protections operate as designed and to detect emerging risks.

An adverse event is an unwanted occurrence associated with participation that causes, or has the potential to cause, harm. Examples include a participant experiencing acute distress, accidental disclosure of identifiable data, unauthorized access, retaliation after participation, or an interview creating an unexpected safety concern. A responsible response includes immediate protection of the participant, documentation, notification through the appropriate institutional route, assessment of scope and severity, corrective action, and communication with affected persons where appropriate.

Researchers should distinguish adverse events from breaches of protocol. A missed consent signature may not harm a participant but still represents a compliance failure. Conversely, a participant may experience distress even when all procedures were followed. Both situations require learning and, where necessary, modification of the study.

Digital Research, Analytics, and Artificial Intelligence

Computer applications expand research capability while complicating ethical responsibility. Online surveys can reach large populations but may expose metadata such as IP addresses, timestamps, device information, or location. Cloud storage improves collaboration but introduces questions about jurisdiction, vendor access, retention, and breach notification. Automated transcription may transfer recordings to external systems. Researchers must understand the actual data flows rather than assuming that a platform is secure because it is widely used.

Business researchers increasingly use machine learning, natural-language processing, sentiment analysis, and generative artificial intelligence. These tools may encode bias, infer sensitive attributes, reproduce confidential text, or generate plausible but inaccurate interpretations. A model trained on employee communications could reveal patterns that participants did not expect to be analyzed. Automated classification may also affect which voices are treated as positive, negative, risky, or valuable.

Ethics-by-design for AI research includes documenting the data source, provenance, representativeness, preprocessing, model purpose, performance, uncertainty, human oversight, and access controls. Researchers should not upload identifiable or confidential material to a public AI service without authorization and a defensible data-protection basis. AI-generated outputs require verification; responsibility cannot be transferred to the software. Where automated decisions affect participants, researchers should consider explainability, contestability, discrimination, and the possibility of human review.

Illustrative Case: An Employee Voice Study

Background

A doctoral researcher proposes to study whether psychological safety influences employees’ willingness to report operational problems. The study will combine an online survey with interviews in three business units of a national logistics company.

Situation and Problem

The company offers access through human-resource managers and requests unit-level results. Employees may fear that negative responses will affect promotion. The proposed survey includes job title, tenure, unit, and open-text comments. In one unit, only six employees occupy a specialized role, making identification possible even without names.

Analysis

The research has social and organizational value, but the initial design creates risks of coercion, deductive disclosure, and professional harm. HR involvement may undermine voluntariness. Unit-level reporting may reveal individuals in small groups. Open-text responses may contain names or allegations. The combination of variables may permit re-identification, and employees may misunderstand the researcher’s independence from management.

Approach and Solution

The researcher revises the protocol. Recruitment is conducted by an independent research office, and managers do not know who participated. The survey omits exact job titles and uses broader role categories. Small groups are aggregated or excluded from separate reporting. Open-text responses are optional, and participants are instructed not to identify colleagues. Interview invitations are sent through a secure system, with contact details separated from research data. Results are reported only where a minimum group size is met, and quotations are edited to remove identifying context. The consent statement explains that the study is independent, describes limits to confidentiality, and states that participation will not affect employment.

A data-management plan specifies encrypted storage, role-based access, a limited retention period, and destruction of the contact key after follow-up. The researcher establishes a distress protocol and a process for reporting suspected retaliation. The ethics committee approves the revised protocol with a requirement for a progress report after the survey phase.

Outcome

The revised study produces fewer individually identifiable data and a more credible account of employee experience. Some detailed subgroup comparisons become impossible, but this is accepted as a proportionate trade-off. The study’s limitations explicitly state that aggregation reduces analytical granularity.

Learning Points

Ethical design may require sacrificing some convenience or analytical detail. Independence must be visible, not merely asserted. Small-cell risks are often more important than direct identifiers. A strong ethics application demonstrates how methodological choices and participant protection reinforce one another.

Challenges, Limitations, and Common Mistakes

Several recurring mistakes weaken ethics applications. Researchers sometimes describe risks in generic language, fail to identify who bears them, or claim that a study is harmless because participation is voluntary. Others confuse anonymization with pseudonymization, overlook metadata, or promise confidentiality that cannot realistically be maintained. Recruitment through a participant’s supervisor is often treated as neutral when it may create pressure.

Another problem is protocol drift. Researchers may add questions, recruit through a new organization, use a new software tool, or share data with collaborators without seeking an amendment. Time pressure can encourage retrospective approval, which is generally unacceptable. Researchers should maintain a version-controlled protocol and decision log.

Ethics review also has limitations. Committees may have incomplete knowledge of local workplace culture, rapidly changing technologies, or specialized methodologies. Formal compliance can become a box-ticking exercise if researchers do not engage substantively with affected communities. Conversely, excessive proceduralism may burden low-risk research without improving protection. Doctoral researchers should treat review as a dialogue grounded in principles, evidence, and context.

Current Developments and Best Practices

Contemporary practice increasingly emphasizes privacy-by-design, community and participant involvement, open science with responsible data governance, and algorithmic accountability. Participatory approaches can improve relevance and identify risks that researchers would otherwise miss, although participation itself must not shift ethical responsibility onto community representatives.

Best practice includes beginning ethics analysis at question formulation; using data minimization; separating recruitment from managerial authority; preparing clear, accessible consent materials; testing procedures through pilot work; documenting data flows; applying role-based access; planning for small-cell disclosure; training all research personnel; maintaining amendment and incident logs; and reviewing risks when circumstances change.

Researchers should also build an ethical stopping rule. If risks become greater than anticipated, safeguards fail, or the study’s value no longer justifies its burdens, data collection should pause while the protocol is reassessed. Ethical competence is therefore not only the ability to obtain approval. It is the capacity to notice, interpret, and respond responsibly to changing conditions.

Chapter Summary

Ethics-by-design embeds ethical reasoning throughout the research lifecycle rather than treating review as a final administrative hurdle. Respect for persons, beneficence, non-maleficence, justice, and proportionality guide decisions about questions, sampling, recruitment, consent, data, analysis, and dissemination. A strong ethics application explains the study operationally, identifies affected parties, assesses probability and severity of risk, and proposes realistic mitigation. Approval is limited to the authorized protocol; amendments, monitoring, and adverse-event procedures are essential forms of continuing oversight. Digital platforms and AI create additional concerns involving metadata, re-identification, bias, confidentiality, explainability, and human accountability. The central professional obligation is to design research whose knowledge value is achieved without imposing unnecessary or unfair burdens.

Key Terms

Ethics-by-design: The deliberate integration of ethical safeguards into every stage of research design and implementation.

Respect for persons: Recognition of autonomy, dignity, privacy, and the right to make informed choices.

Beneficence: The obligation to pursue meaningful benefits through research.

Non-maleficence: The obligation to prevent or minimize avoidable harm.

Justice: Fair distribution of research burdens, benefits, and opportunities for participation.

Proportionality: Matching ethical safeguards and review intensity to the nature and level of risk.

Informed consent: Voluntary agreement based on understandable information about participation.

Minimal risk: A level of risk judged comparable to ordinary risks under the applicable standard.

Confidentiality: Protection of information entrusted to the research team from unauthorized disclosure.

Anonymity: A condition in which participants cannot reasonably be identified from the data.

Pseudonymization: Replacing direct identifiers with codes while retaining a potential re-identification route.

Data minimization: Collecting and retaining only data necessary for the research purpose.

Risk register: A structured record of risks, affected parties, likelihood, severity, mitigation, and residual risk.

Residual risk: Risk that remains after safeguards have been implemented.

Ethics amendment: A formally submitted change to an approved research protocol.

Adverse event: An unwanted occurrence associated with research that causes or may cause harm.

Protocol deviation: A departure from an approved research procedure.

Deductive disclosure: Identification of a person through combinations of contextual details.

Data governance: Policies and controls governing data access, use, security, retention, and accountability.

Algorithmic accountability: Responsibility for the fairness, transparency, performance, and effects of automated systems.

Review Questions

Short Answer Questions

1. What is meant by ethics-by-design?

2. Distinguish confidentiality from anonymity.

3. Why is proportionality important in ethics review?

4. Identify two professional risks that may arise in business research.

5. What is an ethics amendment?

Long Answer Questions

1. Explain how respect for persons, beneficence, non-maleficence, justice, and proportionality influence research design.

2. Describe the principal components of a doctoral research ethics application.

3. Explain how a researcher should conduct and document a risk–benefit assessment.

4. Discuss the ethical challenges created by digital platforms and artificial intelligence in business research.

5. Explain the relationship between ethics approval, monitoring, amendments, and adverse-event responses.

Analytical / Application Questions

1. A researcher plans to survey employees about misconduct using identifiable email addresses and reports to managers. Analyze the ethical problems and redesign the recruitment, data, and reporting procedures.

2. An interview participant discloses serious workplace retaliation after taking part in a study. Develop an immediate and longer-term response consistent with the chapter’s principles.

3. A doctoral student wants to upload confidential interview transcripts to a free generative-AI tool for thematic coding. Evaluate the proposal and recommend a defensible alternative.

22. Multiple Choice Questions with Answers

Question 1

Which design decision most clearly reflects the principle of proportionality?

A. Applying the same extensive procedure to every study regardless of risk

B. Matching review and safeguards to the foreseeable risks and social value of the study

C. Eliminating all studies involving sensitive topics

D. Allowing researchers to decide that their own studies are risk-free

Correct Answer: B. Matching review and safeguards to the foreseeable risks and social value of the study

Question 2

A survey removes names but retains a rare job title, small department, and unusual tenure category. What is the principal concern?

A. Direct physical harm

B. Inadequate scientific value

C. Deductive disclosure

D. Excessive participant compensation

Correct Answer: C. Deductive disclosure

Question 3

Which action best protects voluntariness when researching employees?

A. Having supervisors distribute a list of participants to management

B. Making participation a condition of workplace training

C. Using an independent recruitment route and explaining that refusal has no employment consequences

D. Offering access only to employees who give favorable responses

Correct Answer: C. Using an independent recruitment route and explaining that refusal has no employment consequences

Question 4

What is the most accurate distinction between confidentiality and anonymity?

A. Confidentiality means no data are collected; anonymity means data are encrypted

B. Confidentiality protects information known to the research team; anonymity means participants cannot reasonably be identified

C. Confidentiality applies only to interviews; anonymity applies only to surveys

D. They are identical terms

Correct Answer: B. Confidentiality protects information known to the research team; anonymity means participants cannot reasonably be identified

Question 5

Which item belongs most directly in a risk register?

A. The researcher’s preferred publication journal

B. The risk, affected parties, likelihood, mitigation, and residual risk

C. A list of unrelated theories

D. The institution’s annual budget

Correct Answer: B. The risk, affected parties, likelihood, mitigation, and residual risk

Question 6

A researcher changes the sample and adds collection of sensitive location data after approval. What should normally occur?

A. The changes should be implemented without documentation

B. The researcher should seek an amendment before making the changes

C. The original consent automatically covers all new data

D. The study should be published immediately

Correct Answer: B. The researcher should seek an amendment before making the changes

Question 7

Which response should occur first after an accidental disclosure of identifiable participant data?

A. Delete all records without investigating

B. Ignore it if no participant has complained

C. Protect affected participants, document the incident, and follow the reporting procedure

D. Publish the names to demonstrate transparency

Correct Answer: C. Protect affected participants, document the incident, and follow the reporting procedure

Question 8

Why may a poorly designed study be ethically problematic even when physical risk is low?

A. It may impose burdens without a reasonable prospect of producing valuable knowledge

B. Low-risk studies never require review

C. Scientific validity is unrelated to ethics

D. Participants are always required to benefit directly

Correct Answer: A. It may impose burdens without a reasonable prospect of producing valuable knowledge

Question 9

Which practice is most appropriate when using AI to analyze confidential research material?

A. Uploading identifiable transcripts to any free public tool

B. Assuming automated outputs are accurate because they are statistical

C. Assessing data flows, authorization, security, bias, and human verification before use

D. Allowing the AI system to make final decisions about participants

Correct Answer: C. Assessing data flows, authorization, security, bias, and human verification before use

Question 10

In the illustrative employee voice case, why were small groups aggregated?

A. To increase managerial access to individual responses

B. To reduce the risk that responses could be linked to particular employees

C. To eliminate the need for consent

D. To guarantee statistically significant findings

Correct Answer: B. To reduce the risk that responses could be linked to particular employees

Research Ethics & Computer Applications
Chapter 3 of 15

Research Ethics & Computer Applications

Chapter 4
Human Participants, Consent and Vulnerability

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

4. Human Participants, Consent and Vulnerability

Introduction and Context

Business research frequently involves people whose experiences, choices, records, opinions, or behaviour become evidence for organizational decisions. Employees may be surveyed about leadership, customers may be interviewed about service failures, suppliers may be assessed through audits, and communities may participate in research concerning environmental or economic effects. Although such studies may appear less risky than clinical or biomedical research, they can expose participants to employment consequences, reputational damage, discrimination, financial loss, emotional distress, or unwanted surveillance.

Research ethics therefore requires more than obtaining a signed form. It requires a defensible relationship among the research question, the participant’s autonomy, the distribution of risks and benefits, the protections applied to data, and the researcher’s obligations to institutions and society. In doctoral business research, this relationship is especially important because studies may involve organizational access, commercially sensitive information, digital platforms, algorithmic systems, and unequal relationships between researchers and participants.

This chapter examines informed, dynamic, and digital consent; confidentiality and anonymity; deception; incentives; power asymmetry; withdrawal; and safeguards for employees, customers, communities, and vulnerable populations. The central argument is that ethical participant research is an ongoing governance process rather than a single administrative event.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the ethical foundations of respect for persons, beneficence, non-maleficence, and justice in business research.

2. Distinguish informed, ongoing, dynamic, electronic, and proxy consent.

3. Evaluate confidentiality, anonymity, pseudonymization, and disclosure risks.

4. Identify ethical problems created by deception, incentives, power asymmetry, and restricted withdrawal.

5. Design safeguards for employees, customers, communities, and vulnerable populations.

6. Assess the implications of digital platforms, automated tools, analytics, and artificial intelligence for participant autonomy and privacy.

7. Develop a proportionate participant-protection plan for a doctoral research project.

Ethical Foundations of Participation

Respect for persons treats participants as autonomous agents capable of making meaningful choices. Autonomy is not satisfied merely because a participant clicks “I agree.” A decision is ethically meaningful when the person receives understandable information, has sufficient opportunity to consider it, is free from inappropriate pressure, and possesses the capacity to decide.

Beneficence requires researchers to pursue worthwhile knowledge and, where possible, produce benefits for participants, organizations, or society. Non-maleficence requires the avoidance or reduction of foreseeable harm. Business research often involves minimal physical risk but significant informational, psychological, professional, and social risks. A question about workplace harassment, financial hardship, political affiliation, or health may create risk even when the research method is only an online questionnaire.

Justice concerns the fair distribution of research burdens and benefits. Organizations should not recruit groups merely because they are accessible, dependent, or unlikely to refuse. Nor should communities bear the reputational or environmental risks of research while others receive the benefits. Justice also requires attention to digital exclusion: a study conducted only through a smartphone application may systematically omit people with limited connectivity, disabilities, low digital literacy, or language barriers.

These principles must be interpreted together. For example, a company may argue that employee monitoring produces organizational benefits, but employees’ autonomy and privacy may still be compromised. Conversely, a study may collect highly sensitive data for an important purpose, but its design is not ethically acceptable if the same objective can be achieved with less intrusive information.

Consent as a Process Rather Than a Signature

The elements of informed consent

Informed consent normally requires disclosure of the study’s purpose, procedures, expected duration, types of data collected, foreseeable risks, possible benefits, confidentiality arrangements, voluntary nature of participation, withdrawal procedures, contact details, and any planned secondary use or sharing of data. Participants should also be told whether participation affects employment, access to services, compensation, grades, or organizational relationships.

Information must be presented in language appropriate to the participants. Technical descriptions of statistical linkage, data retention, or machine-learning training may be accurate but not genuinely understandable. Researchers should test consent materials with people resembling the intended participants and revise them when misunderstanding is likely.

Consent also depends on comprehension. A participant who cannot explain in general terms what will happen has not necessarily made an informed decision, even if the form was read aloud or electronically accepted. Comprehension checks can be proportionate to risk. A high-risk interview may require a conversation and opportunity for questions; a low-risk anonymous survey may require a concise information page and an active agreement statement.

Ongoing and dynamic consent

Traditional consent is often obtained at the beginning of a project and treated as permanent. Dynamic consent recognizes that participants may need opportunities to make further choices as the project develops. Participants may be asked whether their data may be used for related studies, linked with administrative records, deposited in a repository, or processed by external analytical systems.

Dynamic consent is particularly relevant where data are collected over time or where future uses cannot be fully specified at recruitment. It can be implemented through secure participant portals, periodic messages, preference dashboards, or renewed consent at key stages. However, repeated requests can become burdensome and may encourage automatic approval. Dynamic consent should therefore offer meaningful, comprehensible choices rather than a succession of lengthy legal notices.

Digital and electronic consent

Electronic consent may be ethically valid when the participant can review the information, ask questions, indicate agreement, and retain a record. A pre-ticked box, forced acceptance of unrelated terms, or consent hidden in a general privacy policy is weak practice. Digital consent systems should accommodate screen readers, multiple languages, low bandwidth, and alternative channels.

Digital environments create special problems. Participants may not know whether a research survey is hosted by a university, an employer, or a commercial platform. Cookies, device identifiers, IP addresses, geolocation, and platform logs may be collected even when researchers do not ask for them directly. The consent process should identify such collection where relevant and should avoid representing an online study as anonymous when technical metadata could permit identification.

Consent in organizational settings

An organizational gatekeeper may authorize access to a workforce or customer base, but gatekeeper permission does not replace individual consent. A chief executive cannot consent on behalf of employees to participate in interviews, and a platform owner cannot automatically consent on behalf of customers. Organizational authorization and participant consent are separate ethical permissions.

Where a study uses existing records, the researcher must determine whether individual consent is feasible, whether a lawful and ethically defensible alternative exists, and whether the proposed use is compatible with participants’ reasonable expectations. Waivers or alterations of consent require strong justification, minimal risk, and appropriate review; convenience alone is insufficient.

Confidentiality, Anonymity, and the Risk of Re-identification

Anonymity means that the researcher cannot reasonably identify a participant from the data. Confidentiality means that identity may be known to the researcher but is protected from unauthorized disclosure. Pseudonymization replaces direct identifiers with codes, but a person may still be identified if the code key or combinations of attributes are available.

Researchers frequently promise anonymity when they can provide only confidentiality. In a small firm, a statement such as “female senior manager in the only regional office” may identify one person even without a name. Rare occupations, dates, quotations, demographic combinations, and distinctive events can create deductive disclosure. Removing names is therefore not sufficient.

A robust confidentiality plan should specify:

  • what identifying information will be collected and why;
  • who will have access to raw data and linkage keys;
  • how data will be encrypted during transfer and storage;
  • how long records will be retained and when they will be destroyed or anonymized;
  • how quotations, tables, and case descriptions will be edited;
  • whether data will be shared with supervisors, sponsors, repositories, vendors, or artificial-intelligence systems.

Data minimization is both an ethical and methodological principle. If age bands are sufficient, exact birth dates should not be collected. If a general region answers the research question, precise location should be avoided. Researchers should separate contact details from research data and restrict access according to role.

Confidentiality has limits. These may include legal reporting duties, immediate threats of serious harm, or explicit provisions in the consent process. Such limits must be explained before participation. Researchers should not promise absolute secrecy when circumstances may require disclosure.

Deception and Partial Disclosure

Deception occurs when researchers intentionally provide false information or conceal material information that could affect participation. In business research, deception might involve posing as an ordinary customer, withholding the true purpose of a field experiment, or telling employees that a management exercise is unrelated to performance evaluation when it is not.

Deception can sometimes be justified when the research question cannot be answered through transparent methods, the social or scholarly value is substantial, the risk is minimal, no effective non-deceptive alternative exists, and participants are debriefed as soon as practicable. Debriefing should explain what was withheld or misrepresented, why this was necessary, what data were collected, and what choices participants now have, including deletion where feasible.

Deception is particularly problematic when it affects employment, access to services, financial decisions, or emotional well-being. A hidden manipulation that causes an employee to believe dismissal is imminent is not justified merely because it produces interesting findings. The distinction between concealment and deception also matters: omitting unnecessary procedural detail may preserve validity, whereas making a false claim about risk or purpose undermines autonomous choice.

Incentives, Undue Influence, and Voluntariness

Incentives may compensate participants for time, travel, inconvenience, or expertise. They may also improve recruitment and reduce unequal burdens. Ethical concern arises when the incentive is so large, urgent, or targeted that it impairs free choice, particularly for people experiencing poverty, insecure employment, or dependency.

Payment should be proportionate to the time and demands of participation, not contingent on providing a preferred answer. Employees should not be offered rewards by their direct supervisors in a way that makes refusal socially difficult. Customers should not lose ordinary service benefits because they decline research participation. A lottery may create different pressures from a fixed payment, especially where participants misunderstand the probability of winning.

Researchers should distinguish compensation from benefit. Reimbursement for expenses does not need to be treated as a reward, whereas a substantial bonus may require additional review. The consent information should state the amount, timing, conditions, taxation implications where relevant, and whether partial participation receives partial payment.

Power Asymmetry and the Right to Withdraw

Power asymmetry exists when one party controls resources, evaluations, opportunities, information, or access on which another depends. Common examples include supervisor–employee, lecturer–student, employer–temporary worker, platform–seller, researcher–community, and lender–customer relationships. The presence of a power difference does not automatically prohibit research, but it increases the burden of justification and protection.

Safeguards include recruitment by an independent person, private responses, separation of participation records from performance systems, neutral communication, alternative activities, and clear statements that refusal will not affect employment or services. Researchers should avoid recruiting their own direct reports where possible. If this is unavoidable, the study should provide channels through which participation decisions cannot be observed by the supervisor.

Withdrawal must be practical, not merely theoretical. Participants should know how to withdraw, until what stage withdrawal is possible, and what happens to data already analyzed or combined into aggregate results. A researcher may be unable to remove an anonymous response or a result already published, but this limitation must be stated in advance. A technically difficult withdrawal process, such as requiring a participant to remember a long code or contact several offices, weakens voluntariness.

Vulnerability in Business Research

Vulnerability is contextual rather than a fixed label attached permanently to a group. It may arise from limited decision-making capacity, dependency, social marginalization, economic insecurity, language barriers, legal status, illness, age, disability, or the sensitivity of the research topic. Employees in precarious work may be vulnerable in one study but not another; senior executives may be powerful in relation to employees yet vulnerable when discussing personal health or illegal conduct.

Additional protections may include consent from an authorized representative where legally appropriate, assent from the participant where possible, accessible materials, interpreters, privacy during participation, independent advocates, additional time for decisions, and procedures for distress or safeguarding concerns. Researchers should not assume that a representative’s permission eliminates the participant’s own voice.

Community research requires attention to collective as well as individual interests. A study can protect names yet stigmatize a neighborhood, ethnic group, or occupational community through careless reporting. Community consultation, locally appropriate dissemination, shared interpretation, and review of potentially harmful descriptions may be necessary. Consultation should not become a substitute for individual consent where individual participation is required.

A Proportionate Safeguard Framework

A useful doctoral planning approach is to move through six connected questions.

First, what is the participant relationship? Identify whether participants are employees, customers, suppliers, community members, minors, patients, or online users, and map dependencies or gatekeepers.

Second, what could go wrong? Consider physical, psychological, economic, professional, legal, social, informational, and collective harms. Include risks created by publication and data linkage, not only by data collection.

Third, what is the least intrusive design that can answer the question? Reduce the number of variables, use indirect questions where appropriate, avoid collecting identifiers, and separate research from organizational evaluation.

Fourth, how will autonomy be protected? Design understandable consent, independent recruitment, accessible formats, realistic withdrawal, and opportunities for questions or renewed decisions.

Fifth, how will information be governed? Define access, encryption, retention, deletion, transfer, secondary use, vendor management, and breach response.

Sixth, how will the study be monitored? Establish procedures for adverse events, complaints, protocol changes, unexpected disclosures, and periodic review. Ethical approval is not the end of oversight; it is authorization to begin under specified conditions.

Digital Research, Analytics, and Artificial Intelligence

Digital research can enlarge access while making observation less visible. Public availability does not automatically mean ethical usability. A social-media post may be technically public but produced in a context where users did not expect systematic analysis, quotation, profiling, or commercial reuse. Researchers should assess contextual integrity, platform rules, user expectations, and the sensitivity of the data.

Web scraping, cookies, mobile applications, biometric systems, workplace monitoring, and customer analytics can generate inferred information that participants never directly supplied. Predictive models may infer income, health status, political affiliation, or vulnerability from apparently ordinary behaviour. Consent materials should address material inferences when they are reasonably foreseeable.

Artificial-intelligence tools create additional risks. Uploading interview transcripts to a public generative-AI service may expose confidential information, transfer data across jurisdictions, or permit retention for service improvement. AI-assisted coding can reproduce stereotypes, misclassify dialects, or obscure the researcher’s accountability. Researchers should use approved secure systems, remove identifiers, document prompts and transformations, validate outputs, and retain human responsibility for interpretation. Participants should be informed when automated processing is consequential to them or materially changes the use of their data.

Illustrative Case: The Employee Experience Dashboard

Background

A fictional multinational retailer, Meridian Stores, commissions a doctoral researcher to study employee experience across 40 branches. The company proposes a mobile application that combines a weekly mood survey, shift records, absence data, and location information. Senior management wants a dashboard predicting turnover risk and identifying “low-engagement teams.”

Situation and ethical problem

The company offers employees entry into a large prize draw for completing surveys and asks branch managers to encourage participation. The proposed consent page is part of the employment application. It states that data will improve workforce planning but does not explain predictive profiling, manager access, retention, or withdrawal. Because each branch is small, supposedly anonymous comments could be recognizable.

Analysis

The study contains several power asymmetries. Employees may believe participation is expected, and managers can observe who completes the survey. The prize may exert pressure on low-paid workers. Combining location, absence, and mood data creates professional and privacy risks. A turnover prediction could affect promotion or scheduling even if management promises that it is “research only.” The proposed design also confuses organizational permission with employee consent and overstates anonymity.

Approach and safeguards

The researcher separates the academic study from performance management and obtains independent ethics review. Recruitment is conducted by the research team, not branch managers. Participation is voluntary, and employees can complete the survey outside managerial observation. The application collects broad shift categories rather than precise location and stores contact information separately from responses. Results are reported only for sufficiently large groups, and quotations are paraphrased when necessary to prevent recognition.

The consent process explains data linkage, predictive analysis, retention, access restrictions, and withdrawal limits. Employees may choose survey participation without permitting linkage to absence records. The prize draw is replaced with modest, equal compensation for time. The research dataset is prohibited from entering the company’s performance system, and an independent data steward controls access. Any future secondary use requires additional review and, where feasible, renewed consent.

Outcome

The revised design produces less granular data than management initially requested, but it better protects employees and reduces the likelihood that research will become covert surveillance. The company receives aggregate findings about workload and communication, while individual-level predictions are not created. The researcher also documents that some questions remain unanswered because the ethical design intentionally limits collection.

Learning points

The case demonstrates that methodological sophistication does not justify excessive intrusion. Voluntariness must be protected structurally, not merely asserted. Anonymity claims must reflect the possibility of deductive identification. Data minimization can improve trust and validity, and an organization’s interest in actionable analytics does not override participants’ rights.

Common Errors and Governance Challenges

Several recurring errors weaken participant protection. Researchers may treat an ethics form as a compliance exercise, use legalistic consent language, collect data “just in case,” assume public data are free of ethical obligations, or promise anonymity without testing re-identification risks. They may also fail to distinguish research from quality improvement, surveillance, audit, or organizational intervention.

Another error is designing safeguards only for recruitment. Risks may arise later when transcripts are shared, quotations published, datasets linked, or findings returned to a small community. A complete protocol therefore follows data throughout their life cycle. Researchers should maintain an audit trail of consent versions, amendments, access decisions, incidents, and destruction or archiving.

Institutions have governance responsibilities as well. Ethics committees should assess proportionality rather than merely inspect paperwork. Sponsors should not condition funding on access to identifiable data. Organizations should define whether research outputs may influence employment decisions, and contracts with cloud or analytics vendors should address security, jurisdiction, retention, and breach notification.

Current Developments and Best Practice

Contemporary participant research is moving toward privacy-by-design, granular consent, federated or distributed analysis, secure research environments, and community-engaged governance. Privacy-enhancing techniques can reduce the movement of raw data, although methods such as aggregation or differential privacy may reduce analytical precision and require specialist judgment. Transparency reports and participant dashboards can make data practices more visible, but technology cannot substitute for ethical reasoning.

Best practice is proportionate, transparent, inclusive, and revisable. Researchers should involve participants or community representatives in design when appropriate; test materials for comprehension; minimize collection; separate identities from responses; use secure and approved technologies; plan for withdrawal and breaches; monitor unintended effects; and report limitations honestly. Most importantly, they should ask not only whether a study is legally permissible, but whether a reasonable participant would understand and regard the arrangement as fair.

Chapter Summary

Ethical research with human participants rests on respect for autonomy, beneficence, non-maleficence, and justice. Informed consent requires understandable information, comprehension, voluntariness, and realistic opportunities to withdraw. Dynamic and digital consent extend these obligations across changing data uses and online environments. Confidentiality differs from anonymity, and both can be undermined by small samples, data linkage, quotations, and inferred information.

Deception requires strong justification and timely debriefing. Incentives should compensate without becoming undue influence. Power asymmetry demands independent recruitment, privacy, and explicit protection against employment or service consequences. Vulnerability is contextual and requires proportionate safeguards for individuals and communities. Digital analytics and AI introduce risks of invisible observation, predictive inference, re-identification, vendor exposure, and automation bias. A sound participant-protection plan integrates ethical design, data governance, monitoring, and institutional accountability throughout the research life cycle.

Key Terms

Autonomy: The capacity and right of individuals to make voluntary, informed decisions.

Beneficence: The obligation to promote potential benefits and social value.

Confidentiality: Protection of information entrusted to the researcher from unauthorized disclosure.

Consent: A voluntary agreement to participate based on adequate information and understanding.

Data minimization: Collecting only the information necessary for the research purpose.

Deception: Deliberate misrepresentation or concealment of material information from participants.

Deductive disclosure: Identification of a person through a distinctive combination of non-name attributes.

Dynamic consent: An ongoing process that permits participants to make choices as data uses evolve.

Electronic consent: Consent recorded through a digital interface or electronic communication.

Incentive: A payment or benefit offered to encourage or compensate participation.

Informed consent: Agreement made after receiving and understanding relevant study information.

Justice: Fair distribution of research burdens, risks, and benefits.

Pseudonymization: Replacing identifiers with codes while retaining a possible route to re-identification.

Power asymmetry: An unequal relationship in which one party can affect another’s opportunities or welfare.

Privacy: An individual’s interest in controlling access to personal information and personal space.

Re-identification: Linking supposedly de-identified data to a specific person.

Vulnerability: A situational condition that increases exposure to coercion, harm, or reduced decision-making power.

Withdrawal: A participant’s decision to stop participation or request removal of data within stated limits.

Review Questions

Short Answer Questions

1. Why is a signed consent form insufficient by itself to establish informed consent?

2. Distinguish anonymity, confidentiality, and pseudonymization.

3. What is dynamic consent, and when is it particularly useful?

4. Why can incentives become ethically problematic?

5. Identify two safeguards for research involving employees.

Long Answer Questions

1. Explain how autonomy, beneficence, non-maleficence, and justice guide business research with human participants.

2. Compare traditional, dynamic, and digital consent, including their respective risks and safeguards.

3. Discuss how power asymmetry affects recruitment, consent, confidentiality, and withdrawal in employee research.

4. Examine the ethical challenges of deception and explain the conditions under which it might be justified.

5. Develop a data-governance plan for a study involving sensitive customer information and predictive analytics.

Analytical / Application Questions

1. A university researcher wants to survey employees through a platform controlled by their supervisors. Analyze the ethical risks and redesign the recruitment and consent process.

2. A customer study proposes linking survey answers with purchase histories and location data. Decide what information should be disclosed, what data should be minimized, and what withdrawal rights should be offered.

3. A community research project will publish quotations from a small occupational group. Design a reporting and confidentiality strategy that addresses individual and collective harms.

22. Multiple Choice Questions with Answers

Question 1

Which condition most directly supports meaningful informed consent?

A. The consent form is long and legally detailed

B. The participant understands the study and can refuse without penalty

C. A senior manager authorizes participation for the workforce

D. The researcher promises that all findings will be positive

Correct Answer: B. The participant understands the study and can refuse without penalty

Question 2

A study removes names but retains exact job title, branch, age, and a rare event description. What is the primary concern?

A. Random sampling error

B. Deductive disclosure

C. Insufficient financial compensation

D. Failure to use deception

Correct Answer: B. Deductive disclosure

Question 3

Which practice best reflects dynamic consent?

A. Obtaining one permanent signature for every possible future use

B. Allowing participants to make further choices when data uses change

C. Removing all information about secondary data use

D. Requiring participants to approve every statistical calculation

Correct Answer: B. Allowing participants to make further choices when data uses change

Question 4

Why is gatekeeper permission insufficient in employee research?

A. Gatekeepers cannot authorize access to any organization

B. Organizations are never allowed to conduct research

C. Individual employees must still be able to make voluntary participation decisions

D. Employees cannot participate in studies involving organizational data

Correct Answer: C. Individual employees must still be able to make voluntary participation decisions

Question 5

Which incentive presents the greatest risk of undue influence?

A. Reimbursement for local travel

B. A modest payment proportionate to interview time

C. A very large payment offered to economically insecure participants

D. A certificate acknowledging professional contribution

Correct Answer: C. A very large payment offered to economically insecure participants

Question 6

Under which combination is deception most ethically defensible?

A. It is convenient, inexpensive, and likely to produce dramatic results

B. It is necessary, low risk, justified by substantial value, and followed by debriefing

C. It is approved by a company manager without participant review

D. It prevents participants from withdrawing after the study

Correct Answer: B. It is necessary, low risk, justified by substantial value, and followed by debriefing

Question 7

Which design most effectively reduces power asymmetry in an employee survey?

A. Having direct supervisors distribute and monitor completion

B. Linking responses to performance evaluations

C. Using independent recruitment and preventing managers from seeing participation decisions

D. Offering promotion to employees who complete the survey

Correct Answer: C. Using independent recruitment and preventing managers from seeing participation decisions

Question 8

A researcher uploads identifiable interview transcripts to a public AI service. What is the central ethical risk?

A. The transcripts will necessarily become statistically invalid

B. Confidential information may be exposed or retained by an external system

C. The researcher will be unable to conduct qualitative analysis

D. Electronic consent automatically becomes impossible

Correct Answer: B. Confidential information may be exposed or retained by an external system

Question 9

Which action best demonstrates data minimization?

A. Collecting exact birth dates when age bands answer the research question

B. Collecting every available identifier for possible future analysis

C. Collecting only broad regional information when precise location is unnecessary

D. Retaining raw data indefinitely in case the sponsor requests it

Correct Answer: C. Collecting only broad regional information when precise location is unnecessary

Question 10

Why should a researcher state limits on withdrawal during consent?

A. Participants can always remove results from a published article

B. Anonymous or aggregated data may not be identifiable or removable later

C. Withdrawal is legally prohibited after the first interview

D. Researchers are not responsible for explaining data handling

Correct Answer: B. Anonymous or aggregated data may not be identifiable or removable later

Research Ethics & Computer Applications
Chapter 4 of 15

Research Ethics & Computer Applications

Chapter 5
Ethical Business, Organizational and Digital Research

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

5. Ethical Business, Organizational and Digital Research

Introduction and Context

Research conducted in businesses, workplaces, organizations, and digital environments differs from research carried out in relatively controlled academic settings. The researcher may need permission from senior managers, human-resource departments, platform administrators, community moderators, or technology providers. Participants may be employees whose careers depend on the organization, customers whose data are collected through digital services, or online users who do not expect their public contributions to become research evidence. These conditions create ethical problems that cannot be resolved simply by obtaining a signed consent form.

Organizational and digital research is also characterized by unequal power, commercially sensitive information, surveillance capabilities, complex data ownership, and competing stakeholder interests. A sponsor may want favorable findings; a manager may attempt to control access to employees; a platform may restrict disclosure of data; and a researcher may face pressure to produce operationally useful results quickly. Ethical research therefore requires attention to access, voluntariness, privacy, confidentiality, data governance, interpretation, and the distribution of benefits and harms.

This chapter examines ethical decision-making in field experiments, case studies, workplace observation, organizational research, online communities, social-media research, and platform-based data analysis. It treats ethics not as an administrative obstacle but as a condition of credible knowledge. When participants fear retaliation, when online context is misunderstood, or when sponsors suppress inconvenient results, methodological validity is weakened as well as ethical integrity.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Explain the ethical significance of gatekeeper access and organizational power.

2. Distinguish overt, covert, and participatory observation in workplace and digital settings.

3. Evaluate privacy, consent, confidentiality, and contextual integrity in online research.

4. Identify stakeholder harms and sponsor influence in field experiments and case studies.

5. Apply a structured framework for ethically designing organizational and digital research.

6. Assess the implications of platform data, surveillance technologies, analytics, and artificial intelligence.

7. Recommend governance and risk-mitigation practices for doctoral research and professional inquiry.

The Ethical Terrain of Organizational and Digital Inquiry

Gatekeepers and the problem of access

A gatekeeper is a person or institution that controls access to a research site, population, dataset, or community. Examples include a chief executive authorizing a case study, a human-resources director approving employee interviews, a hospital administrator granting access to records, and a moderator allowing research in an online community. Gatekeeper permission is often necessary, but it is not equivalent to participant consent.

The distinction is crucial. A manager may authorize a study because it serves organizational interests, while employees may feel unable to refuse participation. Even when participation is formally voluntary, employees may infer that cooperation is expected. Ethical access therefore requires two separate permissions: institutional authorization to enter the setting and individual consent to participate. Researchers should communicate clearly that refusal will not affect employment, promotion, performance evaluation, access to services, or membership in a community.

Gatekeepers can also shape the sample. They may select only high-performing employees, exclude critics, or require that interview questions be approved in advance. Such controls create both ethical and validity risks. The researcher should negotiate access conditions before data collection, including the right to recruit independently, protect identities, report unfavorable findings, and withdraw if agreed protections are not respected.

Workplace surveillance and informational power

Digital workplaces generate extensive records: access logs, email metadata, keystrokes, location data, productivity scores, biometric information, video recordings, and communications on collaboration platforms. These data may be attractive to researchers because they permit unobtrusive and large-scale analysis. However, the fact that data are technically available does not establish that their research use is ethically permissible.

Workplace surveillance raises questions of proportionality, purpose limitation, transparency, and secondary use. Employees may understand that a system records attendance but not that the same information will be used to infer stress, loyalty, political attitudes, or future performance. Data that appear non-sensitive in isolation may become sensitive when combined. For example, time stamps, location records, and messaging patterns may reveal health appointments, union activity, religious observance, or family responsibilities.

A defensible study should specify what is collected, why it is necessary, who can access it, how long it will be retained, and whether individual-level reporting is justified. Aggregation, pseudonymization, restricted access, and deletion schedules reduce risk, but they do not guarantee anonymity. Small teams and distinctive behavioral patterns can make individuals identifiable even after names are removed.

Overt, covert, and participatory observation

Observation is often valuable in organizational research because formal interviews may not capture informal routines, workarounds, conflict, or tacit knowledge. In overt observation, participants know that research is taking place. In covert observation, the researcher conceals the research purpose or identity. Participatory observation combines observation with involvement in the setting.

Overt observation supports informed consent but may produce reactivity: people change their behavior because they know they are being observed. Covert observation may reduce reactivity but normally compromises autonomy and can expose people to unanticipated risks. It should therefore be exceptional, justified by a strong research question, limited in scope, reviewed by an appropriate ethics committee, and followed by debriefing where feasible. Covert methods are especially problematic when the setting involves vulnerable workers, sensitive conduct, or risks of disciplinary action.

Researchers must distinguish between observing an organizational process and recording identifiable personal behavior. Field notes should avoid unnecessary names and details. A researcher should not treat everything seen in a workplace as ethically available merely because it was visible. Confidential conversations, private screens, and informal disclosures retain privacy interests.

Online Communities, Social Media, and Platform Data

Public does not mean ethically unrestricted

Online research complicates the boundary between public and private. A post may be visible to anyone on the internet, yet its author may reasonably expect it to remain within a particular community or conversational context. Ethical analysis should consider the user’s expectations, the sensitivity of the content, the vulnerability of the population, the size and accessibility of the community, and the potential consequences of quotation.

Direct quotations can be searchable and may identify users even when names are removed. Researchers should consider paraphrasing, altering inconsequential details, aggregating results, or obtaining permission before using distinctive material. Screenshots require particular caution because usernames, timestamps, profile images, and links may expose identities.

Online consent is not a single technique. In a large public forum, individual consent from every poster may be impracticable, but transparency through a research notice, moderator consultation, opt-out process, and careful anonymization may be appropriate. In a small support group or closed professional community, direct consent is more likely to be necessary. The ethical response depends on context rather than a simple public/private classification.

Community norms and the ethics of participation

Online communities have governance structures, explicit rules, and informal expectations. A researcher who joins a group under a misleading identity, scrapes posts contrary to community rules, or publishes sensitive discussions without consultation may cause harm even if the material is technically accessible. Researchers should identify themselves when the research relationship begins, respect moderator decisions, and avoid disrupting conversations.

Some communities include children, patients, survivors of abuse, political dissidents, or workers discussing unsafe conditions. The risks of identification, retaliation, stigma, or emotional distress may be substantial. Ethical review should address not only the direct participant but also bystanders and other community members whose information appears in the data.

Platform data and terms of access

Platform data may be obtained through application programming interfaces, data-sharing agreements, web scraping, commercial vendors, or internal organizational systems. Each route creates different obligations. Terms of service may prohibit scraping; an API may provide only a partial or algorithmically selected view; vendor data may contain uncertain provenance; and platform changes may affect reproducibility.

Researchers should document the source, collection date, selection rules, missingness, transformations, and access restrictions. They should avoid assuming that platform metrics represent human attitudes directly. Likes, shares, views, and follower counts are behavioral traces shaped by interface design, recommendation algorithms, bots, commercial incentives, and unequal visibility. Ethical analysis and methodological validity therefore overlap.

Field Experiments and Stakeholder Harm

Field experiments manipulate conditions in real organizational or market settings. Examples include changing the wording of customer communications, testing alternative scheduling systems, varying prices, or introducing a management intervention. Such studies can produce valuable evidence, but they may affect people who never explicitly agreed to participate.

The researcher should identify all affected stakeholders, not only the individuals who provide data. These may include employees, customers, non-participating colleagues, suppliers, competitors, and communities. Potential harms include loss of income, unequal access to services, reputational damage, stress, unfair evaluation, privacy invasion, and exposure to legal or safety risks.

A proportionate design asks whether the intervention is necessary, whether less harmful alternatives exist, whether risks are distributed fairly, and whether stopping rules are defined. Randomization does not make an intervention ethical. Nor does organizational approval eliminate the need to consider individual welfare. Where feasible, researchers should use minimal-risk manipulations, pilot tests, independent monitoring, and post-study communication.

Deception requires additional scrutiny. It may be justified only when the research question cannot be answered without it, the deception does not expose participants to more than minimal risk, and participants are debriefed when doing so will not create further harm. A manager should not be deceived about a study if the deception could compromise safety, legal compliance, or trust in the organization.

Case Studies and Sponsor Influence

A case study often depends on close cooperation with an organization. Sponsors may provide access, documents, funding, introductions, and opportunities for longitudinal observation. These benefits can create dependency. The organization may request anonymity, which can protect it, but anonymity can also prevent readers from assessing the evidence. Alternatively, a sponsor may insist on being named for reputational benefit while attempting to control interpretation.

Before collecting data, the researcher should establish a written agreement covering access, confidentiality, ownership or custody of data, publication rights, review of manuscripts, use of quotations, and procedures for resolving disagreements. Sponsor review should normally be limited to identifying factual inaccuracies, confidential information, or security risks—not to altering findings because they are unfavorable.

A case study may also harm an organization unintentionally. A detailed narrative can reveal strategic weaknesses, labor disputes, regulatory failures, or identifiable employees. Composite cases, altered nonessential details, tiered access to appendices, and delayed publication may sometimes reduce risk. Such methods must not distort the evidence so extensively that the account becomes misleading.

A Framework for Ethical Organizational and Digital Research

A useful decision process consists of seven connected questions.

First, what is the social and scholarly purpose? The study should address a meaningful question rather than collect data simply because technology makes collection easy.

Second, who controls access and who bears the risks? Map gatekeepers, participants, non-participants, bystanders, data subjects, communities, and downstream users.

Third, what is the reasonable expectation of privacy? Examine setting, relationship, audience, sensitivity, visibility, and the possibility of re-identification.

Fourth, is consent meaningful? Assess whether information is understandable, participation is voluntary, refusal is safe, and withdrawal is practicable. Where consent is waived, document the justification and safeguards.

Fifth, is the data practice proportionate? Collect the minimum information necessary, restrict secondary uses, and establish retention and deletion rules.

Sixth, how will power and conflicts be governed? Disclose sponsors, separate managerial authority from recruitment where possible, and protect the researcher’s right to report evidence honestly.

Seventh, what happens after publication or implementation? Consider feedback, correction, participant complaints, data breaches, adverse findings, and whether results could be used for surveillance or discrimination.

This framework should be applied iteratively. Ethical issues often emerge after access has been negotiated or when unexpected data appear. A protocol should therefore include procedures for amendment, incident reporting, and suspension of data collection.

Illustrative Case: The Productivity Dashboard Study

Background

A fictional logistics company, Northstar Distribution, introduced a dashboard that recorded warehouse employees’ scanning speed, movement between zones, break duration, and error rates. The company invited a doctoral researcher to evaluate whether the dashboard improved productivity and employee well-being. Senior management offered access to system logs and requested that the study identify “resistant” employees.

Situation and ethical problem

The research team could analyze historical records without contacting every worker. However, employees had not been told that the data would be used for research, and the dashboard influenced performance evaluations. Workers feared that refusing interviews would affect their contracts. A small number of employees also had unusual movement patterns because of medical conditions.

Analysis

The data were not ethically neutral simply because the company owned the system. The proposed classification of “resistant” employees risked converting a research project into a disciplinary tool. Individual-level analysis could expose health information, and the power imbalance weakened the voluntariness of interviews. The research question also required clarification: evaluating productivity did not require identifying individual dissenters.

Approach

The researcher renegotiated the project. The company agreed that data would be analyzed in aggregate, that individual performance records would not be shared with managers, and that participation in interviews would be recruited by an independent contact. Employees received a plain-language notice explaining the study, the categories of data involved, risks, and their right to decline. Medical and demographic information was excluded unless separately justified. A data-management plan specified pseudonymization, restricted access, a deletion date, and procedures for reporting a breach.

The research agreement gave the team authority to publish results, including unfavorable findings. The company could check factual descriptions of its systems but could not veto interpretation. An employee advisory group reviewed the interview protocol and helped identify harms that researchers had initially overlooked.

Outcome

The study found modest productivity changes but also evidence that dashboard targets encouraged rushed scanning and under-reporting of equipment problems. Because findings were reported at group level, no employee was labeled as resistant. The company revised the dashboard and separated developmental feedback from disciplinary decisions.

Learning points

The case illustrates that gatekeeper access is not participant consent, ownership is not unlimited ethical authority, and data minimization can improve both privacy and analytical focus. It also shows why employee participation, independent recruitment, sponsor agreements, and stakeholder consultation should be designed before data collection begins.

Challenges, Limitations, and Common Errors

A frequent error is treating a signed form as the complete ethical solution. Consent may be formally obtained while employees remain under implicit pressure. Another error is promising anonymity when small samples, quotations, or distinctive roles make identification possible. Researchers also commonly underestimate the risks of data linkage, assume that public posts are free of privacy expectations, or rely on automated sentiment and productivity scores as if they were direct measures of human states.

Other challenges include changing platform interfaces, inaccessible proprietary algorithms, cross-border data transfers, conflicting legal requirements, and the inability to contact all affected data subjects. Ethical review may itself be limited when committees lack expertise in platform governance or workplace technology. Doctoral researchers should seek specialist advice rather than treating institutional approval as proof that every later decision is acceptable.

Governance, Technology, and Emerging Developments

Effective governance combines technical, organizational, and professional controls. Technical measures include encryption, access logs, differential access, pseudonymization, secure analysis environments, and privacy-preserving aggregation. Organizational measures include role separation, data-protection impact assessments, staff training, incident response, and independent oversight. Professional measures include reflexive field notes, conflict-of-interest disclosure, audit trails, and transparent reporting of exclusions and limitations.

Artificial intelligence increases both the scale and opacity of organizational research. Predictive models may infer attrition risk, emotional state, fraud likelihood, or employee engagement from indirect signals. Such inferences can reproduce historical discrimination, encourage intrusive monitoring, and create false confidence in probabilistic outputs. Researchers should distinguish observed data from inferred attributes, test for disparate impacts, document model limitations, and avoid consequential decisions based solely on opaque scores.

Emerging practice is moving toward privacy-enhancing computation, secure data enclaves, responsible data-sharing agreements, participatory research, and algorithmic impact assessments. These developments are useful but not automatically ethical. A technically secure system can still support unfair surveillance, and an accurate model can still be used for an illegitimate purpose. Ethical judgment remains necessary because the central question is not only what can be measured, but what should be measured and who should be exposed to the consequences.

Best Practices for Researchers and Organizations

Researchers should:

  • separate gatekeeper authorization from individual consent;
  • map affected stakeholders before collecting data;
  • use the least intrusive method capable of answering the question;
  • state privacy, confidentiality, and publication limits honestly;
  • minimize collection, access, retention, and quotation of identifiable data;
  • consult communities and employee representatives where appropriate;
  • predefine sponsor rights and protect intellectual independence;
  • document data provenance, transformations, exclusions, and analytic decisions;
  • provide secure channels for complaints and correction;
  • reassess ethics when the research design, platform, or organizational context changes.

Organizations should not use research participation as a hidden mechanism for employee surveillance or discipline. They should provide realistic opportunities to refuse, prevent managers from seeing individual research responses, and distinguish operational monitoring from independent inquiry.

Chapter Summary

Ethical business, organizational, and digital research must address more than formal approval and consent. Gatekeepers control access but cannot consent on behalf of employees or online users. Workplace surveillance and platform data require purpose limitation, proportionality, transparency, and protection against re-identification. Covert observation and deception demand exceptional justification because they compromise autonomy. Public online content may still carry contextual privacy expectations, and quotations can identify their authors.

Field experiments should assess harms to all affected stakeholders, while case studies require agreements protecting confidentiality and the researcher’s independence from sponsors. A practical framework examines purpose, stakeholders, privacy expectations, meaningful consent, proportionality, power, conflicts, and post-publication consequences. Digital tools, analytics, and AI can strengthen research but also intensify surveillance, inference, bias, and opacity. Ethical governance is therefore an ongoing process linking research validity, participant protection, responsible technology, and professional integrity.

Key Terms

Gatekeeper: A person or institution controlling access to a research setting, population, community, or dataset.

Institutional authorization: Permission granted by an organization to conduct research within its domain.

Meaningful consent: Voluntary, informed agreement made without coercion or undue influence.

Workplace surveillance: Systematic monitoring or recording of employee activities, communications, locations, or performance.

Purpose limitation: Restricting data use to specified, legitimate, and communicated purposes.

Data minimization: Collecting only the information necessary for the research purpose.

Pseudonymization: Replacing direct identifiers with codes while retaining a controlled possibility of linkage.

Re-identification: The process of associating supposedly de-identified data with a specific person.

Overt observation: Observation in which participants know that research is being conducted.

Covert observation: Observation in which the research purpose or researcher identity is concealed.

Participatory observation: Research involving observation while the researcher participates in the setting.

Contextual privacy: Privacy expectations shaped by the social setting, audience, and intended flow of information.

Platform data: Information generated, stored, or provided through a digital platform.

Stakeholder harm: Injury or disadvantage experienced by participants, non-participants, communities, or other affected parties.

Sponsor influence: The effect of a funder or organizational partner on research access, analysis, reporting, or publication.

Field experiment: A study that manipulates conditions in a real-world organizational, market, or social setting.

Debriefing: Explaining the research purpose and procedures to participants after participation, particularly after deception.

Data provenance: Documentation of where data originated and how they were collected and transformed.

Algorithmic impact assessment: A structured evaluation of the risks, effects, bias, and governance of an algorithmic system.

Privacy-enhancing technology: A technical method designed to reduce unnecessary exposure of personal information.

Review Questions

Short Answer Questions

1. Why is gatekeeper permission not equivalent to individual participant consent?

2. What is meant by contextual privacy in online research?

3. Identify two ethical risks associated with workplace surveillance data.

4. Why can direct quotations from public social-media posts create identification risks?

5. What is the purpose of a sponsor agreement in a case study?

Long Answer Questions

1. Compare overt and covert observation in organizational research, including their ethical and methodological trade-offs.

2. Explain how researchers should evaluate the ethical use of platform data obtained through APIs or web scraping.

3. Discuss stakeholder harm in field experiments and propose safeguards for reducing it.

4. Analyze the relationship between sponsor influence, publication independence, and research credibility.

5. Explain the seven-question framework for ethical organizational and digital research.

Analytical / Application Questions

1. A company asks a doctoral researcher to use employee messaging data to identify low-engagement workers. Design an ethically defensible alternative study.

2. A researcher wants to quote posts from a small online support group without contacting authors because the group is technically public. Evaluate the proposal and recommend safeguards.

3. An AI system predicts employee attrition from location and communication patterns. Advise the organization on whether and how the system could be studied ethically.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes gatekeeper authorization from participant consent?

A. Gatekeeper authorization automatically permits all uses of organizational data.

B. Gatekeeper authorization permits access, while participants must independently agree to take part.

C. Participant consent is unnecessary when the organization owns the data.

D. Gatekeeper authorization is required only for online research.

Correct Answer: B. Gatekeeper authorization permits access, while participants must independently agree to take part.

Question 2

An employee’s location and messaging records reveal possible medical appointments. Which principle is most directly relevant?

A. Purpose limitation and protection against inference of sensitive information

B. Maximizing data retention for reproducibility

C. Public availability of workplace data

D. Eliminating all organizational oversight

Correct Answer: A. Purpose limitation and protection against inference of sensitive information

Question 3

Why may a quotation from a public social-media post still create ethical risk?

A. Public posts cannot be analyzed scientifically.

B. All public posts are legally confidential.

C. Searchable wording may identify the author despite removal of the username.

D. Online communities never permit research.

Correct Answer: C. Searchable wording may identify the author despite removal of the username.

Question 4

Covert observation is most ethically defensible when it is used only after the researcher has established that it is

A. cheaper than informed research

B. requested by a sponsor

C. likely to produce favorable findings

D. necessary, low risk, carefully limited, and appropriately reviewed

Correct Answer: D. necessary, low risk, carefully limited, and appropriately reviewed

Question 5

Which sponsor demand most threatens research independence?

A. Checking whether the organization’s name and dates are factually accurate

B. Requesting removal of findings solely because they are unfavorable

C. Providing access to relevant records

D. Reviewing confidential security information

Correct Answer: B. Requesting removal of findings solely because they are unfavorable

Question 6

A field experiment changes customer communication for one randomly selected group. What should the researcher do first ethically?

A. Assume randomization eliminates ethical concerns.

B. Identify all affected stakeholders and assess possible harms.

C. Publish individual customer responses.

D. Allow the sponsor to define harm after the study.

Correct Answer: B. Identify all affected stakeholders and assess possible harms.

Question 7

Which practice best reflects data minimization?

A. Collecting every available variable in case it becomes useful

B. Retaining raw identifiable data indefinitely

C. Collecting only information necessary for the stated research question

D. Combining datasets before defining the purpose

Correct Answer: C. Collecting only information necessary for the stated research question

Question 8

In the illustrative dashboard case, why was aggregate analysis preferable to labeling individual employees?

A. It prevented the study from measuring anything.

B. It reduced privacy and disciplinary risks while addressing the research question.

C. It guaranteed that the findings would favor management.

D. It eliminated the need for employee communication.

Correct Answer: B. It reduced privacy and disciplinary risks while addressing the research question.

Question 9

What is a major ethical concern with AI-based employee attrition predictions?

A. They always require handwritten records.

B. They cannot process organizational data.

C. They may infer sensitive characteristics and reproduce discriminatory patterns.

D. They make data minimization unnecessary.

Correct Answer: C. They may infer sensitive characteristics and reproduce discriminatory patterns.

Question 10

Which action best supports ethical governance when a platform changes its data-access rules during a study?

A. Continue without documenting the change.

B. Hide the change to preserve apparent consistency.

C. Reassess the protocol, document the change, and amend safeguards if necessary.

D. Publish the platform’s private credentials.

Correct Answer: C. Reassess the protocol, document the change, and amend safeguards if necessary.

Research Ethics & Computer Applications
Chapter 5 of 15

Research Ethics & Computer Applications

Chapter 6
Misconduct, Authorship and Responsible Publication

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

6. Misconduct, Authorship and Responsible Publication

Introduction and Context

Research is a public trust. Universities, firms, governments, journals, and communities make decisions on the assumption that reported findings represent an honest and reasonably careful account of how evidence was obtained and interpreted. When that assumption is violated, the harm extends beyond a single article. Misconduct can distort theory, misdirect managerial decisions, waste research funds, damage participants, undermine institutional credibility, and weaken confidence in scholarship itself.

Research integrity is therefore broader than avoiding fraud. It includes accurate record keeping, transparent analysis, fair attribution, responsible peer review, appropriate citation, disclosure of conflicts, and correction of the scholarly record. In business research, these responsibilities are especially important because findings may influence investment, employment, consumer welfare, public policy, organizational strategy, and professional practice.

This chapter examines serious research misconduct, questionable research practices, authorship and contributorship, publication ethics, peer review, paper mills, and mechanisms for correction and retraction. The central argument is that responsible publication is not merely a final editorial stage. It is a continuous process beginning with research design and continuing through data management, analysis, manuscript preparation, dissemination, and post-publication correction.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Distinguish fabrication, falsification, plagiarism, and questionable research practices.

2. Explain how selective reporting, p-hacking, HARKing, and inadequate data management can compromise knowledge.

3. Apply principled standards for authorship, contributorship, acknowledgements, and corresponding-author responsibility.

4. Evaluate ethical duties in citation, peer review, disclosure, and the use of artificial intelligence.

5. Recognize indicators of paper mills and assess the appropriate institutional or journal response.

6. Recommend suitable actions involving corrections, expressions of concern, and retractions.

7. Design organizational controls that promote a culture of research integrity.

The Integrity Problem: From Deliberate Fraud to Distorted Evidence

Research misconduct

A widely used core definition identifies three forms of serious misconduct: fabrication, falsification, and plagiarism. Fabrication is making up data, observations, participants, quotations, experiments, or results and presenting them as real. Falsification is manipulating research materials, equipment, processes, images, data, or reporting so that the research record no longer accurately represents what occurred. Plagiarism is presenting another person’s words, ideas, structure, data, or creative work as one’s own without adequate acknowledgement.

These categories are analytically distinct but may overlap. A researcher who invents observations and then alters statistical tables commits both fabrication and falsification. Copying a colleague’s unpublished dataset without permission may involve plagiarism, breach of confidentiality, and unauthorized use of research property. Misconduct normally requires more than an innocent typographical error. Institutional procedures commonly distinguish intentional or knowingly reckless conduct from honest error, although negligence may still require correction or disciplinary action.

Questionable research practices

Between acceptable practice and formal misconduct lies a broad area of questionable research practices (QRPs). Examples include stopping data collection when a desired significance level is reached, testing many outcomes but reporting only significant ones, excluding inconvenient observations without a pre-specified rule, changing hypotheses after seeing results without disclosure, using inappropriate statistical models, and failing to preserve research records.

A QRP may not meet the legal or institutional definition of misconduct, yet it can produce a systematically misleading literature. Its ethical importance depends on intent, magnitude, transparency, and consequences. A post hoc hypothesis can be valuable if identified as exploratory; it becomes misleading when presented as though it had been predicted in advance. Similarly, removing an outlier may be defensible when based on a documented measurement error, but not when the sole reason is that the observation weakens the preferred conclusion.

Selective reporting and researcher degrees of freedom

Selective reporting occurs when researchers choose which analyses, outcomes, samples, or time periods to disclose. Publication bias arises when studies with positive, novel, or statistically significant results are more likely to be submitted, accepted, or publicized than studies with null findings. The result is an exaggerated impression of the strength or consistency of evidence.

Researchers often possess legitimate analytical choices: variable transformations, subgroup analyses, model specifications, missing-data treatments, and stopping rules. These choices are sometimes called researcher degrees of freedom. They become problematic when numerous alternatives are explored but only the successful route is reported. Preregistration, registered reports, analysis plans, robustness checks, and complete disclosure of deviations help distinguish confirmatory from exploratory work.

P-hacking refers to practices that exploit analytical flexibility to obtain a desired p-value. HARKing—hypothesizing after the results are known—presents an observation discovered during analysis as a prediction made beforehand. Neither exploratory analysis nor unexpected findings are unethical. The ethical failure lies in concealing the distinction between discovery and confirmation.

A Framework for Evaluating Integrity

A useful evaluation can examine five questions:

1. What was represented? Was the claim about data, method, authorship, originality, or interpretation?

2. What actually occurred? Can the account be checked against raw data, protocols, logs, drafts, or correspondence?

3. Was the deviation intentional, reckless, negligent, or accidental?

4. Could a reasonable reader be misled? Consider both the immediate statement and its likely use.

5. What remedy is proportionate? Options range from clarification and correction to institutional investigation, retraction, or sanctions.

This framework prevents two common errors. The first is treating every imperfection as fraud. The second is treating technically sophisticated manipulation as harmless because no single sentence is demonstrably false. Integrity is assessed in relation to the reliability of the research record as a whole.

Research teams should maintain an auditable chain from research question to conclusion. This includes version-controlled protocols, dated data dictionaries, decision logs, syntax or code, records of exclusions, consent documentation, secure storage, and a clear distinction between raw, processed, and analyzed data. Reproducibility does not mean every study must yield identical results, but it does require sufficient transparency for qualified researchers to understand and, where possible, reproduce the analytical pathway.

Authorship as Credit and Accountability

Authorship has two dimensions. It gives credit for intellectual work and assigns responsibility for the integrity of the publication. Authorship should therefore not be treated as a reward for seniority, funding, supervision, friendship, or administrative position.

Although exact policies differ across disciplines and journals, defensible authorship normally requires substantial contribution to the conception or design, acquisition or analysis of data, or interpretation of results; participation in drafting the work or critically revising it; approval of the final version; and willingness to be accountable for the work. Someone who makes a substantial intellectual contribution but is excluded may be a victim of authorship abuse. Someone listed merely because of status may be a guest or honorary author.

Ghost authorship occurs when a person who made a substantial contribution is not identified. It can conceal commercial influence, professional writing assistance, or substantive analytical work. Gift authorship gives credit to a person who did not meet authorship criteria, often to secure favor or signal prestige. Coercive authorship arises when a person with power demands inclusion or control over author order without a qualifying contribution.

Contribution statements improve transparency by identifying roles such as conceptualization, methodology, software, data curation, formal analysis, investigation, writing, visualization, supervision, and project administration. A contribution taxonomy does not replace judgment: technical assistance may justify acknowledgement, authorship, or neither depending on intellectual significance and involvement in the manuscript.

Authorship should be discussed at the beginning of a project and revisited when contributions change. A written agreement should address expected contributions, author order, data access, decision rights, and dispute procedures. The corresponding author should coordinate submission, communicate with the journal, confirm authorship approval, preserve relevant documentation, and ensure that concerns are not concealed from coauthors.

Publication Responsibilities

Citation and originality

Citation is not a decorative practice. It enables readers to trace claims, evaluate evidence, locate methods, and recognize intellectual debts. Sources should be cited for ideas, theories, measures, data, distinctive arguments, and borrowed language. Direct quotations require quotation marks and precise location information where appropriate. Paraphrasing requires genuine restatement and citation; changing a few words is not sufficient.

Self-citation is legitimate when prior work is relevant, but excessive self-citation can inflate apparent influence or create the impression of novelty. Citation manipulation includes coercive citation, reciprocal citation arrangements, and adding irrelevant references to satisfy editorial or reviewer demands. Authors should cite primary sources where feasible, represent disagreement fairly, and avoid citing work they have not examined.

Duplicate publication and redundant publication occur when substantially overlapping material is published more than once without transparent disclosure. Salami slicing divides one study into several papers whose separate publication adds little scholarly value. Secondary publication can be acceptable when justified, authorized, and clearly identified, such as an appropriately translated or audience-specific version.

Peer review

Peer review is a process of informed evaluation, not an opportunity to appropriate ideas, delay competitors, promote friends, or impose personal theoretical preferences. Reviewers should accept assignments only when they have suitable expertise and sufficient time. They should disclose conflicts of interest, maintain confidentiality, provide evidence-based criticism, and distinguish fatal methodological problems from amendable weaknesses.

Reviewers must not use unpublished information for personal advantage or share manuscripts without permission. Editors should select reviewers fairly, protect confidentiality, manage conflicts, and ensure that decisions are not based solely on novelty, institutional prestige, or commercial interest. Confidentiality may be limited when journals use transparent or open review, but the applicable policy must be followed.

Disclosure and conflicts of interest

A conflict of interest exists when personal, professional, financial, institutional, or ideological interests could reasonably be perceived as influencing judgment. A conflict is not automatically wrongdoing; concealment is often the more serious problem. Disclosures should cover funding, employment, consultancy, equity, patents, relationships, editorial roles, and other interests relevant to the research.

Disclosure does not cure a biased method or excuse misconduct. It allows editors, reviewers, readers, and decision-makers to evaluate the potential influence. Authors should also disclose the role of sponsors in study design, data access, analysis, writing, and publication decisions.

Corrections, expressions of concern, and retractions

The scholarly record should be corrected when errors are discovered. A minor typographical error may require an erratum or corrigendum. A substantive but localized problem may require a correction that clearly identifies the affected text, data, or interpretation. An expression of concern alerts readers to a potentially serious issue while an investigation remains unresolved.

Retraction is appropriate when findings are unreliable because of misconduct, major error, pervasive analytical problems, ethical violations, or substantial duplication. Retraction is a mechanism for protecting the record, not necessarily a punishment. A retraction notice should explain the reason and preserve the original article’s identity and history. Authors should cooperate with appropriate corrections even when the error does not threaten the central conclusion.

Paper Mills and the Industrialization of False Scholarship

Paper mills are organized operations that produce or sell manuscripts, authorship positions, fabricated datasets, peer-review identities, or publication services designed to simulate legitimate scholarship. They exploit academic incentives based on publication counts, journal rankings, promotion, and research metrics.

Possible warning signs include implausible or generic titles, text that does not match the stated research question, repeated phrases across unrelated papers, manipulated or nonsensical figures, unavailable data, suspicious email addresses, unusual authorship patterns, irrelevant citations, peer reviewers with unverifiable identities, and rapid publication accompanied by pressure to add authors. A single indicator is not proof. Investigation must be careful because language differences, legitimate collaboration, and poor reporting can produce superficial similarities.

Responses should combine technical screening and human judgment. Journals may verify reviewer identities, examine image and text similarity, request raw data or ethical approval, and scrutinize author contributions. Institutions should investigate patterns across submissions rather than treating every questionable article in isolation. Retractions alone do not address the incentive system that made paper-mill services attractive. Doctoral programs and business schools should value methodological rigor, open materials, substantive contribution, and responsible negative findings rather than publication volume alone.

Digital Tools, Data, and Artificial Intelligence

Computer applications can strengthen integrity when used for version control, reproducible scripts, audit trails, secure data management, reference checking, plagiarism screening, image analysis, and preregistration. They can also create new risks. Spreadsheet formulas may silently change; automated data cleaning may remove cases without a record; generative AI may invent citations, reproduce copyrighted language, or obscure who performed the intellectual work.

Researchers remain responsible for AI-assisted outputs. They should verify every citation, protect confidential or personal data from unauthorized systems, document significant uses of AI, and follow journal and institutional policies. AI tools should not be listed as authors because they cannot accept accountability, approve a final manuscript, disclose conflicts, or respond to allegations. Human authors must review generated text and preserve the distinction between assistance with language and substantive generation of analysis or evidence.

Data analytics can detect anomalous patterns, duplicated images, impossible values, or suspiciously similar manuscripts, but automated detection is probabilistic. False positives may unfairly damage reputations, while sophisticated manipulation may evade detection. Digital tools are aids to governance, not substitutes for expert inquiry and due process.

An Illustrative Case: The Marketing Analytics Consortium

Background

The fictional Marketing Analytics Consortium was a multi-university project studying whether personalized mobile promotions increased customer retention. The project involved a doctoral researcher, two faculty investigators, a corporate sponsor, and a data analyst.

Situation

The doctoral researcher discovered that the treatment effect was statistically significant only under one of several plausible model specifications. The team had not preregistered its analysis. The sponsor urged the researchers to emphasize the significant result in a journal submission. A senior faculty member requested first authorship despite limited involvement, while the analyst—who designed the data pipeline and conducted most analyses—was offered acknowledgement only. During revision, a reviewer suggested adding several citations to the reviewer’s own work.

Analysis

Several risks are present. Reporting only the successful model would be selective reporting unless the alternative specifications and rationale were disclosed. Presenting the model as the sole planned analysis would become misleading HARKing or analytical concealment. The sponsor’s role and any restrictions on publication must be disclosed. Authorship should reflect intellectual contribution, not hierarchy. The analyst’s role may qualify for authorship if it includes substantial analysis and manuscript participation. The reviewer’s citation request should be assessed for relevance rather than accepted automatically.

Appropriate approach

The team should reconstruct its analytical decisions, report the range of reasonable specifications, distinguish confirmatory from exploratory results, and explain the effect of model choice. It should document the sponsor’s involvement and confirm that researchers retain control over publication. The team should negotiate authorship using contribution statements and invite the analyst to participate in drafting and revision. The corresponding author should obtain approval from all authors. Irrelevant reviewer citations should be declined politely, while relevant sources should be considered on their merits.

Outcome

The revised article reports a smaller and less certain effect than the original submission, but its conclusions are more credible. The journal accepts a transparent contribution statement and disclosure. The team also deposits an analysis script and a de-identified codebook where ethically permissible. The senior faculty member remains a coauthor only after making a qualifying intellectual contribution.

Learning points

The case illustrates that responsible publication involves judgment before submission, not merely compliance with editorial formatting. Transparency about analytical flexibility may reduce rhetorical impact but increases evidential value. Authorship is linked to work and accountability. Sponsors and reviewers can influence publication without being allowed to control the research record.

Institutional Governance and Common Failures

Integrity depends on systems as well as individual character. Institutions should provide clear policies, responsible-conduct training, mentoring, secure research infrastructure, confidential reporting channels, impartial investigations, protection against retaliation, and proportionate sanctions. They should distinguish allegations from findings and protect the rights of complainants, respondents, participants, and coauthors.

Common failures include leaving authorship discussions until submission, storing the only dataset on a personal device, treating statistical significance as proof of importance, assuming that a supervisor is responsible for every detail without monitoring, using plagiarism software as the sole integrity control, and rewarding publication quantity without examining research quality. Another failure is silence after discovering an error. Delay can allow a flawed result to be cited, implemented, or incorporated into further research.

Responsible organizations create incentives for openness. They recognize data and code stewardship, careful replication, correction of mistakes, mentoring, and high-quality null results. They also ensure that whistleblowing is not confused with disloyalty and that allegations are handled through evidence-based procedures rather than informal reputation contests.

Current Developments and Best Practices

Open science has increased attention to preregistration, registered reports, open data, open materials, transparent peer review, data and code availability statements, and post-publication commentary. These practices are not universally suitable: confidentiality, commercial agreements, privacy, security, and participant consent may restrict openness. The appropriate standard is justified transparency, not indiscriminate disclosure.

A practical responsible-publication workflow is as follows:

  • Agree on authorship and contributions at project initiation and update the agreement.
  • Register hypotheses and analysis plans when appropriate, while labeling later analyses as exploratory.
  • Preserve raw data, metadata, code, protocols, and decision logs securely.
  • Report all relevant outcomes, exclusions, model choices, and material deviations.
  • Check originality, citations, permissions, ethics approvals, and conflicts before submission.
  • Obtain final approval from every author and disclose sponsor involvement.
  • Review proofs carefully and correct the record promptly after publication.
  • Respond to concerns through designated institutional or journal channels, preserving confidentiality and due process.

Chapter Summary

Research integrity includes more than avoiding fabrication, falsification, and plagiarism. Questionable research practices such as p-hacking, HARKing, selective reporting, and inadequate record keeping can also distort evidence. Authorship should provide both fair credit and accountability, while contribution statements clarify individual roles. Responsible publication requires accurate citation, ethical peer review, conflict disclosure, and transparent handling of corrections and retractions. Paper mills exploit publication incentives and require coordinated technical, editorial, and institutional responses. Digital tools and AI can improve reproducibility but introduce risks involving privacy, automation, hallucinated sources, and accountability. The strongest integrity systems combine individual judgment, transparent workflows, institutional governance, and incentives that value reliable knowledge over publication volume.

Key Terms

Fabrication: Making up data, observations, participants, or results and presenting them as genuine.

Falsification: Manipulating research materials, processes, data, or reporting so the record is misleading.

Plagiarism: Using another person’s words, ideas, data, or work without appropriate attribution.

Questionable research practice: A practice that may not meet formal misconduct criteria but weakens research reliability or transparency.

Selective reporting: Reporting only selected outcomes, analyses, or observations, often those supporting a preferred conclusion.

P-hacking: Exploiting analytical flexibility to obtain a desired level of statistical significance.

HARKing: Presenting a post hoc explanation as though it had been hypothesized before results were known.

Publication bias: Systematic underrepresentation of studies with null, negative, or less novel findings.

Guest authorship: Listing a person as an author despite insufficient qualifying contribution.

Ghost authorship: Omitting a person who made a substantial contribution from the author list.

Corresponding author: The author responsible for communication with the journal and coordination of submission matters.

Contributorship: Transparent description of the roles performed by each researcher.

Conflict of interest: An interest that could reasonably be perceived as influencing professional judgment.

Peer review: Evaluation of scholarly work by suitably knowledgeable reviewers before or after publication.

Duplicate publication: Publishing substantially overlapping work without adequate disclosure.

Expression of concern: A journal notice warning readers about a potentially serious unresolved issue.

Retraction: Formal withdrawal of an unreliable publication from the scholarly record.

Paper mill: An organization that produces or sells fabricated or deceptive scholarly publications or authorship.

Preregistration: Publicly recording research questions, hypotheses, or analysis plans before examining outcome data.

Research integrity: Commitment to honesty, accuracy, transparency, accountability, and fairness in research.

Review Questions

Short Answer Questions

1. Distinguish fabrication from falsification and give one example of each.

2. Why can a questionable research practice be harmful even when it is not formal misconduct?

3. What are the two principal functions of authorship?

4. Why should conflicts of interest be disclosed rather than simply ignored?

5. What is the purpose of an expression of concern?

Long Answer Questions

1. Explain how selective reporting, p-hacking, and HARKing can distort the research literature. Discuss controls that reduce these risks.

2. Analyze the ethical responsibilities of authors, reviewers, editors, and institutions in maintaining a trustworthy publication record.

3. Discuss authorship abuse, including guest, ghost, and coercive authorship, and propose a fair contributorship process.

4. Explain how paper mills operate and evaluate the limitations of automated tools used to detect them.

5. Compare correction, expression of concern, and retraction, including the circumstances in which each response is appropriate.

Analytical / Application Questions

1. A researcher runs eight plausible models but reports only the one producing a significant result. How should the study be rewritten and what evidence should be preserved?

2. A corporate sponsor controls access to the dataset and asks to remove unfavorable findings. Identify the ethical and governance issues and recommend an institutional response.

3. A doctoral student discovers that a published article contains a substantial coding error that changes the conclusion. What should the student and corresponding author do, and which post-publication remedy is most likely appropriate?

22. Multiple Choice Questions with Answers

Question 1

Which situation most clearly constitutes fabrication?

A. Removing a documented data-entry error

B. Inventing survey responses that were never collected

C. Reporting an exploratory analysis as exploratory

D. Correcting a mislabeled table after publication

Correct Answer: B. Inventing survey responses that were never collected

Question 2

A researcher tests many models and reports only the model with p < .05 without disclosure. This is best described as:

A. P-hacking and selective reporting

B. Transparent replication

C. Guest authorship

D. A routine correction

Correct Answer: A. P-hacking and selective reporting

Question 3

Which action best distinguishes legitimate exploratory research from HARKing?

A. Deleting all unexpected findings

B. Presenting discovered patterns as preregistered predictions

C. Labeling post hoc explanations as exploratory

D. Reporting only statistically significant outcomes

Correct Answer: C. Labeling post hoc explanations as exploratory

Question 4

The primary ethical purpose of authorship is to:

A. Reward the most senior person in a research group

B. Provide credit and assign accountability

C. Increase the number of institutional publications

D. Guarantee acceptance by a journal

Correct Answer: B. Provide credit and assign accountability

Question 5

Which person is most likely to qualify for authorship?

A. A department chair who provided office space only

B. A colleague who reviewed grammar for ten minutes

C. An analyst who designed major analyses and helped revise the manuscript

D. A sponsor who requested favorable conclusions

Correct Answer: C. An analyst who designed major analyses and helped revise the manuscript

Question 6

A reviewer asks authors to cite several of the reviewer’s unrelated papers. The authors should primarily:

A. Add all citations to avoid rejection

B. Assess each citation for genuine relevance

C. Report the reviewer publicly before contacting the editor

D. Remove all citations to reviewers

Correct Answer: B. Assess each citation for genuine relevance

Question 7

Which statement about a conflict of interest is most accurate?

A. Its existence automatically proves misconduct

B. It should be concealed if the study is methodologically sound

C. Disclosure allows others to assess possible influence

D. It matters only when money is involved

Correct Answer: C. Disclosure allows others to assess possible influence

Question 8

A retraction is generally appropriate when:

A. A paper contains a minor typographical error

B. The central findings are unreliable because of major error or misconduct

C. A reviewer dislikes the theoretical framework

D. The authors receive fewer citations than expected

Correct Answer: B. The central findings are unreliable because of major error or misconduct

Question 9

Which is a possible indicator of a paper mill, but not proof by itself?

A. A clearly documented contribution statement

B. A verifiable institutional email address

C. Repeated generic text and unverifiable reviewer identities

D. A preregistered analysis plan

Correct Answer: C. Repeated generic text and unverifiable reviewer identities

Question 10

Why should AI systems not be listed as authors?

A. They cannot accept accountability, approve a manuscript, or disclose conflicts

B. They are unable to format references

C. They can never assist with language editing

D. They are always prohibited from research use

Correct Answer: A. They cannot accept accountability, approve a manuscript, or disclose conflicts

Research Ethics & Computer Applications
Chapter 6 of 15

Research Ethics & Computer Applications

Chapter 7
Research Data Ethics and Lifecycle Governance

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

7. Research Data Ethics and Lifecycle Governance

Introduction: Data as a Research Responsibility

Research data are more than files, observations, interview transcripts, survey responses, transaction records, images, or code outputs. They are representations of people, organizations, environments, and decisions. Their collection and use therefore create responsibilities that extend beyond methodological competence. A dataset may contain personal information, commercially sensitive knowledge, culturally significant materials, or evidence whose misuse could produce financial, social, reputational, or physical harm. Even apparently harmless data can become sensitive when combined with other sources.

Research data ethics concerns the morally justified collection, interpretation, protection, sharing, and disposal of data. Lifecycle governance converts those ethical commitments into institutional arrangements, documented procedures, technical controls, and accountable decisions. For doctoral researchers and business leaders, this is a strategic issue. Weak data governance can invalidate findings, breach law, damage stakeholder trust, and compromise the legitimacy of an entire research programme. Strong governance improves reproducibility, organizational learning, auditability, and the long-term value of research assets.

The central argument of this chapter is that ethical data management is not a final compliance activity. It begins when a research question is formulated and continues through design, collection, processing, analysis, publication, reuse, retention, and destruction. A responsible researcher must ask not only, “Can this data be obtained?” but also, “Should it be obtained, for what purpose, under whose authority, with what safeguards, and for how long?”

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the ethical, legal, methodological, and strategic significance of research data governance.

2. Develop a data management plan covering collection, documentation, quality, ownership, provenance, retention, sharing, and disposal.

3. Distinguish data stewardship, custodianship, ownership, and responsibility.

4. Apply FAIR and CARE principles while recognizing their different purposes and possible tensions.

5. Select appropriate metadata, security, access, retention, and preservation practices.

6. Evaluate risks associated with secondary use, linkage, artificial intelligence, cloud platforms, and cross-border data transfer.

7. Design governance arrangements that support both research integrity and legitimate stakeholder interests.

The Data Lifecycle as an Ethical Architecture

A data lifecycle is a sequence of interconnected stages through which data move. Common stages include planning, collection or creation, processing, documentation, analysis, dissemination and sharing, preservation, reuse, and disposal. The stages are analytical rather than perfectly linear. A project may return to earlier stages when errors are discovered, instruments are revised, or new consent is required.

Lifecycle governance means assigning decisions, responsibilities, controls, and evidence to each stage. It prevents a common failure in research: treating data protection as a storage problem while neglecting collection, interpretation, or eventual reuse. For example, encrypted storage cannot correct an ethically defective consent process, misleading variable definitions, or undocumented transformations.

A useful governance question at every stage is:

  • What data are needed and why?
  • Who may be affected by their collection or use?
  • What authority permits the activity?
  • What quality and provenance information must be recorded?
  • Who is accountable for decisions and incidents?
  • What controls are proportionate to the risk?
  • What will happen when the research ends?

These questions link ethics to research design. Data minimization, purpose limitation, transparency, fairness, confidentiality, accountability, and respect for autonomy are not separate administrative ideals; they shape the validity and legitimacy of evidence.

Planning and Data Classification

Planning begins with a data inventory. Researchers should identify data sources, formats, volume, sensitivity, ownership claims, expected users, collection locations, and dependencies on third-party systems. A classification scheme may distinguish public, internal, confidential, personal, sensitive personal, proprietary, regulated, and culturally restricted data. Classification should be based on potential harm and obligations, not merely on the researcher's convenience.

Data minimization requires collecting only what is necessary for a legitimate research purpose. A survey that gathers exact birth dates when age bands are sufficient creates avoidable risk. Similarly, storing names in an analytical file when a coded identifier is adequate increases exposure without improving inference. Minimization must, however, be balanced against the need to preserve variables required for valid analysis and future verification.

A data management plan (DMP) records intended practices before collection begins. It should be treated as a living governance document rather than a form completed once for approval. Material changes—such as a new data source, a different sharing purpose, or an unexpected security incident—should be documented and reviewed.

Core Concepts and Terminology

Data provenance is the documented history of data origin, transformation, movement, and use. Provenance answers where data came from, who changed them, when changes occurred, and which procedures produced derived outputs.

Metadata are structured information describing data, including their content, context, structure, quality, creator, access conditions, and technical characteristics.

Data quality refers to fitness for a defined purpose. It may include accuracy, completeness, consistency, timeliness, validity, uniqueness, and representativeness.

Data ownership is a legal or organizational claim concerning rights to control, use, license, or dispose of data. Ownership is not identical to ethical authority.

Data stewardship is the responsible oversight of data throughout their lifecycle. A steward protects value, integrity, rights, and usability.

Data custodian is a person or unit responsible for operational controls such as storage, access management, backup, and security.

Controller generally refers to the party determining purposes and means of processing, while a processor acts on behalf of a controller under defined instructions. Exact legal meanings vary by jurisdiction.

De-identification is the removal or transformation of identifying information. Anonymization aims to make re-identification reasonably impracticable, whereas pseudonymization replaces identifiers with codes but retains a possibility of re-linkage.

Consent is a voluntary, informed, and sufficiently specific agreement to a defined activity. Consent is not always the only lawful or ethical basis for processing.

Retention is the period for which data are preserved. Disposition is the authorized destruction, return, archival transfer, or continued preservation of data.

Interoperability is the ability of systems or datasets to exchange and meaningfully use information. Reproducibility concerns whether results can be obtained again using the described data, code, and procedures.

Data sovereignty concerns the authority of people, communities, nations, or institutions over data relating to them, including where data are stored and who may govern their use.

Designing a Data Management Plan

A doctoral-quality DMP should connect methodological decisions with governance controls. Its sections may include the following.

Purpose, Scope, and Expected Outputs

The plan states the research questions, data required, anticipated outputs, participating institutions, data subjects, and likely secondary uses. It should identify whether the project produces raw, processed, derived, linked, simulated, or administrative data. The distinction matters because derived datasets may remain sensitive even when direct identifiers have been removed.

Collection and Lawful Authority

Researchers should specify instruments, sampling procedures, data sources, collection dates, locations, and responsible personnel. For human data, the plan should address information provided to participants, consent or another lawful basis, withdrawal procedures, compensation, vulnerable groups, deception, and risks of coercion. Institutional ethics approval is important but does not replace continuing ethical judgment.

Secondary data require particular care. Public availability does not automatically mean unrestricted ethical use. A dataset may have been released for one purpose, under conditions that exclude commercial use, individual profiling, or linkage with other records. Researchers must examine terms of access, original notices, restrictions, and the reasonable expectations of data subjects.

Documentation and Metadata

Documentation enables interpretation long after the original team has dispersed. A useful dataset should be accompanied by a readme file, data dictionary, codebook, collection protocol, instrument versions, sampling information, transformation log, missing-data explanation, file naming convention, licensing statement, and contact information. Metadata should describe both technical features and substantive meaning. A variable named “income” is inadequate without its currency, reference period, unit, population, treatment of missing values, and collection method.

Metadata standards should be selected according to discipline and data type. Dublin Core may support general resource description; DataCite metadata support citation and discovery; the Data Documentation Initiative is widely used for social-science data; ISO 19115 supports geographic information; and schema.org can improve web discoverability. Standards should not be adopted mechanically. The governing test is whether metadata allow a competent future user to discover, understand, evaluate, and appropriately reuse the data.

Quality Assurance

Data quality is produced by design, not merely checked at the end. Quality controls may include pilot testing, instrument validation, duplicate detection, range checks, logic checks, audit trails, inter-rater reliability procedures, calibration, version control, and independent review. Researchers should distinguish an error from an unusual but genuine observation. Automatic deletion of outliers can introduce bias and destroy evidence.

Quality reports should disclose missingness, exclusions, measurement changes, coding decisions, nonresponse, sampling limitations, and possible sources of systematic error. In qualitative research, quality documentation may include reflexive notes, interview protocols, coding frameworks, analytic memos, and records of interpretive disagreements. Transparency does not require pretending that all judgment has been eliminated; it requires making significant judgment visible.

Ownership, Rights, and Responsibilities

Ownership may rest with a university, sponsor, public agency, firm, researcher, participant, or several parties under contract. Agreements should address intellectual property, access, publication review, confidentiality, licensing, commercial use, deposits in repositories, and responsibilities after staff departure. Data ownership alone does not authorize unethical use. A company may own a customer database while still being restricted by privacy law, contract, consent expectations, or professional duties.

A responsibility matrix can clarify roles:

  • The principal investigator is accountable for ethical and scientific decisions.
  • Data stewards coordinate classification, documentation, access, quality, and lifecycle controls.
  • Data custodians operate repositories, backups, authentication, and technical safeguards.
  • Analysts protect confidentiality, preserve provenance, and report limitations.
  • Institutional review boards, ethics committees, privacy officers, and research offices provide oversight.
  • Sponsors and data providers must communicate restrictions and support agreed controls.

Shared responsibility must not become diluted responsibility. Every critical decision should have a named accountable role.

Security and Access Control

Security should be proportionate to risk and based on defense in depth. Measures may include role-based access, least privilege, multi-factor authentication, encryption in transit and at rest, secure transfer, device management, logging, backup, vulnerability management, staff training, and incident response. Access should be reviewed periodically, especially after staff changes or project completion.

A secure environment is not necessarily a usable research environment. Excessive restrictions may prevent legitimate analysis, while weak controls expose participants and organizations. Controlled-access repositories, secure enclaves, synthetic data, statistical disclosure control, and data-use agreements can support responsible sharing when open publication is impossible.

Retention, Preservation, and Disposal

Retention should be justified by research integrity, legal requirements, contractual obligations, participant expectations, potential verification, and future value. “Keep everything forever” is not a responsible policy: indefinite retention increases exposure, cost, and the possibility of secondary misuse. Conversely, premature destruction can prevent audit, replication, or the resolution of misconduct allegations.

A retention schedule should distinguish raw data, consent records, identifiers, code, documentation, derived datasets, and published outputs. Identifiers may be destroyed earlier than de-identified analytical data where the research design permits. Disposal must be secure and verifiable: deletion from active systems, removal from accessible backups where technically and operationally feasible, physical destruction of media, and documented authorization. Legal holds or investigations may suspend ordinary destruction.

FAIR and CARE: Complementary but Not Interchangeable

The FAIR principles promote data that are Findable, Accessible, Interoperable, and Reusable. Findability requires persistent identifiers, rich metadata, and indexing. Accessibility concerns retrievability through appropriate protocols, including controlled access where necessary. Interoperability requires meaningful formats, shared vocabularies, and machine-readable structure. Reusability depends on clear provenance, licensing, quality information, and sufficient contextual documentation.

FAIR is primarily a framework for enhancing the utility and stewardship of data. It does not mean that all data should be open. Sensitive data can be FAIR through discoverable metadata and a transparent process for requesting controlled access, even when the data files themselves cannot be publicly downloaded.

The CARE principles—Collective benefit, Authority to control, Responsibility, and Ethics—emphasize Indigenous data governance and the rights and interests of communities. CARE challenges a purely technical conception of openness. Data about a community may be scientifically reusable yet harmful, extractive, or inconsistent with community authority. Community-defined protocols, benefit sharing, culturally appropriate consent, and restrictions on interpretation may therefore be necessary.

FAIR and CARE can be combined, but tensions must be managed rather than concealed. A responsible plan may make metadata findable while restricting records, establish community governance over access, require respectful attribution, and prohibit uses that conflict with collective values. CARE is not simply an additional metadata field; it may alter who decides, what counts as benefit, and whether reuse is legitimate.

From Data Ethics to Organizational Strategy

For organizations, research data governance is an institutional capability. It affects merger due diligence, customer analytics, market intelligence, employee research, innovation, and public reporting. Senior leaders should view governance as a portfolio of risk and value decisions rather than a technical service delegated entirely to information technology.

A data governance committee can align research, legal, compliance, information security, records management, and community or participant interests. It should establish policies, escalation routes, approval thresholds, training requirements, and performance indicators. Useful indicators include completion of DMPs, metadata coverage, access-review completion, unresolved incidents, time to respond to data requests, reproducibility of key analyses, and percentage of datasets with documented retention decisions. Metrics should support learning rather than encourage superficial compliance.

Technology can improve governance through electronic laboratory notebooks, research data repositories, catalogues, workflow systems, version-control platforms, automated validation, lineage tools, and access logs. Automation, however, can reproduce errors at scale. A machine-learning system may infer sensitive attributes, link supposedly separate datasets, or produce discriminatory classifications. Automated quality checks should therefore be validated, monitored, and subject to human review.

Generative artificial intelligence creates additional concerns. Researchers should document whether data were submitted to an external model, whether provider terms permit retention or training, how confidential information is protected, and how generated summaries or code were verified. AI outputs are not automatically reliable evidence. Provenance should distinguish human observations, algorithmic transformations, model-generated material, and researcher interpretation.

Illustrative Case: The Regional Supplier Resilience Study

Background

A doctoral research team at a business school studied whether small manufacturers improved supply-chain resilience after a major disruption. The team planned to combine interviews with procurement managers, supplier-performance records provided by a consortium, and publicly available company information. The consortium wished to receive an industry report, while participating firms were concerned about reputational consequences.

Situation and Problem

The initial proposal requested employee names, exact plant locations, detailed delivery failures, and contract values. The researchers intended to publish a de-identified dataset after completing the study. During review, it became clear that small firms could be re-identified through combinations of location, industry, contract size, and unusual disruption events. Several managers also assumed that their interview statements would be used only for internal benchmarking.

Analysis

The team identified four risks. First, the proposed variables exceeded what was necessary for the research questions. Second, consent and organizational authorization did not clearly cover public release or linkage. Third, the consortium's ownership claim conflicted with firms' confidentiality interests. Fourth, the planned publication lacked a documented lineage from administrative records to analytical indicators.

The team revised its DMP. It collected size bands rather than exact employment counts, generalized locations, and separated direct identifiers from analytical files. A trusted intermediary created coded records, while the linkage key remained under independent custody. Interviews used a revised information sheet distinguishing academic publication, consortium reporting, and future reuse. A data-use agreement specified permitted purposes, access review, breach notification, publication procedures, and destruction dates.

The researchers created a data dictionary, versioned transformation scripts, and a provenance record for each derived resilience measure. The consortium received an aggregated report and methodological documentation. External researchers could discover the dataset through a repository record but could access detailed records only through a controlled application reviewed by a governance panel.

Outcome

The revised design reduced re-identification risk while preserving the variables necessary for analysis. The study reported limitations caused by aggregation and nonresponse rather than presenting the data as complete. When one firm later withdrew permission for a particular interview quotation, the team could locate the quotation through coded records and remove it without corrupting the entire project archive.

Learning Points

The case demonstrates that governance is a design activity, not a post-publication clean-up exercise. It also shows that de-identification is contextual, organizational ownership does not settle ethical authority, and controlled access can support meaningful reuse. Most importantly, the DMP connected consent, data minimization, provenance, security, reporting, and disposal into one accountable system.

Persistent Challenges and Common Errors

One frequent mistake is confusing anonymization with the removal of names. Re-identification can occur through rare combinations, timestamps, geographies, free text, images, or external datasets. Risk assessment must consider realistic means available to likely users.

Another mistake is treating consent as unlimited permission. Participants may agree to a study while rejecting commercial use, automated profiling, or community-level publication. Consent language should match actual practice, and substantial changes may require renewed permission or independent ethical review.

Researchers also commonly neglect version control. Overwriting a spreadsheet, changing a coding rule without recording it, or failing to preserve the exact data used for a published result undermines provenance. Repositories and scripts help, but only when teams use disciplined naming, review, and release procedures.

Open-data advocacy can become ethically simplistic. Openness may conflict with confidentiality, safety, intellectual property, national security, contractual duties, or community sovereignty. The appropriate question is not whether data are open, but whether access is proportionate, justified, and governed.

Finally, governance documents can become performative. A beautifully written DMP has little value if staff are not trained, access is never reviewed, incidents are hidden, or retention schedules are ignored. Governance must be tested through audits, exercises, independent challenge, and corrective action.

Emerging Directions

Research governance is moving toward machine-actionable DMPs in which metadata, permissions, retention rules, and workflows can be interpreted by repositories and research systems. Data spaces and secure federated analysis may allow researchers to run approved computations without transferring sensitive records. Privacy-enhancing techniques—including differential privacy, secure multiparty computation, trusted research environments, and synthetic data—may expand legitimate analysis, although each introduces assumptions and possible quality loss.

There is also a growing emphasis on responsible research assessment. Institutions increasingly recognize that high-quality documentation, carefully managed negative results, community engagement, and reproducible workflows are scholarly contributions, even when they do not produce a publicly downloadable dataset. Future governance will likely require more explicit attention to environmental costs, including the energy and infrastructure demands of large-scale storage and artificial intelligence.

These developments do not eliminate judgment. They make judgment more consequential. Technical capability expands what can be done; ethical governance determines what should be done and under whose authority.

Best-Practice Protocol

A practical governance protocol for doctoral research is to:

1. Inventory all anticipated data and classify risk before collection.

2. Define purpose, authority, affected parties, and minimum necessary variables.

3. Obtain ethics, contractual, privacy, and community approvals appropriate to the project.

4. Assign accountable roles and document ownership and stewardship arrangements.

5. Establish metadata, naming, version-control, quality, and provenance procedures.

6. Separate identifiers from analytical data and implement proportionate security.

7. Review consent, access, and data-sharing decisions when the project changes.

8. Preserve code, documentation, and key versions needed for verification.

9. Publish appropriate metadata and use controlled access where open release is unsafe.

10. Apply a documented retention and disposal schedule, recording exceptions and final actions.

11. Audit compliance and learn from incidents rather than treating them solely as individual failures.

Chapter Summary

Research data ethics governs the entire lifecycle of evidence, from planning and collection to reuse and disposal. A data management plan translates ethical and methodological commitments into decisions about purpose, minimization, consent, quality, metadata, provenance, ownership, access, security, retention, and destruction. FAIR principles improve discoverability, accessibility, interoperability, and reuse, while CARE principles foreground collective benefit, authority, responsibility, and ethics, especially in Indigenous and community-related research. They should be applied together with sensitivity to power and context.

Effective governance assigns clear responsibilities to investigators, stewards, custodians, institutions, sponsors, and communities. It recognizes that public availability does not eliminate ethical duties, de-identification is contextual, and controlled access may be preferable to unrestricted openness. Digital repositories, automation, analytics, and artificial intelligence can strengthen stewardship but also create new risks requiring validation, transparency, and human accountability. The strategic objective is not merely to protect data; it is to produce trustworthy, legitimate, interpretable, and responsibly reusable knowledge.

Key Terms

Data management plan: A living document specifying how research data will be collected, documented, protected, shared, retained, and disposed of.

Data lifecycle: The sequence of stages through which data are planned, created, processed, analyzed, shared, preserved, and disposed of.

Data provenance: The recorded history of a dataset’s origin, transformations, movement, and use.

Metadata: Structured information describing a dataset’s content, context, structure, quality, and conditions of use.

Data stewardship: Responsible oversight of data throughout their lifecycle.

Data custodian: The person or unit operating data storage, access, backup, and security controls.

Data ownership: A legal or organizational claim to control or use data.

Data minimization: Limiting collection to information necessary for a legitimate purpose.

De-identification: Transformation or removal of identifying information to reduce identification risk.

Pseudonymization: Replacing identifiers with codes while retaining a possible re-linkage mechanism.

Anonymization: Processing intended to make re-identification reasonably impracticable.

Data quality: Fitness of data for a defined analytical or operational purpose.

FAIR principles: Principles requiring data to be Findable, Accessible, Interoperable, and Reusable.

CARE principles: Principles emphasizing Collective benefit, Authority to control, Responsibility, and Ethics.

Data sovereignty: Authority of people, communities, institutions, or nations over data relating to them.

Controlled access: A system in which data use is permitted only after defined authorization and safeguards.

Retention schedule: A documented rule specifying how long particular records are preserved and when they are disposed of.

Provenance record: A detailed account linking source data, transformations, analysis, and outputs.

Data-use agreement: A contract defining permitted uses, restrictions, security, publication, and responsibilities.

Research integrity: Conduct that supports honesty, rigor, transparency, accountability, and reliability in research.

Review Questions

Short Answer Questions

1. Why should a data management plan be treated as a living document?

2. Distinguish data ownership from data stewardship.

3. What is the difference between pseudonymization and anonymization?

4. Identify two purposes served by metadata.

5. Why does FAIR not necessarily mean unrestricted public access?

Long Answer Questions

1. Explain how ethical considerations apply at each major stage of the research data lifecycle.

2. Discuss the principal components of a doctoral-level data management plan.

3. Compare FAIR and CARE principles, including situations in which they may come into tension.

4. Explain how provenance and quality assurance contribute to research integrity and reproducibility.

5. Evaluate the organizational roles required for effective research data governance.

Analytical / Application Questions

1. A researcher wants to publish a dataset containing geographic information, firm size, and unusual transaction dates. Analyze the re-identification risks and propose a responsible sharing model.

2. An Indigenous community objects to unrestricted reuse of a dataset collected with university funding. Using FAIR and CARE, design an access and governance approach that recognizes both research value and community authority.

3. A research team discovers that an external generative-AI platform retained confidential interview transcripts. Identify the governance failures, immediate actions, and longer-term controls required.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the purpose of a data management plan?

A. To guarantee that every dataset will be publicly released

B. To document lifecycle decisions, responsibilities, controls, and intended uses

C. To replace institutional ethics review

D. To eliminate the need for data-quality assessment

Correct Answer: B. To document lifecycle decisions, responsibilities, controls, and intended uses

Question 2

A researcher removes participant names but retains exact location, rare occupation, and unusual event dates. What is the principal concern?

A. The data have become too interoperable

B. The metadata are necessarily incomplete

C. Individuals may still be re-identified through combinations of attributes

D. The research has automatically become non-reproducible

Correct Answer: C. Individuals may still be re-identified through combinations of attributes

Question 3

Which practice most directly strengthens data provenance?

A. Overwriting earlier spreadsheets with corrected values

B. Recording source data, transformations, versions, and responsible personnel

C. Deleting raw data after producing a graph

D. Using only proprietary file formats

Correct Answer: B. Recording source data, transformations, versions, and responsible personnel

Question 4

What is the most accurate interpretation of FAIR accessibility?

A. All records must be downloadable without restrictions

B. Data must be stored permanently in an open repository

C. Data should be retrievable through appropriate, possibly controlled, procedures

D. Only researchers from the original institution may use the data

Correct Answer: C. Data should be retrievable through appropriate, possibly controlled, procedures

Question 5

Which principle is most specifically associated with collective benefit and community authority over data?

A. CARE

B. Least privilege

C. Version control

D. Data minimization

Correct Answer: A. CARE

Question 6

A company legally owns a customer database. Which conclusion is ethically justified?

A. Ownership permits any conceivable research use

B. Ownership removes privacy and contractual obligations

C. Ownership may coexist with duties concerning privacy, purpose, consent, and harm

D. Ownership automatically transfers stewardship to the researcher

Correct Answer: C. Ownership may coexist with duties concerning privacy, purpose, consent, and harm

Question 7

Which arrangement best reflects separation of stewardship and custodianship?

A. The analyst alone decides access and operates the server

B. A steward oversees responsible use while a custodian operates technical controls

C. The sponsor destroys all documentation after publication

D. Participants manage every backup without institutional support

Correct Answer: B. A steward oversees responsible use while a custodian operates technical controls

Question 8

Why might controlled access be preferable to unrestricted open release?

A. It prevents all future reuse

B. It can support legitimate reuse while reducing confidentiality and re-identification risks

C. It makes metadata unnecessary

D. It guarantees that the data are error-free

Correct Answer: B. It can support legitimate reuse while reducing confidentiality and re-identification risks

Question 9

Which action is most consistent with responsible retention governance?

A. Keeping every identifier indefinitely as a precaution

B. Destroying all raw data immediately after analysis

C. Setting justified retention periods for different data types and documenting disposal

D. Allowing individual researchers to retain copies permanently

Correct Answer: C. Setting justified retention periods for different data types and documenting disposal

Question 10

A generative-AI tool is used to summarize confidential interviews. What should the research team do first?

A. Assume the provider cannot access submitted material

B. Publish the summaries without verification

C. Assess provider terms, confidentiality risks, authorization, and provenance

D. Delete the interview protocol because the tool performed the analysis

Correct Answer: C. Assess provider terms, confidentiality risks, authorization, and provenance

Research Ethics & Computer Applications
Chapter 7 of 15

Research Ethics & Computer Applications

Chapter 8
Privacy, Cybersecurity and Intellectual Property

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

8. Privacy, Cybersecurity and Intellectual Property

Introduction and Context

Research increasingly depends on digital records, cloud platforms, networked devices, artificial intelligence, and large datasets. These technologies create significant opportunities for doctoral researchers and organizations, but they also create obligations. A dataset may contain personal information, commercially sensitive material, confidential communications, copyrighted works, trade secrets, or inventions that require legal protection. A failure to protect such material can harm research participants, damage institutional reputation, invalidate research findings, expose an organization to liability, and weaken public trust.

Privacy, cybersecurity, and intellectual property are related but distinct domains. Privacy concerns the appropriate collection, use, disclosure, and control of information about identifiable individuals. Cybersecurity concerns the protection of information systems and data against unauthorized access, alteration, disruption, or destruction. Intellectual property concerns legally recognized interests in creations, inventions, expressive works, brands, and certain information resources. Ethical research practice requires these domains to be considered together rather than treated as separate compliance exercises.

The central principle of this chapter is responsible information stewardship. Researchers and managers should be able to explain why data are needed, limit collection to legitimate purposes, protect information throughout its life cycle, respect the rights of creators and data subjects, and respond competently when controls fail. Legal requirements vary across jurisdictions, and this chapter therefore presents general principles rather than jurisdiction-specific legal advice.

Learning Objectives

After studying this chapter, the reader should be able to:

1. Explain the relationship between privacy, cybersecurity, confidentiality, and intellectual property.

2. Apply privacy-by-design and data-minimization principles to research and organizational systems.

3. Distinguish anonymization from pseudonymization and evaluate their limitations.

4. Design proportionate access controls, encryption practices, and incident-response procedures.

5. Evaluate major data-protection principles and the governance responsibilities of researchers and managers.

6. Distinguish copyright, licensing, patents, trade secrets, trademarks, and database rights.

7. Analyze ethical and managerial trade-offs in the use, sharing, and commercialization of data and digital products.

The Information Stewardship Problem

Information has value because it supports decisions, innovation, accountability, and learning. The same information may also create vulnerability. Employee records can facilitate workforce planning but expose individuals to discrimination or identity theft. Customer analytics can improve services but enable intrusive profiling. Research interviews can produce valuable theory but reveal participants’ political views, health information, or professional concerns.

A useful distinction is between confidentiality, privacy, and security. Confidentiality is an obligation not to disclose information to unauthorized parties. Privacy is concerned with the legitimate expectations and rights of individuals in relation to information about them. Security is the set of technical, organizational, and physical safeguards used to protect information. Security supports privacy and confidentiality, but it cannot by itself make an unjustified collection lawful or ethical.

A second distinction concerns the information life cycle: collection, classification, storage, use, sharing, retention, archival, and destruction. A control applied only at storage is inadequate. For example, encrypted storage does not prevent excessive collection, accidental disclosure in an email, or inappropriate access by an authorized user. Governance must therefore follow the data from its origin to its final disposal.

Privacy-by-Design and Data Minimization

Privacy-by-design means incorporating privacy considerations into the architecture, processes, and default settings of a system before harm occurs. It is more effective than adding privacy controls after a database, survey, or artificial-intelligence application has already been implemented. A privacy-by-design review asks what information is necessary, who needs access, how long it should be retained, what risks are foreseeable, and how individuals can exercise their rights.

The principle has several practical implications. Privacy should be proactive rather than reactive; protective settings should be the default rather than an optional burden placed on users; and privacy controls should cover the full information life cycle. Privacy should also be embedded in organizational responsibility, procurement, project management, and system testing.

Data minimization is the practice of collecting, using, and retaining only the information necessary for a defined and legitimate purpose. It is not equivalent to collecting everything that might be useful later. Minimization improves privacy, reduces storage costs, limits breach impact, and often improves analytical quality by reducing irrelevant variables. Researchers should distinguish essential variables from convenient variables and document the rationale for inclusion.

Purpose limitation is closely related. Information collected for one purpose should not automatically be reused for an incompatible purpose. Secondary use may be legitimate when it is authorized, ethically approved, compatible with the original purpose, adequately protected, and transparent to affected individuals. A doctoral researcher who collects employee interviews for a study of organizational learning cannot assume that the recordings may later be used to train a commercial language model.

Anonymization, Pseudonymization, and Re-identification Risk

Anonymization seeks to make it impossible, or reasonably impracticable, to identify an individual from data, alone or in combination with other reasonably available information. Proper anonymization is stronger than removing names. Direct identifiers, quasi-identifiers, unique combinations, free-text comments, images, location trails, and timestamps may all support re-identification.

Common techniques include aggregation, suppression, generalization, perturbation, and controlled release. Aggregation reports groups rather than individuals; generalization changes precise values into broader categories; suppression removes risky values; and perturbation introduces carefully managed statistical noise. These techniques involve trade-offs. Excessive transformation may reduce research validity, while weak transformation may create a false sense of safety.

Pseudonymization replaces direct identifiers with codes or tokens while retaining a separate key that permits re-linkage. It reduces exposure and can support longitudinal research, but it does not make data anonymous if the key or other information can reconnect records to individuals. The key should be separately stored, strongly protected, and accessible only to authorized personnel.

Re-identification risk is contextual and dynamic. A dataset considered low risk when released may become identifiable when combined with public registers, social-media data, commercial datasets, or newly available analytic tools. Researchers should conduct a re-identification assessment, consider the realistic capabilities of potential recipients, and avoid describing pseudonymized data as anonymous.

Data Protection Governance

Data-protection regimes commonly express principles such as lawfulness, fairness, transparency, purpose limitation, data minimization, accuracy, storage limitation, security, and accountability. The exact terminology and enforcement mechanisms differ by jurisdiction, but the governance logic is broadly applicable.

A defensible research project should identify the responsible institution or controller, clarify the role of processors and service providers, document the purpose and legal or ethical basis for processing, specify retention periods, and establish procedures for access, correction, deletion, objection, or other applicable rights. Consent is important in many projects but is not a universal solution. Consent must be informed, specific, voluntary, and capable of withdrawal where applicable. Power relationships, such as those between employers and employees or supervisors and students, may make consent less voluntary than it appears.

A data protection impact assessment is a structured evaluation of processing that may create substantial risks to individuals. It should describe the processing, assess necessity and proportionality, identify threats and harms, evaluate existing controls, and specify additional measures. High-risk projects commonly include sensitive information, systematic monitoring, large-scale profiling, vulnerable populations, biometric identification, or significant automated decision-making.

Institutional policies, research ethics committees, records of processing, vendor assessments, training, and periodic audits convert principles into accountability. Governance should allocate responsibility rather than assume that “the IT department” or “the researcher” alone owns the problem.

Cybersecurity as a Research and Management Responsibility

Cybersecurity protects the confidentiality, integrity, and availability of information—often called the CIA triad. Confidentiality prevents unauthorized disclosure; integrity protects accuracy and completeness; availability ensures that authorized users can access systems when needed. These goals can conflict. Strong access restrictions may improve confidentiality but impair availability; rapid recovery may require temporary reduction of controls. Good security is therefore risk-based and proportionate.

A practical security architecture begins with asset identification and classification. Data may be classified as public, internal, confidential, or highly restricted, with handling requirements assigned to each class. Threat modeling then considers possible adversaries, vulnerabilities, consequences, and existing safeguards. Threats include phishing, credential theft, ransomware, malicious insiders, insecure application programming interfaces, lost devices, misconfigured cloud storage, supply-chain compromise, and accidental disclosure.

Access Controls

Access should follow least privilege: users receive only the access necessary for their current responsibilities. Role-based access control assigns permissions according to job or research role, while attribute-based approaches may also consider location, device security, time, project membership, or data sensitivity. Separation of duties reduces the risk that one person can initiate and conceal a harmful transaction.

Strong authentication should be used for sensitive systems, particularly multi-factor authentication. Access rights should be reviewed regularly, removed promptly when a role changes, and terminated when a relationship ends. Shared accounts undermine accountability and should normally be avoided. Audit logs should record meaningful access and administrative actions, while respecting privacy and retention requirements.

Encryption and Key Management

Encryption transforms readable information into an unintelligible form for anyone without the appropriate key. Encryption in transit protects communications across networks; encryption at rest protects stored data; and, in some contexts, field-level or end-to-end encryption provides additional protection. Encryption is not a substitute for access control. A person who legitimately possesses a decryption key may still misuse the information.

Key management is often more important than the encryption algorithm itself. Keys should be generated securely, stored separately where feasible, rotated according to risk, backed up safely, and revoked when compromised. Passwords should not be stored in plain text; appropriate password hashing and salting should be used for authentication systems. Researchers should also consider encrypted backups and the consequences of losing keys permanently.

Secure Development and Cloud Use

Security should be integrated into system development through requirements analysis, code review, dependency management, vulnerability testing, patching, and controlled deployment. Vendors and cloud providers should be assessed for access practices, breach notification, data location, subcontracting, deletion procedures, audit rights, and continuity arrangements. “Cloud” does not mean that responsibility has disappeared; it changes how responsibility is distributed.

Incident Response and Recovery

An incident is an event that threatens the confidentiality, integrity, or availability of information. Examples include a stolen laptop, accidental email disclosure, ransomware, unauthorized database access, or manipulation of research results. A mature organization plans before an incident occurs.

An incident-response process generally includes preparation, detection and analysis, containment, eradication, recovery, notification, and lessons learned. Preparation involves contact lists, decision authority, backups, logging, forensic procedures, legal guidance, and communication templates. During detection, the organization should preserve evidence and determine scope without unnecessarily destroying systems. Containment limits further harm; eradication removes malicious access; recovery restores trustworthy operations and monitors for recurrence.

Notification obligations depend on the jurisdiction, affected data, contractual terms, and level of risk. Individuals, regulators, funders, partners, insurers, and law-enforcement agencies may need to be informed. Communication should be accurate, timely, comprehensible, and free from speculation. Concealing a material incident can increase ethical and legal harm.

Post-incident review should ask not merely who made an error, but why the system permitted the error, whether training was realistic, whether warnings were usable, and whether incentives encouraged unsafe behavior. A learning-oriented response improves controls without abandoning accountability for reckless or malicious conduct.

Intellectual Property in Research and Digital Business

Intellectual property (IP) law gives creators or rights holders defined interests in intangible outputs. The relevant right depends on the type of output and the jurisdiction.

Copyright generally protects original expression fixed in a tangible or digital form, including articles, software code, photographs, videos, diagrams, and databases as structured works. It protects expression rather than ideas, facts, methods, or discoveries as such. Ownership may belong to the author, employer, commissioning party, or another party under applicable law and contract. Copyright may include economic rights and, in some jurisdictions, moral rights concerning attribution and integrity.

A license is permission to use protected material under specified conditions. Licenses may limit duration, territory, audience, modification, redistribution, commercial use, or sublicensing. Open licenses are not the same as public-domain status. For example, an attribution requirement or share-alike condition may still apply. Software dependencies require particular care because incompatible licenses can restrict distribution or commercial use.

Patents protect qualifying inventions, generally requiring novelty, an inventive or non-obvious step, and industrial or practical applicability, subject to national law. Public disclosure before filing can undermine patentability in many jurisdictions. Researchers should therefore discuss publication and ownership early when a project may generate a commercially valuable technical invention. A patent is a territorial exclusion right, not a guarantee that the holder is free to practice the invention without infringing another patent.

Trade secrets protect valuable information that is secret and subject to reasonable measures to maintain secrecy. Confidential algorithms, pricing models, experimental results, customer lists, and manufacturing processes may qualify. Once information is publicly disclosed, trade-secret protection may be lost. Confidentiality agreements, restricted access, labeling, employee exit procedures, and secure repositories support protection.

Trademarks distinguish goods or services through names, logos, symbols, or other identifiers. They are relevant when research outputs become products, platforms, or consultancy services. Database rights, recognized in some jurisdictions, may protect substantial investment in obtaining, verifying, or presenting database contents, even where individual facts are not copyrighted. The legal treatment of databases varies considerably and requires local advice.

Ownership and authorship should be addressed at project initiation. A written agreement can clarify background IP, newly created IP, publication rights, data access, attribution, commercialization, confidentiality, and obligations when a researcher leaves. Academic authorship should reflect substantial intellectual contribution rather than organizational rank or control of funding.

Ethical and Managerial Trade-offs

Compliance is a minimum threshold, not the complete meaning of ethical conduct. A practice may be legally permissible yet ethically questionable if it is opaque, disproportionate, discriminatory, or inconsistent with reasonable expectations. Conversely, excessive restriction can obstruct reproducibility, public-interest research, and innovation.

Managers must balance openness with protection. Open data may improve verification, but release may expose participants or enable commercial exploitation without fair recognition. Data retention may support auditability, but indefinite retention increases exposure. Automated monitoring may improve security, but excessive surveillance can damage autonomy and trust. Ethical evaluation should consider necessity, proportionality, fairness, power, inclusion, reversibility, and the distribution of benefits and harms.

Artificial intelligence intensifies these challenges. Training data may contain personal information or copyrighted material; model outputs may reproduce protected content; and inference systems may derive sensitive attributes that were never explicitly collected. Organizations should document data provenance, assess licensing and privacy risks, test for discriminatory outcomes, restrict access to prompts and outputs, and avoid entering confidential research material into public tools without authorization. Human review remains important where automated outputs affect employment, credit, education, health, or research participation.

Illustrative Case: The Workforce Analytics Lab

Background

A university research team partnered with a multinational retailer to study employee turnover. The retailer supplied pseudonymized records containing job history, attendance, performance ratings, age bands, location, and free-text manager comments. The team planned to combine these records with public labor-market data and develop a predictive model.

Situation and Problem

The project received ethical approval based on the assumption that the data were anonymous. A data scientist later discovered that a small number of employees could be identified by combining rare job titles, work locations, and dates. The free-text comments also included health references and allegations about workplace conduct. A commercial software vendor requested access to the complete dataset to improve its prediction product.

Analysis

The records were pseudonymized, not anonymous, because the retailer retained a re-identification key and external data could identify unusual cases. The project also raised purpose-limitation and secondary-use concerns. The vendor’s request exceeded the original research purpose, and the free-text field contained more sensitive information than was necessary. The team had not documented retention, access review, incident notification, or intellectual-property ownership for the predictive model.

Approach and Strategy

The team paused external sharing and conducted a renewed impact assessment. It removed free-text comments, generalized locations and dates, reduced variables to those justified by the research question, and retained the re-identification key solely with the retailer. Access was restricted through role-based permissions and multi-factor authentication, while encrypted storage and monitored downloads were implemented. The vendor received only a synthetic or aggregated test dataset until a separate agreement addressed purpose, security, deletion, audit rights, and IP ownership.

The research team also adopted a model-governance plan. It tested performance across employee groups, documented limitations, prohibited use for disciplinary decisions without independent review, and established a destruction date. The publication described the methodology and risks without releasing records that could identify individuals.

Outcome

The revised project produced a less detailed but more defensible dataset. Some predictive accuracy declined, but the team concluded that the reduction was acceptable because the original gains depended partly on variables that created disproportionate privacy risks. The partners agreed that the retailer owned its existing data, while rights in the jointly developed research outputs were allocated by contract. The project generated a publishable methodological contribution concerning responsible workforce analytics.

Learning Points

The case demonstrates that removing names is not sufficient anonymization; privacy risk must be assessed in context. It also shows why privacy, cybersecurity, contractual governance, research ethics, and IP ownership should be addressed at project design rather than after data collection. Finally, a small reduction in analytical performance may be justified when it substantially reduces harm and improves legitimacy.

Challenges, Limitations, and Common Mistakes

Several recurring mistakes undermine responsible practice. Organizations often collect data “just in case,” retain it indefinitely, confuse pseudonymization with anonymity, rely on consent forms that are too general, and overlook information embedded in free text or metadata. Others purchase software without examining vendor access, use shared passwords, fail to test backups, or treat annual training as a substitute for usable security design.

Legal rules also have limits. Privacy law may not fully address group harms, inferred information, or future forms of re-identification. Copyright exceptions differ across jurisdictions and may be uncertain for text and data mining. Patent protection can conflict with timely academic publication. Security controls may exclude legitimate users or create inequitable burdens. Ethical review therefore requires professional judgment, consultation with legal and technical specialists, and continuing reassessment as technology and context change.

Best-Practice Framework for Researchers and Managers

A practical governance sequence is:

1. Define the research or business purpose and identify affected people.

2. Map the data life cycle, including sources, recipients, systems, and deletion points.

3. Minimize variables, retention, copying, and access.

4. Classify data and assess privacy, security, IP, and re-identification risks.

5. Select lawful, ethical, and transparent processing arrangements.

6. Apply least privilege, multi-factor authentication, encryption, secure development, and protected backups.

7. Document ownership, licenses, authorship, publication rights, confidentiality, and vendor obligations.

8. Test controls, review access, monitor incidents, and reassess high-risk processing.

9. Prepare an incident-response and notification plan.

10. Close the project responsibly by returning, archiving, or securely destroying data and keys.

This sequence is not a substitute for specialized advice, but it provides a disciplined basis for decision-making. The strongest programs combine technical safeguards with clear accountability, realistic procedures, informed leadership, and a culture in which reporting concerns is rewarded rather than suppressed.

Current Developments and Emerging Issues

Several developments are reshaping this field. Generative AI increases the volume of data processing and complicates questions of training-data provenance, output ownership, confidential prompts, and automated inference. Privacy-enhancing technologies—including differential privacy, secure multiparty computation, federated learning, and trusted execution environments—seek to support analysis while reducing exposure, although they introduce technical complexity and may affect accuracy.

Regulators and professional bodies are also emphasizing accountability, algorithmic transparency, supply-chain security, resilience, and governance of high-impact automated systems. Cross-border research remains difficult because data-transfer rules, government-access powers, contractual requirements, and IP regimes differ. Organizations that operate internationally should avoid assuming that a control or consent mechanism valid in one jurisdiction is sufficient everywhere.

Chapter Summary

Privacy, cybersecurity, and intellectual property form an integrated foundation for responsible digital research and management. Privacy-by-design places protection into systems from the beginning, while data minimization and purpose limitation reduce unnecessary exposure. Anonymization seeks to prevent identification; pseudonymization reduces risk but preserves the possibility of re-linkage. Effective cybersecurity combines classification, least privilege, strong authentication, encryption, secure development, monitoring, backups, and incident response.

Data-protection governance requires transparency, accountability, proportionality, appropriate retention, and respect for individual rights. Intellectual-property analysis distinguishes copyright, licenses, patents, trade secrets, trademarks, and database rights, with contracts clarifying ownership and permitted use. Ethical practice goes beyond formal compliance by considering power, fairness, foreseeable harm, public benefit, and the consequences of automation. Sound stewardship is therefore a continuing managerial and research responsibility across the entire information life cycle.

Key Terms

Privacy-by-design: Incorporating privacy protections into system architecture, processes, and defaults from the outset.

Data minimization: Collecting, using, and retaining only information necessary for a defined purpose.

Purpose limitation: Restricting use of information to specified and compatible purposes.

Anonymization: Transforming data so individuals are not reasonably identifiable.

Pseudonymization: Replacing identifiers with codes while retaining a protected means of re-identification.

Re-identification: Linking supposedly de-identified information to an identifiable person.

Confidentiality: The obligation to prevent unauthorized disclosure of information.

Cybersecurity: Protection of information systems and data against unauthorized or harmful activity.

CIA triad: Confidentiality, integrity, and availability objectives of information security.

Least privilege: Providing users only the access necessary for their authorized tasks.

Multi-factor authentication: Authentication requiring two or more independent evidence factors.

Encryption: Converting readable data into protected form using a cryptographic key.

Incident response: Coordinated detection, containment, investigation, recovery, and learning after a security event.

Copyright: Protection for original expression fixed in an appropriate form.

License: Permission to use protected material under stated conditions.

Patent: A territorial legal right concerning a qualifying invention.

Trade secret: Valuable confidential information protected through reasonable secrecy measures.

Trademark: A sign that distinguishes the goods or services of one party from another.

Database right: A right, recognized in some jurisdictions, protecting substantial investment in a database.

Data protection impact assessment: A structured evaluation of high-risk processing and mitigating controls.

Review Questions

Short Answer Questions

1. Why is pseudonymization not equivalent to anonymization?

2. Explain the relationship between privacy, confidentiality, and cybersecurity.

3. What are the three elements of the CIA triad?

4. Why should intellectual-property ownership be discussed at the beginning of a research project?

5. What is the purpose of a data protection impact assessment?

Long Answer Questions

1. Explain how privacy-by-design and data minimization can be applied to a doctoral research project involving employee data.

2. Discuss the technical and organizational controls required for responsible access to sensitive research data.

3. Compare copyright, patents, trade secrets, and licenses in terms of subject matter, protection, and managerial relevance.

4. Describe a complete incident-response process and explain why post-incident learning is important.

5. Critically evaluate the claim that legal compliance is sufficient for ethical information governance.

Analytical / Application Questions

1. A researcher removes names from a dataset but retains exact dates, rare occupations, locations, and free-text comments. Assess the re-identification risk and propose a revised design.

2. A company wants to upload confidential interview transcripts to a public generative-AI tool for thematic analysis. Analyze the privacy, cybersecurity, confidentiality, and IP issues and recommend safeguards.

3. A university and a software firm jointly develop a predictive model using university-collected data. Develop a governance plan addressing access, licensing, publication, ownership, bias testing, retention, and incident response.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes pseudonymization from anonymization?

A. Pseudonymization permanently destroys all identifying information.

B. Anonymization always requires encryption, while pseudonymization does not.

C. Pseudonymization retains a protected possibility of re-identification, whereas anonymization seeks to prevent reasonable identification.

D. There is no meaningful distinction between the two concepts.

Correct Answer: C. Pseudonymization retains a protected possibility of re-identification, whereas anonymization seeks to prevent reasonable identification.

Question 2

A research team collects precise home addresses even though neighborhood-level location is sufficient for its research question. Which principle is most directly violated?

A. Data minimization

B. Separation of duties

C. Patent novelty

D. Trademark protection

Correct Answer: A. Data minimization

Question 3

Which control most directly reflects the principle of least privilege?

A. Giving every employee access to the complete research database

B. Giving users only the permissions required for their current responsibilities

C. Allowing users to share one administrator account

D. Retaining access indefinitely after a project ends

Correct Answer: B. Giving users only the permissions required for their current responsibilities

Question 4

Which situation is the clearest example of a confidentiality breach?

A. A database is unavailable because of a power failure

B. A researcher publishes an original diagram with proper attribution

C. An employee sends identifiable participant records to an unauthorized recipient

D. A company renews a software license

Correct Answer: C. An employee sends identifiable participant records to an unauthorized recipient

Question 5

Why is encryption alone insufficient as a complete privacy control?

A. Encryption cannot protect data in transit.

B. Authorized users with decryption access may still misuse the information.

C. Encryption automatically makes data public.

D. Encryption prevents all forms of data minimization.

Correct Answer: B. Authorized users with decryption access may still misuse the information.

Question 6

A vendor requests a complete dataset for a purpose unrelated to the purpose explained to participants. Which issue should be examined first?

A. Purpose limitation and compatibility of secondary use

B. Whether the dataset has a trademark

C. Whether the organization owns a patent

D. Whether the vendor uses a graphical interface

Correct Answer: A. Purpose limitation and compatibility of secondary use

Question 7

Which form of intellectual property most directly concerns original software code as expressive content?

A. Copyright

B. Patent in every circumstance

C. Trademark

D. Database right only

Correct Answer: A. Copyright

Question 8

What is the most appropriate initial response after discovering unauthorized access to sensitive research data?

A. Delete all logs immediately

B. Ignore the event unless the media learns about it

C. Preserve evidence, assess the incident, and begin containment under the response plan

D. Publish the entire dataset to demonstrate transparency

Correct Answer: C. Preserve evidence, assess the incident, and begin containment under the response plan

Question 9

A valuable algorithm is not publicly disclosed and is protected through restricted access and confidentiality agreements. Which protection may be most relevant?

A. Trade secret

B. Trademark exclusively

C. Copyright in the underlying business idea

D. Public-domain status

Correct Answer: A. Trade secret

Question 10

Why should a project assess re-identification risk after combining a pseudonymized dataset with public data?

A. Combining datasets always removes statistical validity.

B. External information may make individuals identifiable despite removal of names.

C. Public data automatically becomes copyrighted.

D. Pseudonymized data cannot legally be analyzed.

Correct Answer: B. External information may make individuals identifiable despite removal of names.

Research Ethics & Computer Applications
Chapter 8 of 15

Research Ethics & Computer Applications

Chapter 9
Digital Research Environments and Reproducible Workflows

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

9. Digital Research Environments and Reproducible Workflows

Introduction and Context

Doctoral research increasingly takes place in digital environments rather than in a single office, laboratory, or archive. A business researcher may collect survey responses through a web platform, conduct interviews through video conferencing, store documents in cloud repositories, analyse data with statistical software, write code in a collaborative development environment, and share findings with supervisors and co-researchers across several institutions. These arrangements create substantial opportunities for efficiency and collaboration, but they also create a central methodological and ethical obligation: the research process must remain understandable, secure, auditable, and reproducible.

Reproducibility does not mean that every researcher will obtain identical results under all circumstances. It means that the evidence, decisions, data transformations, analytical procedures, and computational conditions are documented sufficiently for an appropriately qualified researcher to inspect the work and, where access is permitted, repeat or extend it. Reproducibility therefore connects technical practice with research integrity. A result that cannot be traced to its source data and analytical decisions is difficult to evaluate, regardless of how sophisticated the final report appears.

This chapter examines the digital infrastructure of responsible doctoral research. It focuses on operating systems, cloud platforms, collaborative workspaces, version control, electronic research notebooks, scripting, containers, security, governance, and practical workflow design. The central argument is that reproducibility is not a software feature added at the end of a project. It is an architectural property of the entire research process, created through deliberate decisions about people, tools, data, documentation, access, and accountability.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain reproducibility, repeatability, provenance, auditability, and computational transparency in doctoral research.

2. Design a secure digital research environment using appropriate operating-system, cloud, collaboration, and storage practices.

3. Apply version control and electronic notebooks to preserve the history of research decisions.

4. Use scripts and containers to make data preparation and analysis more consistent and portable.

5. Evaluate ethical, legal, governance, and security risks in digitally enabled research.

6. Develop a practical workflow that supports collaboration, verification, preservation, and responsible sharing.

From Files and Folders to Research Systems

A digital research environment is the combination of hardware, operating systems, software, storage services, networks, identities, permissions, and human procedures used to conduct research. It should be understood as a socio-technical system. Technical controls alone cannot prevent poor documentation, and good intentions cannot compensate for insecure systems or uncontrolled file duplication.

The operating system is the foundational layer. It manages files, processes, users, permissions, installed applications, and connections to external devices. Researchers should maintain supported versions, apply security updates, use separate user accounts where appropriate, and avoid conducting sensitive work on unmanaged or publicly accessible computers. File paths, character encoding, time zones, and software dependencies can affect whether a workflow behaves consistently across Windows, macOS, and Linux environments. A well-designed project should therefore avoid hidden dependence on one researcher’s personal computer.

A useful project directory separates original material from derived outputs. For example, a project might contain folders for documentation, raw data, processed data, scripts, notebooks, results, manuscripts, and administrative records. The exact structure may differ by discipline, but the principle is stable: raw evidence should be protected from accidental alteration; generated files should be distinguishable from source files; and temporary materials should not be confused with authoritative records.

Cloud platforms extend storage and collaboration beyond local devices. They can provide synchronized files, identity management, automated backup, access logs, and controlled sharing. However, cloud storage is not automatically secure or ethically appropriate. The researcher must consider the location of data centres, contractual terms, subcontractors, encryption, retention policies, institutional approval, and whether the platform is permitted for confidential or personally identifiable information. A cloud folder that is convenient for collaboration may be unsuitable for interview recordings or identifiable employee data.

The distinction between synchronization, backup, and preservation is important. Synchronization makes files available across devices but may also synchronize deletion or corruption. Backup creates recoverable copies, ideally with different failure conditions from the original. Preservation is a longer-term activity involving stable formats, documented metadata, integrity checks, and a defined retention period. A single cloud folder should not be treated as all three.

Conceptual Foundations of Reproducible Research

Several related concepts are frequently used together but should not be treated as synonyms.

Repeatability generally refers to obtaining consistent results when the same researcher uses the same data, methods, and computational environment. Reproducibility often refers to another researcher obtaining the same or sufficiently comparable results using the documented materials and procedures. Replicability is commonly used for conducting a new study addressing the same research question, possibly with new data, to assess whether the finding persists. Terminology varies across disciplines, so doctoral researchers should define how they use these terms in a thesis or protocol.

Provenance is the history of an item: where data came from, who handled it, which transformations were applied, and which outputs were produced. Auditability is the ability of an authorized reviewer to inspect that history and assess whether procedures were appropriate. Traceability links a claim or result back through analytical outputs, code, processed data, and source evidence. Computational transparency concerns the disclosure of relevant code, software, parameters, dependencies, and computational decisions.

A reproducible workflow can be represented as a chain:

research question → protocol → source data → controlled transformation → analysis → output → interpretation → preserved record.

At each link, the researcher should be able to answer four questions: What was done? Why was it done? Who did it? Which version of the relevant material was used? This approach supports both epistemic quality and research governance. It also reduces the risk that undocumented convenience decisions—such as excluding observations, changing a coding rule, or rerunning an analysis until a preferred result appears—become invisible.

Reproducibility has limits. Confidentiality obligations may prevent public release of data. Commercial datasets may be licensed rather than shareable. Software may become unavailable, and some qualitative interpretations cannot be reduced to a fully executable script. In such cases, the goal is not indiscriminate openness but proportionate transparency: share what can ethically and legally be shared, provide synthetic or de-identified alternatives where feasible, and document what cannot be released and why.

A Layered Workflow Architecture

A robust doctoral workflow can be designed in layers.

The identity and access layer establishes who may enter the environment and what each person may do. Institutional accounts, multi-factor authentication, role-based access, and timely removal of former team members are essential. Shared passwords weaken accountability because actions cannot be reliably attributed to individuals.

The data layer distinguishes raw, sensitive, processed, and public data. Raw files should normally be read-only or access-restricted. Personally identifiable information should be separated from analytical data through coding or pseudonymization, with the re-identification key stored independently and securely. Public data should still be checked for licensing and embedded personal information.

The code and configuration layer contains scripts, queries, analysis programs, dependency specifications, and configuration files. Code should not rely on undocumented manual actions. If a researcher must click through a graphical application, the procedure, settings, filters, and export options should be recorded.

The documentation layer includes the study protocol, data dictionary, codebook, decision log, ethical approvals, deviation records, README files, and notebook entries. Documentation is not merely administrative. It is part of the evidential basis of the research.

The collaboration layer regulates review, discussion, task assignment, and contributions. A collaborative workspace should make it clear which document is authoritative, which tasks are pending, and which decisions have been approved. Chat messages may support coordination, but important methodological decisions should be transferred to a durable project record.

The preservation and dissemination layer addresses archiving, citation, access conditions, licensing, and publication. A repository record should identify the study, versions, creators, dates, methods, restrictions, and relationships between data, code, and publications.

This layered view prevents a common mistake: attempting to solve a governance problem with a single tool. Version control cannot replace ethical approval; encryption cannot replace a data-management plan; and a notebook cannot compensate for uncontrolled access.

Version Control as a Record of Intellectual Decisions

Version control systems record changes to files over time. Although they are strongly associated with software development, they are also valuable for research protocols, survey instruments, qualitative coding schemes, statistical scripts, figures, and manuscripts. A version-control repository permits researchers to identify what changed, when it changed, who made the change, and often why it changed.

The basic unit is a commit, a recorded set of changes accompanied by a message. A branch provides a separate line of development, allowing an experimental analysis or draft section to be developed without immediately altering the main version. A merge combines changes after review. A tag can identify an important state, such as the version submitted for examination or the code associated with a published article.

Good commit messages are specific and meaningful. “Fix analysis” is weak; “Correct exclusion rule for incomplete responses and update sensitivity table” is stronger. Commits should be reasonably focused so that a reviewer can understand the change. Large collections of unrelated edits reduce interpretability.

Version control does not solve every problem. Binary files, large video recordings, proprietary formats, and confidential data may be unsuitable for ordinary repositories. Sensitive information should not be committed merely because the repository is private. Deleting a file from the current version may not remove it from the repository’s history. Researchers must therefore use approved storage, access controls, and, where needed, specialized large-file or sensitive-data arrangements.

A doctoral team should establish contribution conventions. These may include branch naming, review requirements, authorship expectations, commit standards, issue tracking, and the distinction between exploratory and approved analyses. Such conventions reduce conflict and help demonstrate individual contributions without treating contribution metrics as a complete measure of scholarly value.

Electronic Notebooks and the Memory of the Project

An electronic research notebook is a structured record of activities, observations, decisions, anomalies, and interpretations. It may be implemented through a laboratory notebook platform, a version-controlled text system, a database, or an institutional application. Its value lies less in the specific software than in the quality and continuity of the record.

A useful notebook entry identifies the date, researcher, objective, materials or data used, procedure, result, interpretation, and next action. It should record deviations from the protocol, failed attempts, unexpected observations, and reasons for changing an analytical decision. Negative or inconclusive work is often methodologically important because it prevents later researchers from repeating unproductive paths and reveals whether the final analysis was selected retrospectively.

Notebook entries should be attributable and protected against silent alteration. Where appropriate, systems should provide timestamps, access logs, immutable versions, or electronic signatures. A notebook is not a private diary if it forms part of the official research record; access must be governed by the research team’s roles and by confidentiality requirements.

For qualitative research, electronic notebooks can connect interview identifiers, coding decisions, analytic memos, reflexive observations, and theme development. For quantitative research, they can record model specifications, variable construction, diagnostic results, and sensitivity analyses. In both cases, the notebook should distinguish observation from interpretation. This distinction supports reflexivity and reduces the risk of presenting an evolving judgment as if it had been predetermined.

Scripting, Automation, and Containers

Scripting transforms a sequence of manual operations into an explicit, inspectable procedure. A script may import data, validate fields, recode variables, generate descriptive statistics, estimate models, create figures, and export tables. Automation improves consistency and reduces transcription errors, but it can also reproduce an error at scale. Every automated process therefore requires validation, test data, checks, and human review.

Scripts should be modular, readable, and parameterized. File locations, dates, thresholds, and inclusion criteria should be visible rather than hidden in scattered commands. A data dictionary should explain variable names, units, missing-value codes, and transformations. Where randomization is used, the seed and relevant random-number settings should be recorded. Outputs should carry sufficient labels to identify the data and code version that produced them.

Dependencies are a major threat to reproducibility. A script may rely on a particular programming language version, package release, operating-system library, database driver, or external API. Dependency files can record required packages and versions, but they do not guarantee that the entire environment can be recreated indefinitely. Researchers should preserve environment specifications alongside the code and document the platform used.

Containers address this problem by packaging code, dependencies, and configuration into a portable execution environment. A container image may allow a workflow to run consistently on a laptop, institutional server, or cloud service. However, containers are not virtual machines and do not eliminate all environmental differences. They may contain security vulnerabilities, fail to preserve external data or credentials, and create large preservation burdens. Images should be built from trusted sources, scanned, versioned, and accompanied by instructions. Secrets must never be embedded in an image.

A practical workflow might use a script to create a cleaned analytical dataset, a notebook to explain the analysis and display outputs, a dependency file to specify software requirements, and a container to package the executable environment. The division of roles is important: notebooks support narrative exploration and communication, whereas scripts are often better for stable, repeatable processing.

Security, Ethics, and Governance

Digital research ethics extends beyond informed consent. It includes the confidentiality, integrity, availability, and appropriate use of information. Confidentiality protects data from unauthorized disclosure; integrity protects it from unauthorized or accidental alteration; availability ensures that authorized researchers can access it when needed.

Data minimization is a foundational principle. Researchers should collect and retain only what is necessary for the stated purpose, subject to legitimate scholarly and legal requirements. Pseudonymization reduces direct identification but does not make data anonymous if combinations of attributes can identify individuals. De-identification must therefore be assessed in relation to the research context, available auxiliary data, and likely attackers.

Access should follow the least-privilege principle: a person receives only the permissions necessary for assigned work. Sensitive data should be encrypted in transit and at rest where appropriate. Multi-factor authentication, secure password management, device encryption, patching, malware protection, and tested recovery procedures should be routine. Personal devices and consumer applications require special scrutiny when research data are confidential.

Ethical approval and data-management planning should occur before collection, not after a dataset has been uploaded to a convenient platform. If the research design changes—for example, if identifiable data are moved to a new provider or shared with a new collaborator—the researcher may need to consult the ethics committee, data-protection officer, sponsor, or institutional information-security team.

Governance also concerns intellectual property, licensing, authorship, participant expectations, and institutional ownership. Open science is not equivalent to unrestricted disclosure. Responsible sharing may involve controlled-access repositories, delayed release, aggregate results, synthetic data, code without raw data, or secure analysis enclaves. The appropriate choice depends on risk, consent, law, contractual obligations, and scientific value.

An Illustrative Case: The Meridian Workforce Study

Background

The Meridian Workforce Study is an illustrative doctoral project examining whether flexible working arrangements influence employee retention in medium-sized service firms. The researcher collects survey responses, conducts interviews with managers, and receives organizational records containing coded employee identifiers.

Situation and Problem

Initially, the researcher stores survey exports on a personal laptop, interview recordings in a consumer synchronization folder, and analysis spreadsheets in an email attachment shared with a supervisor. Several versions of the questionnaire circulate. A colleague manually edits a spreadsheet to correct missing values, but the change is not recorded. When the researcher prepares the thesis, the final regression results cannot be linked confidently to a particular cleaning procedure. The organization is concerned that the combination of job title, location, and tenure could identify participants.

Analysis

The problem is not simply disorganized files. The project lacks provenance, access governance, separation of identifiers, version history, and a reproducible analytical path. The convenience of the existing tools has created ethical and methodological exposure. The team also discovers that the consent form describes institutional research storage but does not clearly authorize transfer to an external consumer platform.

Approach and Solution

The research team redesigns the environment. Identifiers are stored separately from survey and interview data in an approved encrypted repository. Each participant receives a study code, and the linking key is restricted to the principal researcher. Raw exports are preserved as read-only files. A version-controlled repository stores the questionnaire, codebook, data-cleaning scripts, analysis scripts, documentation, and thesis figures, while restricted data remain outside the code repository.

The team creates a data dictionary and a decision log. Every transformation is performed through a documented script, including rules for missing responses and construction of retention measures. A secure electronic notebook records interviews, protocol deviations, analytical decisions, and sensitivity analyses. Access is assigned by role, multi-factor authentication is enabled, and former project members are removed promptly. The final workflow is packaged with a dependency specification and a container for the non-sensitive computational components. Because the organizational records cannot be openly shared, the team prepares synthetic demonstration data and a detailed access statement.

Outcome

The researcher can reproduce the reported tables from the preserved analytical dataset and scripts. The supervisor can inspect changes and review methodological decisions. The organization receives a clearer account of confidentiality safeguards, and the thesis transparently explains which materials are restricted and why. The workflow does not make the project risk-free, but it makes responsibilities, limitations, and evidence substantially more visible.

Learning Points

The case demonstrates that reproducibility is designed across the whole lifecycle. Separation of identifiers protects participants; version control protects the history of decisions; scripts reduce undocumented manual intervention; notebooks preserve reasoning; and governance determines what may be shared. No single platform provides all these functions.

Common Failure Modes and Critical Limitations

Researchers often begin with tools rather than requirements. Selecting a popular platform before classifying the data may lead to unsuitable storage or contractual problems. Another frequent mistake is treating a private repository as automatically confidential, or assuming that a backup is valid without testing restoration.

Manual spreadsheet editing is particularly risky when formulas, filters, hidden rows, and copied values are not documented. File names such as “final,” “final2,” and “final_revised” provide little reliable history. Conversely, excessive technical complexity can also damage a project. A small study may not need an elaborate container orchestration system; unnecessary infrastructure can consume time and create new security weaknesses.

Reproducibility may be limited by changing software, unavailable proprietary tools, undocumented institutional systems, inaccessible data, and the interpretive nature of some research. A workflow can be technically repeatable yet conceptually weak if the measures are invalid or the sampling strategy is biased. Reproducible computation is therefore not a substitute for sound research design, critical reasoning, or ethical judgment.

Automation introduces another danger: false confidence. A successful script execution does not prove that the code is correct. Researchers should use validation rules, plausibility checks, independent review, test cases, and sensitivity analyses. They should also record exceptions rather than silently forcing problematic data into a predetermined structure.

Emerging Directions

Research environments are moving toward integrated platforms that connect data catalogues, workflow engines, repositories, notebooks, identity systems, and computational resources. Research software engineering practices are becoming more common in social science and business research, particularly where projects involve large datasets or repeated analyses. Provenance standards and machine-readable metadata may improve the connection between datasets, code, publications, and institutional records.

Artificial intelligence introduces both opportunities and governance challenges. AI tools can assist with code suggestions, data classification, documentation, transcription, and workflow monitoring. Yet researchers must assess confidentiality, model training practices, hallucinated code, hidden bias, intellectual-property conditions, and the absence of stable versioning. AI-assisted work should be recorded sufficiently to identify the tool, purpose, input restrictions, human review, and resulting changes. Sensitive research data should not be entered into an external AI service without explicit authorization.

The future of reproducible research is therefore unlikely to depend on one universal tool. It will depend on interoperable systems, clear institutional policies, skilled researchers, and a culture that values transparent process as much as polished output.

Best-Practice Design Principles

A doctoral researcher can use the following principles when designing a workflow:

  • classify data before selecting tools;
  • separate raw, processed, sensitive, and public materials;
  • use institutional identity and approved storage for confidential work;
  • preserve original data and automate transformations where feasible;
  • record code, dependencies, parameters, decisions, and deviations;
  • use version control for text, code, protocols, and structured project files;
  • keep identifiers and re-identification keys separate from analytical data;
  • test backups and document restoration procedures;
  • review access permissions throughout the project lifecycle;
  • validate automated outputs and obtain independent review;
  • share code, metadata, synthetic data, or controlled-access materials where open release is impossible;
  • archive a clearly identified version associated with the thesis or publication.

These practices should be proportionate to the study’s sensitivity, complexity, duration, and collaborative structure. The objective is not technological sophistication for its own sake. It is a defensible chain of evidence from research question to claim.

Chapter Summary

Digital research environments are socio-technical systems in which operating systems, cloud platforms, storage, collaboration tools, code, notebooks, and governance procedures interact. Reproducibility requires more than retaining a final dataset: it requires provenance, traceability, documented decisions, controlled transformations, identifiable versions, and an appropriate computational environment.

Version control preserves the history of intellectual and technical change. Electronic notebooks preserve procedures, interpretations, anomalies, and deviations. Scripts make transformations explicit, while dependency specifications and containers improve computational portability. Security requires identity management, least privilege, encryption, data minimization, tested backups, and responsible sharing. Ethical research environments must respect consent, confidentiality, intellectual property, institutional policy, and legal requirements.

The most effective workflow is designed from the beginning, reviewed throughout the project, and preserved at its conclusion. Its success is measured not by the number of tools used but by whether an authorized researcher can understand what was done, why it was done, and how the evidence supports the conclusions.

Key Terms

Auditability: The capacity of an authorized reviewer to inspect research activities, decisions, and records.

Backup: A recoverable copy of data or systems maintained to support restoration after loss or corruption.

Container: A packaged computational environment containing software, dependencies, and configuration needed to run a workflow.

Computational transparency: Disclosure of relevant code, software, parameters, dependencies, and computational decisions.

Data provenance: The documented origin, history, handling, and transformation of data.

Data minimization: Collecting and retaining only data necessary for legitimate research purposes.

Electronic research notebook: A digital record of procedures, observations, decisions, results, and interpretations.

Least privilege: Providing each user only the access necessary to perform assigned responsibilities.

Metadata: Structured information describing the origin, content, format, conditions, and use of a research object.

Pseudonymization: Replacing direct identifiers with codes while retaining a separately protected means of re-identification.

Reproducibility: The ability of another qualified researcher to obtain comparable results using documented materials and procedures.

Replicability: Conducting a new study addressing the same research question, often with new data or settings.

Repeatability: Obtaining consistent results using the same data, methods, and computational conditions.

Repository: A managed location for storing, versioning, preserving, or disseminating research materials.

Script: An executable sequence of instructions that automates a computational or data-processing procedure.

Traceability: The ability to link a reported claim or output back to its data, code, and decisions.

Version control: A system for recording and managing changes to files over time.

Workflow: An ordered set of research activities, tools, decisions, and outputs.

Review Questions

Short Answer Questions

1. Distinguish between synchronization, backup, and preservation.

2. What is the purpose of a data dictionary in a reproducible workflow?

3. Define provenance and explain its relevance to auditability.

4. Why should raw data normally be separated from processed data?

5. What does the least-privilege principle require?

Long Answer Questions

1. Explain how operating systems, cloud platforms, version control, electronic notebooks, scripts, and containers can operate together in a doctoral research workflow.

2. Discuss the ethical and governance issues involved in sharing confidential research data through cloud services.

3. Compare repeatability, reproducibility, and replicability, noting why disciplinary definitions may differ.

4. Evaluate the benefits and limitations of using containers for computational research.

5. Explain why reproducibility should be treated as an architectural property of a project rather than as a final reporting activity.

Analytical / Application Questions

1. A doctoral researcher has survey data, interview recordings, and a spreadsheet containing participant identifiers. Design a secure storage, access, documentation, and analysis workflow for the project.

2. An analysis produces different results after a software-package update. Diagnose the likely causes and propose procedures for restoring and documenting reproducibility.

3. A research team cannot legally release its dataset but wishes to support verification. Recommend a proportionate transparency strategy and justify each component.

22. Multiple Choice Questions with Answers

Question 1

Which practice most directly establishes provenance in a doctoral research project?

A. Saving only the final results table

B. Recording the source, transformations, decisions, and outputs associated with the data

C. Using a popular cloud-storage provider

D. Converting all files to PDF

Correct Answer: B. Recording the source, transformations, decisions, and outputs associated with the data

Question 2

Why should a synchronization folder not be treated as a complete backup strategy?

A. Synchronization cannot store documents

B. Synchronized deletion or corruption may propagate across devices

C. Synchronization always prevents collaboration

D. Cloud platforms cannot preserve file dates

Correct Answer: B. Synchronized deletion or corruption may propagate across devices

Question 3

Which version-control practice best supports auditability?

A. Using vague messages such as “update”

B. Deleting earlier versions after each revision

C. Making focused commits with specific explanatory messages

D. Sharing one password among all collaborators

Correct Answer: C. Making focused commits with specific explanatory messages

Question 4

A researcher must protect the link between participant codes and identities. What is the most appropriate arrangement?

A. Store the linking key in the same public repository as the analysis

B. Include names in every analytical file for convenience

C. Store the linking key separately with restricted access

D. Email the key to all project members

Correct Answer: C. Store the linking key separately with restricted access

Question 5

What is the principal function of an electronic research notebook?

A. To replace ethical approval

B. To preserve procedures, decisions, observations, and interpretations over time

C. To guarantee that an analysis is statistically valid

D. To eliminate the need for data security

Correct Answer: B. To preserve procedures, decisions, observations, and interpretations over time

Question 6

Which statement best describes a container?

A. A legal agreement governing data ownership

B. A packaged computational environment containing software and dependencies

C. A backup device for interview recordings

D. A substitute for informed consent

Correct Answer: B. A packaged computational environment containing software and dependencies

Question 7

A script runs successfully but produces implausible values. What should the researcher do first?

A. Assume the output is correct because execution completed

B. Delete the source data

C. Apply validation checks and inspect the transformation logic

D. Publish the results before they change

Correct Answer: C. Apply validation checks and inspect the transformation logic

Question 8

Which principle requires a user to receive only the permissions necessary for assigned work?

A. Open access

B. Least privilege

C. Data saturation

D. Containerization

Correct Answer: B. Least privilege

Question 9

A dataset cannot be publicly released because it contains identifiable employee information. Which response best reflects proportionate transparency?

A. Release the identifiable dataset without restriction

B. Release nothing and provide no explanation

C. Share code, metadata, synthetic data, and a justified controlled-access statement

D. Remove the methodology from the thesis

Correct Answer: C. Share code, metadata, synthetic data, and a justified controlled-access statement

Question 10

Why is reproducibility not a substitute for sound research design?

A. Reproducible workflows cannot use software

B. A flawed design can be executed consistently and still produce invalid conclusions

C. Reproducibility applies only to laboratory science

D. Sound research design prevents all data-security risks

Correct Answer: B. A flawed design can be executed consistently and still produce invalid conclusions

Research Ethics & Computer Applications
Chapter 9 of 15

Research Ethics & Computer Applications

Chapter 10
Digital Literature Review and Knowledge Management

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

10. Digital Literature Review and Knowledge Management

Introduction and Context

A doctoral literature review is not a catalogue of articles. It is a reasoned account of what is known, how knowledge has been produced, where evidence converges or conflicts, and what remains insufficiently explained. Digital technologies have transformed this activity. Scholarly databases, citation indexes, reference managers, screening platforms, text-mining tools, and generative artificial intelligence now enable researchers to locate and organize evidence at a scale that was previously impractical.

Greater technical capacity, however, does not automatically produce better scholarship. Search algorithms privilege some records over others; database coverage varies by discipline, language, geography, and publication type; citation counts reflect social and institutional advantages as well as intellectual influence; and automated classification can reproduce the assumptions embedded in training data. Digital literature review is therefore both a methodological and an ethical practice. The researcher must be able to design a transparent search, evaluate the credibility of sources, preserve an auditable research record, protect data and intellectual property, and make defensible judgments about inclusion and interpretation.

Knowledge management provides the organizing perspective for these activities. It concerns the creation, acquisition, organization, sharing, retention, and responsible use of knowledge. In doctoral research, a literature-management system converts dispersed documents into a structured scholarly knowledge base containing references, annotations, concepts, methodological details, evidence judgments, and links among ideas. This chapter explains how to construct such a system and how to recognize its limitations.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish narrative, systematic, scoping, integrative, and bibliometric literature reviews.

2. Construct reproducible searches using scholarly databases and controlled search logic.

3. Apply reference management, screening, coding, note-taking, and evidence-mapping techniques.

4. Critically evaluate source credibility, research quality, and predatory publishing indicators.

5. Explain how algorithmic ranking and database coverage can bias a literature review.

6. Use digital tools ethically, securely, and transparently in doctoral research.

7. Design a defensible workflow for synthesizing literature into a research argument.

From Document Collection to Knowledge Architecture

A literature review has at least four intellectual tasks. First, it maps the field by identifying concepts, debates, methods, populations, and influential contributions. Second, it evaluates evidence rather than treating every publication as equally reliable. Third, it synthesizes findings into patterns, contradictions, and explanatory relationships. Fourth, it establishes the position and contribution of the proposed study.

These tasks require more than downloading papers. A folder of PDFs is a document store, not a knowledge-management system. A research knowledge base gives each source a place within an analytical structure. It records what a source claims, how it supports the claim, what methods it uses, what limitations it acknowledges, and how it relates to other sources. The unit of analysis may be an article, a construct, a finding, a sample, a method, or a theoretical proposition.

The distinction between explicit and tacit knowledge is useful here. Explicit knowledge can be recorded in a database—for example, a citation, sample size, measure, or reported effect. Tacit knowledge includes the researcher's developing judgment: why one definition is more coherent, why a result may not transfer to another setting, or why two apparently similar studies are conceptually different. Digital tools can support tacit knowledge through reflective memos, but they cannot replace scholarly judgment.

Important terminology includes the following:

  • Search string: A structured combination of keywords, phrases, Boolean operators, truncation symbols, and field restrictions.
  • Boolean operator: A logical connector such as AND, OR, or NOT used to combine search terms.
  • Controlled vocabulary: Standardized database terms assigned to subjects or concepts.
  • Search sensitivity: The ability of a search to retrieve relevant records, closely related to recall.
  • Search specificity: The ability to exclude irrelevant records, closely related to precision.
  • Deduplication: The identification and removal of multiple records representing the same work.
  • Screening: The process of judging records against predefined eligibility criteria.
  • Coding: The systematic assignment of labels or values to features of a source or finding.
  • Evidence map: A structured visual or tabular representation of available evidence across concepts, methods, populations, or outcomes.
  • Bibliographic coupling: A relationship between documents that cite some of the same sources.
  • Co-citation: A relationship in which two documents are cited together by later publications.
  • Co-word analysis: Examination of terms that appear together to identify themes or conceptual clusters.
  • Grey literature: Research and evidence produced outside conventional commercial or scholarly publishing channels.
  • Metadata: Descriptive information about a publication, such as author, title, date, abstract, keywords, and identifier.
  • Provenance: A record of the origin, transformation, and handling of data or evidence.
  • Predatory publishing: Publishing activity that presents itself as legitimate scholarship while failing to provide expected editorial, peer-review, transparency, or publishing services, often using deceptive practices.
  • Algorithmic bias: Systematic distortion arising from data, rules, ranking mechanisms, or design choices in an automated system.

Choosing a Review Design

The review question should determine the design. A narrative review is appropriate when the purpose is conceptual interpretation, theoretical critique, or historical development. It permits flexible searching but requires the author to explain selection and interpretation clearly. A systematic review uses an explicit question, predefined eligibility criteria, documented searching, and a reproducible selection process. It is particularly useful for aggregating evidence about a focused relationship or intervention.

A scoping review is suitable when a field is broad, heterogeneous, emerging, or conceptually fragmented. It maps the range and characteristics of evidence without necessarily estimating a pooled effect. An integrative review combines empirical and theoretical literature to develop a new conceptual understanding. A bibliometric review examines publication patterns, citation structures, collaboration networks, and thematic development. Bibliometrics can reveal the architecture and evolution of a field, but citation prominence should not be confused with research quality.

These designs can be combined. For example, a doctoral researcher may conduct a systematic search, use bibliometric mapping to identify clusters, and then perform qualitative coding of a purposive set of studies. The design must remain coherent: the methods used to find and analyze literature should correspond to the research question.

Designing a Defensible Digital Search

A rigorous search begins with a conceptual question rather than a database. The researcher defines the phenomenon, context, population or organizational setting, and relevant outcomes or relationships. Frameworks such as PICO, PICo, SPIDER, or a purpose-built conceptual model can help structure the question, but they should not be used mechanically in qualitative or theoretical research.

Search terms should include synonyms, spelling variants, abbreviations, related constructs, and alternate terminology used by different disciplines. A search block might be constructed as follows:

`("remote work" OR telework OR telecommut OR "virtual work") AND (productiv OR performance OR effectiveness) AND (manager OR supervisor OR leadership)`

Quotation marks search an exact phrase; the asterisk commonly retrieves word variants, although database syntax differs. OR broadens a concept through synonyms, while AND requires the presence of multiple concepts. NOT should be used cautiously because it can remove relevant records containing an unwanted term in a legitimate context.

A search should normally be tested iteratively. The researcher begins with several known relevant articles, often called sentinel or seed articles, and checks whether the search retrieves them. Missing a seed article may indicate inadequate terminology, a database limitation, or an inappropriate field restriction. The researcher then examines subject headings, author keywords, abstracts, and reference lists to refine the strategy. This process should be recorded rather than performed invisibly.

Database selection is consequential. Multidisciplinary citation indexes may provide broad coverage and citation links, while subject databases offer richer indexing in particular fields. Library catalogues, institutional repositories, dissertation databases, working-paper archives, and government sources can reduce publication and language bias. No single database represents the whole scholarly record. Search logs should record the platform, date, exact string, fields searched, filters, number of results, and any changes made.

A transparent workflow distinguishes discovery from evidence selection. General web search, recommendation systems, and citation chaining are useful for discovering terminology and sources. They should not silently replace the formal search. Backward citation searching examines references cited by an eligible article; forward citation searching examines later works that cite it. Author searching and journal searching can identify relevant streams, but they may amplify established networks and overlook less visible scholars.

Reference Management and the Research Record

Reference-management software can import metadata, store files, generate citations, and synchronize libraries. Its value depends on disciplined use. Each record should be checked against the original publication because imported metadata may contain incorrect authors, dates, titles, page numbers, or document types. Persistent identifiers such as DOI, ORCID, and repository handles assist verification but do not prove quality.

A practical library may use collections for broad topics and tags for analytical dimensions. For example, collections may separate discovery, included studies, background theory, and excluded records, while tags identify method, sector, geography, theory, or evidence direction. Notes should distinguish quotation, paraphrase, researcher interpretation, and unresolved question. Exact quotations require page or location information; otherwise later writing risks accidental plagiarism or inaccurate attribution.

A researcher's knowledge base should also contain a decision log. It may record why a term was added, why a study was excluded, how a duplicate was resolved, or why two constructs were treated as distinct. Such records support dependability and make supervisory discussion more productive. Versioned files, dated exports, and backups protect against data loss. Sensitive notes should not be stored in unsecured consumer platforms, particularly when they contain confidential manuscripts, interview information, or licensed material.

Screening, Coding, and Evidence Mapping

Screening generally proceeds in stages: removal of duplicates, title and abstract screening, full-text assessment, and final inclusion. Eligibility criteria should be established before screening begins, although legitimate refinement may occur when the initial criteria prove conceptually inadequate. Any refinement must be documented and applied consistently.

For collaborative reviews, reviewers can independently screen a sample of records and compare disagreements. Agreement statistics may be informative, but a numerical agreement score does not resolve conceptual ambiguity. Disagreements should be discussed, criteria clarified, and decisions documented. Automation may prioritize records or suggest classifications, but final inclusion decisions require accountable human review, particularly when the evidence is heterogeneous or the consequences of exclusion are significant.

Coding can be deductive, inductive, or hybrid. A deductive codebook derives categories from the research question or theory. An inductive codebook develops categories from the material. A hybrid approach begins with provisional categories and permits new concepts to emerge. A useful evidence-extraction table may include citation, research purpose, theoretical lens, setting, sample, design, measures, principal findings, limitations, author claims, researcher assessment, and relevance to the research question.

Evidence maps make patterns visible. A matrix can place theories in rows and organizational contexts in columns, with cells indicating the number and type of studies. A second matrix can distinguish positive, null, contradictory, and conditional findings. Network maps can display co-authorship, co-citation, or keyword relationships. Visualizations are exploratory devices, not substitutes for interpretation. Clusters are mathematical or algorithmic groupings; their meaning must be established by reading the underlying publications.

Bibliometric Reasoning and Its Limits

Bibliometric analysis uses publication and citation data to study the structure and development of knowledge. Descriptive indicators include publication counts, citation counts, sources, countries, institutions, and collaboration patterns. Relational techniques include co-authorship analysis, co-citation analysis, bibliographic coupling, and co-word analysis. Overlay visualizations may show how themes change across time.

Interpretation requires caution. Citation counts vary by field, publication age, document type, language, and database coverage. A highly cited article may be foundational, controversial, methodologically convenient to cite, or simply old. A recent or locally published study may be important but under-cited. Self-citation, citation cartels, strategic citation, and unequal access to publishing can influence indicators. Normalization and multiple indicators improve interpretation, but no metric eliminates judgment.

Bibliometric data also carry classification assumptions. A database may index journals more comprehensively in some regions or disciplines than others. Name disambiguation may incorrectly merge researchers or split one author into several identities. Missing abstracts and inconsistent keywords affect thematic analysis. Researchers should report the database, retrieval date, cleaning rules, thresholds, software, and analytic decisions. Reproducible scripts and preserved datasets are desirable where licensing permits.

Evaluating Credibility and Recognizing Predatory Publishing

Credibility is multidimensional. The researcher should examine the authority and expertise of authors, the transparency of methods, the fit between claims and evidence, the quality of peer review, the integrity of data and reporting, the publisher's practices, and the relevance of the source to the question. A prestigious journal is not a guarantee of truth, and an unfamiliar journal is not automatically unreliable.

Potential warning signs of deceptive or predatory publishing include unsolicited flattering invitations, false claims about indexing or impact factors, unclear editorial boards, implausibly rapid peer review, hidden fees, poor contact information, copied journal websites, vague peer-review policies, and a mismatch between journal scope and article content. These are indicators for investigation, not a mechanical blacklist. Researchers should verify claims through recognized indexing services, publisher policies, journal archives, editorial information, and library guidance. They should also consider legitimate open-access journals that charge article-processing fees transparently and provide genuine editorial services.

Quality appraisal tools should be selected according to study design. A qualitative study should not be judged by criteria designed for a randomized experiment, and a conceptual article should not be penalized for lacking a statistical sample. Critical appraisal asks whether the design can support the claim, whether limitations are acknowledged, whether analysis is traceable, and whether conclusions exceed the evidence.

Algorithmic Search Bias and Responsible Use of AI

Search engines and scholarly platforms rank records using relevance signals, citations, popularity, personalization, metadata quality, and commercial or platform-specific objectives. Ranking affects visibility. A highly ranked result is not necessarily the most rigorous, and a low-ranked result is not necessarily irrelevant. Recommendation systems can create a feedback loop: visible articles receive more attention, which generates more citations and further visibility.

Algorithmic bias may arise through incomplete training data, English-language dominance, historical underrepresentation, uneven indexing, opaque ranking rules, and proxy measures such as citation counts. The result can be geographical, disciplinary, gendered, linguistic, or institutional distortion. Mitigation requires searching multiple databases, using varied terminology, including grey literature where appropriate, checking references and citations manually, examining excluded and marginal records, and reporting limitations.

AI tools can assist with metadata cleaning, duplicate detection, translation support, clustering, summarization, and preliminary prioritization. They may also hallucinate references, omit qualifications, confuse correlation with causation, reproduce bias, or expose confidential documents. AI-generated summaries should be checked against the source. The researcher remains responsible for every citation, interpretation, and inclusion decision. Institutional policy, publisher requirements, copyright conditions, and confidentiality obligations must be followed, and substantive AI assistance should be disclosed when required.

An Illustrative Case: Building an Evidence Map of Hybrid Work

Background

A doctoral researcher in organizational behavior is studying how hybrid work affects managerial control and employee performance in medium-sized professional-service firms. The topic uses inconsistent terminology: remote work, telework, distributed work, virtual work, flexible work, and hybrid work. Evidence spans information systems, human resource management, psychology, and operations.

Situation and Problem

An initial web search produces thousands of records, many of which are opinion pieces or unrelated to organizational performance. The researcher also notices that highly cited studies are concentrated in North American and European journals. A simple citation-count approach would overlook regional studies and recent evidence.

Analysis and Approach

The researcher defines a review question covering employees and managers in organizational settings, hybrid or partially remote work, and performance-related outcomes. Four database platforms are searched using three concept blocks: work arrangement, managerial or organizational context, and performance or effectiveness. A supplementary search covers dissertations, public research reports, and backward and forward citations.

The researcher records every search string and date, imports results into reference-management software, verifies metadata, and removes duplicates using both automated matching and manual inspection. Title and abstract screening is followed by full-text assessment against predefined criteria. The extraction form records country, sector, organizational size, research design, level of analysis, performance measure, managerial mechanism, and limitations.

A hybrid codebook begins with autonomy, monitoring, coordination, trust, communication, productivity, and well-being. During full-text reading, boundary management and technological infrastructure emerge as additional codes. An evidence map displays findings by country and mechanism, distinguishing self-reported performance from objective or supervisor-rated performance. Bibliometric mapping is used only to identify intellectual clusters and terminology, not to rank evidence quality.

Outcome

The resulting review shows that findings differ according to job interdependence, managerial practices, measurement method, and the degree of employee autonomy. The researcher avoids claiming that hybrid work has one universal effect. Instead, the doctoral proposal identifies a gap concerning how managerial control mechanisms interact with task interdependence in medium-sized firms.

Learning Points

The case demonstrates that search design is part of theory development. Transparent inclusion rules reduce arbitrary selection, while evidence mapping reveals conditional relationships that a simple narrative of positive or negative effects would conceal. It also illustrates why citation prominence cannot substitute for coverage, appraisal, and interpretation.

Ethical and Governance Responsibilities

Digital review work involves several ethical duties. Researchers must respect copyright and database licence restrictions; access to an article does not always authorize redistribution of its full text. They must preserve accurate attribution, avoid plagiarism, and distinguish their own interpretation from an author's words. If confidential manuscripts or unpublished reports are uploaded to an external tool, confidentiality may be compromised.

Research records should be governed through access controls, secure storage, backup procedures, retention rules, and version history. A protocol should identify who may access full texts, extraction sheets, and screening decisions. Where review data include personal information—for example, author correspondence or unpublished participant-level material—privacy and data-protection requirements apply.

Ethical review is also concerned with fairness. Excluding non-English literature may be justified by resources, but it should be acknowledged as a source of bias. Excluding grey literature can increase publication bias. Automated tools should be audited for differential performance across languages, disciplines, and document types. The central principle is accountability: a digital process must remain explainable enough for another scholar to understand how conclusions were reached.

Common Failures and Better Practice

Weak reviews often begin with an unfocused question, rely on one database, treat search results as evidence, or cite abstracts without reading full texts. Other common errors include failing to remove duplicates, changing eligibility criteria without recording the change, confusing a citation metric with quality, and using AI summaries as substitutes for primary sources.

Better practice is to write a brief protocol, pilot the search, use multiple sources, preserve the search history, verify metadata, maintain a decision log, and connect each major claim to appropriate evidence. The researcher should periodically examine what the search is not finding: non-English studies, older foundational work, dissenting findings, practitioner evidence, or research from less visible institutions. A final audit should ask whether another competent researcher could reproduce the main pathway from question to conclusion.

Current Developments

Research infrastructures are increasingly integrating persistent identifiers, open metadata, machine-readable full texts, automated screening, semantic search, and collaborative review environments. Large language models may improve terminology discovery and assist with preliminary synthesis, while knowledge graphs can represent relationships among authors, concepts, methods, and findings. Open science practices encourage preregistered protocols, open materials, transparent exclusions, and reusable data where legally and ethically possible.

These developments create a tension between efficiency and interpretive responsibility. More automation can accelerate routine processing, but it can also obscure decisions and standardize scholarly judgment prematurely. The future-oriented doctoral researcher therefore needs both computational literacy and methodological skepticism. Tools should be selected because they improve validity, transparency, or efficiency—not because automation is inherently superior.

Chapter Summary

Digital literature review is a structured process of searching, evaluating, organizing, and synthesizing scholarly evidence. A defensible review aligns its design with the research question, uses transparent search strategies, selects multiple appropriate databases, and records its decisions. Reference managers, screening systems, coding frameworks, bibliometric techniques, and evidence maps transform dispersed publications into an analyzable knowledge base.

Bibliometric indicators and algorithmic rankings are useful but partial. Database coverage, citation practices, language, historical visibility, and platform design can bias what researchers see. Source credibility must therefore be assessed through methods, transparency, editorial practice, relevance, and evidence—not through prestige or metrics alone. Ethical practice requires respect for copyright, confidentiality, privacy, attribution, and fair representation. AI may assist with routine tasks, but human researchers remain responsible for interpretation and scholarly claims.

Key Terms

Search string: A structured combination of terms and operators used to retrieve records.

Controlled vocabulary: Standardized indexing terms assigned by a database.

Recall: The proportion of relevant records retrieved by a search.

Precision: The proportion of retrieved records that are relevant.

Deduplication: Removing multiple records representing the same publication.

Screening: Assessing records against stated eligibility criteria.

Coding: Assigning analytical categories to source characteristics or findings.

Evidence map: A structured display of evidence across concepts, settings, or outcomes.

Bibliometrics: Quantitative analysis of publications, citations, and scholarly relationships.

Co-citation: The joint citation of two documents by later publications.

Bibliographic coupling: Similarity between documents based on shared references.

Grey literature: Evidence produced outside conventional commercial scholarly publishing.

Metadata: Descriptive information about a document.

Provenance: The documented origin and transformation history of evidence or data.

Predatory publishing: Deceptive publishing activity that fails to provide expected scholarly services.

Algorithmic bias: Systematic distortion produced by data or automated decision rules.

Knowledge base: An organized collection of linked information, interpretations, and decisions.

Decision log: A dated record explaining methodological choices and changes.

Review Questions

Short Answer Questions

1. What is the difference between search sensitivity and search specificity?

2. Why should imported reference metadata be checked against the original publication?

3. Define bibliographic coupling and distinguish it from co-citation.

4. Identify two warning signs associated with potentially predatory publishing.

5. Why is a decision log useful in a doctoral literature review?

Long Answer Questions

1. Explain how a researcher can design and document a reproducible database search.

2. Compare systematic, scoping, narrative, integrative, and bibliometric reviews.

3. Discuss how reference management, coding, and evidence mapping contribute to knowledge management.

4. Critically evaluate the use of citation counts and other bibliometric indicators in judging research importance.

5. Explain the ethical and governance responsibilities involved in using AI tools for literature review.

Analytical / Application Questions

1. Develop a search strategy for a study of leadership practices and employee well-being in hybrid organizations. Identify concept blocks, synonyms, and likely sources of bias.

2. A database returns mostly highly cited English-language articles from large institutions. Propose a process for assessing and reducing the resulting coverage bias.

3. Design an evidence-extraction table and screening workflow for a review containing quantitative, qualitative, and conceptual studies. Justify the fields and decision rules you would include.

22. Multiple Choice Questions with Answers

Question 1

Which review design is most appropriate when the purpose is to map a broad and heterogeneous field without necessarily estimating a pooled effect?

A. Scoping review

B. Laboratory experiment

C. Narrative citation count

D. Bibliographic coupling

Correct Answer: A. Scoping review

Question 2

A researcher uses OR between several synonyms in one concept block primarily to achieve what effect?

A. Reduce the number of retrieved records

B. Broaden retrieval across related terms

C. Remove duplicate records

D. Restrict results to one database

Correct Answer: B. Broaden retrieval across related terms

Question 3

Which practice most directly improves the reproducibility of a digital literature review?

A. Using only the highest-ranked search results

B. Changing eligibility rules without recording changes

C. Preserving databases, search strings, dates, filters, and decisions

D. Relying on citation counts to select studies

Correct Answer: C. Preserving databases, search strings, dates, filters, and decisions

Question 4

Two documents are related because they cite many of the same earlier sources. What relationship does this illustrate?

A. Co-citation

B. Bibliographic coupling

C. Co-authorship

D. Deduplication

Correct Answer: B. Bibliographic coupling

Question 5

Which statement best reflects responsible interpretation of citation counts?

A. High citation counts prove methodological quality

B. Citation counts are irrelevant in all reviews

C. Citation counts are useful indicators but are affected by field, age, language, and database coverage

D. Recent studies always have higher citation validity

Correct Answer: C. Citation counts are useful indicators but are affected by field, age, language, and database coverage

Question 6

During screening, an AI tool labels a study as irrelevant, but the abstract contains an unfamiliar term describing the target phenomenon. What is the best action?

A. Exclude it automatically because the tool has classified it

B. Read and assess it using the stated eligibility criteria

C. Delete the record to prevent duplicate screening

D. Include every record classified as unfamiliar

Correct Answer: B. Read and assess it using the stated eligibility criteria

Question 7

Which is the strongest reason to maintain a distinction between a document store and a research knowledge base?

A. A knowledge base links claims, methods, interpretations, and decisions

B. A document store always contains fewer publications

C. A knowledge base eliminates the need to read sources

D. A document store cannot contain PDF files

Correct Answer: A. A knowledge base links claims, methods, interpretations, and decisions

Question 8

Which combination most strongly suggests that a journal requires further credibility investigation?

A. Transparent fees, identifiable editors, and archived issues

B. Clear peer-review policy and recognized indexing

C. Unsolicited invitations, unverifiable indexing claims, and implausibly rapid review

D. Open access and a stated copyright policy

Correct Answer: C. Unsolicited invitations, unverifiable indexing claims, and implausibly rapid review

Question 9

A bibliometric map identifies a keyword cluster. What should the researcher do before interpreting the cluster as a meaningful theme?

A. Assume the algorithm has established its meaning

B. Read representative publications and examine the data-cleaning rules

C. Remove all low-citation publications

D. Treat the cluster as evidence of causal influence

Correct Answer: B. Read representative publications and examine the data-cleaning rules

Question 10

Which action best mitigates algorithmic and database visibility bias?

A. Use one platform because its ranking is consistent

B. Search multiple databases, use citation chaining, and inspect marginal or excluded records

C. Select only publications from prestigious institutions

D. Replace scholarly databases with general web search

Correct Answer: B. Search multiple databases, use citation chaining, and inspect marginal or excluded records

Research Ethics & Computer Applications
Chapter 10 of 15

Research Ethics & Computer Applications

Chapter 11
Computer-Assisted Data Collection and Database Management

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

11. Computer-Assisted Data Collection and Database Management

Introduction and Context

Computer-assisted data collection has transformed the way organizations, researchers, public institutions, and firms generate evidence. Surveys can be distributed through web and mobile platforms; experiments can record behavioral responses automatically; application programming interfaces (APIs) can provide machine-readable operational data; web-scraping systems can monitor publicly available information; and sensors can capture continuous observations from physical environments. These developments improve speed, scale, and analytical possibility, but they also introduce important methodological, ethical, and governance problems.

The central issue is not simply whether data can be collected. It is whether the data are collected for a legitimate purpose, from an appropriate population, with adequate consent and security, and whether they remain interpretable and trustworthy when stored, combined, analyzed, and shared. A technically efficient collection system can still produce invalid evidence if its sampling frame is biased, its measures are poorly designed, or its database silently changes the meaning of variables.

Database management is therefore part of research design rather than a purely technical activity. Decisions about identifiers, data types, missing values, access permissions, metadata, and retention affect the credibility and reproducibility of research. In doctoral business research, the researcher must be able to connect substantive theory with operational definitions, digital collection instruments, data architecture, quality control, and responsible use.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Design ethically defensible computer-assisted surveys, experiments, API processes, web-scraping systems, and sensor-based studies.

2. Distinguish validity, reliability, representativeness, completeness, accuracy, and timeliness in digital data.

3. Construct relational and non-relational datasets for research and organizational applications.

4. Develop data dictionaries, validation rules, identifiers, metadata, and quality-control procedures.

5. Use SQL concepts to retrieve, join, aggregate, and audit research data.

6. Explain interoperability, provenance, privacy, security, and governance requirements.

7. Evaluate the effects of automation, artificial intelligence, and emerging technologies on research ethics and data quality.

From Research Question to Digital Evidence

A sound collection process begins with a research question, not with a preferred software platform. A research question should be translated into constructs, observable indicators, units of analysis, sources, and time periods. For example, a study of employee burnout may define the construct theoretically, operationalize it through validated survey items, identify employees as the unit of analysis, and specify how workload, autonomy, absence, and well-being will be measured.

This translation is often represented through an operationalization chain:

Research construct → variable or indicator → collection instrument → stored field → analytical measure.

Weakness at any stage can undermine the final inference. A database may contain millions of records, yet fail to measure the intended construct. Conversely, a small, carefully designed dataset may provide stronger evidence because its definitions, sampling strategy, and provenance are clear.

Several dimensions of data quality should be distinguished:

  • Accuracy: the degree to which a value represents the actual phenomenon.
  • Completeness: the extent to which required records or fields are present.
  • Consistency: the absence of contradictory representations across tables or systems.
  • Validity: the extent to which values conform to permitted definitions and formats.
  • Timeliness: whether data are available at the time required for the research or decision.
  • Uniqueness: whether the same entity or event has been duplicated.
  • Provenance: information about where data originated and how they were transformed.

These dimensions may conflict. Real-time sensor data may be timely but noisy; administrative records may be complete but generated for a purpose unrelated to the research question; scraped data may be extensive but unstable because websites change their structure.

Designing Computer-Assisted Surveys

Computer-assisted surveys include web surveys, mobile questionnaires, computer-assisted telephone interviewing, computer-assisted personal interviewing, and mixed-mode instruments. Their main advantage is programmable control. The system can randomize questions, apply skip logic, prevent impossible entries, issue reminders, and timestamp responses. However, automation does not eliminate design error. It can make a flawed instrument operate more efficiently.

Question wording should be evaluated for clarity, neutrality, cognitive burden, and relevance. A double-barrelled question, such as “How satisfied are you with your salary and promotion opportunities?”, combines two constructs and prevents meaningful interpretation. Leading language can influence responses, while excessive use of matrix questions may cause satisficing, in which respondents select convenient rather than considered answers.

A digital survey should specify:

  • the target population and sampling frame;
  • inclusion and exclusion criteria;
  • recruitment and consent procedures;
  • the purpose and expected duration;
  • response scales and permitted values;
  • skip patterns and randomization rules;
  • procedures for incomplete or withdrawn responses;
  • protection of contact information and response data; and
  • retention, deletion, and reporting arrangements.

Validation rules should be proportionate. A required field can improve completeness, but forcing a response to a sensitive question may be coercive. A range rule can detect that age has been entered as 250, but it cannot establish that a reported age of 35 is truthful. For sensitive research, respondents should often have a “prefer not to answer” option, provided that this does not compromise the research design.

A pilot test should examine both substantive and technical performance. Researchers should ask pilot participants to explain how they interpreted difficult questions, while also testing browser compatibility, mobile display, accessibility, time stamps, branching, duplicate submissions, and data exports. Paradata—such as completion time, break-offs, device type, and navigation patterns—may help diagnose instrument problems, but their collection should be disclosed and justified.

Experiments and Computerized Measurement

Computer-assisted experiments may randomize participants into conditions, present stimuli, record reaction times, or connect behavioral tasks to surveys and organizational systems. Randomization code, allocation rules, exclusion criteria, and stopping decisions should be documented before examining outcomes where feasible. Otherwise, flexible data processing can create undisclosed researcher degrees of freedom.

The researcher must distinguish an experimental manipulation from the technology used to deliver it. A software platform may randomize assignments, but the validity of the experiment still depends on allocation concealment, manipulation fidelity, treatment compliance, measurement reliability, and control of confounding influences. Automated logging is valuable only when event definitions are stable. For instance, “session start” may mean opening a webpage in one system and completing authentication in another.

Ethical review should address deception, potential distress, differential treatment, withdrawal, and post-study explanation. Digital experiments involving employees require special care because organizational authority may make voluntary participation difficult. A statement that participation is optional is insufficient if supervisors can identify nonparticipants or if refusal creates workplace disadvantage.

APIs as Research Instruments

An API is a structured interface through which one software system requests data or services from another. APIs may deliver transaction records, social-media data, financial information, geospatial observations, or organizational metrics. A responsible API workflow begins by examining documentation, authentication requirements, rate limits, permitted uses, field definitions, version history, and deletion or correction mechanisms.

API data should not be treated as self-explanatory. Researchers must record the request endpoint, parameters, retrieval time, response version, pagination logic, and transformations applied. If an API returns only current values, historical states may be unrecoverable. If records are updated after retrieval, a later researcher may not reproduce the original dataset unless snapshots or response hashes have been retained appropriately.

A robust API pipeline separates:

1. Acquisition: authenticating and retrieving responses.

2. Staging: preserving raw responses in an unmodified, access-controlled location.

3. Transformation: parsing, standardizing, deduplicating, and enriching records.

4. Validation: testing schemas, required fields, types, ranges, and record counts.

5. Loading: placing approved data into analytical or operational tables.

6. Monitoring: recording failures, changes in schema, missing periods, and unusual volumes.

Credentials must never be embedded in public code or stored in ordinary spreadsheets. Access tokens should be managed through appropriate secret-management mechanisms, with least-privilege permissions and rotation procedures.

Web-Scraping and Publicly Available Information

Web-scraping is the automated extraction of information from websites. Public accessibility does not automatically mean unrestricted ethical or legal usability. Researchers should examine terms of service, robots exclusion signals, copyright and database rights, privacy expectations, authentication barriers, and the sensitivity of the information. A person may post information publicly for a limited social purpose without reasonably expecting large-scale profiling.

Scraping design should minimize burden. Request rates should be low enough to avoid disrupting a service, and researchers should identify themselves where appropriate. Data should be limited to fields necessary for the research question. Sensitive personal information, inferred attributes, and content posted by vulnerable individuals require heightened scrutiny.

Because webpage structures change, scraping requires versioned code, collection logs, source URLs, retrieval dates, parsing tests, and failure alerts. A scraper that silently shifts from collecting product prices to collecting promotional text can create a misleading longitudinal dataset. Researchers should retain sufficient provenance to explain what was collected without unnecessarily retaining personal content.

Sensor-Based and Internet-of-Things Data

Sensors produce observations through devices such as wearables, location systems, cameras, industrial monitors, point-of-sale terminals, and environmental instruments. Sensor studies require attention to calibration, sampling frequency, measurement error, battery or connectivity interruptions, device placement, and synchronization across clocks.

A sensor value is not equivalent to a fact. It is an observation generated by a device under particular conditions. A location reading may be imprecise; an inactivity measure may reflect device removal; a temperature sensor may be affected by placement. Researchers should maintain calibration records, firmware versions, device identifiers, units of measurement, and quality flags.

Sensor research is especially sensitive because continuous collection can reveal routines, health conditions, workplace behavior, or associations. Consent should specify what is collected, how frequently, for how long, who can access it, and whether raw or aggregated data will be shared. Where possible, collection should occur at the lowest resolution necessary. For example, a study of office occupancy may require room-level counts rather than individual movement histories.

Building the Dataset: Relational and Non-Relational Designs

A relational database organizes data into tables connected through keys. A typical research database might contain tables for participants, survey responses, experimental sessions, and events. In a normalized design, each fact is stored in an appropriate location, reducing duplication and update anomalies. A participant table may store one row per participant, while a response table stores one row per question response linked through a participant identifier.

Important relational concepts include:

  • Primary key: a field or combination of fields that uniquely identifies a row.
  • Foreign key: a field referring to a key in another table.
  • Entity integrity: the requirement that primary keys be unique and non-null.
  • Referential integrity: the requirement that foreign-key references correspond to valid records.
  • Normalization: organizing tables to reduce unnecessary redundancy and dependency problems.
  • Denormalization: intentionally combining data to improve analytical performance or usability.

A simplified SQL structure might be expressed as:

```sql

CREATE TABLE participant (

participant_id INTEGER PRIMARY KEY,

consent_status VARCHAR(20) NOT NULL,

enrollment_date DATE NOT NULL

);

CREATE TABLE response (

response_id INTEGER PRIMARY KEY,

participant_id INTEGER NOT NULL,

question_code VARCHAR(40) NOT NULL,

response_value VARCHAR(200),

FOREIGN KEY (participant_id) REFERENCES participant(participant_id)

);

```

A query joining participants with their responses might be:

```sql

SELECT p.participant_id, r.question_code, r.response_value

FROM participant AS p

JOIN response AS r

ON p.participant_id = r.participant_id

WHERE p.consent_status = 'consented';

```

SQL is not merely a retrieval language. Constraints, transactions, views, and audit queries can support governance. For example, an audit can identify response records linked to nonexistent participants, duplicate event identifiers, or dates outside the approved study period.

Non-relational databases are useful when data are highly variable, large in volume, rapidly generated, or naturally represented as documents, graphs, key-value pairs, or time series. A document database may store a survey session with nested answers; a graph database may represent relationships among organizations, directors, suppliers, or customers; a time-series database may efficiently manage sensor observations.

Non-relational flexibility does not remove the need for structure. Schemas may be explicit, implicit, or evolving, but field definitions, versioning, validation, and access controls remain necessary. A document that permits every record to have a different meaning is not a flexible research database; it is an ungoverned collection of ambiguities. The choice between relational and non-relational architecture should follow data characteristics, query requirements, scale, interoperability needs, and governance capacity.

Data Dictionaries, Metadata, and Interoperability

A data dictionary is a formal description of dataset fields. At minimum, it should state the field name, label, definition, data type, unit, permitted values, missing-value codes, source, transformation history, sensitivity classification, and responsible owner. A useful dictionary distinguishes “not applicable,” “not asked,” “unknown,” and “withheld,” rather than coding all four as zero or blank.

Metadata also describes the dataset as a whole: purpose, population, collection period, sampling procedure, instrument version, geographic coverage, processing steps, limitations, and licensing conditions. Without metadata, a technically readable file may be scientifically unusable.

Interoperability is the ability of systems to exchange and meaningfully use information. Syntactic interoperability concerns formats and technical exchange; semantic interoperability concerns whether the same terms have the same meaning. Common formats such as CSV, JSON, XML, and Parquet support exchange, but formats alone do not create meaning. Date standards, controlled vocabularies, code lists, persistent identifiers, and documented mappings are equally important.

A crosswalk can show how fields from two systems correspond. However, a mapping should identify imperfect equivalence. “Customer” in one system may mean a paying account, while in another it may mean any registered user. Treating them as identical can produce erroneous joins and biased findings.

Quality-Control Architecture

Quality control should occur throughout the data life cycle rather than at the end. Preventive controls include clear schemas, required fields, range checks, referential constraints, duplicate detection, and role-based permissions. Detective controls include reconciliation reports, anomaly detection, missingness analysis, sample verification, and comparison with trusted benchmarks. Corrective controls include documented cleaning rules, reprocessing, source correction, and versioned releases.

A practical quality-control plan should answer five questions:

1. What error could occur?

2. How would the error be detected?

3. Who is responsible for reviewing it?

4. What action is taken when it occurs?

5. How is the decision documented?

Cleaning must be reproducible. Researchers should preserve raw data separately, execute transformations through scripts or controlled workflows, record assumptions, and produce a change log. Manual editing of a master file is particularly risky because it obscures who changed what and why.

Missing data require substantive interpretation. Missingness may result from technical failure, participant refusal, skip logic, attrition, or a value that is genuinely undefined. The mechanism may be related to observed or unobserved characteristics, so simply replacing blanks with zero can create serious bias. A missingness report should examine patterns across time, groups, instruments, devices, and collection channels.

Ethical and Governance Responsibilities

Ethical data collection rests on respect for persons, beneficence, justice, transparency, and accountability. Consent should be understandable, specific enough for the proposed uses, and obtained before collection unless a justified and approved exception applies. Consent is not a universal solution: it does not legitimize excessive collection, insecure storage, discriminatory analysis, or uses incompatible with reasonable expectations.

Data minimization limits collection to what is necessary. Purpose limitation prevents later use from silently expanding beyond the original justification. De-identification can reduce risk, but removing names does not guarantee anonymity. Combinations of location, time, occupation, and rare characteristics may permit re-identification. Researchers should distinguish pseudonymization, in which a linking key remains, from anonymization, in which re-identification is not reasonably feasible under the relevant conditions.

Governance should allocate responsibility for data ownership, stewardship, access approval, incident response, retention, deletion, and publication. Technical safeguards include encryption in transit and at rest, authentication, least-privilege access, secure backups, logging, environment separation, and vulnerability management. Data should not be copied casually into personal devices, unmanaged cloud storage, or public repositories.

Regulatory requirements vary by jurisdiction and sector. Researchers must identify applicable privacy, health, employment, consumer-protection, intellectual-property, cybersecurity, and records-management rules. Institutional ethics review, contracts, data-processing agreements, and cross-border transfer requirements may also apply. Compliance is a floor, not a substitute for ethical judgment.

A Research Data Life-Cycle Framework

A defensible workflow can be organized into seven connected stages:

1. Specify: define the question, population, constructs, risks, and lawful or ethical basis.

2. Design: select instruments, sampling methods, architecture, identifiers, and validation rules.

3. Collect: acquire data with consent, security, provenance, and monitoring.

4. Process: stage, clean, transform, link, and document data without destroying raw evidence.

5. Store and govern: apply access controls, retention rules, backups, and versioning.

6. Analyze and share: disclose limitations, protect participants, and release only appropriate materials.

7. Archive or delete: preserve what is necessary for verification and securely dispose of what is no longer justified.

This life-cycle perspective prevents the common mistake of treating data management as an activity that begins after fieldwork. In reality, storage, identifiers, disclosure risk, and retention influence the design of collection itself.

Illustrative Case: A Retailer’s Employee Well-Being Platform

Background

Northbridge Retail, a fictional multi-site retailer, wishes to study whether scheduling predictability is associated with employee well-being and turnover intentions. The organization proposes a mobile survey, integration with scheduling records, and optional wearable data concerning sleep and activity.

Situation and Problem

The initial proposal would collect precise location, full scheduling histories, free-text comments, and continuous wearable data from all employees. Supervisors would receive individual results, and participation would be promoted through line managers. The research team recognizes that the design could create coercion, excessive surveillance, and re-identification risk.

Analysis

The research question requires measures of schedule changes, perceived control, fatigue, well-being, and turnover intention. It does not require continuous location histories or identifiable wearable streams. The employment relationship creates a power imbalance, and supervisors’ access could compromise voluntary participation. Combining schedule and survey data also creates a linkage risk, especially in small stores.

Approach and Solution

The team redesigns the study. An independent research office manages recruitment and consent. Participation is voluntary, and supervisors receive only aggregate results for groups large enough to reduce identification risk. Scheduling data are converted into necessary indicators, such as number of changes and notice period, rather than retaining every location event. Wearable participation is optional, and only weekly aggregated sleep-duration categories are collected.

Each participant receives a random study identifier. The identity key is stored separately with restricted access. The mobile survey uses range and completeness checks but permits “prefer not to answer” for sensitive items. A data dictionary defines every field, while an automated pipeline records source-system version, extraction time, transformation code, and validation results. Raw data are encrypted and retained only for the approved period. The analysis plan specifies how missing responses and employees changing stores will be handled.

Outcome

The revised design produces data that are less intrusive but more closely aligned with the research question. Participants report greater confidence in the study, and managers receive interpretable aggregate findings without access to individual employee profiles. The study cannot answer every possible question about employee behavior, but it provides stronger ethical and methodological foundations for the questions it does address.

Learning Points

The case illustrates that data minimization can improve, rather than reduce, research quality. It also demonstrates that consent, database architecture, aggregation, access controls, and analysis plans must be designed together. A technically possible variable is not automatically a scientifically necessary or ethically acceptable variable.

Challenges, Limitations, and Common Mistakes

Digital collection can amplify selection bias. People without reliable internet access, compatible devices, digital literacy, or willingness to be monitored may be underrepresented. Automated systems can also produce false precision: a timestamp with milliseconds does not make the underlying behavior accurate.

Common mistakes include using convenience samples without acknowledging their limits; changing survey questions mid-study without version control; joining datasets on unstable identifiers; treating “unknown” as zero; overwriting raw files; storing credentials in code; scraping without considering expectations of privacy; assuming de-identification is irreversible; and allowing dashboards to expose small subgroups.

Automation creates operational risk as well. APIs may change, sensors may fail, and scheduled jobs may run twice. A pipeline should be idempotent where possible, meaning that rerunning the same process does not create duplicate records. Monitoring should detect unusual record counts, schema changes, delays, and authentication failures.

Database normalization may produce many joins and affect performance, while denormalization may create inconsistent copies. These are engineering trade-offs, not ideological choices. The appropriate design depends on workload, analytical purpose, update frequency, and governance requirements.

Emerging Developments

Modern collection systems increasingly use edge computing, privacy-enhancing technologies, synthetic data, automated entity resolution, and machine-learning-assisted quality checks. Edge processing can reduce the transfer of sensitive raw data by converting it into lower-risk summaries near the source. Differential privacy and secure multiparty computation may support analysis while reducing exposure, although they introduce technical complexity and can affect statistical utility.

Generative AI can assist with schema documentation, code drafting, anomaly explanation, and instrument review. It can also invent plausible but incorrect transformations, expose confidential data through insecure prompts, or reproduce discriminatory assumptions. AI-generated code and classifications require human review, testing, provenance, and explicit accountability. A model should not be allowed to make unreviewed decisions about participant eligibility, consent validity, or disclosure risk.

Data spaces and interoperable standards are encouraging organizations to exchange data through common definitions rather than isolated files. At the same time, the expansion of connected devices and automated decision systems makes governance more important. The doctoral researcher’s role is therefore not merely to use new tools, but to evaluate whether their epistemic benefits justify their risks and whether their outputs remain interpretable and contestable.

Best Practices for Doctoral Researchers and Managers

A high-quality computer-assisted data project should:

  • begin with a clearly bounded research purpose;
  • define constructs, units, populations, and measures before selecting tools;
  • document consent, lawful basis, risks, and participant communications;
  • collect the minimum information necessary;
  • preserve raw data while separating it from processed releases;
  • use stable identifiers and maintain a secure linkage key;
  • create a complete data dictionary and versioned metadata;
  • validate data at entry, transfer, transformation, and analysis stages;
  • test APIs, scrapers, sensors, and survey logic before deployment;
  • monitor missingness, duplicates, drift, failures, and unusual values;
  • apply least-privilege access, encryption, backups, and audit logs;
  • make cleaning and transformation reproducible;
  • disclose limitations, uncertainty, and sampling bias;
  • review re-identification and group harms before sharing results; and
  • establish retention, archival, incident-response, and deletion procedures.

Chapter Summary

Computer-assisted data collection expands the scale and speed of research but does not replace methodological judgment. Surveys, experiments, APIs, web-scraping systems, and sensors must be designed around research questions, valid measures, appropriate populations, and ethical safeguards. Database management is integral to research quality because identifiers, schemas, metadata, missing-value rules, access controls, and transformation histories shape what the data mean.

Relational databases support structured entities, keys, constraints, and SQL operations, while non-relational systems are useful for documents, graphs, and high-volume or variable data. Both require explicit definitions and governance. Data dictionaries, provenance, interoperability, validation, quality-control plans, and reproducible pipelines protect the integrity of evidence. Ethical practice requires minimization, transparency, privacy protection, security, accountability, and sensitivity to power relationships. Emerging technologies such as edge processing, privacy-enhancing computation, and AI offer valuable capabilities but introduce new risks that require critical evaluation.

Key Terms

API: A structured interface allowing software systems to request and exchange data or services.

Data dictionary: A formal description of dataset fields, definitions, types, units, codes, and permitted values.

Data provenance: A record of data origin, processing history, transformations, and custodial responsibility.

Data minimization: Collecting and retaining only the information necessary for a legitimate purpose.

Entity integrity: The requirement that each relational-table primary key be unique and non-null.

Foreign key: A field that refers to a key in another table and supports relationships between records.

Interoperability: The capacity of systems to exchange and meaningfully use information.

Normalization: Organizing relational data to reduce redundancy and update anomalies.

Non-relational database: A database model using structures such as documents, graphs, key-value pairs, or time series rather than conventional tables alone.

Paradata: Information about the process of data collection, such as completion time, device, or navigation behavior.

Primary key: A unique identifier for a record in a relational table.

Pseudonymization: Replacing direct identifiers with coded identifiers while retaining a separate possibility of linkage.

Referential integrity: The requirement that foreign-key values correspond to valid records.

Schema: The formal structure, fields, data types, and relationships of a dataset or database.

Sensor data: Observations generated by instruments that measure physical, behavioral, or environmental conditions.

SQL: Structured Query Language used to define, retrieve, manipulate, and audit relational data.

Validation rule: A condition used to detect or prevent values that are missing, invalid, inconsistent, or outside permitted limits.

Web-scraping: Automated extraction of information from websites or other online sources.

Review Questions

Short Answer Questions

1. Why should computer-assisted data collection begin with a research question rather than a software platform?

2. Distinguish accuracy, validity, completeness, and timeliness as dimensions of data quality.

3. What purposes do primary keys and foreign keys serve in a relational database?

4. Why is public accessibility insufficient to establish that web-scraping is ethically acceptable?

5. What information should normally be included in a data dictionary?

Long Answer Questions

1. Explain how a researcher should design and pilot an ethical computer-assisted survey.

2. Compare relational and non-relational database designs, including the conditions under which each may be appropriate.

3. Describe an end-to-end API data pipeline and identify quality-control risks at each stage.

4. Discuss the ethical and methodological challenges of sensor-based research involving employees.

5. Explain how provenance, version control, validation, and reproducible cleaning contribute to research credibility.

Analytical / Application Questions

1. A researcher combines survey responses, payroll records, and location data using employee names and dates of birth. Analyze the methodological, privacy, and database risks and propose a safer linkage design.

2. An API pipeline suddenly retrieves 40 percent fewer records, but the software reports no error. Develop an investigation and response plan using provenance, monitoring, validation, and version control.

3. Design an ethical data architecture for a study examining whether flexible work arrangements influence employee well-being. Specify the measures, collection channels, identifiers, access controls, retention approach, and likely limitations.

22. Multiple Choice Questions with Answers

Question 1

Which design decision most directly supports both data minimization and ethical validity in the Northbridge Retail case?

A. Collecting continuous location histories from all employees

B. Replacing detailed location events with necessary aggregate scheduling indicators

C. Giving supervisors access to individual survey responses

D. Making wearable participation compulsory

Correct Answer: B. Replacing detailed location events with necessary aggregate scheduling indicators

Question 2

What is the principal function of a foreign key in a relational database?

A. To encrypt a database table

B. To identify the newest record

C. To connect a record to a related record in another table

D. To replace all missing values

Correct Answer: C. To connect a record to a related record in another table

Question 3

A researcher wants to preserve reproducibility when collecting API data. Which practice is most appropriate?

A. Retaining only the final cleaned spreadsheet

B. Recording endpoint parameters, retrieval time, response version, and transformations

C. Allowing credentials to remain in publicly shared code

D. Overwriting earlier extracts whenever new data arrive

Correct Answer: B. Recording endpoint parameters, retrieval time, response version, and transformations

Question 4

Why can a digitally recorded sensor value not automatically be treated as an objective fact?

A. Sensors never produce numerical data

B. Every sensor observation is affected by device conditions, calibration, and measurement error

C. Sensor data cannot be stored in databases

D. Sensor data are always intentionally fabricated

Correct Answer: B. Every sensor observation is affected by device conditions, calibration, and measurement error

Question 5

Which example best illustrates semantic interoperability rather than merely syntactic interoperability?

A. Two systems both export comma-separated files

B. Two systems use the same network protocol

C. Two systems agree that the term “customer” represents the same underlying population

D. Two systems store dates in different formats

Correct Answer: C. Two systems agree that the term “customer” represents the same underlying population

Question 6

A survey requires an answer to every sensitive question and does not offer a refusal option. What is the main ethical concern?

A. The survey will necessarily have a larger sample

B. The requirement may undermine voluntariness and increase pressure to disclose

C. The database will automatically become non-relational

D. The survey cannot use skip logic

Correct Answer: B. The requirement may undermine voluntariness and increase pressure to disclose

Question 7

Which quality-control action is primarily preventive?

A. Investigating an anomaly after publication

B. Comparing final results with an external benchmark

C. Applying schema constraints and permitted-value checks during data entry

D. Writing a post hoc explanation of missing records

Correct Answer: C. Applying schema constraints and permitted-value checks during data entry

Question 8

What is the main risk of treating all blank values as zero?

A. It guarantees referential integrity

B. It may confuse nonresponse, inapplicability, unknown values, and genuine zero values

C. It improves construct validity in every study

D. It prevents duplicate records

Correct Answer: B. It may confuse nonresponse, inapplicability, unknown values, and genuine zero values

Question 9

Which practice best protects the identity key in a pseudonymized research dataset?

A. Storing it in the same public file as the research data

B. Publishing it with the data dictionary

C. Storing it separately with restricted access

D. Replacing it with participants’ names

Correct Answer: C. Storing it separately with restricted access

Question 10

A web scraper silently begins collecting promotional text instead of product prices after a website redesign. Which control would most likely detect the problem?

A. Increasing the scraping speed

B. Removing retrieval dates from the logs

C. Using schema and content validation tests with failure alerts

D. Deleting the original source URLs

Correct Answer: C. Using schema and content validation tests with failure alerts

Research Ethics & Computer Applications
Chapter 11 of 15

Research Ethics & Computer Applications

Chapter 12
Quantitative Analytics and Computational Research

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

12. Quantitative Analytics and Computational Research

Introduction and Context

Quantitative analytics has become central to contemporary business research. Doctoral researchers increasingly work with large administrative databases, transactional records, digital trace data, sensor outputs, text, experiments, and longitudinal observations. Statistical software and programming environments make it possible to clean, integrate, visualize, model, simulate, and communicate such evidence at a scale that manual methods cannot support. Yet computational capacity does not guarantee valid knowledge. A sophisticated model can produce precise but misleading results when the data-generating process is misunderstood, assumptions are ignored, or analytical decisions are hidden.

Computational research therefore combines technical competence with methodological judgment and research ethics. The researcher must determine whether observations are appropriately represented, whether variables measure the intended constructs, whether missingness or selection has distorted the sample, and whether an apparent association can reasonably be interpreted as causal. Decisions about excluding observations, transforming variables, selecting models, tuning algorithms, and reporting uncertainty are not merely programming choices. They influence the claims that can be made and may affect employees, customers, investors, citizens, and public institutions.

This chapter treats quantitative analytics as a research system rather than a collection of software commands. It examines the workflow from data preparation to reproducible reporting, emphasizing assumptions, uncertainty, causal reasoning, model risk, and responsible use. The focus is not on one particular programming language. R, Python, Stata, Julia, SQL, spreadsheet tools, and specialist platforms can all support rigorous work when their use is documented and critically evaluated.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Design a defensible computational workflow for quantitative research.

2. Distinguish data cleaning, exploratory analysis, statistical inference, causal analysis, simulation, and machine learning.

3. Evaluate assumptions concerning measurement, sampling, missing data, dependence, functional form, and model specification.

4. Interpret estimates, intervals, prediction errors, sensitivity analyses, and simulation results appropriately.

5. Explain why prediction is not equivalent to causal explanation.

6. Assess model risk, algorithmic bias, overfitting, data leakage, and reproducibility threats.

7. Apply ethical, governance, and professional standards to computational research.

8. Communicate quantitative results clearly to scholarly and managerial audiences.

The Computational Research Workflow

A rigorous computational study begins before data analysis. The researcher formulates a question, identifies the target population, specifies the unit of analysis, defines constructs, and develops a data-management plan. A research question such as “Does a flexible-work policy improve productivity?” requires more precision than it initially appears to. Productivity may mean output per employee, quality-adjusted output, revenue, task completion, or managerial evaluation. The policy may be implemented at the employee, team, or organizational level. The relevant comparison may be before and after implementation, between adopting and non-adopting units, or between randomly assigned groups.

The workflow is iterative, but its principal stages are usually:

  • conceptualization and preregistration where appropriate;
  • data acquisition, documentation, and secure storage;
  • data cleaning and transformation;
  • exploratory visualization and descriptive analysis;
  • estimation, prediction, or causal identification;
  • validation, robustness analysis, and uncertainty assessment;
  • interpretation, reporting, and preservation of computational materials.

The distinction between a raw dataset and an analytical dataset is important. Raw data should generally be preserved in an immutable form, while transformations should be performed through scripts or documented procedures that generate analysis-ready files. A data dictionary should identify variable names, definitions, units, permissible values, sources, and changes made during preparation. Version control can record alterations to code and documentation, while a computational environment file can record package versions and dependencies.

A well-designed workflow separates data, code, outputs, and narrative interpretation. This separation reduces accidental overwriting and helps the researcher determine whether a result is produced by the documented analysis rather than by an undocumented manual intervention. Reproducibility does not mean that every study will produce identical findings in every environment. It means that the analytical pathway is sufficiently transparent and preserved for others to inspect, rerun, and evaluate.

Data Quality, Cleaning, and Measurement

Data cleaning is often described as a technical preliminary, but it is also a substantive research activity. Removing an implausible value requires a theory of what counts as plausible. A negative age, for example, may be an obvious coding error; an unusually low sales value may be either an error or a genuine observation. Automatic deletion of outliers can therefore eliminate precisely the cases that reveal important organizational conditions.

Cleaning commonly involves checking duplicate records, inconsistent identifiers, invalid dates, impossible ranges, incompatible units, coding changes, and conflicting sources. The researcher should distinguish four situations: an observed value that is valid, a value that is invalid, a value that is missing, and a value whose status is uncertain. Replacing uncertainty with an arbitrary value creates false precision.

Measurement validity is equally important. A variable may be reliable yet invalid: a survey item can consistently measure a narrow attitude while failing to represent the broader construct of organizational commitment. Composite measures should be justified conceptually and empirically. Researchers should consider content validity, construct validity, criterion-related validity, and measurement invariance when comparing groups or time periods. If a performance metric is redesigned during a study, an apparent trend may reflect a change in measurement rather than a change in performance.

Missing data require analysis rather than routine deletion. Missingness may be completely unrelated to observed and unobserved values, related to observed characteristics, or related to the unobserved value itself. These conditions are often described as MCAR, MAR, and MNAR. Complete-case analysis may be reasonable in limited circumstances, but it can reduce statistical power and introduce bias. Multiple imputation, inverse-probability weighting, sensitivity analysis, and explicit missingness indicators may be appropriate depending on the design and assumptions. No method eliminates the need to discuss why data are missing.

Visualization as Analytical Reasoning

Visualization is not merely a communication device. It is a way of interrogating the data-generating process. Histograms and density plots reveal skewness and multimodality; boxplots can expose group differences and extreme values; scatterplots show nonlinearity, clustering, and heteroskedasticity; time-series plots reveal seasonality, structural breaks, and autocorrelation. Faceted or stratified displays may show that an overall relationship disappears or reverses within subgroups.

Effective visualization requires attention to scale, aggregation, and denominators. A bar chart of total complaints can falsely suggest that the largest branch performs worst when it simply serves the most customers. Rates, exposure-adjusted measures, and confidence intervals may provide a more meaningful comparison. Truncated axes, inappropriate three-dimensional graphics, excessive decoration, and unequal category widths can distort perception.

Exploratory analysis should be distinguished from confirmatory analysis. Exploration may generate hypotheses and identify data problems, but findings discovered after repeatedly examining outcomes and subgroups should not be presented as though they were specified in advance. The distinction is not a prohibition on exploration; it is a requirement for honest labeling and appropriate evidential claims.

Statistical Inference and Uncertainty

Statistical inference uses a sample to learn about a wider population or a data-generating process. An estimate is not the same as the parameter it seeks to describe. Sampling variability, measurement error, model uncertainty, and specification uncertainty all contribute to uncertainty in a conclusion.

A confidence interval describes a procedure that, under repeated sampling and its assumptions, captures the parameter at a stated rate. It should not be interpreted as the probability that a fixed parameter lies inside one particular interval. Similarly, a p-value measures the compatibility of the observed data with a specified null model; it does not measure the probability that the null hypothesis is true or the practical importance of a result.

Researchers should report effect sizes and uncertainty rather than relying on statistical significance. A small effect may be statistically detectable in a very large dataset but irrelevant to a managerial decision. Conversely, a substantively important estimate may be imprecise in a small study. Prediction intervals, which incorporate uncertainty about future observations, are generally wider than confidence intervals for a mean or regression parameter.

Power analysis and precision planning should occur before data collection when possible. Post hoc claims that a nonsignificant finding “proves no effect” are inappropriate unless the study was sufficiently informative for the effect sizes of interest. Equivalence tests, minimum-effect thresholds, and Bayesian approaches can help align inference with substantive questions, although each requires transparent specification of assumptions and priors.

Regression, Model Specification, and Assumptions

Regression models summarize relationships between an outcome and explanatory variables. In a linear model, coefficients describe the expected change in the outcome associated with a one-unit change in a predictor, conditional on the included variables and the model form. This conditional interpretation is not automatically causal.

Key assumptions may include appropriate functional form, independent or correctly modeled errors, constant or appropriately modeled variance, absence of severe multicollinearity, and a meaningful relationship between measured variables and the constructs under investigation. Normality of the outcome is not generally required for unbiased coefficient estimation, but distributional assumptions influence small-sample inference and prediction. Diagnostics should therefore examine residuals, leverage, influence, variance patterns, and dependence rather than applying mechanical tests alone.

Model specification involves decisions about transformations, interactions, fixed effects, random effects, and control variables. A control variable can reduce confounding, but controlling for a mediator or collider may create bias. Directed acyclic graphs can help researchers articulate assumed causal structures before choosing covariates. The logic is substantive: a statistical association cannot identify a causal effect merely because the regression contains many variables.

Regularization methods such as ridge and lasso regression can improve prediction when predictors are numerous or correlated. They shrink coefficients and, in the case of lasso, may set some to zero. However, variable selection produced by a prediction-oriented algorithm should not automatically be interpreted as a theory-based test of importance. Cross-validation must be performed without allowing information from the test set to influence model development.

Causal Analysis: From Association to Identification

Causal analysis asks what would happen to an outcome under alternative interventions. The potential-outcomes framework represents this idea through potential outcomes under treatment and control, while causal diagrams emphasize pathways, confounding, selection, and intervention. Both perspectives clarify that causal claims depend on assumptions that cannot be established solely by running a regression.

Randomized experiments identify average treatment effects when assignment is properly implemented, treatment conditions are sufficiently stable, outcomes are measured validly, and interference is limited or modeled. In observational research, identification may rely on conditional exchangeability, a well-defined treatment, positivity, and consistent measurement. These assumptions are demanding and should be argued using institutional knowledge and research design, not merely asserted.

Common quasi-experimental approaches include difference-in-differences, regression discontinuity, instrumental variables, matching, synthetic controls, and interrupted time series. Difference-in-differences generally requires credible parallel trends in the absence of treatment. Regression discontinuity relies on the treatment threshold and the absence of precise manipulation around the cutoff. Instrumental-variable analysis requires a relevant instrument and a defensible exclusion restriction. Each design offers leverage under particular conditions and fails when those conditions are implausible.

Causal graphs help distinguish confounders, mediators, and colliders. A confounder influences both treatment and outcome and may need adjustment. A mediator lies on the pathway through which treatment operates; controlling for it changes the estimand. A collider is influenced by two variables, and conditioning on it can induce a spurious association. These distinctions are especially important in business databases, where variables such as promotion, customer selection, manager intervention, and performance may be jointly determined.

Simulation and Machine Learning

Simulation is useful when analytical solutions are difficult, when researchers wish to examine the consequences of assumptions, or when decision-makers need to understand uncertainty under alternative scenarios. Monte Carlo simulation repeatedly generates outcomes from specified probability distributions or structural relationships. The validity of the output depends on the validity of the input assumptions. Simulation should therefore include sensitivity analysis across plausible parameter values rather than presenting one numerical forecast as inevitable.

Bootstrapping estimates sampling variability by repeatedly resampling observed data, with modifications required for clustered, dependent, or time-series observations. Resampling cannot correct systematic bias in the original data, but it can provide useful empirical approximations when theoretical formulas are unsuitable.

Machine learning primarily emphasizes prediction, classification, ranking, or representation. Decision trees, random forests, gradient boosting, support-vector machines, neural networks, and ensemble methods can model complex relationships. Their value should be assessed using out-of-sample performance and a decision-relevant loss function. Accuracy alone may be inadequate where false positives and false negatives have different consequences.

The central distinction is between explanatory inference and predictive performance. A model can predict well without revealing a causal mechanism, and a theoretically meaningful causal model may predict modestly. Machine-learning systems are also vulnerable to overfitting, distribution shift, proxy discrimination, unstable labels, and data leakage. Explainability tools can clarify model behavior but do not transform associations into causal effects or guarantee fairness.

Model Risk, Robustness, and Reproducibility

Model risk is the possibility that a model produces misleading conclusions or decisions because of incorrect assumptions, unsuitable data, implementation errors, or inappropriate use. It exists in simple spreadsheets as well as advanced artificial-intelligence systems. Model governance should identify the model’s purpose, population, limitations, owner, validation procedures, monitoring indicators, and conditions under which it should not be used.

Robustness analysis examines whether conclusions survive reasonable alternative choices. Examples include alternative operationalizations, functional forms, sample restrictions, missing-data procedures, estimators, clustering levels, placebo tests, negative controls, and influence diagnostics. Robustness does not mean searching until a preferred conclusion survives. Alternatives should be justified before inspection where possible, and all materially relevant results should be reported.

Researchers should distinguish computational reproducibility, statistical reproducibility, and conceptual replicability. Computational reproducibility concerns rerunning the code and obtaining the reported output. Statistical reproducibility concerns whether similar procedures applied to new data yield comparable evidence. Conceptual replication asks whether the theoretical relationship appears under different operationalizations or settings. Failure at one level does not automatically invalidate a study, but it changes the confidence that should be placed in its conclusions.

Reproducible practice may include preregistration, version control, scripted analyses, automated tests, code review, containerized environments, persistent identifiers, and public repositories. Confidential or proprietary data may prevent full public release; in such cases, researchers can provide synthetic data, de-identified extracts, access protocols, detailed metadata, and executable code that operates on secure data.

Ethical and Governance Responsibilities

Computational research creates ethical obligations beyond statistical correctness. Data collected for one purpose may be repurposed for another without meaningful consent. Digital trace data can reveal sensitive attributes even when direct identifiers are removed. Re-identification risk increases when datasets are linked. Researchers should apply data minimization, purpose limitation, access controls, retention rules, encryption, and appropriate anonymization or pseudonymization.

Fairness requires attention to disparate error rates, unequal access, representational gaps, and the consequences of automated classification. A model may be equally accurate across groups while still producing unequal harms if the costs of errors differ. Conversely, a fairness adjustment that improves one criterion may worsen another when base rates differ. Such tensions cannot be resolved by technical metrics alone; they require institutional and normative judgment.

Research governance should address informed consent, institutional review, data-protection law, intellectual property, commercial confidentiality, and the rights of data subjects. Researchers must not conceal inconvenient analyses, fabricate observations, manipulate visual scales to exaggerate effects, or misrepresent exploratory findings as preregistered tests. Authorship should reflect substantive contributions, and the use of automated coding or generative tools should be documented when it affects the research process.

Illustrative Case: Predicting Employee Attrition

Background

A fictional organization, Meridian Services, wants to reduce voluntary employee turnover. Its analytics team has access to two years of human-resources records, compensation data, engagement surveys, absence records, promotion histories, and monthly performance indicators. Senior managers ask the team to build a model identifying employees likely to resign within six months.

Situation and Problem

The initial model achieves high predictive accuracy in a random train-test split. However, the team discovers that one important predictor is the number of visits to an internal “exit information” webpage. This variable is highly predictive but may reflect employees who have already decided to leave. The data also contain substantially fewer survey responses from hourly employees and inconsistent job codes following an organizational restructuring.

Analysis

The webpage variable creates a timing and interpretive problem. If the model is intended for early intervention, a variable recorded immediately before resignation may constitute leakage or may be unavailable at the point when managers need to act. The random split also allows records from the same employees and time periods to appear in both training and test data, producing an optimistic estimate of generalization. A temporal split would better represent deployment: train on earlier months and test on later months.

The team examines missingness by job category, calibrates predicted probabilities, and evaluates false-positive and false-negative rates across groups. It also conducts interviews with HR professionals to determine whether proposed interventions, such as workload review or career development, are beneficial and voluntary. The organization rejects a policy of automatically labeling employees as disloyal or denying promotion opportunities based on predictions.

Approach and Solution

The revised workflow excludes post-decision indicators, documents all feature definitions, uses a time-based validation design, and compares a transparent logistic model with tree-based alternatives. Performance is reported using calibration, precision-recall measures, and group-specific error analysis rather than accuracy alone. Predictions are used only to offer supportive conversations and resources, with employee privacy protections and human review. The model is monitored after deployment because labor markets, policies, and measurement practices may change.

Outcome

The revised model performs less impressively than the original but provides a more realistic estimate of future performance and produces fewer inappropriate interventions. Managers learn that some important predictors are organizational conditions—unmanageable workloads, limited advancement, and poor supervisory support—rather than individual deficiencies. The analytics project therefore shifts from surveillance toward organizational improvement.

Learning Points

The case illustrates that predictive performance must be evaluated at the point of use; leakage can create misleading results; fairness analysis must consider consequences rather than only aggregate accuracy; and ethical governance can improve, rather than obstruct, managerial value.

Common Failure Modes and Best Practices

Several mistakes recur in computational research. Analysts may begin modeling before clarifying the estimand, treat missing values as zero, remove outliers solely because they affect significance, select variables after examining results, use inappropriate standard errors for clustered data, or report a single preferred specification without sensitivity analysis. They may also confuse a highly predictive feature with a causal lever, publish rounded outputs that cannot be reconciled with the code, or fail to preserve the dataset version used in the analysis.

Best practice begins with a clear analytical protocol. Define the population, outcome, treatment or prediction target, time horizon, and decision context. Preserve raw data, document transformations, and test code. Visualize before modeling, inspect distributions and missingness, and use domain knowledge to evaluate anomalies. Separate training, validation, and test data where prediction is the objective. For causal work, state the identification strategy and its assumptions explicitly. Report effect sizes, uncertainty, sample construction, exclusions, and robustness results. Finally, communicate limitations in language that decision-makers can understand.

Current Developments

Several developments are reshaping computational research. Cloud platforms make large-scale computation more accessible but create new concerns about access governance, vendor dependence, data location, and cost control. Automated machine-learning systems can accelerate model comparison but may obscure feature engineering, tuning decisions, and reproducibility. Synthetic data can support development and sharing, although synthetic records may preserve privacy imperfectly and may fail to represent rare cases.

Causal machine learning seeks to estimate heterogeneous treatment effects and combine flexible prediction with causal questions. Its promise is substantial, but it remains dependent on research design and identification assumptions. Privacy-enhancing technologies, federated learning, differential privacy, and secure multi-party computation may allow analysis with reduced movement of sensitive data. These methods introduce their own trade-offs involving utility, transparency, computational burden, and governance.

The most important trend is not automation alone but the integration of technical systems with accountable research practice. Future doctoral researchers will need to understand both algorithms and institutions: how data are produced, who controls them, who bears error, and how evidence enters decisions.

Chapter Summary

Quantitative analytics and computational research require more than proficiency with statistical software. A defensible study connects theory, data, code, design, inference, and governance. Data cleaning is a substantive act because measurement and inclusion decisions affect conclusions. Visualization supports discovery, while inference requires careful interpretation of uncertainty. Regression and machine learning must be matched to their purposes, and predictive success should not be confused with causal explanation. Causal analysis depends on assumptions about identification, not simply on the number of controls in a model.

Simulation, resampling, robustness checks, validation, and sensitivity analysis help researchers understand model uncertainty and risk. Reproducible workflows preserve the relationship between data, code, outputs, and claims. Ethical practice requires privacy protection, fairness assessment, transparent reporting, responsible use, and attention to the consequences of computational decisions. The mature researcher treats software as an instrument of inquiry whose results remain subject to theoretical reasoning, empirical criticism, and professional accountability.

Key Terms

Computational reproducibility: The ability to rerun documented code and obtain the reported computational results.

Data leakage: The unintended use of information in model development that would not be available at the time of prediction or intervention.

Data-generating process: The underlying mechanism or set of conditions assumed to produce observed data.

Difference-in-differences: A quasi-experimental method comparing changes over time between treated and comparison groups.

Exploratory analysis: Examination of data to identify patterns, anomalies, and hypotheses before or alongside formal testing.

External validity: The extent to which findings generalize to other populations, settings, or periods.

Heteroskedasticity: Nonconstant variance of an error term across levels of predictors or fitted values.

Identification: The conditions under which a causal quantity can be learned from observed data.

Machine learning: Computational methods designed primarily to learn patterns for prediction, classification, or representation.

Model risk: The possibility that a model produces harmful or misleading results because of flawed data, assumptions, implementation, or use.

Missing at random: A missingness condition in which missingness may depend on observed information but not, conditional on that information, on the missing value itself.

Overfitting: Fitting idiosyncrasies of observed data so closely that performance deteriorates on new data.

Prediction interval: An interval expressing uncertainty about a future individual or aggregate observation.

Preregistration: Public or time-stamped specification of research questions, hypotheses, and analytical plans before outcome analysis.

Robustness analysis: Examination of whether conclusions persist under reasonable alternative assumptions or specifications.

Selection bias: Systematic distortion arising because inclusion in the analyzed sample is related to variables relevant to the research question.

Statistical inference: Use of sample evidence to draw conclusions about a population or data-generating process.

Synthetic data: Artificially generated data designed to reproduce selected properties of an original dataset.

Validity: The degree to which a measure or design supports the intended interpretation.

Review Questions

Short Answer Questions

1. Why should raw data be preserved separately from analysis-ready data?

2. Distinguish statistical significance from practical importance.

3. What is data leakage, and why does it threaten predictive evaluation?

4. Explain the difference between a mediator and a confounder.

5. Why is reproducibility an ethical as well as a technical concern?

Long Answer Questions

1. Explain how measurement validity, missing data, and data cleaning decisions can influence the conclusions of a quantitative study.

2. Compare explanatory inference and machine-learning prediction, including their different evaluation requirements.

3. Discuss the assumptions required for credible difference-in-differences analysis.

4. Develop a reproducible computational workflow for a doctoral business research project.

5. Explain how model risk and fairness should be governed when analytics informs employee or customer decisions.

Analytical / Application Questions

1. A retailer’s customer-retention model uses “number of cancellation-page visits” as its strongest predictor. Analyze whether this variable should be retained, considering timing, leakage, intervention, and ethical consequences.

2. A study finds that a new management-training program is associated with higher productivity after controlling for team size, tenure, and prior performance. Identify possible causal threats and propose a stronger research design.

3. An algorithm has equal overall accuracy across two employee groups but produces substantially more false positives for one group. Explain why this may be harmful and recommend additional analyses or governance measures.

22. Multiple Choice Questions with Answers

Question 1

Which practice most directly supports computational reproducibility?

A. Reporting only the final regression table

B. Preserving raw data, versioned code, and documented transformations

C. Deleting intermediate files after publication

D. Using the most complex available algorithm

Correct Answer: B. Preserving raw data, versioned code, and documented transformations

Question 2

A researcher removes all observations with unusually high sales values because they affect the coefficient. What is the primary concern?

A. The model has too few predictors

B. The researcher may be deleting valid information without substantive justification

C. The confidence interval will necessarily become wider

D. Visualization is no longer possible

Correct Answer: B. The researcher may be deleting valid information without substantive justification

Question 3

What does a p-value represent?

A. The probability that the null hypothesis is true

B. The practical importance of an estimated effect

C. Compatibility of the observed data with a specified null model

D. The probability that the sample was randomly selected

Correct Answer: C. Compatibility of the observed data with a specified null model

Question 4

Which condition is especially important for a difference-in-differences design?

A. Perfect normality of the outcome

B. Parallel trends in the absence of treatment

C. A very large number of control variables

D. Equal sample sizes at every time point

Correct Answer: B. Parallel trends in the absence of treatment

Question 5

Why can controlling for a collider create bias?

A. It increases the sample size artificially

B. It can induce an association between variables that were otherwise unrelated

C. It guarantees heteroskedasticity

D. It removes all treatment variation

Correct Answer: B. It can induce an association between variables that were otherwise unrelated

Question 6

A model performs exceptionally well on a test set because information from that set influenced feature selection. This is an example of:

A. Data leakage

B. Measurement invariance

C. External validity

D. Randomization

Correct Answer: A. Data leakage

Question 7

Which statement best distinguishes prediction from causal explanation?

A. Prediction always requires randomization

B. A predictive relationship may be useful without identifying what would happen under an intervention

C. Causal models never make predictions

D. Prediction cannot use observational data

Correct Answer: B. A predictive relationship may be useful without identifying what would happen under an intervention

Question 8

What is the main purpose of a sensitivity analysis?

A. To guarantee that a finding is true

B. To examine how conclusions change under plausible alternative assumptions

C. To eliminate the need for theory

D. To replace data validation

Correct Answer: B. To examine how conclusions change under plausible alternative assumptions

Question 9

In the employee-attrition case, why was a time-based validation split preferred to a random split?

A. It always produces higher accuracy

B. It better represents deployment on future observations

C. It removes the need to examine fairness

D. It guarantees causal identification

Correct Answer: B. It better represents deployment on future observations

Question 10

Which statement about simulation is most accurate?

A. Simulation results are assumption-free because they are computer-generated

B. Simulation can explore uncertainty, but its conclusions depend on the specified input assumptions

C. Simulation is appropriate only for experiments

D. Simulation eliminates model risk

Correct Answer: B. Simulation can explore uncertainty, but its conclusions depend on the specified input assumptions

Research Ethics & Computer Applications
Chapter 12 of 15

Research Ethics & Computer Applications

Chapter 13
Qualitative and Mixed-Methods Computer Applications

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

13. Qualitative and Mixed-Methods Computer Applications

Introduction and Context

Qualitative and mixed-methods research has always depended on close engagement with meaning, context, language, relationships, and interpretation. Digital technologies have transformed how researchers capture, organize, analyse, integrate, and communicate such evidence. Computer-assisted qualitative data analysis software (CAQDAS), transcription systems, reference managers, survey platforms, statistical packages, visualization tools, and increasingly artificial intelligence can reduce mechanical burdens and make complex research designs more manageable. They do not, however, convert interpretation into an automatic or value-free procedure.

For doctoral researchers in business administration, this distinction is decisive. Interviews with executives, observations of organizational routines, internal documents, digital communications, field notes, and survey responses may need to be analysed together. Software can help a researcher locate patterns across thousands of pages, compare cases, construct matrices, link evidence to theoretical propositions, and document analytic decisions. Yet the credibility of the study remains dependent on research design, reflexivity, ethical judgment, contextual sensitivity, and a defensible chain of evidence.

This chapter examines computer applications across the qualitative and mixed-methods research cycle. It treats technology as an interpretive infrastructure rather than as a substitute for methodological reasoning. Particular attention is given to transcription, coding, thematic and content analysis, mixed-methods integration, visualization, audit trails, data security, artificial intelligence, and the preservation of interpretive integrity.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the purposes and limits of computer-assisted qualitative and mixed-methods applications.

2. Design an ethically defensible workflow for preparing, storing, transcribing, coding, and analysing qualitative data.

3. Distinguish descriptive, interpretive, process, and theoretical coding.

4. Apply thematic analysis, qualitative content analysis, and cross-case analysis using digital tools.

5. Integrate qualitative and quantitative evidence through matrices, joint displays, and meta-inferences.

6. Evaluate the use of automation and artificial intelligence without surrendering researcher accountability.

7. Construct an audit trail that supports credibility, dependability, confirmability, and reflexivity.

8. Identify risks involving confidentiality, re-identification, bias, security, and inappropriate software dependence.

From Data Management to Interpretation

Computer applications support several connected but distinct activities. Data management involves file naming, version control, metadata, storage, retrieval, and controlled access. Data preparation includes transcription, translation, anonymization, formatting, and quality checking. Analysis involves coding, categorization, memo writing, comparison, pattern identification, and theory development. Integration links qualitative findings with quantitative results. Communication uses networks, models, tables, timelines, and other visual representations.

These activities should not be confused. A well-organized project is not necessarily analytically strong, and a visually attractive network is not evidence of a meaningful relationship. Software records what a researcher has done; it cannot independently establish whether the interpretation is warranted. The central question is therefore not, “Which program is best?” but, “Which digital arrangement makes the research design, evidence, reasoning, and ethical safeguards most transparent?”

A typical doctoral project may contain audio and video files, transcripts, observation notes, policy documents, spreadsheets, survey exports, bibliographic records, analytic memos, codebooks, and case summaries. A relational approach is useful: each item should have an identifier, provenance, date, consent status, storage location, and relationship to a participant, case, event, or research question. This structure allows the researcher to move from an interpretive claim back to supporting evidence while protecting information that should not be exposed.

Important Concepts and Terminology

Qualitative data are non-numerical or textually, visually, aurally, or materially expressed evidence interpreted in context. CAQDAS refers to software that assists with the organization and analysis of qualitative materials. A unit of analysis is the entity about which a claim is made, such as an employee, team, organization, incident, or industry episode. A code is a label assigned to a segment of data. A codebook records code names, definitions, inclusion and exclusion criteria, examples, and relationships among codes.

A memo is a written record of an analytic thought, question, decision, or interpretation. Reflexivity is the systematic examination of how the researcher’s identity, assumptions, relationships, and choices shape the research. An audit trail is an organized record of methodological and analytic decisions. Data saturation, more cautiously described in some designs as information power or sufficient interpretive depth, concerns whether additional data are likely to change the developing explanation. A theme is a patterned meaning relevant to the research question, not merely a frequently occurring topic.

Mixed-methods integration is the deliberate connection of qualitative and quantitative strands. A joint display is a table, matrix, or visual arrangement that places evidence from both strands together for interpretation. A meta-inference is a conclusion derived from the combined, rather than merely parallel, findings. De-identification removes or alters direct and indirect identifiers; anonymization implies a stronger condition in which re-identification is not reasonably possible. Provenance describes the origin and history of a data item or analytic result.

A Defensible Digital Workflow

Planning the analytic architecture

Before importing data into software, the researcher should specify the research questions, paradigm, design, units of analysis, role of theory, sampling logic, expected data types, and ethical restrictions. A constructivist study may treat coding as an interpretive engagement with multiple realities, whereas a post-positivist content analysis may emphasize predefined categories, reliability checks, and systematic counting. The software should serve this logic rather than silently impose one.

The project should have a data management plan covering consent, retention, access, encryption, backups, transfer, destruction, and responsibility for collaborators. Cloud services require special scrutiny because data may cross jurisdictions or be processed under terms that permit secondary use. Sensitive interviews should not be uploaded to an unapproved transcription or AI service merely because it is convenient.

Preparing and transcribing data

Transcription is an analytic and ethical stage, not a clerical prelude. The researcher must decide whether the transcript will be verbatim, cleaned, phonetic, conversation-analytic, or focused on content. Pauses, laughter, interruptions, emotional expression, code-switching, and silence may matter in studies of leadership, identity, power, or organizational conflict. Automated speech recognition can produce a rapid draft, but accents, technical terminology, overlapping speech, names, and culturally specific expressions require human checking.

A defensible workflow preserves the original recording, the machine-generated draft if one exists, the checked transcript, and a record of corrections. The transcript should be linked to a participant identifier rather than a name. Identifying details can be replaced with brackets or standardized pseudonyms, while a separate, encrypted key is stored with restricted access. Researchers should avoid assuming that removing names is sufficient: job titles, rare events, small departments, and distinctive quotations can make individuals identifiable.

Coding and memoing

Coding may be deductive, inductive, abductive, or iterative. Deductive codes derive from theory or research questions. Inductive codes emerge from engagement with the data. Abductive analysis moves between surprising observations and plausible explanations. In practice, doctoral research often combines these approaches through a provisional codebook that evolves as the researcher encounters negative cases and new meanings.

A useful coding hierarchy can include:

  • descriptive codes, which identify the subject of a passage;
  • process codes, which capture action, change, or sequence;
  • interpretive codes, which express meaning or significance;
  • emotion or values codes, which register affective and normative dimensions; and
  • pattern or theoretical codes, which connect categories to broader explanations.

Coding should not become indiscriminate highlighting. A segment should be coded because it contributes to a question, comparison, concept, process, or interpretation. Overlapping codes are legitimate when a passage performs several analytic functions. The researcher should record uncertainty in memos rather than forcing premature classification. Memos should explain why a code was created, merged, split, renamed, or abandoned and should distinguish participants’ language from the researcher’s inference.

When several researchers code the same material, discussion and calibration are usually more valuable than treating a numerical agreement statistic as proof of validity. Agreement measures can be appropriate in some structured content analyses, but they do not resolve conceptual ambiguity or prove that a codebook captures participants’ meanings. Teams should examine disagreements, clarify definitions, document adjudication, and consider how hierarchy or disciplinary authority shaped the decision.

Analytic Approaches Supported by Software

Thematic analysis

Thematic analysis commonly involves familiarization, initial coding, development of candidate themes, review of thematic coherence, definition and naming of themes, and production of an analytic account. Software can retrieve all passages associated with a code, compare themes across cases, display co-occurrence, and connect excerpts to memos. The researcher must nevertheless ask whether a theme is internally coherent, distinct from other themes, significant for the research question, and supported by varied evidence.

Frequency is a weak proxy for importance. A rarely mentioned experience may reveal a critical power relation, an exceptional crisis, or a marginalized perspective. Conversely, a frequently repeated corporate phrase may reflect institutional language rather than genuine commitment. Themes should therefore be interpreted in relation to context, speaker position, timing, contradiction, and the conditions under which data were produced.

Qualitative content analysis

Content analysis may be conventional, with categories derived from the data; directed, with categories informed by prior theory; or summative, where word or phrase occurrences are interpreted in context. Digital tools can count terms, classify documents, compare categories by organizational unit, and generate summary matrices. Counting is useful when linked to a transparent sampling and categorization procedure, but isolated word counts ignore negation, irony, metaphor, and unequal opportunities to speak.

A rigorous content analysis specifies the unit of coding, category rules, treatment of overlapping categories, sampling frame, missing material, and procedures for checking consistency. Researchers should distinguish manifest content—what is explicitly stated—from latent meaning, which requires interpretive analysis and contextual justification.

Case comparison and process analysis

In business research, the case is often an organization, project, market episode, or strategic initiative. Case nodes, attributes, timelines, and matrices allow comparison of conditions and outcomes. A researcher may construct a matrix with rows for cases and columns for leadership practices, institutional pressures, implementation events, and outcomes. Process coding and event mapping can then support explanations of how change unfolded rather than merely describing what occurred.

Visualization can expose gaps in the evidence. A timeline may reveal that an interviewee’s retrospective account compresses several events. A matrix may show that a proposed pattern is present in only one subgroup. Such discrepancies should prompt further inquiry, not automatic correction of the data.

Mixed-Methods Integration

Mixed-methods computer applications are most valuable when integration is designed from the beginning. In a sequential explanatory design, quantitative results may identify unexpected relationships or groups for qualitative follow-up. In a sequential exploratory design, qualitative findings may generate constructs or items for a later survey. In a convergent design, qualitative and quantitative strands may be collected separately and brought together during interpretation. Embedded designs place one form of evidence within a larger intervention or evaluation.

Integration can occur through connecting, building, merging, or embedding. Digital tools support each operation, but the logic must remain explicit. For example, survey respondents with unusually high turnover intentions may be selected for interviews; qualitative categories may inform a scale; datasets may be merged by case identifier; or interview evidence may explain the mechanism behind a statistical association.

Joint displays are particularly useful. A display might include a quantitative result, the relevant qualitative theme, illustrative evidence, convergence or divergence, and an integrated interpretation. The final column should not merely say “supported.” It should state what the combination means—for example, that formal autonomy predicts innovation only where middle managers protect experimentation from short-term performance pressures. This is a meta-inference, and it requires reasoning across methods.

Divergent findings are not necessarily a defect. They may indicate different populations, time periods, constructs, measurement assumptions, or levels of analysis. A statistically modest effect and powerful narrative accounts may together suggest heterogeneous mechanisms. Researchers should preserve these tensions in the report instead of averaging them into an artificial consensus.

Visualization as an Interpretive Practice

Networks, code co-occurrence maps, concept maps, Sankey diagrams, timelines, geographic displays, and mixed-methods matrices can make complex evidence inspectable. Visualization is not neutral: choices about node size, color, category boundaries, missing data, and aggregation influence what readers notice. A visual should therefore have a declared purpose and a traceable relationship to the data.

Good practice includes showing denominators where counts are used, distinguishing coded presence from frequency, explaining whether relationships are conceptual or empirically observed, and avoiding visual precision that the data cannot support. Quotations in a visual or report should be checked against the source, translated transparently, and assessed for re-identification risk. A compelling diagram cannot compensate for weak sampling or unsupported inference.

Reflexivity, Audit Trails, and Interpretive Integrity

Digital systems can create an illusion of objectivity because they display codes, counts, and diagrams. Reflexivity counters this illusion. Researchers should record positionality, access conditions, relationships with participants, assumptions brought from theory, emotional responses, and moments when their interpretation changed. Reflexive memos should be dated and linked to analytic stages, but they should not be confused with personal diary entries that have no methodological relevance.

An audit trail may include the research protocol, consent materials, data inventory, transcription conventions, codebook versions, coding decisions, memo history, case-selection rationale, negative-case analysis, software settings, integration matrices, and reasons for excluding or revising evidence. Version control is important: a final codebook without earlier versions conceals the development of the analysis. Auditability does not mean that another researcher must reproduce the same interpretation; qualitative credibility depends on making the path of interpretation understandable and defensible.

Interpretive integrity requires retaining context. Researchers should preserve enough surrounding text to understand a quotation, note who produced the statement and under what circumstances, and avoid stripping contradictory evidence from the dataset. Member reflection, peer debriefing, triangulation, prolonged engagement, and searching for negative cases can strengthen an account, but none is a ritual guarantee. Their appropriateness depends on the paradigm and research question.

Ethics, Governance, and Security

Ethical review must address digital risks in addition to ordinary interview or survey risks. Participants may consent to a study without anticipating automated transcription, algorithmic classification, international cloud storage, or future data linkage. Consent information should explain these processes in accessible language. Researchers should collect only what is necessary, restrict access by role, encrypt data in transit and at rest where feasible, use strong authentication, and maintain secure backups.

Organizational research presents special challenges. An executive may authorize access to a company, but employees may still feel compelled to participate. Small samples can make supposedly anonymous quotations recognizable. Researchers must separate organizational permission from individual consent and consider whether reporting a finding could harm a participant’s employment, reputation, or safety.

AI systems introduce additional concerns: opaque training data, hallucinated transcripts or summaries, systematic accent and language bias, data retention by vendors, and automation bias in which researchers accept plausible outputs without checking them. AI may assist with draft transcription, translation, classification, retrieval, or visualization, but the researcher remains responsible for accuracy, confidentiality, disclosure, and interpretation. Every machine-assisted output should be treated as provisional and verified against source material. Researchers should document the tool, version, task, prompts where relevant, human checks, and material corrections.

An Illustrative Case: Integrating Evidence on Hybrid Work

Background

The fictional Meridian Services Group, a multinational professional-services organization, commissioned a doctoral study of hybrid work and knowledge sharing. The project used an employee survey, interviews with thirty-six staff members and managers, team observations, and internal policy documents.

Situation and problem

Survey results showed a moderate positive association between perceived flexibility and job satisfaction but no overall association between remote-work frequency and innovation. Senior leaders wanted a simple conclusion about whether office attendance should be increased.

Analysis and approach

The researcher stored identifiable contact information separately from research data and used pseudonymous case identifiers. Automated transcription produced first drafts, which were checked while listening to the recordings. A provisional codebook included flexibility, coordination, visibility, informal learning, managerial trust, and performance pressure. During iterative coding, the researcher added “protected experimentation” and “unequal access to informal networks.” Memos documented the researcher’s prior assumption that flexibility was inherently beneficial.

A case-by-theme matrix compared teams with high and low innovation scores. A joint display then placed survey patterns beside interview themes and observation evidence. The analysis showed that flexibility supported satisfaction across many teams, but innovation depended on whether teams had routines for spontaneous problem-solving and whether managers protected time for experimentation. New employees and contractors reported weaker access to informal learning. Two cases contradicted the dominant pattern: highly co-located teams experienced low trust and little knowledge sharing.

Outcome

The integrated inference was not that remote work caused or prevented innovation. Rather, flexibility altered the conditions under which coordination, trust, and learning occurred. The organization adopted team-level collaboration routines, mentoring for new employees, and outcome-based performance discussions instead of a universal attendance rule.

Learning points

The case demonstrates why frequency counts cannot replace contextual interpretation, why divergent cases are analytically valuable, and why mixed-methods integration should produce an explanation rather than a simple vote between methods. It also shows how reflexive memoing can reveal assumptions that would otherwise shape coding invisibly.

Common Failures and Practical Safeguards

Several mistakes recur in digitally supported research. Researchers may choose software before clarifying the design, equate the number of codes with analytic depth, merge categories merely to simplify a diagram, or report co-occurrence as causation. They may trust automated transcripts without checking names and negations, export sensitive quotations into unsecured spreadsheets, or delete earlier codebook versions. Another failure is treating inter-coder agreement as the sole evidence of rigor while ignoring power, context, and interpretive disagreement.

Safeguards include a pilot workflow, a written data dictionary, regular encrypted backups, access logs, transcript quality checks, codebook versioning, analytic memos, negative-case review, and explicit integration questions. A doctoral researcher should also be able to explain why a particular tool was selected, what the tool cannot do, and how the project would proceed if the software became unavailable.

Emerging Directions

Current development is moving toward multimodal analysis, large-language-model assistance, real-time transcription, automated entity recognition, collaborative cloud environments, and links between qualitative repositories and statistical platforms. These developments may improve retrieval and support analysis of video, images, gesture, and digital trace data. They also intensify questions about consent, intellectual property, cultural and linguistic bias, explainability, and the ownership of derived representations.

The most defensible future practice is human–machine complementarity. Machines are effective at searching, sorting, detecting recurrent forms, and managing scale. Researchers are responsible for meaning, context, theoretical judgment, ethical evaluation, and the interpretation of silence and contradiction. Institutions will increasingly need governance policies specifying approved tools, data classifications, retention periods, disclosure standards, and review procedures for generative AI.

Best-Practice Framework for Doctoral Researchers

A sound computer-assisted project should:

1. Align tools with the paradigm, research questions, units of analysis, and ethical approval.

2. Separate identifiers from analytic data and apply proportionate security controls.

3. Preserve originals, document transformations, and maintain version history.

4. Treat automated transcription, translation, coding, and summarization as drafts requiring human verification.

5. Use a living codebook supported by memos and examples.

6. Analyse context, absence, contradiction, sequence, and power—not only frequency.

7. Plan mixed-methods integration through connecting procedures and joint displays.

8. Make visualization choices transparent and avoid implying unsupported precision.

9. Record positionality, analytic decisions, disagreements, and negative cases.

10. Report software use sufficiently for readers to assess provenance, limitations, and accountability.

Chapter Summary

Computer applications can strengthen qualitative and mixed-methods research by improving organization, retrieval, comparison, transcription, visualization, and integration. Their value depends on methodological alignment and disciplined human judgment. Transcription requires verification; coding requires conceptual reasoning; thematic and content analysis require context; and visualization requires interpretive caution. Mixed-methods studies gain explanatory power when qualitative and quantitative strands are deliberately connected through case selection, instrument development, data merging, or joint displays. Reflexivity and audit trails make analytic decisions visible, while ethical governance protects participants from confidentiality breaches, re-identification, insecure platforms, and uncritical AI use. The central principle is that software can support the research process but cannot assume responsibility for meaning, evidence, or ethical accountability.

Key Terms

CAQDAS: Computer-assisted qualitative data analysis software used to organize and analyse qualitative materials.

Codebook: A structured record of code definitions, boundaries, examples, and relationships.

Coding: Assigning analytic labels to segments of data for interpretation and comparison.

Data provenance: The origin, history, and transformations associated with a data item or result.

De-identification: Removing or altering direct and indirect identifiers to reduce identification risk.

Audit trail: A documented record of methodological, analytic, and data-management decisions.

Reflexivity: Examination of how the researcher’s position and assumptions shape the study.

Memo: A dated analytic note recording an interpretation, question, decision, or change.

Thematic analysis: Systematic development and interpretation of patterned meanings in data.

Qualitative content analysis: Categorization and interpretation of manifest or latent content.

Unit of analysis: The entity about which a research claim is made.

Joint display: A table or visual that brings qualitative and quantitative evidence together.

Meta-inference: An integrated conclusion derived from combined methodological strands.

Negative case: Evidence that challenges or qualifies an emerging explanation.

Information power: The extent to which a dataset has sufficient relevance, specificity, quality, and analytic depth for a study.

Automation bias: The tendency to accept machine-produced outputs without adequate evaluation.

Interpretive integrity: Faithful, contextual, transparent, and ethically defensible representation of meaning.

Version control: Preservation and tracking of successive data, codebook, or analytic-file versions.

Review Questions

Short Answer Questions

1. Why is automated transcription considered a provisional analytic resource rather than a final record?

2. Distinguish a code, a category, and a theme.

3. What is the purpose of an audit trail in qualitative research?

4. Why can frequency be a misleading indicator of thematic importance?

5. Define a joint display and state its role in mixed-methods research.

Long Answer Questions

1. Explain how a doctoral researcher can design a defensible digital workflow from data collection through reporting.

2. Compare thematic analysis and qualitative content analysis, including the ways computer applications support and constrain each approach.

3. Discuss reflexivity and interpretive integrity in software-assisted qualitative research.

4. Examine the ethical and governance issues associated with cloud-based transcription and generative AI.

5. Explain how divergent qualitative and quantitative findings can contribute to stronger mixed-methods inferences.

Analytical / Application Questions

1. A researcher discovers that an AI transcript has omitted pauses, names, and overlapping speech in interviews about workplace discrimination. Design a corrective and ethically defensible procedure.

2. A survey finds that hybrid work is unrelated to innovation, while interviews strongly associate flexibility with creativity. Using the Meridian Services case, propose an integration strategy that avoids treating either finding as automatically superior.

3. A research team reports a highly connected code network and claims that the most connected code is the main cause of organizational change. Critically evaluate this claim and specify additional evidence required.

22. Multiple Choice Questions with Answers

Question 1

Which practice best preserves interpretive integrity when using automated transcription?

A. Accepting the transcript when its overall meaning appears plausible

B. Deleting the original audio after importing the transcript

C. Checking the draft against the recording and documenting material corrections

D. Allowing the software to resolve ambiguous names automatically

Correct Answer: C. Checking the draft against the recording and documenting material corrections

Question 2

In a mixed-methods study, a joint display is primarily used to:

A. Replace the need for qualitative interpretation

B. Place qualitative and quantitative evidence together to support integrated inference

C. Calculate inter-coder reliability

D. Anonymize interview participants

Correct Answer: B. Place qualitative and quantitative evidence together to support integrated inference

Question 3

Why might a rarely mentioned passage deserve substantial analytic attention?

A. Rare passages are always more valid than frequent passages

B. It may reveal a critical, marginalized, or exceptional meaning relevant to the research question

C. Software assigns greater importance to rare codes

D. It automatically represents the dominant theme

Correct Answer: B. It may reveal a critical, marginalized, or exceptional meaning relevant to the research question

Question 4

Which statement best describes a living codebook?

A. A fixed list of keywords generated before data collection

B. A record that evolves through documented definitions, examples, and analytic decisions

C. A statistical table of response frequencies

D. A transcript containing only participant quotations

Correct Answer: B. A record that evolves through documented definitions, examples, and analytic decisions

Question 5

A researcher separates participant names from transcripts and stores the linkage key in an encrypted, access-restricted location. This primarily addresses:

A. Theoretical saturation

B. Visual design

C. Confidentiality and re-identification risk

D. Inter-coder disagreement

Correct Answer: C. Confidentiality and re-identification risk

Question 6

Which conclusion is most defensible when qualitative and quantitative findings diverge?

A. The qualitative strand must be discarded

B. The quantitative strand must be treated as objective truth

C. The divergence may reflect different constructs, populations, times, or mechanisms and requires interpretation

D. The results should be averaged into one score

Correct Answer: C. The divergence may reflect different constructs, populations, times, or mechanisms and requires interpretation

Question 7

What is the main limitation of interpreting a code co-occurrence network as evidence of causation?

A. Networks cannot contain qualitative data

B. Co-occurrence shows association in coded material, not necessarily temporal or causal influence

C. Causal claims require more colorful visualizations

D. Software networks only display numerical variables

Correct Answer: B. Co-occurrence shows association in coded material, not necessarily temporal or causal influence

Question 8

Which action most directly demonstrates reflexivity?

A. Increasing the number of software licenses

B. Recording how the researcher’s assumptions and position influenced coding decisions

C. Counting every occurrence of a participant’s words

D. Removing contradictory excerpts from the dataset

Correct Answer: B. Recording how the researcher’s assumptions and position influenced coding decisions

Question 9

In the illustrative Meridian Services case, the integrated finding was that:

A. Universal office attendance was necessary for innovation

B. Remote work always increased innovation

C. Flexibility affected the organizational conditions under which coordination, trust, and learning occurred

D. Survey results were invalid because interviews were more detailed

Correct Answer: C. Flexibility affected the organizational conditions under which coordination, trust, and learning occurred

Question 10

Which is the most appropriate position on generative AI in doctoral qualitative research?

A. AI outputs can be treated as verified because they are computational

B. AI should never be used for any research task

C. AI may assist with drafts and retrieval, but outputs require verification, disclosure, and researcher accountability

D. Confidential data may be uploaded whenever a tool is free

Correct Answer: C. AI may assist with drafts and retrieval, but outputs require verification, disclosure, and researcher accountability

Research Ethics & Computer Applications
Chapter 13 of 15

Research Ethics & Computer Applications

Chapter 14
Artificial Intelligence in Research

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

14. Artificial Intelligence in Research

Introduction and Context

Artificial intelligence (AI) has become an important research instrument rather than merely a subject of research. Generative AI systems can summarize texts, propose research questions, write and translate code, classify documents, generate synthetic data, and assist with academic prose. Machine-learning systems can identify patterns in large datasets, predict outcomes, detect anomalies, and automate decisions. These capabilities can improve research efficiency, but they also create significant threats to validity, accountability, privacy, attribution, and scholarly trust.

The central issue is not whether researchers may use AI. In many contexts, responsible use is possible and beneficial. The more important question is how AI use can be governed so that the researcher remains intellectually accountable for the problem formulation, evidence, interpretation, and claims. AI systems do not possess research responsibility. They optimize outputs according to training data, prompts, objectives, or statistical associations; they do not independently establish truth, understand ethical obligations, or assume responsibility for consequences.

For doctoral researchers, AI governance is therefore a methodological issue as well as an ethical one. An apparently efficient tool may alter the research question, exclude relevant perspectives, introduce fabricated references, reproduce historical discrimination, or obscure the reasoning behind a decision. Responsible use requires transparency about the system, preservation of human judgment, verification of outputs, protection of confidential information, and an audit trail sufficient for another scholar to understand how AI affected the research.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish among generative AI, machine learning, automated decision tools, and conventional research software.

2. Evaluate appropriate and inappropriate uses of AI in literature review, coding, data analysis, and academic writing.

3. Explain hallucination, bias, opacity, automation bias, data leakage, and reproducibility risks.

4. Apply a risk-based governance framework involving human oversight, documentation, validation, and disclosure.

5. Design ethically defensible procedures for privacy, attribution, authorship, intellectual property, and research integrity.

6. Critically assess AI-supported research outputs and identify circumstances requiring human review or institutional approval.

The Researcher, the Model, and the Evidence

AI in research should be understood as a relationship among three elements: the researcher, the computational model, and the evidence. The model transforms inputs into outputs, but the researcher determines what the output means and whether it is fit for purpose. Evidence remains the basis of scholarly claims; an AI-generated statement is not evidence merely because it is fluent or statistically plausible.

Generative AI produces new text, images, code, audio, or other content from patterns learned during training. Large language models generate sequences of tokens by estimating likely continuations. They can produce persuasive explanations without possessing a reliable mechanism for distinguishing fact from invention. Machine learning, by contrast, includes supervised, unsupervised, and reinforcement-learning approaches. A supervised model learns relationships between inputs and labelled outcomes; an unsupervised model identifies structure without predefined labels; reinforcement learning optimizes actions through feedback. Automated decision tools use rules, predictions, rankings, or recommendations to support or determine decisions.

These categories overlap. A literature-screening system may use machine learning; a chatbot may generate summaries; a hiring algorithm may make or support decisions. Governance must therefore address the function and consequences of a system, not only its technical label.

A useful distinction is between assistance and delegation. Assistance supports a researcher who remains capable of checking and rejecting the output. Delegation transfers a meaningful research judgment to a system, whether or not the researcher formally acknowledges that transfer. Delegation may be acceptable in low-risk administrative tasks, but it requires stronger justification when it affects participant classification, exclusion from a sample, interpretation of evidence, or publication claims.

AI Across the Research Process

Formulating questions and reviewing literature

AI can help map terminology, suggest related concepts, identify themes in a corpus, and create preliminary search strings. It may help a researcher compare theoretical traditions or detect gaps for further investigation. However, generated research questions can reflect dominant literature, training-data imbalances, or fashionable topics. A model may omit scholarship from less represented languages, regions, or disciplines.

The use of AI for literature review does not remove the need for systematic searching. Researchers should search recognized scholarly databases, retain search strategies, inspect original publications, and verify every citation. A generated reference, quotation, page number, or interpretation must be checked against the source. AI-generated summaries are especially risky when a paper contains qualifications, contradictory findings, or methodological limitations that a short summary omits.

AI may be used to assist screening, but inclusion and exclusion criteria should be established before automated classification. A sample of included and excluded records should be manually assessed, and disagreement rates should be reported where appropriate. If the system repeatedly excludes studies from a particular language, method, or population, the review may acquire systematic bias.

Coding and computational analysis

Code-generating systems can produce scripts, explain error messages, translate code between languages, and suggest tests. These uses can reduce routine workload, especially when the researcher understands the relevant programming concepts. The danger arises when generated code is executed without inspection. A script may contain an incorrect statistical test, silently mishandle missing values, leak data, use an unsuitable package, or generate results that appear reasonable but are invalid.

Responsible practice includes writing a human-readable specification before requesting code, reviewing each important function, testing with known cases, checking assumptions, recording software versions, and preserving the final executable workflow. Researchers should distinguish code that runs from code that correctly operationalizes a construct. A model can implement an instruction literally while misunderstanding the research design.

Data analysis and interpretation

AI can support clustering, classification, forecasting, natural-language analysis, image analysis, and anomaly detection. It can reveal patterns that would be difficult to observe manually. Yet predictive performance does not establish causal explanation. A model may achieve high accuracy because it exploits a proxy for the target variable, because the test data resemble the training data unusually closely, or because information from the future has entered the analysis.

Researchers should separate exploratory from confirmatory use. AI-assisted discovery may generate hypotheses, but hypotheses identified after examining data should not be presented as if they had been specified in advance. Validation should use appropriate holdout data, cross-validation, robustness checks, sensitivity analysis, and, where relevant, external validation. Performance should be assessed with metrics suited to the problem and population, not only overall accuracy. For imbalanced classification, for example, accuracy can conceal poor performance for a minority class.

Interpretability has several meanings. A model may be intrinsically simple, provide feature importance, produce local explanations for individual predictions, or be accompanied by a broader account of how it was trained and validated. None of these automatically proves that the model is fair or causally meaningful. Explanations can be unstable, incomplete, or persuasive without being faithful to the actual computational process. The researcher must therefore explain both what the model does and what it cannot establish.

Academic writing and dissemination

AI can assist with grammar, translation, structure, plain-language summaries, and alternative wording. Such assistance may improve accessibility for multilingual researchers and readers. It becomes problematic when the system generates substantive arguments, fabricates sources, conceals uncertainty, or replaces the author’s intellectual contribution.

The researcher is responsible for factual accuracy, originality, appropriate citation, and compliance with publisher and institutional rules. AI systems should not be listed as authors because they cannot take responsibility, approve a final manuscript, disclose conflicts, or respond to allegations of misconduct. Where required by policy, the researcher should disclose the tool, purpose, material extent of use, and verification procedures. Disclosure is not merely a bureaucratic act; it enables readers and editors to assess the provenance of the work.

A Governance Framework for AI-Assisted Research

A practical governance model can be organized around six questions: purpose, provenance, performance, protection, participation, and presentation.

Purpose asks why AI is being used and whether its use is necessary. A low-risk grammar correction differs from automated classification of research participants. The researcher should identify the decision or task that the tool will influence and consider a non-AI alternative.

Provenance concerns the origin of data, prompts, model versions, training materials, generated outputs, and human edits. A research record should indicate which outputs were accepted, modified, or rejected. Provenance is particularly important when a generated output enters the dataset or becomes part of the analysis.

Performance requires evidence that the system works for the intended context. Validation should reflect the target population, language, domain, and operating conditions. Performance evaluation should include error analysis rather than a single headline metric.

Protection covers confidentiality, privacy, cybersecurity, intellectual property, and data governance. Sensitive data should not be entered into a public or unapproved service. De-identification may reduce risk but does not guarantee anonymity, especially where datasets can be linked. Researchers should understand retention, reuse, access, and training policies of the service provider.

Participation refers to human oversight and affected stakeholders. A researcher should determine who reviews outputs, who can challenge a decision, and when the system must be stopped. For research involving communities or vulnerable participants, consultation may reveal harms that technical testing misses.

Presentation concerns disclosure, attribution, limitations, and communication. Publications should accurately describe AI involvement, avoid overstating capability, and distinguish human conclusions from machine-generated suggestions.

This framework can be combined with a risk matrix. Probability of error and severity of consequence should both be assessed. High-impact uses—such as eligibility decisions, sensitive inference, or analysis of identifiable health information—require stronger controls, independent review, and often explicit institutional approval. A tool used only to correct spelling generally presents lower risk, although confidentiality and intellectual-property concerns can remain.

Core Ethical and Methodological Problems

Hallucination and fabricated authority

A hallucination is an output that is unsupported, inaccurate, or invented but presented in a plausible form. In research, common examples include nonexistent articles, incorrect quotations, fabricated statistics, and false descriptions of methods. The appropriate response is not to ask the system to “be more accurate,” but to establish a verification process. Primary sources, datasets, code, and calculations must be inspected independently.

Bias and representational injustice

Bias can enter through sampling, labels, measurement choices, historical decisions, model architecture, deployment context, or researcher interpretation. A model trained on past organizational decisions may reproduce past discrimination. A language model may provide more reliable outputs for dominant languages and cultural contexts. Bias assessment should examine subgroup performance, error types, missing populations, and the consequences of errors. Fairness is not reducible to one universal metric; different fairness criteria can conflict, and their relevance depends on the research purpose.

Privacy and confidentiality

Prompts and uploaded files may contain personal, proprietary, or identifiable information. Even when a service claims not to use data for training, retention and access conditions must be examined. Researchers should apply data minimization, use approved environments, remove unnecessary identifiers, control access, and obtain appropriate consent. Consent language should not imply uses that participants could not reasonably anticipate.

Explainability, accountability, and contestability

An opaque system can make it difficult to identify error or assign responsibility. Explainability is particularly important when a model affects participants or produces a finding that others may rely upon. A defensible workflow identifies the accountable human decision-maker, records relevant inputs and model versions, preserves an appeal or correction process, and communicates uncertainty. Human oversight must be meaningful: a person who merely clicks approval without reviewing evidence provides nominal rather than substantive oversight.

Reproducibility and instability

Generative outputs may vary with model version, temperature, context, system instructions, or service updates. Proprietary models may not be available to other researchers. Reproducibility therefore requires recording dates, tool names, versions where available, prompts or prompt templates, relevant settings, input materials, outputs, and human interventions. In some cases, researchers should preserve an approved local copy or use deterministic procedures. Reproducibility does not require publishing confidential prompts or protected data, but it does require enough methodological information for a credible evaluation.

Attribution, authorship, and intellectual property

Academic contribution involves judgment, interpretation, accountability, and responsibility. AI can be a tool, but it cannot be an accountable author. Researchers must cite human-created sources used to support claims and should not cite a chatbot as though it were the original authority. Questions concerning copyright and training data vary across jurisdictions and platform terms; consequently, institutional policy and applicable law should be consulted rather than assumed.

An Operational Workflow

A defensible AI-assisted project can follow this sequence:

1. Classify the task. Identify whether AI is being used for administration, language assistance, discovery, analysis, prediction, or decision-making.

2. Assess risk. Consider sensitivity of data, impact on participants, reversibility of errors, bias exposure, and dependence on a proprietary system.

3. Specify human responsibility. Name the person responsible for checking inputs, outputs, interpretations, and final decisions.

4. Select and test the tool. Compare alternatives, review terms of service, conduct pilot tests, and assess performance on representative material.

5. Control data. Minimize inputs, remove unnecessary identifiers, use secure environments, and document permissions.

6. Validate outputs. Verify citations, recalculate results, inspect code, review subgroup errors, and compare with independent methods.

7. Document the process. Preserve prompts, versions, transformations, decisions, exceptions, and rejected outputs in an appropriate research log.

8. Disclose and review. Report material use, limitations, and oversight arrangements; seek ethics or institutional review when required.

The workflow should be iterative. If validation reveals unacceptable errors, the researcher should revise the prompt, change the tool, narrow the use, or abandon automation. Efficiency is not a sufficient justification for exposing participants or weakening validity.

Applications in Business and Management Research

In organizational research, AI can support analysis of employee narratives, customer reviews, financial documents, supply-chain records, and market communications. A researcher may use natural-language processing to identify themes in thousands of annual reports or sentiment patterns in service interactions. However, sentiment scores may confuse sarcasm, cultural expression, or domain-specific language. Employee text may also contain sensitive information, and automated inference of personality, mental health, or performance raises serious ethical concerns.

Managers may use predictive tools for recruitment, promotion, credit, fraud detection, or customer segmentation. Doctoral researchers studying such systems must examine not only predictive accuracy but also institutional context: who defines the target, who benefits, who bears errors, and whether affected persons can contest outcomes. A technically successful model can still be organizationally illegitimate if it embeds discriminatory criteria or eliminates meaningful accountability.

AI can also assist qualitative research through transcription, translation, coding suggestions, and thematic clustering. These functions should supplement, not replace, close reading and reflexive interpretation. Researchers should check transcription accuracy for accents, specialist terms, and emotionally significant statements. When participants have not consented to external processing, uploading recordings to a third-party service may be impermissible.

Illustrative Case: An AI-Supported Employee Attrition Study

Background

A doctoral researcher, Maya, is studying voluntary employee turnover in a multinational services organization. The organization provides three years of de-identified survey responses, absence records, job histories, and exit-interview text. Senior managers request a model that identifies employees who are likely to resign so that retention interventions can be targeted.

Situation and problem

Maya considers using a commercial language model to summarize exit interviews and a predictive model to rank current employees by attrition risk. The dataset appears de-identified, but job titles, dates, locations, and rare comments could make individuals recognizable. Historical turnover is higher among employees from several underrepresented groups. In addition, the organization has used performance ratings that managers acknowledge are inconsistent.

Analysis

The project involves several risks. Uploading text to an external service may breach confidentiality. The outcome label—resignation—may reflect organizational conditions rather than employee characteristics. Historical ratings may encode managerial bias. A high-risk ranking could lead managers to monitor particular employees or offer benefits selectively, creating a self-fulfilling process. Because the model is intended for intervention, not merely academic description, errors have practical consequences.

Approach

Maya first obtains institutional ethics approval and an agreement specifying permitted data use. She uses a secure environment and removes direct and indirect identifiers where feasible. Rather than sending raw interviews to a public model, she tests an approved local language-processing system and manually reviews a sample of classifications. She pre-registers the principal outcome and evaluation plan, separates exploratory text analysis from confirmatory prediction, and compares a transparent baseline model with more complex alternatives.

Performance is evaluated across relevant employee groups, not only in aggregate. Maya examines false-positive and false-negative patterns, tests sensitivity to alternative definitions of turnover, and conducts interviews with employees and HR practitioners to understand how predictions might be used. The study does not produce individual rankings for managerial action. It reports aggregate patterns and explicitly states that associations do not establish that an employee will resign or that an intervention will prevent resignation.

Outcome

The analysis identifies organizational factors—workload instability, limited development opportunities, and inconsistent scheduling—that are more actionable than individual risk scores. The organization agrees to use the findings to review policies rather than target employees. Maya documents tool versions, transformations, validation procedures, and human decisions, and discloses the material role of AI in the methods section.

Learning points

The case illustrates that responsible AI governance is not achieved by improving prediction alone. Data protection, construct validity, subgroup evaluation, stakeholder participation, proportionality, and limits on use are equally important. A less automated and more transparent design may produce stronger research and more constructive managerial consequences.

Common Mistakes and Practical Safeguards

Researchers frequently treat fluent output as accurate, cite sources they have not inspected, upload confidential data for convenience, fail to record model versions, confuse correlation with explanation, and describe generated prose as entirely their own without considering disclosure requirements. Another mistake is to assume that human review automatically solves bias. Reviewers may defer to a system, especially when it presents numerical confidence or technical language. This is known as automation bias.

Safeguards include independent verification, adversarial testing, blind review of selected outputs, comparison with non-AI methods, subgroup analysis, secure data handling, and explicit stop conditions. Research teams should define when a human must intervene and should train members to recognize uncertainty and model limitations. Supervisors, ethics committees, publishers, and organizational partners all have roles, but responsibility cannot be outsourced to a vendor or committee.

Current Developments and Emerging Questions

Research governance is moving toward documentation of foundation models, model cards, dataset statements, impact assessments, provenance standards, and risk-based regulation. Retrieval-augmented systems can ground generation in a supplied corpus, but they do not eliminate errors in retrieval, interpretation, or citation. Synthetic data may assist testing and privacy protection, yet synthetic records can reproduce the biases of the source data and may not preserve relationships needed for valid inference. Autonomous research agents may eventually plan searches, write code, run analyses, and draft reports. Their use will intensify questions about auditability, delegation, and the boundary between assistance and independent action.

Emerging governance should therefore emphasize capability-based evaluation rather than promotional claims. Institutions need clear policies that distinguish acceptable assistance from high-risk automation, provide secure tools, support disclosure, and establish procedures for incident reporting. Scholars should also contribute to governance research by studying the social effects of AI systems rather than treating technical performance as the sole measure of success.

Best-Practice Principles

A concise set of principles follows:

  • Use AI only for a defined research purpose and choose the least risky tool that can perform the task.
  • Treat every generated output as a hypothesis or draft until independently verified.
  • Keep accountable human judgment at points affecting evidence, interpretation, participants, or decisions.
  • Protect confidential and personal data through minimization, approved infrastructure, and access controls.
  • Test for validity, subgroup performance, robustness, and unintended consequences.
  • Preserve an audit trail of tools, versions, prompts, outputs, transformations, and human interventions.
  • Distinguish exploratory discovery from confirmatory analysis and report deviations honestly.
  • Do not assign authorship to AI; attribute intellectual contributions and disclose material use.
  • Explain limitations, uncertainty, and prohibited uses to readers and organizational stakeholders.
  • Stop or redesign the system when risks cannot be reduced to an acceptable level.

Chapter Summary

AI can increase the scale and speed of research, but it does not replace scholarly responsibility. Generative AI is useful for language, discovery, coding assistance, and structured support; machine learning can identify patterns and generate predictions; automated decision tools can influence organizational action. Across all uses, researchers must verify outputs, protect data, assess bias, preserve explainability and contestability, and distinguish association from causal knowledge. A risk-based governance process should address purpose, provenance, performance, protection, participation, and presentation. Meaningful human oversight, reproducible documentation, accurate attribution, and appropriate disclosure are essential. The strongest AI-assisted research is not the most automated; it is the research in which computational assistance is proportionate, transparent, validated, and subordinate to defensible scholarly judgment.

Key Terms

Artificial intelligence: Computational systems designed to perform tasks associated with human intelligence, such as learning, prediction, language processing, or decision support.

Generative AI: AI that produces new content, including text, code, images, or audio, from learned patterns and user inputs.

Machine learning: Methods through which computational models learn patterns from data to make predictions, classifications, or decisions.

Automated decision tool: A system that applies rules, predictions, rankings, or recommendations to support or determine a decision.

Hallucination: A plausible-looking but unsupported, inaccurate, or fabricated AI output.

Bias: A systematic distortion in data, methods, models, or interpretation that produces unfair or invalid results.

Automation bias: The tendency to trust or defer to an automated output even when contrary evidence exists.

Explainability: The extent to which the operation or output of a model can be understood and communicated.

Interpretability: The degree to which a model’s internal relationships or outputs can be meaningfully understood.

Human oversight: Active human responsibility for reviewing, challenging, and controlling an AI-assisted process.

Data minimization: Collecting, processing, and sharing only the data necessary for a defined purpose.

Data leakage: Unintended exposure of confidential information or the use of information in analysis beyond authorized purposes.

Provenance: The documented origin and history of data, tools, outputs, transformations, and decisions.

Reproducibility: The ability to obtain consistent research results through documented procedures and materials.

Construct validity: The extent to which an operational measure represents the theoretical construct it is intended to measure.

External validation: Testing a model on data or settings beyond those used for its development.

Synthetic data: Artificially generated data designed to resemble characteristics or relationships in real data.

Transparency: Clear communication about methods, tools, data, limitations, and research decisions.

Contestability: The opportunity for affected persons or researchers to question, correct, or appeal an AI-supported output.

Research integrity: Commitment to honesty, accuracy, accountability, and responsible conduct throughout research.

Review Questions

Short Answer Questions

1. What distinguishes assistance from delegation in AI-assisted research?

2. Why must AI-generated citations be verified against original sources?

3. Define automation bias and explain why it is dangerous in research.

4. What is the purpose of preserving an AI research audit trail?

5. Why does predictive accuracy not establish causal explanation?

Long Answer Questions

1. Explain how AI can be used responsibly at different stages of the research process, from literature review to academic writing.

2. Discuss the six dimensions of the proposed governance framework: purpose, provenance, performance, protection, participation, and presentation.

3. Critically evaluate the relationship among bias, explainability, human oversight, and research validity.

4. Analyze the ethical and methodological risks of using generative AI with confidential qualitative research data.

5. Discuss why authorship, attribution, disclosure, and accountability cannot be delegated to an AI system.

Analytical / Application Questions

1. You are asked to use a public chatbot to classify identifiable employee interviews into high- and low-risk categories. Design a safer alternative workflow and justify each control.

2. An AI model has 95 percent overall accuracy but performs substantially worse for a minority subgroup. How should the researcher evaluate and report the model before using it?

3. A language model generates a convincing theoretical explanation and several apparently relevant references. Develop a verification and documentation procedure before incorporating the material into a doctoral thesis.

22. Multiple Choice Questions with Answers

Question 1

Which practice best demonstrates meaningful human oversight in AI-assisted research?

A. Accepting all outputs after a researcher clicks an approval button

B. Reviewing, challenging, and documenting important outputs before using them

C. Using a more expensive model without validating its results

D. Allowing the vendor to assume responsibility for research decisions

Correct Answer: B. Reviewing, challenging, and documenting important outputs before using them

Question 2

A language model produces a nonexistent journal article with a realistic title and authors. This is best classified as:

A. External validation

B. Data minimization

C. Hallucination

D. Synthetic data

Correct Answer: C. Hallucination

Question 3

Why can overall accuracy be misleading when evaluating an AI classification model?

A. Accuracy always measures causal effects

B. It may conceal poor performance for a minority subgroup

C. Accuracy cannot be calculated for machine-learning models

D. It automatically proves that the model is explainable

Correct Answer: B. It may conceal poor performance for a minority subgroup

Question 4

Which action most directly protects confidential research data when using an AI tool?

A. Uploading all raw data to a public service for better results

B. Using data minimization and an approved secure environment

C. Removing only the researcher’s name from the dataset

D. Assuming that de-identification guarantees anonymity

Correct Answer: B. Using data minimization and an approved secure environment

Question 5

A researcher uses AI to identify themes after examining the entire dataset, then presents those themes as pre-specified hypotheses. What is the principal methodological problem?

A. The research uses qualitative data

B. The analysis confuses exploratory discovery with confirmatory analysis

C. The researcher used a computational tool

D. The findings must therefore be invalid

Correct Answer: B. The analysis confuses exploratory discovery with confirmatory analysis

Question 6

Which statement most accurately describes explainability?

A. It proves that a model is fair

B. It guarantees that a model establishes causation

C. It concerns how the operation or output of a model can be understood and communicated

D. It eliminates the need for performance testing

Correct Answer: C. It concerns how the operation or output of a model can be understood and communicated

Question 7

In the employee attrition case, why did the researcher avoid producing individual risk rankings for managers?

A. Predictive models cannot analyze employee data

B. Individual rankings could create harmful consequences and be misused

C. Aggregate findings are always more accurate than individual predictions

D. The organization had no interest in retention

Correct Answer: B. Individual rankings could create harmful consequences and be misused

Question 8

Which item is most important for reproducibility when a generative AI system materially affects a study?

A. The researcher’s personal opinion of the tool

B. The tool, version, prompts, outputs, settings, and human interventions

C. The number of pages in the final thesis

D. A claim that the model is unbiased

Correct Answer: B. The tool, version, prompts, outputs, settings, and human interventions

Question 9

Why should AI systems not be listed as academic authors?

A. They are unable to generate any text

B. They cannot assume responsibility, approve a manuscript, or respond to misconduct allegations

C. They are always inaccurate

D. They cannot be used in academic writing

Correct Answer: B. They cannot assume responsibility, approve a manuscript, or respond to misconduct allegations

Question 10

What is the most defensible response when validation reveals unacceptable subgroup error?

A. Hide the subgroup results to avoid confusion

B. Use the model anyway if its average accuracy is high

C. Revise, narrow, replace, or abandon the AI use

D. Transfer responsibility to the software vendor

Correct Answer: C. Revise, narrow, replace, or abandon the AI use

Research Ethics & Computer Applications
Chapter 14 of 15

Research Ethics & Computer Applications

Chapter 15
Open Science, Digital Transformation and Future Research Governance

Doctorate in Business Administration
Research Ethics & Computer Applications   •   Doctorate

15. Open Science, Digital Transformation and Future Research Governance

Introduction and Context

Research ethics has traditionally focused on informed consent, confidentiality, privacy, avoidance of harm, and the integrity of published findings. Digital transformation expands this ethical field. Contemporary research may involve cloud platforms, large administrative datasets, artificial intelligence, automated experimentation, distributed databases, synthetic data, and computationally reproducible workflows. These developments create opportunities for more transparent, efficient, and socially valuable research, but they also introduce new forms of surveillance, exclusion, data misuse, intellectual-property conflict, and automated error.

Open science is a broad movement seeking to make the research process more transparent, accessible, reproducible, and participatory. It includes preregistration, registered reports, open access, open data, open code, open materials, replication, and public engagement. Openness, however, is not an absolute ethical rule. Research data may contain personal information, commercially sensitive knowledge, security-relevant details, or information relating to vulnerable communities. Responsible research governance therefore requires a proportionate balance among transparency, privacy, intellectual property, participant protection, institutional duties, and public value.

For doctoral researchers and business scholars, the issue is strategic as well as methodological. Decisions about data access, publication, software, collaboration, commercialization, and artificial intelligence can affect the credibility of an entire research programme. The central question is not simply whether research should be open, but what should be open, to whom, when, under what conditions, and with what accountability.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the principal practices associated with open science.

2. Evaluate the benefits and limitations of preregistration, registered reports, open data, open code, and replication.

3. Distinguish legitimate confidentiality and commercialization constraints from unjustified secrecy.

4. Apply governance frameworks to synthetic data, autonomous research agents, and federated analytics.

5. Design audit, documentation, and responsible-innovation mechanisms for digitally enabled research.

6. Make defensible decisions about transparency, privacy, security, intellectual property, and accountability.

From Research Transparency to Open Science

Traditional research communication often treated the journal article as the primary research product. The article reported selected methods, analyses, and conclusions, while research materials, data-cleaning decisions, failed analyses, and software dependencies frequently remained inaccessible. Open science challenges this narrow model by viewing research as a sequence of inspectable outputs rather than a single final publication.

The core rationale is epistemic. When methods, data, code, and decisions are visible, other researchers can evaluate the credibility of a claim, identify errors, reproduce an analysis, and build on the work. Openness can also reduce selective reporting and encourage cumulative knowledge. It may improve efficiency by preventing unnecessary duplication and enable interdisciplinary collaboration.

Yet openness produces no automatic guarantee of truth. Publicly available data may be poorly collected; open code may be undocumented; replication may fail because a theory is context-dependent rather than because the original study was fraudulent. Open practices must therefore be combined with methodological competence, critical peer review, data protection, and institutional responsibility.

The principle of “as open as possible, as closed as necessary” offers a useful starting point. It requires researchers to justify restrictions rather than assume either unrestricted disclosure or complete secrecy. A responsible openness statement should identify what is available, what is restricted, why the restriction exists, who may obtain access, and when the restriction will be reviewed.

Preregistration and Registered Reports

Preregistration is the public documentation of a research plan before data analysis, and ideally before data collection. A preregistration may specify research questions, hypotheses, variables, sampling procedures, exclusion criteria, statistical models, and primary outcomes. It does not prevent exploratory analysis. Instead, it distinguishes confirmatory analyses planned in advance from analyses developed after observing the data.

This distinction is important because researchers can unintentionally engage in hindsight bias, selective reporting, or “hypothesizing after results are known.” Preregistration makes analytical flexibility visible and helps readers assess the evidential status of a claim. It is especially valuable in hypothesis-testing research, experiments, surveys, and large-scale computational studies.

Preregistration has limitations. A plan may be changed for legitimate reasons when data quality, measurement, or field conditions differ from expectations. Rigid adherence can encourage mechanical research and discourage valuable discovery. The ethical requirement is not never to deviate, but to document deviations clearly, explain their rationale, and label post hoc analyses appropriately.

A registered report extends preregistration through peer review before the results are known. In the first stage, reviewers evaluate the research question, theory, design, and analysis plan. If the protocol is accepted in principle, the study receives a publication commitment subject to faithful execution and transparent reporting. This separates publication decisions from the attractiveness or statistical significance of results. It can reduce publication bias and reward rigorous null findings.

For doctoral researchers, registered reports also provide an early opportunity to improve design. However, they may be less suitable for highly emergent qualitative inquiry, rapidly changing field settings, or research in which the research question necessarily evolves through engagement with participants. The appropriate response is methodological fit, not universal adoption.

Open Data, Open Code and Replication

Open data means that research data are made available for inspection or reuse, subject to appropriate legal, ethical, and technical conditions. Data may be fully open, available through controlled access, or represented through de-identified or synthetic alternatives. “Data available on request” is often weaker than a structured repository arrangement because requests may be inconsistently handled and links may disappear.

Data sharing requires more than uploading a file. A usable dataset needs a data dictionary, variable definitions, provenance information, collection dates, sampling details, missing-data explanations, codebooks, licenses, and documentation of transformations. Persistent identifiers and version control improve traceability. Sensitive data may require data-use agreements, secure environments, researcher authentication, or review by an access committee.

De-identification is not equivalent to anonymity. When datasets contain many variables, individuals may be reidentified by linking them with other sources. Researchers should therefore evaluate contextual risks, not merely remove names and identification numbers. Small groups, rare occupations, geographic detail, and distinctive events can create substantial disclosure risks.

Open code refers to the sharing of scripts, notebooks, workflows, and computational environments used to generate findings. It strengthens reproducibility by revealing operational decisions that may be invisible in a published article. Good practice includes meaningful file names, comments, dependency specifications, version information, test data, and instructions for execution. Code can itself create risks: it may contain credentials, proprietary algorithms, malware vulnerabilities, or tools that enable harmful use. Security review is therefore part of responsible code sharing.

Replication is the attempt to examine whether a finding can be obtained again. A direct replication seeks to reproduce the original procedures as closely as possible, whereas a conceptual replication tests the underlying proposition using different operationalizations or contexts. Replications are not merely quality-control exercises. They can reveal boundary conditions, cultural variation, measurement weakness, and the difference between statistical reproducibility and theoretical generalizability.

A failed replication should not automatically be interpreted as proof that the original study was invalid. Differences in samples, implementation, statistical power, incentives, and context may explain divergent outcomes. Responsible reporting presents uncertainty and investigates explanations rather than treating replication as a simple pass-or-fail test.

Openness, Commercialization and Confidentiality

Business research frequently involves private firms, proprietary processes, trade secrets, customer information, strategic plans, and contractual restrictions. Commercialization can also create legitimate interests in patent protection, licensing, and competitive advantage. These interests do not eliminate research-ethics obligations, but they require careful governance.

A confidentiality agreement should not be used to conceal fabricated results, serious participant harm, or conflicts that would mislead readers. Researchers must clarify before data collection which information may be published, who owns research outputs, whether sponsors can review manuscripts, and whether the sponsor can delay publication. Contractual terms should preserve academic independence and the right to report unfavorable findings.

A proportionate governance arrangement may include:

  • public release of the study protocol and analysis plan;
  • release of non-sensitive metadata and synthetic or aggregated data;
  • controlled access to sensitive records;
  • publication of code after removal of proprietary components;
  • an embargo limited to a defensible intellectual-property period;
  • independent review of disclosure and conflict-of-interest risks.

Commercial sensitivity must be distinguished from inconvenience. A firm’s preference that competitors not learn an ordinary research finding is not automatically a sufficient reason to suppress evidence. Conversely, disclosure of a trade secret, security vulnerability, or identifiable employee information may be ethically and legally unjustifiable. Governance should document the competing interests and the reasons for each restriction.

A Governance Model for Digitally Enabled Research

A useful model is the CLEAR framework: Clarify, Limit, Explain, Audit, and Reassess.

Clarify the research purpose, data sources, stakeholders, ownership arrangements, legal basis, and anticipated public value. Researchers should identify whether the project is exploratory, confirmatory, commercial, operational, or mixed in purpose.

Limit collection and access to what is necessary. Data minimization, purpose limitation, role-based permissions, encryption, secure storage, and retention schedules reduce exposure. The same principle applies to autonomous systems: an agent should receive only the permissions needed for its task.

Explain decisions through preregistration, documentation, consent language, data-management plans, model cards, risk assessments, and statements of deviations. Explanation should be understandable to relevant stakeholders, not merely technically correct.

Audit the research process and its outputs. Audits may examine data provenance, access logs, code dependencies, model performance, bias, security, consent compliance, and publication integrity. Internal review should be supplemented, where risk warrants it, by independent assessment.

Reassess the project as circumstances change. A dataset may become reidentifiable, a vendor may change its terms, a model may be deployed beyond its original purpose, or a new vulnerability may emerge. Ethical approval should not be treated as a one-time administrative event.

This framework complements established principles such as respect for persons, beneficence, justice, integrity, accountability, and respect for communities. It also reflects responsible innovation, which asks not only whether an innovation can be implemented, but whether its purposes, consequences, distribution of benefits, and distribution of risks are acceptable.

Synthetic Data and Federated Analytics

Synthetic data are generated records designed to reproduce selected statistical properties of an original dataset without directly reproducing every individual record. They can support software testing, teaching, exploratory analysis, and controlled data sharing. Synthetic data may reduce disclosure risk, but they are not automatically safe. If the generation model memorizes unusual cases or reproduces rare combinations, individuals may remain vulnerable. Synthetic data may also preserve historical discrimination or distort relationships that researchers need to study.

A synthetic dataset should therefore be assessed for utility, fidelity, privacy, and bias. Documentation should state how it was generated, which variables were retained, what transformations occurred, and what analyses it cannot support. Synthetic data should not be presented as equivalent to the original evidence.

Federated analytics allows multiple organizations to analyze data without transferring raw records to a central repository. Computation occurs near the data, and only approved summaries, parameters, or model updates are shared. This architecture can be valuable in health, finance, supply-chain, and multinational business research where legal or organizational barriers limit data pooling.

Federation does not remove governance risk. Shared outputs may permit reconstruction attacks; participating institutions may have unequal technical capacity; local data may be inconsistent; and a central coordinator may exercise excessive control. Governance should address participant consent, permitted queries, output checking, security, responsibility for errors, and withdrawal procedures. Privacy-enhancing technologies such as differential privacy, secure multiparty computation, and encryption can reduce risk, but each introduces trade-offs in accuracy, complexity, and interpretability.

Autonomous Research Agents and Algorithmic Accountability

Autonomous research agents are software systems that can plan tasks, search literature, write or execute code, collect information, run analyses, and propose interpretations with limited human intervention. Their use may accelerate systematic reviews, data preparation, simulation, and hypothesis generation. It also raises a fundamental accountability question: responsibility cannot be delegated to a machine.

An agent may hallucinate sources, misinterpret variables, introduce hidden changes into code, use copyrighted material improperly, expose confidential data, or optimize for a proxy that differs from the research objective. In business settings, an agent might prioritize speed or predictive accuracy while ignoring fairness, explainability, or stakeholder harm.

Responsible deployment requires human authorization at consequential decision points, restricted system permissions, logging of prompts and outputs, reproducible environments, source verification, testing against adversarial cases, and clear attribution of human responsibility. Agents should not be permitted to submit manuscripts, contact participants, alter datasets, or disclose sensitive information without appropriate review. The use of an agent should be disclosed when it materially affects research design, analysis, or interpretation.

Illustrative Case: The Meridian Workforce Analytics Project

Background

Meridian, a fictional multinational logistics company, partners with a university doctoral researcher to study employee turnover. The company offers access to five years of workforce records, including role, location, performance ratings, absence data, compensation, and resignation status. Meridian hopes to commercialize a retention-prediction tool.

Situation and Problem

The research team wishes to preregister its hypotheses and publish code. Meridian agrees to publication but refuses to release raw data because of privacy, employment-law, and competitive concerns. The company also proposes an autonomous agent to generate candidate predictors and asks to approve the final manuscript before submission.

Analysis

The team identifies several risks. Employees may not reasonably expect their employment records to be used for doctoral research or commercial product development. Combining location, job history, and absence patterns could reidentify individuals. Performance ratings may encode managerial bias. An unrestricted prediction system could influence promotion or dismissal without adequate explanation. The sponsor’s proposed manuscript veto could compromise academic independence.

Approach and Strategy

The parties adopt a layered governance plan. The study protocol, hypotheses, sampling logic, and analysis plan are preregistered. Raw data remain in a secure environment with role-based access. Researchers receive only pseudonymized records, and outputs are checked for small-cell disclosure. The team publishes a synthetic teaching dataset, data dictionaries, model documentation, and code that excludes proprietary infrastructure. A controlled-access process is created for qualified researchers.

The autonomous agent is restricted to feature suggestions and code drafting. Every suggested variable is reviewed for necessity, fairness, and leakage of future information. All executions are logged, and no agent-generated result is accepted without human verification. Meridian may check factual claims and confidential details but cannot suppress results solely because they are commercially unfavorable. A separate committee reviews employment-impact risks before any operational deployment.

Outcome

The research produces a transparent academic article and a more limited commercial prototype. The prototype is not used for automatic employment decisions. The study reveals that a seemingly strong predictor is largely a proxy for managerial unit and therefore is removed. The parties also discover that predictive accuracy decreases substantially for smaller regional groups, preventing unjustified claims of universal performance.

Learning Points

The case demonstrates that openness is not identical to raw-data publication. Meaningful transparency can be achieved through preregistration, controlled access, documentation, synthetic data, code sharing, and audit trails. It also shows that commercialization should be governed through role separation, publication rights, conflict disclosure, and restrictions on high-impact deployment. Finally, autonomous tools increase the need for human accountability rather than reducing it.

Challenges and Common Mistakes

One common mistake is treating a repository upload as reproducibility. Without documentation, versioning, and a usable environment, an uploaded file may be practically inaccessible. A second mistake is assuming that anonymization is permanent. Reidentification risk changes as external datasets and computational techniques develop.

Researchers may also preregister analyses so vaguely that the registration provides little constraint, or they may present exploratory results as if they were confirmatory. Another error is releasing code containing passwords, personal information, or unlicensed material. Commercial partners may impose broad confidentiality clauses that unintentionally prevent independent scrutiny. Finally, governance may focus on initial ethics approval while neglecting changes in data use, model deployment, or stakeholder impact.

Open science can reproduce inequality. Well-funded institutions may have superior repositories, data engineers, legal support, and computational infrastructure. Researchers in low-resource settings may bear the cost of compliance while their data are extracted and reused by better-resourced organizations. Justice therefore requires attention to benefit sharing, credit, community expectations, and equitable participation.

Professional and Organizational Best Practices

A doctoral research team should establish a data and openness plan at the proposal stage. The plan should specify data ownership, consent boundaries, repository choice, access levels, retention, licensing, code management, authorship, conflicts of interest, and procedures for correcting errors. Research teams should use version control, persistent identifiers, reproducible environments, and contribution records.

Organizations should maintain data-classification policies, secure research environments, access logs, incident-response procedures, and independent ethics or governance review for high-risk projects. Contracts with sponsors should preserve methodological independence and publication rights. Training should cover privacy, security, intellectual property, responsible AI, and the difference between legal compliance and ethical adequacy.

Audits should be risk-based rather than purely procedural. A low-risk public survey may need basic documentation, whereas a federated system using employment or health data may require technical penetration testing, privacy assessment, fairness analysis, stakeholder consultation, and continuing oversight. Audit findings should lead to corrective action, not merely archival reports.

Current Developments and Future Research Governance

Research governance is moving toward continuous oversight. Digital systems can automatically record data lineage, code changes, access events, model versions, and analytical outputs. Such provenance systems support investigation when results change or errors are discovered. At the same time, automated compliance checks must not replace human judgment, especially where values and contested social meanings are involved.

Emerging governance debates concern foundation models, machine-generated scholarship, cross-border data flows, algorithmic intellectual property, environmental costs of computation, and the status of research participants whose data are reused for purposes not imagined at collection. Future frameworks are likely to combine privacy engineering, institutional review, technical auditing, community participation, and sector-specific regulation.

Responsible innovation provides a valuable orientation for this future. It emphasizes anticipation of consequences, inclusive deliberation, reflexivity about assumptions, and responsiveness to evidence. For business researchers, this means assessing not only whether a digital research system produces valid predictions, but also who controls it, who benefits, who bears risk, whether affected people can contest decisions, and whether the system can be withdrawn safely.

Chapter Summary

Open science improves research transparency through practices such as preregistration, registered reports, open data, open code, and replication. These practices clarify the distinction between confirmatory and exploratory analysis, support reproducibility, and strengthen cumulative knowledge, but they do not eliminate methodological or ethical risks. Data and code must be shared proportionately, with attention to privacy, security, intellectual property, commercialization, and participant expectations.

Synthetic data and federated analytics can expand access while reducing the need to transfer sensitive records, but neither guarantees privacy or validity. Autonomous research agents can assist with complex scholarly tasks but require restricted permissions, logging, human verification, and clear accountability. The CLEAR framework—Clarify, Limit, Explain, Audit, and Reassess—provides a practical governance approach. Responsible innovation extends this framework by asking how benefits, risks, voice, and control are distributed. Future research governance will depend on continuous auditing, technical safeguards, institutional oversight, and meaningful stakeholder participation.

Key Terms

Preregistration: Public documentation of a research plan before analysis or data collection.

Registered report: A peer-reviewed research protocol accepted in principle before results are known.

Open data: Research data made available for inspection or reuse under appropriate conditions.

Open code: Publicly shared scripts, software, and computational workflows used in research.

Replication: A study designed to examine whether a prior finding can be obtained again.

Direct replication: Replication that closely follows the original study’s procedures.

Conceptual replication: Testing the same theoretical proposition using different methods or measures.

Data provenance: The documented history and origin of data, including transformations and uses.

De-identification: Removal or alteration of direct identifiers to reduce identification risk.

Synthetic data: Artificially generated data designed to reproduce selected properties of real data.

Federated analytics: Distributed analysis in which raw data remain at participating institutions.

Differential privacy: A mathematical approach limiting what can be inferred about an individual from released results.

Autonomous research agent: Software capable of performing research tasks with limited human intervention.

Responsible innovation: An approach emphasizing anticipation, inclusion, reflexivity, and responsiveness.

Research audit: A systematic examination of research processes, records, controls, or outputs.

Data minimization: Collecting and retaining only data necessary for a legitimate purpose.

Controlled access: A system in which approved users obtain data under defined conditions.

Publication bias: Distortion caused when publication depends on positive, significant, or attractive results.

Audit trail: A chronological record of decisions, changes, access, and system activity.

Review Questions

Short Answer Questions

1. What is the principal purpose of preregistration?

2. How does a registered report differ from ordinary preregistration?

3. Why is de-identification not equivalent to anonymity?

4. Define federated analytics.

5. What does the “as open as possible, as closed as necessary” principle require?

Long Answer Questions

1. Critically evaluate the contribution of open data and open code to research reproducibility.

2. Discuss the ethical tensions between open science, commercialization, confidentiality, and academic independence.

3. Explain the CLEAR framework and show how it can govern a digitally enabled research project.

4. Compare synthetic data and federated analytics as strategies for handling sensitive research data.

5. Examine the accountability challenges created by autonomous research agents.

Analytical / Application Questions

1. A company provides employee data for a doctoral study but prohibits publication of unfavorable findings. Design a governance arrangement that protects confidentiality while preserving research integrity.

2. A synthetic dataset produces excellent statistical similarity but disproportionately reproduces errors affecting a minority group. Should it be released? Explain the assessments and safeguards required.

3. A research agent writes and executes analysis code for a high-impact business study. Develop an audit and human-review protocol before the results are published or used operationally.

22. Multiple Choice Questions with Answers

Question 1

What is the primary ethical purpose of preregistration?

A. To guarantee statistically significant findings

B. To distinguish planned confirmatory analyses from later exploratory analyses

C. To prevent researchers from changing any method

D. To replace peer review

Correct Answer: B. To distinguish planned confirmatory analyses from later exploratory analyses

Question 2

Which feature most clearly distinguishes a registered report from ordinary preregistration?

A. It requires that all data be publicly released

B. It is reviewed and accepted in principle before results are known

C. It can only be used for qualitative studies

D. It guarantees that the hypothesis will be supported

Correct Answer: B. It is reviewed and accepted in principle before results are known

Question 3

Which practice best supports meaningful open-data reuse?

A. Uploading an unexplained spreadsheet

B. Publishing only statistically significant variables

C. Providing a data dictionary, provenance, transformations, and access conditions

D. Removing all documentation to protect the sponsor

Correct Answer: C. Providing a data dictionary, provenance, transformations, and access conditions

Question 4

Why may a dataset with names removed still present reidentification risks?

A. Names are never useful identifiers

B. External data can be linked with distinctive combinations of variables

C. Encryption automatically reveals identities

D. Synthetic data always contain names

Correct Answer: B. External data can be linked with distinctive combinations of variables

Question 5

A commercial sponsor wants to review a manuscript. Which arrangement best protects research integrity?

A. The sponsor may suppress unfavorable findings without explanation

B. The sponsor may check confidential facts but not veto results solely for commercial reasons

C. The researcher must remove all negative findings

D. The sponsor becomes the sole author

Correct Answer: B. The sponsor may check confidential facts but not veto results solely for commercial reasons

Question 6

Which statement about synthetic data is most accurate?

A. Synthetic data are automatically anonymous and unbiased

B. Synthetic data eliminate the need for ethical review

C. Synthetic data require assessment of privacy, utility, fidelity, and bias

D. Synthetic data are always equivalent to original observations

Correct Answer: C. Synthetic data require assessment of privacy, utility, fidelity, and bias

Question 7

What is a central characteristic of federated analytics?

A. All raw data are transferred to one public database

B. Analysis occurs near local data and approved outputs are shared

C. No security controls are required

D. Participating institutions lose all responsibility for results

Correct Answer: B. Analysis occurs near local data and approved outputs are shared

Question 8

Which control is most appropriate when using an autonomous research agent?

A. Allowing unrestricted access to all institutional systems

B. Removing logs to protect the agent’s confidentiality

C. Restricting permissions and requiring human verification of consequential outputs

D. Treating the agent as the responsible author

Correct Answer: C. Restricting permissions and requiring human verification of consequential outputs

Question 9

Under the CLEAR governance framework, what does “Reassess” mean?

A. Repeating the original literature search only

B. Reviewing the project when circumstances, risks, or uses change

C. Deleting all data after publication

D. Avoiding any change to the approved protocol

Correct Answer: B. Reviewing the project when circumstances, risks, or uses change

Question 10

A failed replication should generally be interpreted as:

A. Automatic proof of fraud in the original study

B. Evidence requiring examination of context, implementation, power, and theory

C. Proof that replication is unnecessary

D. A reason to suppress the replication report

Correct Answer: B. Evidence requiring examination of context, implementation, power, and theory

Research Ethics & Computer Applications
Chapter 15 of 15