Collapsing New Product Development Times: Six Case Studies

Today's customers are sophisticated. They demand product variety, functionality and performance. To survive in this arena, successful companies in a global economy must rapidly introduce new products (new product lines or improvements to existing lines) by collapsing their product development times. Vincent Mabert, John Muth and Roger Schmenner report results from a comparative case study of six new product introduction projects at six different firms, identifying those elements that are important to product introduction lead time and how they are influenced by customer and organizational and technical factors. They note that the new product innovation process is very complex, sensitive to external forces like customer demands or expectations and to internal issues like how team leadership is defined for the development team. The article describes the participating companies and analyzes the six projects with particular attention to four structural elements: motivation, workings of teams, external vendor's cooperation with the teams and project control. The authors conclude by identifying the top priority factors influencing new product introduction time.     

Influence of task type on the relationship between communication and performance: the case of software development

The relationships between communication patterns and performance of software development projects mostly resemble those of technical services, and not development projects, in hardware R&D. The local focus of software development projects in their information requirements is emphasized by the positive influence only of the informal and mostly internal literature, while external contacts, participation in conferences, and formal and external literature were inconsequential. The implications are two-fold: a) on the conceptual level they suggest that a trade-off between coordination and innovation requirements of the task might be an important determinant of optimal communication patterns; b) on the practical level it suggests that 'software development' consists of 'software engineering' and 'software production'. Consequently, it should be recognized that as such, these activities should be managed differently—the former as R&D, the latter as manufacturing.     

When Research Meets Development: Antecedents and Implications of Transfer Speed

This paper focuses on the organization of new product development in large, R&D‐intensive firms. In these firms, research and development activities are often separated. Research is conducted in dedicated research projects at specialized research labs. Once research results are achieved by research projects, they are transferred to business units for further development and commercialization. We investigate the speed whereby research projects transfer their first research results to business units (hereafter: transfer speed). In particular, we analyze the antecedents and performance implications of transfer speed. Based on data of 503 research projects from a European R&D intensive manufacturing firm, our results suggest that a fast transfer speed (as measured by the time it takes for a research project to develop and transfer its first research result to business units) is associated with a better research performance (as measured by the total number of transfers the research project generates). Moreover, we find that different types of external R&D partners—science‐based and market‐based partners—play distinct roles in speeding up project first research transfers. While market‐based partnerships (i.e., customers and suppliers) generally contribute to a faster transfer of first research results, science‐based partnerships (i.e., universities and research institutions) only speed up first research transfers of technologically very complex projects. Our results also show that early patent filings by research projects accelerate first research transfers.     

Women and food aid: a developmental perspective

The unique aspect of food aid projects is that food, rather than money, is used for achieving developmental objectives. As food is usually controlled by women, they benefit most from considering it to be of economic value. Poor women seem to be short of resources--time and money--which can be supplemented by food aid. Through its income-transfer effect, food aid can enable women to work fewer hours/day and thus have more discretionary time. It can also provide, directly or indirectly, the cash necessary for women to use skills they already possess to set themselves up in small businesses. Food aid projects achieve their developmental objectives through: the nutritional content of the distributed commodity; the income transfer effect; cooperatives or associations; specific activities associated with the project; community improvement aspects resulting from the project; and provision of budgetary support to release resources for additional developmental activities. There are a number of ways through which food aid exerts its effect on women from a developmental perspective. Consumption of the food aid commodity provides women with an improved diet. Food aid as an income transfer can enable women to have more discretionary time. Providing women with opportunities for income-generating activities is an important aspect of development. Women's cooperatives or associations funded by food aid commodities can provide women with income. Current food aid projects, if properly planned, can be beneficial to women without the incorporation of specific activities or skills training. One way that food aid helps women gain more time is by freeing them from wage employment. Another way is to use the income transfer for the purchasing of consumer goods that reduce their labor.     

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.     

Evaluating QFD's Use in US Firms as a Process for Developing Products

Quality Function Deployment (QFD) is a process that originated in Japan for managing product development. In this article, Abbie Griffin presents results of a field-based, scientific study of US firms' efforts to implement QFD methods. Her research goals were to understand the QFD process as it is used and implemented, to begin to estimate US product development improvements attributable to QFD and to identify factors linked to QFD's successful use. Based on a study of 35 projects, she found that QFD demonstrated only relatively minor, short-term, measurable impacts on product development performance. Yet, the process may have the potential to improve the development climate in the long term, possibly leading to future, measurable improvements in development performance. Successful projects differed in several ways from those projects that failed in their implementation efforts. Finally, the results suggest several characteristics of product development processes that improve the way products are developed in US companies, including structuring the decision-making processes across functional groups, building a solidly organized, highly motivated team and moving information efficiently from its origin to the ultimate user.     

Learning processes in municipal broadband projects: An absorptive capacity perspective

Effective knowledge management is important to the success of information technology projects. This research applies the integrated lens of the absorptive capacity theory and the social process model of information system development projects to examine the dynamic of knowledge activities concerning broadband infrastructure development in the context of municipal broadband networks. The research questions are: (1) What is the extent of the dynamic of knowledge activities involved in the development process?, (2) What are the events that trigger knowledge activities in municipal broadband development?, and (3) How does a city create and utilize new knowledge in the development process? This study examines municipal wireless projects in three cities (Chaska, MN; Hermosa Beach, CA; and Fredericton, Canada). Events that trigger knowledge activities are assignment of personnel, physical system construction, performance problems, resistance, and reassignment of organizational roles. Four factors that influence knowledge activities and project performance are the dynamic of technology development, partnership commitments, limitation of external knowledge and learning-by-doing, and political dynamics. The study has policy implications for cities that are in the process of planning and deployment. A good project planning, user expectation management, systematic performance evaluation, a careful partner selection process, and the use of service level agreements are important to project success. In addition, cities need to take into consideration that the technology is not a plug and play technology and that considerable efforts are needed to integrate the technology with other solutions to deliver broadband services as well as to configure the system according to topologies, street conditions, buildings, density of trees, among others.     

Do development projects crowd-out private sector activities? Evidence from contract farming participation in Northern Ghana

Contract farming (CF) is attractive as a possible private sector-led strategy for improving market coordination and smallholder farmers’ welfare. At the same time, governmental and non-governmental development projects aimed at improving farmers’ welfare continue to be organized. It is not uncommon for CF activities and development projects to take place in the same communities. Yet so far there is no evidence on how development projects affect CF activities. We examine factors affecting entry in and exit from different maize CF schemes in Northern Ghana, and focus specifically on the role of development projects. We find that the presence of agricultural development projects in the community is associated with lower scheme entry, but this not the case for non-agricultural projects. CF exit is more strongly associated with maize projects, but not significantly with non-maize or non-agricultural projects. Thus, our findings do not support concerns of a general moral hazard problem arising from the presence of any development project, but indicate possible negative associations of more closely related agricultural or maize projects with maize CF participation.     

Building Dynamic Capabilities in New Product Development through Intertemporal Integration

Although successful development of a given product may help explain the current success of a firm, creating longer‐term competitive advantage demands significantly more attention to developing and nurturing dynamic integration capabilities. These capabilities propel product development activities in ways that build on and develop technological and marketing capabilities for future product development efforts and create platforms for future product development. In this article, we develop a conceptual model of a dynamic integration process in product development, which we call intertemporal integration (ITI). In its most general form ITI is defined as the process of collecting, interpreting, and internalizing technological and marketing capabilities from past new product development projects and incorporating that knowledge in a systematic and purposeful manner into the development of future new products. Research propositions outlining the relationship of ITI to performance are presented. We provide specific examples of managerial mechanisms to be used in implementing ITI. We conclude with implications for research and practice. Effective management of ITI can increase new product development success and long‐term competitive advantage. This implies that management needs to engage in activities that gather and transform information and knowledge from prior development projects so that it can be used in future development projects. Project audits, design databases in computer‐aided design (CAD) systems, engineering notebooks, collections of test and experimental results, market research and test market results, project management databases, and other activities will all be important in the acquisition of knowledge from prior new product development (NPD) projects. Managers also should initiate the creation and maintenance of databases of technical and marketing information from prior projects, job performance reports, seminars and workshops related to technological issues and advances, and publication of technical journals to assist in the process of knowledge acquisition. Similarly, techniques such as assigning project managers from earlier development projects, reusing key components and technologies, and developing a company‐wide methodology for managing projects can be used to boost the application and use of knowledge.     

Product development strategies for established market pioneers,early followers,and late entrants

At the time of entry, market pioneers are known for emphasizing major product development projects. After being in the market for many years, however, do market pioneers, early followers, and late entrants maintain different product development strategies? Data from 2273 established manufacturing businesses reveal that market pioneers have the highest probability of engaging in product development, which covers product R&D spending as well as new product sales. Even so, market pioneers and early followers tend to emphasize minor projects, such as product improvements and line extensions. Late entrants are less likely to engage in product development, but those that do tend to emphasize major development efforts. Copyright © 2002 John Wiley & Sons, Ltd.     

Links between Internal and External Cooperation in Product Development: An Exploratory Study*

While there is an overwhelming amount of publications on cooperation in product development projects, they mainly focus on cooperation between business functions within an organization (internal cooperation) or on cooperation between organizations (external cooperation). Yet the relationship between internal and external cooperation has received only scarce attention. This article studies how internal and external cooperation relate. Following an extensive literature study and 12 exploratory interviews with managers in eight organizations, a case‐research design was set up. More specifically, six product development projects were studied in depth, combining data from interviews, questionnaires, and information from secondary sources. Based on these cases, the authors present four different links between internal and external cooperation: (1) Internal cooperation may serve as a mechanism to coordinate external cooperation; (2) Internal cooperative norms are similar to external cooperative norms; (3) External cooperation may stimulate internal cooperation; and (4) Internal cooperation may be an essential part of organizational learning from external partners. The results of this exploratory study prove the interaction between internal and external cooperation to be a subject worthy of investigation and demonstrate that in order to appreciate fully the quality of a firm's external cooperation efforts, they should be studied in combination with the firm's internal interfaces. The authors also show the managerial implications of these links, as well as some directions for further research.     

The Role of Suppliers in Market Intelligence Gathering for Radical and Incremental Innovation*

Drawing on transaction cost economics theory, this study addresses the following research questions: (1) Does supplier involvement in market intelligence gathering activities have a greater impact on innovation success in predesign or commercialization activities? and (2) Does supplier involvement in market intelligence gathering activities have a greater impact on success in radical or incremental product innovation? Hypotheses are tested using both subjective and objective measures of success from a study of 205 incremental and 110 radical new product development projects. Results from the estimation of a two‐group path model suggest that this theoretical framework is useful in providing guidance as to when product developers should emphasize the gathering of market intelligence through suppliers. Consistent with conventional wisdom, the findings suggest that supplier involvement in market intelligence gathering activities are positively related to success in incremental innovations across predesign and commercialization activities. However, supplier involvement in market intelligence gathering activities is found to have no significant impact on market share and is negatively associated with perceived product performance in radical innovations in predesign tasks. Also, while there was no significant difference in market share for supplier involvement in market intelligence gathering activities between radical and incremental innovation in commercialization activities, supplier involvement in these activities did have a greater impact on perceived product performance in radical innovation than it did in incremental innovation. Although current practice suggests that teams allocate fewer resources to the gathering of market intelligence through their suppliers during predesign activities in incremental innovation projects compared with radical innovation projects, the findings in this study suggest that they should do the opposite. Shifting resources allocated for engaging suppliers in market information gathering activities in predesign activities from radical innovation projects to incremental innovation projects could increase the return on these investments. Alternatively, these resources currently allocated to the gathering of market intelligence through suppliers in predesign activities of radical innovation projects could also provide greater benefits if allocated to commercialization activities of radical innovation projects, where they have the greatest positive impact.     

Supplier development and the relationship life-cycle

The mainstream view holds that over time buyer–supplier relationships evolve through a number of phases. As a consequence, supplier development as a buyer–supplier relationship management practice should also be adapted to the life-cycle phase. Supplier development activities matching the buyer–supplier relationship life-cycle phase will lead to more favorable performance improvements. However, prior studies have neglected the relationship life-cycle perspective. This empirical study shows how the length of the buyer–supplier relationship can be used to improve the explanatory power of models investigating the performance outcomes of supplier development activities. The results show that supplier development is more effective in mature as opposed to initial and declining life-cycles phases.     

Externally Directed and Internally Directed Market Launch Management: The Role of Organizational Factors in Influencing New Product Success

Introducing new products remains a critical challenge for managers. Consumer acceptance of new products is key to new product success and requires the effective implementation of market launch activities. The present study describes the relationship between different types of market launch activities and market‐related, time‐related, and financial market launch success. The study's framework extends previous work on launch management by complementing the view that launch activities are predominantly outwardly directed with the notion that launch management can also be inwardly directed. More specifically, launch activities can both target customers as the external audience, for example, via communication and pricing, and address an internal audience, such as management and sales personnel, for example, using departmental coordination or employee incentives. The study also sets out to investigate how situational factors impact the relative effectiveness of both externally directed and internally directed launch activities in engendering successful new product launches. In particular, product newness, technology drivers, and firm size are considered as relevant variables. Structural equation analysis of data on 178 new products across industries provide empirical evidence that market launch success depends on the intensity of both externally directed and internally directed market launch activities. With regard to the overall impact of internally directed activities, the findings confirm that organizational factors and antecedents indeed play a critical role in new product launch and its respective performance with internally directed activities having an even stronger impact on time‐related and financial success than outwardly directed instruments. Specifically, these internal activities are often viewed as idiosyncratic resources that are hard for competitors to observe and are therefore more difficult—if not impossible—to replicate compared to externally directed activities in market launch. The paper clearly pinpoints that the successful launch of new products is a complex task that also necessitates the implementation of internally directed launch activities. Fast market penetration requires coordination among the different internal players as well as support from top management. Furthermore, the financial objectives of the market launch can only be met if employees and executives both receive the necessary incentives and support to effectively execute the new product introduction. The study also demonstrates that moderators impact the strength of the effectiveness of these two different types of market launch activities. This research provides important implications for launch management by advocating that the two foci on external and internal constituencies should not be pursued in isolation but that instead, the opposite is true.     

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.     

Product development cycle time for business-to-business products

For a number of years, firms have been implementing changes in the way they develop new products, changes that are targeted at reducing overall product development cycle times. And over the years, a number of academics have conducted research trying to understand the factors that are related to reducing new product development (NPD) times. But the question remains — just how long does product development generally take in absolute numbers? Information on how long product development takes is helpful to firms for planning and controlling the flow of products into the marketplace and in determining resource needs for NPD. Other than anecdotal data pertaining to particular projects that have been commercialized by particular firms, very little hard data have been reported on this topic. This article analyzes data to quantify average cycle times for physical goods commercialized by business-to-business (B2B) firms. The data are a subset of a much larger data set from the Product Development & Management Association's (PDMA) Best Practices research. The analysis presents average product development cycle times for four different types of projects (new-to-the-world, new-to-the-firm, next generation improvements and incremental improvements), presents evidence of the lack of a relationship between cycle time and success and looks at factors that are associated with differences in the length of product development cycle times.     

Investigating differences among research projects and implications for managers

As research and innovation have become central to the economy, the challenge of managing these activities has taken on greater importance. Studies have focused on the impact of organizational variables on research activities, such as work environment, human resource factors, and managerial practices. But little attention has been paid to the effect of differences among types of research projects. While the notion that differences exist among research projects is acknowledged, particularly in the research & development portfolio literature, there have been relatively few studies into the dimensions by which research projects, and needs of project team members, differ. Further, there is little recognition that these differences translate into the need for different research project management practices. The objective of this paper is to investigate differences among research projects along three dimensions, amount of funding, complexity of project teams, and research orientation. These dimensions are selected because of their central theoretical importance in the organizational literature, as well as posing a number of different challenges for research management. This study looked at 18 research projects at a national laboratory and analyzed the responses of project members to a comprehensive research environment survey conducted in 2001. The results of the analysis indicate that there are significant differences between types of projects along three dimensions and suggest ways that research performance can be improved through management intervention.     

Managing Knowledge for Innovation: The Case of Business‐to‐Business Services*

The present study builds a typology of organizational knowledge in business services and empirically examines the effects of knowledge on innovation performance. It is suggested that firms differ with respect to their knowledge creation approaches and that these approaches have implications for firms' innovation activities. A conceptual framework of knowledge assets with degrees of tacitness and collectiveness as the principal axes is used to ground the empirical analysis. The organizational knowledge framework is empirically operationalized using survey data from 167 business service firms and supplementary case study evidence from 16 other firms. It is found that business service improvements and new service introductions are significantly associated with collectively held knowledge, such as codified service solutions or team‐based competences and procedures. In contrast, relying solely on tacit knowledge held by individuals may hamper innovation. The results also suggest that tacit collective knowledge is more closely associated with new service introductions, whereas explicit collective knowledge is associated with service improvements. Tacit collective knowledge is thus conducive. A managerial implication is that new service introductions necessitate team competences and routines, whereas incremental service improvements are more likely if procedures are in place to codify services into explicit solutions or technologies. Thus, the knowledge management approach should depend on the strategic orientation of the service firm toward continuous improvement of existing services or development of completely new services.     

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.     

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.