| Course | GM599 Applied Research Project |
|---|---|
| Unit | Unit 6 |
| Paper type | Seminar reflection |
| Length | About 820 words, 5 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Management |
| Updated | October 2026 |
Free sample paper for GM599 Unit 6
Waiting on Someone Else's Records: A Unit 6 Seminar Reflection at the Capstone's Midpoint
[Student Name]
Purdue University Global
GM599: Applied Research Project
Unit 6 Seminar Reflection
[Instructor Name]
[Date]
Wexmoor Regional Transit and the classmates are composite; the sources cited are real.
The Status Round
The seminar opened with each of us reporting where our capstone stood. Mine: I have seven years of road supervisor posting records from human resources, with names removed. Payroll's earnings bands, which I need to compare operator and supervisor pay, have been in the agency's legal review for three weeks. The survey of 141 eligible operators is drafted and pretested but not launched, because I had planned to wait for the payroll bands so I could check the survey's earnings questions against them. I have not started interviews.
As the round went on, I realized that most classmates were in the same position: waiting on an employer for data, with the rest of the project held behind it.
Two Exchanges
The first came from Danielle, who works in county government. When I described the payroll delay, she pointed out that public agencies often publish their salary schedules and union wage scales, sometimes in board meeting packets. The road supervisor pay range and the operator wage scale might already be public. Overtime earnings would still need payroll's bands, but the basic comparison, a top operator's hourly rate with overtime against a supervisor's salary, could be built from public documents.
The second came from the instructor. My plan still compared the three garages, by marking each garage's paper return envelopes with a different code. She asked how many survey responses I expected from 141 operators, and how many I would need for that comparison. I said I hoped for half, about 70. She asked how many that would be per garage. About 23. And how many of those would be in each tenure band? I did the arithmetic and said honestly that the numbers would be too small to compare anything by garage, and that coding envelopes by garage would quietly reintroduce the identification risk the method had removed by leaving garage off the questionnaire.
I had been holding the whole project behind one delayed data source, and the garage comparison I had planned was one the survey could never support.
Why I Had Not Seen It
Looking back, both mistakes came from treating the method as a fixed sequence rather than a set of choices. I had written that the survey would follow the records, and I read that as meaning every record had to arrive first. And I had listed garage comparisons as a goal in my first proposal, before I knew how many operators were eligible, and never rechecked it against the numbers. Don Dillman and colleagues warn that survey designs often promise subgroup comparisons that the expected number of responses cannot support, and recommend working out the likely size of each subgroup before writing the questions (Dillman et al., 2014). I had written the questions first and done the arithmetic only when asked.
What Changes
I am making two changes. First, I will launch the survey on the union's next garage meeting cycle, in two weeks, whether or not payroll's bands have arrived. The survey's earnings questions ask about expected pay after promotion, which does not depend on the bands. If the bands are still delayed when I analyze the results, I will use the published pay schedules for the basic comparison. Eric Barends and Denise Rousseau describe organizational evidence as including published documents as well as internal data, and recommend using the best evidence available rather than waiting for ideal data (Barends & Rousseau, 2018).
Second, I will move the garage comparison out of the survey and into the interviews. The interviews already select three operators per garage, and they can ask what is different about each garage's culture and supervisors. That is a question better answered in conversation than in a survey with too few responses to split. Dropping the envelope codes also removes the one question most likely to make a cautious operator wonder whether their answers could be traced.
A Question I Am Still Weighing
The design calls for interviews after the survey, so that the guide can focus on what the survey finds. Nataliya Ivankova and colleagues describe that order as the core of a sequential explanatory design (Ivankova et al., 2006). But if the survey launches two weeks late, the interviews will be squeezed into the final weeks of the term. I could start the three supervisor interviews now, since their questions do not depend on the survey, and keep the operator interviews for after. That would bend the design slightly but keep its logic for the operators, whose answers the survey is meant to shape. I think that is the right compromise, and I will ask the instructor to confirm it.
References
Barends, E., & Rousseau, D. M. (2018). Evidence-based management: How to use evidence to make better organizational decisions. Kogan Page.
Dillman, D. A., Smyth, J. D., & Christian, L. M. (2014). Internet, phone, mail, and mixed-mode surveys: The tailored design method (4th ed.). Wiley.
Ivankova, N. V., Creswell, J. W., & Stick, S. L. (2006). Using mixed-methods sequential explanatory design: From theory to practice. Field Methods, 18(1), 3-20. https://doi.org/10.1177/1525822X05282260
GM599 Unit 6 instructions, in plain terms
The GM599 Unit 6 reflection asks you to write, in the first person, about where your capstone stands and what a seminar changed. Begin with an honest status report: what you have, what is delayed and what you have not started. Then describe the exchanges that mattered, such as a classmate's suggestion or an instructor's question, quoting or paraphrasing what was said. Explain why you had not seen the problem yourself, connecting it to a methods source where it helps. State the changes you will make, with dates. Close with a question you are still weighing, and say how you will settle it. Expect about two pages, citing any sources that shaped a change in APA 7.
Inside the GM599 Unit 6 example
The status round records posting records in hand, payroll bands three weeks in legal review, a pretested survey held back and no interviews, and notes that most classmates were waiting on employers. Danielle's point about published salary schedules offers a fallback for the pay comparison. The instructor's arithmetic, about 70 responses and 23 per garage, shows the garage comparison planned through coded return envelopes could not work and would reintroduce identification risk, which the highlighted sentence records. A section explains the mistakes as treating the method as a fixed sequence, citing Dillman, Smyth and Christian on subgroup sizes. Changes launch the survey in two weeks regardless of payroll, citing Barends and Rousseau on using the best available evidence, and move garage questions to interviews. The open question, citing Ivankova and colleagues, is whether to start the three supervisor interviews early.
Reading the GM599 Unit 6 grading rubric
GM599 instructors look for an honest status, specific exchanges and concrete changes. A status report that names what is missing earns more than one that sounds on track. Exchanges should be described specifically enough to show how they changed the writer's plan. Explaining why the writer had not seen the problem shows reflection rather than reporting. Connecting a change to a methods source where relevant strengthens it. Changes should be specific and dated. An open question, with how it will be settled, shows the project is still being managed. Dillman, Smyth and Christian's Internet, Phone, Mail, and Mixed-Mode Surveys, Barends and Rousseau and Ivankova, Creswell and Stick supply the references in APA 7.
GM599 Unit 6 help from the desk
Many GM599 Unit 6 reflections describe the seminar in general and end with a resolve to keep working. Others hide delays, which leaves the instructor unable to help. A common gap is arithmetic: subgroup comparisons promised early in a project often collapse when the expected number of responses is divided among the groups. Some writers list changes without dates. State plainly where your project stands, describe the exchanges that mattered, explain why you missed what they revealed, make dated changes and name the question you are still deciding.
Get a GM599 Unit 6 example written to your instructions
Tell us where your data collection stands, what was said in your seminar or written alternative, and include the reflection prompt and rubric. The reflection you receive reports your status plainly, records the advice that mattered and dates the changes you made. We charge nothing for a first sample, usually delivered in 24-48h. 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 GM599 papers and MS in Management samples
- GM599 Unit 1: Capstone Topic Proposal
- GM599 Unit 2: Capstone Question Test Post
- GM599 Unit 3: Capstone Problem Statement Draft
- GM599 Unit 4: Capstone Literature Synthesis
- GM599 Unit 5: Capstone Methodology Section
- GM599 Unit 7: Data Collection Plan
- GM599 Unit 8: Findings and Analysis
- GM599 Unit 9: Recommendation Set
- GM599 Unit 10: Final Capstone Paper
- GM500 Unit 6: Snowplow Routes Seminar Reflection
- GM594 Unit 6: Project Endings Seminar Reflection
- GM501 Unit 6: Management Fashion Seminar Reflection
- GM593 Unit 6: Status Reporting Seminar Reflection
GM599 Unit 6 questions, answered
Does this work for the written seminar option?
The reflection can respond to the alternative prompt and to classmates' posted status reports, if your section shares them. The structure still works: status stated plainly, what others' experience suggested, the advice or insight that mattered, and the changes it produced. Say clearly which format you completed so the instructor reads it correctly.
Is it acceptable to admit my data is late?
Yes, and at this point in a capstone it is expected. What instructors look for is whether the writer responded, with a fallback, a revised schedule or a narrower analysis. This reflection reports payroll bands stuck in legal review and shows the published pay schedules that would replace them if needed.
Should the reflection cite sources?
Only where a source shaped the thinking, such as a methods text on survey response or the agency's published salary schedule. Most of the reflection draws on the session itself. If your rubric asks for a citation, one or two that bear on a change you made will serve better than general references.
Where can I find a free GM599 Unit 6 sample paper?
This page carries a full GM599 Unit 6 seminar reflection from the midpoint of a transit capstone, with an honest status report, two changes and an open question, and APA 7 references.
Why was the garage comparison dropped from the survey?
About 70 responses from 141 operators would leave roughly 23 per garage, too few to compare once split by tenure. Coding return envelopes by garage would also risk identifying respondents, so the comparison moved to interviews.