Abstract

Despite the vast interest and enthusiasm on the benefits of construction partnering, no apparent trend exists to show that it has become the dominant choice of procurement method across construction industries internationally. Rather, the implementation of construction partnering has been patchy, with varying degrees of success and, in many instances, its adoption is more an exception than the norm. This study argues and sets out to test the proposition that despite the huge advocacy for the use of partnering, its slow uptake and, more importantly, the inconsistent results it yields are due to the lack of systematic investigation into the institutional determinants of partnering. Based on data collected from 526 firms covering various industry disciplines, results show that firms' use of partnering is selective and that this selectiveness is significantly determined by the industry's level of institutional norms and not by the conventional notion that partnering increases a firm's profitability or efficiency. Findings further indicate that firms that perceive there are strong industry norms for partnering are twice as likely to use partnering as firms that do not have such perception. By empirically examining the institutional conditions under which partnering is more likely to occur, this study sheds some light on why the implementation of partnering remains at a conservative rate and suggests avenues for future research.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.