Blog Post
As long as this we can opt our, sure. I don't want that popping up for our C-level customers. At all. Ever.
I also agree to the posts above that suggest the feedback should be available to the app admins.
Honestly, though - I don't see this as a successful approach to eliciting valuable user feedback that will help drive product improvements. What you're rating is less QB and more the ability of the app admins / developers to build things - which is delicate because there are some areas in which QB is severely limited and it hurts the overall user experience. If you read the discussion forum you see hints of the same themes over and over. "How do I?" "Can we?" For every one of those there's either an implied UX challenge ("how do we make that more obvious?" - ex: setting a field to use a pick list, report link fields, modifying reference fields in relationships, etc.) or a possible product enhancement ("yeah - maybe we need something like that" - ex: regex support in formulas, reports as members of the toolbar [I'd so love that...], distinct results in reports, formula fields in section/tab titles, etc.). All of that impacts our ability to deliver a quality UX - but users won't know that. They're not rating QB. They're rating the app admins / developers.
Maybe you should consider surveying the app admins / developers? We have a pretty good handle on things we hear from users and think would be valuable additions to the product.
Yes - I know the user voice submission and voting process is there. To me that just seems like a parking lot and not an effective way to manage the feedback process.
You guys are doing great work improving with these incremental monthly updates. Let us help you with that. We know our pain points and many times they result in user challenges. Sometimes ones we can't fix right now.
I also agree to the posts above that suggest the feedback should be available to the app admins.
Honestly, though - I don't see this as a successful approach to eliciting valuable user feedback that will help drive product improvements. What you're rating is less QB and more the ability of the app admins / developers to build things - which is delicate because there are some areas in which QB is severely limited and it hurts the overall user experience. If you read the discussion forum you see hints of the same themes over and over. "How do I?" "Can we?" For every one of those there's either an implied UX challenge ("how do we make that more obvious?" - ex: setting a field to use a pick list, report link fields, modifying reference fields in relationships, etc.) or a possible product enhancement ("yeah - maybe we need something like that" - ex: regex support in formulas, reports as members of the toolbar [I'd so love that...], distinct results in reports, formula fields in section/tab titles, etc.). All of that impacts our ability to deliver a quality UX - but users won't know that. They're not rating QB. They're rating the app admins / developers.
Maybe you should consider surveying the app admins / developers? We have a pretty good handle on things we hear from users and think would be valuable additions to the product.
Yes - I know the user voice submission and voting process is there. To me that just seems like a parking lot and not an effective way to manage the feedback process.
You guys are doing great work improving with these incremental monthly updates. Let us help you with that. We know our pain points and many times they result in user challenges. Sometimes ones we can't fix right now.