Scenario:

When the team members at Widgets, Inc. sat down for their next meeting, they were surprised to see a single piece of paper at each chair.

“What is this?” asked Linda from IT, picking up the single sheet from her chair. “It looks like…”

“A contract,” chimed in Frank from the marketing department, as he turned the sheet over in his hands.

“Exactly,” said Tim. “It’s a team contract. Just like all of you are familiar with your employment contract, this team contract spells out the specifics of your roles and responsibilities for participating on the team. Unlike an employment contract, it’s not legally binding. But it does state how you’re expected to behave in a respectful manner to others—and also the protections you enjoy against disrespectful behavior.”

“But surely we all know each other, Tim,” said Linda. “We’re familiar with one another. We’re practically old friends.”

“Think of the concept of the Johari window,” said Tim. “It’s a concept that dates back to the 1950s that suggests there are certain elements of everyone’s character that are knowable to yourself and to others. But there are other qualities that are only knowable to yourself and still others that are only knowable to others, but not to yourself. In other words, we all have to engage in continual exploration of the self and the impressions we create. Quite often, we may engage in behaviors that are unknowingly harmful.”

“But is this really necessary to achieve our goals?” asked Frank. “Isn’t that what good teamwork is all about? Achieving goals?”

“A more productive way to think of teamwork may be using the GRPI model, or to see effective teams as consisting of goals, roles, processes, and interpersonal relationships. It’s necessary for people to be self-aware about the roles they are playing to improve the processes and their interpersonal relationships to achieve those goals.”

“It’s true,” said Linda. “None of us here want to be offensive to one another, but when we’re focused on an idea, sometimes it can be easy to be dismissive of another person’s feelings, especially when delegating tasks.”

“Rather than delegation, or simply telling you what to do, I prefer to think of myself as empowering you as a leader, or making you aware of your strengths so you don’t feel hampered to take the initiative. That’s another reason for this contract, however, so we’re all able to do so without making other people feel as if their boundaries are being violated. These are also known as high leader-member exchange (LMX) relationships, which are founded upon a mutual sense of trust that members want to do things—and that you know I, as a leader, set rules for the good of the team, not because I’m engaged in egotistical wish fulfillment. I hope to offer you guidance, rather than leading in an authoritarian manner.”

“I’ve always appreciated how you encourage multiskilling,” said Beth from human resources. “In other words, encouraging people to develop skills that stretch beyond those of narrowly defined competencies. For example, you allowed me to give input into the training for the new software we installed, even though I don’t have technical skills, because I was able to use my understanding of learning to determine what aspects of the program would be the most challenging for laypersons. Now, I feel much better equipped to comment on how technology can be integrated into the workday.”

“Anyway, although a contract sounds like a very formal and intimidating document, think of it as something that protects your rights as a team member, not as signing your lives away!” said Tim.

The team members looked visibly more relaxed.

Address the following questions in your response:

What is a team contract?
What is the Johari window?
What are high-LMX relationships beneficial to?
What do the letters in the GRPI model stand for?
How can the GRPI model be used?
What factors are unproductive in team exercises?
What is the key difference between empowerment and delegation?
What does the term multiskilling refer to, and how is it used?
What measures are not advisable to use when measuring team performance?
What is the SMART acronym used for in management?
What should generally be avoided when giving feedback?
What is not beneficial when building a collaborative work environment?