Setting Expectations to help with Productivity

First, ask yourself...
Do expectations (or lack thereof) influence your team's effectiveness or productivity?

Today's organization is run (and structured) much differently than that of years past. Organizations today are MUCH more interdependent - meaning other people and other departments play a role (sometimes a significant one) helping one another accomplish ultimate goals. We interact with more people in many more areas of the organization as well- we are no longer confined to our silos within our respective departments or locations/branches. Finally, it is much more common today to "bounce around" within one company due to broader job descriptions, the desire to have cross-functional skills and employees, and the increase of technology.

The above are just a few reasons why having clear expectations for our teams is so vital. These expectations are referred to as Team Operating Norms (TONs). A few examples of common TONs are: the way members of the team approach conflict, the process for meetings, how we give/receive feedback, and how we communicate with each other.

TONs help to ensure that any new members joining the team (whether the stay will be permanent or simply for a single project) are crystal clear on expectations, and understand how to interact with the other members of the team - especially when the new team members are already used to working and interacting in a DIFFERENT way based on their last job or team. And don't forget, TONs also help to significantly increase productivity, strengthen relationships, and enhance the effectiveness of communication amongst the current members of the team!

Employee Teamwork

First, ask yourself...
Does my team consistently fail at solving problems right, the first time?

Imagine going to the doctor because you have developed a rash on your arm. The doctor says that you must have rubbed up against some poison ivy, and gives you some ointment. But strangely, 2 months go by and it has gotten worse. You go to another doctor, and come to find out that the reason for your rash is due to you being allergic to a food you have been eating for lunch lately! The first doctor obviously tried to solve the problem without first making sure to identify the root cause.

Of course, this sort of situation is one none of us ever want to be in. But why is it that at work (especially when working as a team) we are always so quick to think we "know the answer" to a problem, and begin to "solve" it without first spending the proper amount of time to be 100% sure? This results in feelings of frustration and helplessness, and anger.

Perhaps the most important step to being able to truly SOLVE problems as a team is to make sure we take the proper time to find the true root cause. This simple act will make the team more efficient, and can also increase the level of buy-in the team members have towards solving the problem. Spending 5-10 minutes as a team to brainstorm possible causes is time very well spent, in comparison to spending weeks (or even months) failing to solve the issue because the team is focused on the WRONG root cause!

This post was made by Jeff Rosset, Pesident of Compass Coaching & Development which is a firm that helps clients around the Chicago area increase employee engagement by providing leadership and organizational training and development services. Learn more at http://www.Compass-CD.com