Prioritizing Feature Requests for Beginners: Vote With Role-Colored Dots Before You Decide

Project & Development

Prioritizing Feature Requests for Beginners: Vote With Role-Colored Dots Before You Decide

A beginner template for small web-service teams (5 to 10 people across product, development, and support) to rank incoming feature requests at the start of each quarter. The whiteboard has four A4 pages. Page 1 sets the quarter's goal and available people and gives each role a dot color, page 2 gathers requests in a table and votes with role-colored dot stamps, page 3 counts votes per role, discusses the differences, and sorts requests into four levels (MoSCoW), and page 4 gives each chosen improvement an owner and a date and drafts replies to customers. The task board has five columns - request inbox, discussing now, building, verifying, and announced - with 4 parent tasks, one per page, and 12 subtasks. When you are unsure how to prioritize feature requests, do not decide by the vote total alone. Look at which role voted most, because a split vote is the one worth discussing. Keep Must to what fits your available people.

0 Likes 0 Copies Author: WeProcess
feature requests prioritization MoSCoW voting product development
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Prioritizing Feature Requests for Beginners: Vote With Role-Colored Dots Before You Decide

Whiteboard preview

① This quarter's goal, available peop... ② Support's color (orange dot) ③ Development's color (blue dot) ④ Product's color (green dot) ⑥ Request list and votes (collect fro... ⑦ Requests support adds ⑧ Requests development adds ⑨ Requests product adds ⑩ Votes by role (count the dot stamps... ⑫ What to say about split requests ⑬ Rules for sorting ⑮ Improvement x owner x due date x ho... ⑯ Replies to customers (reply on both... Feature Request V... How to use (4 pag... Goals and chosen ... Rules and owners Customer pain points Viewpoint gaps an... 1/4 Set the goal and ... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Collect requests ... ↙ 3/4 This quarter's goale.g. Cut cancellation-relatedinquiries from 30 to 15 a month People for improvementse.g. Of 3 developers' 12 weeks,about 6 weeks can go to improvements Decision day and processe.g. Decide in 60 minutes on April 8.Limited-visibility team members can write together e.g. Three support staff take part Up to 3 votes per person, and at most 2 on the same request What to look at is how many inquiries and how much customers struggle e.g. Vote for requests that come in with the same question every month e.g. Three developers take part Up to 3 votes per person, and at most 2 on the same request What to look at is the effort and whether other features might break e.g. Vote for requests that help many people for little effort e.g. Three product staff take part Up to 3 votes per person, and at most 2 on the same request What to look at is fit with the goal in ① and whether more people keep using it e.g. Vote for requests that are a reason people cancel ⑤ Where requests ... Customer feature requests Contact form e.g. About 80 a month. Support sorts them Support email e.g. Requests that came up mid-conversation Sales and meeting notes e.g. Voices of customers unsure about adopting In-app feedback box e.g. Short comments sent from the top right of the screen Social media posts e.g. Found by searching the service name Cancellation survey e.g. Requests written as the reason for leaving Request (in the c... Count and where i... Who is struggling Votes (place dot ... Request 1 e.g. I want to export invoices as PDF e.g. 24 (form 18, email 6) e.g. Accountants who rebuild invoices by hand every month e.g. Orange 3, Blue 1, Green 2 Request 2 e.g. I want to bulk-register users by CSV e.g. 15 (feedback box) e.g. Admins of teams that started with 20 or more people e.g. Orange 1, Blue 0, Green 3 Request 3 e.g. I want to turn off notifications by type e.g. 11 (social 7, form 4) e.g. People who miss important messages in the noise e.g. Orange 2, Blue 2, Green 0 Request 4 e.g. I get logged out too quickly e.g. 9 (email) e.g. People who use it on a phone while out e.g. Orange 2, Blue 3, Green 1 Request 5 e.g. The admin screen is slow e.g. 5 (sales notes) e.g. Larger customers with a lot of data e.g. Orange 0, Blue 2, Green 1 e.g. The steps for a forgotten password are hard to follow Write what you often hear in inquiries but is not in the table on ⑥ Once written, add a row to the table on ⑥ and everyone votes again e.g. Replace the old payment mechanism with a new one Write things customers cannot see but would cause trouble if left alone Once written, add a row to the table on ⑥ and everyone votes again e.g. Add more how-to guides for people trying the free plan Write what is close to the goal in ① but no customer has asked for yet Once written, add a row to the table on ⑥ and everyone votes again 3/4 Sort by viewpoint → 4/4 4/4 Build and reply Support (orange) Development (blue) Product (green) Which role it lea... 1st request e.g. Invoice PDF: 3 votes e.g. Invoice PDF: 1 vote e.g. Invoice PDF: 2 votes e.g. Even (all three roles voted) 2nd request e.g. Login: 2 votes e.g. Login: 3 votes e.g. Login: 1 vote e.g. Leans to development 3rd request e.g. CSV upload: 1 vote e.g. CSV upload: 0 votes e.g. CSV upload: 3 votes e.g. Leans to product (development has 0 votes) 4th request e.g. Notifications: 2 votes e.g. Notifications: 2 votes e.g. Notifications: 0 votes e.g. Only product has 0 votes ⑪ MoSCoW (sort in... MustEssential e.g. Invoice PDF. Must build this quarter. Place only what fits the people in ① ShouldImportant e.g. Login. Build this quarter if people are left over CouldIf possible e.g. Turning off notifications by type. Build when there is free time Won'tSkip this time e.g. CSV upload. Do not build this quarter; talk again next quarter e.g. For CSV upload, product sees it preventing cancellations, while development sees 4 weeks of work Each role that placed many votes and each that placed none gives one reason Talk about the request, not the person Keep Must to what fits the people in ① For a request only one role voted on, place it after talking Do not delete skipped requests; review them next quarter ⑭ Build stages (m... Decide spec e.g. Product and support decide the fields on the invoice PDF Build e.g. Development builds it in 2 weeks, with one demo along the way Verify e.g. Support tries it with real inquiry examples Announce e.g. Release notes, and a message to the people who asked Improvement (from... Due date How to check Current stage (on... Improvement 1 e.g. Invoice PDF: 1 developer and 1 from product e.g. May 20 e.g. Invoice inquiries drop to 10 a month or fewer e.g. Decide spec Improvement 2 e.g. Login: 1 developer e.g. June 10 e.g. Complaints about being logged out drop to 3 a month or fewer e.g. Build Improvement 3 Improvement: ____ Owner: ____ Due: __/__ e.g. Write it in a way you can check with numbers e.g. Not started yet Improvement 4 Improvement: ____ Owner: ____ Due: __/__ e.g. Write it in a way you can check with numbers e.g. Not started yet Reply for a request we will builde.g. We will make the invoicePDF export available in May Reply for a request we passed one.g. We are skipping bulk registration this time,but will consider it again at the July review What carries over to next quartere.g. If skipped requests pile up,always add them to the table in ⑥ next quarter → 2/4 Collect requests ... ↙ 3/4 Sort by viewpoint → 4/4 Build and reply
100%

Drag to move, scroll to zoom

Task board contents

Request inbox 16 items

Set goal & colors
Collect votes
Sort by viewpoint
Build in order
Write goal & people
Pick role colors
List sources
List requests
Vote with dots
Add by role
Count by role
Discuss splits
Sort into 4 levels
Assign and date
Move by stage
Reply to customers

Discussing now 0 items

Building 0 items

Verifying 0 items

Announced 0 items

← Back to templates