| Course | MGMT 527 Leading Project Teams (MGMT527) |
|---|---|
| Module/Week | 3 |
| Assignment | Team Leadership in Practice |
| Paper type | Case study research paper |
| Length | about 1,337 words, 5 double-spaced pages plus title page and references. Course guide: per the course guide, a 4-5-page research-based paper in current APA format with a title page, an introduction and a conclusion, presenting three cases of engaged team performance and one case of poor team development, with at least six references (three from peer-reviewed journals) besides the Starbird and Cavanagh text and the Bible |
| Format | APA 7 student paper |
| Points | 150 |
| School | Liberty University Online |
| Program | MS in Project Management |
| Where it sits | Module/Week 3 in Liberty's published MGMT 527 course guide; current sections can differ |
| Updated | October 2026 |
Free sample paper for MGMT 527 Week 3
Engaged Teams Under Pressure: Three Cases of Team Success and the Columbia Mission Management Team
[Student Name]
School of Business, Liberty University
MGMT 527: Leading Project Teams
Team Leadership in Practice
[Instructor Name]
[Date]
The three successful cases and the contrasting case are real and are described from their published accounts; the analysis is written for this sample; the requirements follow Liberty's public course guide for MGMT 527.
Engaged Teams Under Pressure: Three Cases of Team Success and the Columbia Mission Management Team
Teams succeed or fail on more than talent. Some of the most capable groups in the world have failed in public, and some ordinary groups have done extraordinary work under pressure. Starbird and Cavanagh (2011) argue that engaged team performance comes from aligning a team's processes and its people around shared results. This paper examines three teams that achieved that alignment, cardiac surgery teams that learned a difficult new operation, the rescuers of 33 trapped Chilean miners and the Pixar filmmakers who critique one another's work, and identifies four reasons they succeeded. It then contrasts them with NASA's Mission Management Team during the final flight of the space shuttle Columbia, where the same four conditions were missing.
Case 1: Cardiac Surgery Teams Learning a New Procedure
When sixteen U.S. hospitals took up minimally invasive cardiac surgery, Edmondson et al. (2001) followed their operating teams. The technique changed how surgeons, anesthesiologists, perfusionists and nurses had to coordinate because the surgeon could no longer see and touch the heart directly. The hospitals bought the same equipment and attended the same training, yet some teams mastered the procedure while others abandoned it. The successful teams followed a recognizable path. Their surgeons treated the new operation as a team learning project rather than a technical add-on, chose team members deliberately and kept the same team together for early cases, rehearsed the procedure before operating, and met to review cases afterward. In those teams, nurses and perfusionists spoke up during operations because the surgeon had invited them to, and the team improved quickly. The study's central lesson is that the same technology produced different results depending on how the team's leader framed and structured the work.
Case 2: The Chilean Mine Rescue
In August 2010, a collapse at the San José copper and gold mine in northern Chile trapped 33 miners about 700 meters underground. Rashid et al. (2013) describe how the rescue, led by the engineer André Sougarret, drew together government officials, the state mining company, drilling contractors, international specialists and NASA advisers. The leaders did not wait for a single perfect plan; they pursued several drilling approaches at once and kept the teams working on them informed of each other's progress. Seventeen days after the collapse, a drill reached the miners and returned with a note saying all 33 were alive. Sixty-nine days after the collapse, every miner was lifted to the surface in a specially built capsule. Rashid et al. (2013) emphasize the leaders' willingness to admit what they did not know, to bring in expertise from outside, and to keep hope realistic while testing many options.
Case 3: Pixar's Braintrust
Catmull (2008), then president of Pixar, described how the studio built a culture in which films that begin, in his words, as ugly and unformed are made good through candid collective critique. Its central mechanism is the Braintrust, a small group of experienced directors and storytellers who watch a film in progress and give its director notes. The group has no authority: the director decides what to do with the notes. Catmull explains that removing authority from the critics made candor safer, because the director could listen without feeling overruled. Pixar also holds daily reviews at which animators show unfinished work to colleagues. The studio's record of commercially and critically successful films in its first two decades, and its recovery of Toy Story 2 when that film was in trouble, illustrate the value of a team process built for honest feedback.
Why These Teams Succeeded
Four reasons appear in all three cases. First, the leaders framed the work as learning rather than execution. The cardiac surgeons, the rescue leaders and Pixar's directors all treated uncertainty as normal and expected their teams to learn as they went. Second, each team had structures that brought people together around the work: rehearsals and case reviews in the operating room, coordinated drilling teams in Chile and regular film reviews at Pixar. Third, candor was protected. Nurses could speak up during surgery, rescuers could report bad news, and Pixar's critics could speak frankly because they held no authority over the director. Fourth, the leaders drew on expertise beyond their own rank, inviting perfusionists, foreign drillers and colleagues from other films into the decisions.
These reasons fit what research says about team leadership. Pooling studies of who leads inside teams and how, Burke et al. (2006) found that both task-focused and person-focused leader behaviors were related to team effectiveness, and that empowering behavior was particularly related to team learning. Zaccaro et al. (2001) argue that team leaders work largely by shaping the team's shared understanding, motivation, emotional climate and coordination, rather than by directing each task. Starbird and Cavanagh (2011) make a similar point in practical terms: engagement grows when people see the line between their own tasks and the team's results and work inside processes that invite their contribution. Lacerenza et al. (2018) add that team development interventions, especially structured debriefs after performance, are among the most dependable ways to improve teamwork, which matches the case reviews of the surgical teams and the daily reviews at Pixar.
The Contrasting Case: Columbia's Mission Management Team
On January 16, 2003, a piece of insulating foam broke from the external tank of the space shuttle Columbia during launch and struck the left wing. During the sixteen-day mission, engineers on a debris assessment team grew concerned and sought satellite or other imagery of the wing, but their requests did not reach or persuade the Mission Management Team, which concluded that foam strikes were a maintenance issue rather than a flight risk. On February 1, 2003, Columbia broke apart during reentry, and all seven crew members were lost. The Columbia Accident Investigation Board (2003) concluded that NASA's organizational causes were as responsible as the physical cause, citing a culture in which past success with foam strikes had made them seem acceptable and in which dissenting engineering views struggled to be heard.
Measured against the four reasons, the Mission Management Team lacked each one. Its meetings framed the foam strike as a known issue to be closed rather than an uncertainty to be learned about. Its structure separated the engineers who held the concern from the managers who made the decision. Candor was not protected; the board found that engineers felt unable to press their concerns more forcefully. And the team did not reach for available expertise, since the requests for imagery that might have answered the question went unfulfilled. The individuals involved were capable and committed, which is the most sobering lesson of the case: without the right team processes, capability was not enough.
A Biblical Perspective
Paul describes the church as a body in which no member can tell another that it is not needed, and in which the parts that look least important turn out to be the ones the body cannot do without (English Standard Version Bible, 2001/2016, 1 Corinthians 12:21-22). The Columbia engineers were treated as the weaker members of the body, and their concern was the one the mission most needed. The successful teams in this paper honored every member's contribution, from the perfusionist to the drilling contractor to the animator showing unfinished work. Solomon's observation that plans fail without counsel and succeed with many advisers (English Standard Version Bible, 2001/2016, Proverbs 15:22) describes Pixar's Braintrust almost exactly. A Christian team leader has both a practical and a moral reason to build teams in which every voice can be heard.
Conclusion
The three successful teams in this paper worked in very different settings, yet they shared four conditions: leaders who framed the work as learning, structures that brought people together around the task, protected candor and a willingness to draw on expertise regardless of rank. The Columbia case shows that the absence of these conditions can defeat even an exceptionally talented organization. For a project manager, the practical implications are concrete: frame a new project as a learning effort, hold rehearsals and reviews, make it safe and expected for team members to raise concerns, and seek out the person who knows the most about a problem regardless of where that person sits on the chart. These are the processes through which talented people become an engaged team.
References
Burke, C. S., Stagl, K. C., Klein, C., Goodwin, G. F., Salas, E., & Halpin, S. M. (2006). What type of leadership behaviors are functional in teams? A meta-analysis. The Leadership Quarterly, 17(3), 288-307. https://doi.org/10.1016/j.leaqua.2006.02.007
Catmull, E. (2008). How Pixar fosters collective creativity. Harvard Business Review, 86(9), 64-72.
Columbia Accident Investigation Board. (2003). Report of the Columbia Accident Investigation Board (Vol. 1). National Aeronautics and Space Administration.
Edmondson, A. C., Bohmer, R. M., & Pisano, G. P. (2001). Disrupted routines: Team learning and new technology implementation in hospitals. Administrative Science Quarterly, 46(4), 685-716. https://doi.org/10.2307/3094828
English Standard Version Bible. (2016). Crossway. (Original work published 2001)
Lacerenza, C. N., Marlow, S. L., Tannenbaum, S. I., & Salas, E. (2018). Team development interventions: Evidence-based approaches for improving teamwork. American Psychologist, 73(4), 517-531. https://doi.org/10.1037/amp0000295
Rashid, F., Edmondson, A. C., & Leonard, H. B. (2013). Leadership lessons from the Chilean mine rescue. Harvard Business Review, 91(7/8), 113-119.
Starbird, D., & Cavanagh, R. (2011). Building engaged team performance: Align your processes and people to achieve game-changing business results. McGraw-Hill.
Zaccaro, S. J., Rittman, A. L., & Marks, M. A. (2001). Team leadership. The Leadership Quarterly, 12(4), 451-483. https://doi.org/10.1016/S1048-9843(01)00093-5
What the MGMT 527 Week 3 instructions ask
Team Leadership in Practice falls in Module/Week 3 of MGMT 527, the same week as the Forum 2 thread, after Part II of Lead Like Jesus Revisited and chapters 5 and 6 of Starbird and Cavanagh. The guide sets its shape clearly: a research-based paper of four to five pages in current APA style, built on case studies of team cultures. Three of the cases must show engaged team performance, and the paper has to work out why those teams succeeded; a fourth case, one of poor team development, is then contrasted with them. A title page, an introduction, a conclusion and a reference page are required, and the reference page must list six or more sources, three from peer-reviewed journals, not counting the course text and Scripture.
How this MGMT 527 Week 3 example is built
After a short introduction stating its claim, the paper takes each successful case in turn. The cardiac surgery case draws on Edmondson, Bohmer and Pisano's study of sixteen hospitals adopting a new operation, the rescue case on Rashid, Edmondson and Leonard's account of the Chilean mine rescue, and the creative case on Catmull's description of the Braintrust. A comparison section then names four common reasons for success and ties each one to the meta-analysis of functional team leadership by Burke and colleagues and to Starbird and Cavanagh. The Columbia section uses the accident board's report to show the same four conditions missing. A biblical section reads Paul's body metaphor against the Columbia case, and the conclusion turns the reasons into practices for a project manager.
MGMT 527 Week 3 grading rubric: where the points go
Graders of this paper look first at whether it does the analytical work the guide names: three engaged teams described accurately, a clear account of why they succeeded, and a contrast case that illuminates those reasons rather than standing apart. Cases drawn from published sources are stronger than personal recollection, because the reasons for success can be checked. The six-reference minimum, with three peer-reviewed journal articles, is counted separately from Starbird and Cavanagh and the Bible. Integration of the course text and of Scripture is expected to shape the analysis. Clear organization, an introduction that states the paper's argument, a conclusion that does more than repeat it, and current APA form on the title page, headings and references complete the evaluation.
MGMT 527 Week 3 help: mistakes that cost points
Many drafts of this MGMT 527 paper tell four stories and simply stop. After the cases, write a section that compares them and names the reasons for success in your own words, and then use those same reasons to explain the poor case. Choose cases with published accounts you can cite, because a reason for success that a reader can check in print persuades more than one remembered from work. Keep each case summary short, about a paragraph or two, since the comparison carries more weight than the retelling. Do not let the length run past five pages; tighten summaries before cutting analysis. Check that each of the three journal sources does real work, such as supporting a reason with research, and that the biblical integration speaks to the cases directly.
Related MGMT 527 sample papers
Other MGMT 527 weeks
- MGMT 527 Week 1: Forum 1: An Engaged Project Team
- MGMT 527 Week 2: Forum 1 Replies: Conflict, Cohesion
- MGMT 527 Week 4: Forum 2 Replies: Empowering Teams
- MGMT 527 Week 5: Forum 3: Conflict on a Project Team
- MGMT 527 Week 6: Organizational Team Assessment
- MGMT 527 Week 7: Forum 4: Leading a Dispersed Team
- MGMT 527 Week 8: Forum 4 Replies: Virtual Teams
MGMT 527 Week 3 questions, answered
What is MGMT 527 Team Leadership in Practice?
A 150-point case paper due in Module/Week 3 that presents three cases of engaged team performance, explains why they succeeded and contrasts them with one case of poor team development.
Where can I find a free MGMT 527 Week 3 sample paper?
A finished Team Leadership in Practice paper for MGMT 527 Week 3, built on cardiac surgery teams, the Chilean mine rescue, Pixar's Braintrust and Columbia's final flight, appears in full here.
How many sources does the MGMT 527 Team Leadership paper need?
Six or more references, three of them from scholarly peer-reviewed journals, counted in addition to the Starbird and Cavanagh textbook and the Bible.
What did the Columbia Accident Investigation Board conclude about teams?
The board found that NASA's organizational culture and decision practices contributed to the loss as much as the foam strike, including engineers' concerns that did not reach decision makers.
What is Pixar's Braintrust?
A group of experienced filmmakers who review a film in progress and give its director candid notes; the group has no authority to impose changes, which leaves the decisions with the director.
Use it as a model, or ask for your own
This paper is an original model written by our desk for study. It is not a submitted student paper and not an official Liberty University document. Read it for structure and reasoning, then write your own to the instructions in your Canvas course. If you want a version built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Ask for a custom MGMT 527 Week 3 sample · All MGMT 527 weeks · All courses