ORG 5013 Module 5 Virtual Team Change and Crisis Leadership Plan Example

A Typhoon in Manila and a Wrong Tax Table in Ohio: Leading a Virtual Team Through Crisis

Student Name

American College of Education

ORG5013: Organizational Leadership in the Virtual Workplace

Module 5 Assignment

Instructor Name

August 30, 2027

Introduction

Across the four earlier papers I studied why our three-country implementation group was missing go-live dates, chose tools and routines, addressed culture and language and planned how to rebuild trust through cross-site client pods. A team's structure and trust are tested most when something goes badly wrong. This final paper plans how I would lead the team through a crisis, using a scenario built from risks the team actually faces: a client's payroll goes out with an error during the same week that a typhoon cuts power and internet to the Manila members. The plan covers preparation, the first hours, communication, care for people, shared leadership, recovery and learning, and it closes with how the team would apply the same approach to planned change.

The Scenario

On a Friday in January, an Ohio manufacturing client with about 1,100 employees runs its first payroll on our software after go-live. That afternoon its payroll manager calls: employees who live in Kentucky but work in Ohio have had Ohio tax withheld instead of Kentucky tax, because a reciprocity setting was missed in configuration. The client is angry and wants corrected paychecks before its employees' next payday. At the same time, a typhoon has struck Luzon, and three of our five Manila members, including the data specialist on this client's pod, have no power or reliable internet. Two members in Monterrey are on approved vacation. The client's account executive is asking who is responsible.

What Research Says About Leading in Crisis

Wu et al. (2021), reviewing research on crisis leadership, organized leaders' work into what they do before, during and after a crisis, including preparing, making sense of events, deciding, communicating and learning afterward. Weick (1993), analyzing how a firefighting crew's organization collapsed during a wildfire, showed that groups fall apart when shared understanding of roles disintegrates, and that resilient groups keep functioning because members can improvise and each carries a mental picture of the whole role system, so someone can step into a missing role. Hoch and Kozlowski (2014) found that in more virtual teams, structural supports and leadership shared among members matter more for performance than direct supervision. Together, these findings suggest a plan built on preparation, clear but flexible roles and distributed leadership.

Before: Preparation

Preparation happens long before the call. Each pod will maintain a crisis card in the tracker naming, for every active client, a primary and a backup for each role: client contact, configuration, data and testing, with the backup at a different site wherever possible. The company will provide Manila members with a stipend toward battery backup units and mobile internet devices, since typhoons are a known seasonal risk. Every quarter, each pod will run a thirty-minute tabletop exercise on a realistic failure. These steps follow Weick's insight that groups survive disruption when members know the whole system well enough to step into one another's roles.

During: The First Hours

In the first hour, I would take the role of incident lead and open a dedicated crisis channel and tracker item, so that information is in one place, as the Module 2 routines require. Using the crisis card, the configuration backup in Monterrey and the data backup in Kansas City would step in for the unreachable Manila specialist. Within two hours, the pod would confirm the cause, identify affected employees and propose two options to the client: an off-cycle correction payroll on Monday or an adjustment on the next regular payday. The client chooses; our job is to make either work. I would take the call with the client myself, acknowledge the error plainly and commit to times for updates rather than to answers we do not yet have.

During: A Communication Rhythm

In a crisis, silence is filled by rumor and blame. The team would receive short written updates every four hours in the crisis channel, covering what is known, what is being done, who is doing it and when the next update will come, timed so that each site wakes up to a current summary. The client would receive updates at agreed times, by phone and in writing. Senior management and the account executive would receive one daily summary from me, so they do not contact team members directly. When the account executive asks who is responsible, the answer is that the team is responsible and the review will find the process cause, consistent with the blame-free approach set in Module 4.

During: Caring for People

The Manila members facing a typhoon are dealing with a crisis far more serious than a payroll error. My first message to them would ask about their safety and their families and tell them clearly not to work until they are safe and have power, and that their pod has covered their tasks. When they return, they should be welcomed back without pressure to catch up overnight. Members covering extra work in Kansas City and Monterrey would be thanked by name, and overtime would be approved without debate. Caring visibly for people during a crisis is part of the benevolence that the trust plan depends on.

Shared Leadership

I cannot be awake across thirteen hours of time difference. Consistent with Hoch and Kozlowski's findings, each pod's most experienced member will act as incident lead during the hours when I am off, with authority to make decisions within agreed limits, such as approving an off-cycle run or escalating to the client. Handover between incident leads would use the same recorded walkthrough format the team uses for routine handoffs, so that the crisis rhythm builds on everyday practice.

After: Recovery and Learning

Once the corrected payroll is delivered, the pod would hold a blame-free review within a week. Likely findings include a missing reciprocity check in the configuration checklist and a need for a second reviewer for multistate clients. The review's actions would be added to the checklist and the crisis card template, and the scenario would become the next quarter's tabletop exercise. I would also meet the client's leadership to explain what changed, which often strengthens a relationship more than a flawless launch would have.

Applying the Approach to Planned Change

The same principles apply to planned change, such as the company's intended expansion to a fourth site in Bogota next year. Preparation means designing pods that include Bogota members from the start; the communication rhythm means regular, predictable updates about what will change and when; care means asking how the change affects each site's workload and roles; shared leadership means giving pod leads a voice in the design; and learning means reviewing the first months openly. A team that has practiced crisis together is better equipped for change it can see coming.

Conclusion

A payroll error during a typhoon would test every part of the team's new structure: its single source of information, its cross-site pods, its trust and its culture of honest review. Research on crisis leadership, sensemaking and virtual teams points to preparation, backup roles, a steady communication rhythm, visible care for people and leadership shared across time zones. With those in place, the team can recover from a crisis with its trust intact and, ideally, strengthened.

References

Hoch, J. E., & Kozlowski, S. W. J. (2014). Leading virtual teams: Hierarchical leadership, structural supports, and shared team leadership. Journal of Applied Psychology, 99(3), 390-403. https://doi.org/10.1037/a0030264

Weick, K. E. (1993). The collapse of sensemaking in organizations: The Mann Gulch disaster. Administrative Science Quarterly, 38(4), 628-652. https://doi.org/10.2307/2393339

Wu, Y. L., Shao, B., Newman, A., & Schwarz, G. (2021). Crisis leadership: A review and future research agenda. The Leadership Quarterly, 32(6), Article 101518. https://doi.org/10.1016/j.leaqua.2021.101518