SAS(1) days (aka analyst consulting days, see definition) are a popular tool with many technology vendors. If done correctly SAS days can have a great ROI. If done poorly, a SAS day is a waste of time, money, and AR political capital. It also has the added risk of hurting your company’s relationship and standing with the analyst.
The business problems for the IT vendor community lie in the fact that neither the analysts nor the vendors have a good process in place to ensure that the analyst consulting day will deliver value to the client. Too often analyst consulting days are executed in a haphazard manner with little prior planning or even a formal agenda. In order to solve this problem, vendors need to take a more a systematic approach to deciding whether or not an analyst consulting day is even required and then executing the days purchased with more rigor.
The critical success factor to ensuring SAS success is for AR managers to take full responsibility for driving business value from the engagement. Taking responsibility also means managing colleagues as well as analysts. You need a process, best practices, checklists, and participant training to ensure your colleagues are fully prepared and in agreement with the desired outcomes for the SAS day.
In terms of the analysts, AR needs to work hard to ensure the analyst is fully engaged in preparing for the day and completing any follow up that you specify. AR also needs to work doubly hard to make sure the analyst does not try to stay for less than (more…)
Filed under: AR best practices | Tagged: analyst consulting day, analyst relations, AR, Gartner, SAS | 1 Comment »
As was briefly mentioned in