What is an Opportunity Card?
Opportunity Cards document customer problems, needs, or desires worth solving. They are created based on:- Customer conversations and interviews
- User feedback collection
Statuses
Once opportunities have been prioritized, use statuses to communicate when and if the team will address them. Opportunities support the following status:| Stage | Commitment | Description |
|---|---|---|
| Identified | No/Unknown commitment | Aware that the Opportunity exists but have made no commitment to solving it. This is how all Opportunities start. |
| Not now | No commitment | Recognized as an opportunity but deliberately chosen not to address it at this time, possibly due to resource constraints or competing priorities. |
| Later | Committed (Moderate Confidence) | Committed (for now) to solving the Opportunity. Confidence is relatively high that it’s an opportunity worth addressing, but this is subject to change. |
| Next | Committed | Committed and will begin work soon to start addressing the opportunity. It may be the case that the opportunity is currently being researched or solutions being identified. |
| Now | Committed | Committed and work is actively underway to address it. It’s best if there is an identified solution associated with an opportunity in Now - if not, solutioning should be underway. |
Tracking Delivery Progress
Opportunities can be linked to engineering delivery tools to track implementation progress:- Jira Integration: Link Jira issues and epics to opportunities to track work addressing customer problems
- Linear Integration: Connect Linear issues and projects to opportunities for cross-team initiatives
Opportunity Card Best Practices
See the best practices opportunity guides to learn more about:- Sizing opportunities
- Aligning the top-level of your opportunity space to customer journeys, jobs (Jobs To Be Done), or customer segments
- Well structured opportunities