Supporting Team-Based Work
Supporting Team-Based Work
Join the DZone community and get the full member experience.Join For Free
The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.
Many of the companies I work with want the benefit of the team effect in software development. The managers in these companies recognize the enormous benefits teams provide to the company–creativity, engagement, learning.
However, in many of these companies, the HR systems focus only on individual accomplishment. Individual goals, individual bonuses and merit-pay processes cause real damage when the desired behavior is collaboration and team work. I’ve talked to managers who spend the year building up teams, only to see their work undone by the review and ranking process.
In a small company, managers have the ability to directly change the goal, bonus, and pay systems. In large companies, or in companies where the software group is only one division, changing those policy may seem impossible.
Until you persuade HR to change to more team-focused strategy, take these steps to minimize competitive focus and amplify the emphasis on shared goals.
Amplify the Importance of Team
Make the expectation for teamwork behaviors explicit. Make team performance a significant portion of each team members performance expectation. By significant, I mean 60% or more. Anything less communicates that teamwork is “nice to have,” but not essential. When people must rely on others to achieve a useful goal, tie the success together in performance expectations.
Dampen the Race for Rankings
Minimize the competitive focus by reducing stratification. Rather than have five or more ratings, use only three categories.
The top category is for people who are truly exceptional. They may out-perform the system, make an extraordinary contribution on a project, or stand out in some other way. In most organizations, there aren’t many of these people, and most people know who they are and agree on who they are.
The bottom category is likewise small and for people who are exceptional. This is for people who clearly are unable to perform, due to lack of skills, poor fit for the job or some other reason. Note: Before you put someone in this category, check the manager’s contribution to the problem. Most performance problems are not the sole fault of the employee. When an employee is in the wrong job, or clearly lacks the skills, that points to problem with the hiring process, not the person. Of course, it doesn’t make sense to keep someone in a job they cannot do. But let’s not blame the individual when a management process has failed.
The middle category is the big one–for the people who are doing their jobs well and performing within the bounds of the system. Many companies waste an enormous amount of managers’ time arriving at fine-grained but spurious distinctions between employees contribution. Such distinctions are meaningless in collaborative and interdependent work. Managers’ time would be better spent working to improve the system so everyone does better.
A three-tier strategy based on normal variation and exceptions reduces the unhealthy effects of ranking individuals against each other. As a bonus, it frees up a great deal of time that managers would otherwise spend on suspect differentiations.
Don’t Treat People as Fungible
Don’t waste time comparing people as part of the evaluation. Comparing people within a team or group fosters division and competition. Comparing people across teams or functions is irrelevant–except when considering promotions.
Emphasize Interdependent and Collaborative Work
Eliminate individual performance bonuses. Some companies give team bonuses to recognize a team that has solved a particularly difficult problem, saved the company a huge amount of money, or launched a successful product. Since the bonus goes to the team, in most cases, the team members divide it equally.
Even without formal team bonuses, you can use the pot of money HR allocates for individual bonuses in this way.
Aim for Policies that Focus Improving the Organization
In the long run, consider some form of profit sharing or gain sharing based on the over-all performance of the department. Couple this with a clear emphasis on improving team and system performance and meeting business goals. This reduces the likelihood that people will skew their effort towards meeting individual goals at the expense of unit wide business goals.
Take a Stand
Many managers tell me that HR forces them to act out harmful policies related to annual evaluations, ratings, and rankings. HR is there to support performance, not disrupt it. Talk to them about the detrimental effects you are seeing. Share the research. Decline to participate in the ranking mess. If HR insists, distance yourself from the mess and have an HR manager communicate the ratings/rankings.
I have talked to many managers who have opted out of the rating and ranking madness and none of them have been fired. And several of them–through their action–started the conversation and change towards policies that support rather than hinder team work.
Opinions expressed by DZone contributors are their own.