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.     

Leadership Style: Its Impact on Cross-Functional Product Development

This article reports the results of a study in which cross-functional product development projects in six companies were analyzed. The study was conducted as part of an interdisciplinary research involving technological, organizational, and behavioral analysis. The article draws on an excerpt of the data collected on leadership styles among project managers as well as some data on organizational climate and team learning. Leadership style, especially the leaders' employee orientation, co-varied significantly with how members of the cross-functional teams perceived their work climate and possibilities for innovative learning. The results of the analyses point to the leader's behavior, rather than his power, as an important factor determining the work climate in successful cross-functional product development projects.     

The Impact of User‐Oriented Design on New Product Development: An Examination of Fundamental Relationships*

Design offers a potent way to position and to differentiate products and can play a significant role in their success. In many ways it is the focus on deep understanding of the customer or user—what may be termed user‐oriented design (UOD)—that transforms a bundle of technology with the ability to provide functionality into a “product” that people desire to interact with and from which they derive benefits. Even though the importance of this type of design is gaining recognition, several fundamental relationships between user‐oriented design contributions and the new product development (NPD) process and outcomes (i.e., product) remain unresearched, although they are assumed. This article examines the fundamental relationships underlying the incorporation of a user orientation into the NPD process. The discussion is organized around UOD's impact in terms of enhancing collaborative new product development (process oriented), improving idea generation (process oriented), producing superior product or service solutions (product oriented), and facilitating product appropriateness and adoption (product oriented). Each of these is developed and presented in the form of a research proposition relating to the impact of user‐oriented design on product development. The fundamental relationships articulated concerning UOD's impact on NPD form a conceptual framework for this approach to product design and development. For practitioners, the article suggests how user‐oriented design can improve NPD through its more grounded and comprehensive approach, along with the elevated appreciation of design challenges and heightened sense of possibilities for a product being developed. For scholars, the article identifies four important areas for UOD research. In addition to the rich avenues offered for research by each of these, the framework presented provides a foundation for further study as well as the development of new measures and tools for enhancing NPD efforts.     

A Discussion of the Link Between One Organization's Style and Structure and Its Connection With Its Market

A growing body of literature has identified some important characteristics of organizations that produce product innovations. This work demonstrates the importance of staying close to the customer and using market input for new product development. In this study, Kathleen Bentley helps us understand the relevance of this research for one small high-technology firm. She uses qualitative data to develop a detailed picture of what close customer contact means for this firm, and how the firm's ability to relate to its customers is tied to the nature of its organization. The article concludes that the organization's structure and style are tightly linked to its ability to connect with its market and maintain its competitive edge.     

Product Innovativeness and Entry Strategy: Impact on Cycle Time and Break-even Time

New product development time, or cycle time, has become a critical competitive variable, particularly for small high-tech manufacturing firms. The business press is filled with examples about large firms that have successfully reduced cycle time. This article investigates the relative impact of product innovation and entry strategy on cycle time and initial market performance of small firms. Using a sample of seventy-three small manufacturing firms, Abdul Ali, Robert Krapfel, Jr., and Douglas LaBahn find that faster product development is associated with shorter break-even time. Their results also indicate that these firms are achieving shorter cycle time not by sacrificing product quality, but by keeping the technical content of the product simple. Past research has not taken into account this relationship, and this may be one of the reasons why researchers have often suggested conflicting impact of entry strategy on market performance.     

Product Technology Transfer in the Upstream Supply Chain

This article addresses the transfer of new product technologies from outside the firm for integration into a new product system as part of a product development effort. Product technology transfer is a key activity in the complex process of new product development and is the fundamental link in the technology supply chain. Product technology transfer too often is dealt with in an ad‐hoc fashion. Purposeful management of the product technology transfer process leads to more effective transfers in terms of timeliness, cost, functional performance, and competence building. Better management of product technology transfer gives firms access to a greater variety of new technology options, improves a firm's ability to offer significantly differentiated products, deepens the firm's competitive competencies, and positively influences sustained product development success. The central objective of this article is to gain insight into product technology transfer so that companies can manage this process more successfully and so that researchers can investigate this critical activity further. This article describes the technology supply chain as a unique form of a supply chain that poses a set of managerial challenges and requirements distinguishing it from the more traditional component supply chain. Because a single product technology transfer project is the fundamental piece in the technology supply chain, understanding this piece well is key to leveraging the extended technology supply chain and to improving overall product development performance. This article integrates literatures on new product development, supply chain management, and technology management and builds on organizational theory to present a conceptual model of determinants of product technology transfer success. The core proposition is that product technology transfer effectiveness is greatest when companies carefully match (or “fit”) the type of technology to be transferred (the “technology uncertainty”) with the type of relationship between the technology supplier and recipient (the “interorganizational interaction”). A quite detailed framework characterizing technology uncertainty along the dimensions of technology novelty, complexity, and tacitness is presented to help in assessing the challenges associated with transferring a particular product technology. This article also considers detailed elements characterizing the interorganizational interactions between the technology source and recipient firms. This helps firms consider the appropriate means to facilitate the interfirm process of technology transfer. Overall, this article provides practical insight into characterizing technologies and into improving the product technology transfer process. This article also provides a strong theoretical foundation to aid future research on product technology transfer in the technology supply chain.     

Product Development Strategy: An Integration of Technology and Marketing

Although it seems obvious that a new product development strategy must bring together marketing and R&D strategies, the conceptual development of marketing and R&D strategies has taken place in relative isolation. More than ten years ago, when Professor Harry Nyström began his research program on product development in Swedish firms, he realized that the isolation wasn't an appropriate point of view. He began to construct a conceptual framework for analyzing product development strategies that incorporated many more variables than had traditionally been considered. The latest set of firms in the research program are four pulp and paper companies. They are in mature, process industries, quite unlike the earlier study firms. Yet many of the same propositions from the earlier research still hold. In this article, Professor Nyström presents the most recent version of his framework to help managers develop an integrated product development strategy.     

Critical path method for introducing an industrial product

New product development continues to be a vital evil for most organizations. Considerable attention has been directed toward this function in the consumer goods field but relatively little research has been directed toward this critical task for producers of industrial goods. Industrial goods marketing managers seem to agree that error at the announcement/ introduction phase of the new product development process is responsible for the greatest number of new product failures. This article suggests use of the critical path method to ensure success at this crucial stage.     

Nine Tested Ways to Mislead Product Planners

Once concept development is completed, the next stage of the new product project has begun. It's time for more marketing research—good marketing research, because mistakes at this stage mean big money losses as well as job losses. This article sets out a number of marketing research mistakes that product planners should watch for.     

Coordination of Design Supply Chains for Bundling Physical and Software Products*

Research on product development management has concentrated on physical products or on software, but not both. This article explores a special new product development (NPD) approach in which the internal development of core physical products is augmented by bundled and largely outsourced software features. We studied a medical device producer that has established a new medical information product group (MIPG) within their NPD organization to create software features that are bundled with their core physical products. The MIPG has conceptualized these software features as multiple software development projects, and then coordinated their realization largely through the use of external software suppliers. This case study centers on the question: how can firms effectively coordinate such product development processes? Our analysis of case evidence and related literature suggests that such product bundling processes, when pursued through design supply chains (DSC), are more complex than is typical for the development of streams of either physical products or software products individually. We observe that DSC coordination transcends the requirements associated with traditional “stage‐gate” NPD processes used for physical product development. Managers in DSC settings face a tension inherent to distributed work: keeping internal and external development efforts separate to exploit the design capabilities within a network of software suppliers, while ensuring effective delivery of a stream of bundled products. Many managers face this coordination tension with little, if any, prior knowledge of how to create a streamlined and effective DSC. Our research indicates that these managers need to make a series of interrelated decisions: the number of suppliers to qualify and include in or exclude from the DSC; the basis for measuring and modifying the scope of the suppliers' work; the need to account for asymmetric cost structures and expertise across the DSC; the mechanisms for synchronizing development work across elements of the DSC; and the approaches for developing skills—both technical and administrative—that project managers need for utilizing in‐house competencies while acquiring and assimilating design know‐how from external development organizations. When managers take a flexible approach toward these decisions based on a modular set of software development projects, they can improve their NPD outcomes through technical and organizational experimentation and adjust their own resource deployment to best utilize the suppliers' capabilities within their DSC.     

Disconnected Amid the Networks and Chains: Employee Detachment from Company and Union after Offshoring

Much has been written about the relocation of services jobs away from OECD nations by offshoring. But what happens to those who remain employed at workplaces where offshoring has been carried out? Based on survey and interview data of UK insurance and banking staff, this article explores employees' subjective understandings of the impacts of offshoring. The article brings together literature on Global Commodity Chains and Labour Process Theory, as it expands the focus of research on offshoring from macro/meso discussions of globalization and firm strategy into more micro‐level analysis of employee interpretations of workplace change. The data indicate a collapse in morale and work dignity for UK financial services workers and suggest that offshoring is not associated with a rise in skill levels of surviving jobs. Many staff reported a climate of detachment and cynicism after offshoring. Detachment and disaffection applies to employees' feelings towards their employer and their union, and is discussed as a paradoxical by‐product of the growing incorporation of services work into Global Commodity Chains or Global Production Networks.     

Investigating the Drivers of Innovation and New Product Success: A Comparison of Strategic Orientations*

The notion of producing innovations and achieving new product success has received a great deal of attention. Though many have investigated these effects in marketing and various fields within management, there has been little cross‐fertilization between fields of study to explain the basis for this superior performance. Though research has examined the resource‐based view (RBV) and market orientation individually, none has evaluated and compared their effect on firm innovation and new product success in one study. Furthermore, although empirical work has been conducted between market orientation and organizational learning, comparatively less research has been conducted to evaluate the relationship between organizational learning and the RBV to examine their combined effects on a firm's ability to innovate and succeed. Subsequently, the purpose of the present article is to investigate whether a focus on the customer (i.e., market orientation) or the firm (i.e., RBV) will drive the ability to (1) innovate within the firm and (2) succeed in terms of new product success, financial performance, market share, and customer value. The present article examines the relationship between organizational learning and the RBV and market orientation. It presents an empirically testable framework that investigates the relationship that RBV and market orientation have with performance outcomes. Data were collected from 249 senior executives. LISREL was applied to evaluate the relationships. Confirmatory factor analysis and related techniques were applied to assess the robustness of the measures used. Findings show that organizational learning is strongly associated with market orientation, which in turn impacts various performance outcomes including customer value. The RBV had a significant relationship with new product success. These results suggest that managers seeking innovation and new product success should focus less on the provision of customer value. Instead they should look toward developing their resources within the firm, including investing in human resources, to ultimately provide value to the firm. Findings indicate that this unique offering—innovations—will have an indirect effect on customer value and financial performance. In contrast, those in pursuit of positive financial performance and customer value should focus on the development of market orientation. Even though this will not necessarily lead to the development of innovative processes and new product success according to the present study, this approach may lead to a greater market share in the long term. This article reviews theoretical and managerial implications in more depth, providing an impetus for further research.     

QFD—linking the customer to the product development process as a part of the TQM concept

LKAB is one of the world's leading sup-pliers of advanced iron ore products. Its most important markets are the blast furnace based steelworks of Europe. As a result of customers' demands for ever-better products, LKAB has begun to apply Quality Function Deployment (QFD) to its product development pro-grammes. QFD, originally developed in Japan, is a technique which utilises a series of matrices to translate customers' requirements into technical specifications that the producer can use. So far the methodology has mainly been used in the manufacturing industry, with very few applications in process industry.
When launching its QFD project, LKAB began by making strenuous efforts to acquire credible and relevant customer data. Experience after one year's work has been encouraging; the QFD technique has proved to be an effective instrument for feeding customers' requirements into the product development process. In addition, it serves as a guide to setting priorities for research projects. The technique promises to become an established tool in the cornpany's Total Quality Management programme.     

Exploring purchasing integration in product development

With increasing outsourcing and the growing importance of product innovation as a means for creating competitive advantage, the integration of purchasing and product development processes has become a key issue for many firms. Although, consequently, the integration of purchasing and suppliers in product development has attracted growing attention from practitioners and researchers, most research on the topic remains limited to the context of single development projects. The integration with long-term issues such as technological alignment between supplier and manufacturer is often neglected. This limited conception and the lack of a coherent definition of what purchasing integration in product involvement is form a major impediment to the advancement of knowledge in this field. Therefore, this article develops a framework encompassing various activities across different management levels, which embody the alignment and integration of purchasing and product development processes.     

The Valley of Death as Context for Role Theory in Product Innovation

The purpose of this paper is to define and explain the front end of product innovation as a discrete segment of development between research and product development. The Valley of Death is used as a metaphor to describe the relative lack of resources and expertise in this area of development. The metaphor suggests that there are relative more resources on one side of the valley in the form of research expertise and on the other side by commercialization expertise and resources. Within this valley a set of interlocking roles are examined that move projects from one side to the other. The empirical methodology used in this study gathered data from 272 Product Development & Management Association (PDMA) members with extensive experience in the front end of product development using a Web‐based survey instrument. Extensive pretests with experienced practitioners were conducted to develop the instrument. Results indicate that significant development takes place before projects enter into a firm's formal product development process. The data also support the roles of champion, sponsor, and gatekeeper as major actors that work together to develop and promote projects for introduction into the formal process. Champions make the organization aware of opportunities by conceptualizing the idea and preparing business cases. Sponsors support the development of promising ideas by providing resources to demonstrate the project's viability. Gatekeepers set criteria and make acceptance decisions. The data also reveal a dynamic interdependence between role players. It is concluded that the Valley of Death is a productive tool for identifying and understanding a critical area of development that has not been adequately addressed. This research finds a dynamic interplay between roles to accomplish tasks that are not well understood in practice or the literature. The implications of this research are far‐ranging. It suggests that companies must understand the challenges in the valley, must develop the skills, and must make resources available to master the front end of product innovation. Recognizing roles, providing resources, and establishing expectations and accountability in this area of development become manageable in light of these results. Theoretically, this research informs role theory of a dynamic set of relationships previously treated as static. It also empirically investigates an area of product development where there is limited data. This paper opens profitable inquiries by focusing on an area of development not adequately researched yet drives the activities and investment made in subsequent steps of product development.     

FROM EXPERIENCE: Developing New Product Concepts Via the Lead User Method: A Case Study in a "Low-Tech" Field

Conventional market research methods do not work well in the instance of many industrial goods and services, and yet, accurate understanding of user need is essential for successful product innovation. Cornelius Herstatt and Eric von Hippel report on a successful field application of a "lead user" method for developing concepts for needed new products. This method is built around the idea that the richest understanding of needed new products is held by just a few users. It is possible to identify these "lead users" and then draw them into a process of joint development of new product concepts with manufacturer personnel. In the application described, the lead user method was found to be much faster than traditional ways of identifying promising new product concepts as well as less costly. It also was judged to provide better outcomes by the firm participating in the case. The article includes practical detail on the steps that were used to implement the method at Hilti AG, a leading manufacturer of products and materials used in construction.     

Applying multiple perspectives to the design of a commercialization process

Most commercialization models begin by taking an idea through some sort of stage‐gate product development process. There is much talk about building market thinking into this process, but this paper argues that much more is required. The research identified three perspectives required to be present at all stages of product development. The first is labelled ‘technical and operational’, the second ‘strategic’ and the third ‘commercial’. The paper argues that each perspective is required at every stage to drive the right activities that lead to successful commercialization. The science, idea and opportunity stage leads onto the technology and feasibility stage, which in turn leads onto the product and market readiness stage. The research applied the grounded theory methodology to categorize and represent data obtained from interviews and desk research. The resulting model was introduced to a New Zealand Crown Research Institute during a consulting assignment in 2004. Three external experts were selected based on their particular perspectives and experience in the area of product development. Each perspective was built into the commercialization process. Applying multiple perspectives has led to a more robust approach to product development and a greater awareness of how multiple tools work together to create a holistic product development process. Each perspective of the commercialization process can be broken down into detailed stages. The technical and operational perspective addresses areas such as opportunity creation, proof of concept and market readiness. The strategic perspective addresses areas such as strategic fit, strategic analysis/choice and pathways to market. Finally, the commercial perspective addresses areas such as opportunity assessment, feasibility study/business planning and launch.After being in place for 18 months, the challenges faced in implementation were discussed with the current commercialization manager and the model was adapted to another institute wishing to develop a design‐led commercialization process. A key finding of the research was the common understanding of language and meaning across three distinct disciplines and the involvement of each discipline in the decision‐making process. All parties accepted the value of each other's contribution once the different perspectives were understood and accepted. The paper provides useful insights for those involved in the design of commercialization processes and establishes a multi‐dimensional framework that assists in facilitating the different perspectives required for successful commercialization.     

An Interim Report on Measuring Product Development Success and Failure

This article represents findings of a PDMA task force studying measures of product development success and failure. This investigation sought to identify all currently used measures, organize them into categories of similar measures that perform roughly the same function, and contrast the measures used by academics and companies to evaluate new product development performance. The authors compared the measures used in over seventy-five published studies of new product development to those surveyed companies say they use. The concept of product development success has many dimensions and each may be measured in a variety of ways. Firms generally use about four measures from two different categories in determining product development success. Academics and managers tend to focus on rather different sets of product development success/failure measures. Academics tend to investigate product development performance at the firm level, whereas managers currently measure, and indicate that they want to understand more completely, individual product success.     

Developing new business-to-business professional services: What factors impact performance?

Business-to-business professional services has been a high growth area for over a decade. Increasing complexity and high technology characterizes this sector, making new product development both essential and risky for firms. Surprisingly little research has been done to understand the industrial professional services sector and, in particular, to discover what factors lead to new product success or failure, however. This article reports the results of an investigation that examines how professional services firms develop new products and what factors impact the performance of these ventures.     

Determinants of Success in the Development of Applications Software

In this article, the third in the trio of software innovation articles, Chris Voss outlines the key factors that determine whether a new software development is likely to be successful. His research draws on an innovation framework that has emerged from previous research. His results are similar to those of the earlier studies and suggest that the software innovation process has many demands that are common to innovation in other product areas.