| Course | GB891 Doctoral Project II: Project Design and Implementation |
|---|---|
| Unit | Unit 5 |
| Paper type | Pilot test summary |
| Length | About 880 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for GB891 Unit 5
Three Problems Found Before Any Real Data: A Unit 5 Pilot Test Summary for a Bakery Safety Study
[Student Name]
Purdue University Global
GB891: Doctoral Project II: Project Design and Implementation
Unit 5 Pilot Test Summary
[Instructor Name]
[Date]
Corliss Baking Company, its pilot plant and every figure are composite and illustrative; the methods sources cited are real.
What the Pilot Was For
A pilot study is not a small version of the main study, and its results say nothing about whether the intervention works. Leon et al. (2011) argue that pilot studies should be used to test feasibility, the procedures, instruments and logistics a full study will depend on, and that effect sizes estimated from a pilot are too imprecise to guide anything. This pilot was designed accordingly. It asked three questions: do associates understand the pulse items as intended, can observers agree on the observation definitions, and can associates use the near-miss form?
Methods
The pilot ran for three weeks on two crews at the Jasper plant, the company's fifth bakery, which is excluded from the main study. The research assistant ran three weekly pulse cycles on both crews, drawing four members per crew each week. The two observers conducted nine joint observation sessions across the five stations, recording independently. And the assistant conducted cognitive interviews with seven associates, in which each person talked through their reasoning while answering the pulse items and the survey and then restated each question as they understood it, an approach Willis (2005) describes for finding where respondents' understanding departs from the designer's intent.
Finding One: The First Pulse Item
The first pulse item, in version 1.0, asked: "How many times this week did your supervisor talk about safety?" Scores were high on both crews, averaging more than four occasions a week. The cognitive interviews explained why. Five of the seven associates counted the mandatory stretch-and-flex routine at the start of every shift, which the supervisor leads and which includes a sentence about working safely. By that count, every supervisor talked about safety at least five times a week, and the item could not distinguish supervisors who raised safety at other times from those who did not.
Revision. Version 1.1 asks: "Outside the start-of-shift meeting, how many times this week did your supervisor bring up safety with you or your crew?" In the third pilot week, with the revised item, average scores fell to about one occasion a week and varied between associates in a way that matched what the observers had seen.
Finding Two: Agreement on Jam Clearing
Observers agreed well at four stations, with kappa values in the range Landis and Koch (1977) describe as substantial or better. At the jam-clearing station on the packaging line, they agreed in only 61 percent of intervals, and kappa was low. The disagreement came from the definition. Version 1.0 described safe jam clearing as stopping the line and using the clearing tool. Observers disagreed about intervals in which an associate stopped the line but reached in briefly before picking up the tool, and about intervals in which the line had already stopped for another reason.
Revision. Version 1.1 narrows the definition to hand position at the moment the line stops: an interval is safe if, when the line comes to a stop, the associate's hands are outside the guard and the tool is in hand or within reach. In six further joint intervals at the end of the pilot, the observers agreed in all six, which is encouraging but too few to establish reliability; agreement will be checked again in the first week of the main study.
Finding Three: The Near-Miss Form
Corliss's near-miss form was accessed by scanning a QR code posted at each station. Version 1.0 asked for the associate's badge number, name, shift, station, a description and a suggested fix. Associates at the pilot plant took about four minutes to complete it, and three of the seven interviewed said they would not use it because the badge number made them identifiable. The form defeated the purpose the framework assigns to near-miss reporting, which depends on associates believing reports are welcome and safe.
Revision. Version 1.1 has five fields, station, shift, what happened, what could have happened and a suggestion, and no identifier. It takes under two minutes on a phone.
The near-miss form asked for the one piece of information that made associates unwilling to fill it in.
What the Pilot Could Not Test
The pilot could not test whether the feedback sheets change supervisors' behavior, because three weeks with two crews is far too short and too small, and because testing the intervention was never its purpose. It could not test how the procedures hold up under high turnover, because the pilot crews happened to be stable during those three weeks. And it could not test the Haitian Creole materials, since no pilot associates spoke that language. These limits are carried into the main study as risks to be watched, not as problems solved.
Changes Carried Into the Protocol
All three revisions are recorded in the protocol's change log with the date and reason, and the version numbers on every instrument have been updated to 1.1 before the main study begins.
References
Landis, J. R., & Koch, G. G. (1977). The measurement of observer agreement for categorical data. Biometrics, 33(1), 159-174. https://doi.org/10.2307/2529310
Leon, A. C., Davis, L. L., & Kraemer, H. C. (2011). The role and interpretation of pilot studies in clinical research. Journal of Psychiatric Research, 45(5), 626-629. https://doi.org/10.1016/j.jpsychires.2010.10.008
Willis, G. B. (2005). Cognitive interviewing: A tool for improving questionnaire design. SAGE.
The Purdue Global GB891 Unit 5 instructions
Unit 5 in GB891 asks you to summarize your pilot test and what it changed. Begin by stating what the pilot was for, which is feasibility rather than effect, and cite a source on the purpose of pilots. Describe the pilot's methods: where, with whom, for how long and what was tested. Then report findings instrument by instrument, explaining what the problem was and how you discovered it. For each problem, state the revision and, where possible, show that the revised version worked better. Report observer agreement with a recognized statistic. Describe what the pilot could not test and how you will watch for those problems in the main study. Close with how the changes were recorded in the protocol. About six pages with a revision table listing each instrument, problem, revision and version number is a common format.
How the GB 891 Unit 5 example is put together
The summary opens with Leon and colleagues' point that pilots test feasibility, not effects. Methods describe two crews at Jasper, three pulse cycles, nine joint observation sessions and seven cognitive interviews following Willis. Finding one shows high scores on the first pulse item because five of seven associates counted the stretch routine; version 1.1 excludes the meeting and scores fell, as a margin note explains. Finding two reports kappa in the substantial range at four stations under Landis and Koch, but 61 percent agreement at jam clearing, fixed by a narrower definition. Finding three, the highlighted sentence, removes the badge number from the near-miss form. Limits and the change log close it.
Where the points sit in the GB891 Unit 5 rubric
The GB891 pilot summary is graded on what it changed. Instructors expect the pilot's purpose framed as feasibility, with a supporting source. Methods should be specific enough to show what was tested. Each finding earns credit when the summary explains how the problem was discovered, for example through cognitive interviews. Revisions should be concrete, and evidence that a revised version worked better is weighted. Observer agreement reported with a recognized statistic, and interpreted against benchmarks, shows rigor. Stating what the pilot could not test, and carrying those gaps into the main study as risks, demonstrates honesty. Recording changes with version numbers shows the protocol was updated. Sources should be cited accurately throughout the summary.
GB891 Unit 5 help from the desk
Many GB891 pilot summaries report that everything went well, which usually means the pilot tested too little. Others report a pilot effect size as if it predicted the main study's result. Students often describe problems without saying how they were found. Revisions are stated without any evidence that they fixed the problem. Observer agreement is reported as a percentage without a chance-corrected statistic. Limits are skipped. Frame the pilot as feasibility, describe exactly what was tested, explain how each problem surfaced, revise concretely, show the revision helped, report agreement with kappa, state what the pilot could not test and record version changes. If your pilot is complete, our writers can help you summarize it.
Get a GB891 Unit 5 example written to your instructions
Instruments, pilot notes and any figures available, however rough, give a writer enough to work with, alongside your Unit 5 prompt and rubric. Returned within 24-48h, the summary reports each problem the pilot exposed, the evidence and the numbered revision. A first custom sample is free of charge. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More GB891 papers and MBA samples
- GB891 Unit 1: Protocol Document
- GB891 Unit 2: Consent Language Draft
- GB891 Unit 3: Review Board Application
- GB891 Unit 4: Recruitment Plan
- GB891 Unit 6: Seminar Reflection
- GB891 Unit 7: Collection Log
- GB891 Unit 8: Fidelity Monitoring Memo
- GB891 Unit 9: Deviation Report
- GB891 Unit 10: Implementation Chapter Draft
- GB890 Unit 5: Literature Synthesis
- GB815 Unit 5: Data Source Audit
- GB500 Unit 5: Market Structure Case
- GB794 Unit 5: Measurement Validity Review
GB891 Unit 5 questions, answered
What if my pilot found no problems?
Look again at what it measured. A pilot that finds nothing often tested too little: too few participants, too short a period, or no check on agreement or understanding. If it genuinely ran cleanly, report what was tested and the evidence it worked, such as agreement figures or cognitive interview results, and state what remains untested.
Can pilot participants join the main study?
Generally they should not, because exposure to earlier versions of the instruments can change later answers, and some designs treat pilot sites as contaminated. Running the pilot at a site or group outside the study, as the Corliss sample does with its fifth plant, avoids the problem. Your design and review board determine what is acceptable.
Do instrument changes after a pilot need approval?
Often, if the review board approved the original instruments. Changes to wording, procedures or consent documents typically go back as an amendment before use. Your board's rules decide, and the summary should say which revisions need submission and leave their status for you to record rather than assuming approval.
Where can I find a free GB891 Unit 5 sample paper?
This page carries a full GB891 Unit 5 pilot test summary for a bakery safety study, reporting three instrument problems found in a three-week pilot and the revision each forced.
What is a cognitive interview?
It asks respondents to think aloud while answering a question and to explain what they understood it to ask. It reveals where people interpret an item differently from what the researcher intended.