RES 728 Week 3 Case Study Protocol Example

Reviewed by Davina Cresswell, MBA · University of Phoenix · Updated

This RES 728 Week 3 example writes a case study protocol, the document that keeps data collection consistent across several cases and makes a multiple case study reliable and auditable. University of Phoenix RES 728 develops a case study protocol in Week 3, and RES/728 asks DBA learners to set out the study overview, field procedures, protocol questions and a report outline, plan a case study database and chain of evidence and test the protocol in a pilot. The protocol serves the composite Cincinnati HR vice president's multiple case study of how three Ohio firms that became employee-owned build ownership culture. The paper presents each protocol section with examples, distinguishes questions for the investigator from questions for interviewees, maps sources to propositions, describes the database and reports what a pilot visit changed.

CourseRES 728 Qualitative Case Study (RES/728)
Week3
Paper typeDoctoral case study protocol
Lengthabout 1,151 words, 4 double-spaced pages plus title page and references
FormatAPA 7 student paper
SchoolUniversity of Phoenix
ProgramDBA
UpdatedOctober 2026

Free sample paper for RES 728 Week 3

1

The Same Study Three Times: A Case Study Protocol for Three Employee-Owned Firms

[Student Name]

University of Phoenix

RES/728: Qualitative Case Study

Week 3 Assignment

[Instructor Name]

[Date]

The learner, the companies and the planned study are composites written for a model paper.

What this part is doingThe title captures the protocol's purpose: doing the same study consistently at each site.
2

Week 2 bounded three cases for the composite Cincinnati HR vice president's study: a Toledo distributor, a machining firm near Lancaster and a Columbus engineering firm, all employee-owned through an ESOP. Studying three firms in different towns, industries and sizes raises a practical risk: collecting different kinds of data in different ways at each site, which would make comparison unreliable. A written protocol addresses that risk directly and visibly.

Why a Protocol

Yin (2018) describes the protocol as a major way of increasing the reliability of case study research, especially in multiple case studies, and recommends four sections: an overview of the study, data collection procedures, protocol questions and a tentative outline for the case study report. The protocol is addressed to the investigator, not to participants, and reminds the researcher what the study is about at every site.

Gibbert et al. (2008) reviewed case studies published in leading management journals and found that many reported little about how they addressed reliability and validity; the more rigorous studies described a protocol, a database and procedures in enough detail for others to follow. Their review gives the protocol a further purpose: making the study's rigor visible to reviewers.

What this part is doingCiting evidence that published case studies often under-report rigor shows why the protocol matters.
3

Section 1: Overview

The overview states the purpose, to learn how ESOP conversions in Ohio turn into an ownership culture and why the results vary; the three research questions; the three propositions about information, control and differences among employee groups; and the case selection logic. It lists key readings on psychological ownership and the pieces of ownership, and a one-page background on each firm: industry, size, conversion date and ownership history.

Section 2: Field Procedures

Access: a signed letter from each CEO granting access to employees, meetings and documents, and agreeing that employees may decline without consequence.

Contacts: one liaison at each firm, usually an HR manager, who schedules but does not choose participants.

Scheduling: interviews and focus groups spread across shifts so front-line employees can take part during paid time.

Consent: individual consent forms; a script explaining that the firm will not see who said what.

Site kit: protocol, consent forms, two recorders, observation template, document request list.

Daily log: after each site day, a short summary of what was collected and what remains.

Section 3: Protocol Questions

Protocol questions are what the investigator needs to learn, not what she will ask employees. Each is linked to sources.

What practices share financial or performance information, with whom, how often and in what form? Sources: leader interviews, documents such as meeting slides, observation of an all-company meeting.

How do employees in each group describe their understanding of company performance? Sources: employee interviews, focus groups.

What decisions can employees influence, and through what channels? Sources: leader and employee interviews, committee charters, meeting minutes.

How do employees in each group describe what being an owner means to them? Sources: interviews, focus groups.

How has the ESOP been explained since conversion? Sources: ESOP education materials, trustee interview, onboarding documents.

What events since conversion have strengthened or weakened ownership feeling? Sources: leader and employee interviews, newsletters.

The investigator asks herself what practices share information; she asks employees to tell her about the last time they saw the company's numbers.

Mapping Sources to Propositions

A matrix lists each proposition against each source. For P1, on information sharing, every source contributes: documents show what is shared, observation shows how, interviews and focus groups show how employees understand it. For P3, on differences among employee groups, interviews and focus groups are central, with sampling within each firm designed to include all three groups. The matrix shows no proposition depends on a single source.

Section 4: Report Outline

Each case report follows the same outline so cases can be compared: firm background and conversion; ownership practices, organized by wealth, information and control; employees' experiences, by group; how practices and experiences relate; and how the case bears on each proposition. Cross-case analysis in Week 7 will draw on these parallel reports.

What this part is doingA shared report outline turns three separate studies into one comparison.
4

Case Study Database

Rowley (2002) emphasizes that case researchers should organize evidence so it can be retrieved and examined, separately from the researcher's report. The database will hold transcripts, field notes, documents, the daily logs and memos in folders by firm and source type, with each item coded by date, firm, source and embedded unit. A spreadsheet index lists every item with a short description, so the learner, her committee or a later researcher can find any piece of evidence quickly.

Chain of Evidence

Every claim in the final report will cite items in the database, which link to protocol questions, which link to research questions and propositions. A reader should be able to move from a conclusion back to the evidence and from a research question forward to the conclusion.

Pilot Visit

A one-day pilot at a fourth employee-owned firm, a printing company outside the study, tested the protocol. Four revisions followed. Front-line employees could not attend interviews during peak production, so interviews were moved to shift overlaps. The document request list was too long for a small HR team and was cut to essentials. One protocol question about "governance" confused leaders, who associated the word with the board, so it was reworded around decisions in daily work. And the observation template lacked space for who spoke in meetings, which the pilot showed was revealing.

Keeping the Protocol Current

Fieldwork will reveal issues the pilot did not. Any change to the protocol after the first firm visit will be dated, explained in a memo and, where possible, applied at the firms already visited through follow-up calls or document requests. The version used at each firm will be stored in the database. This prevents the protocol from drifting so far between sites that the cases are no longer comparable.

Sequencing the Three Sites

The learner will visit Firm C, the mixed case, first, then Firm A and Firm B. Starting with the case expected to show internal contrast lets her refine questions about employee groups before visiting the polar cases. Each firm will receive two site visits, spaced about six weeks apart: the first for leader interviews, observation and document collection, the second for employee interviews and focus groups, informed by what the first visit had revealed about the firm.

Ethics at Each Site

Because leaders arrange access, employees may fear that participation or comments will be reported. The protocol requires that the liaison not choose participants, that interviews occur away from supervisors and that quotations in reports be attributed only to an employee group. The trustee's interview will avoid any discussion of individual accounts.

Conclusion

The protocol's overview, field procedures, investigator questions mapped to sources, report outline, database and chain of evidence make data collection at three firms consistent and traceable. A pilot visit improved scheduling, document requests, wording and observation. Week 4 will plan the individual interviews.

5

References

Gibbert, M., Ruigrok, W., & Wicki, B. (2008). What passes as a rigorous case study? Strategic Management Journal, 29(13), 1465-1474. https://doi.org/10.1002/smj.722

Rowley, J. (2002). Using case studies in research. Management Research News, 25(1), 16-27. https://doi.org/10.1108/01409170210782990

Yin, R. K. (2018). Case study research and applications: Design and methods (6th ed.). Sage.

What the RES 728 Week 3 instructions ask

Week 3 of RES 728 has doctoral learners develop a case study protocol. Prompts usually ask for an overview of the study with purpose, questions, propositions and key readings; field procedures covering access, scheduling, consent and materials; protocol questions that guide the investigator, linked to data sources; a tentative outline for each case report; and plans for a case study database and chain of evidence. Some versions require a pilot case or a matrix linking sources to propositions. Write the protocol for the learner's own cases, show how it supports reliability and consistency across sites, cite case study methodologists in APA and explain what the protocol allows another researcher to repeat.

How this RES 728 Week 3 example is built

Our sample paper builds the protocol in four sections recommended by the leading case study text. The overview restates three questions and three propositions about sharing information, control and wealth. Field procedures cover CEO agreements, scheduling across shifts, consent and a site kit. Protocol questions are addressed to the investigator, such as "What practices share financial information, with whom and how often?", each linked to interviews, focus groups, observation and documents. A report outline keeps the three case reports parallel. Drawing on research on what makes case studies rigorous and a practical guide to case research, the protocol adds a database and a chain of evidence, and a pilot visit to a fourth firm prompted four revisions.

RES 728 Week 3 grading rubric: where the points go

Doctoral graders reward protocols that are complete and usable. Strong papers include an overview, field procedures, protocol questions linked to sources and a report outline, and explain how the protocol supports reliability and consistency across cases. Credit goes to distinguishing questions the investigator must answer from questions asked of participants, to mapping sources against propositions, to a clear database and chain of evidence and to revisions based on a pilot. Graders also value attention to ethics and logistics at each site and a plan for keeping the protocol current as revisions are made during fieldwork. Case study methodology cited in APA supports the protocol.

RES 728 Week 3 help: mistakes to avoid

Protocol papers often present an interview guide and call it a protocol. A protocol is broader: it tells the researcher what to find out, from which sources, at every site. Another frequent gap is protocol questions that cannot be traced to research questions or propositions; map each one. Learners also omit field procedures, then improvise at each site, which weakens comparability. Some papers forget the case study database; decide now how notes, transcripts and documents will be stored and linked. Finally, pilot the protocol at a site outside the study. Date every version of the protocol. A tutor can help you turn your interview guide into a full protocol.

Related RES 728 sample papers

Other RES 728 week samples

More DBA sample papers

RES 728 Week 3 questions, answered

What does RES 728 Week 3 usually cover?

It usually covers the case study protocol: study overview, field procedures, protocol questions, report outline, case study database and chain of evidence.

Where can I find a free RES 728 Week 3 sample paper?

This page carries the full RES 728 Week 3 protocol for three ESOP companies, with no charge.

What is a case study protocol?

A document guiding data collection across cases, including the study overview, field procedures, questions for the investigator and a report outline.

What is a chain of evidence?

Explicit links from research questions to protocol questions, data sources, the case study database and conclusions, so readers can trace any claim.

Why pilot a case study protocol?

To test questions, procedures and logistics at a site outside the study and revise the protocol before collecting data.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.