Custom Fields
Custom fields in Vistaly support your team’s unique needs.
Add custom fields to any card type by visiting the card settings menu.
This video shows how custom fields are used to visualize and compare opportunity sizing.
Supported Custom Field Types
Rating Scales (Likert)
Your standard rating scale - great for quick input.
Rating scales have two variations, sentiment and star.
Note: Star rating scales can be adjusted to support between 3 and 10 inputs.
Sliders
Sliders are a variation of the rating scale. Instead of picking fixed values, adjust your selection on a sliding scale.
Yes / No (Checkbox)
Great for capturing true/false criteria.
Single Select
Great when you have a set of standard options, like small/medium/large.
Controlling display order
To customize the order in which custom fields display within the workspace, drag and sort the fields.
Displaying Custom Fields
Sometimes, you need to see sizing criteria side-by-side to make better decisions. Showing sizing criteria on the cards within the workspace view can be done by toggling the custom field display settings.
Tip: It’s much easier to compare and contrast when the tree is top-down-oriented.
Tip: Keeping the custom fields visible while casually exploring the workspace can slow you down with extra scrolling. Enabling the custom fields only when needed will keep the workspace tidy.
Filtering the Workspace by Custom Fields
Use the filters menu to show only cards that match one or more specific custom field values.
Compose custom fields together for advanced filtering.
Standard Custom Fields
All workspaces start with a few default Custom Fields on Opportunity cards:
Opportunities
| Sizing Criterion | Description |
|---|---|
| Frequency | How often do customers experience this pain/need? |
| Reach | How many customers experience this pain/need? |
| Severity | How painful will it be to customers if left unaddressed? |
| Differentiation | Is it table stakes or a differentiator? |
These criteria help teams quantify and prioritize opportunities based on customer impact. Using a consistent evaluation framework allows for more objective comparison between different opportunities.
Assumptions
An assumption is a belief accepted as true without definitive proof. Every proposed idea inherently contains multiple assumptions that should be identified and validated. Below are common categories of assumptions that teams should consider:
| Assumption Type | Description |
|---|---|
| Desirability | Does this solution solve a meaningful problem for users, and will they want it? |
| Usability | Will users intuitively understand and successfully use this solution? |
| Feasibility | Can this solution be delivered with the current team, resources, and capabilities? |
| Viability | Does this solution align with strategic goals and generate measurable business value? |
Additional Considerations:
| Assumption Type | Description |
|---|---|
| Ethical Considerations | Does this solution align with ethical standards and avoid potential harm to users, society, or the environment? |
| Scalability | Can this solution grow to meet increasing demand without degrading quality or performance? |
| Legal | Are there legal considerations that might impact implementation or adoption? |
While the first four assumption types are foundational to most product development efforts, the additional types should be evaluated when relevant to the specific solution context.