My computer is having a spaz attack – discuss!
I was working from home yesterday. My daughter stormed into my office:
- “Dad, I need to use your computer”
- “Why?”
- “I need to print some pictures”
- “Why don’t you use your laptop?”
- “It’s not working…”
- “What do you mean ‘it’s not working’? What is not working?”
- “I don’t know, it’s having a spaz attack”
I have long given up any pretence of understanding the etymology of the teenage language. In a language where “fit” means handsome and “sick” means nice, I have no hope in tracing the origins of “spaz”. I can only guess that it stems from “spastic” or “spasmodic”. I have learned that “spaz” is an abbreviation of “spasticated” (as in “it’s gone all spasticated…”), which leaves me none the wiser. I digress… Whatever the origin of the term, in my thirty years of troubleshooting computers I’m pretty sure that epileptic seizures where never on the symptom list…
- “Why didn’t you bring it down so that I can sort it out?”
- “I don’t have time for that. All I need is to print three pictures for my artwork.”
I yielded, even though every fibre in my body was screaming for answers and detail. There is no such thing as “Not working”.
I saw a huge IT generation gap issue here: When I started working with computers, somewhere in the prehistoric early ‘80s, you needed to understand computers to use them. I won’t bore you with stories of bootstrapping from paper tapes and disk drives that needed to be shutdown in a certain way because the heads would physically crash on the disk, but to a whole generation of us, “not working” immediately triggers a root cause analysis mechanism in our brain: Power, motherboard, fans, memory, disks, peripherals, operating system, drivers, software, network connection, telephone line, etc. By process of elimination, ONE of them is not working, but not usually the whole. And part of “using” the computer was to understand which part is not working and how to get it to work. Because, frankly, if we didn’t figure it out there wasn’t anyone else around that could.
My daughter is a typical business user: To her, the computer is a means to an end. Her laptop is a tool. She has no interest to find out which part isn’t working or to make any attempt to fix it. If she can’t go to Google and print the three pictures she needs, when she needs them, it renders the tool useless. “The computer is not working”, does not mean the physical machine is broken, it means “my tool doesn’t do what I need it to do”. Why and how is irrelevant.
A couple of weeks ago, when her laptop refused to start altogether (hard disk index corruption problem, a simple CHKDSK fix), her only concern was if she would lose the book she has been writing for the last six months – cue the usual backup lecture from dad… She doesn’t want to learn how to do backups, she wants her book to be there.
Interestingly, the same gap exists between most business user communities and IT. IT will worry about which part of the infrastructure is failing, which vendor to contact, which component needs tweaking, which performance bottleneck requires more resources at peak time. For the users it’s black & white: “The system” is working, or it’s not.
Coincidentally, I saw another example of the same gap earlier in the day, yesterday, when I went to my dentist. After paying for my check-up, and after several failed attempts, the receptionist informed me that they could not give me a receipt because the printer is broken and they were waiting for the engineer to arrive. I could see the aforementioned printer from where I was standing: It was flashing a red light with a message that it had a paper-jam. There were four people at reception, and various dentist assistants that paraded through. Not one of them had either the skills or the inclination to clear the jam.
I felt envy towards the engineer – Money for nothing!
I also resisted the temptation to say “Can I try and sort it for you?”, but it was hard! I agreed to have my receipts posted in the mail, instead.
Data Governance is not about Data
Those that have been reading my blogs for a while, know that I have great objections to the term “unstructured” and the way it has been used to describe all information that is text-based, image-based or any other format that does not tend to fit directly into the rows and columns of a relational database. None of that “unstructured” content exists without structure inside and around it, and databases have long moved on from storing just “rows and columns”.
A conversation last night with IDC Analyst @AlysWoodward, (at the excellent IDC EMEA Software Summit in London), prompted me to think about another problem that distinction has created:
Calling that content “unstructured” is a convention invented by analysts and vendors, to distinguish between the set of tools required to manage that content and the tools that service the world of databases and BI tools. The technologies used to manage text-based content and digital media need to be different, as they have a lot of different issues to address.
It has also been a great way of alerting the business users that while they are painstakingly taking care of their precious transactional data, that only represents a about 20% of their IT estate, while all this other “stuff” keeps accumulating uncontrolled and unmanaged on servers, C: drives, email servers, etc.
These artificial distinctions however, are only relevant when you consider HOW you manage that information, the tools and the technologies. These distinctions are not relevant when you are trying to understand WHAT business information you hold and need as an organisation, WHY you are holding it and what policies need to be applied to it, or WHO is responsible for it: The scanned image of an invoice is subject to the same retention requirements as the row-level data extracted from it; the Data Protection act does not give a different privacy rules for emails and for client records kept in your CRM system; a regulatory audit scrutinising executive decisions will not care if the decisions are backed by a policy document or a BI query; you can’t have a different group of people deciding on security policies for confidential information on your ERP system and another group for the product manufacturing instructions held in a document library.
“Data Governance” (or “Information Governance”, or “Content Governance”, I’ve seen all of these terms used) is not an IT discipline, it’s a business requirement. It does not only apply to the data held in databases and data warehouses, it applies to all information you manage as an organisation, regardless of location, format, origin or medium. As a business, you need to understand what information you hold about your customers, your suppliers, your products, your employees. You need to understand where that information lives and where you would go to find it. You need to understand who is responsible for managing it, making sure it’s secure and who has the right to decide that you can get rid of it. Regardless if that information lives in a “structured” or “unstructured” medium, and regardless of the tools or technologies that are needed to implement these governance policies.
The Data Governance Council, has developed an excellent maturity model for understanding how far your organisation has moved in understanding and implementing Data Governance. It covers areas such as “Stewardship”, “Policy”, “Data Risk management”, “Value Creation”, “Information Lifecycle Management”, “Security”, “Metadata”, etc. etc. All of these disciplines are just as relevant in taking control of the data in your databases, as they are for managing the files on your shared drives, your content repositories and the emails on your servers.
I seriously believe that by propagating this artificial divide between “data” and “content”, we are creating policy silos that not only minimise the opportunity for getting value out of our information, but we are introducing even further risks through gaps and inconsistencies. We may have to use different tools for implementing these governance controls on different mediums, but the business should be having ONE consistent governance scheme for all its information.
Open to your thoughts and suggestions, as always!
The Great Big File Box in the sky – help me out here…
The internet is buzzing with the success stories of Dropbox.com and Box.net. How much they’ve grown, how much they are worth, who’s likely to buy whom, where does iCloud/iPages come into it, etc., etc.
Am I the only one who doesn’t quite get the point here? Yes, I can see how it makes file sharing easier and how it potentially reduces internal IT costs by outsourcing the management of large volumes of information.
How is this ever a good strategy?
We have spent the last 20 years, trying to educate companies on the need to organise their information rather than just dumping in on shared file drives. Classification, version control, metadata, granular security, records management, etc. Anything to convince users to think a little bit further than just “File, Save As” in order to minimise the junk stored on servers, to maximise the chance of finding information when you need it and maintain some sense of auditability in your operations.
So instead of moving forwards, we’re moving backwards! First Sharepoint and now these wonderful cloud services, allow us to shift our junk from our own fileservers to The Great Big File Box in the sky. With no plan, no structure, no governance, no strategy, no security model, no version control or audit trail.
How is this ever a good idea? I plead ignorance – please help me understand this…
Did anyone go to an “all you can eat” buffet restaurant and not come out feeling bloated??
Law – The fire within…
I must confess: I am not a legal expert and my closest encounter with a courtroom is through the safety of a television screen.
I realised recently however, that inside my brain I have multiple and conflicting views of “The law”.
I grew up in Athens and, even though my grandfather was a lawyer (or maybe echoing his cynicism), I have grown up with an inherent mistrust of all thing ‘legal’: Legalese language that seeks to confuse and befuddle the average mortal; vulcher lawyers that procrastinate in order to maximise their hourly fees; legal cases that run for years and years because scheduled court hearings get postponed on technicalities; the list goes on…
In another compartment of my brain lives the virtuous, almost glamourous, world of TV courtroom drama with a very diverse portrayal of reality, ranging from Rumpole Of the Bailey and Kavanagh QC to Ally McBeal and Law and Order. Where young and old conscientious lawyers are burning the midnight oil, over endless stacks of case law books, looking for the one nugget that will exonerate their Ill-accused client and where honour, ethics and the omnipotent sage of the presiding Judge, prevail to save the day.
Many many years ago, I was involved in the delivery of early, bespoke Document Management systems to large law firms, such as Clifford Chance, Linklaters, Cameron Markby Hewitt (as it was then…), and others, which gave me yet a different perspective: One where Law firm partners are considered akin to deity, hordes of hopeful legal students and young lawyers work through endless hours of menial tasks in order to establish themselves on a career ladder, where information is king but information systems are a foe and where laborious, manual processes represent the status quo. Admittedly that experience was over ten years ago, but it was a cut-throat business then and I doubt that much has changed since.
More recently, I have been marginally involved with the world of electronic discovery and reading about legal proceedings on both sides of the Atlantic, often through the excellent commentary of Chris Dale’s insightful blog. Through this, I have seen a more earthy view of litigation, where monetary considerations, negotiations, common sense (if such a thing exists….), judgments written in plain English, project management, geopolitical variances and the general admission that nobody, not even judges, are immune to the complexities of technological innovation, paint a picture of a legal environment that looks, well… almost business like! Commercial reality (and the associated astronomical costs of litigation) often dictate that cases are assessed, negotiated and settled on the merits of cost and objectives, not just “fairness” and “justice”.
Which of the views in my brain is more realistic? I don’t know. I find all of them fascinating: I am intrigued, watching an industry which is thousands of years old, constantly evolving and seeking to learn new tricks, acknowledging its own shortcomings and fighting to keep up with technological innovation – just like the rest of us!
“Hey, Watson! Is Santa real?” – Why IBM Watson is an innocent 6-year old…
I love the technology behind “IBM Watson“. I think it’s been a long time coming and I don’t doubt that in a matter of only a few years, we will see phenomenal applications for it.
Craig Rhinehart explored some of the possibilities of using Watson to analyse social media in his blog “Watson and the future of ECM”. He also set out a great comparison of “Humans vs. Watson”, in the context of a trivia quiz. However, I believe that there is a lot more to it…
Watson is a knowledgeable fool. A 6-year old kid, that can’t tell fact from fiction.
When Watson played Jeopardy!, it ranked its possible answers against each other and the confidence that it understood the questions correctly. Watson did not for a moment question the trustworthiness of its knowledge domain.
Watson is excellent at analysing a finite, trusted knowledge base. But the internet and social media are neither finite, nor trusted.
What if Watson’s knowledge base is not factual?
Primary school children are taught to use Wikipedia for research, but not to trust it, as it’s not always right. They have to cross-reference multiple research sources before they accept the most likely answer. Can Watson detect facts from opinions, hearsay and rumours? Can it detect irony and sarcasm? Can it distinguish factual news from political propaganda and tabloid hype?
If we want to make Watson’s intelligence as “human-like” and reliable as possible, and to use it to drive decisions based on internet or social media content, its “engine” requires at least another dimension: Source reliability ranking. It has to learn when to trust a source and when to discredit it. It has to have a “learning” mechanism that re-evaluates the reliability of its sources as well as its own decision making process, based on the accuracy of its outcome. And since its knowledge base will be constantly growing, it also needs to re-assess previous decisions on new evidence. (i.e. a “belief revision” system).
Today, Watson is a knowledge regurgitating engine (albeit a very fast and sophisticated one). The full potential of Watson, will only be explored when it becomes a learning engine. Only then can we start talking about real decision intelligence.



