(Original creator: jhuggins)
So why isn’t everyone innovating? Sometimes people simply get too comfortable with the status quo to try something new. Think how many users were reluctant to move from Windows 7, which admittedly let them do their job fine, to Windows 8, which some considered less perfect. But, once they were through the Windows 7/8 mourning curve, it was easy to change to Windows 10, with very quick emotional acceptance and significant benefits. Another major reason for not innovating is that people have more pressing things to do, and this is no doubt true. Throughout life, we often hear phrases like: “I’m too busy,” “I’ve got higher priorities,” and “We have to clear the backlog.” Within the IT function, some technical teams are big enough only to keep up with day-to-day maintenance, leaving no scope to craft new solutions or modernize legacy applications. Large organizations may also find they spend too much time and resources “keeping the lights on,” with little left for innovation.
A Catch 22 situation then arises, because by not moving forward, it becomes harder to deliver. This can lead to a failure to give the organization the business agility it needs. Another reason for failure to innovate at the right pace, is that for many organizations, it’s difficult to make innovation work. As discussed
in a recent article by Anderee Berengian, the innovation lab model has often failed. I’m going to elaborate on Berengian’s conclusion that “real innovation comes from outside your company,” as although that may be true for some, for the rest of us there is an alternative. In my first blog post I addressed the question: What comes first—innovation or agility?
In my next post I will look at 3 approaches to innovation for organizations.
This series is based on the paper: Agility and Innovation in Application and Mobile Development.
This page has no comments.