Where do product ideas go before they're ready to be issues?
Every software team has this problem: someone has an idea. It's not urgent, it's not fully formed, and it's definitely not ready to be a sprint issue. But if you don't write it down somewhere structured, it gets lost.
The options most teams use are bad. A Slack message disappears in 48 hours. A Notion page nobody reads. A JIRA issue that sits in the backlog for two years and confuses everyone. A sticky note on a monitor.
PlanIT's Idea Board is a dedicated space designed specifically for this problem. It sits between "raw thought" and "active issue" — a structured holding area where ideas can be captured, discussed, refined, and eventually promoted to issues when they're ready.
What the Idea Board is
The Idea Board is a separate view in PlanIT — distinct from your project backlog and sprint issues — where team members can submit product ideas in a lightweight format.
Each idea has:
- A title and description — enough to explain what you're thinking
- A category — to help with browsing (feature request, UX improvement, technical debt, research, etc.)
- Comments — for team discussion on the idea itself, before it becomes a formal issue
- Votes — team members can vote on ideas to signal priority without committing to implementation
- Status — Draft, Under Discussion, Accepted, or Declined
The key design decision: the Idea Board is explicitly not the backlog. Ideas don't have assignees, don't appear in sprints, and don't affect velocity metrics. They exist in their own space until a conscious decision is made to promote them.
Why separate ideas from issues?
The cleanliness of your active backlog matters more than most teams realize. When product ideas live in the backlog, the backlog becomes a dumping ground. Real sprint candidates get buried under speculative future ideas. Estimation and planning become harder. The signal-to-noise ratio drops.
Keeping ideas in a dedicated board solves this without losing the ideas. The backlog stays clean and actionable. Ideas stay visible and organized. The boundary between "we're thinking about this" and "we're committed to building this" is explicit.
This separation also changes how team members interact with ideas. When an idea is in the backlog, the implicit question is "when are we doing this?" When it's on the Idea Board, the implicit question is "should we do this?" That framing difference leads to better conversations.
How teams use the Idea Board in practice
The most effective usage patterns we see:
Capturing ideas immediately, refining them later. The lowest-friction capture wins. When someone has a product thought during a coding session or a customer call, they post it to the Idea Board immediately — even if the description is rough. Refinement happens through comments over the following days, not during the initial capture.
Using voting for low-stakes prioritization. Before a quarterly planning session, teams ask everyone to vote on the current ideas. The vote counts don't determine what gets built, but they surface signal about what the team thinks matters. It's a lightweight way to aggregate judgment across the whole team without a meeting.
Promoting ideas to issues when the timing is right. When an idea reaches a threshold — enough votes, a natural opportunity in the sprint, a customer request that aligns with it — someone promotes it to a real issue. In PlanIT, the "Promote to Issue" action copies the idea's title and description into a new issue in the relevant project, and marks the idea as Accepted. The idea's comment thread provides context for the issue.
Declining ideas explicitly. Not every idea should become a feature. When a team decides an idea isn't right — wrong timing, not enough value, conflicts with product direction — declining it explicitly with a comment is better than letting it sit indefinitely. "We decided not to do this because X" is useful information. An undead backlog item is just noise.
The Idea Board and AI workflows
PlanIT's MCP server exposes the Idea Board to AI tools. This opens up some useful patterns (see the MCP setup guide if you haven't connected your AI tool yet):
Idea capture from AI conversation. If you're discussing a product problem with Claude and land on an idea worth capturing, you can ask Claude to post it to the Idea Board without switching context:
Add this to the PlanIT Idea Board: "Add keyboard shortcut for
creating new issues — users report reaching for Cmd+N instinctively."
Category: UX improvement.
The idea is captured with the context from your conversation.
Summarizing the Idea Board for planning. Before a planning session, ask Claude to summarize the Idea Board:
Summarize the top-voted ideas on our PlanIT Idea Board that
haven't been declined yet.
You get a concise summary without opening a browser.
Linking ideas to in-progress issues. When you're working on a feature and realize a related idea exists on the board, you can reference it in the issue:
Check the Idea Board for anything related to PL-89 (rate limiting).
If there's a relevant idea, add a comment linking them.
Setting up the Idea Board for your team
The Idea Board is available in all PlanIT plans. To start using it:
- Navigate to Idea Board in the left sidebar
- Customize the categories to match your team's vocabulary (Settings → Idea Board → Categories)
- Post a brief explanation in your team chat: "We're using the Idea Board for product ideas that aren't ready to be issues. Post here instead of the backlog."
- Seed it with three to five ideas to make it feel alive from day one
The biggest adoption mistake is trying to retroactively migrate old backlog items to the Idea Board. Don't. Start fresh with new ideas. Old backlog debt is a separate problem to solve separately.
What a healthy Idea Board looks like
A healthy Idea Board for a small team typically has:
- 10–30 active ideas — enough to be a useful reference, few enough to stay navigable
- Regular new additions — one to three per week from the team
- Active comment threads — ideas getting refined through discussion
- Occasional promotions and declines — movement, not stagnation
- A review cadence — a monthly or quarterly pass to clean up and make decisions
If your Idea Board has 200 items and nothing ever moves, it's become a graveyard. The fix is a single focused session to decline everything older than 12 months that hasn't attracted votes or comments, then starting fresh with current ideas.
The connection to shipping
The Idea Board exists because ideas are the raw material of features, and losing ideas is expensive. Good software products aren't built from specifications alone — they're built from a continuous stream of observations, reactions, and hunches that get refined into requirements over time.
The Idea Board gives that stream a structured home. Not everything on it becomes a feature. A lot of ideas should be declined. But having the ideas written down, visible to the team, and connected to the project management system means the good ones don't get lost.
That's the job: capture ideas when they're raw, refine them through conversation, promote the ones worth building, decline the ones that aren't. Simple structure, significant compounding value over time.
If you want to try it, PlanIT is free for small teams — the Idea Board is available on all plans. For context on how the Idea Board fits into PlanIT's broader AI-native design philosophy, see Why We Built PlanIT.