Evaluate collected feedback and feature requests by impact, effort and customer context. Turn shared scores into backlog priorities, then choose the work your team will put on the roadmap.
Prioritize your requestsKeep customer signals alongside estimates of reach, impact, confidence and implementation effort.
Review scores and disagreements, check dependencies and capacity, then decide what to plan next.
Custom roles is one of several requests your team could build. Compare it with an export fix, SSO and other backlog work using the same criteria.
In the demo, engineering revises Custom roles from 4 to 6 person-months. Its score decreases while the underlying request and customer context stay connected.
Organize the feedback first, then compare the work needed to solve it alongside bugs and other planned improvements.
Record who asked, what they are trying to do and why it matters. Review related requests before merging duplicates.
Collect and organize feature requests →Capture selected messages as drafts and preserve useful context when the request reaches your backlog.
Add an idea to the internal backlog or link it to existing Jira, Linear or other supported tracker work. Evaluate it alongside the issues your team already manages.
Link requests and backlog work →Ducalis is a feature prioritization tool with configurable criteria, rating scales and scoring formulas. Start with a framework, then make its definitions useful for your product.
Use the same goal and rating scale across requests. Estimate reach over a defined period and record the evidence supporting your impact estimate.
Have engineering estimate the work using consistent units. Include dependencies and revise effort when the technical scope becomes clearer.
Review votes, customer segments, account context and confidence in your estimates. Keep measured signals distinguishable from assumptions.
RICE prioritization → · WSJF prioritization → · Value versus effort → · Explore frameworks →
Custom roles has an estimated quarterly reach of 150 people, impact 2 and confidence 80%. Engineering’s revised effort changes the calculation.
| Custom roles | Initial estimate | After engineering review |
|---|---|---|
| Reach · people / quarter | 150 | 150 |
| Impact · shared scale | 2 | 2 |
| Confidence | 80% | 80% |
| Effort · person-months | 4 | 6 |
| RICE · reach × impact × confidence ÷ effort | 60 | 40 |
| Votes · observed sample count | 40 | 40 |
| Associated customer ARR · sample context | $180k | $180k |
| Custom score · RICE + 2 × votes + ARR / $1k | 320 | 300 |
Assign criteria to teammates with the relevant expertise. Compare their evaluations and discuss where the scores differ before committing to the plan.
Customer-facing teammates contribute problem and account context; product defines the outcome; engineering estimates effort and technical dependencies.
Assign users and criteria →Use Alignment to find differences in issue scores. Clarify the scope or criteria, then revisit the estimates your team needs to agree on.
Align the team on backlog priorities →Ask your connected agent to summarize feedback and flag gaps before scoring. The team validates the context and estimates before using them to decide.
Connect your AI agent →Review the ranked backlog against your current goals, dependencies and available capacity. In the sample, the team selects Custom roles and links its public idea to Linear ENG-142.
Write a clear customer-facing summary and choose its visibility and status. The public roadmap communicates the plan your team has reviewed.
Configured tracker rules keep the linked idea’s status aligned with delivery progress. After release, a reviewed announcement tells customers what changed.
Show customers your public roadmap → · Close the loop with release updates →
App crashes on CSV export
Bug → Bugs board
SAML SSO for our company
Enterprise request → Enterprise board
Dark theme please!
Reviewed duplicate → merged into “Dark mode”
Edit boards offline
Team-selected idea → Planned, related requests linked
ENG-142linked backlog issue
Custom roles
DoneIdea linked to backlog issue ENG-142Your team ships it in LinearConfigured status rule → Done on the roadmap
Planned
In progress
Done
Compare scoring approaches and a feedback-driven workflow before applying criteria to real requests.
Start with three collected requests. Define your criteria, record the evidence, review the scores and choose what to plan next.
Prioritize your requests