Archive for category Teams

Stages of Team Development

imageMost materials discuss the four primary distinct phases of team development. These phases include forming, storming, norming and performing (McDonald, 2005). Looking further into the stages it becomes clear that teams progress through these four stages possibly multiple times (Holpp, 1999), before entering a fifth stage which is referred to as adjourning (Scott, 2005).  Analyzing the progress of an actual team  it is clear the team progresses through all of these stages through the course of it’s existence.

The Team

Limited Brands is a large organization with many teams. Over the course of seven years, the Limited Brands‘s Victoria’s Secret eCommerce development team progressed through many iterations of the stages of team development. The team formed in the late 1990’s as a small group of individuals focused on developing a website for the predominantly catalog based organization. This loose team had no strict governance or guidance. In the early 2000’s the site had been established as a leader in internet commerce. The team was in the spotlight within the organization as the business shifted toward digital commerce. New members were added, new skills were learned and the team grew and reformed. Around 2005 the organization began to restructure, separating the traditional clothing side of Limited Brands from the Intimates and Fragrances. Leadership saw a new vision for the ecommerce division. This new vision positioned the Intimates division as a center for not only multi-brand commerce but also as a service for other companies looking to sell online. At this point leadership sought out high end vendors to create a new site architecture and ecommerce platform that would supplant the existing one. The plans for the new site were not widely known. Within the original team however word got around as team members began to consult on the new platform. Slowly members of the original team were moved to the new platform or left the company. The result was a skeleton crew left maintaining the original site.

The stages

This team represents a typical case, common in many organizations where teams are built for a project then dismantled once the project has been completed. The journey these teams progress through is also similar across organizations. Understand the stages and the needs of each stage enables leaders to position their teams for success.

Forming

imageIn the forming stage the team is founded and members tend to share an optimistic view (McDonald, 2005). There is seldom conflict as the group looks to see who fits where. Leaders can facilitate progress through this stage by clarifying the objective of the team, soliciting strengths and weaknesses, identifying roles and defining conflict resolution systems (McDonald, 2005).

The development team at Victoria’s Secret progressed through this phase similar to most organizations. The group came together with a clear focus, create an ecommerce website. The team also waited for roles and responsibilities to be resolved. Over time team member skills began to surface and the team began to organize.

Storming

imageThe storming phase is often one of the most critical phases for a team. It is at this stage that the team begins to understand the true scope of the tasks at hand as well as the nature of the various team members. While this phase is typically credited as one that exhibits personality clashes, and team conflict (McDonald, 2005), more commonly these elements are not readily visible. Frequently the storming phase is hidden in civility and expressed through sarcasm and innuendo (Scott, 2005). Professionals are trained to be polite and civil to each other. It is important to note however that if the team progresses through this phase without resolving differences there may be long lasting liabilities for the team and project (Scott, 2005). This is the phase where the team really learns how to work together. The storming phase results from team members trusting each other enough to say what they honestly feel regardless of the risks (Patnode, 2003). The storming process improves ideas, challenges assumptions and obstacles (Patnode, 2003). While this phase is typically the most uncomfortable it is also the most important and should be encouraged rather than quickly passed over.

The development team experienced many episodes of storming over the project lifecycle. After the initial forming stages as well as after new members joined the team, eventually personalities would reset and voices would be heard. These conflicts were productive and ranged from meeting attendance to application design principles. This team understood the storming phase well.

Norming

imageFinally in the norming stage, the team begins to work together. Fighting and bickering reduces (Scott, 2005) while communication becomes open and honest (McDonald, 2005). At this point leaders should focus on progress and encouragement. Managers should celebrate progress but continue to foster communication (McDonald, 2005).

Looking at the Victoria’s Secret development team there is evidence of multiple norming stages coupled to each storming phase. Through this phase management did in fact continue to encourage communication and worked to improve the team even more.

Performing

Here in the performing stage, clear stable structures appear and the team is able to work toward a shared goal (Scott, 2005). At this point the team works with a high degree of mutual support and respect (McDonald, 2005). Leaders at this stage may feel imagea sense of relief and may be tempted to relax, however there are still activities that will promote continued success in the team. Leaders should work to celebrate the teams successes, recognize the achievements an continue to challenge the team (McDonald, 2005). In most long lasting projects and teams, the progress through these phases tends to be more cyclical where teams slip back into previous stages (Holpp, 1999), managers should be mindful in this stage to watch for team regression to a previous stage (McDonald, 2005).

The development at Victoria’s Secret was no different than those in other organizations. The performing stage was clearly recognizable as the team gelled and produced many successes. Leadership was always ready with praise and additional challenges.

Adjourning

Often neglected in texts is the adjourning stage. The adjourning stage is when the team disbands and the project is ended (Scott, 2005). Many projects end and teams disband with little to no intervention by management. Team members are sent to other teams where their accomplishments and hard work may not be recognized. Management needs to take time and care to integrate these displaced members into the organization. These stars can fade if not transplanted with care.

Thus was the case in Limited Brands. The organization had placed the majority of the attention on the new project yet left the existing team with no means. Team members were left to find their own way to new teams in the organization, while others simply left the company. The adjourning stage of the process can be the most risky. Organizations spend lots of time and money training and building individuals talent and knowledge into business critical assets. Poor execution in the adjourning phase can have significant effects on these investments.

Conclusion

While teams and organizations all will differ, there are core aspects that are universal. These phases of team development are critical to the success of all teams. Individuals in leadership or on the front lines can impact a team’s development and performance by taking these stages into account. Planning for and encouraging the various stages of team development will lead to high performing teams and organizations.

References

Holpp, L. (1999). Managing Teams. New York: McGraw-Hill.

McDonald, T. (2005, Nov). Building an Effective Team. Health Care Registration: The Newsletter for Health Care Registration Professionals , Vol. 15 (Issue 2), pp. p3-4.

Patnode, N. H. (2003, Mar/Apr). Can’t Get To Performing Without Storming. Program Manager , Vol. 32 (Issue 2), p. p42.

Scott, J. T. (2005). Chapter 10: Managing Teams and Work Groups. Concise Handbook of Management: A Practitioner’s Approach , p79-84.

Leave a Comment

Building High Performing Teams

Introduction

Successful teams exhibit elements that can be utilized and fostered by leaders in their own teams to increase performance and collaboration. There are six components leaders should consider when fostering team development. These components include Size, Composition, Governance, Identity, Interaction and Culture. There is not one right composition of these elements rather a unique blending that each group requires to become a high performing team. An example of the impact of these elements can be viewed in the cases of two real teams. The first team, CodeMonkeys, was a software development team assembled to fulfill the coding needs of a major software initiative. The second team, Pixelators, were also software developers but were filing more of a support and maintenance role for a single application. Both of these teams exhibit characteristics from each of the six core elements. The ability of these teams to perform at their maximum was driven by this composition.

Various Elements of Team

Size

The number of members of a team impacts many of the other elements. Smaller teams trend to communicate better and require less governance. Conversely as the size of these teams grows, members tend to collaborate less (Gratton & Erickson, 2007). The Pixelators included 8 core members located in the same office space. The CodeMonkeys on the other hand varied between 30-80 at any given time and were spread between onsite and offshore locations. The smaller Pixelators team clearly collaborated much more frequently than the larger CodeMonkeys team.

Composition

Teams are built for various reasons and those needs dictate the various types of people the team needs. The composition of the teams extends beyond the technical skills of its members and includes some of the softer skills such as managing people and interpersonal communications. When building a team leaders should be mindful of the composition and makeup of the group. The Pixelators was a small team composed of individuals with unique skill sets. At most, two people would be a master of a particular skill. The team also had a breadth of leadership, interpersonal, and management skills to complete the structure. The CodeMonkeys on the other hand was comprised of individuals with similar skills. Members were interchangeable and common. The team lacked a sense of leadership or interpersonal skills and relied solely on the technical makeup to satisfy the needs of the project.

Governance

The governance of teams also varies based on size and makeup. Teams may be managed formally or self-managed. The larger and more sophisticated the monitoring and measurements become the more skilled the managers need to be (Liang, Rajan, & Ray, 2008) which can result in additional levels of skilled resources within the teams. Teams that are able to self govern tend to be given an objective and are able to figure out the means to accomplish it without being told. Managed teams are told not only what the objectives are but how and when to do each component. The CodeMonkeys had many levels of management and tools for tracking performance. The individuals felt no personal empowerment to make decisions on their own. When faced with an unexpected situation members would wait for direction rather than find a solution. The Pixelators represented a rather self directed team structure. While the group had formal management members were given objectives and were able to work out the solutions on their own. This built levels of trust and collaboration within the team making them ultimately more self sufficient.

Interaction

How members of the team communicate and collaborate plays an important role in the ability of the team to succeed. Face to face communication typically provides the best results but various technologies can be utilized to facilitate interactions. It should be noted however that teamwork most successfully occurs after team building, and too often this team building is lacking in online environments (Staggers, Garcia, & Nagelhout, 2008). This can be seen clearly with the CodeMonkey team. This larger group communicated regularly providing status reports and task updates to other members of the team. Little if any team building occurred and interpersonal interactions were minimal. Great distances and cold technology enabled individuals to isolate and function away from the team. The Pixilators worked in close proximity interacting both in person and through technology regularly daily. Team building occurred frequently as members discussed non work events building camaraderie and personal relationships

Identity

In order to build a team the individuals need to feel part of the group. To enable these teams need to be able to demonstrate boundaries of the team versus the rest of the world. This ability to identify the team can be address in multiple ways. Proximity and frequency provide the most straight forward means of designating groups. The closer individuals are to each other, the more likely they are to associate as a group. Additionally the more time these individuals spend together, through technology or in person, the more likely group tendencies will arise. To further enable the team identity leaders should consider a name for the group. Names promote a team atmosphere and support the bonding of a group into a team. The names used here are not the real names for these teams. Leadership however did provide CodeMonkeys with a name for the team. Unfortunately the high rate of turnover, great distances, and lack of interpersonal interactions left the group with a name and no identity. In reality the Pixilators did not have as strong a team name; however the proximity and shared purpose set the group apart as a team with a clear identity.

Ideology

Ultimately individuals bond with others who share similar traits. As teams form they build upon those shared values and ideals. Leaders have traditionally focused on three primary elements of team culture including Norms, Roles, and Goals, however these alone do not provide the means for a group to bond into a team. Norms, the rules and standards the team adopts, Roles each member holds and the Goals the team is working toward can be placed on the team or developed by the team. The CodeMonkeys had volumes of documentation clearly stating the norms of the team, how people should interact, how decisions were made etc. There were also scores of responsibility charts defining roles, and of course the project charter defined the goal. Yet with all these elements readily available none of the members really felt part of that ideal. One might suggest that the team culture needs to be developed and absorbed by the members rather than forced upon by outside entities. The Pixelators had no formal documentation stating role or norms but it was clear overtime that coming late to meetings was not acceptable and certain people were in more leadership positions than others. The team did not have a vision or mission statement but they all shared the same goals and objectives.

Conclusion

These six elements represent areas leadership needs to consider when developing teams. In most cases high performing teams bond on a personal level. Leadership needs to support team development by creating environments and situations with Size, Composition, Governance, Identity, Interaction and Culture that enable individuals to join and create high performing teams.

References

Gratton, L., & Erickson, T. J. (2007, Nov). 8 Ways to Build Collaborative Teams. Harvard Business Review , 85 (11), pp. p100-109.

Liang, P. J., Rajan, M. V., & Ray, K. (2008, May). Optimal Team Size and Monitoring in Organizations. Accounting Review , 83 (3), pp. p789-822.

Staggers, J., Garcia, S., & Nagelhout, E. (2008, Dec). Teamwork Through Team Building: Face-To-Face to Online. Business Communication Quarterly , 71 (4), pp. p472-487.

2 Comments

Bite Size: Fortifying Your Team

imageThe agricultural industry has know for centuries that the earth can only give so many nutrients to a crop before it is exhausted. Letting the fields lay fallow for a season allows the soil to regain some of its value. Unfortunately in this system the field is left unused for a season providing no direct value to the farmer. Crop rotation on the other hand provides similar benefits by utilizing for different crops that consume different nutrients. In this manner the soil is allowed to replenish certain nutrients while continuing to provide direct value with a different crop.

Businesses can benefit from this same methodology, while it is well known that appropriate hours and vacation time are critical to an employee’s sustainability  simply letting the employee lay fallow may not provide as much benefit as adding skill rotation into the plan. In addition to vacation time managers should seek to fortify their team by rotating skills throughout the team on a regular imagebasis. Here in the IT world that may mean things a simple as passing around on-call support. Steven Covey speaks about sharpening the saw, with this in mind a more fulfilling technique would be to rotate R&D responsibilities in the team which would enhance both the skills of the individual and opportunities of the organization.

Rotate your crops and fortify your teams.

, , ,

Leave a Comment

Coffee Notes: Scrum’s, Common sense?

One of the best things about agile methodology is the communication between everyone. At the root of that communication are the daily scrum sessions the teams have to discuss status, plans and issues. These brief meetings each day help keep everyone on tap with the details of the project at hand.

So my question is, is the concept of a daily status meeting that new and unique or just a reiteration of some basic common sense?

I think historically developers have had the leeway of not being truly accountable for their work. Effort and quality were rather subjective. With daily, open communication and open reports noting code quality, the development process can reduce the overall degree of bravado and focus on production.

, , , , , , , ,

Leave a Comment

Follow

Get every new post delivered to your Inbox.

Join 473 other followers