The biggest reward I get from working on IT projects is the opportunity to take new ideas and new strategies and piece them together into something that has never been done before.  Even when I'm not the one originating the new idea, I like helping other innovative people bring their ideas to the table.  I have ideas, dreams, and aspirations to help take my workplace to the next level of where it should be via innovative use of what I know best, information technology.  How could innovation and all these wonderful ideas I have in my head not be anything but a good thing for my organization?  A recent article in the Wall Street Journal answers just that question by saying that there are negatives for an organization that innovates too much.

In "How Innovation Can Be Too Much of a Good Thing", George Anders writes about how companies and business consultants are rediscovering that less innovation can produce better business results.  Companies that used to push the limit in efficiency are finding that they're "jamming too many new ideas into a product pipeline, without enough slack time to ensure that critical tasks stayed on schedule".

Similar insights have been standard wisdom on the manufacturing floor for decades. Factory managers learn about bottlenecks through the formal discipline of queuing theory. That teaches them to keep a little slack in the system to handle the unpredictable -- but inevitable -- crunch times.