Product planning turns the needs you have collected into a plan your team can build. It's included in the Pro plan. On Team, the Product menu shows what Pro adds.
How the pieces fit
- A strategy is a goal, such as "Win larger logistics accounts". It covers one or more products.
- An initiative is a body of work under a strategy, such as "Enterprise readiness". It can carry a theme that groups related work across strategies.
- A feature is something you'll build for a product. It can belong to an initiative, a capability (a part of the product), and a release.
- A requirement is something a feature must do, with acceptance criteria your team can test.
Every feature should have a customer reason, so you link features to the needs they address. A feature with no linked need is flagged in amber on every board and in Product insights.
Product overview
Choose Product in the top bar. You'll see, for the selected product:
- Active features, and how many are scheduled in each release
- Features linked to a need, as a percentage, with the features that have none
- Open needs not planned: needs no feature links to yet
- Requirements in draft, including how many the AI drafted
- The roadmap by release, your strategies with how far their features have shipped, and Product insights
Product Strategy
Choose Product Strategy in the left rail to see each strategy with its products, initiatives, features, and percentage complete. Open a strategy to:
- Add or remove the products it covers.
- Create initiatives with New initiative.
- See its features grouped by initiative, plus the covered products' features that have no initiative yet. Drag a feature onto an initiative to assign it. Use the Show chips to focus on some initiatives.
Feature Builder
Choose Feature Builder in the left rail. Pick a product, then filter by initiative, theme, capability, or state.
- Roadmap shows a column per release, plus Unscheduled. Drag a card to another column to change its release.
- Priority shows the product's features in priority order. Drag a card up or down to reprioritize.
Each card shows how many needs and customers are behind the feature and their total annual contract value. Click a card to open its panel, where you can edit its fields, link and unlink needs, and see suggested needs that look related.
Scheduling and reordering need the Product manager role or higher.
Generate requirements
With at least one need linked, open the feature's panel and choose Generate requirements. The Requirements Generation Agent reads the linked needs and their evidence and drafts requirements, each with acceptance criteria and the evidence it's based on. As with every AI feature, personal data is replaced with aliases first.
Nothing is created until you review the drafts:
- Drafts based on customer evidence start selected.
- Drafts suggested from common practice, with no customer evidence, start unselected.
- Choose Create to add the selected drafts as requirements in Draft, or Regenerate for a fresh set. Unselected drafts are discarded.