MGT 420 Topic 7 structural root cause diagnosis example

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

This MGT 420 Topic 7 sample paper diagnoses why technicians at a composite health system's IT help desk close tickets that are promptly reopened. It was prepared for GCU MGT 420, Organizational Behavior and Management, catalog code MGT-420, in the Grand Canyon University BS in Business Management program. Supervisors call the team sloppy. Five candidate causes are tested, and the decisive one is a scorecard that rates closures per hour and logs a reopened ticket as new work, so a rushed fix is paid twice. Reopens jump at month end and stay low on a team measured on confirmed resolution. Contributing causes are ranked beneath the root.

CourseMGT 420 Organizational Behavior and Management
TopicTopic 7
Paper typeRoot cause diagnosis
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 7

1

Paid Twice for a Rushed Fix: A Structural Root Cause Diagnosis of Reopened Tickets at a Composite IT Help Desk Described as Sloppy

[Author Name]

Colangelo College of Business, Grand Canyon University

MGT-420: Organizational Behavior and 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 this page is doingThe title states the root cause in one phrase and the explanation it replaces. The company, its help desk and every figure are an illustrative composite; the sources are real.
2

Paid Twice for a Rushed Fix: A Structural Root Cause Diagnosis of Reopened Tickets at a Composite IT Help Desk Described as Sloppy

The Pattern and the Easy Explanation

At a composite regional health system, the internal IT help desk supports about 6,000 employees. Its eighteen first-level technicians close tickets for password resets, printer problems, software errors and access requests. Over the past year, 23 percent of closed tickets were reopened within five days because the problem had not been solved. Supervisors describe the team as sloppy and have proposed retraining and a written warning for technicians with the highest reopen rates.

Sloppiness is an explanation about character, and observers tend to reach for such explanations while overlooking the situation people work in (Ross, 1977). This diagnosis lists candidate causes across the organization's systems, gathers evidence for each and ranks them.

What this page is doingThe paper names the easy explanation and the bias that makes it attractive, then commits to testing it alongside other causes rather than dismissing it.
3

Candidate Causes

Five candidate causes were identified, one in each of the systems that shape technicians' work.

1. People: technicians lack the skill to diagnose problems properly.

2. Measurement and reward: the way performance is measured encourages rushed closures.

3. Tools: the knowledge base lacks reliable fixes for common problems.

4. Workload: ticket volume is too high for careful work.

5. Process: tickets arrive without the information needed to solve them, such as which device or application is affected.

Listing causes by system, rather than by who might be at fault, keeps the diagnosis from settling on the first plausible answer. Each candidate is a hypothesis with a test: skill should vary with experience, workload should track volume, tools should affect some ticket types more than others, and measurement should show up wherever the measure bites hardest.

The Evidence

Table 1

Evidence for Each Candidate Cause

Candidate causeEvidenceVerdict
SkillReopen rates vary little with tenure; technicians with three years' experience reopen at 21 percent, new hires at 25 percentMinor contributor
Measurement and rewardTechnicians are rated monthly on tickets closed per hour; a reopened ticket is logged as a new ticket and counts againRoot cause
Knowledge baseAbout 30 percent of articles are out of date; technicians report using them as a starting point onlyContributing
WorkloadTicket volume rose 8 percent last year; reopen rate rose 6 points over the same periodContributing
ProcessAbout 15 percent of tickets arrive missing device or application detailsContributing

Table 1 sets out the evidence gathered for each cause.

The table also shows what can be ruled out quickly. Skill varies too little with tenure to explain a 23 percent rate, and the workload rise is too small to account for a spike that appears only at month end.

The Decisive Finding

The scorecard pays twice for a rushed fix. Technicians are rated on tickets closed per hour, which forms most of their monthly performance score and determines eligibility for a quarterly bonus. When a ticket is reopened, the system logs it as a new ticket rather than reviving the old one. A technician who closes a ticket quickly without solving the problem gets credit for the first closure, and whoever picks up the reopened ticket gets credit for a second closure. Thorough work, which takes longer per ticket, lowers the score. The organization hopes for problems solved the first time and rewards tickets closed fast, a textbook case of what Kerr (1975) called the folly of paying for one result and expecting a different one.

Strengthening the Diagnosis With Variation

A root cause should explain variation in the pattern, not just its existence. Two kinds of variation support this one.

Timing within the month. Reopen rates climb from about 18 percent in the first three weeks of each month to 34 percent in the last four working days, when technicians close to the bonus threshold push their counts. A skill or knowledge-base problem would not vary with the calendar. Measurement pressure does.

A team measured differently. The health system's second-level desk, which handles escalated tickets, is rated on resolution confirmed by the requester rather than on closures per hour. Its technicians use the same knowledge base and handle harder problems, yet their reopen rate is 6 percent. If sloppiness were a trait of the help desk staff, this team, drawn from the same hiring pool and some former first-level technicians, should show it too.

Goals tied to a single narrow measure tend to produce gaming and neglect of what the measure leaves out (Ordóñez et al., 2009). The pattern here, sharp at month end and absent under a different measure, fits that account.

What this page is doingVariation by time of month and by team turns a plausible cause into a demonstrated one, because a character explanation predicts neither pattern.
4

Contributing Causes, Ranked

Beneath the root cause, three contributors are ranked by how much of the problem they plausibly explain. First, missing information in incoming tickets: about 15 percent of tickets arrive without device or application details, and technicians under time pressure guess rather than ask. Second, the outdated knowledge base, which makes a quick fix more likely to be the wrong fix. Third, the 8 percent rise in volume, which adds time pressure on top of the scorecard. Skill differences contribute little; tenure barely changes the reopen rate. Each contributor makes the root cause worse, but none would produce the month-end spike or the gap with the second-level desk on its own.

What the Diagnosis Means

The team is not sloppy in any sense a warning would fix. Retraining and warnings target the minor contributor and leave the root cause in place; the next technicians would face the same scorecard and behave the same way. The fix begins with the measure: reopened tickets should be reattached to the original and count against the closure, and performance should be judged on problems resolved rather than tickets closed. The intervention plan in Topic 8 sets out how.

The diagnosis also explains why supervisors saw sloppiness. They watch closed-ticket counts daily and reopen rates monthly, so the behavior the scorecard rewards is the behavior they see, and the cost it produces arrives later under a different heading.

References

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

Ordóñez, L. D., Schweitzer, M. E., Galinsky, A. D., & Bazerman, M. H. (2009). Goals gone wild: The systematic side effects of overprescribing goal setting. Academy of Management Perspectives, 23(1), 6-16. https://doi.org/10.5465/amp.2009.37007999

Ross, L. (1977). The intuitive psychologist and his shortcomings: Distortions in the attribution process. Advances in Experimental Social Psychology, 10, 173-220. https://doi.org/10.1016/S0065-2601(08)60357-3

The MGT-420 Topic 7 assignment instructions

MGT-420 Topic 7 asks students to find the structural root cause of a recurring performance problem. Accepting a character explanation, or listing every possible cause without ranking them, misses the task. The prompt rewards a diagnosis that lists candidate causes across the organization's systems, gathers evidence for each and identifies the one that explains the pattern best. Students should strengthen the finding with variation, such as changes over time or differences between groups measured differently, cite research on how measures shape behavior and rank contributing causes beneath the root so the reader knows what to fix first and what to address later.

How the MGT-420 Topic 7 example is put together

The diagnosis opens with the reopen pattern and the supervisors' view, set against the fundamental attribution error. Five candidate causes are listed, one per system. Table 1 shows the evidence for each, from tenure data on skill to the scorecard rules. The decisive finding explains how the scorecard rewards a rushed fix twice, drawing on Kerr's classic warning about reward systems. Variation by time of month and a comparison with the second-level desk strengthen the diagnosis, supported by research on narrow goals. Three contributing causes are ranked, and the conclusion explains why warnings would miss the root cause. Each verdict in the table is labeled as root, contributing or minor, so the ranking is visible at a glance.

Where the marks sit in the MGT 420 Topic 7 rubric

Faculty grading the root cause diagnosis reward candidate causes tested against evidence rather than assumed. Strong papers identify a root cause that explains not only that the problem exists but also when and where it varies. Credit goes to using comparisons, such as a team measured differently, that a character explanation cannot account for. The rubric values ranking contributing causes clearly and citing research on measures and goals accurately. The highest band explains why the obvious fix would leave the root cause in place and points to what should change instead. Diagnoses that blame individuals without testing the system tend to lose marks.

MGT 420 Topic 7 help before you submit

The heaviest deduction lands on diagnoses that conclude the staff need retraining or closer supervision, since that treats the behavior as the cause and leaves the scorecard paying for it. A candidate cause offered with no mechanism is untestable, and a list of every system in the organization is no more useful than a list of none. Ignoring variation in the data wastes the strongest evidence a diagnosis can offer, because a structural cause should predict where and when the behavior peaks. Treating every contributing condition as equally important produces a diagnosis with no root. Blaming the measure without showing how it rewards the behavior asserts the finding rather than establishing it. Diagnoses with no confirming prediction offer a reader no way to know whether they are right.

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

Send the MGT-420 Topic 7 instructions, the rubric from your classroom and the behavioral problem your case presents. We write a custom example to those criteria, with the problem defined by its pattern, candidate causes listed by system with mechanisms, variation used as evidence and the root separated from contributors, back in 24 to 48 hours. The first one is free.

More MGT 420 papers and BS in Business Management samples

MGT 420 Topic 7 questions, answered

What makes a cause structural rather than personal?

It sits in the arrangements rather than in the individuals, and it would affect anyone placed in the same position. Performance measures, reward formulas, workload, reporting lines and procedural rules all qualify. The test is whether replacing the people would change the behavior. If a new technician would face the same scorecard and rush the same fixes, the cause is structural.

How can data variation support a diagnosis?

A genuine cause should predict where and when the behavior is strongest. If rushed fixes rise when targets tighten and fall on a team measured differently, the measure is implicated. If the behavior is spread evenly regardless of conditions, the proposed cause is weaker. Using variation turns a plausible story into an argument a reader can check against the numbers.

What is rewarding A while hoping for B?

The pattern Steven Kerr described, in which an organization says it wants one behavior while its reward system pays for another. A help desk that wants lasting fixes but pays for closures is a clear instance. The idea is useful in diagnosis because it directs attention to what the measures actually reward, which is frequently the opposite of what the mission statement says.

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

The help desk diagnosis is above, including the pattern, five candidate causes, the evidence table, the decisive finding, the variation that supports it, the ranked contributors and what it means. Describe the problem you are diagnosing, and we can draft a free version around your case.

What is the root cause in MGT 420 Topic 7?

The scorecard. Technicians are rated on tickets closed per hour, and a reopened ticket counts as new work, so a quick fix that fails earns credit twice while careful work lowers the score.