Why have certain IT issues persisted despite shortening innovation cycles?


2.9k views1 Upvote15 Comments

Head of Security and Compliance in Software, 51 - 200 employees
Data is not static. The data that we are generating is exponentially increasing and as new problems are introduced, everything gets more complex. Another issue is interoperability. Back when we were building the systems, or at least the network protocols, we always had interoperability testing. Nearly all the players had to run against this test to make sure that they qualify to be able to sell. That's completely gone now and we are not building the protocols and hand shaking to make sure that we all agree to some common standard.
CIO, 5,001 - 10,000 employees
In IT and business, we continue to solve the same problems; we never get to a place where we can say something is done and move on to the next thing. But when you think about the pace at which consumer applications are built today, we have made significant progress. Otherwise, we wouldn't see that velocity of change. Consumer applications are now composed from elements of Amazon and the cloud where you don't have tech debt to deal with, yet that hasn't helped business to completely arrive around IT’s core tech stack, such as ERP or CRM. It feels more like activity than progress sometimes.
1 Reply
CEO in Services (non-Government), Self-employed

I would say the same thing about the cloud: It's refactoring and re-architecting, and it's taking me years to get there. I won’t be better off in the end because when my business model undergoes dramatic change, it won't necessarily be the best place to keep my data for outage or security reasons. Another reason is that the cloud itself has not evolved.

Director Of Technology in Education, 51 - 200 employees
Certain IT issues will always exist as that is the nature of the work.  Certain jobs are circular and nature and must be re-done regularly.

Certain IT issues may be persisting due to hardware issues or software bugs.   And, of course upgrading doesn’t solve all issues automatically.  And some IT issues are caused by shadow IT or staff turnover.

There are other issues that a shortened IT innovation cycle doesn’t fix…. but that just means we need another trip around the innovation cycle.
Vice President Information Technology in Finance (non-banking), 201 - 500 employees
Certain IT will continue to exist due to disruptive pace of Technological innovations.  Orgs. which were shying or concerned of the data security on cloud have gained enough confidence and gradually adapting cloud technologies to quickens their innovation journey but the pace at which these technologies are advancing is really disruptive and therefore leading to more and more adopting of it. 
Vice President Information Technology in Finance (non-banking), 201 - 500 employees
Certain IT issues will continue to exist due to disruptive pace of Technological innovations.  Orgs. which were shying or concerned of the data security on cloud have gained enough confidence and gradually adapting cloud technologies to quickens their innovation journey but the pace at which these technologies are advancing is really disruptive and therefore leading to more and more adoptions of it.
CTO in Services (non-Government), 51 - 200 employees
A really interesting question - I would suggest the cause is because those persistent issues are rooted in choices made when developing fundamental technologies. Not always mistakes, they are often trade-offs. If a tech is developed, and a change is needed before any subsequent tech is built ontop it is often a straightforward fix. But once other libraries start importing your library, or software is coded for your hardware, or your protocol reaches wide adoption, etc any change has an enormous flow on effect rendering the difficulty of any changes from difficult to impossible. This generally means the fix requires either enough increasing impetus, or combined with other issues to drive a incompatible rebuild or fork of the underlying tech.
Director - IT, Enterprise Services and Value Management in Software, 10,001+ employees
There are two ways to look into this interesting question. One, the issue is seen as continuous as every improvement or innovation leads to enhancement yet enables possibilities of new set of bugs, expectations, and issues. Two, it is true that some issues persist a while we have advanced in many aspects, an example, video conferencing is never 100% sure, I bet it will not meet six sigma criteria. Yet, the reason it probably remains around is many unknown and the real impact of these is lower than the effort or cost it may take to resolve. And hence, in the corporate world, the focus is on the next big thing as against the last seen (and ignorable) issue.
CIO in Education, 1,001 - 5,000 employees
Innovation is not the magic to resolve IT issues. There will always be IT issues as the demands continuously change and new solutions may require changes to be done and sometimes these are only discovered after implementation. The environments change and this itself brings its own issues too.
Director of Enterprise Technology Advisory in Software, 10,001+ employees
Perhaps a to wider scope?  Innovation isn't problem management?  

When launching a new innovation initiative, be clear on what you are trying to solve for so that underlying things like technical debt, which may be causing specific issues in the environment are addressed.
Director of software engineering in Software, 201 - 500 employees
Because people stay the same. Change requires people to change their thinking. And most people are unwilling to do this.

Then there's the fact that people can only move/work so fast. The speed of your people has always to be kept in mind. 

Content you might like

Community User in Software, 11 - 50 employees

organized a virtual escape room via https://www.puzzlebreak.us/ - even though his team lost it was a fun subtitue for just a "virtual happy hour"
10
Read More Comments
8.7k views26 Upvotes59 Comments