Friday, October 31, 2014

Organizational Conflict

After reading through Bolman and Deal's chapter regarding interpersonal and group dynamics, I realized that many of the same themes that pervade mainstream management theory are present in their discussion of organizational conflict. They begin with a focus on interpersonal skills and interaction, and then go on to describe factors such as emotional intelligence, management style, and both formal and informal roles within an organizational hierarchy. While these are most certainly important determinants of a groups interaction norms, I find that the chapter does not do much to mention what I find is the greatest source of conflict in an organization: task interdependence.

As I mentioned in last week's post, I work at as a server in a restaurant in my home town over my summers off of school. Overall, I would say that the restaurant team - managers, servers, kitchen, and bus staff - generally experienced a functional and productive amount of conflict. Process disagreements and constructive input were always accepted and appreciated, however leadership was careful to ensure that conflict within the restaurant never got to a level where it interfered with the productivity and satisfaction of the employees or customers. Thankfully, interpersonal conflict such as arguments and personal disagreements were minimal and generally could be worked through. What made the level of organizational conflict functional at the restaurant was the centrality of task interdependence as the source of the conflict. Since each separate team must be both internally functional and externally functional with the other teams to provide service, everyone needed to perform their own tasks efficiently while simultaneously communicating with others. For example, when managers communicated with the staff, it was always relating to what a team or individual was doing and how they were doing it. 

A common source of conflict was slow service. If a manager noticed that a party had been seated for a long time without being served or if a customer raised a complaint, he or she would immediately set about rectifying the mistake by identifying the source of the conflict and consulting the parties involved. For slow service, it meant that either the server was too slow to address the table, get their order, and input it into the ordering system, or that the kitchen did not receive the order or that they had overlooked it in some way (either due to lack of attention or confusion from busy service). Once the source of the conflict was identified, the managers would go about rectifying it by first informing the dependent team of their overlooked table or order, then informing the team or person at fault of their mistake. Finally, they would speak with the customers so as to inform them of the service timing they could expect. This management method allowed for constructive criticism when one's service was less than spectacular while simultaneously addressing potential breakdowns of communication between the service and kitchen teams. Ultimately, this seemed (to me at least) like an effective way to manage the intergroup conflict that arose from task interdependence.

2 comments:

  1. I wonder if there were any situations that festered in the restaurant, where some employee bore a grudge against another employee. Did something like that happen? If so, what transpired between the two employees might properly be described as conflict. In what you wrote about I can't tell. The alternative is that there is a transient disagreement that is quickly resolved. That might happen with some frequency, as poor service from time to time may be inimicable to the restaurant business. I don't know whether that is true or not, but I can imagine it to be the case at any restaurant that is not too pricey. In any event, quick resolution is not what we mean by conflict. There needs to be sustained disagreement that often gets personal in nature and fairly emotional for the participants.

    It sounds like the management at your restaurant tried to be proactive about the issue - nipping the problem in the bud as best as they could. That is good an proper. It also sounds like they didn't take sides and simply were trying to make the service better. That sort of an approach can work.

    ReplyDelete
  2. Luckily, there was not too much in terms of sustained and insurmountable conflict between employees. On occasion, there would be frictions between employees and managers over certain decisions. For example, one of the more senior severs who had been with the restaurant for many years felt that she was not getting sufficient party sizes when being seated by the hostesses and managers. So she brought this to the attention of the managers but did so in a highly emotional and accusatory way. This led to a fairly intense conflict between her and the manager, which ultimately ended in this server getting all of her hours for the next two weeks cut. I'm uncertain whether this was an optimal way to deal with this specific conflict, but the manager's exercise of coercive power at least seemed to eliminate the symptoms of the conflict.

    I think that a large part of why the restaurant didn't see much organizational conflict was because most of the task and procedural conflict that resulted from trying to improve efficiency and innovation were centralized to a few team leaders. Managers and head chefs would discuss and debate dishes to retire and new dishes to put on the menu. However this sort of conflict was actually highly functional and did not drag in personal disagreements.

    ReplyDelete