The Neverending Quest for Feedback


Microsoft bloggers frequently blog their interest for receiving your feedback on ideas to improve our products and content. Of course, this is mutually beneficial; you obtain a product that meets your needs, and we enjoy the benefit of selling a product people want.

Most Team System bloggers have blogged on topics that included requests for feedback, or mentioned the value of feedback received. Here is just a sample from the past few days:

Here’s an example from outside Team System, but from a blog I follow:

Last week we also hosted an online chat, which gave over 100 people the opportunity to interact with members of the product team in realtime to provide feedback and raise their favorite issue. Either respond to the blog posts above, participate in the next online chat, or simply visit Microsoft Connect to let your voice be heard.

1081

Tags:  | | |

Comments (5)

  1. Sometimes a little leadership is needed. Sometimes it seems like Microsoft wants the customer to find the problems, offer solutions for the problems, and even (as in Codeplex) fix the problems.

  2. DaveS says:

    Hmm – here’s a frustration with feedback – on a couple of occasions I have made suggestions via the feedback site that are fairly simple things that could be done to "match" capabilities that competing products have (that we miss since migrating) – on those occasions my response is "Closed" and "Not going to fix" with no explanation – some reasoning as to why would be nice.

  3. Aaron Hallberg on Team Build API: GetBuildURI and GetBuildDetails.

    Brian Harry on The Next TFS Power…

  4. RobCaron says:

    As in any other software development organization, we go to great lengths to find and fix issues in our products before we release them. However, for a product as large as Team System, absolute perfection is not realistic. See this post by Irene Fran from the Visual Basic team, Battling Bugs: A Glimpse of “VB War” (http://blogs.msdn.com/441841.aspx). But not all feedback is about identifying issues. It’s also about feature requests, capability improvements, and even the elimination of features (see Clippy).

  5. RobCaron says:

    btw, if you submit feedback in Microsoft Connect and the only response you received from Microsoft was to close the issue, and mark it "Not going to fix" without explanation, that’s a problem. I recognize the effort it takes to submit feedback, and I think we owe you more than that.

Skip to main content