Originally Published March/April 2001
Values-Driven Product Innovation
To create a reputation for innovative products, company leaders first have to build a company culture that supports innovation.
The
business bookshelves are brimming with titles advocating speed,
innovation, creativity, and teamwork in the product development
process. Despite the ready availability of such a wealth of data
based on hard-earned experience, however, effective product development
remains a problem for many medical device companies.
The medical device companies that struggle most with their product development processes are often found to be missing a key ingredient. In many such cases, company leaders have failed to develop a set of shared values to define the culture of the company as one that is driven by innovation.
Without such a set of shared values, employees, shareholders, and even company executives themselves may begin to question the strategic direction of the company and its commitment to developing products that meet the needs of the marketplace. In the long term, such uncertainty can translate into a wide range of problems for the company, including reduced investment and lower share prices, a high rate of employee turnover, and inefficiencies that damage the company's ability to develop new products.
Today, a number of forces have become prominent influences over companies' product development processes. First, there is the need to respond to a marketplace whose supply and distribution chains are becoming increasingly globalized at a rapid pace. In this environment, the number of world-class competitors is always growing, creating a more intense, demanding, and rigorous business environment. Second, there are the always-increasing demands of purchasers, who may be scattered throughout the world. Such global markets demand products that meet escalating levels of cost-effectiveness, reliability, and ease of use. And finally, there is the pressure generated by scientific advances with application to medical products. Breakthrough discoveries and technologiessuch as those now being explored in the realm of genomicsproduce an ever-changing competitive framework in which manufacturers must work to meet the needs of demanding markets.
The effects of such macroforces are not limited to the medical device industry. However, medical product developers are especially susceptible to them because new products have traditionally accounted for a major proportion of companies' revenues, without which companies could not justify the huge investments necessary to support continued R&D. Similarly, the need to develop new products renders medical device companies dependent on access to scientific breakthroughs, without which they cannot meet the competitive challenges of the marketplace.
As these forces converge on medical device companies and their staffs, the result is often shorter product life cycles, faster R&D turnaround, and a greater number of development projectsall needing to be accomplished with the fewest possible resources. To remain competitive, device companies must ensure that their product development processes operate at the greatest possible efficiency.
Executive Leadership
The first step toward improving the functioning of a company's product development processes is to determine what elements need to be changed. Development programs that are dysfunctional can often be distinguished from successful programs by reference to the values that drive them (see Table I). To be successful, companies that place a high value on innovation must also follow through on that commitment by developing functional structures and policies that support innovation.
The R&D functions and market positions of many medical device companies can appear deceptively similar. Yet some are clearly more successful than others at supporting innovation. The critical difference often lies with senior management's enthusiastic and visible support of development initiatives, which carries through to the ways that executives manage the company's resources, processes, and values. Properly arranged and managed, these elements help to define a company's culture as one that is committed to innovation.
Resources. A company's resources encompass its employees, technologies, intellectual properties, physical plant, business partners, and many other elements. Carefully conserved and managed, they provide the essential underpinning for everything that the company seeks to accomplish, thereby defining the scope of the business and its operating environment. Neglect of a company's resourceswhether they be sources of funding or products in inventoryis one of the quickest ways to squander away a company's R&D future.
Processes. A company's processes include the core competencies and operating procedures that enable it to effectively utilize resources as necessary to pursue business goals. Virtually every functional area in a company possesses processes and procedures that can and should be adjusted if company executives are serious about supporting a culture of innovation. Examples directly related to product development include employee training, project management, design control, manufacturing processes, and change management.
Values. Support for innovation-related values is often the critical difference between the success and failure of product development initiatives. In this context, innovation-related values can be defined as visible, management-supported, and articulated business criteria for the exploration of new product and market opportunities. Examples of such criteria include the following.
-
Market definition. Under this heading can be grouped criteria for evaluating the technologies, customer segments, and geographic territories that will define the future position of the company.
-
Market size and growth. In this area, company leaders seek to define the minimum market size and growth potential necessary to support a product development initiative, as well as other company objectives.
-
Returns. In this area, management measures a proposed product development initiative against the minimum acceptable return on investment, net present value, or cash flow. Together with other factors, this evaluation can then be taken into account in determining whether to move ahead with the proposal.
Once such values-based criteria have been established, senior management must clearly articulate them throughout the organization. Doing so helps to build a common vision of the company's future direction, markets, customers, and products. When these values have been accepted as guiding principles throughout the organization, senior management must then take the next step of endorsing processes that will effectively mobilize the company's resources in support of those principles.
Product Development Process
No company's processes can ever be any better than the information supplied to them and the tools used to manage their outcome. In the case of product development programs, effective use of time and resources is critical. Waste of either can result in a missed launch window (defined as the point in time of a competitive product launch) and, ultimately, lost profitability.
It has been estimated that, for most industries, missing a launch window by six months can mean the difference between profitability and breakeven (see Figure 1). Alternatively, launching a product six months early can result in a threefold increase in profitability.1
|
| Figure 1. Relationship of cumulative profits over a product's life cycle to the product's launch date relative to that of a competing product. A launch date six months after release of a competing product can reduce profitability by nearly a third; releasing six months ahead of the competition can increase profitability by a factor of three. Modified from Wheelwright and Clark.1 |
Often, the difference between the success and failure of a product development process lies in the company's effective use of design control and project management to control the process. Many companies use a decision process similar to the development decision cycle described below (see Figure 2). Although there exist many variations as needed to address a company's particular needs, most such product development cycles include some version of the following nine phases.
1. Idea Generation. The development decision cycle starts with the search for ideas. The search should be a formal, structured process that seeks out and includes input from relevant medical and scientific literature, customers, advisory bodies, other company departments, and company partners (e.g., suppliers, distributors, development partners). Ideas generated in this phase should be tested for compatibility with the company's predefined innovation valuesthat is, its visible, articulated goals, objectives, and strategies.
2. Screening. In this phase, ideas should be further screened to determine whether the company possesses the necessary competencies and resources to support the idea. If not, a further examination should be considered to determine whether the company can obtain them, how it can do so, and what the cost of obtaining them might be.
3. Concept Testing. During this phase, the product development team refines the product idea into a product concept targeted to specific customer segments. The key question to be answered in this phase is whether the concept is marketable.
4. Strategy Development. In this phase, the team defines the size and structure of the product's target market, creates a strategy for positioning and selling the product, and establishes goals for market share and profit for the first few years after launch of the product.
5. Financial Analysis. Using information developed during previous phases, in this phase the development team conducts a rigorous examination of the marketing strategy to determine whether it is possible for the product to meet company sales, cost, and profit objectives.
6. Product Development. If responses to all the company's previous inquiries have been positive, the product development team is finally ready to turn its attention to the actual development of the product itself. During this phase, which includes an iterative loop linked to market testing (below), the team develops the product concept, drawing, or prototype into a physical product. The key question addressed during this phase is whether the product is technically and commercially viable.
7. Market Testing. In this phase, pilot production units of the finished product are tested to determine whether it performs as expected in final form. Questions asked during this phase include issues of functionality (e.g., are the packaging, labeling, and servicing characteristics as expected?) as well as business issues (e.g., will the product in this form meet the company's sales and financial expectations?). Feedback from this phase must be provided to product development personnel for needed refinements.
8. Commercialization. This phase is intended to determine when, where, and how the completed product should be launched. Fixing the timing of a product launch could be as simple as the date of the next relevant trade show, or as complicated as watching the competition in order to preempt, parallel, or follow its lead in the market.
The location of a product launch can be equally complex. The team must decide whether to launch its product in a particular region, nationally, globally, simultaneously in several places, or on a rolling basis starting in some defined locale and advancing in defined steps.
If the team has done its earlier work properly, how the product is to be introduced is usually a simpler question to answer. In effect, the task at this phase is to confirm the positioning, targeting, and distribution strategies already defined for the product (strategy development, above).
9. Postlaunch Review and Future Development. In this phase, the development team convenes to gather and critique user feedback necessary to update and revise forecasts and expectations. Such feedback should also be used as a basis for development of the next generation of the product, or for the generation of ideas for an entirely new development cycle.
Funnels, Stages, and Gates
By their nature, development projects are complex, multifunctional endeavors that require precise management. Company leaders can benefit by thinking of this process in terms of the following two fundamental concepts.
Project Management Funnel. The new-product development cycle can be visualized as a pipeline or funnel feeding dozens of ideas into the front end of the process. Project management integrates all of the processes necessary for this cycle to operate efficiently. The project manager and team shepherd the project through a series of reviews (at predetermined milestones), where performance is evaluated against business and design control criteria.
Institutionalized project management also ensures that there is executive oversight of the development process to reduce schedule slippage and rework. In short, project management integrates the company by spanning the critical business functions and institutionalizing teamwork.
Design Control Stages and Gates. At specified stages in the product development cycle (design control phase reviews), the company's ideas are tested against defined criteria. The ideas may pass review and be moved along to the next phase, or may fail and end up in the reject bin. Sophisticated project management is required to ensure the timely conduct of these reviews, which are carried out by the product development team.
Such design control phases and reviews constitute a set of interrelated checks and balances that control the product development process. In practice, each design control phase or "stage" offers senior management and the development team an improved view of the design process.
With this better vision, company leaders are able to recognize problems earlier, make midcourse corrections, and adjust resource allocations. The design control process ensures that design input matches design output through a series of interlocking verifications, validations, and phase reviews, or "gates." These phase reviews are used to allocate resources for the next phase of product development.
Conclusion
There are many benefits associated with a company culture that embraces innovation values. A few of the more visible benefits include the following.
-
Less is more. Rigorous reduction by means of the product funnel ensures that only products with the best chance of market success receive priority. As a result, more products hit specified launch windows.
-
Faster cycle times. With better management of a smaller number of projects, companies can ensure both better design and faster development cycles.
-
Better integration. The use of institutionalized project management and design control ensures the integration of business functions and development phases, thereby promoting teamwork and accountability.
-
Increased sales, profitability, and market share. Hitting or accelerating launch windows increases the chances of market success in terms of sales, profits, and market share.
-
Success breeds success. As more successful projects hit their launch windows and meet company expectations, the slope of the learning curve will decline and the processes will become second nature.
Even among medical device companies with well-established organizational structures and highly defined processes, the track records of many companies suggest that product development failures remain a common occurrence. Often, the cause of such failures can be traced to a lack of leadership or absence of management buy-in to the values that are most important for supporting innovation. In short, company executives that fail to develop a culture of innovation can hardly be surprised to find that their companies are not considered innovative.
By contrast, when company executives visibly articulate their support of innovation values, they can ensure that the resources and processes of the organization are utilized to meet and exceed corporate objectives and revenue goals.
|
Further Reading |
References
To the MX main page | To the March/April Table of Contents



