Planet RoadmapTemplates
Feedback
Feature Request Form Template
Standardize how you collect feedback from customers and internal teams. Use this structured format to move beyond 'we need this' to understanding the actual business value.
When to use this template
- •A customer suggests a new capability during a sales call or support interaction.
- •Internal stakeholders propose ideas that lack clear business justification or impact data.
- •Setting up a public feedback portal where users can submit and vote on new product ideas.
How to fill it in
- 1.Define the core problem being solved before describing the requested feature functionality.
- 2.Estimate user impact by quantifying how many customers or users are affected by the gap.
- 3.Document current workarounds to determine the true urgency and severity of the request.
- 4.Categorize the requester context to differentiate between enterprise needs and general user requests.
Template preview
The Core Request
- ·Request Title: Multi-Select Batch Actions in Table View
- ·Problem Statement: Users cannot archive multiple tasks at once, leading to repetitive clicks.
- ·Proposed Solution: Add checkboxes to each row and a floating action bar for bulk updates.
Impact Assessment
- ·User Impact: Medium (Saves 10-15 minutes per day for power users)
- ·Frequency: Daily usage for project managers
- ·Requester Context: High-value Enterprise account (Acme Corp)
Technical Context
- ·Current Workarounds: Users click into 50+ individual tasks manually to archive them.
- ·Attachments: Screen recording showing the friction in the current workflow.
- ·Priority Signal: High - Frequent complaint in recent customer success reviews.
Copy as Markdown
# Feature Request Form Use this template to capture high-quality feedback from customers, stakeholders, and internal teams. Standardizing this data helps prioritize the roadmap based on evidence rather than volume. ## 1. Request Overview - **Request Title:** [e.g., Bulk User Permissions Management] - **Status:** [New / Under Review / Researching] - **Submission Date:** [YYYY-MM-DD] ## 2. Problem Statement > "People don't want to buy a quarter-inch drill. They want a quarter-inch hole." - Theodore Levitt - **What is the core problem being solved?** [Describe the pain point, not the feature. What is the user unable to do today?] - **Evidence of Pain:** [Links to support tickets, customer quotes, or user research notes] ## 3. Proposed Solution - **How should it work?** [Describe the desired functionality. Be as specific as possible about the ideal user flow.] - **Success Criteria:** [How will we know this feature is successful? e.g., 'Reducing time spent on X by 50%'] ## 4. Business & User Impact - **User Impact:** [High (Daily blocker) / Medium (Significant friction) / Low (Nice to have)] - **Frequency of Use:** [Daily / Weekly / Monthly / One-time event] - **Target Segment:** [e.g., Enterprise Admins, Power Users, New Signups] - **Requester Context:** [Customer Name or Internal Department] ## 5. Feasibility & Workarounds - **Current Workarounds:** [How is the user handling this today? Are they using spreadsheets? A different tool?] - **Alternative Solutions:** [Are there other ways we could solve this problem with less engineering effort?] - **Attachments:** [Upload screenshots, Loom videos, or PDF reports here] ## 6. Internal Triage (For Product Team Only) - **Strategic Alignment:** [Does this align with current OKRs? Which one?] - **Effort Estimate:** [S / M / L / XL] - **Confidence Score:** [1-10 (How sure are we that this solves the problem?)] - **RICE Score:** [Reach x Impact x Confidence / Effort] --- Template provided by [Planet Roadmap](https://planetroadmap.com)
Use this template inside Planet Roadmap's public feedback portal to automatically group similar requests and track voter interest without per-user fees.
Skip copy-paste. Set up this template inside a Planet Roadmap project in one click.
FAQ
Why should I ask for the problem before the solution?
Users often suggest solutions that don't address the root cause. Identifying the underlying pain allows your engineering team to design the most effective technical solution.
How do I handle vague requests like 'Make it faster'?
Ask the requester to document the specific workflow that feels slow and provide a screen recording. This pinpoints whether the issue is network latency, UI responsiveness, or process design.
Should I share the internal priority signal with customers?
Generally, no. Keep internal scoring and triage notes private to maintain flexibility in your roadmap and avoid setting false expectations on delivery dates.
How often should I triage new submissions?
Set a weekly or bi-weekly sync to review new requests. Every submission should be moved to a state like 'Under Review', 'Planned', or 'Closed' to keep the feedback loop active.