67
Ability for admins to weigh/prioritize requests
planned
Activity
Newest
Oldest
C
Cassandra Summer
@Sarah Hum do you have an update on when this will be released? Our company is contemplating moving off of canny because this feature is not available.
Sarah Hum
@Cassandra Summer: Hi Cassandra, thanks for the nudge! It's a big feature because everyone prioritizes differently and we don't want to rush it. I'm actively looking to have conversations with teams to understand this better. Do you have time to chat? https://cozycal.com/sarah/chat
Sarah Hum
Merged in a post:
Add an Estimate field
Paul May
We're using jira and canny together and our hope is to split the process as follows: 1) conduct decision-making about new feature prioritization in canny, and 2) once we decide where a feature slots into the schedule, move it into jira.
The problem is that, other than notes, we don't have a way to enter estimates in canny. So when we have our weekly meeting, I either have to export them to google sheets or I have to create jira issues for them. Both of these options are time-consuming and they mean I'm not managing them in a single place.
Sarah Hum
planned
Hello everyone, happy 2020! We're planning to make a bunch of improvements around Canny this year—including this! Please reach out directly or comment here if you have additional thoughts on this feature. Otherwise, stay tuned for more updates!
Julien Berthomier
@Sarah Hum: We've recently tested https://airfocus.com/ for our internal roadmap prioritization. I must say their scoring system is really good. I would def benchmark what they did to get inspiration. It's simply based on the RICE method with a fully customizable 3 factor system (see ours attached). There might be ways to simplify it further.
Sarah Hum
@Julien Berthomier: Thanks for sharing this Julien! We've been thinking about this specifically for the last couple days. We're considering keeping it simple initially with prescribed, fixed-weight scores (eg. we determine the formula). How important is it for you to be able to customize your own weighting?
Julien Berthomier
@Sarah Hum: At first I didn't think it would matter too much but as we prioritized for our next launch yesterday with the team, weight became a big deal. We typically prioritize for different contexts (batch of bugs, launch, etc.) and depending on the context we might want to put more weight on one factor over another (ex: for our 2.0 launch the "wow effect" would have to matter more than in other contexts.
Sarah Hum
Merged in a post:
Custom fields for posts for admins
B
Basil Weibel
When discussing Canny with our devs, they point out, that they would like to store certain infos like
- Link(s) to github issues
- story points
- engineering work hours to deliver
- sales value
- Number of bugs / problems a feature solves (for us a new feature often replaces an older more error prone module)
- etc
with posts. Now I think this should be internal fields. It would be very similar to "Estimated dates for posts" but really generalized for any kind of custom field, not just dates (but keeping the internal/external tickmark). https://feedback.canny.io/feature-requests/p/estimated-dates-for-posts
I would expect this to behave pretty much the same way as segmentation for according to user attributes, but it would segment based on post attributes. In terms of interface, it would sit in the admin view on the left either in the segment part or as new part at the bottom (see attached mockup).
R
Rick van den Dijsel
Currently, I'm putting the effort of a feature/idea (post) into the internal comment section. This is difficult to see and allows me as a Product Owner to always open the feature/idea to see it. It would be nice to have a separate field with this value in a feature that is visible in the post list. In my opinion, this can be a text or number value so that anyone can choose between a numeric system like Fibonacci or text high, medium, low as an example. We can use this weight to communicate to the customer why we don't want to do a certain feature. Most of the features recommended by customers are worth to investigate but most require a lot of effort to implement which makes the feature less attractive.
Sarah Hum
Merged in a post:
Enhancement weightings / dashboard
J
John McMahon
I'd like the ability to add custom weighting categories and scores in Admin View. Example below where four custom weighting categories have been added:
1) Dev Effort: Small (-5) Medium (-15) High (-30)
2) Increase Revenue: No (-5) Indirectly (5) Yes (15)
3) Strategic: Yes (20) No (0)
4) Retain customers: Yes (20) No (0)
This would allow one of our dev team to set 1) and one of our product managers to indicate 2)-4). Resulting in a total weighting being set which is relatively objective.
With this in place you could have a real time report / dashboard of which things look best to do based upon more than just votes/hunches.
Julien Berthomier
Hi there! Has this been prioritized by any chance? We've been looking at different tools and this is the one key feature we miss to switch to Canny.
Gathering feedback from the community is essential but as a PM or founder you know context that users don't (ease of implementation, strategic alignment, etc.). Being able to override the public votes with a scoring of your own is key to better prioritize in some cases.
ProductBoard offers custom scoring but it is not designed for gathering public feedback and it's quite overwhelming to use. In contrast, your UX/UI is out of this world!
Custom scoring 🙏🤗😍
Congrats on such a great product!
Andrew Rasmussen
Thanks for posting!
This one seems similar to https://feedback.canny.io/feature-requests/p/vote-types---sentiment, would you agree? I'm thinking about merging them.
Michelle Darmetko
@Andrew Rasmussen: I would disagree. This is a tool that would allow say a product manager to apply metrics to the feature. Like high score for impact and low score for effort would be an easy win.
Drew Libin
@Andrew Rasmussen: I agree with Michelle here. I think it'd be great to separate these. For instance, our users are eagerly demanding a high-functioning Android App. It'd be great to contextualize the effort required in some way.
Mike Lauf
Love this idea and was going to add it, myself! Personally, I use a 4 point weighting system - 1 = high effort, low impact, 2 = low effort, low impact, 3= low effort, high impact, 4 = high effort, high impact.
Simply multiplying the weighting by the number of upvotes would go such a long way in being able to more easily prioritize our roadmap.