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 data science. Show all posts
Showing posts with label data science. Show all posts

Sunday, January 1, 2017

Whatever Happened to Knowledge Management?

Information Technology is a dynamic field, one often driven by buzzwords and fleeting trends. Sometimes these trends continue for decades, other times they fade somewhat quickly. One trend that experienced that fate seems to be Knowledge Management (KM). I recall first hearing about it in the early 2000’s and at that time it seemed to encompass several classes of subordinate technologies including but not limited to the following:
  • Document Management
  • Content Management
  • Search technology (various)
  • Business Intelligence (A.K.A. Decision Support or Analytics)
  • Metadata Management
  • Learning Management

It also tended to include more specialized tools such as knowledgebases or FAQ generators and it potentially seemed to include more integrative content-focused technologies such as Wikis. For a time KM seemed poised to also include a wide range of Semantic technologies as well. However, in the last two years or so in particular, the term Knowledge Management has seemingly dropped off of the map. I was wondering to myself why this may have happened and whether anything in particular had replaced it.
To be sure, there are a couple of related trends that have dominated the IT landscape in the past two or three years; the most significant of those being Data Science & Big Data. However, neither of these seems to fulfill the role KM was being groomed for over the previous decade. In fact, in some ways these more recent trends have become much less specific in regards to their expectations or scope (which has actually become a problem for both of them). This situation may actually help to explain what happened to Knowledge Management - perhaps the original scope was too expansive? But was it just a scope issue?
I want return again to the core or implied premise associated with Knowledge Management, that there ought to be some sort of enterprise-wide ability to help unify all of these knowledge related functions or processes and resources. The problem with this premise is related to the scope, in that there isn’t one product group of technologies associated with it, but rather a fairly large set of technologies – some of them not closely related at all other than in a philosophical sense – in other words that they could be construed as part of a larger knowledge ecosystem. So, we seem to be missing an industry impetus, but we also seem to be lacking any sort of agreed upon knowledge process or framework that would necessarily help to tie all of these diverse technologies together. This latter problem takes us deep into the heart of the larger philosophical question which KM seemed to be begging – e.g., what is the difference between information and knowledge? That isn’t an easy question to answer – and in some sense parallels my recent discussion on Artificial Intelligence versus Artificial Thought. In fact, AI could even be considered as part of KM depending on how you look at it.
So back to the tough question, what makes data or information become knowledge? Is that dependent on adding value to the data or information though specific types of processes or is it merely in the integration and analysis of such source data that the source transcends itself to become knowledge? Or is knowledge only something we can consider in a collective sense; with the sum total of all data assets being knowledge potential of some sort? These types of questions may have been raised during the years that KM was discussed actively but I think never properly answered.
You might have noticed from my initial list of related technologies that I seemed to have left out Data Management or Information Management. Either of those could potentially be considered to be part of a knowledge management framework – however the reason I left them out is that for those fields, there is a much better operational understanding of how those type of technologies work. In fact, the view from with one of these areas, Data Management overlaps quite a bit with some of what I’ve attributed to Knowledge Management (one need only look at the DMBOK to see this illustrated). Thus Data Management as a trend has continued (for decades now), primarily concerned with operational maintenance of a number of unrelated technologies without the implied necessity to integrate it all into something transcendent across the enterprise.
What if we did wish to settle the deeper question though, regarding the differing expectations between operational management of source data and knowledge exploitation? It is now 2017, are we in a position to define an integrative knowledge framework and if so what would the philosophical foundation consist of? Moreover, would coming up with this type of framework help to redeem the dimming trends of Big Data and Data Science? I think it’s worth trying to answer the question and also worth taking a shot at defining the missing knowledge framework. I will tackle both parts of this problem in two upcoming posts…
Copyright 2016, Stephen Lahanas

Sunday, December 4, 2016

Technology & Election 2016 part 3 – The Failure of Data Science?

The first reaction on election night, November 8th, 2016 was – what, how did that happen? The entire country and in fact the whole world was more or less shocked at the unexpected outcome. But why was it so unexpected? The top level answer to that is simply that nearly every major poll or projection turned out to be wrong. What kind of numbers are we talking about? For example, Nate Silver’s FiveThirtyEight blog projected Clinton to win by about 5% in the popular vote (with 71% certainty). If we drill down to the state polls we see that the projections showed all 3 key turnover states, Wisconsin, Michigan and Pennsylvania going to Clinton by 3 to 5% in each contest. This is significant because many of these projections (and blogs like FiveThirtyEight) were using aggregates of dozens or hundreds of polls, not just one or a handful and the differences exceeded the margin of error.
Let’s step back for a moment and talk about the typical role that Data Science plays in the election process today. This role encompasses several well-known and some lessor known functions, including:
  • Predictive polling
  • Exit polling
  • Predictive modeling
  • Vote targeting (which facilitates a sort of CRM for campaign marketing as well as Get Out the Vote efforts)
There’s nothing new about polling, it’s been around for a long time. In fact, the last time there was a collective shock like this year’s outcome was in 1948, when the polls had predicted Dewey would win (by 50 to 45% - but Truman won by 50% to 45%). Polls have improved since then and of course, now we have the benefit of the latest data technology as well as 70 years of added experience, so how did nearly every major poll get it wrong this year? There are some theories; they include the following:
  1. A lot of people changed their minds at the last moment and weren’t particularly firm in their previous opinions.
  2. The Russians did it.
  3. Many polls were not properly targeting prospective voters for their models.
  4. Many people who had said they were voting for Clinton didn’t turn out to vote at all (e.g. the lack of enthusiasm)
  5. The poll numbers for the 3rd party candidates may have been inflated, and when it came to election day these candidates received far fewer votes that had been predicted (the implication being they went ahead and voted for one of the main candidates with Trump being the main beneficiary).
To be honest, we may never have a fully satisfactory answer for what happened in the 2016 election. It is likely that we’ve never had a race where both of the main candidates were universally unpopular and that kind of situation might never happen again (and there’s no telling how that may have impacted the polling results). How do we move forward then? Did technology, did Data Science fail us in 2016? Maybe, but probably not. What we witnessed however is that technology is only as good as our ability to apply it. If situations become more dynamic, complex within a relatively short window, do we stick with what we know or do we adjust our models or practices?
I’d like to step back for a moment here and ask a larger question. Do we really want ironclad predictions before elections in the first place? Before the big upset on election night, many pundits were talking about the lessons learned from the 1980 election where results from the East Coast encouraged West Coast voters to stay home thinking their votes didn’t really count. Because of that, the FEC passed a rule prohibiting networks from announcing winners before certain polls close. Don’t polls predicting a sure outcome before an election have a similar chilling effect? This year for example, how many voters may have stayed home because while they weren’t terribly enthused about Clinton, thought she would win? That’s a hard question to ask because people who don’t show up to vote can’t be interviewed in exit polls (or at least typically aren’t interviewed as part of the election post mortem).
What can we do in Future to avoid getting surprised?
I think it is important that in coming up with suggestions here, we need to weigh the relative value of using a particular solution with the potential impacts of using it. In other words, if we view predictive polling as a relativistic activity (e.g. a bit like Heisenberg’s principle in that taking a measure can influence the outcome), then we might conclude that the highest value of such predictive polls relative to possible harm might end several weeks before the election. How then could we be assured that elections are honest, that public sentiment is in fact aligned with election results? Well, that can still come through exit polling – polls taken of actual voters on election day and in addition, sentiment polls taken the day after the election of potential voters who didn’t vote (something that doesn’t typically happen now).  
Suggestion – Place a moratorium on predictive polls at least 2 weeks prior to election day and preferably 4 weeks prior. Why would this work? Here are few potential benefits of doing it:
  • This has the immediate effect of not making the election as much of a horse race and more of a contest of ideas.
  • It has at least the potential of driving up voter participation – a lot can happen in 4 weeks, people can vote based on their opinions and do a little less hedging in making their decisions.
  • It helps to combat Group-think (people swarming to the anticipated victor or becoming despondent about their own preferred candidates)
  • It certainly eliminates the main source of any potential surprise.
  • It may encourage candidates to take a more expansive view towards courting voters, recent trends have focused way too much attention on potential swing states and districts.
As you can tell, this and potentially other suggestions may have relatively little to do with Data Science itself, but have everything to do with how we apply it to given situations. I don’t believe the technology failed us here, I think we failed to recognize how much it already influences election outcomes. In my next post in this series, I’ll talk a bit more about Get Out the Vote (GOTV), politics as demographics and how technology has been and will be used to manage campaigns.

Copyright 2016, Stephen Lahanas