Sensemaking, safety, and situated communities in (con)temporary networks

This paper discusses the difficulties involved in managing knowledge-intensive, multinational, multiorganisational, and multifunctional project networks. The study is based on a 2-year quasi-ethnography of one such network engaged in the design and development of a complex new process control system for an existing pharmaceutical plant in Ireland. The case describes how, drawing upon the organisational heritage of the corporations involved and the logic implicit within their global partnership arrangements, the project was initially structured in an aspatial manner that underestimated the complexity of the development process and the social relations required to support it. Following dissatisfaction with initial progress, a number of critical management interventions were made, which appeared to contribute to a recasting of the network ontology that facilitated the cultivation and protection of more appropriate communicative spaces. The case emphasises the need to move away from rationalistic assumptions about communication processes within projects of this nature, towards a richer conceptualisation of such enterprises as involving collective sensemaking activities within and between situated ‘communities’ of actors. Contrary to much contemporary writing, the paper argues that space and location are of crucial importance to our understanding of network forms of organising.

Exploration of the relationship between tacit knowledge and software system test complexity

This research has explored the relationship between system test complexity and tacit knowledge. It is proposed as part of this thesis, that the process of system testing (comprising of test planning, test development, test execution, test fault analysis, test measurement, and case management), is directly affected by both complexity associated with the system under test, and also by other sources of complexity, independent of the system under test, but related to the wider process of system testing. While a certain amount of knowledge related to the system under test is inherent, tacit in nature, and therefore difficult to make explicit, it has been found that a significant amount of knowledge relating to these other sources of complexity, can indeed be made explicit. While the importance of explicit knowledge has been reinforced by this research, there has been a lack of evidence to suggest that the availability of tacit knowledge to a test team is of any less importance to the process of system testing, when operating in a traditional software development environment. The sentiment was commonly expressed by participants, that even though a considerable amount of explicit knowledge relating to the system is freely available, that a good deal of knowledge relating to the system under test, which is demanded for effective system testing, is actually tacit in nature (approximately 60% of participants operating in a traditional development environment, and 60% of participants operating in an agile development environment, expressed similar sentiments). To cater for the availability of tacit knowledge relating to the system under test, and indeed, both explicit and tacit knowledge required by system testing in general, an appropriate knowledge management structure needs to be in place. This would appear to be required, irrespective of the employed development methodology.