
We worry a lot about Moore’s Law running out of gas right about now. Now comes former AMD CEO Hector Ruiz with this piece on Harvard Business Review’s blog: “There, however, is a possible “off-ramp” to Moore’s Law that offers [...]
LOS ANGELES–So often, we get ahead of ourselves a consuming public, especially when it comes to technology innovation. Take power generation and smart-grid management. We know that electronics that drive enormous efficiency gains on the grid. After all, our smart [...]
By Malcolm Fuller, contributing writer SANTA CLARA, Calif. – You wake up in your chilly San Francisco apartment (or any chilly place for that matter), and your first instinct is not to crank up the thermostat several notches (too expensive!). [...]
By Brian Fuller We’ve written all lot about the quickening pace of innovation in automotive electronics design. And you’ll recall the centerpiece of the first part of the Drive for Innovation was an all-electric Chevy Volt, which took us around [...]
4 April 2012
I share innovation blog posts that I come across because not only is that part of what this site is about, but I'm also interested in learning more about organizational dynamics and improving productivity. The intersection of technology and human frailty, if you will, is ceaselessly fascinating to me.
So I came across "Five Key Innovation Questions to Ask" by Robert Brands. (By the way, what a great last name if you're in the marketing-consultant business, which Brands is; there's a "Who's on first?" joke here somewhere).
His aren't the questions to ask. And even if they were, there's no organization in the world that has trained its employees to be so disciplined as to run through such a list on a regular or serendipitous basis, to build them into its DNA if you will. 
That said, there is a question you need to ask. And this assumes that your organization has an average distribution of leaders, followers and, the really important types, the nut-jobs. (Let's be honest: really brilliant engineers live just on the hairy edge of insanity; you know who they are, even though they often don't know who they are).
So given that your organization is average, here's the one question you need to ask:
"Is the idea so simple that it will never happen?"
Ideas that get that reaction are among the most innovative you'll come across. And they get that reaction because humans know in their heart of hearts that the most elegant solution is the simplest. And since it's the simplest, we dismiss it because "real innovation" has to be hard; it has to come down from a mountaintop, accompanied by thunder, lightning and a ringing chorus of cherubs.
"Real" innovation needs to over-turn the apple cart, upset the dominant corporate paradigm, cause walls to catch fire and stultified careers to free fall into darkness. "Real innovation" comes after toil because that's what we're supposed to do, right? That's the Protestant work ethic writ large.
But real innovation is never (if you could ask it) so pretentious. Real innovation is simple and accessible because it understands that everything is evolutionary; nothing is revolutionary.
Real innovation is looking at a music score and deciding that instead of ending with a dominant chord, maybe we should end with a seventh or a minor chord. Real innovation puts two buttons on something, not 10. Real innovation doesn't look at the boulder in the middle of the stream and explore how to deconstruct the boulder; it finds its way around. Real innovation zigs when everybody zags.
The sad thing is that, in the workplace, we have this reaction all the time to clever ideas. It's prompted by a cynicism that was born the second or third time you saw an elegant solution, an innovative solution, dismissed as too simple.
But maybe if we embrace the simple, we'll push ahead a little faster and more efficiently.
CC Vandorne April 18, 2012 at 12:48 pm
Scott Adams speaks.
*Required

TK April 6, 2012 at 4:20 pm
My take on all of this is that often times in engineering organizations, some 'architect' type (the more experienced the worse), comes up with some plan on what to do based on lessons he learnt —- that he of course wont share the genesis of, lest it become obvious that he had learnt the wrong lesson. The troops then are required to implement that, and managers are required to issue bromides to egg the troops on, and make it sound like the project is a crusade, rather than one of the few money making devices the VP can think of.
Most good troopers over time train themselves to not step back and look at the abject inaneness of what they are doing —- because they are scared that they'll get demotivated and stop working and incur the wrath of said bromide issuing managers. The ones who do call BS have options —- either because they are young enough (in which case they're just happy that somebody 'senior' listened to them), or are confident that when they incur said wrath they have lined up some other job that's not as inane.