How Formal Control Influences Decision‐Making Clarity and Innovation Performance

Implementing formal planning instruments such as the stage‐and‐gate‐type system (SGS) and project management (PM) have long been seen as the key to new product development (NPD) success. They create the structure needed for managing NPD activities, supporting coordination among functional groups, reducing uncertainty and error, and assuring time and cost efficiency. But recent research presents ambiguous results, suggesting that SGS and PM as formal controls can also have a negative effect. Integrating ideas from three literatures—i.e., NPD management, organization control theory, and technical control theory—the present study assesses NPD programs in terms of three perspectives: (1) the formal control mechanisms used for managing NPD programs—specifically SGS, which is mainly seen as a higher organizational level approach used for guiding and implementing a portfolio of NPD projects, and PM, which is a precise formal control mechanism relevant for managing specific problems at a single project level; (2) the immediate outcome of the application of formal controls, i.e. decision‐making clarity (DMC); and (3) degree of NPD innovativeness, a key contingency hypothesized to impact the efficacy of formal controls. For the empirical analysis, data are collected through a survey of 162 corporate NPD programs (Austria and Denmark, manufactured goods and services) where a total of 1274 respondents provide information relevant to their position. Hierarchical regression analysis is used to test the relationships. Results indicate that the performance effect of NPD formal control is fully mediated by DMC. Further, of the six hypothesized outcome relationships, four are fully supported. Both SGS and PM are effective systems for managing NPD when degree of innovativeness is not taken into account. PM, however, loses its efficacy at higher degrees of NPD program innovativeness while SGS continues to work at achieving positive DMC at the radical end of the innovativeness spectrum. Analysis of interaction effects indicates that for more innovative NPD programs, best results are achieved when companies implement an interactive system of both SGS and PM, where the two systems complement each other.     

Team member experiences in new product development: views from the trenches

Although cross-functional teams are often used for new product development (NPD), many companies struggle to implement them successfully. Through in-depth interviews with 71 team members from 18 companies in a variety of technology-based industries, this study focuses on the experiences of the people who actually do much of the work of NPD (team members) and explores their perceptions and attitudes about cross-functional team assignments. The purpose of our study is to identify the factors that influence and shape NPD team member experiences. Our results suggest that although NPD work can be rewarding and productive, NPD team members are often neglected by other team members, project leaders, and senior management. This sense of neglect has important implications for all of these constituencies, but particularly for senior management.     

Planning and uncertainty in new product development

The domain of New Product Development (NPD) is subject to considerable uncertainties. Aside from market‐related sources of uncertainty, the degree of innovativeness of the underlying product concept is a significant source of uncertainty, as unclear goals and specifications like, e.g. product specifications may lead to substantial delays in the project. However, companies are required to manage the innovation process as efficiently as possible. The resulting conflicting demands often leave companies struggling to achieve both efficiency as well as flexibility due to their often opposing implications for organizing and managing NPD projects. In this context, planning plays a central role; however, its usefulness for NPD project success is perceived quite differently. While there are reports about a positive influence of initial planning on various success measures, others have questioned the effectiveness of elaborated initial planning and contend that the ability to rapidly react to changes later in the process and to improvise may lead to success in NPD. This study aims at achieving a better understanding of planning in NPD by investigating a sample of 475 Research & Development projects in Japanese electrical and mechanical engineering companies. Regression analysis is used to shed more light on the interplay of planning intensity, changes, and the degree of technological newness of the NPD project and their influence on project success. Our results indicate planning to be of value for different types of innovation projects. Furthermore, the influences of the variables in question vary with the success measures that are taken into account, indicating that a more detailed and contingent understanding of planning in NPD needs to be developed.     

Exploring New Product Development Project Review Practices*

Most organizations use new product development (NPD) processes that consist of activities and review points. Activities basically solve problems and gather and produce information about the viability of successfully completing the project. Interspersed between the development activities are review points where project information is reviewed and a decision is made to either go on to the next stage of the process, stop it prior to completion, or hold it until more information is gathered and a better decision can be made. The review points are for controlling risk, prioritizing projects, and allocating resources, and the review team typically is cross‐disciplinary, comprising senior managers from marketing, finance, research and development (R&D), or manufacturing. Over the past four decades, research has greatly advanced knowledge with respect to NPD activities; however, much less is known about review practices. For this reason, the present paper reports findings of a study on NPD project review practices from 425 Product Development & Management Association (PDMA) members. The focus is on three decision points in the NPD process common across organizations (i.e., initial screen, prior to development and testing, and prior to commercialization). In this paper, the number of (1) review points used, (2) review criteria, (3) decision makers on review committees and the proficiency with which various evaluation criteria are used are compared across incremental and radical projects and across functional areas (i.e., marketing, technical, financial). Furthermore, the associations between these NPD review practices and new product performance are examined. Selected results show that more review points are used for radical NPD projects than incremental ones, and this is related to a relatively lower rate of survival for radical projects. The findings also show that the number of criteria used to evaluate NPD projects increases as NPD projects progress and that the number of review team members grows over the stages, too. Surprisingly, the results reveal that more criteria are used to evaluate incremental NPD projects than radical ones. As expected, managers appear to more proficiently use evaluation criteria when making project continuation/termination decisions for incremental projects; they use these criteria less proficiently during the development of radical projects, precisely when proficiency is most critical. At each review point, technical criteria were found to be the most frequently used type for incremental projects, and financial criteria were the most commonly used type for radical ones. Importantly, only review proficiency is significantly associated with performance; the number of review points, review team size, and number of review criteria are not associated with new product performance. Furthermore, only the coefficient for proficiently using marketing criteria was significantly related to new product program performance; the proficiency of using financial and technical information has no association with performance. Finally, across the three focal review points of the NPD process in this study, only the coefficient for proficiency at the first review point, (i.e., the initial screen) is significantly greater than zero. The results are discussed with respect to research and managerial practice, and future research directions are offered.     

Improving Supplier New Product Development Performance: The Role of Supplier Development

Suppliers play an increasingly central role in helping firms achieve their new product development (NPD) goals. The literature implicitly assumes that suppliers are able to meet or exceed the quality standards and technological expectations of the firm, and yet, in practice, suppliers often lack the technological capabilities needed to undertake collaborative NPD. In such situations, a firm may choose to intervene and actively develop the supplier's technological and product development capabilities. We develop a theoretical framework that conceptualizes supplier development activities within interorganizational NPD projects as part of a bilateral knowledge‐sharing process: design recommendations, technical specifications, and new technology flow from supplier to the firm, and in turn, the firm can implement supplier development activities to upgrade the supplier's technological capabilities. Antecedents (supplier responsibility, skills similarity, single sourcing strategy) and consequences of supplier development activities (on supplier, product, and project performance) are examined using a sample of 153 interorganizational NPD projects within UK manufacturers. We find broad support for our hypotheses. In particular, we show that the relational rents (in the form of improved product and project performance) attained from supplier development activities in new product development are not achieved directly, but rather indirectly, via improvements in the supplier's creative and technological capabilities. Our results emphasize the importance of adopting a strategic view of the potential returns available from investing in the NPD capabilities of key suppliers, and provide clues about underlying reasons for the suboptimal experiences of many companies' collaborative NPD projects.     

The fuzzy front end of Japanese new product development projects: impact on success and differences between incremental and radical projects

This study of Japanese New Product Development (NPD) projects explores the fuzzy front end of innovation. The goal of the paper is twofold: First, we analyse the impact of the fuzzy front end on the success of all the NPD projects. We develop a conceptual model based on the information-processing approach. A structural equation model was fitted to data from 497 NPD projects in Japanese manufacturing firms to test the proposed model. The empirical analysis suggests that an early reduction of market and technical uncertainty as well as an initial planning before development have a positive impact on NPD project success. The model accounts for 17% of the variance of the efficiency and 24% of the variance of the effectiveness-dependent variable. Thus, the front end phase is an important driver of NPD project success. Second, we compare the fuzzy front end of incremental to radical NPD projects. Although these projects differ in many aspects of newness, we found only a few differences with regard to the fuzzy front end. For instance, it was more difficult to estimate the market size and price sensitivity of the customers during the fuzzy front end of the radical NPD projects compared with the incremental projects. Implications of the empirical results and limitations of the study are discussed.     

Impact of new product development (NPD) proficiency and NPD entry strategies on product quality and risk

This research explores the variation of new product quality and risk associated with New Product Development (NPD) entry strategies (e.g. in‐house developments and joint ventures). Our first two research questions examine the quality of new products and the variation of risk across five NPD entry strategies. Our third and fourth research questions investigate the association of the proficiency with which NPD technical activities are performed with new product quality and the risk involved in developing new products. Our final two research questions explore whether the type of NPD entry strategy mediates the association between the proficiency with which NPD technical activities are performed and the quality and risk associated with the development of new products. Our study focuses on new products developed by three major industries, namely medical devices, electrical equipment, and heavy construction equipment. Our research suggests that there is no difference in the quality or the risk associated with the development of new products across NPD entry strategies. We also found that new product quality was associated with the proficient performance of many NPD technical activities whereas risk was associated with the proficient performance of fewer NPD technical activities. We found that choice of NPD entry strategy mediates the relationship between new product quality and NPD technical activity proficiency. Unlike product quality, NPD entry strategy selection appears to mediate NPD risk minimally. Our study contributes to NPD knowledge and managerial decision making by pointing out that the technical activities performed during the early stages of the NPD process are important to the attainment of a quality product and positively, not negatively, associated with perceived NPD risk. Additionally, our study extends knowledge of the association between proficiently performed NPD technical activities and the resultant product quality and perceived risk felt when individual NPD entry strategies are implemented.     

Towards Holistic "Front Ends" In New Product Development

Any firm that hopes to compete on the basis of innovation clearly must be proficient in all phases of the new-product development (NPD) process. However, the real keys to success can be found in the activities that occur before management makes the go/no-go decision for any NPD project. In other words, the most significant benefits can be achieved through improvements in the performance of the front-end activities—product strategy formulation and communication, opportunity identification and assessment, idea generation, product definition, project planning, and executive reviews. Noting the inherent difficulty of managing the front end, Anil Khurana and Stephen R. Rosenthal discuss findings from in-depth case studies of the front-end practices in 18 business units from 12 U.S. and Japanese companies. They offer a process view of the activities that the front end comprises, and they discuss the insights that their case studies provide regarding key success factors for managing the front-end activities. The case studies involved companies in industries ranging from consumer packaged goods to electronics and industrial products. Foremost among the insights provided by the case studies is the notion that the greatest success comes to organizations that take a holistic approach to the front end. A successful approach to the front end effectively links business strategy, product strategy, and product-specific decisions. Forging these links requires a process that integrates such elements as product strategy, development portfolio, concept development, overall business justification, resource planning, core team roles, executive reviews, and decision mechanisms. The case studies suggest that firms employ two general approaches for achieving these links. Some companies rely on a formal process to lend some order and predictability to the front end. Other companies strive to foster a company-wide culture in which the key participants in front-end activities always remain focused on the following considerations: business vision, technical feasibility, customer focus, schedule, resources, and coordination. This cultural approach is more prevalent among the Japanese firms in the study; the U.S. firms tend to rely on formality of the front-end process. The case studies also suggest that the front-end approach must be compatible with the firm's product, market, and organizational contexts. For example, standardized approaches seem to work best for incremental innovations.     

The Role of Market and Technical Information Generation in New Product Development

Firms are investing an increasing amount of time and resources to gather information about market and technology in new product development (NPD). Yet there is a lack of consistent understanding of whether such costly information generation activities can improve product outcomes. More importantly, it is unclear how the benefit of market information and technical information generation may differ and how they may jointly impact new product performance. This study examines the role of market and technical information generation in NPD in three ways: (1) It contrasts the effects of market and technical information generation on product outcomes; (2) it identifies conditions that moderate the effects of market and technical information generation and further investigates how the moderating effects differ for these two types of activities; and (3) it examines the joint effect of market and technical information generation to understand potential synergies between them. Using survey data at the NPD project level, we find that market information generation has an inverted U‐shaped effect on new product advantage, whereas the effect of technical information generation follows a U‐shape. Furthermore, these effects are moderated differently by two conditions: a firm’s R&D intensity that influences NPD projects’ need for different types of information, and the use of multidisciplinary teams that affects the degree to which information can be shared and utilized to improve product design. The findings provide important implications for organizational learning and shed light on how to manage information generation activities to achieve NPD success.     

Systematic Design Methods and the Creative Performance of New Product Teams: Do They Contradict or Complement Each Other?

Can organizations exert control and provide structure for NPD activities while at the same time encouraging and managing creative performance? Any new product development (NPD) project requires some level of creative effort. In new product development, creative performance is of preeminent importance. Most NPD projects are executed with the NPD team as the organizational nucleus. As a result, managing creativity in NPD thus implies managing the creativity of NPD teams. Besides having to manage creative performance, companies are generally also concerned with improving the efficiency and effectiveness of the NPD process. Modern NPD projects therefore have the need for an approach that can be planned, optimized, and verified. As a consequence, systematic design methods have become widely used in NPD. In this article conceptual model is developed of the effect of modern design methodology on the creative performance of NPD teams. First, it is argued that the effect of systematic design methodology on NPD team creativity is mediated by the communication patterns of the NPD team. It is then proposed that four principles underlie modern design methodology: hierarchical decomposition, systematic variation, satisficing, and discursiveness. These principles affect NPD communication by, respectively, influencing the establishment of subgroups, the frequency of communication, the level of agreement or disagreement in the team, and the level of centralization of communication. Next, arguments are presented of how each of these four communicational characteristics shapes the creative performance of NPD teams. This second part of the conceptual model is tested empirically. This is done by studying the communication patterns in 44 NPD teams, employing social network analysis tools. These patterns of communication are then related to team‐level creative performance through a set of regression analyses. The main conclusion of the article is that the design principles work together and need to be considered as an integrated whole: the creative performance of NPD teams can only effectively be managed by using and aligning all four of them.     

New Product Development: Impact of Project Characteristics and Development Practices on Performance

Concurrent product development process and integrated product development teams have emerged as the two dominant new product development (NPD) “best practices” in the literature. Yet empirical evidence of their impact on product development success remains inconclusive. This paper draws upon organizational information processing theory (OIPT) to explore how these two dominant NPD best practices and two key aspects of NPD project characteristics (i.e., project uncertainty and project complexity) directly and jointly affect the NPD performance. Contrary to the “best practice” literature, the analysis, based on 266 NPD projects from three industries (i.e., automotive, electronics, and machinery) across nine countries (i.e., Austria, Finland, Germany, Italy, Japan, Korea, Spain, Sweden, and the United States), found no evidence of any direct impact of process concurrency or team integration on overall NPD performance. Instead, there is evidence of negative impact of the interaction between project uncertainty and concurrent NPD process and positive impact of the interaction between project complexity and team integration on overall NPD performance. Moreover, the study found no evidence of any direct negative impact of project uncertainty or complexity on overall NPD performance as suggested in the literature, but found evidence of a direct positive relationship between project complexity and overall NPD performance. The practical implications of these results are significant. First, neither process concurrency nor team integration should be embraced universally as best practice. Second, process concurrency should be avoided in projects with high uncertainty (i.e., when working with unfamiliar product, market, or technology). Finally, team integration should be encouraged for complex product development projects. For a simple product a loosely integrated team or a more centralized decision process may work well. However, as project complexity increases, team integration becomes essential for improved product development. There is no one‐size‐fits‐all solution for managing NPD projects. The choice of a product development practice should be determined by the project characteristics.     

Does Strategic Planning Enhance or Impede Innovation and Firm Performance?*

Does strategic planning enhance or impede innovation and firm performance? The current literature provides contradictory views. This study extends the resource‐advantage theory to examine the conditions in which strategic planning increases or decreases the number of new product development projects and firm performance. The authors test the theoretical model by collecting data from 227 firms. The empirical evidence suggests that more strategic planning and more new product development (NPD) projects lead to better firm performance. Firms with organizational redundancy benefit more from strategic planning than firms with less organizational redundancy. Increasing R&D intensity boosts both the number of NPD projects and firm performance. Strategic planning is more effective in larger firms with higher R&D intensity for increasing the number of NPD projects. The results reported in this study also consist of several findings that challenge the traditional views of strategic planning. The evidence suggests that strategic planning impedes, not enhances, the number of NPD projects. Larger firms benefit less, not more, from strategic planning for improving firm performance. Larger firms do not necessarily create more NPD projects. Increasing organizational redundancy has no effect on the number of NPD projects. These empirical results provide important strategic implications. First, managers should be aware that, in general, formal strategic planning decreases the number of NPD projects for innovation management. Improvised rather than planned activities are more conducive to creating NPD project ideas. Moreover, innovations tend to emerge from improvisational processes, during which the impromptu execution of NPD activities without planning spurs “thinking outside the box,” which enhances the process of creating NPD project ideas. Therefore, more flexible strategic plans that accommodate potential improvisation may be needed in NPD management since innovation‐related activities cannot be planned precisely due to the unexpected jolts and contingencies of the NPD process. Second, large firms with high levels of R&D intensity can overcome the negative effect of strategic planning on the number of NPD projects. Specifically, a firm's abundant resources, when allocated and deployed for NPD activities, signal the high priority and importance of the NPD activities and thus motivate employees to acquire, collect, and gather customer and technical knowledge, which leads to creating more NPD projects. Finally, managers must understand that managing strategic planning and generating NPD project ideas are beneficial to the ultimate outcome of firm performance despite the adverse relationship between strategic planning and the number of NPD projects.     

An investigation of the use of global, virtual, and colocated new product development teams

This paper presents the results of an investigation of differences between global, virtual and colocated new product development (NPD) teams. Specifically, we examined whether and how these three types of teams differed in terms of usage, challenges, and performance. A survey of PDMA members was undertaken to collect the data. Out of 103 firms participating in the survey, 54 had used or were using global teams for some of their NPD efforts. Overall, we found that the use of global teams in our respondent firms is rapidly increasing. Our respondents indicated that by the year 2001, approximately one out of every five NPD teams in their companies are likely to be global. However, our respondents also expect that their companies will be using multiple types of teams that is, global, virtual, and colocated, to develop their new products. Our findings also suggest that global teams generally face greater behavioral and project management challenges than either colocated or virtual teams. Global team performance is also lower than the performance of virtual or colocated teams. Are these challenges associated with poorer performance? In examining this question, our results suggest that greater project management challenges are associated with lower performance, for all three types of teams. Surprisingly, behavioral challenges were not associated with performance for any team type. Our results suggest that firms face different problems associated with managing each type of NPD team—global, virtual and colocated. To effectively manage each type of team may, in turn, require that companies and their managers employ different solutions to these different problems. Additionally, companies may find that the preparation they provide to their managers and team members to work in these different team environments may also need to be different. Further research is clearly needed to address these managerial implications.     

Project Suspensions and Failures in New Product Development: Returns for Entrepreneurial Firms in Co‐Development Alliances

Entrepreneurial biotech and large pharmaceutical firms often form alliances to co‐develop new products. Yet, new product development (NPD) is fraught with challenges that often result in project suspensions and failures. Considering this, how can firms increase the chances that their co‐development alliances will create value? To answer this question, the authors build on insights from signaling theory to argue that prior project suspensions provide positive signals leading to an increase in value creation, while project failures have the opposite effect. In addition, drawing on insights from temporal construal theory, this research predicts that the strength of these effects is contingent on the stage along the exploration–exploitation continuum at which the alliance is formed. The authors undertook event study analyses of 248 alliances formed by 104 biotechnology firms from the United States and Europe listed on eight stock exchanges over an 8‐year period between 1996 and 2003. The results confirm that prior NPD project suspensions have a stronger value creation effect (or prior failures have a weaker value destruction effect) in the case of exploration alliances in the upstream of NPD processes than in the case of moderate‐scale exploitation alliances in the downstream of NPD. This study is among the first to examine how both prior NPD project suspensions and failures of firms affect the abnormal returns achieved from co‐development alliances. This research therefore contributes to the innovation literature by honing a better understanding of setbacks and failures in NPD. Moreover, the findings contribute to the literature on strategic alliances by identifying new conditions under which firms can create or preserve value. This research also contributes to signaling theory by providing evidence of the moderation effect caused by the signaling environment. Finally, this study contributes to the entrepreneurial literature on value creation for entrepreneurial firms in alliances following adverse events.     

Evaluating failure in the innovation process: the micropolitics of new product development

For almost 40 years academics from a wide range of disciplinary backgrounds have sought to improve our understanding of the innovation process. In this paper, we examine the contribution made by those such as Kotler who have attempted to describe a rational approach to New Product Development (NPD). We argue that such frameworks offer a view of organisational activity which substantially understates the political activity associated with managing the innovation process. Most of those writing from a marketing perspective acknowledge external political influences such as government policies and the leverage of 'special interest groups'. We focus on the work of Burns and Stalker who clearly recognised the way in which internal political struggles to access resources or to improve career prospects impact on innovation. To analyse the role of micropolitics in the NPD process we describe the case of WEL, a medium-sized manufacturing firm, as managers and engineers attempted to develop an important new product. We conclude that it is essential to incorporate the role of internal politics into any framework which claims to offer a realistic account of NPD.     

New Product Development Practices and Early‐Stage Firms: Two In‐Depth Case Studies

New product development practices (NPD) have been well studied for decades in large, established companies. Implementation of best practices such as predevelopment market planning and cross‐functional teams have been positively correlated with product and project success over a variety of measures. However, for small new ventures, field research into ground‐level adoption of NPD practices is lacking. Because of the risks associated with missteps in new product development and the potential for firm failure, understanding NPD within the new venture context is critical. Through in‐depth case research, this paper investigates two successful physical product‐based early‐stage firms' development processes versus large established firm norms. The research focuses on the start‐up adoption of commonly prescribed management processes to improve NPD, such as cross‐functional teams, use of market planning during innovation development, and the use of structured processes to guide the development team. This research has several theoretical implications. The first finding is that in comparing the innovation processes of these firms to large, established firms, the study found several key differences from the large firm paradigm. These differences in development approach from what is prescribed for large, established firms are driven by necessity from a scarcity of resources. These new firms simply did not have the resources (financial or human) to create multi‐ or cross‐functional teams or organizations in the traditional sense for their first product. Use of virtual resources was pervasive. Founders also played multiple roles concurrently in the organization, as opposed to relying on functional departments so common in large firms. The NPD process used by both firms was informal—much more skeletal than commonly recommended structured processes. The data indicated that these firms put less focus on managing the process and more emphasis on managing their goals (the main driver being getting the first product to market). In addition to little or no written procedures being used, development meetings did not run to specific paper‐based deliverables or defined steps. In terms of market and user insight, these activities were primarily performed inside the core team—using methods that again were distinctive in their approach. What drove a project to completion was relying on team experience or a “learn as you go approach.” Again, the driver for this type of truncated market research approach was a lack of resources and need to increase the project's speed‐to‐market. Both firms in our study were highly successful, from not only an NPD efficiency standpoint but also effectiveness. The second broad finding we draw from this work is that there are lessons to be learned from start‐ups for large, established firms seeking ever‐increasing efficiency. We have found that small empowered teams leading projects substantial in scope can be extremely effective when roles are expanded, decision power is ground‐level, and there is little emphasis on defined processes. This exploratory research highlights the unique aspects of NPD within small early‐stage firms, and highlights areas of further research and management implications for both small new ventures and large established firms seeking to increase NPD efficiency and effectiveness.     

Distributed New Product Development Project Based on Internet and World-Wide Web: A Case Study

The deluge of hype about the wonders of the Internet, Intranets, and the World Wide Web continues unabated. At the same time, we hear numerous tales about endless streams of busy signals, broken connections, and painfully slow response times. Surveying the apparent gap between the promise and the often-painful reality, a skeptical manager might reasonably question whether this technology can satisfy the rigorous demands of business users such as product development project teams. In a case study of a large, geographically distributed product development project, Ari-Pekka Hameri and Jukka Nihtila find that Web-based applications can play an important role in new-product development (NPD) efforts. Particularly when projects involve numerous teams from various locations, such tools can provide effective media for communicating and disseminating information. The case study also suggests that these networked information technology (IT) applications can offer important benefits in terms of project and process management. The project described in this study involves a major NPD collaboration, with several independent subprojects and hundreds of team members from various research institutes and companies. The Internet and the World Wide Web provide the media for managing and disseminating project data. Using hypertext links, the Web-based system gives team members easy access to engineering drawings, 3D models, parameter lists, prototype test results, and other engineering information. The point-and-click interface also allows team members to access information about the project structure and schedules, as well as meeting notes, newsgroups, and electronic bulletin boards. Analysis of the file-transfer activities between the Web server and the project groups highlights several important points regarding networked IT applications, information sharing, and project management. First, the system used in this project serves primarily for disseminating information, rather than for fostering collaboration between different groups. Increased collaboration among networked team members probably requires more sophisticated version- and configuration-management capabilities. Second, file-transfer activities typically come in bursts around project milestones; this highlights the essential role that project milestones play in coordinating the work of distributed team members. The electronic media enhance not only the work leading up to milestones, but also the dissemination of decisions made at each milestone.     

Perspective—Riding the Wind: Managing New Product Development in an Age of Change

New product development (NPD) has never been more challenging or rewarding than it is today. With the dawning of the new millennium, new product developers now find themselves in an “age of change,” the likes of which the world has never known. The rate of change is numbing, if not stupefying for many business people. With the winds of change blowing at near gale force intensity levels, this is clearly a time for NPD professionals to pursue new product and market strategies that are anchored on sound business fundamentals. This article begins with a brief review of the Product Development & Management Association's 1998 International Research Conference held in Atlanta. The theme for the conference was “Achieving Excellence in New Product Development and Management.” The article then offers a reflective look at seven NPD themes that could dominate new millennium business thinking and offer guidance to those seeking new product success. The article's first theme discusses why NPD is increasing in importance. The second theme outlines key NPD building blocks which NPD champions must bolster for new product success. The third theme explores the value in conceptualizing NPD output in items of “turns per decade.” The fourth theme champions the notion that continuous quality improvement is an integral part of NPD's contribution to a firm. The fifth theme explains why product elimination is an essential element in the innovation process. Theme number six reminds readers that fun and optimism are essential and commonly overlooked ingredients for sustaining NPD achievement. The seventh theme states that product development professionals build credibility and successful careers by delivering on promises made. Innovation opportunities embedded within each theme are explored from both firm‐level and individual developer‐level perspectives. In building the case for their themes, the authors initially provide a rationale for NPD's growing stature and importance. Then they suggest NPD strategies that firms can implement with high likelihood of success. The article concludes with suggested actions that individual developers can undertake to bolster their own careers while simultaneously strengthening the NPD profession.     

Early supplier integration: the dual role of purchasing in new product development

Interest in early supplier integration in new product development (NPD) has increased as an open innovation approach has become more common in firms. To support supplier integration, the purchasing function of a firm can assume a new ‘dual’ role: contributing to NPD while also managing overall costs. Previous research has offered few insights into how the purchasing function should best be organised so that it will fulfil this dual role. This paper reports on the results of a consortial benchmarking study in which an industry–academic consortium visited and analysed six best‐practice firms. The findings describe how innovative firms organise their purchasing function, distinguishing between ‘advanced sourcing’ and ‘life‐cycle sourcing’ units. The results include the tools that these firms use, such as regular innovation meetings with suppliers and technology roadmaps linking firm strategy, innovation strategy and sourcing strategies. The paper also recommends that researchers shift from a narrow focus on a single project to a broader consideration of supplier and organisational issues in NPD.     

Do the best new product development practices of US companies matter in Hong Kong?

Past research offers numerous “best practice” studies in New Product Development (NPD). One important characteristic of the earlier “best practice” studies is that they are primarily based on Western samples. Because management practices, cultures, and norms differ around the world it has been argued that the findings of the earlier studies will likely to be less applicable to firms managing NPD outside the West. This study fills this gap by surveying Hong Kong companies and comparing the NPD activities in Hong Kong with those in the US. The results revealed interesting similarities and differences between US and Hong Kong firms with regard to their NPD activities.