Conflict Management Styles Ion Hong Kong Industries
Conflict Management Styles Ion Hong Kong Industries
Conflict Management Styles Ion Hong Kong Industries
393399, 1999
# 1999 Elsevier Science Ltd and IPMA. All rights reserved
Printed in Great Britain
0263-7863/99 $20.00 + 0.00
PII: S0263-7863(98)00059-3
Department of Manufacturing Engineering and Engineering Management, City University of Hong Kong,
83 Tat Chee Avenue, Kowloon, Hong Kong, People's Republic of China
Review of literature has revealed that little research on conict management has been conducted
in Hong Kong industries despite Hong Kong being one of the world's most competitive economies, and a major commercial, nancial, industrial centre. This paper examines the use of dierent conict resolutions in 63 actual case studies from Hong Kong industries. Contrary to
common perception and previous ndings, `confrontation', as a mode of conict resolution, is
found to be more commonly used in handling conict. And signicantly, almost all of the case
incidents which used the `confrontation' approach were said to have achieved positive consequences. The authors argue that this change of resolution strategy in the past decade could be
due to the increasing number of Hong Kong companies adopting the matrix structure explicitly
or implicitly in carrying their projects. It appears that in Hong Kong industries, the inuence of
the Chinese culture and traditional values in attitude, behaviour and professional practices of
both engineers as well as managers, is diminishing. Although the `withdrawal' and `forcing'
approaches were also being used for certain types of conict, as revealed by some of the case
studies, the consequences are often recognised to be dysfunctional to team work. # 1999 Elsevier Science Ltd and IPMA. All rights reserved
Keywords: conict resolution, conict management styles, case studies, Hong Kong industries
Introduction
In recent years, a number of researchers and practitioners in project management have reported that
there is an increasing trend in the use of cross-functional project teams because of the dynamic nature of
today's projects and their life cycles.1, 2 More and
more, conict is being perceived and accepted as inevitable in such a stressful project-oriented environment.
Project managers should therefore be able to identify
the sources of conicts and apply appropriate resolutions in today's project environment.1 Tjosvold3 and
Deustch4 suggest that when conict is appropriately
managed, it could be constructive and even add substantial value to an organisation. They, and a number
of other Western researchers, have written much about
how to eectively confront and resolve the various
types of organisational, task-related or personal conicts (e.g.1, 38).
Hong Kong was ranked as the world's third most
competitive economy in the Institute for Management
Development's
1996
World
Competitiveness
Yearbook.9 It is located at the major conuence of
eastwest commercial, nancial, industrial and cultural
activities. From our extensive literature search on conict management and its related issues in Hong Kong
industries, to our surprise, we have found little being
written about this subject locally in the last few dec-
Methodology
The ndings presented in this paper are based on the
analysis of 63 conict case incidents written and submitted by part-time students of the MSc in
Engineering Management (MScEM) programme at the
City University of Hong Kong over the last 3 years.
This MScEM is a post-experience engineering management development programme conducted in the evenings. These students (i.e. the original case authors)
come from a diversied industrial background including government agencies, public utilities, large corporations and small enterprises. They are professional
engineers, technical personnel or engineering managers
from dierent Hong Kong industrial sectors and have
an average of 7 years' working experience. The piechart in Figure 1 shows the distribution of the
MScEM students across industries involving public utilities (electricity, gas, telecommunications, transportation), manufacturing (electronics, electrical products,
computers and peripherals), government agencies
(highway department, electrical and mechanical services department), and engineering services (construction, electrical and mechanical engineering services,
and installation and maintenance). Although there
were occasionally a few non-Chinese students in the
MScEM classes during the past few years, all of the
case authors of these 63 case incidents were local
Chinese. As a part of the programme requirements,
the students were required to submit a written assignment selecting from a set of questions. One of the
questions asked them ``to describe a good and/or bad
experience of conict and conict resolution'' in their
respective organisations with consideration of the following suggested areas:
.
.
.
.
.
.
Conict sources
Thamhain and Wilemon15, 16 have categorised causes of
conict over the life cycle of a project into 7 major
sources, namely, project priorities, administrative procedures, technical opinions and performance trade-os,
manpower resources, cost, schedules and personality.
Recently, Kezsbom1 presented a more comprehensive
list of 13 major conict sources. She included in this
expanded list, 6 other sources like, communication,
reward structure/performance appraisal, politics, leadership, ambiguous roles/structure, and unresolved
prior conicts. Brief descriptions of these 13 conict
sources are given below:
1. Schedulingdisagreements that develop around
the timing, sequencing, duration of projects and
feasibility of schedule for project-related tasks or
activities.
2. Managerial and administrative proceduresdisagreements that develop over how the project will
be managed; the denition of reporting relationships and responsibilities, interface relationships,
project scope, work design, plans of execution,
negotiated work agreements with other groups,
and procedures for administrative support.
3. Communicationdisagreements resulting in poor
information ow among sta or between senior
management and technical sta including, such
topics as misunderstanding of project-related goals
and the strategic mission of the organisation and
the ow of communication from technical sta to
senior management.
4. Goal or priority denitiondisagreements arising
from lack of goals or poorly dened project goals,
including disagreements regarding the project mission and related tasks, diering views of project
participants over the importance of activities and
tasks, or the shifting of priorities by superiors/customers.
5. Resource allocationdisagreements resulting from
the competition for resources (for example, personnel, materials, facilities and equipment) among
projects members or across teams, or from lack of
resources of downsizing of organisations.
6. Reward structure/performance appraisal or measurementdisagreements that originate from dierences in reward structure and from the insucient
match between the project team approach and the
performance appraisal system.
7. Personality and interpersonal relationsdisagreements that focus on interpersonal dierences
rather than on `technical' issues; includes conicts
that are ego-centred, personality dierences or
caused by prejudice or stereotyping.
8. Costsdisagreements that arise from the lack of
cost control authority within either the project
management or functional group, or from the allocation of funds.
9. Technical opiniondisagreements that arise, particularly in technology-oriented projects, over technical issues, performance specications, technical
trade-os, and the means to achieve performance.
10. Politicsdisagreements that centre on issues of
territorial power, personal inuences or hidden
agendas.
11. Leadership: poor input or directiondisagreements
that arise from a need for clarication from upper
management on project-related goals and strategic
mission of the organisation, or from a perception
by specialists of a lack of decision-making regarding project goals.
12. Ambiguous
roles/structuredisagreements,
especially in matrix structures where two or more individuals or sections have related or overlapping
assignments or roles.
13. Unresolved prior conictdisagreements stemming
from prior unresolved conicts.
There is also a number of other authors who have
classied conicts sources or causes dierently in
dierent working environments (see e.g.2427). We are
of the opinion that Kezsbom's list is more comprehensive in today's dynamic project environment. As mentioned in the previous section, it is used by the
MScEM students as a reference checklist in their
evaluation and write-up of their chosen case incidents.
Withdrawal
Conict resolutions
Forcing
(4)
(2)
(21)
(2)
8 (0)
1 (0)
2 (0)
3 (0)
7 (0)
2 (0)
1 (1)
3 (0)
1 (1)
30 (29)
13 (0)
10 (0)
5 (2)
Confrontation
4
2
22
2
Smoothing
Compromising
Total
1 (0)
14
3
36
8
2
63
2 (1)
2 (0)
5 (1)
Note: each bracketed gure shows the number of cases which are said to have been resolved with positive eects or consequences.
Conict categories
Scheduling
Managerial and administration procedures
Communication
Goal/priority denition
Resource allocation
Reward structure /performance appraisal
Personality and interpersonal relations
Costs
Technical opinion
Politics
Leadership: poor input or direction
Ambiguous roles/structure
Unresolved prior conict
Conict resolutions
Confrontation Withdrawal
Forcing
(intergroup
(interpersonal
(intergroup
conict)
conict)
conict)
Smoothing
3
7
6
1
6
(3)
(3)
(5)
(1)
(6)
3
1 (1)
1 (1)
1 (1)
1 (1)
3
1 (1)
1
5 (5)
2 (1)
1 (1)
1
2 (1)
1 (1)
3 (3)
1 (1)
1 (1)
Compromising
Sub Total
5
14
7
4
10
0
10
2
6
0
1
2
2
Note: each bracketed gure shows the number of cases where the dispute or disagreement was classied as intergroup or interpersonal conict.
397
was often used to handle intergroup conicts concerning `managerial and administration procedures',
`resource allocation' and `communication'. We suggest
that this may be directly linked to the increasingly
popular use of matrix organisation structures, as noted
in a recent study of Chuah et al.12 The matrix project
team is a temporary structure. It is often unlikely that
every member of a matrix team is at the same stage of
the `learning curve' and there will inevitably be confusion in procedures and communication, or disagreements on individuals' level of responsibility and
authority etc. The project manager or co-ordinator in
such an environment needs to work with other functional members under the inherent project constraints
of time, costs and resources. The level of intergroup
communication increases dramatically in this type of
project organisation structure. The project manager or
co-ordinator must ensure eective cross-functional as
well as intra project team communication. The project's cost and schedule objectives and performance
specications have to be met. Sub-optimal compromises or partial completion are not acceptable. And
the project manager or co-ordinator in a matrix project team does not have the full authority to dictate
terms or to `force' a solution he/she wants.
Confronting the conict issues openly then seems to be
the only acceptable option under such circumstances.
`Withdrawal' ranked the second most favoured conict resolution mode and was used in about 20%, or
13 of the 63 reported cases. In contrast, Thamhain and
Wilemon16 found that `withdrawal' was the least
favoured conict resolution mode and more than 40%
of the project managers in their sample rejected this
mode of conict resolution. It is interesting to note
that the `withdrawal' approach is popularly used to
handle conict over personality clashes and interpersonal relations in 8 out of 13, in other words, more of
the 60% of the `withdrawal' cases. We believe that this
phenomenon is related to the inherent inuence of
Chinese culture and traditional values,10 especially in
these types of conict. The Chinese engineers or managers tend to prefer to avoid interpersonal conict in
the belief that maintaining the personal `guan-xi' or relationship and `being a friend rather than an opponent'
are necessary for sustaining goodwill and ensuring
future co-operation or collaboration. However, the
case data in Table 1 have shown that none of the
reported conict issues including the interpersonal
ones, could be satisfactorily resolved by this approach.
In other words, there was no reported `positive' consequence in all of the 13 cases where the `withdrawal'
approach was adopted!
The third choice was the `forcing' mode. Ten out of
the 63 cases had used it. The data in Table 1 show
that more engineers/managers used this technique to
handle intergroup conict. Table 2 shows that the `forcing' mode was more likely to be used to resolve issues
related to resource allocation and managerial and administration procedures. This perhaps is related to the
unique organisational culture in Hong Kong that there
is still a large proportion of rms being owned and
run by members belonging to the same families or
clans.23 In such organisations, autocracy in decision
making and conict resolution is still very much the
norm. However, as in the cases which used the `withdrawal' approach, none of the 10 cases where the `for398
Conclusions
This study has found some empirical evidence from
collected case incidents that the inuence of Chinese
culture and traditional values on Hong Kong engineers/managers' perception of conict, and their choice
of resolution methods is diminishing. The information
extracted from the 63 case incidents signies a trend
References
1. Kezsbom, D. S., Re-opening Pandora's box: sources of project
conict in the `90s. Industrial Engineering (USA), 1992, May,
5459.
2. Ranney, J. and Deck, M., Making teams work: lessons from
the leaders in new product development. Planning Review, 1995,
23(4), 612.
3. Tjosvold, D., The Conict Positive Organization: Stimulate
Diversity and Create Unity. Addison Wesley, 1991.
4. Deutsch, M., Constructive conict resolution: principles, training and research. Journal of Social Issues, 1994, 50(1), 1332.
5. Thamhain, H. J. and Wilemon, D. L., The eective management of conict in projectoriented work environments.
Defence Management Journal, 1975, 11(3), 2940.
6. Rahim, M. A., Managing Conict in Organizations. Praeger
Publishers, New York, 1986.
7. Gupta, A. K. and Wilemon, D., The Credibilityco-operation
connection at the R&Dmarketing interface. Journal of Product
Innovation Management, 1988, 5, 2031.
8. Amason, A. C., Distinguishing the eects of functional and
dysfunctional conict on strategic decision making: resolving a
paradox for top management teams. The Academy of
Management Journal, 1996, 39(1), 123148.
9. The World Competitiveness Yearbook 1996. Institute for
Management Development, (1996).
10. Tang, S. F. Y. and Kirkbride, P. S., The Development of
Conict Handling Skills in Hong Kong: some cross-cultural
issues. Working Paper No. 7, City Polytechnic of Hong Kong,
Hong Kong, 1986.
11. Tsang, C. H. Y., An Exploratory Research on Conict
Management Styles of Chinese and Western Managers in Hong
Kong. Undergraduate Final-year Project Report, City
Polytechnic of Hong Kong, Hong Kong, 1993.
12. Chuah, K. B., Tummala, V. M. R. and Nkasu, M. M., Project
management structures in Hong Kong industries. International
Journal of Project Management, 1995, 13(4), 253257.
13. Blake, R. R. and Mouton, J. S., The Managerial Grid. Gulf
Publishing, Houston, Texas, 1964.
14. Burke, R. J., Methods of resolving interpersonal conict.
Personnel Administration, 1969, JulyAugust, 4855.
15. Thamhain, H. J. and Wilemon, D. L., Diagnosing conict
determinants in project management. Transactions on
Engineering Management, 1975, EM-22(1), 3544.
16. Thamhain, H. J. and Wilemon, D. L., Conict management in
project life-cycle. Sloan Management Review, 1975, 16(3), 31
49.
399