| Course | MGT 475 Technology in Human Resource Management |
|---|---|
| Topic | Topic 7 |
| Paper type | Implementation evaluation |
| Length | About 960 words, 4 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Business Management |
| Updated | October 2026 |
Free sample paper for MGT 475 Topic 7
What the System Fixed and What It Never Touched: An HRIS Implementation Evaluation for a Grocery Chain, Objective by Objective With an Owner for Each Finding
[Author Name]
Colangelo College of Business, Grand Canyon University
MGT-475: Technology in Human Resource Management
Topic 7 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
What the System Fixed and What It Never Touched: An HRIS Implementation Evaluation for a Grocery Chain, Objective by Objective With an Owner for Each Finding
The Objectives
Twelve months ago, Prairie Market implemented the HRIS selected after the needs analysis in Topic 1. That analysis set four objectives: reduce the time HR generalists spend re-entering data, reduce pay errors caused by late or incorrect status changes, move routine updates such as addresses and tax forms to employee self-service, and replace store managers' scheduling spreadsheets with the system's scheduling module. This evaluation sets each objective against a measure taken before and after implementation and names what the system achieved and what it did not. All figures are illustrative.
Results by Objective
Table 1
Objectives and Measures Before and After Implementation
| Objective | Measure | Before | After |
|---|---|---|---|
| Reduce HR re-entry | Share of HR generalists' week spent on address, tax and status updates | About 30% | About 12% |
| Reduce pay errors | Pay corrections per pay period | 64 | 58 |
| Move updates to self-service | Share of employees who logged in at least once | Not applicable | 71% of full-time; 38% of part-time |
| Replace scheduling spreadsheets | Stores where managers no longer keep a separate spreadsheet | 0 of 38 | 16 of 38 |
Table 1 sets each objective beside its measure.
What the System Can Claim
The reduction in HR re-entry is real and attributable to the system. Before implementation, generalists spent about 30 percent of their week keying in address changes, tax forms and status changes that arrived on paper or by email. Afterward, most of those arrive through the system already entered, and generalists spend about 12 percent of their week on them. The time freed has gone mainly to answering employee questions and supporting store managers on employee relations cases, which HR leadership regards as a better use of the team.
The improvement also reduced errors in employee records, since data entered once by the employee or manager is not re-keyed by someone reading handwriting. HR found that mismatched addresses on tax forms, a recurring issue before implementation, nearly disappeared.
Pay Errors: A Step the Software Never Touched
Pay corrections barely moved, from 64 per pay period to 58. The evaluation traced the remaining errors and found that most arise when store managers enter status changes, such as a cashier moving from part-time to full-time, after the pay period has closed. The system routes changes faster once they are entered, but it cannot make managers enter them on time. The step that causes most errors happens before the software is involved.
Finding: late status changes by store managers. Owner: the vice president of store operations, who can set a deadline for status changes in each pay period and include compliance in store managers' reviews.
Self-Service: A Split by Employee Group
Self-service use splits sharply. Seventy-one percent of full-time employees logged in at least once in the year, but only 38 percent of part-time cashiers did. Interviews in six stores explained the gap. Most part-time cashiers have no company email address, which the system requires for login setup, and they rely on a single break-room kiosk that is often occupied during short breaks. Many did not know they could use the system on their own phones, and those who tried found that password resets required the company email they did not have.
Research on technology acceptance has found that whether people use a system depends heavily on the conditions that make use easy, such as access, support and compatibility with how they work, not only on whether they find the system useful (Venkatesh et al., 2003). The part-time cashiers' low use is a problem of access, not motivation.
Finding: part-time employees lack a workable way to log in. Owner: the HRIS manager, who can enable login by personal phone number and add a second kiosk in the largest stores.
The split matters because part-timers outnumber every other group in the stores and move house and change tax elections most often. Until they can use self-service, a large share of routine updates will continue to reach HR on paper.
Scheduling: Spreadsheets That Remain
In 22 of the 38 stores, managers still keep a scheduling spreadsheet alongside the system. Interviews found two reasons. The system's scheduling module does not handle split shifts, which several stores use for their deli counters, and it does not record employees' availability constraints, such as school schedules, in a form managers trust. Managers build the schedule in the spreadsheet and copy it into the system, which doubles their work.
Finding: the scheduling module does not fit how 22 stores schedule. Owner: the vice president of store operations, with the vendor, to configure split shifts and availability or to accept the spreadsheet for those stores until it can.
The evaluation names each of these as a finding with an owner, not as a training problem. Calling a mismatch between a system and the work a training issue tends to place the blame on users for a problem in the design (Bondarouk & Brewster, 2016).
Overall Assessment
The system has delivered its clearest benefit to HR's own workload. It has not yet delivered on pay errors, self-service for part-time staff or scheduling, and in each case the evaluation identifies a cause outside the software's basic function and an owner who can address it. A second evaluation in six months, using the same measures, should show whether those owners' actions have closed the gaps. Implementations are often judged a success or failure as a whole, but evaluating objective by objective shows where the remaining work lies (Kavanagh & Johnson, 2018).
The evaluation also recommends that the HRIS steering group, which disbanded after go-live, be reconvened quarterly for the next year to track the four owners' actions. Implementation work rarely ends at go-live, and the most important fixes here require decisions outside HR.
References
Bondarouk, T., & Brewster, C. (2016). Conceptualising the future of HRM and technology research. International Journal of Human Resource Management, 27(21), 2652-2671. https://doi.org/10.1080/09585192.2016.1232296
Kavanagh, M. J., & Johnson, R. D. (Eds.). (2018). Human resource information systems: Basics, applications, and future directions (4th ed.). Sage.
Venkatesh, V., Morris, M. G., Davis, G. B., & Davis, F. D. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425-478. https://doi.org/10.2307/30036540
MGT 475 Topic 7 instructions, in plain terms
MGT-475 Topic 7 asks students to evaluate whether an HR technology implementation achieved what it was meant to. Overall satisfaction scores or vendor reports rarely show where the work remains. The prompt rewards measuring each original objective before and after, crediting the system only with changes it plausibly caused and tracing remaining problems to the step where they actually arise. Students should treat mismatches between the system and how people work as findings with owners rather than as training problems, use research on technology acceptance where it helps explain low use and propose a follow-up evaluation with the same measures.
Inside the MGT 475 Topic 7 example
The evaluation opens with the four objectives from the needs analysis. Table 1 sets each objective beside its measure before and after. A section credits the system with the reduction in HR re-entry and fewer record errors. The pay error section traces most remaining corrections to late status changes by store managers and assigns an owner. The self-service section explains part-time cashiers' low use through access barriers, citing technology acceptance research. The scheduling section explains why 22 stores keep spreadsheets. Each finding has an owner, and the overall assessment recommends reconvening the steering group and repeating the evaluation. Interviews in six stores support the self-service finding.
Where the marks sit in the MGT 475 Topic 7 rubric
Faculty grading the implementation evaluation reward objectives measured before and after on a consistent basis. Strong evaluations separate what the system achieved from problems it never touched, and trace each remaining problem to its real cause. Credit goes to findings stated with owners who can act on them, rather than general calls for more training. The rubric values research used to explain patterns such as low adoption among some employee groups. The highest band proposes a follow-up evaluation with the same measures and a structure to track owners' actions. Evaluations that judge the implementation as a single success or failure usually lose points. Showing how each finding was confirmed, by interviews or records, also counts.
MGT 475 Topic 7 help before you submit
Credit drains away fastest from evaluations that stop at launch day, since a delivery milestone says nothing about whether the work changed, and that is the question this topic sets. A paper celebrating an on-time, on-budget launch has answered the project manager's question and skipped the organization's. Measures reported with no baseline cannot show change, and baselines reconstructed from memory after launch invite a marker to doubt every figure. Crediting the system with every improvement in the period, including one a wage increase explains, overstates what the implementation did. Averages across all staff hide the part-time employees the design left behind. Papers that blame low use on resistance to change, recommending more training, usually miss that the barrier is access, and a parallel spreadsheet is a finding to investigate rather than a habit to scold.
Get an MGT-475 Topic 7 example written to your instructions
Send the MGT-475 Topic 7 instructions, your section's rubric and whatever implementation, objectives or data the assignment describes. We write a custom example to those criteria, with objectives carried forward, baselines sourced, changes measured, other causes weighed, workarounds recorded and findings assigned to owners, in 24 to 48 hours. The first one is free.
More MGT 475 papers and BS in Business Management samples
- MGT 475 Topic 1: Hris Needs Analysis
- MGT 475 Topic 2: Hr Data Field Trace
- MGT 475 Topic 3: People Analytics Question Brief
- MGT 475 Topic 4: Algorithmic Screening Audit
- MGT 475 Topic 5: Recommendation Ownership Dq Post
- MGT 475 Topic 6: Employee Monitoring Assessment
- MGT 475 Topic 8: Hr Technology Oversight Plan
- BUS 317 Topic 7: Investment Timing Comparison
- MGT 470 Topic 7: Two Country Incentive Redesign
- BUS 332 Topic 7: Engagement Measurement Proposal
- MGT 465 Topic 7: Bargaining Preparation Brief
MGT 475 Topic 7 questions, answered
Why not judge an implementation at go-live?
Because go-live shows the system was delivered, not that anything improved. Most of the value an HR system promises depends on people changing how they work, and that shows up months later, if at all. An evaluation several months after launch can compare the work before and after, find the workarounds that appear once the project team leaves, and test whether the original case held.
How does the evaluation separate the system's effect from other changes?
By listing everything else that changed during the period and asking whether it could explain each result. A wage increase that lifted applicant numbers would shorten time to hire with or without new software. Where a measure moved for a reason unrelated to the system, the evaluation says so and declines the credit, which makes the gains it does claim more believable.
Is low self-service use a training problem?
Sometimes, but it is worth checking access first. In the example, part-time cashiers have no company email and share one break-room kiosk, so their low use reflects how the system reaches them. More training would not change that. The evaluation recommends mobile access with a personal login, owned by the HRIS manager, and remeasurement after one quarter.
Where can I find a free MGT 475 Topic 7 sample paper?
The HRIS evaluation is above in full, from the objectives and results table to what the system can claim, the three remaining findings with owners and the overall assessment. Tell us your implementation's objectives and a free evaluation can be drafted.
Why did pay errors barely fall in MGT 475 Topic 7?
Most remaining errors come from store managers entering status changes after the pay period closes. The system routes changes faster once entered but cannot make managers enter them on time.