| Course | MGT 640 Fundamentals of Project Management |
|---|---|
| Topic | Topic 8 |
| Paper type | Governance failure diagnosis |
| Length | About 990 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MBA |
| Updated | October 2026 |
Free sample paper for MGT 640 Topic 8
Nineteen and a Half Million Dollars and Four Gates That Noted Rather Than Decided: A Governance Failure Diagnosis of a Canceled Commercial Lines Platform
[Author Name]
Colangelo College of Business, Grand Canyon University
MGT-640: Fundamentals of Project 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.
Nineteen and a Half Million Dollars and Four Gates That Noted Rather Than Decided: A Governance Failure Diagnosis of a Canceled Commercial Lines Platform
The Outcome
Three years ago, Larkspur Mutual began replacing its commercial lines policy platform with a packaged system from a large vendor. Last quarter, a newly appointed chief financial officer canceled the project after spending had reached $19.5 million: $13.9 million paid to the vendor and $5.6 million in internal costs. No part of the new platform is in use. This diagnosis works from the record of the project's governance gates to identify where the failure could have been caught and why it was not. All figures are illustrative.
Gate One: A Case Without Owners or a Stopping Condition
At the first gate, the governance board approved the business case. The case credited its expected gains, cheaper operations and quicker new products, to the commercial lines division in general. No named person was accountable for any benefit. The case also stated no condition under which the project should be stopped: no cost ceiling, no date beyond which benefits would no longer justify continuing and no milestone that had to be met. From the start, there was no one whose job was to ask whether the project was still worth doing, and no test for answering that question.
A stopping condition does not mean expecting failure. It means deciding in advance what result would show that the project no longer makes sense, so that the decision to stop does not depend on someone being willing to admit, years later, that an earlier choice was wrong.
Gate Two: A Bid That Contradicted Its Own Evidence
At the second gate, the board accepted the vendor's fixed-price bid of $9.8 million. The bid was premised on configuring the package, adjusting its settings, without custom development. The same gate pack contained the project team's gap analysis, which listed 140 of Larkspur Mutual's requirements that the package did not meet out of the box. Meeting those requirements would require custom development, which the fixed price excluded. The minutes record that the gap analysis was "noted." No one asked how 140 unmet requirements could be delivered by configuration alone, or who would pay for the difference.
This was the most important missed decision. The evidence that the bid was unrealistic was in front of the board, in the same document, and the board approved the bid anyway.
The board's members later said they assumed the vendor had accounted for the gaps in its price. The gate pack did not say so, and nobody asked. A gate is only as good as the questions the board is willing to ask of the evidence in front of it.
Change Requests Below the Line
The 140 gaps did not disappear. Over the next eighteen months, the vendor submitted eleven change requests to build custom functions. The project manager had authority to approve changes up to $500,000 each without going to the board. Every one of the eleven was priced below that limit, and together they totaled $4.1 million. The board never saw any of them. The governance design assumed that large changes would be visible, but it had no rule for adding up many smaller ones.
Some of the change requests were also related. Three concerned the same rating engine and could have been treated as one change; split into three, each stayed under the limit. Whether or not that was deliberate, the effect was to keep a significant overrun out of the board's view.
Gate Three: A New Schedule Without a New Case
At month 18, the project was well behind. The board approved a revised schedule that moved go-live back fourteen months. It did not revisit the business case, although benefits would now arrive fourteen months later and costs had risen by the $4.1 million in change requests. A case built on earlier benefits and lower costs was left standing, so the project's apparent value on paper no longer matched its real value.
The Pattern
Taken together, the record shows a governance process that received information and recorded it without making the decisions it existed to make. Each gate had what it needed to change course: a case without owners, a gap analysis that contradicted the bid, eleven changes that added up to a large overrun and a schedule that invalidated the case. At no point did the board ask whether the project should continue.
Escalation of commitment helps explain why. People responsible for an earlier decision tend to invest further after setbacks, interpreting negative information in ways that justify continuing (Staw, 1976). Large projects are also prone to optimistic estimates at approval that later prove unrealistic, a pattern seen across many sectors (Flyvbjerg, 2014). Governance exists to counter those tendencies by giving someone the authority and the obligation to decide, and here no one exercised it (Too & Weaver, 2014). The new chief financial officer, with no stake in earlier decisions, stopped the project within a quarter of arriving.
What Would Have Changed the Outcome
Four governance changes would have caught the failure earlier, and the diagnosis recommends them for all future projects. Every business case must name an owner for each benefit and state conditions for stopping, such as a cost ceiling or a latest date for go-live. Any evidence in a gate pack that contradicts the proposal before the board must be resolved in writing before the gate is passed. Change requests must be reported to the board when their running total exceeds a threshold, such as 10 percent of the approved budget, not only when a single change does. And any revised schedule or budget must come with a revised business case, so the board decides on current figures. On this project, the first gate would have set a stopping condition, and the second gate would have rejected a bid its own evidence showed could not be delivered.
References
Flyvbjerg, B. (2014). What you should know about megaprojects and why: An overview. Project Management Journal, 45(2), 6-19. https://doi.org/10.1002/pmj.21409
Staw, B. M. (1976). Knee-deep in the big muddy: A study of escalating commitment to a chosen course of action. Organizational Behavior and Human Performance, 16(1), 27-44. https://doi.org/10.1016/0030-5073(76)90005-2
Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394. https://doi.org/10.1016/j.ijproman.2013.07.006
The MGT-640 Topic 8 assignment instructions
MGT-640 ends with Topic 8, where students apply the course's ideas on selection, governance, delivery and benefits to a project that failed. The brief asks for a diagnosis, not a narrative of events: what decisions allowed the failure, who made them, and what controls would have changed the outcome. Papers meet it when they work from the documentary record, such as business cases, gate packs, contracts and change logs, and identify the pattern across individual failures. Graduate responses should test the obvious explanation against the evidence, use governance and project failure research and end with specific, testable rules tied to each failed decision. The paper should also reflect, briefly, on what the case shows about governing projects across the portfolio.
How the MGT-640 Topic 8 example is put together
The finished diagnosis works from the gate record, all figures labeled illustrative. At the first gate the business case was approved with its benefits assigned to commercial lines as a whole and no stated condition for stopping it. At the second, the committee accepted a 9.8 million dollar fixed-price bid premised on configuration only, while the gap analysis in the same pack listed 140 requirements the package did not meet; the minutes record it as noted. Eleven change requests followed, each kept under the project manager's 500,000 dollar limit and together worth 4.1 million, none seen by the committee. At month 18 a new schedule was approved without revisiting the case, though benefits now arrived fourteen months later. With internal costs of 5.6 million, spending reached 19.5 million before a new CFO canceled the work.
Reading the MGT 640 Topic 8 rubric
An Excellent diagnosis earns its marks by tracing failure to approvals. The rubric rewards a paper that reads each gate in order and shows what was in front of the committee when it decided, as with the 140 unmet requirements sitting in the same pack as the fixed-price bid. Graders credit catching the change requests split below the 500,000 dollar limit and recognizing the month-18 re-baseline as a new investment decision. Strong papers test the vendor explanation against the contract instead of accepting or dismissing it. The highest band names the pattern, gates that noted rather than decided, and ends with rules tied to each failure, including a cumulative change threshold and case review at re-baseline, supported by project governance research.
MGT 640 Topic 8 help before you submit
Failure papers most often settle on a villain, usually the vendor or the project manager, and stop looking. A diagnosis that blames the vendor without reading the contract and the gate papers has repeated the insurer's own story rather than testing it. Papers that list what went wrong in date order describe symptoms, while the topic asks which approvals allowed them. Missing the change requests split beneath the threshold overlooks how 4.1 million bypassed the committee entirely. Treating the month-18 re-baseline as a scheduling event misses that the investment changed at that meeting. Recommendations for stronger leadership or better communication cannot be tested, and a graduate diagnosis ends with rules tied to each failed decision, such as a cumulative change threshold and a mandatory case review at every re-baseline.
Get an MGT-640 Topic 8 example written to your instructions
Send the MGT-640 Topic 8 instructions, your section's rubric and the failed project or case the assignment describes. A custom example is written to those requirements, with the outcome reconciled, each decision point examined against what governance knew, the popular explanation tested and a rule proposed for every failed approval, in 24 to 48 hours. The first one is free.
More MGT 640 papers and MBA samples
- MGT 640 Topic 1: Strategic Initiative Triage Memo
- MGT 640 Topic 2: Competing Business Case Appraisal
- MGT 640 Topic 3: Steering Committee Decision Audit
- MGT 640 Topic 4: Methodology Fit Assessment
- MGT 640 Topic 5: Stopping Criterion Dq Post
- MGT 640 Topic 6: Portfolio Resource Contention Analysis
- MGT 640 Topic 7: Benefits Realization Review
- MGT 641 Topic 8: Hybrid Delivery Defense
- MGT 605 Topic 8: Personal Leadership Plan
- MGT 655 Topic 8: Lean Process Improvement
- LDR 670 Topic 8: Global Readiness Plan
MGT 640 Topic 8 questions, answered
Why diagnose failure from approvals rather than from events?
Because events show what went wrong while approvals show where the organization chose to let it. A delay or an overrun is a symptom; the decision that accepted a flawed premise, or waved through a change, is where governance could have acted. Diagnosing at that level produces rules a future committee can follow, which a list of mistakes does not.
What is threshold splitting in change control?
Dividing a large change into smaller requests that each fall below the level needing senior approval. It can be deliberate or simply the result of changes arriving one at a time. Either way, the cumulative effect escapes review. A common safeguard is a cumulative threshold, so that once approved changes pass a set total, every further request goes to the committee.
Is it fair to reject the vendor explanation?
Only on evidence, and the example shows it. The contract specified configuration of the standard package, the vendor delivered that, and the gap analysis revealing the need for customization was in the committee's own papers before the contract was signed. A vendor can still perform badly, and a diagnosis should say so where the record supports it. Here the record points to the approvals.
Where can I find a free MGT 640 Topic 8 sample paper?
The complete governance failure diagnosis is on this page: the outcome, each gate, the split change requests, the re-baseline, the pattern and the rules that would have changed it. Name the canceled or troubled project your course assigns, and a free diagnosis can follow its own gate record.
What pattern does the MGT 640 Topic 8 diagnosis find?
At every gate the committee noted information rather than deciding on it: a case without owners, a bid contradicting its own gap analysis, change requests below the threshold and a new schedule approved without a new case.