Product Development

During the past couple of years, Spectre Marine has evolved not only in teaching methodology competence and boat conductance. The amount of experiences from different kind of boats increases exponentially with each and every individual being a part of the Spectre organization. A highly differentiated team with such extreme diversity in individual background generates aspects of product development probably unique on the marine arena.

Environmental dynamics

Spectre Product Development (SPD) has a standardized way of working in order to provide time and cost efficient results. Where in the process Spectre is to be involved is of course a decision made by the client. Most often, it starts as a question from a client such as “what do You think about this?”. This, however, most often results in a counter-question manner, since the question itselft cannot be answered in a way simply implying a product to be good or bad. There is a large quantity of factors involved in order to reveal the complete dynamics of how to analyze the product. When all questions are answered, the issue regarding “good or bad” most probably still cannot be answered by one single person. The idea with SPD is that relevant persons are involved in the product development, depending on results of the product usage questionnaire. An ambulance boat should not involve only engineers, but rather people from the organization with experience of ambulance operations and emergency medicine.

Why employ Spectre?

One can of course ask the most relevant question of them all: “Why should we employ Spectre? We can do this better our selves since we are the one with the knowledge about our product. How can they provide useful information?” This is a highly relevant point of view. However, it lacks in taking important issues into consideration:

Being blind to flaws: After have been working intensly with a product for several years, it is completely natural to be blind for possible flaws. The conflict arising when designers, engineers and manufacturers tries to stay within deadlines and budgets, most often the most simple and cheapest solution is chosen, perhaps failing to acknowledge that the user possibly can suffer from this during usage. This bridge is overcome by the totally independent and unaffected position of Spectre.

Experts vs novice: The one designing the products are most often the very experts of that exact arena. However, this can very often create problems in terms of who is supposed to use the product. An expert might say that a product is bad, in terms of his or hers way of working. This very seldom implies to a novice user, however listening to the “expert advice”. This bridge is overcome by the diversity of the Spectre Organization.

Revenue vs research: Spectre withholds expertise from engineering and scientific levels. Combining theory and practice knowledge and testing of a product enables the client to create revenue from the PD outcome, in terms of increased marketing value. By just saying “this product has become better” is not affirmation enough. Spectre engineers have the tools needed to ensure that the outcome will have quantifiable improvements.