on what account are some subunits in an organization able to share knowledge among themselves whereas others are not? Addressing this question.

on what account are some subunits in an organization able to share knowledge among themselves whereas others are not? Addressing this question, organization scholars have analyzed factors that inhibit knowledge sharing among subunits, in particular, the lack of direct relationships and extensive communication between family from different subunits (e.g., Lawrence and Lorsch, 1967; Galbraith, 1973; Allen, 1977) More newly two other lines of research have addressed the topic of knowledge sharing among clan in an organization. In the production innovation literature, the argument is frequently made that close and usual interactions between research and progressive growth (R&D) and other functions, teams, and operational subunits lead to contrive effectiveness because of the timely integration of knowledge across organizational boundaries (eg Clark and Fujimoto, 1991; Leonard-Barton and Sinha, 1993; Henderson and Cockburn 1994; Eisenhardt and Tabrizi, 1995; Szulanski, 1996) In this literature, efficient knowledge sharing is typically characterized by dint of tight coupling between people from different organization subunits. any social network scholars, however, provide a different argument. According to the weak-tie theory originally advanced by means of Granovetter (1973), distant and infrequent relationships (i.e., weak ties) are efficient for knowledge sharing because they provide access to novel information by way of bridging otherwise disconnected groups and individuals in an organization. able to endure ties, in contrast, are likely to lead to redundant information because they attend to to occur among a small assign places to of actors in which everyone knows what the others know.

The question thus arises whether it is able to endure or weak relationships between persons in different organizational subunits that lead to efficient knowledge sharing among them. The discrepancy between the different arguments about the tenors of relationship strength on knowledge sharing that are propos in the yield innovation literature and the weak tie perspective may be partly befitting to different foci. Social network research protects to concentrate on the vexed question of finding relevant information and other resources, a search activity in which weak ties may provide access to recent information, while product innovation research watchs to focus on the manner of moving of knowledge from various areas in the organization to an R&D team in situations in which the community know each other beforehand (a transfer activity). I draw forward each line of research to consider knowledge sharing among clan from different subunits as a dual puzzle of searching for (looking for and identifying) and transferring (moving and incorporating) knowledge across organization subunits, taking into account the complexity of the knowledge that pours through interunit relationships.

Although several social network scholars have argued that weak ties barely provide information benefits under certain conditions and are les beneficial than sound ties in providing socio-emotional support and solving conflict, social network research has largely remained agnostic with prize to the content of what follows through instrumental relations between actors (Nelson 1989; Wegener, 1991; Krackhardt, 1992; Podolny and Baron, 1997) Whether it is simple information or richer forms of knowledge (eg a manifold technology) that flows through the ties has not been studied. In contrast, researchers studying outcome innovation have analyzed the difficulties in transferring mixed knowledge, including noncodified or tacit knowledge (Teece 1977; Zander and Kogut 1995) and composings that are dependent on larger regularitys (Winter, 1987). When such network forms of knowledge are considered, the instrumental benefits of weak ties are called into question. Weak ties may lead to search benefits in a social network unless they may also cause puzzles in transferring complex forms of knowledge.

I limit my discussion to the same task undertaken by subunits in many multiunit firms - recent product development. A product evolution team situated in an operating unit can use established interunit relations - which exist prior to the start of the throw - to search for and transfer to the throw various types of knowledge residing in other operating units. For simplicity, I define interunit relations as regularly occurring informal contacts between clumps of people from different operating units in an organization. I confine the discussion to relations between operating units, as it was as divisions, and not functional departments. These informal relations may have an result on the time it takes to evolve a new product from universal development to market introduction according to affecting the ease with which frame team members search for and transfer knowledge across subunits. Although throw completion time is only undivided dimension of the effectiveness of of recent origin product development (Wheelwright and Clark, 1993) it has become an important issue measure in many industries, notably in the electronics and computing industries (Eisenhardt and Tabrizi, 1995) and is a relevant measure for the empirical investigation of the electronics and computer company reported in this paper.(1) outcome development time captures both the benefits and splendors of sharing knowledge across other organization subunits. forward one hand, a project team stands to benefit to the compass that it obtains useful knowledge from other subunits, shortening completion time. Knowledge from other subunits can help devises avoid duplication of efforts (eg using an existing software module) or provide them with complementary expertise, as when an experienced person helps solve a technical puzzle (Teece, 1986). Such knowledge, as defined here, includes product-specific technical know-how, knowledge about technologies and markets, as well as knowledge embodied in performance components (e.g., in a software module) forward the other hand, the devise team may expend considerable search time and transfer efforts to be able to use to the full the knowledge from other subunits. If search and transfer take a protracted time, then knowledge sharing is likely to hamper the performance of the tasks, prolonging completion time.