ORG 5013 Module 4 Virtual Trust and Relationship-Building Plan Example

Blame Travels Faster Than Data: Rebuilding Trust Across a Three-Site Payroll Implementation Team

Student Name

American College of Education

ORG5013: Organizational Leadership in the Virtual Workplace

Module 4 Assignment

Instructor Name

August 23, 2027

Introduction

Earlier modules in this project found that Prairie Ledger's implementation team, sixteen people setting up payroll software for clients from Kansas City, Manila and Monterrey, has a trust problem as well as a coordination problem. Only half of the members agreed that colleagues at other sites would do their part on time, and each site tended to explain delays by the behavior of the others. New tools and a team charter address some of the causes. This paper focuses on trust itself: what kind of trust is missing, what research says about building trust at a distance and what changes in the team's structure and habits will rebuild it.

What Trust Is Made Of

Mayer et al. (1995) described trusting someone as accepting exposure to that person's actions because one expects them to behave in ways that matter to oneself, and they named three qualities that make someone seem trustworthy: ability, benevolence and integrity. Ability is competence in the relevant area; benevolence is the belief that the other person cares about one's interests; integrity is adherence to principles one accepts. Applied to our team, the Module 1 evidence suggests that members rarely doubt one another's ability, since every site does skilled work. The doubts concern reliability, an aspect of integrity, and, between sites, a sense that the others do not much care what happens after the work leaves their hands.

How Trust Forms Across Distance

Two studies explain why our trust has worn thin. Jarvenpaa and Leidner (1999), studying global virtual student teams, found that some teams developed swift trust at the start, built on early enthusiasm and frequent, predictable communication, but that this trust was fragile and depended on members' continued responsiveness and follow-through. Wilson et al. (2006) found that trust in teams communicating electronically starts lower than in face-to-face teams but grows over time, eventually reaching similar levels. Our team's experience fits both findings. Trust grew while the team was small and stable, then eroded as missed replies and slow handoffs accumulated, each one read by the waiting site as evidence of indifference.

Change One: Cross-Site Client Pods

The most important change is structural. Today, work moves in stages from one site to the next, so no one sees a client from start to finish and each site experiences the others mainly as a source of delay. I will reorganize the team into four client pods of four members each, every pod including at least one person from each site. Each pod will own its clients from kickoff to go-live, share the client's success or failure and meet weekly in its own overlap window. Members will still specialize in mapping, configuration or training, but their colleagues at other sites become teammates on a shared project rather than an upstream or downstream station.

Change Two: Visible Reliability

Integrity, in the sense of doing what one says, can be made visible. Each pod will publish response commitments in its tracker space: any question that stops someone's work gets a reply by mid-morning at the site that receives it, handoff videos recorded before the end of each working day and decision items updated within one day of a client change. A simple monthly report will show each pod how often it kept those commitments, by site. The purpose is not to rank individuals but to replace impressions with facts; if Monterrey's answers are on time 95 percent of the time, the belief that Monterrey is slow will have to change.

Change Three: Time for Relationships

Benevolence grows when people know one another as people. Each pod will spend fifteen minutes of its weekly meeting on non-work conversation, with a rotating member choosing the topic, such as a photo from the weekend or a local food. Once a month, the whole team will hold a short optional social call at a rotating time. New members will be paired with a buddy from a different site for their first three months. The two in-person gatherings proposed in Module 3 will include time set aside for pods to work together in the same room and for the whole team to share a meal.

Change Four: Handling Failure Without Blame

Trust is tested most when something goes wrong. When a go-live slips or a client complaint arrives, the pod will hold a review within a week that asks what happened in the process, what each site knew and when, and what will change, rather than who was at fault. I will lead the first several reviews to model the tone, and the written summary will name process causes rather than people. Repeated individual performance problems will still be handled, but privately and separately from the review, so that the review stays a safe place to share mistakes.

Testing the Pods First

Reorganizing sixteen people at once would itself strain trust, so the pods will start with a pilot. Two pods will form in September and take on the next four new clients, while the rest of the team continues in the stage-based structure. After two months, the team will compare the pilot pods' handoff delays, kept-commitment rates and survey scores with the rest of the team, and pod members will describe what helped and what did not. If the results are good, all four pods will be in place by the start of the new year, after the busy year-end payroll season. Running the pilot openly, with results shared with everyone, also signals that the change is being tested rather than imposed.

My Role

As the team's leader, my own reliability and fairness set the standard. I will answer escalations within the same response window I ask of the team, rotate my own working hours one week a month to overlap with Manila's day, visit each site at least once a year and share credit for successes across all three sites in reports to senior management. I will also say openly, in the first pod meeting, that the earlier structure made blame between sites likely and that it was a design problem, not a character problem, which may help members let go of past frustrations.

Measures and Risks

Progress will be measured through the cross-site trust survey item, now at 50 percent, with a target of 75 percent after six months; the pods' kept-commitment rates; the number of blame-free reviews held; and voluntary turnover, which rises when trust collapses. The main risk is that pods create new divisions, with pods competing or one pod becoming a favorite. Rotating one member between pods each half year and sharing pod results openly should limit that risk.

Conclusion

The team's trust problem lies mainly in reliability and benevolence across sites, worn down by a structure that made colleagues at other sites look like obstacles. Research shows trust at a distance can grow but stays fragile without follow-through. Cross-site pods, visible reliability, time for relationships, blame-free reviews and changes in my own behavior aim to rebuild it. Module 5 will consider how to lead this team through change and crisis without losing the trust these steps create.

References

Jarvenpaa, S. L., & Leidner, D. E. (1999). Communication and trust in global virtual teams. Organization Science, 10(6), 791-815. https://doi.org/10.1287/orsc.10.6.791

Mayer, R. C., Davis, J. H., & Schoorman, F. D. (1995). An integrative model of organizational trust. Academy of Management Review, 20(3), 709-734. https://doi.org/10.2307/258792

Wilson, J. M., Straus, S. G., & McEvily, B. (2006). All in due time: The development of trust in computer-mediated and face-to-face teams. Organizational Behavior and Human Decision Processes, 99(1), 16-33. https://doi.org/10.1016/j.obhdp.2005.08.001