Start with a simple workflow
- Collect — New portal and staff submissions land in Pending.
- Clarify — Move promising items to Reviewing; ask follow-up questions in comments.
- Decide — Promote clear opportunities to Planned, or Closed if you will not pursue them.
- Ship — Use In Progress, then Completed when live. Link completed work to a changelog entry when you announce it.
Use boards to reduce noise
- Separate Bugs from Features (or similar) so urgent defects are not lost in idea threads.
- Avoid creating a board for every feature area—too many boards slow triage.
- Hide boards from the portal when they are internal-only (Settings → Feedback portal → Visibility).
Prioritize with signals, not volume alone
- Check vote counts and comments, but also consider who asked and how the request fits strategy.
- Set Priority for urgency; set Effort for relative cost.
- If you enable scoring under Settings → Feedback → Scoring, use it as a conversation starter, not an automatic ranking.
Keep the portal honest
- Only show statuses and boards you want customers to see.
- Move inactive work to Closed (usually Hidden on the portal) instead of leaving stale Planned items forever.
- Publish changelog posts when you complete linked requests so voters see progress.
Cadence that works
- Triage Pending on a fixed schedule (daily or a few times a week).
- Review Planned before committing roadmap capacity.
- After each release, update statuses and ship a short changelog.