Stakeholders in the Product Development
THE ROLE AND IMPORTANCE OF STAKEHOLDERS IN PRODUCT DEVELOPMENT
Patrik Nilsson and Björn Fagerström Engineering and Industrial Design Product and Production Development Chalmers University of Technology SE-412 96 Göteborg, Sweden
Abstract: Today, product development is a complex process: the designer continuously needs to consider new demands from different stakeholders and analyse how these demands can be fulfilled. Gathering and sharing stakeholder information is important, but is only beneficial if the information is used effectively. This is not a straightforward task. Information must be shared across design functions, and all involved need to develop a common understanding of the evolving design and the importance of particular stakeholders. This process relies to a large extent on the individual designer's intuition since there is lack of effective formal tools to support this. We argue in this paper the need for a holistic view, in order to manage all criteria, considering relevant perspectives and interests. To support this holistic view, we have developed a model that provides a common understanding for stakeholders involved, together with the requirements, functions and systems of the product being designed. This model will help facilitate the information sharing between members of extended design teams. Based on this, the model will support the decision-making process, and help the design team balance the interests of different stakeholders and the related functions. The model has been applied in an industrial case study. Key words: product modelling, stakeholders, requirements management, and information sharing.
Introduction and motivation
Product development is one of the most important activities in an industrial company. It is a key for future success. The ability to make competitive scenarios of future market demands and to continuously adapt to new demands is also a critical factor for success. Furthermore, it is well accepted that satisfied
Patrik Nilsson and Björn Fagerström Engineering and Industrial Design Product and Production Development Chalmers University of Technology SE-412 96 Göteborg, Sweden
Abstract: Today, product development is a complex process: the designer continuously needs to consider new demands from different stakeholders and analyse how these demands can be fulfilled. Gathering and sharing stakeholder information is important, but is only beneficial if the information is used effectively. This is not a straightforward task. Information must be shared across design functions, and all involved need to develop a common understanding of the evolving design and the importance of particular stakeholders. This process relies to a large extent on the individual designer's intuition since there is lack of effective formal tools to support this. We argue in this paper the need for a holistic view, in order to manage all criteria, considering relevant perspectives and interests. To support this holistic view, we have developed a model that provides a common understanding for stakeholders involved, together with the requirements, functions and systems of the product being designed. This model will help facilitate the information sharing between members of extended design teams. Based on this, the model will support the decision-making process, and help the design team balance the interests of different stakeholders and the related functions. The model has been applied in an industrial case study. Key words: product modelling, stakeholders, requirements management, and information sharing.
Introduction and motivation
Product development is one of the most important activities in an industrial company. It is a key for future success. The ability to make competitive scenarios of future market demands and to continuously adapt to new demands is also a critical factor for success. Furthermore, it is well accepted that satisfied
References: Akao, Y., (1990). Quality Function Deployment, QFD - Integrating Customer Requirements into Product Design. Productivity Press, Portland, USA. Ehrlenspiel, K. and Dylla, N., (1993). Experimental Investigation of Designers Thinking Methods and Design Procedures, Journal of Engineering Design, 4, 201-212. Fujita, K. and Nishikawa, T., (2001). Value-Adds Assessment Method for Product Development Across Life Stages Through Quality Function Deployment. Proceedings of ICED '01, Glasgow, UK. Harding, J. A., Popplewell, K., Fung, R. Y. K. and Omar, A. R., (2001). An Intelligent Information Framework Relating Customer Requirements and Product Characteristics. Computers in Industry, 44, 51-65. Isaksson, O., Fuxin, F., Jeppsson, P., Johansson, H., Katchaounov, T., Lindeblad, M., Haxue, M., Malmqvist, J., Meshihovic, S., Sutinen, K., Svensson, D., and Törlind, P., (2000). Trends in Product Modelling - an ENDREA Perspective. Proceedings of Produktmodeller, Linköping, Sweden. Nidamarthi, S., Chakrabarti, A. and Bligh, T. P., (1997). The Significance of Co-Evolving Requirements and Solutions in the Design Process. Proceeding of ICED '97, Tampere, Finland. NCR (2003). http://www.metis.no/ Pouloudi, A., (1999). Aspects of the Stakeholder Concept and their Implications for Information Systems Development. Proceedings of the 32nd Hawaii International Conference on Systems Sciences, IEEE Computer, Maui, Hawaii. Schachinger, P. and Johannesson, H., (2000). Computer Modelling of Design Specifications. Journal of Engineering Design, 11, 317-329. Sharp, H., Finkelstein, A. and Galal, G., (1999). Stakeholder Identification in the Requirement Engineering Process. Proceedings of Database and Expert Systems Applications, IEEE Computer Society Press, Florence, Italy. Wallace, G. W, (1995). Balancing Conflicting Stakeholder Requirements. Journal for Quality and Participation, 18, 84-89.