Tag Archives: information

There IS such a thing as data, Benedict Evans

Again I was drawn to Benedict Evans’ emphatic statement that there is no such thing as data (There’s no such thing as data — Benedict Evans (ben-evans.com)). In this essay, Benedict challenges the present infatuation with data, claiming that in practice, data’s value is ineffectual, even bordering on the irrelevant.

He first succeeded at baiting my click with an episode of the same title on his Another Podcast with Toni Cowan-Brown (11 January 2021). Back then I think I surmised their argument is that data gets complicated with ownership and differing source systems, so it’s not worth worrying about too much. In this more recent essay though, perhaps the crux of the argument is more simple.

I was actually hoping that this topic would be in a similar vein to Professor Tom Wilson’s 2002 academic paper, The nonsense of ‘knowledge management’ – which was very formative in my early days of data and information management. In that paper, the professor argued quite successfully that the term KM was little more than a blurring of lines with information management. And that blurring was due to the information field no longer being sexy enough for management consultants and platform roadmaps.

Mr Evans though has come from very different stock, from largely telco market analysis and tech venture capital & industry trends. So it’s unsurprising he (quite sensibly) may have never thought of the discipline of data and information management as sexy.

I didn’t tweak this point at the time. Maybe I assumed due to half a dozen years of appreciating Benedict Evans’ content on Twitter – and as a subscriber to his newsletter for the past couple, that I would always agree with everything he says. Until now this position has held true for topics I don’t remotely understand. And perhaps this is why I immediately bit at this apparent reheating of a position that data (a topic I’ve had two decades of involvement with) is all nonsense.

https://twitter.com/benedictevans/status/1532632592658440194

Benedict was more clear, and correct in his reply. I was hung up with how things were phrased, rather than the accuracy of the claim. To begin an essay with the dismissive premise was actually a wonderful prompt to spark the attention of a student and practitioner of data, information, and architecture. The master stroke however was to go on to say it isn’t worth anything. I of course figured this to mean the personal, intrinsic and ongoing value that our data retains. I found, however, it most probably reflects the kind of returns that a venture capital lens would expect to see in a portfolio.

This point is developed further in the essay, claiming that our Instagram posts mean very little. A quick learner, I tried re-reading this as they mean “very little commercially”. But people aren’t interested in the commercialisation of their data. Quite the opposite. (Although we’ll all have a problem with non-viable platforms if no one is profiting.) Benedict views Instagram likes as “not [being] your ‘my’ data or ‘your’ data alone, and it’s not worth much without the context of all the other likes and follows.” This doesn’t sound like a problem of data not existing, or nonsense. It sounds like much more data exists than we originally conceived, and its ownership and management is complicated.

Similarly for likes on other social media platforms. Adding TikTok and PageRank into this same discussion, he sees “the value isn’t in the ‘data’ at all but in the flow of activity around it”. Yet it somehow omits that this flow of activity is captured, of course, in data. Then it steps further to consider those data streams of human interactions to not be restricted just to the world of the living. He challenges us to see these phenomena as mechanical Turks. I read this as data represents human activity, therefore, like other human processes we can automate without humans, and with scale. I worry what kind of future that will be. They are systems – it correctly highlights – but they’re human systems. By default those will always compose and present human data.

But back to the definitions used. I’m not sure we started with a valid foundation when it begins with “‘data’ is not one thing, but innumerable different collections of information.” Data is generally about one thing, and collections of it progresses to information with adding a context. It’s through context, we can understand. It’s not the other way around. There is little to no value in the isolated values of spreadsheet columns, but if we know the rows represent a highly sensitive context, the overall information asset which is produced has a clearer value and can certainly be leveraged to produce greater insights.

The contrary example the essay used here was combining wind turbine telemetry with specific public transport events. Their unhelpful correlation is pretty obvious. That’s not the fault of data, but the juxtaposition of two completely different contexts. Data relates to things (or events/entities). So very different “things” will rarely have a useful relationship between their data. What can be notable, and perhaps is undersold here (and oversold in plenty of industries) is how the advances in AI can bring potential in inferring and identifying causal relationships between disparate data. Such links may be inconceivable and inaccessible to the capabilities and capacity of human analysis.

Not to stop there, Evans asserts the “uselessness of common assertions” with an interesting example that routing insights from delivering large volumes of restaurant orders may not assist missile guidance systems. I hope not! (Although I think we’ve been through the idea of borrowing military hardware to deliver food.) My view again is that data is merely an atomic representation of the thing. It’s not a useful or achievable goal to make a single pool of all and everything we know about everything in an understandable (let alone actionable) way. For the reasons of analysis, many relatable (but not all) data sets can be brought together for wider insights. At the level of enterprises, data lakes aim to be that comprehensive repository of respective insight. I say respective, because it will still be based on a context of how, and for what, it was collected; and thereby how it might and might not be used. Even climate change won’t boil the ocean quick enough for arbitrary links to be made between everything and everything. And despite Benedict raising the challenge and nonsense of such an activity, I’m not sure that anyone is explicitly asserting they can and will.

The essay ended with a summary comparing the current AI and data concerns, with previous generational concerns associated during the early adoption of databases. It argues that the risks didn’t live up to the concerns of that time. So we shouldn’t worry now about topics of National or strategic data. Maybe Benedict’s position is indeed accurate, but the question will remain who is making most value from key data sets. Data exists everywhere, and vast arrays of data at scale with advanced analytics can tell us things we didn’t know before.

Any new insights that are generated can be used exploitatively before regulators can catch up. Surely this should all be handled with care, which is best done by appreciating its true value. So I like to think, even at a non-macro level, data is somewhat more than a nonsense or in fact not non-existent.

To conclude, I really like the referenced Tim O’Reilly macro quote that ‘data isn’t oil – it’s sand’. But I also like a competing value proposition by kids author & broadcaster, Michael Rosen, in the form of a poem called Words Are Ours. [laughing emoji didn’t work here]

#entarch to business speak translator

I had quite a positive meeting with someone from the business regarding enterprise architecture (EA) . It’s an interesting engagement, which we’ve yet to do in any other part of the business. To put it mildly, the area is terribly unhappy with their IT support. I’d suggest their issues are mostly with delivery and communication, program management, application portfolio management, technology modernisation, and business automation in general. This is why I am absolutely certain an EA view and strategy will provide massive benefits. The entire enterprise is so EA immature though, broaching the discipline with the business carries some risk. This wasn’t a major concern for me. It’s clear from the size of the above issues and the major stakeholder’s passion and urgency to fix them, that they “get” it.

To prevent any bad first impressions of EA, I carefully spoke to their needs. I stayed well-clear of our usual enterprise architecture mother-tongue/pseudo speak. (I feel describing enterprise architecture in any real detail intimidates even some IT folks who are more comfortable on the software side.) I was out of practice in business discussions, but the outcome was OK.

I thought it’d be interesting to take the time to record some of the key concepts I remember avoiding, and publish the business-friendly versions which worked. And it’s helpful to consider some more this “enterprise architecture to business speak translator”. Anyone is welcome to contribute their own. I’ve been to presentations some time ago which covered IT to business communication more generally. And there are probably stacks of posts on this topic which I’ll maybe reference later.

Enterprise architecture concept Business description
Meta model Big clear picture to describe everything we need to understand.  Ordinarily this is not something I’d recommend sharing anyway, but this was a special case.
Conceptual to logical to physical Going from the big picture of what you need, down to the level of detail where we know what we’ll put in place
As-is picture View of what’s there today
Business architecture Everything we need to know about how the operation is organised, and how it runs
Data entities Information
Association matrix Mapping
Business to IT alignment Implementing the right supportive technology that business processes require.  (The meaning changes slightly, but was correct in that instance.)
Tactical solutions What we can do in the short-term to help
Standardisation
Thanks Chris
Increase profit by reducing waste

Information poetry

I never thought a poem would appeal to me as an information architect. I thought this unknown fuzzy discipline is buried too heavily in business data and technology to enjoy something designed for pleasure purposes alone. Never in my wildest dreams did I think the information domain would be so clearly understood by someone other than an information manager, let alone a children’s author.

Michael Rosen changed this though. Myles had to watch his performance of We’re Going On A Bear hunt as part of his home work. My curiosity took me to his web site where I found a fantastic bit of prose, called

Words Are Ours:

In the beginning was the word
and the word is ours:
the names of places,
the names of flowers,
the names of names,
words are ours.
Page-turners
for early-learners
How to boil an egg
or mend a leg
Words are ours
Wall-charts
Love hearts
Sports reports
Short retorts
Jam-jar labels
Timetables
Words are ours
Following the instructions
for furniture constructions
Ancient mythologies
Online anthologies
Who she wrote for
Who to vote for
Joke collections
Results of elections
Words are ours
The tale’s got you gripped
Have you learned your script?
The method of an Experiment
Ingredients for merriment
W8n 4ur txt
Re: whts nxt
Print media
Wikipedia
Words are ours
Sub-titles on TV
Details on your cv
Book of great speeches
Guide to the best beaches
Looking for chapters
on velociraptors
Words are ours
The mystery of history
The history of mystery
The views of news
The news of views
Words to explain
the words for pain.
doing geography
Autobiography
What to do in pay-phones
Goodbyes on gravestones
Words are ours.
Source: http://www.michaelrosen.co.uk/poems_wordsareours.html, accessed 20 October 2010