“My own experience with analysts is mixed. Analysts tend to be great at predicting the past, but far less adept at predicting the future.” – Matt Asay
I submit that the above is true. Well, generally true. Analysts, as a rule, are better at predicting certain subsets of the past; the lack of reliable adoption and deployment metrics for open source, as an example, is a recurring problem for measurement and metrics firms. But it is more or less accurate to state that the traditional industry analyst industry is more comfortable by far predicting the past than the future. Who wants to author another “Windows NT will wipe out Linux” paper, after all?
I further submit that the above is true because that’s what the typical analyst customer wants. This is, as far as I’m concerned, nothing more than the obvious conclusion to be drawn from the financial performance of the market leaders. Matt goes on to assert that analyst customers are, in fact, looking for quite the opposite, saying “[the future] is actually what customers expect from them.” I do not agree.
It would be difficult, after all, to imagine that all of the industry giants were simultaneously failing to serve that same need, that same craving for predictions of the future. It stands to reason that, in the face of demand, one of them would emerge, differentiated on their ability to service these requests. That this has not occurred – though some might dispute this – tells me what I already believed: that analyst customers, particularly the larger ones, are thinking less about the future than the present, and less about the present than the past.
And, it must be said, less about the past than their jobs.
There has rarely been more pressure, after all, on IT departments. Budgets are being cut, resources being let go, enterprise pricing is going up, and on top of it all the technology landscape is increasingly fluid. The trio of open source, Software-as-a-Service and consumer technologies are putting IT staffers in the awkward position of explaining why they can’t deliver the same technology that their kids use to chat at home. In such an environment, is it any wonder that conservativism is the rule?
The problem, then, with traditional analyst coverage is one of audience – if indeed it’s a problem at all.
The audience for major industry analyst coverage wants to know not about what’s new, not about what’s exciting, not about what’s cutting edge, but rather what is safe. What will keep them in the CIO’s office longer than the oft-cited 18 months figure. Which the larger firms are, frankly, excellent at delivering. Not to mention monetizing.
And while the temptation might be to lament a status quo that favors a geological pace for technology development, such tears are entirely unnecessary. Because while the available evidence indicates that the powers that be within industry analyst customers are indeed looking backwards rather than forwards with respect to their analyst research, it also demonstrates quite effectively that the folks in the trenches are exceedingly effective at routing around such obstacles. With, or more likely without, the help of industry analysis and research.
As I’ve been telling audiences for years now – see this presentation from 2005, or this one from 2006 for examples – the power within the enterprise has shifted. As proof, I point you to the success of Linux, Apache, MySQL and PHP – even Skype or WordPress: technologies that were successful not because of analysts, or CIOs, or – with the odd exception – vendors, but rather because of the audience that did not and does not make deployment decisions based on analyst reports. Just what works.
rPath CEO Billy Marshall’s piece the “The CIO is the Last to Know” says it better than I can. But I still love telling the story of the CIOs and IT managers from broker/dealer firms I spoke with years ago, who told me that because they hadn’t issued instant messaging software none of their people were using it. The punchline, I’m sure, you can guess.
It is these on-the-ground, in-the-trenches audiences – who are neither the primary target audience for traditional research nor the ones funding it – that are the foundation of RedMonk. We listen, of course, to CIOs and vendors alike, but the bulk of our intelligence derives from the developer masses. These good folks tell us what works, and what does not. Which sometimes aligns with what we hear from vendors, and sometimes does not.
When we say “Analysis for the people, by the people,” we’re not trying to be cute…well, actually, yes. Yes we are. But it is at the same time a simple reflection of the truth as we see it, that we happen to be more forward looking because that’s where our readers – who double as our researchers – are pointed. The technology trends that I flatter myself to believe that we have correctly identified and championed well ahead of the curve – from the cloud to database developments to dynamic languages to mashups to REST to SaaS and so on – were not, themselves, RedMonk conclusions. They were the conclusions of our community; we merely researched and extrapolated from them.
None of this is to say that one approach or the other is entirely correct: it is, as always, a fundamental question of audience. CIOs ask for one type of research, and there are firms – many of them – that deliver on those expectations in fine fashion. Early adopters, on the other hand, ask for something quite different, and we and others try and deliver that. Whether you’re looking to forestall future criticism or read about the latest trends in web scale out, after all, you deserve research that suits your needs.
What’s more, a tension between the conservative and the radical is not only necessary in the context of technology adoption, but desirable.
If you’re looking for industry analysis, then, I would tell you to remember your elementary school History lessons: consider the source, and perhaps more importantly, the source’s source. Whether you’re conservative or bleeding edge, there is research available. You just have to know where to look.