Friday, 18 August 2006

The revolving door is in full spin...

Looks like the summer analyst job market is in full swing (see previous post Summer revolving doors).

David, him again, lists a few more in this other post:
Analyst Insight: A few more analysts in Europe including:

From another source we gather that Lee Geishecker resigned from Gartner (yet another high profile departure) where she was covering ERP and various other software bits. Does anyone know where she's going?

Saturday, 12 August 2006

Summer revolving doors

David summs up various movements in this post: Analyst Insight: Various analyst changes.

In brief, Quocirca finally signed up a new analyst, Butler loses another analyst (fed-up with compiling door-wedges-reports?) and Forrester shrinks too. It looks like the latter still has some open headcounts to cover consumer markets and applications to further enrich their "molten core". Quite why they missed the train of departing soon-to-be-ex-META analysts still puzzles us...

Monday, 7 August 2006

How much then?

Stinky wanted to know how much a Gartner analyst makes...

The ARmadgeddon staff estimates (.3 probability) this to a range starting from £60k for a junior to £120k for a senior analyst.

Has anyone got comments?

Wednesday, 26 July 2006

Media continues to cite META Group

I have found a fascinating page at Topix. It tracks mentions of META Group. Interestingly, even though Gartner announced the purchase of that firm in 2004, there are some.

A great example is this story from May this year, in which a META Group analyst comments on Dell's performance.

How serious are journalists' conversations with analysts if they don't even check the name of the analyst firm they are citing?

Wednesday, 19 July 2006

Another one bites the dust

In the wake of SageCircle and Kensington Group, we can now report at Serendipp, a UK analyst relations consultancy, has also closed.

Readers might recall that last December we had some criticisms and harsh comments about that company. In Serendipp's opinion, "Analysts only do two things: size markets and do case studies".

Our comments was this: "This is so far from being right, it's not even worth calling wrong. Sizing markets and writing case studies is what gets outsourced to India. The real work of analysts is quite different: and that is why analysts have substantial advisory, consulting and custom research businesses. If an AR advisor doesn't realize this, then heaven help their clients."

Indeed, the company has now closed. A posting on the firm's blog explains that those the firm's partners have taken employment elsewhere. Rest in peace.

However, this story has a little tickle are the end. Our chiding of Serendipp last years ended this this comment which, in hindsight, is amazing prescient: "It would be far better to understand one's limitations and keep only do what you know how to do. In that respect, kudos to Hill & Knowlton. If Duncan's latest post is correct (my Norwegian is rusty) their European AR is led by their partner agency in Oslo, Gambit, which hired a former IBM AR manager in 1999."

What's interesting is that one of Serendipp's partners has been hired by H&K to work on its European analyst relations. Let's hope his boss in Oslo doesn't let her analyst relations business go the same way as Serendipp.

Friday, 14 July 2006

Blon-idc and briefing 101

David posted those links recently:

IDC analyst going blonde (Analyst Insight: Mobile analyst goes blonde for charity)

and this briefing 101 from a Yankee analyst, well worth a read even if you've been doing AR for a while [The Human Capitalist:] The Vendor Pitch

Tuesday, 11 July 2006

Gartner bullies Redmonk (and then apologises)

The summer was going to pass by whitout major events (apart from the World Cup of course) when Gartner suddlenly headbutted Redmonk:

James Governor's MonkChips: My First Gartner Cease And Desist: the missing link

Now, this is quite funny -the only thing James did was to post this link on his blog, there. And Gartner issued a cease and desist, for deep linking probably?

Although we have great respect for some Gartner analysts, it's probably fair to say that the Borg behaves itself like a bully. It was until now confined to vendor relations but this Borgian trait seems to be spreading....

17/7 update: commenting on a subsequent post where James publishes the incriminating email, Allison from the Borg Vendor Police apologises for their bullying. Borg 0 - Blogosphere 1.

Thursday, 6 July 2006

IDC and DQ: sausage factories?

Witty comparison from Cambashi between market numbers and sausages:
Everyone likes sausages Jun 2006

Monday, 3 July 2006

Ovum targets vendors

Ovum, which has recently IPO'ed (read this) is buying
Summit Strategies, a US firm doing business mostly with IT vendors (consulting and commissionned white papers).

Ovum had already forayed across the pond with the RHK purchase, however this time they're targeting IT vendors and not IT users: although Ovum is indeed selling research and advisory services (RAS, in plain English consulting days and access to a research library) it does not typically accepts commissionned white papers from vendors -which is Summit's business.
It will be interesting to see how Ovum deals with the integrity issue (for memory, Gartner killed META Group's white papers offering when it took it over).

Bottom line: Ducan seems to think Ovum is doing well but
we still are reserved as to whether they are capable to position themselves as a credible alternative to the Gartner Borg outside a few markets such as telcos.

Friday, 9 June 2006

We get roasted for pro-Gartner bias

Perhaps Hugo Chavez will be the new face of Hugo Boss, but that would not surprise me more than a comment on Catherine Heltzerman's blog. This post includes a fascinating comment about us:

Armadgeddon excited me to start with, but I am increasingly surprised at how pro Gartner all their analysis is especially given they go under a nom de plumes.
This is a fascinating comment from James Governor. The idea that this blog is pro-Gartner will be a shock to post readers, especialy those who have read this series here.

What's eating James? Does he really think we are pro-Gartner stooge, or is it just than we don't really rate his firm on a par with them?

Answers on a postcard please to ARmadgeddon, PO Box 666, Stamford, 06902. Or post your comments below.

Thursday, 25 May 2006

[Analyst Insight:] Forrester's latest AR Council initiative

David reports here a very daft idea:
Analyst Insight: Forrester's latest AR Council initiative

Why on earth would a vendor want to invite other vendors to one of their briefings?

The only explanation we can find is that there's been some space-cake abuse during a brain storming at Forrester's Amsterdam office.

We've posted before (here, here and there for instance) and to be frank we struggle to see their relevance -here in Europe at least. We can't see thought leadership, their sales efforts are timid at best and we haven't seen much of a strategy.

Despite garden, Oracle isn't mellowing

According to Berkeley's heartthrob analyst, "The hottest rumor in recent weeks among analysts was that Oracle’s head of analyst relations had lost her head in a power struggle".

Josh's article explains that vice-president Peggy O'Neill was thought to have been ousted because of growing frustration with Oracle's highly controlled analyst relations.

We are scratching our heads at that idea. Here on the ARmadgeddon campus, there's general agreement that agressive management of AR is more likely to be rewarded at Oracle than punished. Remember, it's hard-nosed Oracle that bought the PeopleSoft hippies, not the other way around.

If Oracle didn't intent to play to win, then they had the opportunity to change course in 2003. The evidence suggests to us that Peggy's tactics are fair, but people still asked Oracle to mellow and cut analysts more slack. They have not, and we don't see a growing demand inside Oracle for the firm to loosen up, even if Larry's main interest is his Japanese garden.

Mind you, the very idea of Peggy leaving Oracle is interesting. If she was to switch career, what would she be well suited to? Answers on a postcard, please.

Thursday, 11 May 2006

The Borg mexican army

During a teleconference yesterday, Gartner's head of research Peter Sondergaard (or is it Dale Kutnick?) announced a reshuffle to accomodate the new role-based research structure. The new execs and their research groups:

  • Mike Lafford: sourcing & vendor management (they wrote vendors, not IT providers :-)
  • Jane Doorly: security & privacy
  • Jamie Popkin: business intelligence and information Management
  • Joe Baylock: IT infrastructure and operations
  • Val Sribar: applications management
  • Jennifer Beck: business of IT (whatever that is)
  • Bruce Bond: vertical industries (isn't that a pleonasm?)
  • Mike Harris: Dataquest (Gartner's number-crunching bunch)
  • Satoshi Yamanoi: Japan research
  • Jenni Lehman: research operations (analyst's bosses)
These are only internal changes in the Borg Mexican Army (over 70% of their analyst have "Vice President" in their titles but we have failed to identify to this day whether they really mean "Vices Preside"). The net impact for AR professionals is minimal as so far the new roles-based structure is more an internal reorg. However, Stephen England from KGC "bloviated about" the fact this could signal the Borg may price each research group separately, thus forcing vendors to buy more seats.

No new news there Stephen, just the usual highway robbery from the Borg.

Monday, 8 May 2006

Sageza ties in Tony

Looks like the UK analyst scene never stays still (see Is there an afterlife for analysts?, Becoming an analyst, getting it right and being paid for it! and Making it up While Drinking)
as we learn today that Tony "fancy ties" Lock is transferring from Bloor FC to Sageza Dynamo for an undisclosed sum this month.

Tony will probably play in the infrastructure frontline and continue to press for the formation of a European league together with his new colleague Joyce Becknell. Other clubs in the league are of course MWD and Freeform Dynamics, with more rumoured.

The coach Clay Ryder is said to be delighted with this new addition to his squad. Poor old Justin though...

Tuesday, 2 May 2006

Want a job at Microsoft?

Well, if you're an analyst you might stand a good chance. Following suit from a few ex-colleagues (read Microsoft boosts its AR and Microsoft hires from Gartner, right, left and centre!), we have heard a rumour that Larry Velez is leaving Forrester for Microsoft.

Larry might need to do something about hairstyle... (compare him vs them)

Wednesday, 26 April 2006

How many are too many Gartner events?

Duncan publishes a glowing report on the latest Borgference here:
ANALYST EQUITY: Gartner's Outsourcing Summit spotlights opportunities:

So the content was good (we agree) and we found the audience was good. Location was the Royal Lancaster again (as some others and the upcoming Datacenter Summit), however there are two caveats.

  • There are now 11 events (including vision events and the fall Symposium) for the second half of the year. Are all of those event providing value for a specific audience and can the market sustain it?
  • Duncan mentions the majority of attendees at the Outsourcing Summit were vendors. Those summits are an attractive option for networking, as the Symposia have become too large for debating ideas. But only if they are not overtaken by vendor presence.
We'd love to hear your views on the subject.

Monday, 24 April 2006

Step up a geAR or disappeAR!

While many AR professionals are not yet prepared to take the bold step Duncan discusses here (Should AR run Influencer Relations?), it remains that they should go outside their comfort zone and address the following challenges:


ARmadgeddon's take:
  • We believe that only 5-15% of IT vendors have best-in-class AR practices and AR staff of the right caliber to transition from AR and grow into IfR: Influencer Relations. This supposes the ability to recruit the right people and secure significant incremental resources.
  • Second tier AR teams will face budget cuts and (re)-integration within the communications department, with the prospect to be compensated/promoted on clippings levels (or worse, on activity) rather than relationships and sales impact (or even research quality and thought leadership).

ARmadgeddon's predictions:
  • The dichotomy between best in class AR and second tier will no longer be based upon basic know-how as best practices filter through, but will rather be the result of AR measurement and strategic policies (.7323 probability)
  • Further re-alignment with media relations will impact positively analysts-for-hire's business (more budget allocated to paid-for reports) but this trend is detrimental to both analysts and AR credibility overall (.5itting-on-the-fence probability)

Giving customer goggles to Borg analysts?

David reports a comment from Richard Stiennon on Bitter Andy's blog here:

Analyst Insight: Using customers to win credibility with Gartner?

It assumes that, since Gartner analysts speak to few clients each week, AR professionals have a good chance to influence them by getting clients to call them.

ARmadgeddon's take: this indirect approach is interesting but IT vendors should be careful and not risk the assumption that (all) Gartner analysts would be daft enough not to smell something fishy going on. Covert AR operations often back-fire and vendors should be advising to call specific analysts only if they add value both to the end user with clear and insightful recommendations (only minority of analysts achieve this, even at Gartner).
AR managers should concentrate on providing relevant and unfettered customer references -this being one of the top analyst requests.

Wednesday, 19 April 2006

Wanted: Analyst Relations Director (job posting)

We recived an email this morning from some recruiter looking for a US based AR Director asking us if we could post the following job ad. Hey, why not? Here you are...

HIRING: ANALYST RELATIONS PROFESSIONALS
Title: Director, Analyst Relations
Company: Confidential [Fortune 500 IT company]
Location: Pennsylvania

To learn more about this opportunity drop an e-mail to:
Edward Proctor, Researcher,KG Group

Tuesday, 18 April 2006

Bitter Andy defends his Tragic Quadrant

Nothing better than some fun reading when coming back from a four-day bank holiday week-end.

Borgmember Andy (Bitterer) has kindly obliged, after seeing red for a Gartner Magic Quadrant on Business Intelligence (is that not an oxymoron?) had been criticised by a certain David Stodder from Intelligent Enterprise.

Of course, David's has Beotian views on the Borgian Tragic Quadrant and Andy is right to put things in their place. His A3Q (Andy's Advanced Automobile Quadrant) is funny and a good metaphor, but Gartner and the overall ecosystem would nevertheless benefit from disclosing methodologies behind the Magic Quadrants.

PS: to Andy's credit, he's one of the few Borg analysts to comment and blog.

Links:
bit blue blog: Show me your Quadrant and I show you mine
Step Outside the Magic Kingdom

Sunday, 16 April 2006

AR is a sales job with no quota

Karen Rohack Mclaughlin, Queen Buckaroo at QB Comm, Inc., wrote these notes of a Silicon Vlley PRSA meeting two or three years ago. Re-reading them, I think think deserve a wider audience. To find out more about the SV-PRSA, visit siliconprsa.org.

(AR) has evolved into a critical function due to the industry analyst’s ability to impact a firm’s shareholder price, strategic position and overall mindshare buzz.

The panel explained that AR is a sales job with no quota and no typical day. As with PR, AR influences the mindshare of a key audience by educating them about the company’s business and marketing strategy, key messages and by freely exchanging information. The panel felt AR provides a good return on investment because of its ability to understand the competitive landscape, its positive impact on a company’s strategy and message development, and its ability to give management an honest viewpoint about what’s happening in the marketplace.

A panelist commented that PR tends to take a short-term view, while AR has a more long-term perspective and relationship-building function. This comment made me wonder if AR’s exposure to PR is not to its strategic planning and execution functions, but rather only to the tactical, short-term PR projects such as product intros, new programs and initiatives and crisis response.

What Makes An AR Program Successful? The panel emphasized that support from senior management—their provision of time, financial resources and staff --- are all crucial for the long-term success of an AR program. The panelist’s AR departments averaged between two and 20 people, and all utilized some type of “home grown” contact database solution to keep track of analyst contacts.

While it was mentioned that Cisco offers an annual two-day analyst conference that is a combo of AR and Investor Relations (IR), the panel cautioned that it’s not a good idea to do a large mixed-analyst briefing for a new product or company initiative, especially with tier one analysts. One-on-one briefings are best. However, a large briefing of analysts from one firm can be a cost-effective way to communicate.

Similar to the way many of us set up our press relations, HP tiers their analysts. Level one analysts receive one-on-one briefings and more direct contact, while levels two and three are updated mainly through teleconferences. The panel also noted that because analysts know the market and the players, they can be used to bulletproof presentations, messages and to fine-tune company or product positioning. The AR department can help PR select the appropriate analysts for these types of briefings.

AR’s Biggest Challenge: The analyst landscape is constantly changing. With so many mergers and acquisitions, customer solutions are expanding, so there is a real need to balance corporate vs. technology messages to the analysts. One panelist mentioned, “...many don’t know where the industry is going, so we’re all hedging our bets with strategy/product solutions.”

Key Points to Remember: In AR, you can never rest on your laurels. AR is only one data point for the analysts to secure information about a company’s strategy, technologies or products. It takes hard work to continue to be viewed as an important and knowledgeable resource to the analysts and to reinforce your company’s mindshare and analyst relationships. Also, there must be a strong synergy between the AR/PR/IR functions, as all are important partners in the communications effort. It’s critical to keep everyone updated on goals, strategies, programs, and the competitive and internal issues that might impact the audience.

Wednesday, 12 April 2006

It's time to cut Rob Enderle some slack.

I never thought I'd say this. It's time to cut Rob Enderle some slack.

As his resume reminds us, Rob Enderle is one of the most referenced analysts (according to analysis of the US media by long-dead Kensington Group, whose data reflected his years with Giga). He will comment to the media on almost anything. He is the analyst industry's answer of the Hollywood star who turns up if she's invited to the opening of an envelope.

An article in 'The Register', Sun zinged by rent-a-quote analyst, mentions that Enderle is not only critical of Sun, but is also paid by Sun's competitors. The Register's premise is the idea that Enderle's comments are swayed against Sun because his customers include competitors of Sun. The article describes Enderle as a 'rent-a-quote' analyst: they feel Enderlie has been rented by Sun's competitors to be critical of that fim.

Here on the ARmadgeddon campus we take a neutral view towards Sun and its fortunes. We know that many of its customers have remained fans of the firm for good reasons. However, it's a bit like being a fan of the Seattle Seahawks. There are few victories that attract fairweather friends. Indeed, even rehirings are seen as a victory -- a sign that things are at least not as bad as they were recently.

It has to be admitted that you don't need to rent analysts to get them to criticize Sun. It's a technical and evangelical organization, facing an analyst community that is increasingly disinterested in technology - almost to the point of naïveté. Sun sells to tech-savvy companies more easily than most. Analysts increasingly dismiss strong technology as 'speeds and feeds', sometime for good reasons, sometimes for bad reasons

On the same Register web page was an advert for one of Sun's competitors. It seems unfair for 'The Register' to not judge others by its own standards. How can it assume that Enderle has been 'rented', when we are sure they they would say that they have not been. How come analysts' are corrupted by vendor money, in their view, when The Register is not?

Of course, these are ridiculous standards: analysts are able to comment on technology vendors partly because they are paid by multiple competitors, without being corrupted. Many analysts are paid by Sun's competitors -- and by Sun. The idea that are 'rented' simply by being consulted by these organizations is lazy and untrue.

If 'The Register' was to make these charges against a large analyst house, like Gartner, then lawyers would be involved right now. Rob and his partner don't have in-house legal staff, but they must surely be considering it.

P.S. The comments on this post have encouraged us to clarify our views. Our criticism is that The Register assumes that Enderle is biased against Sun because his clients include competitors of Sun. In our opinion, this is not the right basis on which to be critical of Enderle (Perhaps this is the right basis. We also point readers to the fourth comment here). Other analysts are also hired by Sun's competitors and, of course, The Register also has those firms as clients. In our opinion it is unfair, if not fatuous, for The Register to assume that Enderle is corrupted simply by these commercial links -- especially since The Register has the same links (and presumably feels that it is not biased by its advert revenue).

Fox News certainly is biased. However, the right does not need to pay Fox for it to criticize the left. Fox would do that for free. Similarly, Enderle does not need to be paid to criticize Sun: Enderle will do that for free.

The Register's article aims to discredit Enderle simply because of his commercial ties, and not because of the correctness or falsehood of his views. In our opinion, that is a red herring. It is also dangerous for analyst relations professionals. If analysts are discredited simply because their clients include vendors, then this will make it harder for both users and vendors. Like it or not, analysts are less biased than other sources. That is why businesses trust them. Analyst houses would be not more or less independent if they did not have vendors as clients: but they would be smaller, less economical, more expensive and less effective. That is is no-ones' interest. Specifically for AR professionals, The Register's baiting of analysts also obstructs our work. We want our colleagues to be less anxious towards analysts: The Register simply throws more trash into the sea of putrid cynicism.

Of course, this does not mean that Enderle is right with this -- or any -- comment he gets into the media. However, we do feel that any errors in analysts' views are as much despite close relationship with vendors as they are because of those relationships.

El Reg takes on The Economist and Rob Enderle

The Registers fires at pointblank on Rob Enderle on the allegation he's a "rent-a-quote analyst" paid by Sun's competitors:
Sun zinged by rent-a-quote analyst | The Register

The article contains some strong language, which seems to be a trademark of Ashlee Vance. But who pays HIM?

Beyond the apparent scandal, this raises again the issue of transparency in the analyst community.

See also:
The Governor, ancient Iraq and Gartner

Monday, 10 April 2006

AR 101 series: NDA's

Briefings under NDA are not only a recurring question for AR newbies but are also the source of ongoing debates among the AR community, see for instance the comments on this SVG post:



1. What is an NDA?
In industry analyst relations terms, it is used when vendors schedule an analyst for briefings containing information not publicly available. These briefings are commonly referred to as "under NDA", after the "Non Disclosure Agreement" analysts are kindly asked to sign. This agreement is prepared by our friends from the legal department and is a contract which simply aims at protecting the IP discussed during this briefing. As a contract, it needs to be signed by both parties to be binding. It also should have a specific timeframe during which the IP is under NDA and should delimit very clearly what is covered: products, strategy, offerings, competitive tactics, etc...
The term NDA is commonly used outside of AR, not only in the IT industry but also in general business. In the dark world of media relations, this is similar to an embargo, in that a date and time is before before which the information cannot be shared. As often with PR, it has a much more restricted meaning as it usually describes a one-way communication that should not be reported before the announcement date. Unlike an NDA, an embargo works on trust rather than legal force. Phil posted another definition here.


2. Why should I organise NDA briefings?

The simple answer is because both parties have an interest in doing so.

With NDA briefings, vendors can schedule briefings ahead of announcements and make sure air-miles-junkies get the news (old news is no news). Those briefings are also an opportunity to get feedback before releasing something into the wild, thus potentially avoiding big and costly mistakes or refining the messaging (see #8).

On the other side of the table, and as we mentioned here, analysts are interested first and foremost by future strategies and roadmaps. The essence of their job is analysing information they have gathered, so access to unpublished details is a differentiator for them.

NDA briefings also benefit users who are clients of both analysts and vendors: imagine a bank considering a new application and hiring an analyst to advise. You're about to launch a new release and the analyst is not briefed. You missed the sale because you were not on the short list. Now consider the case where the analyst was briefed under NDA: he can say something like "I think you should also go to vendor X and ask them a pitch on their upcoming product release". You may be considered for the RFP and have a chance to get the deal!


3. When should I do briefings under NDA?
Vendors should use NDA's wisely. If the whole marketplace is buzzing about an upcoming announcement, they may become a laughing stock when trying to enforce NDA which does not bring new news to the analyst.
On the political side of things, NDA briefings might also a good way for AR professionals to be covered in case of leaks (see #5 and 6).


4. What form should I use?
If you have a legal background, you should know. In any other case , go to your legal department or legal counsel. The form usually asks analysts not to talk or write about what was disclosed until a specific date. Make sure it's very specific on what is under NDA and until when. And always keep the required paperwork at hand.... (see also #7)


5. Do analysts break NDA's?
Analysts' existence largely depends on their reputation. If they are known to not abide by the rules of the game, they will quickly be excluded. On the corporations are ready to go to great length to avoid sensitive information to fall into public domain.
So it's no surprise if leaks are neither common nor widely publicised. It is often the case that analysts obtain information from other sources, like two well-known cases. It is more tricky to assess when analysts share something under NDA within their firm.
At the end of the day, it is a question of trust: only brief analysts that you have complete trust and resist pressures to extend your A list. Do give some though on the impact on your customers.


6. What can we do if an analyst don't observe an NDA?
The Apple Secrets case was a PR disaster and it's impossible to take back something that's published. Check your facts, make sure you clearly said it was under NDA. Then go to the analyst and ask some explanation. If inconclusive, ban the analyst and tell your peers. Keep in mind this is a one way avenue and that you won't easily recover this relationship. But the analyst should know too.


7. Should I always use a form?
No. Use the forms when the project discussed has very high sensitivity and exposure within your company to CYA. Most of the time, the form is there to inform the analyst -as we've seen in #6, there's little way to seek redress if things go pear shaped.
In most cases, analysts are pretty good with observing NDA's and it's a question to know which ones to trust or not.
However, be very careful to flag what is presented to analysts under a non-disclosure agreement, mark the sensitive slides as "VENDOR X INTERNAL USE ONLY" or similar injunctions. Orally, say it's under NDA several times. This also apply to customer references: if the customer and your account team did not explicitly approve for public consumption (make sure you have an email trail stating it), then release the story, the industry but not the name and say it's under NDA.


8. How do analysts react to NDA's?
Some perceive NDA as a signal that they are being admitted within a small trusted circle and react well! Others pretend to be offended because you don't trust them enough!

As with most things in business NDAs should not come as a surprise. Surprises are nice if you're a 10 and it's your birthday. Do let the analysts know when inviting them to a physical briefing that they'll be expected to sign an NDA. In the case of telephone briefings, do send them the form before, requiring they fax it back. Far too often AR people pass analysts NDAs, which basically forces the analyst to sign the NDA without reading it [which would mean the NDA would not stand up in a European court] or to delay the briefing until the NDA has been studied.

Some analysts refuse to sign NDAs because they feel NDAs prevent them from doing their work. Many also point out that NDAs are typically far too wide to be enforceable. To ease the concerns of these analysts, make sure dates and secrets are precisely stated and avoid blanket NDAs. Bear in mind that you're communicating information to help them do their job and broker it.

Some analysts will still refuse, claiming it's against their company policy (like the Gartner Borg). In many cases, Gartner has a blanket NDA with most large vendors, which can be okay. Do CYA with your legal department though.


9. An NDA briefing is not a consulting engagement
If you're after message testing and validation, then you should not expect analysts to deliver this for free. The temptation is great to call on their goodwill to get feedback but a line needs to be drawn somewhere. This will be the subject of a further AR 101 on briefings. Note that engagements under NDA are easier to police too.


Bottom line:
  • Vendors should use NDA with moderation, clearly delimit what is under NDA and what is not, specify a reasonable end date and resist abuse briefings to get feedback.
  • Analysts should not sign an NDA without specific date is mentioned or if products/offerings are not clearly marked out and be careful not to spill the beans.



  • Links:
  • Gartner analysts to no longer agree to non-disclosure agreements for briefings
  • AR 101 series: briefing analysts
  • Ovum breaks the iPod cellphone embargo?
  • Frank Gilroy, Entrepreneur: Non-Disclosure Agreements (NDAs)
  • Sacred Cow Dung: MYTH: NDAs are a Good Idea
  • Starting a Software Company: To NDA or not NDA
  • James Governor's MonkChips: On How To Brief Analysts what we are, and expect
  • The Devil's IT Dictionary: NDA
  • The Infamous EMC Storage Analyst Letter
  • IBM letter to a Isham Research
  • Friday, 7 April 2006

    Borg Games

    The feedback gathered after the latest AR Club meeting in London is interesting. It shows a growing dissatisfaction with the Gartner/Borg commercial practices, value for money and processes. Long gone are the days where most parts of the marketplace were "balanced" thanks to the META techno-utopians and where vendors could implement effective "dual-vendor" policies.

    So it seems like the Borg is trying to sweat as much as possible from the resources they refer to as human by increasing analysts' billable time in several ways:

    • There's been ample discussion, including with the only Borg analyst who should be credited for having the guts to come and discuss on this blog, about the Vendor Police trying to limit briefings to 30 minutes. Some vendors mentioned that Gartner is trying to force clients to use inquiry time for briefings. By decellerating and obstructing the effectiveness of the briefing booking process, vendors who can afford it simply book lots of advisory calls to take the place of the one briefing they and the analyst would have prefered. Furthermore, Gartner now bullies clients to buy an advisory user seat for EVERY participant who wants to speak. This might be great for meeting sales quotes, but it wastes the analysts' time and frustrates our spokespeople.
    • Of course, some suspect the Borg want to monitor useage and divert inquiries to less busy analysts. Forcing briefings to be booked as advisory sessions increases all the usage ratios. It's even better if analysts who don't know very much are used: then one inquiry turns into three or four. That's a massive waste of everyone's time, but it makes all the rations looks great (apart from next year's renewal figure).
    • Others have commented that the vendor briefing process is painful and is slowing down, not only for having to go through the Vendor Police (and having to fill in a form even if an analyst has informally pencilled in an appointment) but also being told in some cases that "the analysts were not available". We suspect that the system diverts requests from busier analysts to slacker analysts, regardless of their relevance. Therefore briefing requests either get declined or are accepted by analysts who want to look busy.
    • The policy seems to be increasingly endorsed and enforced by sales teams.
    • It seems that Gartner is also trying to discourage the use of SAS days for speaking engagements with tactics such as charging for travel time or bundling-in hyperinflated expenses, in addition to having dramatically increased the price. This of course prompts the question of value for money: how many more attendees can a vendor achieve by putting Gartner (or IDC, Forrester, Yankee...) on the speakers list? Will the choice of analysts affect the conversion rates?
    • The expenses figure added on by Gartner really irritates us. It's a random variable that cannot be backed up. If Gartner was an accounting firm, a method like this would have Gene's perp walk on the front page of the Journal.
    • The logic is of course to squeeze the lemon by boosting analyst utilisation rates (Gene Hall used the words "increase leverage").
    • Gartner however have reportedly capped spending to 3% per vendor (which at the present going rate represents a nice $30 million, leaving plenty of progression margin for their largest accounts) and restricted the products offered to vendors (no white papers for instance -with possible exceptions in far flung geographies though?).

    ARmadgeddon recommendations: with the Gartner Borg having as much as 40-50% market share, the RAS marketplace is now heavily concentrated. Vendors should strive to balance their RAS portfolio. Unfortunately, other global players such as IDC or Forrester are a far cry under Gartner for product breadth and brand recognition while regional players such as Ovum still fail to achieve the brand recognition they deserver because of poor marketing. Gartner is also hard to match when it comes to user reach and influence. On the events side, the picture is more contrasted, as the Symposia are certainly the largest but maybe not the most relevant/insightful and certainly not the best ROI. Research quality is more subjective (or maybe not?)
    Vendors should therefore have a multi-sourcing policy and use the Borg in conjunction with independent analysts on a case by case basis. They should also look at developping other influencers (such as bloggers, academia, etc...)

    Links:

    Thursday, 6 April 2006

    This We'll Defend

    Thinking back over the last few days here at Forrester's GigaWorld conference, the most passionate conversations have been about Gartner.

    Every market leader gets a hard time, and Gartner is no exception. Perhaps it's a measure of how bad things are that the troubles people complained of last year are now seen as the good old days. At the AR Council last weekend, they should have shown Jarhead.

    If my account manager is like the rest, the performance of Gartner's sales function has been really affected by new policies. There's a move away from the global sales approach. I can see that Gartner has an interest in deepening its relationships with a second line of clients in organizations. Perhaps Gartner think that clients like us, who are centralizing our buying from the analysts, simply increase our power and make things harder for them. That's not our view. When our buying was fragmented, we wasted a lot of money. We used to by a lot of research, sometimes twice or three times over. We didn't have enough scale to buy more advisory seats and more time from analysts. It's only that higher quality that allows us to really show Gartner's quality inside the company. The new approach suggests that Gartner loses the ability to meet the needs of buyers outside the center if it's selling to a global buyer. As a result, it wants to break down the global sales approach.

    Decentralizing sales could allow Gartner to sell directly into business units, geographies and subsiduaries. That trend will probably be strongest in enterprises, where Gartner is pushing role-based views. Gartner seems to think that the only way that most of these specialized role-based managers will be able to experience the impact of the new role-based services is if they pay themselves, and that not all central research buyers will care about the new role-based services.

    Of course, decentralization will displease a lot of central research buyers. It also poses questions of how to consolidate invoices and orders globally, and of how then to target and bonus local sales staff.

    All of this fits with the wider context at Gartner. John Moroney had some interesting things to say about this last month, and Duncan's post gives a flavor of John's conference call. Gartner faces high production costs in its research business and a deep challenge in sales force management. Much of the market is uncovered by Gartner's sales force, who are often remote from key, under-penetrated, market segments.

    Whatever happens -- whether the sales strategy is shown to be successful or not -- it will have to be tested by Gartner and then reverted back from. After 2 or 3 years, either clients will have been convinced centrally of the value of these role-based services, or they will have been terminated. So, although the probable fate of Gartner's sales team is a partial break-up, over 3 years we expect we will see it swing back to centralization. It's the classic Gartner scenario of permanent change.

    Monday, 3 April 2006

    Pay to play, the PR way

    Interesting article in yesterday's Sunday Times: Catfight at the 'backscratch club'

    It details how a well connected PR "guru", Julia Hobsbawm, set up Editorial Intelligence (EI) and invites columnists to advise companies in return of a £1,000 pa fee and organises relationship events to make all those people connect. It doesn't get much closer to bribing...

    Of course, Hobsbawm claims that "We are not selling access to journalists. Nor are we asking journalists to write puff pieces for clients.” but one would be naive to imagine that a columnist would not return a call after a "Caribbean freebies".

    Tuesday, 28 March 2006

    Ovum is floating -just about

    As we announced before, Ovum has now gone through their IPO on the 10th at 190 pence. Their stock shot up to 219 on the 12th and went back to 198 on the 24th in small volumes.

    Some in the industry have been speculating on what may happen next:

    • A mass exodus of suddenly enriched analysts?
    • An acquisition?
    • Aggressive development plans, for instance in consulting?

    Read also:

    Friday, 10 March 2006

    NEW: AR 101 feed

    In response to the success of our popular AR 101 series, we've introduced a specific feed, with a number of subscription options below. Note that any input and suggestions for upcoming topics is welcome.


    RSS (Atom + XML feed)

    Add to your MyYahoo!

    Subscribe in Bloglines Add to your Bloglines



    Tuesday, 7 March 2006

    AR 101 series: briefing analysts

    James, Jon and Andy kindly provided quite a lot of (free) advice on how to brief IT Analysts.

    Here are six simple steps to get your briefing right (tell us if we forget anything guys).

    1. Synch briefings with research agendas
    A good briefing should be prepared before to make sure that the information given to analysts match their research agendas and interests. This is of course easier done for one-on-one briefings (some simple filtering questions at the start help). For one-to-many briefings (not the preferred briefing for most analysts but often the most practical compromise to update analysts on announcements in a short timeframe) it is good practice to send 2-3 questions to key analysts before the call.

    Read AR 101 series: the research process for more. Jon made the following remark:

    • Take the time to understand research programs and assignments of the analyst firms you have in your sights, and use this information to make the correct people available to support the analysts that you meet. For example, if a firm is conducting a market analysis study, there is little point in providing a technical expert at a briefing; similarly, a brand manager will be of only limited use if a product comparison is taking place. Either of these situations may lead to the worst-case scenario of not being mentioned at all.


    2. Don't give analysts a dog's dinner
    Bear in mind that you may be talking to a diverse audience. Analysts fall into four categories: RAS analysts, market watchers, consulting analysts and sell-side analysts.

    So, as Jon says in this great post, you need to "Make Briefings Worth It":
    • "At the best of times, briefings can be dull for analysts as much as for vendors. This is often down to the fact that briefing sessions are inappropriate, badly planned or conducted."
    He suggests that a good preparation is paramount:
    • Only use source information that is relevant to the briefing at hand. Don’t waste anyone’s time in briefings, by slogging through irrelevant presentations that have been picked off the shelf
    • Customize your message before the briefing
    Analysts usually want to hear the following:
    • Corporate strategy
    • What are you announcing? (high-level messages AND product details)
    • How is that going to fit with the strategy and go-to-market model
    • How are you going to compete?
    • How does this fit with your announcement roadmap?
    And be flexible to respond to analysts prompts during briefings, do not hesitate to skip the introduction and go directly to the point. A common mistake is to explain granny how to suck eggs, for instance by lecturing numbers analysts (say from IDC) on market stats (say from Gartner/Dataquest). Andy illustrates this graphically in his post:

    • "That mistake is mostly made by smaller companies, where some VP or Director of Marketing is doing his (or her) run-of-the-mill pitch that would be equally used in any sales opportunity. So they go on and on about stuff that we have heard a million times already, have zero value to an analyst, and simply waste time. It's particularly annoying if those briefings are conducted via WebEx, because the analyst cannot [...] tell the vendor to skip to slide 32 [...]"
    • Vendors that do it very well [...] spend two or three minutes on chit-chat [...], then run through a few figures [...] and not more than 10 minutes after the call starts jump right into the product update, demo, or discussion.
    Read also the comments Vinnie, Dean and Jon have left here on the subject. We had the following bottom-line in the same post:
    • ARmadgeddon is against unnecessary analyst cruelty and agrees that vendors could do a better job at scoping briefings to better address analysts needs.
    Finally, read also: AR 101 Series: Don't use a sales presentation with analysts

    3. The best briefings are interactive
    Do allow time for analyst feedback during briefings ; bearing in mind that there must be something in for the analyst -the analyst should not feel like she/he is giving out all his IP for free. Bear in mind that analysts need to make a living and allow budget for buying reprints or getting the analyst under retainer. When the interaction is good, your company will gain a lot.Do not let short-term tactics waste this potential by making sure that your briefings are win-wins.

    As Jon writes:
    • If you are able to provide an analyst and his or her company with timely, tangible value, the analyst is more likely to have something to say about your company and your products.
    James made similar comments in his post Redmonk: how to brief analysts):
    • So, an analyst briefing is (should) a two-way conversation (otherwise it's called a press conference).
    4. Don't forget NDA's
    Analysts are interested first and foremost by future strategies and roadmaps. Do balance this requirement with the need to keep your job (and those of your executives) by being careful to flag what is presented to analysts under a non-disclosure agreement. Always keep the required paperwork at hand.

    Read also Ovum breaks the iPod cellphone embargo?

    5. Do a dry run
    As we've said before: NOBODY should be talking to analysts without going through a good AR training first. This should be a corporate policy. If you don't have the skills or the credibility to deliver it in house, get some professional help. For instance from Duncan or David (to name only some who linked to us), if you pick-up someone else, make sure that they know the European market (not like KGC).

    Furthermore, AR professionals should rehearse unless they're fully confident in the speaker's capabilities. This will not make them look appear as PITA's but rather as pros who need to make sure they avoid un-necessary risks.

    5. Follow-up
    Finally, do make sure that AR does the follow-up and stays in the loop -possibly by recommending that executives don't give out business cards. This should not annoy the analyst if you're responsive and has the benefit of being in a position to schedule additional briefings when required and stay abreast of the analyst agenda. This brings us back to step 1!


    Additional bedtime reading:


    Monday, 6 March 2006

    [deal architect:] Credibility of Analysts

    Vinnie has a special talent for finding the sweet spot and sharp comments.

    In this post, [deal architect:] Credibility of Analysts, he comments on the Borg IP police: the Gartner Ombudsman blog.

    They posted a lame rebuttal to the Information Week article on Analyst Credibility. The comments on that post (the Borg must be congratulated, yes congratulated, for having a real blog) are worth a read.

    Carter Lusher, the HP (HPQ) AR head argues for greater separation and transparency.

    Chris Carter (?) asks two penetrating questions, only to find deafening silence. Follow-on through to Vinnie's blog for more....

    Friday, 3 March 2006

    The Borg AR call

    We were hoping that Joe, Duncan or Dave would write a take on Wednesday's Gartner call as it was really quite dull... The only really funny thing was that Pamela Miranda referred to the Miranda act, so she must have read this Gartner Watch post.

    Laura McLellan, Gartner Research VP was first to speak. She covers vendor (IT providers) marketing strategies research. She started to say Gartner was not going to start to analyse AR (as the Oracle AR VP pointed out, this would be a conflict of interest) and compete with KGC.

    She had an interesting take on analyst taxonomy, depicting it as an inverted triangle: on top analyst which are end users focussed (advise buyers), in the middle market watchers (who look at forecasts and trends) and on the bottom (tip) the vendor focussed analysts (advise sellers). Quite why the triangle is inverted, we don't know -there may be more user facing analysts in Gartner but in the overall analyst landscape the vendor facing analysts outnumber them by far. ARmadgeddon will be publishing an official Analyst Taxonomy soon. She then said that you need to adapt your approach to the kind of analysts. Not exactly new news but maybe a useful reminder.

    She then further continued to explain grandmas (AR professionals listening into the call) how to suck eggs: one needs to segment the communication type to audience. Laura also plans to research which AR comms are effective or not and why. That would indeed make up for an interesting and more specific call.

    She gave a quick round up on what analysts love most: face time, AR contact list (inc. responsibilities), announcement advance notice / pre-briefing and email opt-out.

    She gave some insight on analyst psychology (gives a new meaning to analysing the analysts): they are motivated by influence and knowledge (explains the ego side) and turned off by community and reprocity (not sure what James will have to say on this).

    These other points were on her charts:

    • Semi-annual tours with topic managers to discuss the “bigger picture”
    • Portal to find “basics” without bothering AR person
    • On-line presentations and [important] transcripts
    • Upcoming events calendar
    • Annual executive sessions [access to the “big cheeses”]
    • Opt out “push” e-mails with the news
    • Access to your customer presentations

    Probably worth a reminder indeed. She finished by saying what makes a good AR person: being a good relationship builder. What does the R in AR stand for again?

    She gave the following good and bad for AR managers:

    • GOOD: Enabler vs. roadblock, Proactive, Accountable, Responsive, Truthful, Trustworthy, Empowered, Persistent, Follows up, Management confidante, Value creator, Helpful, Relationship builder
    • BAD: Defensive & suspicious, Gatekeeper (analyst = enemy), Unresponsive, Self-important (does not mix well with analysts?), Territorial, Siloed (not like Gartner then?), Roadblock, Inconsistent, Inaccurate, Don’t understand own organization, Don’t understand how analysts work, Not influential in organization supported

    She finally hinted that Gartner might create a research role to look at vendor marketing.

    The call then moved on to Pamela Miranda, Head of Vendor Briefings who spoke about briefings. She did not really cover the points that were on her agenda:

    • How to seek analyst attendance at your events
    • What’s the latest on vendor-paid travel
    • Focus: The most frequently misunderstood parts of the process


    Joe commented on the scheduling process here: Gartner's briefing on their briefing policy (Gartner Watch). As we've commented before, this process is lengthy and time consuming. One of the reasons that was


    Read also:

    Thursday, 2 March 2006

    AR 101 series: selling the value of AR

    As we previously wrote, AR is NOT an outbound tactic: briefing analysts and expecting them to write something is called PR and does only harness a small part of the value AR can deliver. However, few AR people feel confident selling the value of AR back to other stakeholders, such as sales and marketing.

    Here are a simple 5 steps guide to getting it right.

    Step 1: establishing AR
    AR often grows out of media relations and tend to have communication as a reporting line (this seems to be the prevalent model for small organisations). AR practitioners should seek to clearly differentiate their audience (read AR 101: Analyst vs. press) as it will impact management and stakeholders expectations.
    In this post (AR 101: Measuring Analyst Relations), we lay out three models for AR:

    • Outbound: pushing information out to analysts in the hope of generating reports
    • Transactional: pulling targeted analysts into a relationship with the firm
    • Insight: primarily using analysts to develop internal understanding and direction
    AR professional should strive towards establishing an insight-based AR practice and align with sales and marketing rather than with comms. See Duncan's tips here.

    Step 2: setting goals and measurements
    Thanks to Pavlov, we know that rewards conditions behaviours: it is crucial to align AR with sales and marketing goals. In this post (AR 101: Measuring Analyst Relations), we give the following recommendations:
    • AR's primary goal should be create a positive external environment for business
    • Focus and attention should be given to setting up balanced metrics to measure AR not only on raw clippings and quotes but also by weighting them to reflect the importance of the analyst, by surveying all analysts and through independent perception audits.
    • AR need long term objectives and can contribute positively to developing corporate strategies.
    Read also ANALYST EQUITY: Share of Voice: Useful, Often Vital.

    Step 3: impacting the strategy
    Well executed, AR can leverage the analysts privileged position and wealth of knowledge as a competitive advantage. Do use analysts to get a sanity check and/or coach execs, balancing independent analysts (they offer better value) from those having customer insight. Do schedule message testing sessions way ahead of launches (under NDA). Do allow time for analyst feedback during briefings (bearing in mind that there must be something in for the analyst, like buying reprints or getting the analyst under retainer). Do not let short-term tactics waste this potential.

    Step 4: Shaping the agenda
    Having engaged proactively with analysts should give your company clues about trends you might not have spotted before. This not only gives your execs the chance of fine tuning their strategy and messages, but armed with this knowledge you should be able to also synch briefings and announcement with the analysts' research agenda. Read also AR 101 series: the research process.

    Step 5: delivering to sales and marketing
    There are multiple ways for AR to help marketing. Do start by making sure that AR tactics are included into the marketing plan, it should also provide for analyst deliverables (such as speaking engagement, research projects, etc...) Do plan AR tactics way ahead of product launches.

    Do spend some time to explain how analysts come in the sales cycle and do raise awareness with the sales community so that they come back to AR when they hear of an analyst being consulted by the prospect or client. If you have followed step 4, you should be able to know where the analyst is coming from and what should her/his objections. You should thus be in a position to balance this with either positive research (from another firm or sometimes from the same firm) or to help sales refocusing the discussion. Remember that sales always get the kudos for wins and will try to deflect the blame for losses.
    Read also Reacting to an analyst attack and Advisory analysts do impact vendor sales and make/break products.


    Good selling!

    Wednesday, 1 March 2006

    Borg softens 30mn rule

    In an email today, the Gartner Vendor Relations (briefing police) and Ombudsman (IP police) appear to have read ARmadgeddon's posts on briefing length:

    • the 30 mn limit is now only a proposal
    • they recognise the vendor briefing request process is f****d-up, as vendors commented it leads to intolerable delays
    • analysts can extend the time if they deem it "required to obtain maximum value from the briefing"
    ARmadgeddon's comment: recognising a problem is a first step to correct it, we will be monitoring Gartner's briefing process closely in the coming months.

    In the meantime, there has been a lot of interesting comments on what briefings are and how long they should be, mainly here, there and there:
    • We agree with the analysts that vendors need to do a better job at briefings and to avoid death-by-powerpoint. Vinnie quite rightly says that briefings should be more focused ; that pitching to analysts is quite easier than pitching to the Wall-Mart procurement team.
    • There seem to be a consensus that 30 mn are okay for a quick update on a specific offering but does not allow enough time for wide-area-analysts (WAA, as opposed to Narrow Silo Analysts)
    • Dale and others however said that restricting briefings to a mere half an hour would eliminate the discussion. James argued that this was precisely what the Borg intended ; that it is an opportunity for independent analysts.
    We look forward to today's call where the Borg will share its recommendations for AR professionals, and more.