12 May Teamwork — Or Not?
“Talent wins games, but teamwork and intelligence win championships.” Michael Jordan1
Teamwork offers significant advantages over individual work through better communication and synergy, leading to enhanced problem-solving, innovation, and creativity. It often results in a positive work environment and improved morale, although this is not always the case. Most people prefer working in teams rather than individually, and I have always enjoyed being part of teams.
Here are a few examples from my work experience that highlight a lack of teamwork:
I was part of the Executive Group at a software company. During a meeting, a peer who had previously privately agreed with me changed his stance and opposed me in front of the group. When asked why he did that afterward, he responded, “I will look better if I oppose you and make you look worse.”
I led a technical support group in a similar situation at another software company. The VP of Sales told me he didn’t care if he created problems for my team with customers. Teamwork was not a concept that he practiced.
I joined Deloitte as an “advanced hire,” meaning they recruited me based on my work experience rather than as a recent university graduate. Before an orientation meeting, I requested a non-smoking, single room, but was assigned a roommate who snored loudly, like an airplane taking off. After insisting on my preference, the hotel moved me to a room of my own. The next day, during the session, a partner warned me about my insistence on changing to a room without a roommate. He was visibly annoyed and told me in front of the group that all Deloitte employees, even firm partners, have roommates when they travel.
Throughout the orientation, teamwork was emphasized as essential for success at Deloitte. However, back in the Chicago office, teamwork was not widely practiced. For example, when I secured the Chicago Transit Authority (CTA) as a client, a partner from Boston attempted to take over the project, claiming more experience with urban transportation. Despite his efforts, the CTA chose to sign with the Chicago team. Teamwork? I don’t think so. This situation almost derailed the engagement, and the CTA might have chosen to work with another firm if it hadn’t been for my previous business experience with the finance and IT departments.
I faced another challenge shortly afterward while planning the staffing for the CTA project. I identified a qualified individual in St. Louis who had successfully implemented the selected Payroll/Human Resources (HR) system at another urban transit system. I discovered that he was not on a current billable assignment; in Deloitte’s terminology, he was “on the beach.” I contacted the partner this individual reported to and requested that he be assigned to our project. (The billable revenue would go to the St. Louis partner he reported to.) However, the partner stated that the individual was unavailable because he refused to release him due to his dislike of my reporting partner. This lack of teamwork was incredibly frustrating.
Soon after, the partner in charge of the Deloitte Chicago office consulting practice asked about my experience. I suggested that partners attend the new hire orientation to understand the importance of teamwork. He seemed startled by my suggestion. Despite these challenges, I remained optimistic about my role at Deloitte and was satisfied with my experience with the firm.
In conclusion, I believe in the many positive benefits of working in a team. However, some people in the corporate world are more interested in their own agendas and careers and may sometimes sabotage others. So be aware!
1 1 https://www.elitecolumn.com/michael-jordan-quotes/michael-jordan-quotes-2/#google_vignette