Skip to navigation, content

Showing 21 - 30 of 61 matches

Page 1 2 3 4 5 6 7    
  1. Must-Have or Nice-to-Have? Using Conjoint Analysis to Measure and Decide Locked

    Research | Posted: 2005-01-15

    By Brian Ottum Going out and hearing the ‘voice of the customer’ is easy. The hard part is separating out the “nice to have’s” from the “must have’s.” Conjoint analysis is an excellent tool for creating a succinct ranking of what is most important to customers. It uncovers the realistic importance of product and service features, as well as price sensitivity. Conjoint is much more accurate than old fashioned direct questioning because it more closely mirrors actual purchase decisions. This presentation covers the basics of conjoint analysis presenting some theory with a number of examples. (65 pages)

  2. Taking Voice of the Customer to the Next Level: Key Findings and Conference Highlights Locked

    Research | Posted: 2004-11-30

    At a November 2004 conference, "Taking Voice of the Customer (VOC) to the Next Level," leading practitioners from companies such as Microsoft, Dow Chemical, General Motors, and Sara Lee discussed approaches for gathering and analyzing customer needs. Presenters from a wide range of functional specialties shared their experiences regarding both traditional and non-traditional methods of involving customers in new product development. Presenters urged companies of all sizes to get started on VOC in whatever capacity possible. Consensus was heard on the need to use varied, converging VOC methods with complementary strengths and weaknesses to achieve a complete picture of customers. Presenters recommended combining VOC with other sources, such as Website click-through data or point-of-sale data. Lastly, the need for alignment and integration of VOC efforts throughout the organization echoed throughout the conference. (7 pages)

  3. Getting Voice of the Customer Right:  Taking the Ambiguity Out of Product Definition [Transcript] Locked

    Research | Posted: 2004-11-20

    Led by Sheila Mello, Principal and Managing Partner, Product Development Consulting, Inc.Schedule slips, wasted development resources, and products that fail or never make it to market – these are some of the consequences of poor product definition. Identifying unambiguous customer requirements is at the core of a company’s potential for growth – it determines everything from where your development time and dollars are spent to what your customers might pay a premium for. This session outlines a step-by-step process for generating products that provide maximum customer value. This process balances your company's core competencies with market needs, positioning you to surpass competitors. (21 pages)

  4. Getting Voice of the Customer Right: Taking the Ambiguity Out of Product Definition [Presentation Slides] Locked

    Research | Posted: 2004-11-20

    Presentation Slides accompanying the transcript above: "Getting Voice of the Customer Right: Taking the Ambiguity Out of Product Definition." Download these slides to follow along with the transcript.

  5. Black and Decker’s Strike Force Takes to the Road Locked

    Research | Posted: 2004-09-29

    Black and Decker's (B&D) Strike Force team is a roving band that brings product development directly to the customer. Strike Force consists of teams driving vans loaded with B&D tools and prototypes to sites around the country. Typical destinations include retailer’s grand openings and community events. The Strike Force sets up an elaborate display that allows for large numbers of users to test an array of tools – while they are carefully observed. Team members include product managers, engineers and industrial designers. When not driving to event sites, team members spend 100 percent of their working time with consumer-users. As few as three and as many as ten B&D people are present at each event. They provide explanatory material about the tools and start participants off at the first workstation. At any given event, the Strike Force expects to work with an average of 600 people a day. By inviting the consumer to participate in the creation of products that satisfy and serve real needs, the Strike Force serves to bring user awareness into the heart of product development. (5 pages)

  6. Product Strategy 101: The Saturn Difference Targets Customer Enthusiasm Locked

    Research | Posted: 2004-09-28

    From its inception, Saturn was challenged to introduce a new American car into a highly competitive and vastly oversupplied marketplace, in a time of national economic uncertainty, when more and more Americans were buying imports. To succeed, Saturn had to foster a different kind of consciousness. “The Saturn Difference” was a customer-focused culture and process aimed at attracting and satisfying import-minded buyers. The central idea that drives Saturn rests in the phrase “moments of truth.” These moments include all of the points where customers interact with the company. Saturn created a list of these moments, including such items as exposure to an ad for the product; walking into a retail facility; asking for a test drive; buying the product; bringing it in for service; and coming back for a trade-in. Each moment of truth was analyzed to identify what it would take for customers to feel enthusiasm, to share it with others, and to keep coming back. Saturn’s moments of truth research resulted in seven books that detail every aspect of laying out and running a first-rate auto store. The goal: consistent, high-quality customer experience across the entire spectrum of buying and owning a Saturn product. (4 pages)

  7. How Partnering With the Customer Helped Nortel Shift Strategy Locked

    Research | Posted: 2004-09-28

    Northern Telecom (Nortel) put itself on the fast track to becoming a “solutions” rather than a “technological products” company by inviting end users to participate in product design and development. Nortel's “Solutions Through Partnership” process began with focus-groups intended to provide designers with product feedback. Two sessions, each lasting two days, occurred off site: one session was devoted to distributors, the other to end users. Enthusiastic end-user response gave the Nortel group support to go further – bringing in end users to look at a whole new redirection of products built around broad customer business objectives and needs. Nortel created a two-part program.The first part aimed at understanding end user’s major business challenges, surfacing trends, and learning how telecommunications technology could support their performance; part two brought designers back to present prototypes based on earlier feedback. As designers stepped into the end-user’s shoes, new product design criteria, based on customers’ genuine needs, become the designer’s key objectives. Nortel also discovered that building end-user feedback into design reduced cost on a release-over-release basis, and improved time to market. (6 pages)

  8. Dade International Uses Market-Driven Product Definition to Prioritize Customer Requirements Locked

    Research | Posted: 2004-09-27

    Dade International became quite proficient at the development process from the feasibility stage through commercialization. But Dade benchmarking studies indicated that its teams could get much greater value for their R&D dollar through optimizing the "fuzzy front-end" of the development process. Dade turned to Market-Driven Product Definition, a method for gaining clarity around customer requirements, for reducing risk and limiting guesswork. Market-Driven Product Definition is a five step process for discovering customers’ latent needs, establishing measurable criteria for meeting requirements, and limiting confusions that lead to costly delays. With MDPD, team members collect unfiltered customer information; they translate responses collected from customers into requirements; they establish metrics for downstream development; the team then validates, prioritizes, and selects requirements using traditional market research tools such as surveys; and finally, they generate product specifications, by inviting creative problem solvers to participate in idea generation. Says a manager at Dade, “MDPD get(s) the whole team involved in understanding the environment in which we’re going to introduce a product…focusing on what needs to be done, from the customer's point of view." (6 pages)

  9. IBM ThinkPad 760CD Success Reflects Changes to Internal Culture and Streamlined Processes Locked

    Research | Posted: 2004-09-27

    This report describes best practices from the team that created IBM’s ThinkPad 760CD, an award-winning notebook computer in the 1990s. The team employed a combination of traditional and unconventional methods to hear the voice of the customer. At one end of the spectrum, they used focus groups, quantitative market research, and surveys, as well as working the industry trade shows. They also held customer and industry advisory council meetings with customers, competitor's customers, re-sellers, and distributors, as well as with significant industry opinion leaders. At the less-traditional end of the spectrum are their Road Warriors Council and ThinkPad Partners. The first is what an IBM director calls "heat seekers" – Lead Users who provide candid feedback. The ThinkPad Partners is a small band of Internet junkies who may be likened to Harley Davidson’s owners group. They devote up to 20 hours a week of unpaid time, responding to questions about ThinkPads. Along the way, IBM has learned that spending less on product development may pay greater dividends, in terms of product cost and time to market, by avoiding product complexity. (4 pages)

  10. Cisco Systems Uses Web-Enabled Processes To Drive Market Focused Product Development Locked

    Research | Posted: 2004-09-27

    This report describes how Cisco Systems, a leading provider of networking equipment and related products, has used the Internet to enhance global product development, create efficiencies and reduce time-to-market. In an environment characterized by increasing globalization and customization, Cisco developed Internet-based tools to capture customer insights and enhance communication, both internally and with its growing network of suppliers. Cisco’s tools create efficiencies in all phases of the development process: integrated front-end tools for design and development; integrated portals for the team to access and exchange information in real-time; and integrated back-end tools for coordinating suppliers with manufacturing and production. This report describes how Cisco leveraged these tools to gain value-added design and development input; to enable collaboration and reduce cycle time; and to integrate suppliers with manufacturing and production through a set of common tools. Cisco’s experience shows that it’s important to get the process right first – and then choose the right technology to facilitate that process. (6 pages)

Page 1 2 3 4 5 6 7