28.11.2012 Views

Innovation and Ontologies

Innovation and Ontologies

Innovation and Ontologies

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

38 Roadmap for the Fuzzy Front End<br />

� For this thesis, a method50 is defined as orderly process or procedure, according to which<br />

particular activities are performed in order to achieve a given objective 51 .<br />

Although countless tools <strong>and</strong> methods are available, they are rarely implemented to support the<br />

innovation process 52 (Viertlboeck, 2000). In their study on adoption rates of best practices in new<br />

product development, Dooley <strong>and</strong> partners found that during front end it is only 36% (compared<br />

to 58% of adoption in the area of goals <strong>and</strong> strategy) (Dooley, Subra & Anderson, 2002).<br />

Especially SME adopt methods only rarely. This has been shown by studies on the relation<br />

between company size <strong>and</strong> deployment of methods (Bonaccorsi & Manfredi, 1999; Braun, 2005;<br />

Gausemeier, 2000).<br />

Especially methods which target only particular phases of the process (e.g. the Fuzzy Front End)<br />

are poorly implemented <strong>and</strong> rather considered as ‘supplementary’ by practitioners (Araujo et al.,<br />

1996; Ehrlenspiel, 2007; Gausemeier, 2000; Grabowski & Geiger, 1997; Meyer, 2000).<br />

Literature lists a number of reasons for this state which provide interesting insights going far<br />

beyond the scope of this subsection (Braun, 2005; Guenther, 1998; Hutterer, 2005; Meyer, 2000;<br />

Reinicke, 2004; Stetter, 2000; Viertlboeck, 2000). The most prominent reasons identified by<br />

academia are summarized in figure 16; attention is drawn particularly to the argument of the<br />

difficulty in selecting a method (bold box).<br />

figure 16 Reasons of poor use of methods to support innovation management<br />

50 Following IEEE Computer Society (1990), a methodology is “a comprehensive, integrated series of techniques or methods creating a general<br />

systems theory of how a class of thought-intensive work ought to be performed”, a method is a set of “orderly process or procedure used in<br />

the engineering of a product or performing a service” <strong>and</strong> a technique is “a technical <strong>and</strong> managerial procedure used to achieve a given<br />

objective”.<br />

51 In accordance with literature, my definition merges the IEEE nomenclature of method <strong>and</strong> technique, renouncing on the use of the latter (IEEE<br />

Computer Society, 1990). This reduces terminological confusion (Braun, 2005; Ehrlenspiel, 2007; Eversheim, 2003; Lindemann, 2007).<br />

52 An exception from the rule are integrated methods transferred from other fields of management, like project management or quality<br />

management. They have already been integrated as st<strong>and</strong>ard tools in the management of innovations (Ehrlenspiel, 2007; Eversheim, 2003).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!