Cyber Security Predictions for 2017

2016 was a big year in the annals of Cyber Security, and 2017 promises to eclipse it.

Creating an Enterprise Data Strategy

An introduction to the process of developing comprehensive strategies for enterprise data manangement and exploitation.

A Framework for Evolutionary Artificial Thought

Let’s start at the beginning – what does this or any such “Framework” buy us?

The Innovation Dilemma

What things actually promote or discourage innovation? We'll examine a few in this post...

Digitial Transformation, Defined

Digitial Transformation is a hot topic in IT and big money maker for consultants - but what does it really mean?.

Showing posts with label Hype Cycle. Show all posts
Showing posts with label Hype Cycle. Show all posts

Saturday, September 6, 2014

How IT Hype Inhibits Technology Innovation

There are many unique characteristics connected to the IT industry, some of them are more associated with pure-play IT vendors but others seem to pervade most all organizations which utilize IT in any significant manner. One of the strangest of these characteristics is the obsession with buzzword Hype. For most people this is symbolized through the development and dissemination of Gartner's famous Hype Cycle diagrams. However, the Hype obsession existed before the Hype Cycle ever did and doesn't explain the phenomenon in a satisfactory manner.

So, what's wrong with Hype? Isn't it just a harmless offshoot of public relations or perhaps just some benign manifestation of mass psychology? Perhaps some of our readers here are old enough to remember the endless silly fads of the 1970's which included Pet Rocks and Mood Rings. Did buying these worthless trinkets in any way negatively impact our later lives - probably not. What these harmless trends did perhaps achieve though was a sort of conditioning that might have pre-disposed the vast majority of us to assign more attention to trends then they might otherwise merit.


Pet Rocks were definitely low tech - but represented a hype-generated trend none-the-less

Now without diving into the implications of psychological theory in regards to conditioning and behavior, it is does seem as though much of what we see or talk about is driven by various Hype cycles. This occurs in entertainment, in business, in food & dining - in nearly every aspect of popular culture and remarkably it also affects science and technology. What represents Buzz in the Scientific community over recent years? Well, how about the Stem Cells, The God Particle and Fractals (or Fibonacci numbers) to name a few.

Getting back to Information Tech - how are we influenced by fads, trends and Buzzword Hype? Well, let's attempt a definition here first...

Buzzword Hype - This represents a unique form of public relations wherein somewhat complex concepts are crammed into a single buzzword (although Buzzwords can technically include several words in them - Master Data Management has three, Big Data has two). While this phenomenon is not limited to IT - it is the most prevalent form of Hype in the technology arena.

So, if an acronym is a mnemonic for a complex term (MDM for Master Data Management), the term itself is a mnemonic for the complex concept that everyone already understands, right? Wait a minute, perhaps we've discovered the first problem; how many people actually understand these terms? Furthermore, how many people are actually concerned with learning these terms?

Let's hone in on one of the biggest Buzzword Hype examples of the last few years - Big Data (we've touched upon this topic before in Technovation Talks). How many people actually have a comprehensive knowledge of what this represents? or even have the same expectations or knowledge about it? Is Big Data just the Hadoop distributed fault tolerant file system, it is the lack of SQL and relational structure, is it the high capacity or throughput or is it some combination of these elements and much, much more. Even more importantly, is Big Data even something that can be neatly defined as one standard solution? All good questions, none of which are typically addressed in the core Hype surrounding the buzzword.

The buzzword hype for Big Data seems to imply more, better, faster, bigger with very little consideration as to how that might happen or what the eventual impacts would be. The term itself becomes its own justification - if everyone is talking about doing it and beginning to do it - why shouldn't we, right? And by the way, what is it again?

Let's step back a moment and try to classify what the core problems associated with the Hype Cycle are:

  • These buzzwords actually drive business decisions, regardless of the level of education or understanding associated with them.
  • There is an undercurrent of peer pressure that tends to 'force' people into making those decisions - decisions they weren't ready to make (because they didn't have time to evaluate the situation properly).
  • The hype tends to drown out most other types of discussions associated either with the technology in question or the real trends of what's happening across most enterprises. And I characterize these as 'real' because they represent common challenges which aren't necessarily product-driven (thus not good candidates for hype).
  • Premature adoption based on hype cycles often has the opposite effect on a particular technology area - it stifles it as too much bad word-of-mouth feedback circulates and what might otherwise be a promising field of practice languishes as a result (E-learning is the best of example of this I can think of).

How does all of this impact or otherwise inhibit Innovation? Well, here are some things to think about:

  • Some Hype Trends are not in fact very innovative, yet if everyone is doing it - then folks trying to introduce truly innovative techniques or products may be drowned out or suppressed. 
  • Most Hype Cycles tend to pose the key buzzword focus area as a "silver bullet" solution - as those of us who have practiced IT for a while can all attest to, there are few if any actual Silver Bullet solutions. Similar the Heisenberg Principle (and we're not referring to Breaking Bad here), introduction of a new element impacts the existing elements in unanticipated ways (well, this isn't an exact analogy to the Heisenberg Principle but it's close enough). The whole of IT might be viewed as "Magic Happens Here" by outsiders but inside we know there is a constant struggle to impose order over chaos - silver bullets are often disruptive. Yes, that's good but not if you don't understand the nature of the disruption before you go whole hog (so to speak).
  • Hype & Buzzwords tend to make people think situations are simpler than they really are, and in some senses actually discourage the necessary analysis that should be occurring when adopting new technology. Innovation cannot be sustained when and where it becomes too expensive to manage.   


We will ever escape the grip of unreasoning Hype in IT? Will our lives be forever ruled by an unrelenting cascade of product focused buzzwords? Who knows - IT is still in its infancy and unlike most other professions we have the opportunity to reinvent ourselves on an almost continual basis - so anything is possible.



Copyright 2014, Stephen Lahanas


#Semantech
#StephenLahanas
#TechnovationTalks

Wednesday, October 17, 2012

Whatever happened to SOA?

Not too long ago Service Oriented Architecture (SOA) was the hottest IT trend around, at least if measured by the sheer amount of attention or hype that was associated with it. The fate of SOA is interesting for a number of reasons:
  • It helps to illustrate the nature of Hype Cycles in IT and how they influence both industry and individual enterprises.
  • It helps to provide context for why Cloud solutions have now become the "killer solution" (it can't be described as an app) that most folks are examining today.
  • It is an interesting case study in regards to the difference between product-based Hype-Cycles and architecture or standards based hype cycles.
So what did happen to SOA? Strictly speaking, it's still around and going strong, however it is no longer at the top of the 'must have' or 'must do' lists in most IT departments these days. Many SOA initiatives took the bridge to nowhere or have been merged into newer or perhaps more specific enterprise goals and objectives. Before we go any further though, let's recap what SOA represents:
  1. SOA is not limited to one product or product family.
  2. SOA encompasses both capabilities and process.
  3. SOA is very focused on a key set of (mostly W3C) interoperability standards, notably SOAP, XML, WSDL and UDDI.
  4. SOA is not merely a solution but also a solution strategy and architectural approach. This last point is both critical and very subtle. 
  5. SOA has an systems integration focus, not merely a software development one.
This diagram illustrates a number of the Use Cases associated with SOA Adoption
 Each of the last five points is important and several of them are relatively complex issues. Essentially, taken together they tend to imply that anyone wishing to deploy SOA in a significant way would in effect be attempting some form of enterprise-wide transformation. That's a big deal regardless of the technology or technological paradigm targeted in the transformation. Change is never easy - it's less so when dealing with an entirely new way of managing your IT portfolio. These are some of the reasons that SOA is not the driving force in industry it was just four years. So, let's look at what did happen with SOA:
  • SOA was and SOA is hard. There's no silver bullet solution - all options require a lot of work and some risk.
  • SOA initiatives usually become Systems Integration exercises. Many providers or organizations without that systems integrations background attempted SOA solutions and quickly realized it's a skill that takes years to develop (both personally and organizationally).
  • There's more than one way to do SOA - in fact there's quite a few ways. This implies a wide array of possible tools or software options. Navigating those decisions is confusing to say the least and since this happens up front it often short circuits projects before they ever get off of the ground. There's not one piece of software associated with a proto-typical SOA solution.  
  • Often times key elements of SOA infrastructure are not implemented as part of an initiative. Common examples of this include failure to deploy a SOA Registry or Governance paradigm. This tends to limit the effectiveness of the solution and eventually restricts the scope of the entire solution.
One of the reasons people were initially enthused about SOA was that it seemed to represent an easy path to bypass many of the ills associated with the ad hoc heterogeneous sprawl that had become the typical IT enterprise by the mid-2000's. That initial assessment was a misconception, but so too are similar assessments being made now about "Cloud Computing" and "Big Data." Behind the Hype and the marketing buzz, there are certain underlying problems that all IT trends are focused on resolving. More often than not however, no single trend is positioned to solve the challenges alone. We will talk more about Cloud Computing, Big Data and SOA in future posts and presentations. Also be sure to check out our Technovation Glossary page.


Copyright 2012, Semantech Inc. All rights Reserved