These areas, through necessity, teach sound innovation practices.
In engineering, the necessities are to try to avoid killing or hurting people and also to make sure things work before spending a bunch of money on building a full scale version, having learned the lesson in past experience that you rarely know what you don’t know ahead of time.
So, before building a bridge with a new design just from a set of plans, it is often built on smaller scales and put to the test in the real world to find out what they don’t know.
I remember in one of my engineering classes seeing the footage of the Tacoma Narrows bridge collapse to make this exact point. That stuck in my head and I think of it often. The bridge itself seemed good enough on paper, but in the real world it didn’t play well with crosswinds. It’s not obvious. Hey, make sure the crosswinds don’t start vibrating the the bridge at a resonant frequency!
In cycling, the necessity is that you learn to avoid making untested changes to your bike, clothing, training, sleep cycle and nutrition right before some big event, because it can cause an unintended outcome that spoils your big event.
You also learn that it’s good to do some course recon work and go for a shakeout ride or two in the area and on the course, just so you know the lay of the land and if your chosen set up will work.
If you want to buy a new pair of cycling shoes, you try to avoid making the first ride in them be the big event. You also don’t throw out your old shoes until you determine if the new shoes will work.
So, you try to give yourself a couple weeks worth of rides in the new shoes to see if they fit right and don’t cause rubbing or blisters. We ‘test’ them out. Then when they past the test, we’ll use them in the big event and feel comfortable throwing the old shoes out.
Every now and again we violate that rule and are punished and reminded of why we have that rule. I had a friend violate it and buy new shoes before a long, multi-day event two years ago and he was kicking himself the whole way because the new shoes ended up being too tight and made his feet hurt and made the event less enjoyable for him.
For people with these backgrounds, this type of stuff becomes second nature.
But for some reason, these lessons are lost on the folks who innovate at many companies.
They don’t think it’s necessary to put something to the test before rolling out. In the past few years, I’ve seen companies roll out a big new systems and big new products with disastrous results because they didn’t test them out.
The disasters could have been easily avoided by testing them out and finding the bugs and fixing them.
But, in all cases, the folks who made the roll decision were overconfident, just like my friend with his new shoes for the bike ride.
They had not learned the lesson that they don’t know what they don’t know.
Sadly, I’ve seen the backed of these flops, and they resist that lesson. They think they can avoid the disaster next time simply by thinking harder to identify all possibilities, rather than simply putting it to the test.
They almost take offense to the idea that they should put something to the test.
That part I haven’t figure out, yet. How do engineers and cyclists seem to learn pretty quickly that the best way to find out what they don’t know is to test something in the real world, but these folks continue to believe they can outsmart the real world?
It’s a possibility that engineering and cycling end up selecting for folks who are able to learn that lesson and folks that don’t end up going onto other things.