It is critical for Analyst Relations (AR) to thoroughly research a particular Magic Quadrant and its history. Even AR staffs that have been working with Gartner on a MQ for a long time could benefit from doing a little digging into the background of the MQ in order to separate reality from faulty memory and myth.
Kea Company Technique:
Talk with the analyst – Obviously, AR should be interacting with their Tier 1 analysts on a regular basis on a number of issues. In many cases being in charge of a MQ means automatic Tier 1 status for a Gartner analyst. Many of those interactions will provide valuable insights into the MQ and the analyst’s criteria for it. However, there needs to be a dedicated call on the MQ* that occurs once a quarter. Topics to be covered include:
- Changes in the analyst’s responsibility, new additions to the team, both creation and peer review
- If you are on a Magic Quadrant with more than one author, what is the currentrelationship between the multiple authors and how is that evolving? Will that impact your position?
- Changes in criteria, weights and assumptions
- Analyst’s vision for the market
- Whether new MQs will be created that overlap this space
- Next publication date and format
- What you have to do to move in desired direction
- What the competition is doing to leapfrog you
- Danger signs
- Strengths and weaknesses of the players on the Magic Quadrant
- Necessary proof points to meet criteria.
A tricky insight to obtain from analysts is the team dynamics. Often you have to approach this issue indirectly.
During these MQ intelligence-gathering calls, do not argue with the analyst about your company, your products, position or criteria. Because these are regular quarterly calls you don’t want the analyst to feel uncomfortable when they see it on their calendar. Nor do you want the analyst to act defensively during the call. Rather use this call to gather needed information that will help you plan future interactions. After each quarterly call, you should send an e-mail to the analyst documenting what you heard. This will provide an audit trail in case there are disagreements in the future about whether or not your company should have a more favourable positioning on the next MQ.
* Kea Company clients can schedule an inquiry to help you prepare for your quarterly analyst calls and then analyze what you heard.
Bottom Line: It is important for AR teams to do their homework to stay on top of evolving criteria and assumptions. Assuming that you know what the important underlying criteria and assumptions are for the Magic Quadrant without talking to analysts can result in work to create proof points for your company that does not matter. Just reading the Research Notes is not sufficient, as the most important criteria are often not captured in written format. Savvy AR professionals will be in frequent contact with the analyst seeking intelligence about the market in order to anticipate changes in criteria and assumptions.
Question: Do you have regular calls with analysts in charge of relevant MQs to determine how they perceive the market is changing and how this will impact the criteria for a MQ?
This post is one in a series about tech vendors and their relationship with the Gartner Magic Quadrant. In addition to this series, there is a Kea Company Guide to the Magic Quadrant that helps research consumers – whether enterprise IT managers or vendors – make appropriate use of this most famous and misused research deliverable.
With this series I want to build on the excellent work that Dave and Carter did at SageCircle. The MQ is relevant today and many tech vendors struggle to get their strategy right. This alone is enough to warrant further exploration of the topic.
This post originally appeared on LinkedIn. It is part of a series of 7 articles on the Gartner Magic Quadrant. Other parts can be found here.
Ready for more? Subscribe to Kea Company’s Influencer Insights
Join hundreds of peers and get Kea Company’s latest blogs, webinars and downloadable content straight to your inbox. Enter your email address below:
[contact-form-7 404 "Not Found"]