MGT 420 Topic 8 work design intervention plan example

Organizational Behavior and Management Grand Canyon University Free custom sample in 24 to 48h

This MGT 420 Topic 8 sample paper plans four changes to the work of help desk technicians whose scorecard rewards rushed fixes. It belongs to GCU MGT 420, Organizational Behavior and Management, the course listed as MGT-420 in the Grand Canyon University BS in Business Management. Every change sits within a manager's authority: counting reopens against the original closure, thirty minutes of extra diagnosis without approval, returning reopened tickets to their owner and a weekly summary of what failed. The job characteristics model shapes the redesign, likely gaming of each new measure is anticipated and a twelve-week pilot on the day shift is compared with the unchanged evening shift.

CourseMGT 420 Organizational Behavior and Management
TopicTopic 8
Paper typeIntervention plan
LengthAbout 980 words, 4 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Business Management
UpdatedOctober 2026

Free sample paper for MGT 420 Topic 8

1

Four Changes a Manager Can Make on Monday: A Work Design Intervention Plan for a Help Desk That Rewards Rushed Fixes, With a Pilot Team and a Comparison Team

[Author Name]

Colangelo College of Business, Grand Canyon University

MGT-420: Organizational Behavior and Management

Topic 8 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 this page is doingThe title promises only changes within a manager's authority and names the test that will judge them. The health system's help desk and every figure are an illustrative composite carried from Topic 7; the sources are real.
2

Four Changes a Manager Can Make on Monday: A Work Design Intervention Plan for a Help Desk That Rewards Rushed Fixes, With a Pilot Team and a Comparison Team

What This Plan Contains, and What It Does Not

Topic 7 found that the help desk's 23 percent reopen rate comes mainly from a scorecard that rewards tickets closed per hour and counts a reopened ticket as new work. This plan proposes four changes, each within the help desk manager's authority to decide: how performance is measured, who may approve an exception, how work is divided and how feedback reaches technicians. It contains no workshops, no culture statements and no appeals to engagement. Each change is written with the behavior it is expected to produce, so the plan can be judged by what happens.

The redesign is shaped by the job characteristics model, which holds that people put more into jobs that use a range of their skills, let them finish a whole piece of work, matter to others, leave room for judgment and show them how they are doing (Hackman & Oldham, 1976). A large meta-analysis later confirmed that these characteristics, especially autonomy and feedback, are associated with higher satisfaction and performance (Humphrey et al., 2007). The help desk job currently scores low on two of them: technicians rarely see whether their fix worked, and they have no authority to spend extra time on a hard problem.

What this page is doingThe plan states its boundaries before its contents, which keeps every proposal within what a manager can actually decide.
3

The Four Changes

Table 1

Changes, Job Characteristics and Expected Behavior

ChangeJob characteristic addedExpected behavior
1. Measure resolved tickets, not closures: a reopened ticket reattaches to the original and counts against itFeedback from the workTechnicians confirm a fix before closing; month-end spike disappears
2. Technicians may hold a ticket open for up to 30 minutes of extra diagnosis without supervisor approvalAutonomyFewer guessed fixes on unclear problems
3. The technician who closed a ticket gets it back if it reopens within five daysTask identityTechnicians own their fixes from start to finish
4. A weekly two-minute summary to each technician of their reopened tickets and what solved themFeedback from the workTechnicians learn which fixes fail

Table 1 sets out each change, the job characteristic it adds and the behavior it is expected to produce.

Why Each Change

The first change removes the root cause. Under the current scorecard, a rushed fix is paid twice, once for the first closure and once for the reopened ticket. Counting a reopen against the original closure makes a rushed fix cost the technician rather than pay them, which aligns the reward with the outcome the organization wants (Kerr, 1975).

The second change gives technicians the autonomy to spend time where it is needed. Today, a technician who takes longer than the expected handling time must ask a supervisor, which few do at month end. Thirty minutes is enough for most hard problems and limited enough that supervisors keep control of the queue.

The third change restores task identity. At present, a reopened ticket goes to whoever is next in the queue, so the technician who made the mistake never sees it. Returning it to the original technician lets them finish the job they started.

The fourth change provides feedback from the work itself. Technicians currently learn about reopens only through their monthly score. A short weekly summary of their reopened tickets, with the fix that eventually worked, turns each failure into specific information they can use.

Together the four changes alter what a good month looks like for a technician. Under the old scorecard, a good month meant many closures. Under the new one, it means few reopens, which can only be achieved by fixing problems properly the first time.

Unintended Effects

Any new measure invites people to optimize it at the expense of the goal, and these changes have their own risks. Technicians might avoid closing difficult tickets at all, leaving them open to protect their resolution rate; the plan therefore also tracks average time to close and flags tickets open more than two days. Technicians might ask requesters to confirm fixes they have not tested; the summary will note confirmations later reopened. The 30-minute allowance could become a default rather than an exception; the plan tracks how often it is used and on which ticket types. Naming these effects in advance means they can be watched for from the first week.

What this page is doingThe plan anticipates how each new measure could be gamed and attaches a check to each, rather than assuming the redesign will only produce the intended behavior.
4

The Pilot

The help desk has two shifts of nine technicians each, working the same ticket types under the same supervisor structure. The day shift will adopt all four changes for twelve weeks. The evening shift will continue unchanged and serve as the comparison. At the end of twelve weeks, the two shifts will be compared on four measures: reopen rate within five days, average time to close, tickets closed per technician per day and requester satisfaction from the one-question survey sent after each closed ticket.

The pilot succeeds if the day shift's reopen rate falls below 12 percent while the evening shift's stays near its baseline, and if average time to close rises by no more than 15 percent. A small rise in handling time is expected and acceptable if fewer tickets come back. If the reopen rate falls only modestly, the weekly summaries and the 30-minute allowance will be examined separately to see which change carried the effect.

After the Pilot

If the pilot succeeds, the changes extend to the evening shift, and the help desk manager proposes to the IT director that the quarterly bonus be tied to resolution rather than closures across the department. If it fails, the comparison with the evening shift will show whether the cause was the design or something else that changed during the twelve weeks. Either way, the decision rests on what technicians actually did, which is the standard Topic 7 applied to the explanation that they were simply sloppy.

References

Hackman, J. R., & Oldham, G. R. (1976). Motivation through the design of work: Test of a theory. Organizational Behavior and Human Performance, 16(2), 250-279. https://doi.org/10.1016/0030-5073(76)90016-7

Humphrey, S. E., Nahrgang, J. D., & Morgeson, F. P. (2007). Integrating motivational, social, and contextual work design features: A meta-analytic summary and theoretical extension of the work design literature. Journal of Applied Psychology, 92(5), 1332-1356. https://doi.org/10.1037/0021-9010.92.5.1332

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

MGT 420 Topic 8 instructions, in plain terms

The Topic 8 instructions for MGT-420 ask students to propose an intervention for a diagnosed organizational behavior problem. Plans built on training sessions, slogans or appeals to engagement rarely change what people do. The assignment rewards changes a manager can actually make, such as how performance is measured, who approves exceptions, how work is divided and how feedback reaches employees, each with its expected behavioral effect stated. Students should ground the redesign in a recognized model, anticipate how new measures could be gamed, design a pilot with a comparison group and set criteria for judging success before the pilot begins.

How this MGT 420 Topic 8 example is built

The plan opens by stating what it contains and what it leaves out, and introduces the job characteristics model with meta-analytic support. Table 1 lists four changes, the characteristic each adds and the behavior it should produce. A section explains each change, linking the first to Kerr and the others to autonomy, task identity and feedback. A section on unintended effects names three ways technicians might game the new measures and the check for each. The pilot compares the day shift with the evening shift on four measures over twelve weeks, with success criteria stated. A closing section explains what happens after the pilot. Every proposal can be traced back to a finding in the earlier diagnosis.

Reading the MGT 420 Topic 8 rubric

Instructors grading the intervention plan reward changes within a manager's authority, each paired with an expected behavior. Strong plans use a recognized model to explain why each change should work and cite its research support. Credit goes to anticipating how people might game new measures and attaching a check to each risk. The rubric values a pilot with a comparison group and success criteria set in advance, including an acceptable trade-off such as slightly longer handling time. The highest band explains how the result will decide the next step, whether the pilot succeeds or fails. Plans that rely on workshops or culture statements usually land in the lower bands. Measures should be ones the help desk already records, so the pilot needs no new reporting.

MGT 420 Topic 8 help before you submit

Plans built around training, communication campaigns or efforts to change mindsets lose the largest share of marks, because they aim at attitudes the diagnosis already showed were not the cause. Proposals that name no owner or cost read as wishes, since a change nobody has authority to make will not happen. Changes listed without a predicted behavior give a reader no way to tell whether the intervention worked. Ignoring side effects assumes the revised measure will be followed in good faith, which the earlier topics give every reason to doubt. Rolling a change out everywhere at once removes any comparison and leaves the result open to other explanations. Plans lacking a stated failure condition cannot return to diagnosis when the evidence disappoints.

Get an MGT-420 Topic 8 example written to your instructions

Send the MGT-420 Topic 8 instructions, your section's rubric and the diagnosis or case your plan responds to. We write a custom example to those criteria, with every change aimed at conditions a manager controls, a predicted behavior and indicator beside each, side effects anticipated and a pilot with a comparison team, back in 24 to 48 hours. The first one is free.

More MGT 420 papers and BS in Business Management samples

MGT 420 Topic 8 questions, answered

Why not include training in the plan?

Training can be part of a plan when the diagnosis found a skill gap, but it rarely fixes behavior that conditions produce. If a scorecard pays for rushed work, trained employees will still rush once they return to it. Including training as the main intervention signals that the diagnosis was not believed. Where it appears, it should support a change to conditions rather than replace one.

How specific should the predicted behavior be?

Specific enough to count. Reduced reopen rates, faster escalation of difficult cases or more exceptions approved at the front line are predictions someone can check. Improved morale or better engagement are not, because they describe feelings rather than actions and can be claimed whatever happens. A prediction that could turn out wrong is the only kind that tests the plan.

What if the pilot shows no change?

Then the plan has done its job by producing an answer. Either the diagnosis was wrong, the change was too weak, or another condition is holding the behavior in place. Your plan should state in advance which of these it will examine first, so a disappointing result sends the work back to diagnosis instead of prompting a larger rollout of the same idea.

Where can I find a free MGT 420 Topic 8 sample paper?

The full help desk plan appears here: its limits, the four changes, why each was chosen, unintended effects, the pilot design and what follows. Tell us the problem your plan must fix, and a free intervention plan can be built for it.

How is the plan tested in MGT 420 Topic 8?

The day shift adopts all four changes for twelve weeks while the evening shift continues unchanged. Success means the day shift's reopen rate falls below 12 percent with handling time up no more than 15 percent.