| Course | GM503 Leadership Theory and Practice II |
|---|---|
| Unit | Unit 6 |
| Paper type | Seminar reflection |
| Length | About 800 words, 5 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Management |
| Updated | October 2026 |
Free sample paper for GM503 Unit 6
Rotating Command or Sharing It: A Unit 6 Seminar Reflection on a Mountain Search Team's Night
[Student Name]
Purdue University Global
GM503: Leadership Theory and Practice II
Unit 6 Seminar Reflection
[Instructor Name]
[Date]
The search team, the incident and the classmates are composite; the frameworks and studies cited are real.
The Case
My classmate described a callout for an overdue hiker on a mountain trail in late October. Fourteen volunteers responded. An incident commander stayed at the trailhead with radios and maps, assigned field teams of three to search segments and kept a log. A medical lead, a paramedic, waited to deploy once the hiker was found. Field teams worked through the night in cold rain.
The decisive moment came at about 1 a.m. One field team leader, a geologist who had climbed the area for twenty years, radioed that the assigned segment followed a drainage the hiker was unlikely to have taken, because a recent rockfall had made it nearly impassable. She proposed searching a ridge route instead. The incident commander agreed, reassigned two teams and the hiker was found on the ridge at 3:40 a.m., hypothermic but alive.
My View Going In
I argued that this was not shared leadership but an ordinary chain of command that moved by role. The incident commander held authority at the trailhead; the field team leader held authority in her segment; the medical lead held authority once a patient was found. Each was in charge of a defined piece. That is rotation by role, I said, not sharing.
The Argument
Two classmates pushed back. The first asked who actually decided where to search at 1 a.m. The incident commander held the formal authority, but the direction came from the field team leader, who was neither in charge of the search nor of the other teams. The commander's role was to recognize her expertise and act on it.
The second brought in research. Jennifer Carson and colleagues defined shared leadership as an emergent team property in which leadership influence is distributed among members rather than concentrated in one appointed leader, and found that teams with more shared leadership performed better, especially when members shared a sense of purpose and felt supported (Carson et al., 2007). The point, she said, is not who holds a title but whose influence shapes the team's direction at a given moment.
My mistake was looking for leadership in the org chart of the search; the decision that saved the hiker came from someone the chart did not put in charge of it.
Why I Conceded
The instructor sharpened the distinction. Rotating command, she said, means authority passes from one person to another according to role or phase. Shared leadership means several people influence the team's direction at once, often across role boundaries. In the search, both happened. Authority did rotate by role. But at 1 a.m., the direction of the entire search came from a field team member, the commander's acceptance turned it into a decision, and the medical lead's earlier advice about hypothermia risk had already shaped the decision to search through the night. Influence flowed in several directions at the same time.
Beth Bechky and Gerardo Okhuysen studied how SWAT teams and film crews handle surprises and found that members shift roles, reorganize routines and draw on shared knowledge of each other's work in ways that go beyond formal structure (Bechky & Okhuysen, 2011). The search team showed the same pattern: its formal structure set the frame, but its success depended on members acting beyond it.
What I Still Hold
I still think the formal structure mattered. The incident commander's log and the clear assignment of segments meant the ridge proposal could be acted on quickly, because everyone knew where each team was. Shared leadership worked inside a strong command structure, not in place of it. Pearce and Conger's collection makes a similar point: shared and vertical leadership are not opposites, and teams often need both (Pearce & Conger, 2003).
What I Will Do Differently
I lead a small engineering team that responds to production outages at a software company. When an outage begins, I usually take charge and assign tasks. After this seminar, I plan to add one step to our outage process: within the first ten minutes, ask whether anyone has knowledge that changes where we should look. That is the question the field team leader answered without being asked.
The Question I Still Have
I am not sure how a team builds the kind of trust that lets a commander accept a redirect from the field at 1 a.m. without hesitation. My classmate said it came from years of training together. I would like to know whether teams that work together less often can develop it faster.
References
Bechky, B. A., & Okhuysen, G. A. (2011). Expecting the unexpected? How SWAT officers and film crews handle surprises. Academy of Management Journal, 54(2), 239-261. https://doi.org/10.5465/amj.2011.60263060
Carson, J. B., Tesluk, P. E., & Marrone, J. A. (2007). Shared leadership in teams: An investigation of antecedent conditions and performance. Academy of Management Journal, 50(5), 1217-1234. https://doi.org/10.5465/amj.2007.20159921
Pearce, C. L., & Conger, J. A. (Eds.). (2003). Shared leadership: Reframing the hows and whys of leadership. Sage.
GM503 Unit 6 instructions, in plain terms
In GM503's sixth unit you reflect on a seminar that tested shared leadership against a real setting. Summarize the case in a short paragraph, focusing on the moments where direction was decided. State the view you brought to the session and why it seemed right. Follow the argument as it developed, naming the classmates' points and any research that challenged you. The key distinction is usually between authority that rotates by role and influence that several people exercise at once; explain it in your own words. Say what you conceded and what you still hold, since shared and vertical leadership often coexist. Apply the insight to a team you work in with one specific change. Close with a question the seminar did not resolve. Write two to three first-person pages, suitable for the live session or the posted alternative questions, citing the research used in APA 7.
How this GM503 Unit 6 example is built
The case paragraph describes the October callout, the trailhead incident commander, three-person field teams and a paramedic medical lead. The decisive radio call at 1 a.m. and the ridge reassignment follow. The writer's view going in, rotation of command by role, is stated plainly. Two classmates push back: one asks who actually decided where to search, and another introduces Carson, Tesluk and Marrone's definition of shared leadership as distributed influence. The highlighted sentence names the writer's mistake. The instructor's distinction between rotating command and sharing it, and Bechky and Okhuysen's study of SWAT teams and film crews, explain the concession. A section keeps the value of formal structure, citing Pearce and Conger. The writer adds a ten-minute knowledge question to a software outage process and asks how teams that rarely train together can build the trust the search team had.
GM503 Unit 6 rubric: what earns full points
Graders of this GM503 reflection look for a clear starting view, an accurate account of what challenged it and a precise statement of the distinction learned. The difference between rotating authority and shared influence should be explained in the writer's own words and tied to a moment in the case. Credit goes to engaging research rather than only classmates' opinions. Keeping part of the original view, such as the value of formal structure, and saying why, adds credibility. A specific new step in a team the writer belongs to proves the lesson travels. Any open question should come from something the seminar genuinely left unsettled. Carson and colleagues and Bechky and Okhuysen in the Academy of Management Journal and Pearce and Conger's edited book on shared leadership provide the sources in APA 7, used briefly and accurately.
Common GM503 Unit 6 mistakes, and how to avoid them
GM503 seminar reflections often summarize the case at length and add a short paragraph on what the writer learned. The learning should be the body of the paper. Others announce a reversal but leave out the argument that produced it. A common error is defining shared leadership loosely, as everyone helping, which blurs the distinction the seminar was built around. Some writers drop the value of formal structure entirely, though most teams need both. Applications to the writer's own work are often generic. Describe the case briefly around its decisive moment, state your starting position, follow the argument point by point, explain the distinction between rotating and sharing leadership, say what you still believe about formal structure, add one specific practice to a team you lead or belong to and end with a question about how trust or skill makes sharing possible.
Get a GM503 Unit 6 example written to your instructions
Describe the setting your seminar examined, the argument it had and where you ended up. Written-alternative questions can stand in for a live session, and the Unit 6 prompt and rubric complete the set. Delivered within 24-48h and free the first time, the reflection follows your instructions and keeps classmates' workplaces unidentifiable. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More GM503 papers and MS in Management samples
- GM503 Unit 1: Follower Question Discussion Post
- GM503 Unit 2: Ballpark Turnaround Relational Analysis
- GM503 Unit 3: Admissions Team LMX Study
- GM503 Unit 4: Orchestra Followership Analysis
- GM503 Unit 5: Housing Nonprofit Authenticity Case
- GM503 Unit 7: Servant Leadership Application
- GM503 Unit 8: Distributed Leadership Paper
- GM503 Unit 9: Ethics and Trust Analysis
- GM503 Unit 10: Relational Leadership Portfolio
- GM502 Unit 6: Substitutes Seminar Reflection
- GM501 Unit 6: Management Fashion Seminar Reflection
- GM500 Unit 6: Snowplow Routes Seminar Reflection
GM503 Unit 6 questions, answered
What if the seminar concluded that leadership was not really shared?
That can support an excellent reflection. Shared leadership research sets demanding conditions, and many teams that feel collaborative do not meet them. Record the evidence the session used, the condition that failed, and whether you agree. A reflection explaining why a promising case fell short often shows firmer understanding than one confirming the framework without resistance.
Should my own workplace appear in the reflection, and how much?
Usually a paragraph near the end, enough to show the framework traveling from the seminar case to a setting you know. Some prompts ask for more. Keep the seminar at the center, though, since the reflection is graded on what the discussion did to your thinking. A brief, concrete test of your own team works better than a general comparison.
Can I include points I thought of after the session?
Yes, if they are labeled as later thoughts. Many reflections gain from a point the writer only reached afterward, especially when it resolves a disagreement the session left open. Keep the account of the live discussion accurate, then add the later reasoning in its own paragraph so the instructor can see both and tell them apart.
Where can I find a free GM503 Unit 6 sample paper?
This page carries a full GM503 Unit 6 seminar reflection on a mountain search team's night search, moving from rotating command to shared leadership, with research, a workplace change and APA 7 references.
What is the difference between rotating command and shared leadership?
Rotating command passes formal authority from one person to another by role or phase. Shared leadership means several people influence the team's direction at the same time, often across roles, as when a field team leader's knowledge redirected the whole search.