Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20019

A word of thanks to SolarWinds about WWWO section

$
0
0

Hello,

 

This is a simple letter with one single goal; to thank SolarWinds for the creation of the What we're working on section.  It is very refreshing and commendable to see the level to which SolarWinds encourages and supports input from anyone (whether a current customer or a potential one). Here at my firm, we work with several other major application vendors whose names I won't mention to avert legal action  .  One thing I can say is that I've never seen other application vendors encourage input about their products to the extent that SolarWinds does.  Yes, other vendors have user forums, but none of them allow users to vote on each others' ideas. 


Imagine this; we are even able to interact directly with each of the SolarWinds' product managers and voice our concerns and/or requests to them.  This excellent, since it allows SolarWinds (and its customers) to have a good grasp of which ideas they should focus on.  Of course, none of us are perfect and there will always be something that we could do better -- SolarWinds is not exempt from this.  Even I have a small gripe that I have with them:


  • Some of the WWWO pages do not get updated as frequently as I'd hope.  What's more, sometimes, it seems as if those pages are not updated until several customers enter repeated comments requesting them.  Fortunately, this only happens with a few WWWO sections, for which I am most definitely grateful.


Again, perfection is something we should continue to strive for, and some may spend their whole lives striving towards that goal.  So, I want to end this letter by simply thanking SolarWinds again for the creation of the WWWO sections. Please, continue these great forums and many thanks for your willingness to hear our us!!! 


Viewing all articles
Browse latest Browse all 20019

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>