Originally Posted by
Scott Monash
What a great link, thanks for that Bob.
I think they hit the nail on the head, with their creativity and innovation model.
This framework neatly accounts for the similarity and difference between useful and not useful innovative ideas, and explains why you can't have one without the other.
This is why I think that innovation should not be rewarded for its own sake, particularly at the FSAE level.
Successful innovation should be its own reward.
Take inspiration from the best ideas or solutions around, explore them, understand them and their weaknesses, and then if (and only if) you see potential benefits to innovating, then do so.
Do not think that different is always better, its not.
Do not expect a hand out just because something is different, particularly if you cant demonstrate why it needed to be.
This kind of thinking is probably an artefact of the "copying culture" that the article discusses and the workshop tries to break down, as a key inhibitor to the cooperative design process.
Have a health amount of respect for what has come before, you are not the first engineer to walk the earth.
Teams that state that their primary mission in FSAE is to "be the most innovative" scare the hell out of me.
Completely abandoning convention invites multi-faceted disaster.
In my opinion, the path to success lies in maintaining a delicate and measured tension between convention and innovation.
And not fooling yourself.
We are engineers, let the data be your guide.