Managing New Product Development Teams in a Globally Dispersed NPD Program

Globalization is a major market trend today, one characterized by both increased international competition as well as extensive opportunities for firms to expand their operations beyond current boundaries. Effectively dealing with this important change, however, makes the management of global new product development (NPD) a major concern. To ensure success in this complex and competitive endeavor, companies must rely on global NPD teams that make use of the talents and knowledge available in different parts of the global organization. Thus, cohesive and well‐functioning global NPD teams become a critical capability by which firms can effectively leverage this much more diverse set of perspectives, experiences, and cultural sensitivities for the global NPD effort. The present research addresses the global NPD team and its impact on performance from both an antecedent and a contingency perspective. Using the resource‐based view (RBV) as a theoretical framework, the study clarifies how the internal, or behavioral, environment of the firm—specifically, resource commitment and senior management involvement—and the global NPD team are interrelated and contribute to global NPD program performance. In addition, the proposed performance relationships are viewed as being contingent on certain explicit, or strategic, factors. In particular, the degree of global dispersion of the firm's NPD effort is seen as influencing the management approach and thus altering the relationships among company background resources, team, and performance. For the empirical analysis, data are collected through a survey of 467 corporate global new product programs (North America and Europe, business‐to‐business). A structural model testing for the hypothesized effects was substantially supported. The results show that creating and effectively managing global NPD teams offers opportunities for leveraging a diverse but unique combination of talents and knowledge‐based resources, thereby enhancing the firm's ability to achieve a sustained competitive advantage in international markets. To function effectively, the global NPD team must be nested in a corporate environment in which there is a commitment of sufficient resources and where senior management plays an active role in leading, championing, and coordinating the global NPD effort. This need for commitment and global team integration becomes even more important for success as the NPD effort becomes more globally dispersed.     

Managing the Sources of Uncertainty: Matching Process and Context in Software Development

There is increasing interest in the literature about the notion of a contingent approach to product development process design. This interest stems from the realization that different types of projects carried out in different environments are likely to require quite different development processes if they are to be successful. Stated more formally, a contingent view implies that the performance impact of different development practices is likely to be mediated by the context in which those practices operate. This article provides evidence to support such a view. Our work examines whether projects in which the development process matches the context achieve superior performance. We focus on two sources of uncertainty that generate challenges for project teams: platform uncertainty, reflecting the uncertainty generated by the amount of new design work that must be undertaken in a project; and market uncertainty, reflecting the uncertainty faced in determining customer requirements for the product under development. We develop hypotheses for how these sources of uncertainty are likely to influence the relationships between a number of specific development practices and performance. We then test these hypotheses using data from a sample of 29 Internet software development projects. Our results provide evidence to support a contingent view of development process design. We show that in projects facing greater uncertainty, investments in architectural design, early technical feedback, and early market feedback have a stronger association with performance. The latter relationships are influenced by the specific sources from which this uncertainty stems: platform uncertainty mediating the impact of early technical feedback and market uncertainty mediating the impact of early market feedback. Our results also indicate that while greater uncertainty is associated with making later changes to a product's design, this practice is not associated with performance. Our findings suggest that managers carefully must evaluate both the levels and sources of uncertainty facing a project before designing the most appropriate process for its execution. In particular, they should explore the use of specific development practices based upon their usefulness in resolving the specific types of uncertainty faced. Importantly, these decisions must be made at the start of a project, with purposeful investments to create a process that best matches the context. Reacting to uncertainty ex‐post, without such investments in place, is unlikely to prove a successful strategy.     

The Effect of Interactional Fairness on the Performance of Cross‐Functional Product Development Teams: A Multilevel Mediated Model*

Cross‐functional product development teams (CFPDTs) are receiving increasing attention as a fundamental mechanism for achieving greater interfunctional integration in the product development process. However, little is known about how team members' interactional fairness perception—fairness perception based on the quality of interpersonal treatment received from the project manager during the new product development process—affects cross‐functional communication and the performance of CFPDTs. This study examines the effects of interactional fairness on both team members' performance and team performance as a whole. It was predicted that interactional fairness in CFPDTs would significantly affect team members' task performance, both task‐ and person‐focused interpersonal citizenship behaviors, as well as team performance. Additionally, commitment would partially mediate the effects of interactional fairness on these performance outcomes. Analyzing survey responses from two student samples of CFPDTs with hierarchical linear modeling techniques, it was demonstrated that team members' task performance, interpersonal citizenship behavior, and team performance are enhanced when team members are dedicated to both the team and the project, and such dedication is fostered when project managers are fair to team members in an interpersonal way.     

Managing the Unexpected Across Space: Improvisation,Dispersion, and Performance in NPD Teams

Organizations are increasingly moving toward a team‐based structure for managing complex knowledge in new product development (NPD) projects. Such teams operate in an environment characterized by dynamic project requirements and emergent nonroutine issues, which can undermine their ability to achieve project objectives. Team improvisation—a collective, spontaneous, and creative action for identifying novel solutions to emergent problems—has been identified as a key team‐situated response to unexpected challenges to NPD team effectiveness. Geographic dispersion is increasingly becoming a reality for NPD teams that find themselves needing to improvise solutions to emergent challenges while attempting to leverage the knowledge of team members who are physically distributed across various locations. However, very little is known about how teams' improvisational actions affect performance when such actions are executed in increasingly dispersed teams. To address this gap in the literature, this paper draws on the emerging literature on different forms and degrees of team dispersion to understand how team improvisation affects team performance in such teams. In particular this paper takes into account both the structural and psychological facets of dispersion by considering the physical distance between team members, the configuration of the team across different sites, as well as the team members' perception of being distant from their teammates. Responses from 299 team leaders and team members of 71 NPD projects in the software industry were used to analyze the relationship between team improvisation and team performance, as well as the moderating effect of the three different conceptualizations of team dispersion. Results of the study indicate that team improvisation has a positive influence on project team performance by allowing team members to respond to unexpected challenges through creative and timely action. However, increasing degrees of team member dispersion (both structural and psychological) attenuate this relationship by making it difficult to have timely access to other team members' knowledge and by limiting real‐time interactions that may lead to the development of creative solutions. The results of this research offer guidance to managers about when to balance the desire to leverage expertise to cope with unexpected events. Moreover, the present paper provides directions for future research on improvisation and team dispersion. Future research is encouraged to investigate factors that may help highly dispersed teams to overcome the shortcomings of team dispersion in dealing with emergent events.     

Learning in New Technology Development Teams

One factor that may distinguish effective new product development teams from ineffective ones is the ability to learn in purposeful and cumulative ways. History can sometimes teach important lessons, yet history is not always transmitted efficiently within organizations. Patricia Meyers and David Wilemon present a study of new product development teams' learning in technology-based organizations. They note especially the learning modes employed by teams, the conditions blocking team learning which create errors and the learning transfer among teams. Using findings from previous and current research, the authors establish the importance of effective team learning whenever teams are asked to deal with complex new product development challenges. Further, they suggest ways to create a productive learning climate for new product teams and close with a discussion of both managerial implications and suggestions for further research.     

Leadership Differences in New Product Development Teams

Innovativeness is unlikely without skilled leaders to guide the teams which develop new products and technologies. Although the importance of leadership to innovation success is often discussed, the specific practices of effective team leaders are not. In this study, Gloria Barczak and David Wilemon focus on the roles, functions and methods employed by leaders of operating and innovating types of new product development teams. Operating teams are part of the daily activities of the firm, are involved with current markets and develop products similar to current product offerings. Innovating teams do not routinely engage in day-to-day activities. They pursue new markets and develop products quite different from existing ones. The results suggest that successful leaders of both types of teams perform similar roles and functions. However, the methods they use to achieve them vary by the type of new product development team.     

Interdependence and Managing Conflict with Sub-Contractors in the Construction Industry in East Asia

In contrast to traditional assumptions about Asian conflict management, interdependence may induce cooperative approaches to conflict rather than avoidance or competition. Findings from supervisors on 216 subcontractors in Korea, Japan, and Hong Kong support the hypotheses that interdependence leads to cooperative conflict which results in constructive conflict which in turn helps the subcontractor contribute to the main contractor. However, competitive and avoiding conflict were found to be useful in Taiwan. Results were interpreted as suggesting that the theory of cooperation and competition offers the potential for strengthening conflict management in East Asia and that cooperative conflict, rather than avoiding, may reinforce feelings of interdependence in East Asia.     

Procedural Justice Climate in New Product Development Teams: Antecedents and Consequences

With the increasing interest in the concept of justice in the group behavior literature, the procedural justice (PJ) climate attracts many researchers and practitioners from different fields. Nevertheless, the PJ climate is rarely addressed in the new product development (NPD) project team literature. Specifically, the technology and innovation management (TIM) literature provides little about what the PJ climate is, its nature and benefits, and how it works in NPD project teams. Also, few studies investigate the antecedents and consequences of the PJ climate in NPD teams enhancing the understanding of this concept from a practical perspective. This paper discusses the PJ climate theory in a NPD team context and empirically demonstrates how team members' positive collective perceptions of a PJ climate can be developed and how a PJ climate influences a project's performance in NPD teams. In particular, team culture values including employee orientation, customer orientation, systematic management control, innovativeness, and social responsibility were investigated as antecedents, and team learning, speed to market, and market success of new products were studied as outcomes of PJ climate in this paper. By studying 83 NPD project teams it was found on the basis of using partial least squares (PLS) method that (1) the level of employee, customer and innovativeness orientation as well as systematic management control during the project had a positive impact on developing a PJ climate in an NPD team; (2) a PJ climate positively affects team learning and product development time (i.e., speed to market); and (3) team learning and speed to market mediate the relations between the PJ climate and new product success (NPS). Based on the findings, this paper suggests that managers should enhance the PJ climate and team culture in the project team to enhance team learning and to develop products faster. In particular, managers should (1) open a discussion forum among people and create a dialogue for people who disagree with the other project team members rather than dictating or emposing others ideas to them, (2) facilitate information searching and collecting mechanisms to make decisions effectively and to clarify uncertainties, and (3) allow team members to challange project‐related ideas and decisions and modify them with consensus. Also, to enhance the PJ climate during the project, managers should (1) respect and listen to all team members' ideas and try to understand why they are sometimes in opposition, (2) define team members' task boundaries and clarify project norms and project goals, and (3) set knowledge‐questioning values by facilitating team members to try out new ideas and seek out new ways to do things.     

Soaking It Up: Absorptive Capacity in Interorganizational New Product Development Teams

Prior research has acknowledged the importance of an organization's absorptive capacity—the ability to acquire new knowledge and information, assimilate, transform, and exploit it—for innovation purposes. Because innovations are usually developed by project teams, this suggests that absorptive capacity, as a construct, may also be usefully applied at the team level. Consequently, this study developed a measure for team‐level absorptive capacity, investigated the potential influencing factors, and examined its relationship to team effectiveness in terms of product innovativeness in an interorganizational context. Specifically, building on the theory of homophily and information and decision‐making theories, three factors (social‐category similarity, work‐style similarity, and knowledge complementarity between the recipient and the partner organization teams) were identified as likely antecedents of team absorptive capacity. The hypotheses were tested on data from 98 interorganizational new product development teams and included responses from team members, team leaders, and team‐external managers. With regard to the antecedents of team absorptive capacity in interorganizational settings, the results showed a significant positive association with partners' work‐style similarity and an inverted U‐shaped relationship with partners' knowledge complementarity. Social‐category similarity was not significantly associated with team absorptive capacity. We also examined whether team absorptive capacity was related to interorganizational team effectiveness and found a significant positive relationship between team absorptive capacity and product innovativeness. The study demonstrates that absorptive is indeed related to team effectiveness outcomes in an interorganizational context, which underlines the importance of team‐level absorptive capacity for product innovation management and suggests paying more attention to the lower levels of absorptive capacity.     

Crossfunctional Teams in Product Development: Accommodating the Structure to the Process

This article reports the conclusions from a study of crossfunctional product development teams with emphasis on the implications for altering organizational structure to accommodate team process. A comparative study of teams in four U.S.firms, using anthropological and sociolinguistic methods, found that team work is inherently paradoxical. It poses numerous contradictions and paradoxes for individuals, teams, and organizations. At one of the research sites, tacit recognition of this reality and a conviction that teams were critical to product development led to a continuous accommodation of the organization to the requirements of team work and to impressive organizational outcomes. Conceptual and managerial lessons are drawn from this successful case and are offered here to help guide both future research and the actual implementation of team work in firms.     

Managing Supplier Involvement in New Product Development: A Multiple‐Case Study*

Existing studies of supplier involvement in new product development have mainly focused on project‐related short‐term processes and success factors. This study validates and extends an existing exploratory framework, which comprises both long‐term strategic processes and short‐term operational processes that are related to supplier involvement. The empirical validation is based on a multiple‐case study of supplier collaborations at a manufacturer in the copier and printer industry. The analysis of eight cases of supplier involvement reveals that the results of supplier–manufacturer collaborations and the associated issues and problems can best be explained by the patterns in the extent to which the manufacturer manages supplier involvement in the short term and the long term. The results of this study reveal that the initial framework is helpful in understanding why certain collaborations are not effectively managed yet conclude that the existing analytical distinction among four different management areas does not sufficiently reflect empirical reality. This leads to the reconceptualization and further detailing of the framework. Instead of four managerial areas, this study proposes to distinguish between the strategic management arena and the operational management arena. The strategic management arena contains processes that together provide long‐term, strategic direction and operational support for project teams adopting supplier involvement. These processes also contribute to building up a supplier base that can meet current and future technology and capability needs. The operational management arena contains processes that are aimed at planning, managing, and evaluating the actual collaborations in a specific development project. The results of this study suggest that success of involving suppliers in product development is reflected by the firm's ability to capture both short‐ and long‐term benefits. If companies spend most of their time on operational management in development projects, they will fail to use the leverage effect of planning and preparing such involvement through strategic management activities. Also, they will not be sufficiently able to capture possible long‐term technology and learning benefits that may spin off from individual projects. Long‐term collaboration benefits can only be captured if a company can build long‐term relationships with key suppliers, with which it builds learning routines and ensures that the capability sets of both parties are aligned and remain useful for future joint projects.     

Antecedents and Consequences of Unlearning in New Product Development Teams

Unlearning, which first appeared almost 30 years ago as a subprocess of the organizational learning process, has received only limited attention in the literature. Rather than building on empirical research, the existing scholarship is largely anecdotal, aimed at reviewing the literature and generating new insights. Further, unlearning studies tend to analyze the organizational level and neglect smaller units such as work groups and teams. To address this gap in the understanding of unlearning, this article empirically investigates unlearning in work groups in general and new product development (NPD) teams in particular. This study, based on the literature of organizational memory and change, operationalized team unlearning as changes in beliefs and routines during team‐based projects and then discussed the importance of unlearning behavior in NPD teams. Specifically it was argued that unlearning guards beliefs and routines against rigidity to cope with environmental turbulence. This is of particular note when rigid product development procedures and group beliefs inhibit the reception and evaluation of new market and technology information and reduce the value of perceived new information. To test the antecedents and consequences of the team unlearning model, 319 NPD teams were investigated. Using structural equation modeling, it was found that (1) team crisis and anxiety have a direct impact on team unlearning; (2) environmental turbulence also has a direct impact on both team crisis and anxiety and team unlearning; and (3) after team beliefs and project routines have changed, implementing new knowledge or information positively affects new product success. Specifically, the findings revealed that changes in team members' collective beliefs in accordance with environmental changes and the in‐process planning or adjustment of project work activities and procedures as the projects evolve enable teams to develop and launch new products successfully. Also, results indicated that team crisis and anxiety in NPD projects assist team members in revising their previous beliefs and routines when project teams are performing in turbulent environments. This article suggests that managers can enhance team unlearning by (1) creating a sense of urgency by introducing an artificial crisis; and (2) avoiding the groupthink phenomena by bringing in an outsider to challenge existing policies and procedures, and training the team on lateral thinking. In addition, managers can plan project activities in a flexible manner that allows changes as the project evolves to facilitate team unlearning. However, managers should also be cautious when promoting team unlearning. Without careful and considerable evaluation, change in beliefs and routines can cause information/knowledge loss.     

Product Development and Learning in Project Teams: The Challenges Are the Benefits*

The value of teams in new product development (NPD) is undeniable. Both the interdisciplinary nature of the work and industry trends necessitate that professionals from different functions work together on development projects to create the highest‐quality product in the shortest time. Understanding the conditions that facilitate teamwork has been a pursuit of researchers for nearly a half century. The present paper reviews existing literature on teams and team learning in organizational behavior and technology and innovation to offer insights for research on NPD teams. Building on prior work, the organizational benefits of NPD teams are summarized, and five attributes of these teams are identified that hinder attainment of their potential: (1) project complexity; (2) cross‐functionality; (3) temporary membership; (4) fluid team boundaries; and (5) embeddedness in organizational structures. It is argued here that effective management of these five attributes allows not only organization‐level benefits but also team‐level benefits in the form of new capabilities and team member resilience. The critical roles of leadership and of communication and conflict management training are then highlighted as strategies for overcoming the challenges to team effectiveness in NPD as well as for realizing five team benefits: (1) project management skills; (2) broad perspective; (3) teaming skills; (4) expanded social network; and (5) boundary‐spanning skills. The paper concludes with a discussion of the implications of these ideas for conducting future team research.     

《平面杆机构分析》CAI软件的开发

介绍了《平面杆机构分析》ＣＡＩ软件从系统需求分析、教学设计、程序设计到软件调试的过程,以及对复杂参数的计算、动态模拟和动画的处理方法。     

An Exploratory Model of Interpersonal Cohesiveness in New Product Development Teams

There has been a heavy emphasis in new product development (NPD) research on intrateam issues such as communication, trust, and conflict management. Interpersonal cohesiveness, however, has received scant attention. In addition, there are conflicting findings regarding the effects of close‐knit teams, which seem to have a beneficial effect up to a point, after which the tight bond becomes a detriment. This paper addresses these issues by introducing an exploratory model of interpersonal cohesiveness→NPD performance that includes antecedents, consequences, and moderating factors. Antecedents of interpersonal cohesiveness include clan culture, formalization, integration, and political dominance of one department, while consequences are groupthink, superordinate identity, and, ultimately, external/internal new product (NP) performance. The relationships among interpersonal cohesiveness, groupthink, and superordinate identity appear to be influenced by two moderating factors: team norms and goal support. Additionally, product type is identified as a moderator on the effects of both groupthink and superordinate identity on external NP performance. The model is built from two sources: a synthesis of the literature in small group dynamics and NPD, and qualitative research conducted across 12 NPD teams. Individual team leaders were interviewed first, followed by interviews with two additional members on each team, for a total of 36 interviews. In keeping with the goals of qualitative research, the interviews and analysis were used to identify and define aspects of interpersonal cohesiveness rather than to test a preconceived model. Representation of different industries and product types was sought intentionally, and variance in NP innovativeness as well as in NP market success/profitability became key criteria in sample selection. The exploratory model and propositions developed in this study provide a framework for understanding the role of interpersonal cohesiveness in NPD teams and its direct and indirect effects on NP performance. Although a significant amount of research on cohesiveness has been conducted in previous studies of small groups, the narrow laboratory settings of that research have limited the generalizability of the findings. This study therefore serves as a useful starting point for future theory development involving interpersonal cohesiveness in NPD. It also provides a guide for managers in dealing with team cohesiveness.     

Increasing Learning and Time Efficiency in Interorganizational New Product Development Teams*

Despite the growing popularity of new product development across organizational boundaries, the processes, mechanisms, or dynamics that leverage performance in interorganizational (I‐O) product development teams are not well understood. Such teams are staffed with individuals drawn from the partnering firms and are relied on to develop successful new products while at the same time enhancing mutual learning and reducing development time. However, these collaborations can encounter difficulties when partners from different corporate cultures and thought worlds must coordinate and depend on one another and often lead to disappointing performance. To facilitate collaboration, the creation of a safe, supportive, challenging, and engaging environment is particularly important for enabling productive collaborative I‐O teamwork and is essential for learning and time efficient product development. This research develops and tests a model of proposed factors to increase both learning and time efficiency on I‐O new product teams. It is argued that specific behaviors (caring), beliefs (psychological safety), task‐related processes (shared problem solving), and governance mechanisms (clear management direction) create a positive climate that increases learning and time efficiency on I‐O teams. Results of an empirical study of 50 collaborative new product development projects indicate that (1) shared problem solving and caring behavior support both learning and time efficiency on I‐O teams, (2) team psychological safety is positively related to learning, (3) management direction is positively associated with time efficiency, and (4) shared problem solving is more strongly related to both performance dimensions than are the other factors. The factors supporting time efficiency are slightly different from those that foster learning. The relative importance of these factors also differs considerably for both performance aspects. Overall, this study contributes to a better understanding of the factors that facilitate a favorable environment for productive collaboration on I‐O teams, which go beyond contracts or top‐management supervision. Establishing such an environment can help to balance management concerns and promote the success of I‐O teams. The significance of the results is elevated by the fragility of collaborative ventures and their potential for failure, when firms with different organizational cultures, thought worlds, objectives, and intentions increasingly decide to work across organizational boundaries for the development of new products.     

Managing business-to-business open innovation: A project-level approach

Embracing business-to-business open innovation (B2B OI) can enable firms to remain competitive in an increasingly saturated business environment. Whilst B2B OI is generally undertaken to serve the needs of a specific innovation project, previous research has mainly studied it from the firm-level perspective. Accordingly, the number of project-level studies on B2B OI, especially empirical, remains limited, resulting in an incomplete understanding of B2B OI management. In this editorial, we briefly review the B2B OI literature, discuss the importance of studying B2B OI at project level, and describe how each of the six articles included in our special issue contributes to this field. Moreover, we suggest future research opportunities with regard to issues and topics that remain largely under-investigated in project-level B2B OI, but which also open up to a multilevel perspective.     

Knowledge Sharing in Interorganizational Product Development Teams: The Effect of Formal and Informal Socialization Mechanisms*

Working collaboratively with suppliers is increasingly cited as a “best practice” in product development. The importance of sharing knowledge between buyer and supplier in this context has been well recognized, although comparatively little research exists on the interorganizational socialization mechanisms that facilitate it. The present research proposes and tests a theoretical model of the impact of formal and informal socialization mechanisms on the level of knowledge sharing within interorganizational product development projects and the subsequent effect on buyer firm performance. Results from this study of 111 manufacturing organizations in the United Kingdom largely support its hypotheses. It is revealed that informal socialization mechanisms (e.g., communication guidelines, social events) play an important role in facilitating interorganizational knowledge sharing, whereas formal socialization mechanisms (e.g., cross‐functional teams, matrix reporting structures) act indirectly through informal socialization to influence knowledge sharing. The results also show that interorganizational knowledge sharing is positively associated with supplier contribution to development outcomes, which, in turn, improves buyer product development performance and, ultimately, financial performance. Product development managers are encouraged to build social ties between interorganizational development teams to increase the flow of knowledge and to improve both product development outcomes and financial performance.     

Time-Driven Development of Software in Manufactured Goods

Microprocessors are being incorporated into an increasingly wide range of products. However, many of the companies that manufacture such products are not effectively managing software development for these embedded systems. Despite the current focus on concurrent engineering and cross-functional teams, software engineering is often poorly integrated with the rest of the product development effort. The result is usually a costly delay in the product's introduction to the market. Tomlinson G. Rauscher and Preston G. Smith describe several practices that have proved helpful for accelerating the development of products that incorporate embedded software. Managerial and economic opportunities for accelerating development of hardware-software systems involve planning for dramatic growth in products that include embedded software, cultivating in-house software knowledge, recognizing the financial effects of project decisions, and measuring project progress. Improving time to market requires hiring and developing software engineering staff and managers with the requisite knowledge of the application, ensuring that they understand the techniques for specifying requirements and design, and providing them with clear guidelines for evaluating the trade-offs between project duration, project cost, and product performance. Progress should be measured in terms of the number of components completed, rather than the number of lines of code that are written. During the development process, emphasis should be placed on managing the scheduling links between hardware and software development, obtaining user feedback about the system as early as possible, and using a flexible, ongoing review process. Development groups should establish software requirements and design parameters before they start coding, and testing should commence early in the system design process. By creating a working prototype of the user interface, developers can obtain user feedback and thereby sharpen the design specification. Effective, timely software development requires focusing greater energy and resources on development of the requirements specification. By expending this effort in the first phase of a project, the development team can minimize its use of the time-consuming code-and-debug approach to software development. In addition to breaking down a complex system into understandable pieces, a modular design supports efforts to accelerate product development. With a modular design, work on various modules can be assigned concurrently to relatively independent teams. A modular design facilitates testing of the product as well as reuse of software that was developed and deployed in previous projects.