| Course | GB520 Strategic Human Resource Management |
|---|---|
| Unit | Unit 7 |
| Paper type | Performance management design |
| Length | About 900 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for GB520 Unit 7
Retiring the Zero-Injury Bonus: A Unit 7 Performance Management Design for Refrigeration Crews
[Student Name]
Purdue University Global
GB520: Strategic Human Resource Management
Unit 7 Performance Management Design
[Instructor Name]
[Date]
The contractor, its crews and every figure are composite and illustrative; the regulation and sources cited are real.
Why the Current System Fails
Kestrel Refrigeration Services pays each crew a quarterly bonus of $600 per person if the crew records no injuries. The bonus was meant to improve safety. In the last year, recorded injuries fell by half, but first-aid cases logged by the shop's tool crib, such as burn ointment and bandages issued after jobs, rose. Two technicians told the safety manager they had stopped reporting minor injuries so the crew would not lose the bonus. A refrigerant burn left untreated on one job became an infection that cost a technician two weeks of work.
Kerr (1975) named this trap long ago, in an article about paying for A while hoping for B. Kestrel hoped for safer work and paid for silence.
The rest of the system is an annual review with a one-to-five rating, completed by project managers who rarely see the crews work. It measures nothing the growth plan needs.
Exhibit 1: The Goal Cascade
Three strategic goals sit at the top: grow CO2 installations, deliver systems that work the first time, and send every technician home safe. Each cascades to crew measures, and crew measures to individual ones.
Crew measures
First-time startup success: the share of systems commissioned with no callback for the same fault within 90 days; current 81 percent; target 92 percent.
Punch-list items at commissioning: open items on the grocer's checklist at startup; current average 14; target 6.
Schedule adherence: milestones met within three working days of plan; current 74 percent; target 88 percent.
Hazard and near-miss reports submitted: reports per crew each quarter, with a follow-up recorded for each; current about 1; target 6 or more.
Leak checks completed on time on older systems: current 86 percent; target 98 percent.
Individual measures
For crew leads: coaching record, including hours spent coaching academy participants on startups and the progress of apprentices on the crew; the crew's results on the measures above.
For technicians: certifications completed, such as manufacturer CO2 training; observed safe practices on unannounced field audits, scored against a checklist; and contribution to the crew's punch-list and startup results.
A crew earns more under the new system by reporting a near miss than by hiding one, because hazard reports with follow-up are a measure in themselves.
Exhibit 2: The Calendar
Quarterly check-ins: each lead meets each technician for 30 minutes to review progress on individual measures and agree on one development goal. The project manager meets each lead to review crew measures.
Mid-year review: a short written summary, with no rating, to flag anyone off track early.
Year-end calibration: operations leaders from each branch meet to compare proposed ratings across crews, with evidence from the measures, so that a lead in Milwaukee and a lead in Minneapolis are judged on the same standard.
Rewards: a crew quality bonus paid twice a year on first-time startup success, punch-list results and schedule adherence, provided the crew has met its hazard-reporting floor. Merit increases follow year-end ratings.
Pulakos and O'Leary (2011) trace most failures to systems built around a yearly form, and most successes to managers who talk with people often and specifically about their work. The quarterly check-ins and the calibration session are designed around that finding.
Legal and Ethical Considerations
Under the federal injury records rule, Kestrel must give workers a sensible way to tell it about an injury, and it may not punish anyone who does (29 C.F.R. § 1904.35, 2024). Federal safety officials have said that incentive programs are not automatically prohibited, but a program that discourages employees from reporting injuries can be treated as retaliation. A bonus that crews lose when one member reports an injury creates exactly that pressure, which is the main legal reason for retiring it.
The new system raises ethical questions of its own. Hazard reports could be inflated to meet a target, so each report counts only when a follow-up is recorded. Field audits must be unannounced but fair, using the same checklist for every crew. Ratings should be checked each year for differences by sex, race and age at calibration, since subjective judgments are where bias enters. Aguinis (2019) recommends that a performance system be seen as fair by those it measures, and the calibration session and written evidence for each rating are meant to make it so.
Links to the Rest of the Strategy
The cascade connects to the academy in Unit 6, since coaching hours and certifications are measured, and to the pay strategy in Unit 8, since the crew quality bonus replaces the injury bonus. First-time startup success is the measure the grocers care about most, so it links crew work directly to the growth goal.
Implementation
Announce the change in a meeting with every crew, explaining why the injury bonus is ending and what replaces it. Run one quarter with the new measures reported but not yet paid, to test the data. Train leads in quarterly check-ins before the first round. Review the system after one year, asking crews whether reporting has become easier and whether the measures reflect their work.
References
Aguinis, H. (2019). Performance management (4th ed.). Chicago Business Press.
29 C.F.R. § 1904.35 (2024). https://www.law.cornell.edu/cfr/text/29/1904.35
Kerr, S. (1975). On the folly of rewarding A, while hoping for B. Academy of Management Journal, 18(4), 769-783. https://doi.org/10.2307/255378
Pulakos, E. D., & O'Leary, R. S. (2011). Why is performance management broken? Industrial and Organizational Psychology, 4(2), 146-164. https://doi.org/10.1111/j.1754-9434.2011.01315.x
What the GB520 Unit 7 assignment asks for
In GB520 Unit 7 you design a performance management system that supports an organization's strategy. Diagnose the current system's problems with evidence. Build a cascade from strategic goals to team and individual measures, with current values and targets. Set out the calendar of reviews, conversations and calibration, and how results link to rewards. Discuss the legal and ethical issues the design raises, including how measures could be gamed. Show how the system connects to other parts of the human resource strategy, and close with an implementation plan. Cite performance management research and any applicable regulation in APA 7.
How this GB520 Unit 7 example is built
The design opens with the injury-free bonus, rising first-aid cases and an untreated refrigerant burn, citing Kerr's classic warning about mismatched rewards. Exhibit 1 cascades three goals to five crew measures, from first-time startup success at 81 percent toward 92 percent to hazard reports per quarter, and to individual measures for leads and technicians; the highlighted sentence states the incentive reversal. Exhibit 2 sets quarterly check-ins, a mid-year summary, year-end calibration and the crew quality bonus, citing Pulakos and O'Leary. The legal section applies the federal injury reporting rule, and the ethical section addresses gaming and rating bias, citing Aguinis. Links and a one-quarter trial follow. Implementation begins with a meeting at every crew to explain why the injury bonus is ending, followed by training for leads in quarterly check-ins.
GB520 Unit 7 rubric: what earns full points
GB520 instructors grade this design on a diagnosis with evidence and a system whose measures reward what the strategy needs. A cascade from goals to team and individual measures, with targets, earns credit. Measuring at the level where the work happens shows understanding. A calendar with frequent conversations and calibration carries significant weight. The legal analysis should apply the anti-retaliation rule accurately. Anticipating how new measures could be gamed shows judgment. Links to training and pay and a staged rollout complete it. In APA 7 the design draws on Kerr's classic article, Pulakos and O'Leary, Aguinis and the federal recordkeeping rule.
GB520 Unit 7 help: mistakes that cost points
Many GB520 Unit 7 designs list measures without showing which strategic goal each serves. Others replace one flawed incentive with another that can be gamed just as easily. A common gap is the legal analysis: a safety incentive that discourages reporting can conflict with federal rules, and the design should say why. Some writers keep the annual review as the only conversation. Diagnose with evidence, cascade goals to measures, set a calendar of frequent check-ins and calibration, address gaming and bias, and roll out with a trial quarter. Requiring a recorded follow-up before a hazard report counts is one way to close the obvious loophole. Linking the new measures to the training and pay units, as this sample does, also helps the design read as part of one strategy.
Get a GB520 Unit 7 example written to your instructions
Performance systems depend on what the firm is trying to achieve, so include the strategic goals stated in the Unit 7 scenario, or describe an employer's current process in general terms, with the rubric. The design returns within 24-48h, measures cascaded from strategy and the cycle mapped. A first design is free. 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 GB520 papers and MBA samples
- GB520 Unit 1: Strategic People Management Post
- GB520 Unit 2: Employment Law Analysis Memo
- GB520 Unit 3: Workforce Planning Paper
- GB520 Unit 4: Recruiting Strategy and Decision Matrix
- GB520 Unit 5: Selection Methods Analysis
- GB520 Unit 6: Training Needs Analysis and Academy
- GB520 Unit 8: Compensation Strategy
- GB520 Unit 9: Retention and Relations Analysis
- GB520 Unit 10: Human Resources Strategy Proposal
- GB519 Unit 7: Variance Analysis Memo
- GB518 Unit 7: Debt Versus Equity Analysis
- GB513 Unit 7: Two-Sample T Test Comparison
- GB512 Unit 7: Annotated Report Outline
GB520 Unit 7 questions, answered
Why retire a safety bonus?
Because a bonus paid for zero recorded injuries gives crews a reason not to report them, which hides hazards and can conflict with federal rules protecting employees who report injuries. The example replaces it with leading indicators such as near-miss reports submitted and hazards corrected, which reward attention to safety rather than silence about it.
Where can I find a free GB520 Unit 7 sample paper?
This page carries a full GB520 Unit 7 performance management design for a refrigeration contractor's crews, with a goal cascade, a review calendar, legal and ethical analysis and APA 7 references.
How are crew and individual performance balanced?
Each is measured where the work happens. Startup success, punch-list items and schedule adherence belong to crews, since no technician produces them alone, while certifications, observed safe practices and a lead's coaching record belong to individuals.
How could the new measures be gamed?
Crews could file trivial hazard reports to meet the target, so a report counts only when a follow-up is recorded. Unannounced field audits use one checklist for every crew, and calibration checks ratings for bias.
Why run a trial quarter before paying the new bonus?
Reporting the new measures without paying on them tests whether the data are accurate and the targets realistic, so crews are not paid or penalized on figures that turn out to be wrong.