Giving Product Feedback To A Ladybug

Earlier tonight, I wrote about something known as Ladybug. It’s a server-side application that certain parts of Microsoft use to track beta software bugs with their communities. The problem is: 99% of Microsoft’s beta software teams aren’t using Ladybug. This, in and of itself, is a bug. Old methods are outdated and far past their prime, and the Redmond giant is moving as slow as one by not adopting MSDN’s Product Feedback Center’s mechanism.

By going the Ladybug route, Microsoft will finally see which issues (read: bugs) are more important in the eyes of their most passionate users. They’re documenting what they know doesn’t work, and prioritizing what users care about most - and being completely transparent about it, instead of hiding behind a gigantic question mark (which does nothing but frustrate the very people who have to develop for and/or use products on your platform).

Microsoft would be eliminating guesswork, showing their various communities that they really do CARE about what users have to say, and giving them a feeling like they’re participating in the development of the product. It’s about as close as Microsoft is ever going to come to being open source - like Firefox (in IE7’s case).

When I file a bug right now, I have no idea if the right person has seen / heard it, nor do I know how many other users feel the same way I do or see the same thing I see. That’s frustrating to the point where I don’t even bother to submit bugs anymore. What’s the point, if I feel they’re falling into a void (even though I know that if I direct it to the right person, it’s not likely falling on deaf ears).

Change the paradigm, Microsoft. You’ve already got the killer tool for it.