Practice‐oriented toolkits for virtual communities of practice

Purpose – The purpose of this paper is to discuss the collaborative practices of virtual teams carrying out knowledge‐based work and the tools required/used to assemble “collective” artefacts. Design/methodology/approach – The vast majority of recent work on communities of practice is devoted to community management (i.e. discovering, building, and maintaining communities), dismissing or undermining community practices and how they are technologically mediated (i.e. the practice‐specific tools and artefacts involved). This paper investigates existing practices and makes use of scenarios to envision new distributed collective practices in a designated application domain. The instruments used include both empirical tools (i.e. survey of current practice and expert interviews) and analytical tools (i.e. scenarios of use, walkthroughs, and virtual prototyping) to provide insight towards the design of practice‐oriented toolkits. Findings – The proposed approach is validated in the context of an electronic village of local interest with a thematic focus on regional tourism, highlighting the key role of “collective” knowledge management in information‐based industries whose products are non‐material (intangible) and knowledge is central to gaining competitive advantage. The results include a general model for practice‐oriented toolkits conceived of as separate software components from (but interoperable to) the community support system and devised to establish a place for engaging in the practice the community is about. This model is then used to build an operational toolkit for assembling vacation packages by cross‐organization virtual communities of practice. Practical implications – Virtual communities of practice (or partnerships) necessitate smooth integration of community management and practice‐specific tasks and tools. Community management tasks can be supported by augmenting capabilities of existing community portals to allow for community registration, role undertaking, declaration of virtual assets, etc. Practice‐oriented tasks should be designed in such a way so as to capture and accommodate domain‐specific vocabulary. Originality/value – Model‐based techniques and domain‐specific design languages are used as the unifying mechanism (i.e. software factory) for integrating community management and practice‐oriented artefacts. These techniques are designed and implemented into a software platform so as to facilitate the systematic accumulation and reuse of knowledge towards the construction of collective artefacts.