TL;DR: Prioritizing feature requests shouldn't feel like a political battle. This free Notion voting board template helps you make data-driven decisions using customer votes, effort estimates, and impact scores—all visualized in a Kanban view.
"What should we build next?"
This question creates more conflict in product teams than almost any other. Sales wants the feature that'll close the enterprise deal. Support wants the fix that'll reduce their ticket volume. Engineering wants to pay down technical debt. And leadership wants everything done yesterday.
Without a transparent system, prioritization becomes a power struggle. The solution isn't better argumentation skills—it's better data.
Why Voting Boards Work
A voting board transforms feature prioritization from opinion-based to evidence-based. Instead of arguing about what matters, you let the data speak:
- Customer votes show actual demand
- Effort estimates prevent overcommitting
- Impact scores align with business goals
- Status columns create transparency
When everyone can see the same data, conversations shift from "I think we should..." to "The data suggests..."
The Free Template
This Kanban-style Notion template includes everything you need for transparent feature prioritization:
👉 Get the Feature Request Voting Board
Kanban Columns (Status Flow)
| Status | Purpose |
|---|---|
| Requested | New requests awaiting review |
| Under Review | Being evaluated by product team |
| Planned | Approved for upcoming sprints |
| In Progress | Currently in development |
| Shipped | Released to customers |
Key Properties
- Votes (Number) — Count of customer votes or internal champions
- Customer Segment (Select) — Enterprise, SMB, Startup, etc.
- Effort (Select) — S (small), M (medium), L (large)
- Impact (Select) — S (nice-to-have), M (important), L (critical)
How to Use the Voting Board
Step 1: Capture All Requests
Every feature request should enter the "Requested" column. Sources include:
- Customer support tickets
- Sales call notes
- User interviews
- Internal stakeholder requests
- Public roadmap submissions
Don't filter at this stage. The goal is comprehensive capture, not premature prioritization.
Step 2: Run Weekly Triage
Block 30-45 minutes weekly to review new requests:
- Quick wins (Low effort + High impact) → Fast-track to "Planned"
- Investigate (Unclear scope or duplicates) → Add notes, merge if needed
- Defer (Low priority now) → Keep in "Requested" with a note
- Decline (Doesn't fit vision) → Archive with explanation
Step 3: Calculate Priority Score
Create a simple formula that balances customer demand with business impact:
Priority = Votes × Impact Weight × (1 / Effort Weight)
Where:
- Impact Weight: L=3, M=2, S=1
- Effort Weight: S=1, M=2, L=3
High-impact, low-effort items bubble to the top. Large efforts need proportionally more demand to justify.
Step 4: Communicate Transparently
Share the board (view-only) with stakeholders. When someone asks "Why isn't X being built?", you can point to the data instead of getting defensive.
🤖 Pro Tip: AI-Powered Pattern Analysis
Notion AI (requires Pro/Business subscription) can reveal insights hidden in your voting data.
Find Voting Patterns
Select all items in a segment (e.g., Enterprise requests) and ask Notion AI:
- "What are the common themes in these requests?"
- "Which feature areas have the highest total votes?"
- "Are there any related requests that could be addressed together?"
Predict Impact
For new requests, AI can help estimate potential impact:
"Based on similar past requests, predict the likely vote count and customer segment interest for [new feature]."
Generate Summaries
Create stakeholder updates automatically:
"Summarize the status changes and top priorities from the last two weeks."
Best Practices
1. Weight Votes by Customer Value
Not all votes are equal. A vote from a $100K ARR enterprise customer should count more than one from a free trial user. Consider adding an "ARR Weight" formula:
Weighted Votes = Votes × (Total Requesting ARR / Average ARR)
2. Avoid Feature Factories
Don't build something just because it has lots of votes. Always ask:
- Does this align with our product vision?
- Will this help us reach our target customers?
- Is this a symptom of a deeper problem?
3. Close the Loop
When you ship a requested feature:
- Update status to "Shipped"
- Notify customers who voted
- Link to release notes or changelog
This builds trust and encourages future feedback participation.
4. Review Velocity
Track how many items move from "Requested" to "Shipped" each quarter. If requests pile up in "Requested" indefinitely, you have a capacity problem—or a prioritization problem.
The Effort/Impact Matrix View
Add a second view to your database: a Table grouped by both Effort and Impact. This creates a visual 2×2 matrix:
| Low Effort | High Effort | |
|---|---|---|
| High Impact | 🎯 Quick Wins | 🗓️ Major Projects |
| Low Impact | 🤷 Maybe Later | ❌ Probably Never |
Focus on Quick Wins first. They deliver value fast and build momentum. Major Projects require careful planning. "Maybe Later" items can wait. "Probably Never" items should be archived.
When Manual Tracking Breaks Down
This template works well for teams handling 20-50 requests per month. But as you scale:
- Manual vote counting becomes tedious
- Duplicate detection gets harder
- Cross-channel aggregation takes hours
- Pattern recognition becomes impossible
When you're processing 100+ requests monthly from support tools, sales calls, and user research, consider automating the collection. Pelin integrates with Intercom, Zendesk, Slack, and more to automatically aggregate, deduplicate, and analyze feature requests—so you can spend time making decisions instead of updating spreadsheets.
Get Started
👉 Duplicate the Feature Request Voting Board
Transform prioritization from political battles into data-driven discussions.