26.10.2014 Views

„‚ CONDITIONS THAT HINDER EFFECTIVE COMMUNICATION

„‚ CONDITIONS THAT HINDER EFFECTIVE COMMUNICATION

„‚ CONDITIONS THAT HINDER EFFECTIVE COMMUNICATION

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

internal resource people (consultants) who can aid in feedback meetings. These people,<br />

while not normally members of the group actually conducting the feedback meeting, are<br />

still internal to the total system receiving feedback; and their continued presence in that<br />

system combined with system-level diagnosis provides support for the feedback activity.<br />

The focus of the feedback activity is on issues related to existing work units within<br />

a hierarchy. The design is thus best used for work on within-group issues and also for<br />

work on problems of communication up and down the hierarchy of the organization.<br />

The waterfall concept is both a strength and a weakness. Although having feedback at<br />

higher levels before having feedback at lower levels builds support for the activity, if a<br />

breakdown occurs at any one level, it is highly likely that the activities at all levels<br />

below that one may be less effective. Obviously, the training and skills of the internal<br />

resource people are critical. They need to be familiar with the content of the feedback<br />

data as well as to possess process skills.<br />

Subordinate Group<br />

Another variation on the family-group approach has been suggested by Schein (1976).<br />

Using the family group has risks because of the possibility of conflict between the role<br />

of the supervisor as the leader of the meeting and the role of the supervisor as the<br />

possible focus of feedback. The supervisor may do things that hinder the group’s ability<br />

to work with data. Schein offers an alternative to the “top-down” survey-guideddevelopment<br />

approach: a “bottom-up” subordinate-group approach. In this case,<br />

subordinates in the family group receive the feedback and work with it with the<br />

assistance of a consultant before the supervisor ever sees the data. Only after<br />

considerable work has been done is the supervisor given the data and asked to join the<br />

meeting. Thus, by the time the supervisor does join the meeting, the data have been<br />

validated, the group feels some ownership over them, and the process of using them as a<br />

problem-identification and -solving tool has been started. Much of the initial anxiety,<br />

fear, and defensiveness is defused by having the supervisor absent.<br />

Although the subordinate-group feedback design makes use of existing work units<br />

(the family group), it uses them in parts rather than as a whole (for example, part of the<br />

unit—the subordinates—meets to work with the data before the whole unit meets).<br />

Clearly the sequence of receiving data is bottom-up, and the design involves an external<br />

consultant. As the bottom-up sequence runs contrary to the normal methods of<br />

distributing information, it has consequences for power relations and may be very<br />

threatening to the supervisor.<br />

Thus, a competent and credible outside consultant is important; that consultant has<br />

the significant role of helping the supervisor to avoid natural feelings of defensiveness<br />

and of aiding the subordinates in using the data constructively. The design is particularly<br />

useful for working on issues of power and on particular issues of superior-subordinate<br />

relations and communications within the particular work unit. By removing the superior,<br />

the design also may facilitate clearer and more open communication among work-unit<br />

members about problems of relationships among themselves. The greatest risk,<br />

206 ❘❚<br />

The Pfeiffer Library Volume 6, 2nd Edition. Copyright ©1998 Jossey-Bass/Pfeiffer

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!