86
Ability for admins to weigh/prioritize requests
in progress
Michelle Darmetko
Give the ability to weight requests (say impact & effort, or customizable). This will allow users to prioritize their list of requests. Bonus points for displaying it on a matrix.
Sarah Hum
in progress
This was a tricky one to design but we're excited to build out our solution. You'll be able to:
- Send select posts to a roadmapping view
- Create and assign values for weighted impact factors (eg. reach, confidence, revenue, etc.)
- Prioritize based on effort vs. impact
We'll be looking for a few teams to be the first to try this out and give us feedback. Please leave a comment or shoot us a message if you're interested. We'll reach out when we're ready to share it with you!
Activity
Newest
Oldest
Paul May
Hi Sarah. Definitely interested in testing this and providing feedback. Thanks!
Sarah Hum
Thanks to those who have expressed interest in joining our beta for roadmap prioritization in Canny! We're excited to show you what we've been working on.
Please fill out this short survey and we'll let you know when the beta is ready for your team.
Chris Berkompas
We're very interested in testing this out, do you have an estimated release date?
Seth Killian
@Sarah Hum Do you envision allowing us to weight the requests of certain users? I could imagine sending a weight or something in through the API that we can then use to give certain users more voting power than others.
Sarah Hum
Hey @Seth Killian! No, I think that would be more this post. This feature is more about including other dimensions to prioritize based on. Votes are one thing and are helpful but there are other factors like reach or confidence that should be weighed in. From our research, frameworks like RICE are popular for prioritization. We'd like to enable people to do that prioritization in Canny. Hope that makes sense!
Sarah Hum
in progress
This was a tricky one to design but we're excited to build out our solution. You'll be able to:
- Send select posts to a roadmapping view
- Create and assign values for weighted impact factors (eg. reach, confidence, revenue, etc.)
- Prioritize based on effort vs. impact
We'll be looking for a few teams to be the first to try this out and give us feedback. Please leave a comment or shoot us a message if you're interested. We'll reach out when we're ready to share it with you!
Liya Ai
@Sarah Hum: Amazing!! Would love to test this feature out for our teams
C
Cassandra Summer
@Sarah Hum: you know I’m so excited for this and SO ready to help try it out. Thank you so much for all of your hard work so far to make this a reality!
Seth Killian
@Sarah Hum: We'd also love to test this!
Brian Craft
@Sarah Hum: the Sapling team would love to be in on this: we already use RICE influenced by but outside of canny.
Georgeta Pojoga
@Sarah Hum: Hi Sarah! We would like to try this feature :)
Aurélien
@Sarah Hum: Hey Sarah, that's great news and we would be thrilled to test this ! Thank you :)
George Plummer
@Sarah Hum: HI Sarah, we would also like to try this feature out please.
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 Dijssel
Currently, I'm putting the effort of a feature/idea (post) into the internal comment section. This is difficult to see and requires 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.
Load More
→