DesignOps with Coda
Share
Explore
Examples

Feature Request Ranking

At Coda we'll often use a scoring system to evaluate different improvements. Below is a sample we did for a ship-a-thon where we prioritized different improvements we could make in a single day coding event.
Papercuts
0
Search
Brief Title
Reach
Feedback
Simplicity
Team Nudge
Score
1
Change default level of precision for Numbers & Percents
13
2
Add min and max for gradient conditional formats
13
3
Disable auto complete on text formats
11
4
Add option to hide collaborative highlights
11
5
Increment names when you copy objects.
10
6
Change click behavior of section icons
10
7
Allow buttons in explore panel to be dragged into tables
9
8
Show hidden table names on hover
9
There are no rows in this table
Reach
5. Affects every user (Everyone can benefit from this change)
3. Affects some users (Some users in certain use cases can benefit)
1. Niche (and edge case)
Feedback
5. Hear it all the time (across all our feedback channels - Users, Codan's, Research)
3. Heard it from many people (lower frequency but consistently coming back)
1. Heard if from a few users or less (logged once, doesn't seem to churn users, less vocal)
Simplicity
5: Simple (simple to implement & design, low regressions)
3: Somewhat Complicated (general idea of how to do this, need to validate and refine)
1: Complex (unclear how best to solve it, requires buy-in, controversial, complexity in code area)
Team Nudge
We probably won't use this much, everything default to 1, explicit move up from team)
5: Strategic investment (Investment that could outweigh the other pillars)
3: Morale Booster (Codan's feels strongly about this and has logged it many time, harness activation energy)
1: No Nudge (default, let the other pillars decide, removes from this list after set)
Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.