---
title: "On an industry analyst daily diary and RedMonk's collaborative conversational model."
date: 2005-12-09T19:23:47Z
modified: 2005-12-09T19:23:47Z
permalink: "https://redmonk.com/jgovernor/on-an-industry-analyst-daily-diary-and-redmonks-collaborative-conversational-model/"
type: post
status: publish
excerpt: ""
wpid: 419
categories:
  - Uncategorized
timestamp: 2005-12-09T19:23:47Z
tags:
  - Uncategorized
---

I came across Richard Monson-Haefel’s [blog](http://rmh.blogs.com/weblog/) today and I am impressed. 



Its the first blog I have seen that [opens the kimono](http://avc.blogs.com/a_vc/2005/12/vc_cliche_of_th.html) about the working life of an industry analyst at one of the major firms, in this case, Burton Group. How, for example, research agenda planning processes work, in [When Analysts Collide](http://rmh.blogs.com/weblog/2005/11/when_analysts_c.html).



The restriction of the kind of working environment Richard describes is one of the reasons I am very happy to be working more independently. If me or Stephen spent three days researching a topic and didnt even get a blog out of it, I would fear for our future… but I understand that adversarial peer review has a role to play in the industry analyst business. A vicious peer review was a famous and well established part of the Meta Group hiring process. If you got through a session presenting to the firm’s senior analysts without them tearing you and your idea a new one, Meta was confident you would thrive in their mountain goat environment.



A big difference at RedMonk is that we look to the community, rather than just our internal colleagues, for peer review on our ideas. We’re more bazaar than cathedral. The community (hopefully of many eyeballs) tightens up our thinking and irons out our bugs. That is one of the reasons we value our super platinum mega value readers so much. They don’t pay us money, but they do drive our research forward. People like [Stephe Walli](http://stephesblog.blogs.com/), [Jaime Cardoso](http://jroller.com/page/jaimec), [Mike Champion](http://blogs.msdn.com/mikechampion/) (now there is a chap that will force you to be rigorous through incredibly polite disagreement), [Gary Edwards](http://openstack.us/) ([when 2c is worth a lot more than that](http://www.redmonk.com/sogrady/archives/000890.html)), [Bobby Woolf](http://www-128.ibm.com/developerworks/blogs/dw_blog.jspa?blog=392) and [Bill Higgins](http://www-128.ibm.com/developerworks/blogs/dw_blog.jspa?blog=396) (IBMers that aren’t client types but push us hard on issues like patterns, SOA and standards), [James McGovern](http://duckdown.blogspot.com/) (enterprise architect seeks open source analysis for friendship and maybe more, must strong sense of irony), The [Two Neils](http://www.mwdadvisors.com/about/profiles.php) (work at a competitor, or is [MWD](http://www.mwdadvisors.com/index.php) a collaborator? Both.), [Alex Barnett](http://blogs.msdn.com/alexbarn/archive/2005/11/13/492350.aspx) (dragging us all into the future). One of the people I am writing this blog for is [Ryan Tomayko](http://naeblis.cx/rtomayko/), because he says my technical analysis is ok, but my analysis of the business I work in is really interesting. Well now you can add Richard to your blogroll). 



So that is how RedMonk works. And [this is how Burton does](http://rmh.blogs.com/weblog/2005/11/burton_groups_b.html). 



You should look to industry analysis on a blog like [tecosystems](http://www.redmonk.com/sogrady/), but Richard is doing something different with his blog. Let me explain: while RedMonk uses blogs as a primary mechanism for our conversations with the market, to underpin a collaboration with those outside our firm, as a primary publishing vehicle, other industry analyst firms take a different approach, based on their history.



What Richard is doing is opening up the business with a blog that takes the venerable daily diary form. The blog helps to demystify the business, which has to be a good thing. I really like it when Richard calls out, for example, the importance of admitting [you don’t know the answer](http://rmh.blogs.com/weblog/2005/11/sometimes_the_b.html). Analysts in my experience HATE doing that – but oftentimes saying “I don’t know” is the only way you can really help your client.



Welcome to my blogroll Richard, and welcome to my community.