This post is a response to Tom LaRock’s (Blog | @SQLRockstar | SQLPeople) awesome idea: Meme Monday.
… I would like a revamp of Microsoft Connect. Feedback is part of any good Continuous Improvement endeavor. I like the idea of Connect – a lot. It’s a decently-designed portal, in my humble opinion. It allows me to report issues and request functionality with SQL Server. That part all works fine.
I would like for Microsoft to change the way Connect Items are managed and the communication around the status of filed items.
I think we need more statuses. “Closed Won’t Fix” sounds a little harsh, don’t you think? “By Design” sounds like “You’re Doing It Wrong”. Maybe I’m just being sensitive here. Instead, how about:
- We agree it is a bug but we do not have time this cycle release, we will file it away for the next release or SP.
- We agree this is a bug but we do not think many will encounter this issue.
- This is something we didn’t consider.
- We do not think this is a bug.
Perhaps it would be enough if every closed bug required a non-generic explanation of why it was closed.
I ask that the good people at Microsoft consider my meta-feedback: I believe they are smart enough to make this really cool feedback site more useful. I bet if they do, they will get more and better feedback – especially from people who anxiously anticipate each new Release Candidate (RC) or Community Technology Preview (CTP) of The Next Cool Thing.
As it stands, Connect is mostly an engine of loss. I sincerely hope “Connect Items Closed” is not a metric in some variation of Performance-Based Management (PBM) for the development teams at Microsoft. Why? Because impeding open and honest feedback is a quality-killer (a lot of PBM kills quality – go read that post).