A primer on feature status
In productboard, feature status is a handy way to show what phase a feature is in within the product development lifecycle.
You can arrange your Features board by feature status:
Or filter is to view only features of certain status values:
For example, you might decide only to show candidates on your board, but not new ideas. This could be helpful when you're trying to fine-tune your plans after prioritizing what to build.
Arrange Roadmap by status
Now you can also arrange your Roadmap by status. This Kanban-like view is a helpful way to track and share the progress of features through the various phases from idea through delivery.
Customizing your project's feature status values
In project settings, admins can customize a project's status values to match the team's workflow.
From here you can add, remove, or rename status values. The only status values that cannot be removed are the basic statuses: Candidate and Launched. However, you can rename them.
Hidden on boards by default
Features assigned a status that appears in the lower section on the Status customization page may not appear on boards by default.
In the example above, features assigned a status of archived or won't do will always be filtered off of the Roadmap and will not appear in the linking popup on the Insights board.
Removing a status
When you remove a status, there may be existing project features currently marked with that status. If this happens you'll be prompted to indicate which status this features should be assigned.
Custom status examples
Here are a few custom statuses you might implement right away:
- New idea: For those features not yet vetted by the team or validated by other similar requests – you'll often want to filter these out during prioritization.
- Candidate: For feature ideas you're actively tracking – these are in the running to be prioritized.
- Won't do: For feature ideas you've discarded because they are not aligned with your product/strategy or are technologically infeasible. Still... maybe they'll seem more interesting a few years from now.
If you use dual track Scrum like we do, you might also consider adding additional status values to indicate where feature ideas are in the discovery process. For example, there are some ideas that are highly requested but we're not entirely sure what the real underlying user need is – a prerequisite for prioritizing the feature. It takes some effort to research why users are asking for a feature so this is labeled discovery.
Here's the full set of custom status values our team currently uses in our team's productboard project:
- New idea
- Won't Do
*Features: Launched, Archived, and Won't Do appear in the lower section of the Status customization page and will not appear on boards by default.