Skip to main content

Specifying the Product

  • Chapter
  • First Online:
Management of Innovation and Product Development

Abstract

Chapter 13 led us into the “front end” of the product development process, with a perspective that focused on the market. Readers should have left that chapter understanding how firms can interpret market needs and come up with a concise description of the product and of the market segment to address.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 109.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    If one thinks about a simple product such as the remote control for a TV set, a user need elicited during market research may be “I don’t want to have to put my eyeglasses on when operating the remote control”. The firm may therefore decide to cope with this need by asserting the following requirement “button labels must be readable in 50 lux (dim light) by a user having a visual impairment of1diopters”. The requirement may then be translated into a specification such as “characters for button labels must be at least 6 mm tall and must be color-contrasted with their background”.

  2. 2.

    In the remote control example, it is up to the company to decide on the degree of readability of button labels with respect to illumination level and the degree of visual impairment, and to decide whether 6 mm tall and color-contrasted characters would adequately meet such requirement.

  3. 3.

    When defining character size for button labels, the designer is assuming that the remote control will be operated with physical buttons, which is only one of the many possible technical solutions allowing the required functions to be carried out (for instance, a remote control might be conceived with a touch screen-based interface).

  4. 4.

    For instance, suppose users of a high-end digital camera ask for a “reliable” product, where “reliability” implies a defined number of years before the product fails and has to be replaced. The manufacturer will probably view a connection between this need and the expected lifetime of the mechanical shutter, expressed in thousands of actuations. However, it will be possible to connect the requirement to a specification only if the manufacturer correctly defines the “mission profile” of the camera. In this simple example, the product brief might recite: “this camera is aimed at photography enthusiasts and professionals who need a stand-in product along to their main camera”. The manufacturer will therefore have to define the number of yearly shutter actuations that can be expected to be made by the customers belonging to these two segments.

  5. 5.

    User-centered design actually merges three different design approaches, and namely cooperative design, from the Scandinavian tradition of design of IT artifacts (Greenbaum and Kyng 1991), participatory design*, by the North American design school (Schuler and Namioka 1993), and contextual design*, that connects customer-centered design to the actual circumstances surrounding the “use situation” (Beyer and Holtzblatt 1997). User-centered design has become a formalized procedure through the ISO standard “Human-centred design for interactive systems” (ISO 9241–210, 2010).

  6. 6.

    For instance, one may define “Marie, 35-year old IT professional, mom of two children (4-year-old Susie and 2-year-old Jean). She is the wife of Robert, an airline pilot who is often away from home. They live in an apartment in the XV Arrondissement of Paris”. Diversity may be increased by adding to the family “Jeanne, Robert’s 70-year-old mother, who lives close to Robert and Marie and sometimes borrows their car to visit her friends during the weekend”.

  7. 7.

    For example, a scenario associated to Mary’s usage of the family car might be “Mary has collected her kids from school and now is in the grocery store’s parking lot, having to move items from the shopping cart to the trunk of the car”. This scenario can be further split into a best-case scenario such as “the sun is shining, the kids are happy and singing a song”, and the worst-case scenario “it’s raining heavily, the kids are crying and a phone call is coming from Singapore, where Robert is minutes away from taking-off for a long-haul flight”.

  8. 8.

    A distinction can be made between slips and mistakes, the former being errors in the execution of appropriate actions, the latter being errors associated to the very action to be taken. For instance, a slip occurs if a user that must press a button presses both the right one and—inadvertently—another one that is located too close. It would be a mistake if the user pressed the wrong button, having misunderstood the functions associated to it.

  9. 9.

    For instance, a self-steering car capable of keeping the same lane with unpredictable traffic could be currently difficult to develop from a technical and regulatory perspective. Current lane assist systems therefore augment drivers’ perception by providing feedback if the vehicle leaves the lane, for instance by making the steering wheel vibrate. Such feedback must of course be easy to interpret (e.g., a buzzer would not fully meet this criterion).

  10. 10.

    For instance, in the case of a public transport bus, the buyer is the purchasing office of a municipal transport authority, the users will be the employees, such as bus drivers and maintenance crews, and the direct beneficiaries are the passengers who buy tickets and ride the bus. External beneficiaries include citizens being affected by the emissions of the vehicle, or pedestrians who may be impacted by the bus—quite literally in fact—in case of an accident.

  11. 11.

    Referring to the public transport example, it is obvious to assume that—all the rest being equal —managers will prefer a bus that minimizes harmful emissions, even without being directly influenced by citizens. However, the importance that management will attach to this need may be altered if citizens actively cast such an influence through a citizens-rights association.

  12. 12.

    We have often observed salesmen interact with the product development team and ask “the features you are proposing for this product are cool, but how are we going to sell it?”.

  13. 13.

    For instance, a new bus that comes with a powerful but difficult-to-use IT-based fleet management system will probably not be adopted, because drivers will object to the procurement office and oppose the purchasing decision, or may simply avoid using it once it has been bought. Conversely, a system that is user-friendly but expensive will probably be vetoed by managers even if drivers push for its adoption, unless the latter are able to show that it will lead to financial benefits that out-weight the additional cost.

  14. 14.

    The bias emerges because product developers usually have a technical competence and an inclination for technology that is far superior to users’. Moreover, the target customer segment can be significantly different from the one that the product development team is used to consider (e.g., a team that has to develop a new car model for a geographical market in which the team has no prior experience).

  15. 15.

    It is probably appropriate to remind that these average ratings should not be computed on the entire sample used for market research, but only on the subset of respondents that can be associated to the customer segment the product is being targeted to.

  16. 16.

    For instance, in a passenger car it makes sense to specify maximum speed and acceleration, but not engine horsepower and torque, which would be the corresponding specifications at engine level.

  17. 17.

    For instance, a firm may set the price of a product by computing the annual savings or profits P it determines on a customer firm, and hypothesizing that customers will purchase it if its price PR ≤ P PBT, where PBT is a payback time.

  18. 18.

    For instance, parametric models can be based on rules such as “surface treatment X costs 22 €/m2”, or “with technology Y, the cost of producing parts like this is about 12 €/cm3 , adding 2 € per each geometric feature to be machined”.

  19. 19.

    For instance, a die used in an injection molding process will be a fixed cost up to a given production level. After that threshold is passed, the firm will have to invest in a second die.

  20. 20.

    For instance, if the cost driver used is direct labor hours, the firm will first compute the total annual cost of the overhead cost pool, TAC, and the total labor hours worked, TLH. It will then determine an “overhead rate” of TAC/TLH €/hour, which will be added to the direct costs of the product.

  21. 21.

    A difference is sometimes made between learning effects and curves (Wright 1936) and experience effects and curves (Henderson 1974), the former related to labor productivity and the latter to overall efficiency. The two phenomena follow mathematical models that are equivalent, and we will therefore consider the two interchangeably in the following discussion.

  22. 22.

    For a review of learning curve models, readers may refer to Anzanello and Fogliatto (2011).

  23. 23.

    When dealing with continuous improvement projects, it is customary to say that it is easy to “pick low-hanging fruit” at first. Following on this analogy, exponential learning would be as if fruit had already fallen on the ground, and one simply had to find it hidden in the grass.

  24. 24.

    For instance, an automotive manufacturer that is developing a passenger car may decide to incorporate components that are more expensive but more reliable than the ones that were previously used, and therefore decrease servicing requirements for the vehicle.

  25. 25.

    For example, if customers are unwilling to pay a higher price for a system that has very low maintenance costs, a producer might find it highly profitable to start leasing it. This is especially true if the producer is able to secure finance at low interest rates, while customers base their purchasing decisions on short-term criteria such as Payback Time.

References

  • Akao GH, Mazur Y (2003) The leading edge in QFD: past, present and future. Int J Qual Reliab Manage 20(1):20–35

    Article  Google Scholar 

  • Anzanello MJ, Fogliatto FS (2011) Learning curve models and applications: literature review and research directions. Int J Ind Ergon 41(5):573–583

    Article  Google Scholar 

  • Armstrong JS, Green KC (2007) Competitor-oriented objectives: the myth of market share. Int J Bus 12:117–136

    Google Scholar 

  • Beyer H, Holtzblatt K (1997) Contextual design: defining customer-centered systems. Morgan Kaufmann Publisher, San Francisco

    Google Scholar 

  • Bills AG (1934) General experimental psychology. Longmans psychology series, Longmans, Green and Co, New York

    Google Scholar 

  • Cantamessa M, Cascini G, Montagna F (2012) Design for innovation. In: Proceeding of the design conference, DESIGN 2012. Dubrovnik, Croatia

    Google Scholar 

  • Cantamessa M, Messina M, Montagna F (2013) Multi-stakeholder analysis of requirements to design real innovations. In: Proceeding of international conference on engineering design (ICED13). Seul, Korea

    Google Scholar 

  • Cascini G, Montagna F (2014) Modelling (pre-)design activities with a multi-stakeholder perspective. In: Taura T (ed) Principia Designae - Pre-Design, Design, and Post-Design. Springer, Tokyo

    Google Scholar 

  • Cristiano JJ, Liker JK, White CC III (2000) Customer-driven product development through quality function deployment in the U.S. and Japan. J Prod Innov Manage 17:286–308

    Article  Google Scholar 

  • Dar-El E (2000) Human learning: from learning curves to learning organizations. Kluwer Academic Publishers, Boston

    Book  Google Scholar 

  • Dean EB, Unal R (1992) Elements of designing for cost. In: Proceeding of aerospace design conference, AIAA 1992. Irvine, USA

    Google Scholar 

  • Dunk AS (2004) Product life cycle cost analysis: the impact of customer profiling, competitive advantage, and quality of IS information. Manage Account Res 15(4):401–414

    Article  Google Scholar 

  • Fabrycky WJ, Blanchard BS (1991) Life-cycle cost and economic analysis. Prentice Hall, Englewood Cliffs, NJ

    Google Scholar 

  • Franceschini F, Rossetto S (2002) QFD: an interactive algorithm for the prioritization of product’s technical characteristics. Integr Manuf Syst 13(1):69–75

    Article  Google Scholar 

  • Gilbert RJ, Lieberman MB (1987) Investment and coordination in oligopolistic industries. Rand J Econ 18:17–33

    Article  Google Scholar 

  • Greenbaum J, Kyng M (1991) Design at work—cooperative design of computer systems. Lawrence Erlbaum, Hillsdale

    Google Scholar 

  • Henderson BD (1974) The experience curve reviewed: the experience curve reviewed: why does it work? Boston consulting group. Perspectives, 128

    Google Scholar 

  • Henderson BD (1984) The logic of business strategy. Harper & Row, Cambridge

    Google Scholar 

  • ISO 9241-210 (2010) International organization for standardization. http://www.iso.org/iso/catalogue_detail.htm?csnumber=52075. Retrieved 12 Feb 2015

  • Li G, Rajagopalan S (1998) Process improvement. Qual Learn Eff Manage Sci 44(11):1517–1532

    MATH  Google Scholar 

  • Liao SS (1988) The learning curve: Wright’s model vs. Crawford’s model. Issues Account Edu 3:302–315

    Google Scholar 

  • Niazi A, Dia JS, Balabani S, Seneviratne L (2006) Product cost estimation: technique classification and methodology review. J Manuf Sci Eng 28:563–575

    Article  Google Scholar 

  • Norman DA (1998) The invisible computer. MIT Press, Cambridge

    Google Scholar 

  • Norman DA (2002) The design of everyday things. Basic Books Inc., New York

    Google Scholar 

  • Norman DA (2005) Emotional design: why we love (or hate) everyday things. Basic Books Inc., New York

    Google Scholar 

  • Norman DA, Draper SW (1986) User centered system design; new perspectives on human-computer interaction. Erlbaum Associates Inc., Hillsdale, USA

    Google Scholar 

  • Park J, Simpson TW (2005) Development of a production cost estimation framework to support product family design. Int J Prod Res 43(4):731–772

    Article  Google Scholar 

  • Ritter FE, Schooler LJ (2001) The learning curve. In: International encyclopedia of the social and behavioral sciences. Pergamon, Amsterdam, pp 8602–8605

    Google Scholar 

  • Schuler D, Namioka A (1993) Participatory design: principles and practices. Lawrence Erlbaum, Hillsdale, New York

    Google Scholar 

  • Teplitz CJ (1991) The learning curve deskbook: a reference guide to theory, calculations, and applications. Quorum Books, New York

    Google Scholar 

  • Tornberg K, Jamsen M, Paranko J (2002) Activity-based costing and process modeling for cost-conscious product design: a case study in a manufacturing company. Int J Prod Econ 79(1):75–82

    Article  Google Scholar 

  • Ulrich KT, Eppinger ED (1995) Product design and development. McGraw-Hill, New York

    Google Scholar 

  • Wright TP (1936) Factors affecting the cost of airplanes. J Aeronaut Sci 3(4):122–128

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Marco Cantamessa .

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer-Verlag London

About this chapter

Cite this chapter

Cantamessa, M., Montagna, F. (2016). Specifying the Product. In: Management of Innovation and Product Development. Springer, London. https://doi.org/10.1007/978-1-4471-6723-5_14

Download citation

  • DOI: https://doi.org/10.1007/978-1-4471-6723-5_14

  • Published:

  • Publisher Name: Springer, London

  • Print ISBN: 978-1-4471-6722-8

  • Online ISBN: 978-1-4471-6723-5

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics