Blog Post
this is great input and we are tihnking a lot about this. it is apparent to me that a few tihngs are true...
first, i think that within our product team, there is a great deal of work we are doing to constantly try to listen and gauge user feedback and interest in different areas of our product.
also, we are working hard to make the best prioritization decisions we possibly can, and this invariably means tradeoffs. for example, we specifically chose to focus on bringing the new Grid and Exec Dashboards to market ahead of the work we're planning to rethink Forms. and we intentionally chose that because we thought that prioritizing making Quick Base more approachable for end users is for now slightly higher in importance than making Form building better. that's just one example, among hundreds of others, around us making prioritization decisions.
now all that said, it is also very apparent to me that there is more we can and need to do to provide more transparency to our community around what we're choosing and why. part of this is more engagement on the community. part of this is probably me doing more blogging and updates as to our roadmap, adjustments on bug lists, uservoice intrepretation and choices, etc. I think the net net is that we need to communicate out more often from Product to you as to what we're choosing to do and how we arrived at that prioritization. I want us to get better here, but I don't yet have the concrete plan on how (yet).
I appreciate very much the input though!
first, i think that within our product team, there is a great deal of work we are doing to constantly try to listen and gauge user feedback and interest in different areas of our product.
also, we are working hard to make the best prioritization decisions we possibly can, and this invariably means tradeoffs. for example, we specifically chose to focus on bringing the new Grid and Exec Dashboards to market ahead of the work we're planning to rethink Forms. and we intentionally chose that because we thought that prioritizing making Quick Base more approachable for end users is for now slightly higher in importance than making Form building better. that's just one example, among hundreds of others, around us making prioritization decisions.
now all that said, it is also very apparent to me that there is more we can and need to do to provide more transparency to our community around what we're choosing and why. part of this is more engagement on the community. part of this is probably me doing more blogging and updates as to our roadmap, adjustments on bug lists, uservoice intrepretation and choices, etc. I think the net net is that we need to communicate out more often from Product to you as to what we're choosing to do and how we arrived at that prioritization. I want us to get better here, but I don't yet have the concrete plan on how (yet).
I appreciate very much the input though!