Thread by @fab_biscotti

Have you ever wondered how we craft the @Gartner_inc market shares for Application Infrastructure and #Middleware?
gartner.com/doc/4000910

Let me tell you...

@Gartner_inc Step 1. #Segmentation: in June/July we discuss if the segments we have reflect the way end users buy products. If not we do change the segmentation. or adjust it or refresh the naming

@Gartner_inc Step 2. #Vendors: Between August and October we consider which vendors to add or drop. We do take into account M&As, up-and-coming vendors, vendors that have changed focus. We ask our end-user focused colleagues (typically the authors of an MQ) for their input.

@Gartner_inc Step 3. #Information Gathering: In December we review all the publicly available information (Jan-Sept quarterly financials, major announcements etc.) and the internal info (our notes from vendor briefings & vendor events and any other non-NDA info gathered through the year)

@Gartner_inc Step 4. #InitialEstimates (Part 1): we (the vendor focused analysts) draft the initial estimates segment by segment (e.g. #iPaaS, #aPaaS, #RPA etc.) and vendor by vendor. It's bottoms up based on the previous year consolidated and published estimates.

@Gartner_inc Step 5. #InitialEstimate (Part 2): we sit down with the end user focused analysts (the authors of the MQs, basically those who talk to end users all the time) and we validate and/or restate the initial estimates by segment (e.g. #iPaaS, #aPaaS, #RPA etc.) by vendor. Line by line

@Gartner_inc This is important because "end user analysts" have a sharp focused pulse on end user inquiries of the very customers of specific vendors. They also know well product features and functions, the product readmap and any positive or not so positive user feedback.

@Gartner_inc This part of the estimation process is the real deal: both the vendor focused analysts (@fab_biscotti and @BhullarBindi in this case) and the end user focused analysts need to agree or, if the worst comes to the worst, find a middle ground perspective.

@Gartner_inc @BhullarBindi Step 6. #InternalReview: December: the "negotiated initial estimates" are presented to several Research Communities related to the AIM market (Integration, API management, process automation etc.). The community scrutinizes the numbers and a consensual view is established.

@Gartner_inc @BhullarBindi This is when any major issues with the initial estimates are discussed. Research communities can have over 30 analysts. All these analysts have a perception on how the market is doing and how vendors are performing. Brought together, these perceptions become our view on a market

@Gartner_inc @BhullarBindi Step 7. #ExternalReview: at this stage we have an educated set of estimates commonly agrred and vetted by the research communities of multiple analyst. We send the estimates to the vendors. The process is traced and back and forth emails are stored for auditing purposes.

@Gartner_inc @BhullarBindi Caveat: if we know a vendor publishes the end of year financials on a specific date (between January & March), once we have the publicly available numers we circle back with the research communities and highlight any differences with the initial estimates (in case there are any)

@Gartner_inc @BhullarBindi Step 8. #VendorFeedback (or lack of it). It does occur via email or via a call. We take notes and circle back to the end user analysts in case this feedback diverges significantly from the initial estimates.

@Gartner_inc @BhullarBindi At this stage we triangulate between the vendor and the end user analysts (and the entire research community with an email discussion) to find an agreed view on the estimates. If we cannot agree (with the vendor), we'll go with the consensus based view of the research community.

@Gartner_inc @BhullarBindi Step 9. #FinalReview. It is now March and the initial estimates have been vetted by vendors. We roll up all the data and share (again) the data with the relevant research communities. At this point there should not be any surprises in the numbers. Market shares are published.

@Gartner_inc @BhullarBindi So, as highlighted, it is a consensus based process. Operationally led by vendor focused analysts but from a content perspective is a COLLECTIVE exercise. Material errors can happen and it ain't a science. But, even if it is not an MQ... it needs #Archat attention. My 2 cents.

@Gartner_inc @BhullarBindi BTW allow me to take the opportunity to thank several folks who help us crafting the market shares: @BhullarBindi @mpezziniGartner
@TheMarkONeill
@fintanr
@BLheureux
@KeithG_Gartner
@ynatis
@AnneWoof
@PaulVAtGartner
@egolluscio
@arunbatchu
@mobilegourmet
@adrleow
@metamurph #FF

@Gartner_inc @threadreaderapp unroll