Routine Communication

What kinds of tasks fall into each quadrant? Therefore, what kinds of communications norms do we need? routine/autonomous To the extent team members are working autonomously on tasks which remain static, there is little need for a lot of cross-team communications. Communications should be: Minimalist. Local. Compliance oriented where necessary. Automated whenever possible. The danger for virtual teams is that the â€Å"disconnected† feeling of a distributed team sometimes leads to over-reporting as a strategy to give people the feeling of â€Å"knowing what's going on. Sometime team members generate a lot of reporting in order to make sure the team leader â€Å"knows† that they are working. This kind of communication creates sludge in the team's arteries. It is a common cause of information overload which can sometimes result in team members avoiding engaging in the communications which actually are important to the team. The team needs to agree on a strategy to defend itself against communication sludge! Be on the lookout for what can be eliminated. 2 of 5routine/interdependent. Team members need to provide enough information to each other about areas where their routine work is interdependent to enable them to coordinate. Communications should be: Standardized. Organized. Easy. â€Å"Pull† v. â€Å"Push† (You go get what you need when you need it rather than having it pushed at you automatically). The danger for virtual teams is that because we have technology which allows us to exchange and store large amounts of information, we do it because we can without really addressing whether doing it adds value. The team needs to agree on a strategy to manage and coordinate this communication. Choose a few, processes for exchanging critical information and make a commitment to sticking to agreements about when and what will be produced by each member of the team. emerging/autonomous When individuals (or sub groups) on the team notice changes emerging in the work they have been doing, it's critical to make this â€Å"intelligence† available to the team as a whole. Communications should be: Timely (it can't wait for the next face-to-face meeting). â€Å"Push† v. â€Å"Pull† (to make sure that nobody misses a key indicator). The danger for distributed teams is that a weak communications strategy results in missing signals where something new happening in one place is a bell weather for something that will sooner or later have an effect on other parts of the system. A team that doesn't share this kind of intelligence is less than the sum of its parts. The team needs a strategy for scanning, scouting the environment within which they are operating, noticing pattern changes to make sure that important things get up on the team's radar screen soon enough when something which has been static starts changing. But it's not enough to simply report the information, it's critical that the whole team have an opportunity to discuss its meaning.