These are great feature requests. In order for this process to add value to the RICOH product development, we need to both organize the feedback and then present it to TK, the RICOH product manager. I feel that that present to TK portion is going smoothly as he is open to having meetings with us to review the feedback. Also, we have the poll data to help him send summary information to the RICOH engineers and executives in Tokyo, both as email and during meetings with them.
The poll is a great advancement in providing summary feature requests. I think we next need to work on how to get individual feature requests into the poll. I foresee us running into these problems:
- we'll start missing feature requests like the many you have in the post above and these requests never get into the poll due to human error on our side
- the poll becomes long and cumbersome
My current idea to meet these challenges:
we store the feature requests into something easier like a spreadsheet or database (which is probably not going to happen in the short-term). The spreadsheet could be a google sheet and possibly inputted with a Google Form. That way, we can easily compare the October poll bullets with the requests for new features
we break up the poll into different polls and just run one section each month. For example,
- RICOH mobile app.
- cloud-based viewing site.
For now, I think our current system is doable. However, we may want to address these issues before the October poll.
It's a bit unfortunate that Discourse doesn't have more advanced group collaboration features that would help us to build the poll collaboratively. We could put the Oct poll up as a Google Doc to collaborate and then copy that into Discourse.