I wish to apologize for all of the demos I have somehow disrupted, those in the past and I am sure, in the future.
I see a lot of vendor briefings as an analyst. A disturbing number of them go wrong. I cannot count how many times I heard the phrase “Haven’t seen that before…” or “Can you see anything?” or “It worked this morning.” My favourite is “We just released a new build, and it might not be completely stable,” as the software crumbles into a smouldering heap of bits.
Or worse. Just this week, a very proud web conferencing vendor wanted to show me their flashy new version. It did look good, until it crashed my machine with a Blue Screen of Death, the first one of those I have seen in several years. That day also saw the second and third time I saw it, until we finally gave up.
I’m not sure why, but I am prepared to believe it is my fault somehow. I spend a lot of time in the mountains, which makes for sometimes dodgy Internet connections. Maybe that is what does it.
Maybe its just my karma. Whatever the reason, I am sorry. If I could make it stop, I would.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Gartner Top 10 Strategic Technology Trends for 2016
Strategic technology trends are rapidly changing disruptive trends with significant potential for enterprise impact over the next three...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.