Motivation
With limited resources, we need to direct effort to the right places to develop features that our users want. Though we can have propose and make a hypothesis on what features people want, the cost of a developing something people do not want is rather high.
Hence we propose a data driven approach to include users in the feature decision process. We will include ways for users to cast votes on features that they want within the app.
Details
In order for this method to be effective, the will be a few new processes and components.
All product features will need a proposal document to outline what the feature is. This document will then be linked to the the place in the app where the feature will likely be displayed. We will then integrate into the existing “coming soon” component with a support and details button.
The support button will add a vote for the user on the feature. Number of votes per user can be decided on engineering limitations.
The details button will link to the details to the feature being proposed. Comments on these pages are nice to have and not a hard requirement.
Within the coming soon component can also be a quick summary of the feature and get people excited about the feature.
Mock up
Blog organization
Our engineering blog will be where we post the feature requirements (as well as engineering decisions linked to the feature).
Every feature will (ideally) have a product document and an engineering document. they will be categorized under the their respective category (product and engineering).
Documents related to the same feature will be under the same tag.
So if you want to see all documents related to the feature, you can look under tag their tags. This will also be where the details button will lead to. the tag linked to the feature. not the actual product document.
Admin Panel
Once we get the data, we will need an admin panel to consolidate this data and choose which feature to focus on. Hence an admin panel need to be constructed to show this data.
The admin panel will contain the following:
- feature vote counter
- heat map?
just basic for now. base on counter we will allocate development time.
Other requirements
We want to record the users vote. So we can notify them when a certain feature is released for them to try.
Status
[>] In Review
[-] Technical Design
[-] Development
[-] Testing
[-] Live