# Create a new card
Source: https://docs.vistaly.com/api-reference/cards/create-a-new-card
https://api.vistaly.com/v1/swagger.json post /beta/cards
Create a new card in your organization
# Get card context
Source: https://docs.vistaly.com/api-reference/cards/get-card-context
https://api.vistaly.com/v1/swagger.json get /beta/cards/{cardId}/context
Retrieve hierarchical context for a card including ancestors (parent cards), descendants (child cards), or both. Each card in the response includes a 'level' field (0=target card, positive integers=distance from target) and a 'children' array (IDs of direct child cards). Use direction='ancestors' to understand what problems/objectives a card supports, direction='descendants' to see solutions/experiments beneath a card, or direction='both' for complete tree context. The hierarchy can be reconstructed using the children arrays and level fields.
# Get card details
Source: https://docs.vistaly.com/api-reference/cards/get-card-details
https://api.vistaly.com/v1/swagger.json get /beta/cards/{cardId}
Retrieve detailed information about a specific card
# List comments for a card
Source: https://docs.vistaly.com/api-reference/cards/list-comments-for-a-card
https://api.vistaly.com/v1/swagger.json get /beta/cards/{cardId}/comments
Retrieve all comments for a specific card
# Search cards using semantic search
Source: https://docs.vistaly.com/api-reference/cards/search-cards-using-semantic-search
https://api.vistaly.com/v1/swagger.json post /beta/cards/search
Search for cards across your organization using natural language queries
# Submit bulk metrics for a card
Source: https://docs.vistaly.com/api-reference/cards/submit-bulk-metrics-for-a-card
https://api.vistaly.com/v1/swagger.json post /v1/cards/{cardId}/metrics/bulk
Submit multiple metrics related to a specific card identified by `cardId`. This allows for bulk import of metric datapoints for tracking and performance measurement.
# Submit metrics for a card
Source: https://docs.vistaly.com/api-reference/cards/submit-metrics-for-a-card
https://api.vistaly.com/v1/swagger.json post /v1/cards/{cardId}/metrics
Submit various metrics related to a specific card identified by `cardId`. This allows for tracking and performance measurement of the card.
# Update card
Source: https://docs.vistaly.com/api-reference/cards/update-card
https://api.vistaly.com/v1/swagger.json put /beta/cards/{cardId}
Update an existing card
# Update card parents
Source: https://docs.vistaly.com/api-reference/cards/update-card-parents
https://api.vistaly.com/v1/swagger.json put /beta/cards/{cardId}/parents
Update a card's parent relationships by adding new parents and/or removing existing parents in a single atomic operation. This enables moving cards (remove old, add new) and multi-parent scenarios.
# Redirect to full LLM documentation
Source: https://docs.vistaly.com/api-reference/documentation/redirect-to-full-llm-documentation
https://api.vistaly.com/v1/swagger.json get /v1/docs/full
Redirect to the complete Vistaly documentation with detailed guides, blog posts, API reference, and extensive examples for LLMs.
# Redirect to summary LLM documentation
Source: https://docs.vistaly.com/api-reference/documentation/redirect-to-summary-llm-documentation
https://api.vistaly.com/v1/swagger.json get /v1/docs/summary
Redirect to the comprehensive Vistaly documentation including API reference, guides, and key concepts in a condensed format for LLMs.
# Delete feedback
Source: https://docs.vistaly.com/api-reference/feedback/delete-feedback
https://api.vistaly.com/v1/swagger.json delete /v1/feedback/{feedbackId}
Delete a feedback entry. This performs a soft delete by marking the feedback as deleted while preserving the data.
# Get feedback
Source: https://docs.vistaly.com/api-reference/feedback/get-feedback
https://api.vistaly.com/v1/swagger.json get /v1/feedback/{feedbackId}
Retrieve a single feedback entry, including its full body text and metadata. Use this to read the complete feedback content (the list endpoint only returns a short preview).
# List feedback
Source: https://docs.vistaly.com/api-reference/feedback/list-feedback
https://api.vistaly.com/v1/swagger.json get /v1/feedback
List feedback that has been submitted to the organization. Feedback can be filtered by whether it has been processed (analyzed for insights and opportunities). Results are ordered newest-first and include a short text preview of each feedback entry. Results are paginated: when more feedback is available the response includes a `nextCursor` token to pass back as the `cursor` parameter on the next request.
# Process feedback
Source: https://docs.vistaly.com/api-reference/feedback/process-feedback
https://api.vistaly.com/v1/swagger.json post /v1/feedback/{feedbackId}/process
Mark a feedback as processed, optionally attaching it to one or more cards. Attaching highlights the entire feedback and creates an insight linked to the given cards — the same linking that happens when feedback is created with cardIds.
# Submit user feedback
Source: https://docs.vistaly.com/api-reference/feedback/submit-user-feedback
https://api.vistaly.com/v1/swagger.json post /v1/feedback
Submit feedback from users to improve the product. This can include general comments or specific insights on their experience.
# Delete interview
Source: https://docs.vistaly.com/api-reference/interviews/delete-interview
https://api.vistaly.com/v1/swagger.json delete /v1/interviews/{interviewId}
Delete an interview entry. This performs a soft delete by marking the interview as deleted while preserving the data.
# Get interview transcript
Source: https://docs.vistaly.com/api-reference/interviews/get-interview-transcript
https://api.vistaly.com/v1/swagger.json get /v1/interviews/{interviewId}/transcript
Retrieve the transcript for a specific interview
# Submit interview data
Source: https://docs.vistaly.com/api-reference/interviews/submit-interview-data
https://api.vistaly.com/v1/swagger.json post /v1/interviews
Submit an interview record that contains valuable information regarding user interactions, feedback, and insights.
# Introduction
Source: https://docs.vistaly.com/api-reference/introduction
Welcome to Vistaly's API Documentation
Vistaly's API is available to Business and Enterprise-team plans
## Welcome
To get started, you'll need to create your Vistaly [API Key](/documentation/integrations/vistaly-api) for authentication.
## APIs
Sync the value of [KPI](/documentation/core-concepts/card-types/kpi) and [Outcome](/documentation/core-concepts/card-types/outcome) with your product analytics and BI tools.
Working with customer interviews.
Working with customer feedback.
API Health Checks
# Auth info endpoint
Source: https://docs.vistaly.com/api-reference/system/auth-info-endpoint
https://api.vistaly.com/v1/swagger.json get /v1/auth/info
Returns the information related to the api key.
# Health check endpoint
Source: https://docs.vistaly.com/api-reference/system/health-check-endpoint
https://api.vistaly.com/v1/swagger.json get /v1/health
Returns the health status of the API. This is used to verify if the API is operating normally.
# 2023
Source: https://docs.vistaly.com/changelog/2023
This is an older changelog. Some of these updates may no longer be relevant or have been enhanced. See the [latest changelog](/changelog/latest) to keep up to date on what's new.
## December 30th, 2023
### Feature Updates 🎉
* Allow deleting a custom field with responses (after confirmation).
## December 28th, 2023
### Feature Updates 🎉
* Launch beta version of sessions.
### Bugfixes 🐛
* Fix bug where custom names wouldn't show in settings.
## December 20th, 2023
### Feature Updates 🎉
* Allow customizing number of stars in rating custom field.
## December 19th, 2023
### Performance 🏎️
* Split client-side JavaScript bundle reducing time to download
assets.
## December 14th, 2023
### Feature Updates 🎉
* See online teammates in the tree.
### Performance 🏎️
* Improve Slack bot performance.
## November 28th, 2023
### Bugfixes 🐛
* Fix comment highlighting.
### Feature Updates 🎉
* Add threads to comments.
* Add comment deletion.
* Add last signed-in to team settings.
## November 16th, 2023
### Performance 🏎️
* Workspace render performance. Workspaces load faster, and adding cards feels smoother.
### Security 🔒
* Enforce adjusted password complexity.
## November 15th, 2023
### Bugfixes 🐛
* Fix Excel export on large trees.
## November 14th, 2023
### Feature Updates 🎉
* Update Jira integration to support rich text format.
* Pinch to zoom on the map.
* Auto-populate workspace name in Slack insight workflow.
* Export tree UX (Beta feature, available upon request).
### Bugfixes 🐛
* Fixes bug where sometimes the backlog would not close
## November 10th, 2023
### Bugfixes 🐛
* Fix the delete label bug with migrated workspaces.
* Fix insight similarity API when payloads are large.
## November 8th, 2023
### Feature Updates 🎉
*Fullscreen Mode*
Now, view any card fullscreen.
* Add sentiment and reverse sentiment custom field types (Beta Only)
## November 5th, 2023
### Feature Updates 🎉
*Custom Fields* (Beta Only)
With custom fields, add your sizing criteria directly to any opportunity.
### Bugfixes 🐛
* Improved error handling.
## October 30th, 2023
### Bugfixes 🐛
* Prevent the "Unsaved changes" alert from displaying unexpectedly.
## October 25th, 2023
### Feature Updates 🎉
* Rich text support for card titles.
### Bugfixes 🐛
* Address issues where card titles with quotes are incorrectly displayed with new formatting.
## October 17th, 2023
### Feature Updates 🎉
There is a new and improved insight repository experience!
* Combines both inbox and catalog for a simple, unified experience.
* Allows for attaching insights to multiple cards.
* Configure columns to show and hide exactly what you want
* Sort by multiple properties
* Export as a CSV
* Search across multiple properties
## October 14th, 2023
### Bugfixes 🐛
* Ensure the overview tab is opened by default
* Onboarding experience issues
* Slack insight bug
## October 6th, 2023
### Feature Updates 🎉
* Allow the list view navigator to be fully minimized. Take advantage of the full screen when presenting the roadmap.
## October 3rd, 2023
### Security 🔒
* Reduce session duration length.
## October 2nd, 2023
### Feature Updates 🎉
* Dynamically update title tag for better tab management
### Bugfixes 🐛
* Fix bug where Tree would occasionally move unexpectedly
## September 29th, 2023
### Bugfixes 🐛
* Fix regression where details wouldn't show in report & roadmap
## September 28th, 2023
### Feature Updates 🎉
* Sort slack bot dropdown alphabetically
* Add leave organization functionality to workspace selection screen
* Include comment creator in email / slack message notification
## September 27th, 2023
### Feature Updates 🎉
* Highlight card when navigating to it from search results
### Performance 🏎️
* Make navigating from report back to tree faster
## September 26th, 2023
### Bugfixes 🐛
* Fix filter bug where all matching cards wouldn't return
## September 22nd, 2023
### Feature Updates 🎉
* Allow insights to be attached to multiple cards
## September 15th, 2023
### Feature Updates 🎉
* Make zooming in / out feel more natural
### Security 🔒
* Improve security through additional response headers
## September 6th, 2023
### Feature Updates 🎉
* Add request access workflow to the share workspace workflow.
## September 5th, 2023
### Feature Updates 🎉
* Add metric history to reporting views
## September 1st, 2023
### Feature Updates 🎉
* Improve keyboard shortcuts and make them more consistent with common UX patterns
### Bugfixes 🐛
* Fix hidden tooltips on tree cards
* Fix windows shortcut mappings
## August 26th, 2023
### Feature Updates 🎉
* Add inline label editing support
* Add comment & insights bar – *Hide using the settings menu*
## August 25th, 2023
### Feature Updates 🎉
* Update inline text editing behavior (Consistent shortcuts)
* Update text body auto-submit behavior
* Add support for moving insights between workspaces
### Performance 🏎️
* Improve move card performance
* Improve delete card performance
## August 22nd, 2023
### Feature Updates 🎉
Inline Status Editing
Quickly make status changes without opening the side menu.
### Bugfixes 🐛
* New comment sort order.
* Delete card from side menu.
* Backlog card inconsistencies.
## August 18th, 2023
### Bugfixes 🐛
* Fix bug where a metric's target was displaying the wrong value.
* Fix bug where backlog cards wouldn't load.
## August 16th, 2023
### Bugfixes 🐛
Fix regression where metric history wouldn't show up in drawer.
## August 15th, 2023
### Bugfixes 🐛
Allow number inputs to have decimals entered with leading zeros.
## August 10th, 2023
### Feature Updates 🎉
#### Advanced Filters
Filtering just got a major upgrade.
* Create complex chainable queries
* Filter on card metadata like who created a card or when
* Save and share your favorite filters
Once the filter is applied, the tree now displays the specific subset of data that matches your filter, and that's it. No more scrolling to find the next match. See exactly what you want to see, all in one place, and explore where you want from there.
Check out some of the more interesting use cases:
* **Use Case 1: [Customer Segmentation](https://blog.vistaly.com/posts/use_case_customer_segments)**
Look at your tree through the eyes of a specific customer or customer segment. Filter opportunities and other cards by the customers that provide insights into their specific pain points or needs.
* **Use Case 2: [What's new?](https://blog.vistaly.com/posts/use_case_show_me_whats_new)**
Over time, your workspace will grow. Keeping up on what's new or changed just got a whole lot easier.
* **Use Case 3: [Show me my work](https://blog.vistaly.com/posts/use_case_show_my_work)**
Save time finding your work, whether that’s discovery, delivery, or experimentation work.
#### Navigation Improvements
Clearer indications of what's hidden, and hiding individual paths.
## August 1st, 2023
### Feature Updates 🎉
* Add support for insights attached to any card type.
## July 27th, 2023
### Feature Updates 🎉
* Modeling your trees just got more flexible. Directly nest "Objective" card types.
* Add archived support to list view. Now use the new settings menu to show archived cards in the list view.
## July 23rd, 2023
### Feature Updates 🎉
#### Metric Intregrations – BETA
Are you using Looker or PostHog? We're privately testing the ability to auto sync metrics with your BI & analytics systems directly with your KPIs/Outcomes/Key Results in Vistaly.
If you'd like to help iterate on these capabilities in Vistaly, or suggest others, reach out to [support@vistaly.com](mailto:support@vistaly.com). We want to hear from you!
## July 13th, 2023
### Feature Updates 🎉
#### Customizable Card Names
Not every team uses the same language to communicate similar concepts. Adjust card language to match how your team communicates.
#### Improved quickstart experience
Onboarding is important. We've invested time to support our new friends. 😁
## June 19th, 2023
### Feature Updates 🎉
* The **Insights Workflow** is now out of Beta! A huge thanks to all the teams that have helped refine the workflows. We are committed to continued improvements and look forward to learning more about your use cases.
> To learn more about the new insights workflow, check out [the docs](/documentation/views/insights).
## June 10th, 2023
### Feature Updates 🎉
#### Insight Slack Support
Add insights directly from Slack! Check out the insights docs to learn more.
## June 6th, 2023
### Bugfixes 🐛
* Fixes how archived cards are handled when prioritizing a set of children.
## May 17th, 2023
### Feature Updates 🎉
#### Metric Updates
#### Workspace Migration Service
If your team has multiple workspaces across various accounts and you're looking to bring them together, we're here to help! Reach out to **[support@vistaly.com](mailto:support@vistaly.com)**, and we'll help you bring your data together in one place.
## May 2nd, 2023
### Feature Updates 🎉
Quick Playlists *Deprecated*
## April 30th, 2023
### Feature Updates 🎉
#### Flexible KPI Trees
KPI Trees can now be modeled higher in your workspace. If you'd like to learn more about this change, check out [this post](https://blog.vistaly.com/posts/flexible-kpi-tree).
### Security 🔒
* Increased security for hosted images uploaded through the in-app document editor.
## April 20th, 2023
### Feature Updates 🎉
#### Updated Statuses
Statuses have been upgraded! We’ve listened and simplified how statuses work.
Now, simply select the corresponding status, and Vistaly will take care of the rest!
If you'd like to learn more about this change, check out [this post](https://blog.vistaly.com/posts/statuses).
#### Improved Roadmap Views
There are three different tabs in the roadmap view that support all the new statuses.
* Discovery: What do we want to learn more about?
* Experiments: What are we testing?
* Delivery: What work are we committed to delivering?
#### Disable Auto Submit on Enter
There's a new advanced user preference for disabling auto-submit on enter. *This feature was introduced to better support [input method editors (IMEs)](https://en.wikipedia.org/wiki/Input_method)*
#### "What's New?" Workflow
Stay up to date with all major changes.
### Bugfixes 🐛
#### Card Resizing
Fixes an issue where card resizing failed to calculate correctly under certain circumstances.
## April 10th, 2023
### Feature Updates 🎉
#### Enhanced Story Mode
Organize your workspace in one click to create focus around the bigger picture.
Story mode has replaced both the story tab *(which will be removed in a future release)*, and *linear mode*.
#### Data Export (Public Beta)
We know that there are several reasons to take your data out of Vistaly (reporting, data security, data validation, and so much more.) So now export your workspace and backlog with **on the main workspace view**.
Note: Export itself is ready for use. It's considered beta because the data format is subject to change. If you have feedback, we want to hear it!
#### Improved pinch-to-zoom
Pinch to zoom was too fast for many users' preferences. This update slows down the scroll speed to give more control over zooming.
#### Additional Metadata Updates
All records with timestamps now display exact dates on hover.
#### Read-only Support
If your account has exceeded the freemium tier limits, you can now access and continue using your workspace but will have to upgrade to one of the paid plans to add additional data.
### Bugfixes 🐛
#### Tree Filter
* Some filters were incorrectly applied to the tree in specific states *(lineage mode)*.
## March 27th, 2023
### Feature Updates 🎉
#### Improved metadata
Now hovering over any metadata records shows when it was created and by whom.
#### Pinch to Zoom
Trackpad pinch-to-zoom is now supported!
#### Attach insights from within the workspace *(Beta Users Only)*
Now you don’t have to leave the tree view to add insights from the inbox.
Selecting \*Add Existing Insight(s) opens the inbox within the current view, where you can filter and search insights.
#### Insight Filtering – By tag & Search *(Beta Users Only)*
Filter insights by themes using tags, or search for similar text to find what you’re looking for quickly.
#### Customer Management *(Beta Users Only)*
Now manage which customers provided insights to help prioritize and shape the opportunity space.
### Bugfixes 🐛
#### Inactive Dropdowns
Some users experienced dropdowns that became unresponsive over time.
# 2024
Source: https://docs.vistaly.com/changelog/2024
This is an older changelog. Some of these updates may no longer be relevant or have been enhanced. See the [latest changelog](/changelog/latest) to keep up to date on what's new.
## December 10, 2024
### Feature Updates 🎉
* Allow moving cards across workspaces
* Add logged in user filter
* Persist filters to your organization so they are shared with your teammates.
* Allow filtering tree on KPI status.
### Bugfixes 🐛
* Hide filters when its corresponding card type is disabled.
* Fix insight source filter so it works with the updated insight experience.
* Update filter language to use customized card language.
* Fix bug that would prevent interviews from showing up until a feedback was created.
## December 7, 2024
### Feature Updates 🎉
* Update roadmap filters to match tree filters.
## December 5, 2024
### Feature Updates 🎉
* Add ability to filter tree based on insight count.
### Bugfixes 🐛
* Fix slack bot bug when choosing person for feedback.
* Update notification link to select cards on the tree.
## December 3, 2024
### Feature Updates 🎉
* Add ability to filter tree based on card type.
## November 29, 2024
### Bugfixes 🐛
* Fix bug that prevent sessions from loading when deep linking to them.
## November 28, 2024
### Bugfixes 🐛
* Fix image uploading from insights.
## November 21, 2024
### Feature Updates 🎉
* Add ability to bulk import insights via CSV.
## November 14, 2024
### Major Update to Insights
We just released a massive overhaul to Insights that has everything teams need to collect, analyze, and organize customer feedback and discovery interviews directly into your Opportunity-solution Trees.
Vistaly now offers two different types of input for capturing insights:
1. **Interviews -** PMs, designers, and researchers can take long-form discovery interview notes right in Vistaly. You can link snippets of these notes to (as Insights) to the relevant card.
2. **Feedback -** as customer-facing teams (like sales, support, and customer success) talk to prospects and customers, they can relay product feedback and other relevant information that might inform product strategy to the product team.
[Read the updated docs](/documentation/views/insights) for full details on the changes.
## October 21, 2024
### Bugfixes 🐛
* Fix visual bug where custom fields prevent long multi-select options from overflowing.
## October 1st, 2024
### Feature Updates 🎉
* Updated app-wide navigation. These navigational changes lay the foundation for an upcoming major release. Stay tuned!
* Added workspace management page to admin views
## September 2, 2024
### New pricing plans
TLDR: we’re sunsetting our Freemium plan and moving from a “per seat” to “pricing tiers” model.
### We we're getting rid of Freemium
Our initial thesis behind the Freemium plan was that it would be a great way for teams to get started with Vistaly. They’d adopt the product with a small team, and usage would spread throughout company, ultimately prompting an upgrade to paid.
This rarely happens. The overwhelming majority of our paid customers convert to a paid plan relatively quickly, without a prolonged Freemium usage period.
We want to sunset the Freemium tier so that we can prioritize solving for and offering assistance to people with a high level of motivation to become more Outcomes-focused.
### **What happens next?**
If you’re currently on a plan, we’ll be transitioning you to an state with a trial length of **60 days**. This means you’ll have 60-days of unlimited access to really exercise the product before deciding if you want subscribe to one of the [new paid tiers](https://www.vistaly.com/pricing).
We’re offering a lifetime discount of 10% to current Freemium users as a thank you for being part of our early community.
If you’re on one of the existing paid plans, you don’t *have* to do anything for now. We may choose to sunset these legacy plans in the future.
However, if you’d like to make changes to your existing plan, you’ll need to move onto one of the new plans to do so.
### Questions or concerns?
If you have any questions or concerns with this change, send us an email at [support@vistaly.com](mailto:support@vistaly.com) and we’ll get back to you ASAP.
## August 10, 2024
### Bugfixes 🐛
* Fix bug that prevented card links from opening in a new tab.
### Feature Updates 🎉
* When clicking on an insight from your search results, you can now
edit/delete it, add it to a new card, or view the cards it's attached to.
## August 9, 2024
### Bugfixes 🐛
* Fix bug that wouldn't allow you to edit a link's content.
## August 8, 2024
### Bugfixes 🐛
* Fix bug that prevented links from being changed when on a card's first line.
* Fix bug that wouldn't allow you to click "View in Tree" from an insight.
* Fix race condition that would occasionally occur when deep linking to the drawer.
## August 7, 2024
### Bugfixes 🐛
* Fix bug that would prevent editing your active workspace's name from settings.
* Fix loading bug when deep linking to a session and then navigating to the tree.
### Feature Updates 🎉
* Redesign search to make it a cleaner experience. Adds ability to remove insights and/or
archived cards from the search results.
* Reduce minimum number of characters to trigger search from 3 to 2.
* Make update modal's refresh button more prominent.
## August 5, 2024
### Bugfixes 🐛
* Fix loading bug when deep linking to a session.
### Performance Improvements 🏎️
* Make many search results render more quickly.
## August 1, 2024
### Bugfixes 🐛
* Fix onboarding tooltip bug.
* Fix race condition that would result in app crashing.
* Add polling to app to ensure dropped messages are rehydrated.
### Feature Updates 🎉
* Update cards to auto-save if you click off of them.
* Add text cursor to make it clear where you should click to edit card.
* Drop root workspace selector and always redirect to first workspace.
* Move leave organization under advanced settings.
* Allow key results to have an unset start or target value.
## July 25th, 2024
### Bugfixes 🐛
* Fix bug that would result in infinite spinner when loading the tree.
## July 24th, 2024
### Performance Improvements 🏎️
* Loading trees (especially large trees) is much faster.
### Bugfixes 🐛
* Eliminated race conditions that resulted in odd behavior.
* Fix card centering bugs on the tree view.
## July 3rd, 2024
### Feature Updates 🎉
* Updates story mode to use folds instead of being a dedicated experience.
## June 27th, 2024
### Feature Updates 🎉
* Adds update modal to notify you when Vistaly has launched a new version.
## June 26th, 2024
### Major update to the Roadmap view
Out vision for the Roadmap is that it's a tool for communicating at a high-level the Solutions you're working on now, and the Opportunities you are committed to addressing in the future.
We found that showing Opportunities and Solutions on different views makes it hard for stakeholders to quickly understand what the product teams are doing.
***What are we doing to address this?***
* We're combining Opportunities and Solutions into a single unified [Roadmap view](/documentation/views/roadmap) (and moving Experiments to their own [Experiment Tracker view](/documentation/views/test-tracker)).
* The "status" of Opportunities is now [driven by child cards](/documentation/views/roadmap#status-updates-propagate-up-to-parent-opportunities) -- parent cards will automatically take on the furthest now-next-later status of their child cards.
* We only [show the "furthest down"](/documentation/views/roadmap#focusing-on-child-cards) child on the Roadmap
See the [Roadmap documentation](/documentation/views/roadmap) for full details on how this view works now.
### Other Updates 🎉
* You can now disable the Assumption and Experiment cards. Doing so will also remove the Experiment Tracker from the top navigation.
* We display a tooltip with full names when hovering over assignees on a card
* Added [Custom Fields](/documentation/core-concepts/custom-fields) to the Export artifact
* Updated our [Jira integration](/documentation/integrations/jira) to support updates on Atlassian's end
* Major overhaul to the docs site to account for updated views and card styles this year
* Major overhaul to the new user onboarding experience
### Bugfixes 🐛
* If someone else moved a card to another parent, we weren't broadcasting that such that others using the tool
## April 5th, 2024
### Feature Updates 🎉
* You can now disable the Vision Statement, Objective, or KPI card type, making it easier for your whole team to understand which cards to use and speak the same language.
* We've updated KPI statuses to , , and . The previous set of statuses implied that you were actively working on improving the KPI. The proper way to communicate that effort is to use the Outcome (aka Key Result) card.
## March 27th, 2024
### Feature Updates 🎉
* You can now [sort Roadmap items](/documentation/views/roadmap) *within* a given column. This will help you more clearly communicate what your team's focus is.
* You can now [add Unmapped cards](/documentation/views/roadmap) to your Roadmap using the "+" icons in column headers
### Usability Improvement 🤩
* You can shift+click a card's "Show Above" button to show all the way up to the top of the Workspace
## March 14th, 2024
### Feature Updates 🎉
* Continuing from last week's release, we've updated how cards look in the Roadmap (formerly List) and Reports view.
* The link to the Insights page has moved from the top navigation to the left sidebar.
* You can now update a user's role without needing to re-invite them.
### Looking For Beta Testers 🧪
* We're about to launch the ability to sort items within the Now/Next/Later Roadmap. If you'd like to get early access and give feedback, send an email to [steve@vistaly.com](mailto:steve@vistaly.com).
## March 6th, 2024
### Feature Updates 🎉
* We launched a major overhaul to how cards look and function on the Tree view. See the video below.
* You can now use cmd + scroll (in addition to shift + scroll) to zoom in/out.
### Performance Improvements 🏎️
* We refactored the front and and performance (espcially in Workspaces with high card counts) should feel dramatically faster.
### Bugfixes 🐛
* Fixed a bug where users that just joined your organization wouldn't show as active up in the bottom right until you refreshed.
* Fixed a bug where using the mouse to highlight the text in a card would drag the entire Workspace.
## February 20th, 2024
### Bugfixes 🐛
* Fix bug that would prevent custom field dropdowns from showing up in list or report view.
### Feature Updates 🎉
* Improve customer and label pickers.
## February 16th, 2024
### Feature Updates 🎉
* Public launch of custom fields, check out [the docs](/documentation/core-concepts/custom-fields). Thanks to everyone who helped with the beta!
* Switch to for search.
### Bugfixes 🐛
* Fix bug that could occur when creating comments & having slack integration setup.
## Februrary 13th, 2024
### Feature Updates 🎉
* Allow reordering single-select custom options.
## February 2nd, 2024
### Feature Updates 🎉
* Add single-select custom field.
* Add single-select tree filter.
### Bugfixes 🐛
* Fix card content overflow in tree view.
## January 30th, 2024
### Feature Updates 🎉
* Add custom field filters (rating) to tree view.
* Add planning column to roadmap allowing you to view ideas.
## January 24th, 2024
### Bugfixes 🐛
* Fix race condition that would occasionally result in
infinite spinner when loading app.
## January 22nd, 2024
### Feature Updates 🎉
* Add custom field filters (slider & yes/no) to tree view.
## January 18th, 2024
### Feature Updates 🎉
* Roadmap text search support.
## January 17th, 2024
### Feature Updates 🎉
* Support reordering custom fields.
* Allow viewing custom fields on card faces in the tree view.
### Performance 🏎️
* Improve performance of notification routes.
## January 8th, 2024
### Bugfixes 🐛
* Fix bug where filters would be incorrectly applied in
tree view when story mode was enabled.
## January 8th, 2024
### Feature Updates 🎉
* More clearly separate KPIs (persistent) and Key Results/Outcomes (point-in-time). For more information and tips on using KPIs and Key Results/Outcomes, check out [this guide](/guides/metrics/kpi-trees).
### Bugfixes 🐛
* Fix bug where labels would be cut off.
## January 6th, 2024
### Feature Updates 🎉
* Adds quick submit for card editor.
* Adds facilitator and details to session email.
# 2025
Source: https://docs.vistaly.com/changelog/2025
## December 29, 2025
### Feature Updates 🎉
* Update MCP to be label & workspace aware
## December 22, 2025
### Bugfixes 🐛
* Fix bug when uploading images in interview notepad
### Internal Improvements 🛠️
* Remove in-app notification & tree sessions in preparation for future enhancements
## December 18, 2025
### Bugfixes 🐛
* Fix bug when moving outcome cards via [API][api] / [MCP][mcp]
## December 16, 2025
### Feature Updates 🎉
* Introducing the Billing Manager role - team members can now manage billing and subscription settings without requiring an editor seat
## December 15, 2025
### Feature Updates 🎉
* Add ability to delete interviews & feedback to [API][api] / [MCP][mcp]
## December 11, 2025
### 🚀 Add Links to Card
You can now add links to external resources like Figma, Notion, Google Docs, etc. to cards in your tree.
### Feature Updates 🎉
* Add suggested insight count to interview preview
## December 10, 2025
### Feature Updates 🎉
* Add ability to move cards via [API][api] / [MCP][mcp]
## December 9, 2025
### Feature Updates 🎉
* Add tooltips to workspace picker
### Bugfixes 🐛
* Fix Jira rate limiting bug
* Fix bug when updating card type via [API][api] / [MCP][mcp]
## December 8, 2025
### Bugfixes 🐛
* Fix bug where API created feedback would fail to create with multiple new lines.
## December 5, 2025
### 🚀 AI Discovery Copilot
The newly launched [AI Discovery Copilot](/documentation/views/insights#the-ai-discovery-copilot) is now generally available to all users!
Upload the recording of your discovery interviews, sales calls, customer success touchpoints, and usability testing sessions, and the AI Discovery Copilot will:
* Write a quick summary of what was discussed during the call
* Identify problems, pain-points, and unmet needs (a.k.a. opportunities) raised by the customer
* Find cards in your opportunity solution tree that are related to the opportunities raised by the customer
The AI Discovery Copilot is free to use for all users for now, but limits may be applied in the future.
### Bugfixes 🐛
* Fix search regression for Jira integration introduced with key search
## December 4, 2025
### Feature Updates 🎉
* Update [MCP][mcp] to be aware of custom card names
## December 2, 2025
### Feature Updates 🎉
* Update Jira integration's search to allow searching by key (ex: `VST-1`)
## November 28, 2025
### Bugfixes 🐛
* Fix broadcast bug when creating a card via [API][api] / [MCP][mcp]
## November 27, 2025
### Feature Updates 🎉
* Add support for setting a card's status on create via [API][api] / [MCP][mcp]
* Allow changing a card's type via [API][api] / [MCP][mcp]
* Auto-redirect authenticated users from [https://www.vistaly.com](https://www.vistaly.com) to [https://app.vistaly.com](https://app.vistaly.com)
### Bugfixes 🐛
* Fix backlog card creation via [API][api] / [MCP][mcp]
## November 26, 2025
### Feature Updates 🎉
* Add archived filter to card picker in reports view
* Improve card matching for suggested insights found within the [interview copilot][insights]
* Improve interview tab navigation with smart default tab selection (video interviews default to transcript, others default to notes)
### Bugfixes 🐛
* Fix bug where KPI cards would occasionally fail to update via [API][api]/ [MCP][mcp].
* Fix bug where suggested cards would be duplicated if you manually attached them
* Fix thumbnail positioning for interview previews
* Fix bug where insight preview wouldn't always include full transcript preview
## November 24, 2025
### Feature Updates 🎉
* **\[Beta]** Improvements to [interviews][insights]
* Add "archived", "done", and "unmapped" badges to card chips throughtout the interface
* Use video thumbnails for interview previews
* Add "explore tree" buttons to various spots in the interface
* Add more tooltips for better usability
### Bugfixes 🐛
* **\[Beta]** Fixes for [interviews][insights]
* Fixed video player tooltip display issues
* Fixed suggested insight header clickability
* Moved interview coach feedback to the left side
## November 20, 2025
### Feature Updates 🎉
* **\[Beta]** Launch [redesigned interviews][insights]
* Launch [API][api] / [MCP][mcp] card context endpoint - retrieve hierarchical card relationships with ancestors, descendants, or both directions, including metrics, insights, and comments
### Bugfixes 🐛
* Fix jira integration pagination bug
## November 19, 2025
### Feature Updates 🎉
* **\[Beta]** Launch [AI Document Drafting][ai-drafting] - Generate evidence-based documentation for your cards using AI and customizable templates. Create comprehensive PRDs, opportunity summaries, and custom documents that automatically link to your workspace data, customer insights, and team discussions.
* **\[Beta]** Launch [Template Management][template-management] - Create and manage reusable templates to standardize AI-generated documentation across your organization. Design custom templates with sections and instructions, or use built-in templates for common use cases.
## November 13, 2025
### Feature Updates 🎉
* Date pickers now properly localize based on your browser language settings
## October 31, 2025
### Feature Updates 🎉
* The [Linear][linear] integration is now generally available to all users! Connect your cards to Linear issues and projects, create new issues directly from Vistaly, and keep work in sync across both platforms.
* Enhanced [Jira integration][jira] to support linking issues to any card type (Solutions, Opportunities, Outcomes, etc.) - not just solution cards
* Added comprehensive [Linear integration][linear] and [Jira integration][jira] documentation with best practices and use cases
## October 30, 2025
### Feature Updates 🎉
* Add support for updating a card's status via [API][api] / [MCP][mcp]
## October 29, 2025
### Feature Updates 🎉
* Enhanced Jira issue creation with comprehensive field support including user assignment, labels, dates, priorities, and custom fields
* Added ability to create Jira epics and link issues to parent epics during creation
* Jira forms now remember your last selected project and issue type for faster workflow
* Improved Jira search to support multiple projects and issue types simultaneously
## October 27, 2025
### Bugfixes 🐛
* Fixes bug where insight previews wouldn't render in node drawer
## October 24, 2025
### Feature Updates 🎉
* Enhanced Jira integration with card preview, URL search, and progress tracking
### Bugfixes 🐛
* Fixes bug where you couldn't remove cards from insights
## October 17, 2025
### Feature Updates 🎉
* Allow linking a single Jira issue to multiple Vistaly cards
## October 16, 2025
### Feature Updates 🎉
* Customer descriptions in feedback workflows can now be auto-populated
### Bugfixes 🐛
* Fixed bug when removing highlighted text from interviews and feedback
* Fixed issue where insights could overlap in the drawer
## October 15, 2025
### Feature Updates 🎉
* Added roadmap card face customization to control what information displays on cards
* Linear cards now link back to Vistaly for easier navigation between tools
## October 10, 2025
### Feature Updates 🎉
* Interview recordings now support larger file sizes with improved upload reliability
### Bugfixes 🐛
* Improved error handling for failed interview uploads and audio extraction
## October 8, 2025
### Feature Updates 🎉
* Linear project progress tracking now available in connected cards
### Bugfixes 🐛
* Better error messaging when attempting to link already-linked Jira issues
## October 7, 2025
### Feature Updates 🎉
* Launch Linear integration - connect cards to Linear issues and projects, create new issues directly from Vistaly, and keep work in sync
## October 3, 2025
### Bugfixes 🐛
* Fixed suggested highlight positioning bugs in interviews and feedback
## October 1, 2025
### Bugfixes 🐛
* Fixed Jira integration URL parsing to properly extract cardId from Vistaly URLs
## September 23, 2025
### Feature Updates 🎉
* Viewers can now submit feedback through the Slack integration
### Bugfixes 🐛
* Fixes web extension bug where creating feedback would cause it to crash
## August 22, 2025
### Bugfixes 🐛
* Fixes bug with insight person filters
## August 11, 2025
### Bugfixes 🐛
* Fixes bug that would result in users being logged out more often than necessary
## August 7, 2025
### Feature Updates 🎉
* Improved search functionality from feedback and interviews
### Bugfixes 🐛
* Fixes bug with Slack app dropdowns
* Fixes bug where initial sign-in route will be lost when logging in with Google or Microsoft
## August 1, 2025
### Feature Updates 🎉
* Add card link unfurling to [Vistaly Slack Integration][slack]
## July 31, 2025
### Feature Updates 🎉
* Add bulk metric uploading via [API][api] / [MCP][mcp]
## July 29, 2025
### Style Updates 🎨
* Updated code block styling to be a little easier on the eyes
### Bugfixes 🐛
* Fixes bug that would prevent drag & drop from working within interviews and feedback
## July 26, 2025
### Bugfixes 🐛
* Fixes bug that would sometimes cause insights to overlap in the drawer feed
## July 25, 2025
### Feature Updates 🎉
* Add insight rollup tooltip preview. Now get a sense for which customers shared insights under entire branches of your workspace.
### Internal Improvements 🛠️
* Enhanced API authentication reliability with retry logic and exponential backoff to handle concurrent access
## July 24, 2025
### Feature Updates 🎉
* Added markdown parsing support to public API for structured feedback and interview content
## July 23, 2025
### Feature Updates 🎉
* Adds ability to update card title and details via [API][api] / [MCP][mcp]
## July 22, 2025
### Feature Updates 🎉
* Vistaly MCP server now supports [remote integration][mcp] - connect directly without installing the `@vistaly/mcp` package
### Bugfixes 🐛
* Fixes bug that prevents sentiment custom fields from being filterable
* Fixes bug that resulted in unmapped cards showing descendants in delete confirmation modal
## July 20, 2025
### Feature Updates 🎉
* Added unmapped cards access to insights tree view for improved workflow
## July 18, 2025
### Feature Updates 🎉
* Added organization menu to workspace selector with quick links
## July 17, 2025
### Feature Updates 🎉
* Adds ability to see and filter cards by [insight rollups](/documentation/views/insights#insights-rollups).
## July 16, 2025
### Feature Updates 🎉
* Alphabetized organizations and workspaces in workspace selector
### Bugfixes 🐛
* Fixes an issue that prevented new Slack bot installations from completing successfully
* Fixes a race condition that could result in API created interviews / feedback not creating properly
* Fixes Slack bot feedback creation when triggered via `/vistaly feedback`
## July 15, 2025
### Bugfixes 🐛
* Fixes bug where cards created via [API][api] appear disabled until page refresh
## July 14, 2025
### Feature Updates 🎉
* Adds ability to filter interviews and feedback by companies and participants
* Adds ability to filter interviews and feedback by interviews you participated in or feedback you submitted
* Adds ability to create cards from API and MCP
* Adds clickable link to customer user tooltip for easier navigation
### Bugfixes 🐛
* Fixes insights navigation bug
* Fixes API error message handling
* Fixes infinite spinner issue when onboarded users visit /welcome route
## July 11, 2025
### Bugfixes 🐛
* Fixed bug that could result in the roadmap view becoming unresponsive when adding unmapped cards directly
## July 10, 2025
### Feature Updates 🎉
* Insights in the card drawer now include styling from your interview and feedback
### Bugfixes 🐛
* Fixed bug that would prevent insight and feedback editor from adjusting some text styles
## June 26, 2025
### Feature Updates 🎉
* Update API timestamps to work better with MCP
## June 25, 2025
### Feature Updates 🎉
* Adds sign in with Microsoft
* Launch [Beta MCP](/documentation/integrations/model-context-protocol)
## June 23, 2025
### Bugfixes 🐛
* Fixed bug that would cause full reload of the app in the insights view
* Fixed bug that would prevent you from pasting text into an existing insight
## June 18, 2025
### Bugfixes 🐛
* Fixed bug that could result in interview & feedback documents not loading until refresh
## June 16, 2025
### Feature Updates 🎉
* Add ability to move insight across cards from insight tab in card drawer
## June 12, 2025
### Bugfixes 🐛
* Fixed bug where you couldn't create insights from drawer
## June 11, 2025
### Bugfixes 🐛
* Fixed z-index issue with inline editing that caused UI elements to overlap incorrectly
* Fixed loading issue where feedback and interviews would sometimes not properly load in the drawer
## June 5, 2025
### Feature Updates 🎉
* Card details now automatically save when closing the drawer
## June 3, 2025
### Feature Updates 🎉
* Enhanced feedback view to include unattached insights for better context
* Added smooth drawer animation to interview drawer
## June 2, 2025
### Feature Updates 🎉
* Enhanced insight linking experience with improved search and attachment workflow
* Improved document loading states
* Made move card icon consistent
### Bugfixes 🐛
* Fixed loading issues that could sporadically occur
* Resolved various edge cases in the insight attachment flow
## May 7, 2025
### Bugfixes 🐛
* Fixed bug where hiding a branch wouldn't properly recenter you in the tree
* Fixed issue where mirrored cards weren't properly displaying in roadmap and reports
### Feature Updates 🎉
* Added workspace name to comment notification emails
* Updated the icon for 'remove mirror' to distinguish it from the 'remove card' icon
### Internal Improvements 🛠️
* Preparatory work for the upcoming 'Add Suggested Opportunity' to insights
## May 1, 2025
### Bugfixes 🐛
* Fixed card link behavior so URLs now properly open in new browser tabs when clicked
* Resolved issue with accessing edit options for assignees and labels from the card menu dropdown
## April 25, 2025
### Feature Updates 🎉
* Support navigating tree with arrow keys. To try it out, first select a card and then navigate using the arrow keys.
## April 24, 2025
### Feature Updates 🎉
* Launched beta support for cards with multiple parents
* Improved status propagation for card statuses
* Improved performance and overall navigation within the tree
* Improved modal dialogs for deleting and archiving cards, with clearer confirmations
* Added API documentation links and call-to-action in relevant areas
* The app now better remembers your last spot in the tree when refreshing or switching between views
### Bugfixes 🐛
* Filters persist on refresh
* Clicking on search results will properly center on the card
## April 10, 2025
### Feature Updates 🎉
* Added ability for viewers to export workspace data
* Enhanced roadmap customization options column reordering (found in advanced settings)
* Improved workspace navigation to maintain current view when switching workspaces
## April 9, 2025
### Feature Updates 🎉
* Added ability to create opportunities under objective cards
* Enhanced KPI charts in reports with target line visualization
* Improved label picker with option to prevent duplicate label creation
* Reworked layout algorithm to support cards with multiple parents (coming soon!)
* Updated card settings view for improved usability
### Bugfixes 🐛
* Fixed a bug with report card picker functionality
## April 6, 2025
### Bugfixes 🐛
* Improve tree performance when many cards are expanded
## April 3, 2025
### Bugfixes 🐛
* Fixed an issue that prevented the index from rendering in the tree
* Fixed a bug allowing cards to be reordered in situations where reordering should be restricted
### Feature Updates 🎉
* Redesigned the metadata bar for a more streamlined look and feel
* Improved error handling for CDN-related issues
* KPI statuses are now hidden from card faces unless they're out of bounds
* Laid the groundwork for supporting cards with multiple parents
## March 21, 2025
### Bugfixes 🐛
* Fix roadmap filters bug that would cause numeric filters to crash the app
## March 13, 2025
### Bugfixes 🐛
* Fix tree loading bug where large trees would initially load slowly
## March 6, 2025
### Feature Updates 🎉
* Launch enhanced reports experience (see [Reports](/documentation/views/reports) for more information)
## March 5, 2025
### Feature Updates 🎉
* Add ability for users to request viewer access if they navigate to a url they don't have access to
## February 24, 2025
### Bugfixes 🐛
* Fix minimum height of comments to prevent tooltips from not showing in certain cases
### Feature Updates 🎉
* Automatically set start date & end date for outcomes based on status changes
* Make newly created outcomes default to progressing status
* Support uploading PDFs to comments
## January 21, 2025
### Feature Updates 🎉
* Launch API access (see the [Vistaly API](/documentation/integrations/vistaly-api) docs for more information)
## January 17, 2025
### Feature Updates 🎉
* Improve tree loading performance
## January 15, 2025
### Bugfixes 🐛
* Fix feedback importer bug preventing users from getting imported
[api]: /api-reference/introduction
[mcp]: /documentation/integrations/model-context-protocol
[slack]: /documentation/integrations/slack
[jira]: /documentation/integrations/jira
[linear]: /documentation/integrations/linear
[ai-drafting]: /documentation/ai-document-drafting/overview
[template-management]: /documentation/ai-document-drafting/template-management
[insights]: /documentation/views/insights
# Latest Changelog
Source: https://docs.vistaly.com/changelog/latest
## Next Release
### Feature Updates 🎉
* Retry interview classification with the full transcript when an interview was classified as an unsupported type (e.g. sales call, team meeting, usability session, invalid transcript)
### Bugfixes 🐛
* Fix bug where a transient error fetching your profile on page refresh or deep link could incorrectly redirect you to the onboarding form
* Roadmap now shows opportunities from orphan trees (cards placed directly on a space canvas rather than descended from the outcome) so the roadmap reflects everything on the canvas
* Roadmap now hides ancestor cards when one of their descendants is already shown in a prioritized column, so each card shows up once, as its furthest-progressed leaf
## January 23, 2026
### Bugfixes 🐛
* Fix bug when pasting images into feedback editor
* Fix bug where feedback created from the card drawer would not link properly
## January 20, 2026
### Feature Updates 🎉
* Create interview insights and summaries in the same language as the uploaded transcript
### Bugfixes 🐛
* Fix bug when suggesting insights for text transcripts with rich text
## January 8, 2026
### Feature Updates 🎉
* [MCP][mcp] is now available to all users, including Starter plans
* Allow resizing text highlights in interview and feedback
[api]: /api-reference/introduction
[mcp]: /documentation/integrations/model-context-protocol
# Drafting Documents
Source: https://docs.vistaly.com/documentation/ai-document-drafting/drafting-workflow
Step-by-step guide to generating AI-powered documentation
**Beta Feature:** AI Document Drafting is currently in beta. We're actively improving the feature based on user feedback.
# Drafting Documents
This guide walks through the complete workflow for generating AI-powered documentation, from template selection to final draft.
## Starting a Draft
AI drafting is available in three locations throughout Vistaly.
### 1. Card Description Editor
The most common entry point for creating card documentation.
**Steps**:
1. Open any card in your workspace
2. Look for the **"Draft with AI Templates"** button in the description field
3. Click to launch the drafting workflow
**When to use**:
* Documenting opportunities, solutions, or problems
* Creating comprehensive card descriptions
* Generating structured documentation from workspace data
### 2. Jira Integration
Generate issue descriptions when creating Jira issues from Vistaly.
**Steps**:
1. Create a Jira issue from a Vistaly card
2. In the issue creation dialog, click **"Draft with AI Templates"** in the description field
3. Select a template and generate
**When to use**:
* Creating detailed Jira issues from Vistaly cards
* Ensuring Jira tickets have comprehensive context
* Maintaining consistency between Vistaly and Jira
### 3. Linear Integration
Generate issue descriptions when creating Linear issues from Vistaly.
**Steps**:
1. Create a Linear issue from a Vistaly card
2. In the issue creation dialog, click **"Draft with AI Templates"** in the description field
3. Select a template and generate
**When to use**:
* Creating detailed Linear issues from Vistaly cards
* Ensuring Linear tickets have comprehensive context
* Maintaining consistency between Vistaly and Linear
## Step-by-Step Workflow
The AI drafting workflow consists of several distinct steps:
### Step 1: Template Selection
After clicking "Draft with AI Templates", you'll see all published templates compatible with your current card type.
**What You'll See**:
* Template name and icon
* Brief description
* Preview of template sections (expandable)
Hover over any template to expand and preview its sections before selecting if you're unsure which one you should use.
### Step 2: Context Collection
After selecting a template, you'll provide additional context. By default, Vistaly's document drafting experience will only generate content when evidence exists to support it. This is your opportunity to share any context you have to improve the quality of the output with infrormation not stored in Vistaly.
#### What is Extra Context?
Extra context is **optional** information that's not captured in your Vistaly workspace.
**What AI Already Knows**:
* Your target card plus relevant surrounding context
* All comments on these cards
* All customer insights linked to these cards
* Your organization description (from Settings)
You don't need to repeat any of this information.
**When to Provide Extra Context**:
✅ **Do Provide**:
* Specific technical requirements from external docs
* Stakeholder decisions made in offline meetings
* Research or data from other tools
* Context from outside your workspace
* Any context required by your template that lives outside of Vistaly
❌ **Don't Provide**:
* Information already in your card hierarchy
* Insights already linked to cards
* General requests like "make it detailed"
* AI instructions (use template sections for this)
**Example Extra Context**:
```markdown theme={null}
## Additional Requirements
- Must integrate with Salesforce API
- Target launch: Q2 2024
- Engineering budget: 3 developers for 6 weeks
## Stakeholder Input
From 1/15 planning meeting:
- VP Sales wants mobile-first experience
- Support team needs admin dashboard
- Compliance requires audit logging
```
#### Navigation
* **Back to Templates**: Return to template selection
* **Generate Draft**: Proceed with AI generation (disables after clicking)
### Step 3: Generation
After clicking "Generate Draft", AI processes your request.
**What Happens** (10-30 seconds):
1. **Data Collection** (automatic):
* Fetches target card and additional context
* Retrieves all linked customer insights
* Retrieves all comments on these cards
* Fetches your organization description
2. **AI Processing**:
* Combines workspace data with template structure
* Integrates your extra context
* Links all required insights to source cards
* Acknowledges gaps where evidence is missing
* Generates structured markdown
3. **Display**:
* Editor opens with generated content
* Content is fully editable
### Step 4: Reviewing the Draft
The generated draft appears in a markdown editor, ready for review and editing.
**What You'll See**:
**Structured Sections**:
Every section from your template, populated with relevant content:
```markdown theme={null}
## Customer Evidence
Based on customer feedback, teams need better collaboration
([Company A](link1), [Company B](link2)). Users specifically
mentioned challenges with real-time updates ([Company C](link3)).
> "We waste hours each day syncing across tools."
> — Jane Smith, [Company A Interview](link1)
```
**Linked Insights**:
All required insights are linked as clickable references back to source cards in Vistaly.
**Evidence-Based Content**:
Only information from your workspace is included. No fabrication.
**Acknowledged Gaps**:
When evidence is missing, AI explicitly notes it:
```markdown theme={null}
## Market Sizing
*(Evidence not yet available)*
```
This is intentional and better than fabricated information.
```markdown theme={null}
## Additional References
- Workflow friction challenges [[1]](url1)[[2]](url2)
- [Users struggle to find insights](url3) (Company X)
```
### Step 6: Saving Your Draft
Once you're satisfied with the content:
1. Click **Save** or use your platform's save mechanism
2. The draft becomes your card description (or Jira/Linear issue description)
3. All insight links are preserved and clickable
## Preparing for Better Drafts
The quality of your generated drafts depends on the data in your workspace.
### Before Drafting
**Link Relevant Insights** to your card and surrounding context:
* AI pulls insights from target card and related cards
* More insights = richer, more evidence-backed content
* Insights closer to your target card are prioritized
**Update Organization Description** (Settings > Advanced):
Set your organization description to help AI understand your business context. Include:
* Your industry and market
* Product focus and offerings
* Target customers
* Company mission or value proposition
**Example**:
> "Acme Inc. is a B2B SaaS company building project management software for distributed engineering teams. We focus on mid-market companies (50-500 employees) in the technology sector. Our platform combines real-time collaboration with automated workflow management to help remote teams coordinate complex software projects."
**Choose the Right Template** for your use case:
* Early exploration: "Opportunity Summary"
* Building solution: "Solution Brief"
* Specialized needs: Custom template
## Workflow Tips
### First Draft Mindset
Treat generated drafts as a strong starting point, not a final product:
* **Review for accuracy**: Verify all linked insights are relevant
* **Fill gaps**: Add missing information manually
* **Enhance**: Expand sections that need more detail
* **Refine**: Polish tone and structure
### Iterative Refinement
For complex documents:
1. **Generate initial draft** with template
2. **Manually review and edit** for accuracy and completeness
### Time Savings
* **First draft**: Seconds (AI generation)
* **Review and edit**: Minutes to hours (depending on complexity)
* **Total time**: 50-80% faster than starting from scratch
Focus your time on strategic thinking and refinement rather than structure and evidence gathering.
## Workflow Approaches
Different approaches work for different documentation needs:
### Quick Draft Approach
For routine documentation or early-stage exploration:
1. **Generate with template** (1-2 min)
2. **Quick manual edit** (5-10 min)
3. **Save and iterate later**
**When to Use**: Internal docs, early drafts, rapid prototyping
### Three-Pass Approach
For complex, important documents:
**Pass 1 - Generate Structure** (AI):
1. Select template and generate initial draft
2. Review for completeness and structure
3. Identify gaps and missing evidence
**Pass 2 - Fill Gaps** (Manual):
1. Add missing information from other sources
2. Link additional insights
3. Enhance thin sections
4. Correct any inaccuracies
**Pass 3 - Final Polish** (Manual):
1. Polish tone and readability
2. Final review for accuracy
**Time Investment**: 30-70 minutes vs. 2-4 hours from scratch
### Progressive Refinement Approach
For documents you'll build over time:
1. **Generate skeleton** early with limited data
2. **Review and identify gaps**
3. **Add evidence** (insights, comments) to workspace
4. **Regenerate** as you gather more information
**When to Use**: Long-running initiatives, evolving documents, research-heavy projects
## Troubleshooting
### Template Not Available
**Checklist**:
* Is the template published? (Check Settings > Templates)
* Does the template support your card type?
* Refresh the page to load latest templates
### Missing Expected Insights
**Possible Causes**:
* Insights aren't linked to card or surrounding context
* Insights are too far removed from the target card
* Template sections don't align with insight content
**Solutions**:
* Link insights directly to target card or closely related cards
* Ensure insights are connected to relevant cards in your hierarchy
* Adjust template section descriptions to match available data
### Draft Quality Issues
**Sparse Output**:
When your draft feels thin, try these solutions:
* **Link more insights** from customer interviews or research to the card and surrounding context
* **Add comments** to cards with key context before drafting (stakeholder feedback, decisions, requirements)
* **Use extra context field** generously for information not in Vistaly (meeting notes, research, requirements)
* **Accept shorter draft with gaps** and fill manually as needed
**Missing Metrics or Data**:
When template asks for metrics but you don't have them yet:
* **Accept the gap** - AI will note `*(Evidence not yet available)*` which is honest and appropriate
* **Define metrics separately** in a working session
* **Manually add to draft** once defined
* This honest documentation evolves as you gather data
**Generic Output**:
When draft feels vague despite having data:
**Likely Causes**:
* Template section descriptions too vague
* Template too broad for use case
* Missing organization description
* Insufficient extra context
**Solutions**:
* Improve template section descriptions with specific guidance
* Create more focused templates for specific card types
* Add organization description in Settings > Advanced
* Provide targeted extra context for specific requirements
**Duplicate Information**:
If same insight appears multiple times:
* Link insight to **most relevant card only** in your hierarchy
* AI prioritizes insights from closer cards, so linking to the most specific card prevents redundancy
**Missing Sections**:
* Check template has complete sections (both title and description)
* Verify template is published
* Try regenerating
### Generation Takes Too Long
**Normal**: 10-30 seconds depending on data volume
**Too Long** (>60 seconds):
* Check internet connection
* Try refreshing and regenerating
* Contact support if persistent
## Best Practices
### Before Drafting
* [ ] Review card hierarchy and linked insights to get a sense of what's available
* [ ] Choose appropriate template for use case
* [ ] Prepare extra context if needed
### During Review
* [ ] Check for acknowledged gaps and determine if acceptable
* [ ] Assess overall structure and flow
* [ ] Note sections that need expansion
### After Drafting
* [ ] Fill acknowledged gaps with manual content
* [ ] Enhance sections with additional context
* [ ] Polish tone and readability
* [ ] Save and share with team
## Next Steps
* **[Template Management](/documentation/ai-document-drafting/template-management)**: Create custom templates for your needs
***
Questions about the drafting workflow? Contact us at [support@vistaly.com](mailto:support@vistaly.com)
# Document Drafting Overview
Source: https://docs.vistaly.com/documentation/ai-document-drafting/overview
Generate evidence-based documentation for opportunities, solutions, experiments, and any other card type using AI and templates
**Beta Feature:** AI Document Drafting is currently in beta. We're actively improving the feature based on user feedback.
# AI Document Drafting
Generate structured, evidence-based documents for opportunities, solutions, experiments, and any other card type using AI and customizable templates. AI combines your workspace data (cards, insights, comments) with template instructions to create comprehensive documentation that links directly to source data.
## How It Works
```
Workspace Data + Template + Your Context = Evidence-Backed Draft
```
1. **Select a Template**: Choose from your organization's templates or start blank
2. **Add Context** (optional): Provide additional details not in Vistaly
3. **Generate**: AI creates documentation following your template structure
4. **Refine**: Edit and polish your draft to perfection
AI automatically sources context from surrounding cards by leveraging relationships, associated insights from interviews, feedback, integrated metric data, and team conversations.
**Key principle**: When evidence is missing, our drafting experience explicitly acknowledges gaps and points out where information is thin. When there's rich information, links are automatically generated to interviews, feedback, conversations, and more.
## Where to Access
Available in three places:
1. **Card Description Editor** - Generate documentation for any card
2. **Jira Integration** - Draft issue descriptions when creating Jira tickets
3. **Linear Integration** - Draft issue descriptions when creating Linear issues
## Common Use Cases
**Product Requirements (Solution Brief template)**:
* Problem definition with customer evidence
* Solution approach and key features
* Goals, success metrics, and scope
**Opportunity Analysis (Opportunity Summary template)**:
* Market opportunity with customer validation
* Current state and impact sizing
* Success metrics
**Custom Templates**: Design your own for technical specs, research summaries, retrospectives, or any structured documentation needs.
## Next Steps
* **[Template Management](/documentation/ai-document-drafting/template-management)**: Learn how to create and manage templates
* **[Drafting Workflow](/documentation/ai-document-drafting/drafting-workflow)**: Step-by-step guide to using AI drafting
***
Questions or feedback? Contact us at [support@vistaly.com](mailto:support@vistaly.com)
# Template Management
Source: https://docs.vistaly.com/documentation/ai-document-drafting/template-management
Create and manage templates for AI-powered document drafting
**Beta Feature:** Template Management is currently in beta. We're actively improving the feature based on user feedback.
# Template Management
Templates define the structure and content guidelines for AI-generated documentation. Each template includes sections that guide the AI in creating comprehensive, consistent documents tailored to your organization's needs.
## Accessing Template Management
Navigate to **Settings > Templates** to view and manage your organization's templates.
## Creating Templates
1. Click the **Create** button in the template list
2. A new template is created with default values
3. The editor opens automatically for you to customize
### Basic Information
Every template requires the following metadata:
**Name**: A descriptive name for the template (e.g., "Solution Brief", "Opportunity Summary"). Keep names clear and use terminology your team understands.
**Description**: A brief explanation of what the template is for and when to use it.
Example: *"Comprehensive product requirements document that connects problem understanding to solution details. Use for feature planning and cross-functional alignment."*
**Icon**: A quick way to visually identify the template when making a selection.
**Card Types**: Restrict which card types can use this template for drafting.
### Context Types
Context types determine how the AI gathers information from your workspace when generating documents. This setting affects which cards and insights are considered when creating your document.
#### How We Got Here
**Purpose**: Understanding the story behind a card by looking backward through its history.
**What it does**:
* Focuses on the target card and its **ancestors** (parent cards)
* Examines up to 2 levels of parent cards to understand the full context
* Prioritizes insights from the target card and its immediate parents
* Creates a narrative that traces how you arrived at this point
**Best for**:
* Documenting opportunities and their origins
* Understanding problems and their context
* Creating retrospective documentation
* Explaining the reasoning behind decisions
* Tracing the evolution of ideas
**Example**: When documenting an opportunity, "How We Got Here" will look at the problem that led to it and the broader strategic goals that informed the problem.
#### Where We're Going
**Purpose**: Planning and tracking progress by looking forward to what needs to be done.
**What it does**:
* Focuses on the target card and its **descendants** (child cards)
* Examines child cards deeply to understand planned work
* Includes limited ancestor context for background
* Creates a forward-looking narrative focused on execution
**Best for**:
* Progress tracking and status updates
* Solution planning and roadmaps
* Forward-looking documentation
* Documenting active work and next steps
* Breaking down complex initiatives
**Example**: When documenting a solution, "Where We're Going" will look at the experiments, tasks, and sub-solutions that make up the implementation plan.
#### Choosing the Right Context Type
The context type should match your document's purpose:
* Use **How We Got Here** when the document needs to explain origins, reasoning, or historical context
* Use **Where We're Going** when the document focuses on execution, progress, or future plans
You can create multiple templates for the same card type with different context types to serve different documentation needs.
### Template Instructions
Global instructions that apply to the entire template.
Use this field to:
* Set overall tone and style
* Define the document's purpose
* Specify target audience
* Add general content requirements
**Example**:
> "Create a comprehensive product requirements document for engineering and design teams. Focus on clarity and completeness. Connect customer problems to proposed solutions with evidence. Maintain a professional, technical tone suitable for cross-functional review."
**Tips**:
* Be specific but concise
* Focus on high-level guidance
* Section-specific instructions go in section descriptions
* Optional field—leave blank if sections provide sufficient guidance
### Template Sections
Sections structure your generated documents. Each section becomes a heading (##) in the output.
#### Adding Sections
1. Click **Add Section** at the bottom of the section list
2. Enter a section title
3. Enter a section description
4. Section is automatically saved
#### Section Components
**Title** (required):
* The section heading in the generated document
* Use clear, standard headings (e.g., "Goals & Success Metrics", "The Problem")
* Will be formatted as `## Title` in markdown
**Description** (required):
* Instructions to the AI about what content to generate for this section
* Be specific and actionable
* Think of it as instructions and best practices you'd share with anyone filling out the template
#### Writing Effective Section Descriptions
Section descriptions are the most important part of your template. They directly guide AI output quality. Each section will have access to all the relevant workspace context.
**Be Specific About Content**:
✅ Good:
> "Define what success looks like. List specific metrics you intend to move and explain why they matter. Group metrics logically (user adoption, business impact, quality indicators). Include baseline values if available in card context."
❌ Too Vague:
> "Add success metrics here."
**Acknowledge Data Limitations**:
✅ Good:
> "Provide market size estimates, TAM/SAM/SOM analysis, or revenue projections if this data exists in card context. If market sizing hasn't been done, explicitly note that this analysis is needed. Do not invent numbers."
❌ Missing Boundary:
> "Add market sizing analysis."
**Guide Information Organization**:
✅ Good:
> "Present customer feedback, interview insights, and market research supporting this opportunity. Organize by strength of signal. Include direct quotes with attribution."
❌ Unclear Structure:
> "Add customer evidence."
**Set Evidence Expectations**:
✅ Good:
> "Link all insights. Use direct quotes where compelling. Acknowledge if evidence is sparse."
❌ No Guidance:
> "Include relevant data."
#### Examples of Strong Section Descriptions
**For a "Problem Statement" Section**:
> "Describe the core problem customers are facing. Include specific pain points from customer interviews with direct quotes. Quantify the impact where data exists (time wasted, cost incurred, opportunities missed). Link all insights. If the problem isn't well-validated yet, acknowledge this explicitly."
**For a "Key Features" Section**:
> "List the main capabilities we're building to solve this problem. For each feature, briefly explain what it does and why it matters to users. Focus on user value, not technical implementation. Organize by priority or logical grouping. Link to any insights that informed feature decisions."
**For a "Success Metrics" Section**:
> "Define what success looks like with specific, measurable metrics. Group into categories: user adoption, business impact, and product quality. For each metric, include the target value and explain why it matters. Note if baseline values exist. Acknowledge if metrics need to be defined."
#### Reordering Sections
Sections appear in your generated document in the order listed.
1. Click and hold the drag handle (⋮⋮) next to a section
2. Drag to new position
3. Release to drop
4. Order saves automatically
#### Deleting Sections
1. Select or hover over a section and click the remove icon.
2. Confirm deletion
3. Section is permanently removed
Deleting a section cannot be undone. Pre-existing documents will not be adjusted. This only impacts newly created documents using this template.
## Template Design Principles
### Focused vs. Broad Templates
**Focused Templates (Recommended)**:
Create templates for specific use cases with a single, clear purpose.
**Characteristics**:
* Single purpose (PRD, opportunity analysis, experiment report, etc.)
* 5-7 sections optimized for that specific use case
* Clear, consistent narrative flow
* Specific content guidance in each section
**Benefits**:
* Higher quality output
* More predictable results
* Easier to maintain and iterate
* Better user experience
**Examples**:
* "Opportunity Summary" for market analysis
* "Solution Brief" for product requirements
* "Experiment Report" for test results
* "User Research Summary" for interview synthesis
**Broad Templates (Use Sparingly)**:
Templates that attempt to serve multiple purposes across different contexts.
**Characteristics**:
* Multiple use cases
* Generic sections that work for many scenarios
* Flexible structure
**Drawbacks**:
* More generic output quality
* Harder to write effective section descriptions
* Less predictable results
* Requires more manual editing after generation
**When to Use**: Only for truly general documentation needs where a focused template doesn't fit.
## Publishing Templates
Templates must be **published** before they appear in AI drafting.
### Draft vs. Published Status
**Draft Templates**:
* Visible only in template management (Settings > Templates)
* Not available when drafting documents
* Can be edited freely without affecting users
**Published Templates**:
* Visible in template management AND drafting workflow
* Available for all organization members to use
* Changes take effect immediately
### Publishing a Template
1. Ensure template passes validation (see below)
2. Toggle the **Published** switch in the template editor
3. Template immediately becomes available for drafting
### Unpublishing a Template
1. Toggle the **Published** switch to off
2. Template immediately becomes unavailable for new drafts
3. Existing drafts created with this template are not affected
Templates automatically unpublish if edited in a way that makes them invalid.
## Template Validation
Templates must meet these requirements before publishing:
* ✓ Name
* ✓ Description
* ✓ Icon
* ✓ At least one card type
* ✓ At least one complete section (with both title and description)
The publish toggle is disabled if requirements aren't met. Sections missing a title or description are filtered out during AI generation but don't prevent publishing.
## Editing Templates
All changes save automatically. Published template changes take effect immediately for new drafts. Existing drafts are not affected. If edits make a published template invalid, it automatically unpublishes.
## Managing Multiple Templates
### Copying Templates
Start with an existing template to create variants:
1. Click the menu icon (⋮) on any template in the list
2. Select **Copy Template**
3. A new template is created with "(Copy)" appended to the name
4. All sections are duplicated with new IDs
5. Copy is always created in draft status
6. Edit the copy to customize for your needs
**Use Cases**:
* Create variants for different audiences (technical vs. executive)
* Adapt templates for different maturity stages (early exploration vs. detailed planning)
* Customize for different product areas while maintaining base structure
### Deleting Templates
1. Click the menu icon (⋮) on the template
2. Select **Delete Template**
3. Confirm deletion
Deleted templates cannot be used for new drafts but existing drafts are preserved.
### Organizing Templates
Templates are automatically sorted:
* Published templates appear first
* Then draft templates
* Within each group, alphabetically by name
This ensures the most useful templates are always at the top.
## Template Management Best Practices
### Before Publishing
* [ ] Review generated output for quality and completeness
* [ ] Verify all required fields are complete
* [ ] Check section descriptions are clear and actionable
* [ ] Ensure card type targeting matches intended use
* [ ] Test on cards where context is not thin (contains surrounding insights, comments, and other supported data)
### Maintaining Templates
* Review templates regularly based on usage and feedback
* Update section descriptions to refine output quality
* Create variants rather than making breaking changes to published templates
* Unpublish templates that are no longer needed
### Iterative Improvement
Continuously improve templates based on draft quality:
1. **Generate draft** using template
2. **Note issues** during manual editing (what's missing, unclear, or needs restructuring)
3. **Update template** section descriptions to address issues
4. **Regenerate** to test improvements
5. **Iterate** until consistently good output
### Team Collaboration
* Use descriptive names and descriptions so team members understand when to use each template
* Document template purpose and use cases in the description field
* Create templates collaboratively by gathering section requirements from stakeholders
* Share examples of well-generated documents to demonstrate template value
## Troubleshooting
### Template Won't Publish
**Check validation errors** displayed below the publish toggle:
* Missing required fields (name, description, icon, card types)
* No complete sections (all sections missing title or description)
### Poor Output Quality
**Likely causes**:
* Section descriptions too vague
* Template too broad for specific use case
* Insufficient data in workspace (not a template issue)
**Solutions**:
* Review and improve section descriptions with specific guidance
* Create more focused templates for specific card types
* See "Template Design Principles" section above for guidance on focused vs. broad templates
### Template Not Appearing in Drafting
**Checklist**:
* Is template published? (Check toggle in template editor)
* Are you drafting on a compatible card type? (Check template's card type settings)
## Next Steps
* **[Drafting Workflow](/documentation/ai-document-drafting/drafting-workflow)**: Learn how to use templates for document generation
***
Questions about templates? Contact us at [support@vistaly.com](mailto:support@vistaly.com)
# Archiving
Source: https://docs.vistaly.com/documentation/core-concepts/archiving
Archiving work is a great way to keep a workspace clean and focused without losing historical data.
### Archiving paths
To archive a path, select **Archive card** in the card sub-menu.
### Viewing archived paths
Once a path is archived, you can view it by selecting any parent *(or ancestor)* card and selecting **Show archived cards** from the card sub-menu.
Edits to an archived card are not possible until the card is unarchived.
### Unarchiving paths
To unarchive a path, select the topmost **(root)** archived card, then select **Unarchive card** from the card sub-menu.
# Assumption
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/assumption
Assumptions are one of the supported [Discovery Space](/guides/getting-started/the-discovery-space) card types.
## What is an Assumption Card?
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.
## Learn more
To learn more about how to use assumptions with other card types, view the [Discovery Space](/guides/getting-started/the-discovery-space) guide.
# KPI/Metric
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/kpi
KPIs *(Key Performance Indicators)* are for quantitative measures of business performance, product usage, or user sentiment.
## What is a KPI Card?
Use the KPI card type to track business or product metrics that remain relevant over extended periods of time *(they are persistent)*.
Popular terms used to communicate this concept:
* Key Performance Indicator – KPI **(Vistaly Default)**
* Business Metric
* Health Metric
You can use the [Vistaly API](/documentation/integrations/vistaly-api) to sync your KPI cards your CRM, BI and product analytics tools, or spreadsheets. This way your workspace always has live, accurate data.
### KPI Thresholds and Statuses
You can set upper and lower thresholds for your KPIs to define acceptable performance ranges. This helps in identifying when a KPI is performing well or when it requires attention.
For example, if you wanted to be alerted when something like "conversion rate" dips below a given percentage, you could set a lower threshold for that KPI.
| **Stage** | Commitment | Description |
| ----------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **In Bounds** | Within acceptable parameters | The KPI measurement is currently within the defined threshold range, indicating healthy performance. |
| **Out of Bounds** | Outside acceptable parameters | The KPI measurement has crossed a defined threshold boundary, requiring attention and potential intervention. |
## Learn More
View the [Strategy Space Guide](/guides/getting-started/the-strategy-space) to learn how to use KPI Cards to make a special KPI Tree we call a ["Value Exchange Model"](/guides/getting-started/the-strategy-space#2-a-value-exchange-model).
# Objective
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/objective
Objectives are **Near-term Goal cards** that qualitatively describe the progress you want to make in the coming months/quarters/year.
## What is an Objective Card?
*Qualitatitive* near-term goal cards, like an Objective, help bridge the gap between long-term vision and actual execution work by *describing in words* the focus areas your team is pursuing in the current time period *(typically quarterly or bi-annually)*.
**Popular Terms:**
* Objective **(Default in Vistaly)**
* Initiative
* Narrative
* Strategy
If you utilize a goal setting framework like OKRs *(Objectives and Key Results)*, the Near-term strategic context in that framework is the Objective component.
Depending on the questions answered during onboarding, qualitative goal cards may be disabled by default. You can [enabled them](/documentation/core-concepts/card-types/overview#adjusting-card-type-language) at any time in Card Settings.
### Enabling the Objective Card
Depending on selections during onboarding, the Objective Card may be disabled by default. Enable this card type in Card Settings within your workspace administration panel.
## Learn More
View the [Strategy Space Guide](/guides/getting-started/the-strategy-space) to learn more about how Objective Cards fit into the broader strategy stack.
# Opportunity
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/opportunity
Opportunities are one of the supported [Discovery Space](/guides/getting-started/the-discovery-space) card types.
## 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
Whereas product usage metrics in your [Value Exchange Model](/guides/getting-started/the-strategy-space#2-a-value-exchange-model) tell you *what's* happening, Opportunities tell you *why* it's not happening more (or less, or faster, etc.)
## 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](/documentation/integrations/jira)**: Link Jira issues and epics to opportunities to track work addressing customer problems
* **[Linear Integration](/documentation/integrations/linear)**: Connect Linear issues and projects to opportunities for cross-team initiatives
When linked, delivery status and progress appear on opportunity cards in the [Roadmap view](/documentation/views/roadmap), helping you see both customer problems and the work being done to address them.
## Opportunity Card Best Practices
See the [best practices](/guides/getting-started/the-discovery-space#opportunity-space-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
# Outcome
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/outcome
Outcomes are Near-term Goal cards that quantitatively measure the progress you want to make in the coming months/quarters/year.
## What is an Outcome Card?
Outcome (or "Goal") cards measure success for specific objectives within a defined timeframe. They have clear start and end dates with target values to achieve.
Popular terms used to communicate this concept:
* Outcome **(Vistaly Default)**
* Key Result
* Goal
* Rock
If your team uses OKRs, you can think of Outcome Cards as the **Key Results** in your OKR framework.
## Outcome Statuses
Outcomes support the following statuses to communicate commitment and risk:
| **Stage** | Commitment | Description |
| --------------- | ----------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Uncommitted** | No official commitment | The outcome has been identified but not yet formally committed to by the team or organization. |
| **At Risk** | Committed but endangered | Progress toward the outcome is threatened by obstacles, delays, or resource constraints. |
| **Progressing** | Committed with active work | Work toward achieving the outcome is underway with noticeable progress, but not yet complete. |
| **On Track** | Committed and proceeding well | The outcome is being pursued according to plan, with expected progress and no significant obstacles. |
## Additional resources
* [KPI Trees & Time-bound Goals](/guides/metrics/kpi-trees)
# Card Type Overview
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/overview
Configure Vistaly Cards to match your business' language.
Not every business works the same – we get that.
We also know teams don't want to spend an incredible amount of time managing bespoke systems strung together by spreadsheets, slides, and wikis.
Vistaly strikes a balance between ultimate configurability and fully opinonated software. Take a look at how you can adjust Vistaly to match your work style 👇
## Configuring Card Types
Cards are core to how Vistaly works. There are several card types, each with its own purpose.
Here's an overview of each type and a general description.
| Card Type | Type | Common Names | Description | Required? | Enabled By Default? |
| ---------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | --------- | -------------------- |
| **[Workspace](/documentation/core-concepts/workspaces)** | - | - | Root card that contains and organizes all other cards in a workspace | Yes | Yes |
| **[Vision](/documentation/core-concepts/card-types/vision-statement)** | Strategy | - Vision Statement
- Mission Statement
- Strategic Pillar
| Long-term strategic context card that represents enduring organizational direction and purpose | No | No |
| **[KPI](/documentation/core-concepts/card-types/kpi)** | Strategy | - Business Metric
- Health Metric
| Persistent measurement card that tracks ongoing metrics relevant over extended periods, typically without end dates | No | Yes |
| **[Objective](/documentation/core-concepts/card-types/objective)** | Strategy | - Initiative
- Narrative
- Strategy
| Near-term strategic context card that bridges long-term vision with execution work, typically for a quarter or bi-annual period | No | Onboarding selection |
| **[Outcome](/documentation/core-concepts/card-types/outcome)** | Strategy | | Time-bound measurement card with clear start/end dates and target values to achieve within a defined period | No | Onboarding selection |
| **[Opportunity](/documentation/core-concepts/card-types/opportunity)** | Discovery | | Cards documenting customer problems, needs, or desires worth solving, based on customer conversations, feedback, and usage data | Yes | Yes |
| **[Solution](/documentation/core-concepts/card-types/solution)** | Discovery | | Actions taken to address identified Opportunities, which can include new features, improvements, or other interventions | Yes | Yes |
| **[Assumption](/documentation/core-concepts/card-types/assumption)** | Discovery | | Beliefs accepted as true without definitive proof that underlie Solution proposals and can be validated through experimentation | Yes | Yes |
| **[Experiment](/documentation/core-concepts/card-types/test)** | Discovery | | Evidence-gathering activities designed to validate or invalidate high-risk assumptions, saving time and resources | Yes | Yes |
### Adjusting Card Type Language
If you're using a name or concept not covered in the table above, modify the closest one matching the language or concepts you want to use.
1. Navigate to **Card Settings**
2. Select the card type to disable
3. Select a common name or "Customize"\*\* to set your own.
### Enabling / Disabling Card Types
**Workspace**, **Outcome**, **Opportunity**, and **Solution** are the required card types.
If a card type is not required, it can be removed from a workspace. Removing unused card types simplifies a workspace, while adding card types allows for advanced modeling, provides a layer of segmentation, or acts as a closer representation of how your business is structured.
To enable or disable a card type:
1. Navigate to **Card Settings**
2. Select the card type to disable
3. Toggle the "Card Type Enabled" field to **off**
# Solution
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/solution
Solutions are one of the supported [Discovery Space](/guides/getting-started/the-discovery-space) card types.
## What is an Solution Card?
Solutions are actions taken to address an Opportunity. This can be launching a new feature, improving an existing feature, improving documentation, and so on.
**Popular Terms:**
* Solution **(Default in Vistaly)**
* Bet
* Feature
## Statuses
Once solutions have been ideated, use statuses to communicate when and if the team will implment them. Solutions support the following status:
| Stage | Commitment | Description |
| ----------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Idea** | No/Unknown commitment | Initial concept for addressing an Opportunity. No commitment to implementation has been made. |
| **Not now** | No commitment | Solution evaluated but intentionally deprioritized due to resource constraints, technical limitations, or strategic considerations. |
| **Later** | Committed *(Moderate Confidence)* | Planned for a future timeframe beyond the current planning horizon. Recognized as valuable but with lower immediate priority than Now/Next items. |
| **Next** | Committed | Solution approved with implementation details being finalized. Awaiting resource allocation or developer availability. |
| **Now** | Committed | Solution actively under development. Implementation work is in progress. |
Note: Using "Later" for Solutions is generally discouraged. The "Later" status is more appropriate for Opportunities (problems) where you've committed to solving them but haven't yet fully defined the problem space or solution approach.
## Tracking Delivery Progress
Solutions can be linked to your engineering team's delivery tools to track implementation progress:
* **[Jira Integration](/documentation/integrations/jira)**: Link Jira issues and epics to solutions to track development status
* **[Linear Integration](/documentation/integrations/linear)**: Connect Linear issues and projects to see progress directly on your roadmap
When linked, delivery status and progress appear on solution cards in the [Roadmap view](/documentation/views/roadmap), giving you visibility into both strategic direction and execution reality.
## Learn more
To learn more about how to use solutions with other card types, view the [Discovery Space](/guides/getting-started/the-discovery-space) guide.
# Experiment
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/test
Experiments (Assumption Tests) are one of the supported [Discovery Space](/guides/getting-started/the-discovery-space) card types.
## What is an Experiment Card?
Experiments provide evidence to de-risk high-risk assumptions. As a result, they save time, money, and energy by preventing investment in a solution that will give little to no return on investment.
***Tip**: Consider running experiments on assumptions with weak evidence AND would run a high risk of project failure if not correctly understood.*
## Statuses
Once solution assumptions have been identified, use experiment *(assumption test)* statuses to communicate how tests are progressing. Experiments support the following statuses:
| **Stage** | Commitment | Description |
| -------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Developing** | In preparation | Experiment design is being created or refined before execution. Methods and metrics are being established. |
| **Pending** | Ready for execution | Experiment is fully designed and waiting to be run. All prerequisites are in place. |
| **Running** | In progress | Experiment is currently active and collecting data. Results are not yet available. |
| **Failed** | Completed (invalidated) | Experiment has concluded and results indicate the assumption was incorrect or not supported by evidence. |
| **Passed** | Completed (validated) | Experiment has concluded and results support the original assumption, providing validation. |
## Learn more
To learn more about how to use experiments with other card types, view the [Discovery Space](/guides/getting-started/the-discovery-space) guide.
# Vision/Mission
Source: https://docs.vistaly.com/documentation/core-concepts/card-types/vision-statement
Vision (Mission) Cards are part of the [Strategy Space](/guides/getting-started/the-strategy-space).
## What is a Vision Card?
Create a Vision or Mission card to represent the enduring organizational direction. They are the stable, overarching purpose that guides all work.
**Popular Terms:**
* Vision **(Default in Vistaly)**
* Mission Statement
* Strategic Pillar
By default, the Vision/Mission Card is disabled, this keeps getting started simple. As you begin to use Vistaly across the organization, enable this card type in [Card Settings](/documentation/core-concepts/card-types/overview#adjusting-card-type-language).
**Why Use One:**
* Provide long-term direction that spans multiple years
* Align all teams across the organization around common aspirations
* Serve as the foundational lens for downstream strategic decisions
## Learn More
View the [Strategy Space Guide](/guides/getting-started/the-strategy-space) to learn more about the Vision (Mission) Cards fit into the broader strategy stack.
# Commenting
Source: https://docs.vistaly.com/documentation/core-concepts/commenting
Commenting supports documenting learning, and collaboration across one or more teams.
## How do I view comments?
Each card supports a comment thread, and the comment bubble on the front of the card indicates how many comments have been made.
Selecting the icon will open the comment thread in the side panel.
## Notify users with @mention
When writing a comment, the **@** symbol will display a list of users to be referenced and notified.
# Custom Fields
Source: https://docs.vistaly.com/documentation/core-concepts/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.
# External Links
Source: https://docs.vistaly.com/documentation/core-concepts/external-links
Add links to external resources like Figma, Notion, Google Docs, etc.
Product work can be messy and spread across a handful of tools. Designs, specs, and other important context often live in tools outside of Vistaly—like Figma, Google Docs, Miro, GitHub, and more.
External links allow you to reference these resources directly from your Vistaly cards, keeping all relevant information connected and accessible.
### How to add/manage external links
External links can be added to any card in Vistaly. When viewing a card, look for the external links section where you can add URLs to relevant resources.
Each link can include:
* **URL** - The web address of the resource
* **Title** - A descriptive name to help identify the resource
You can edit or remove external links at any time by clicking on the card to open the card details panel.
# Filters
Source: https://docs.vistaly.com/documentation/core-concepts/filters
Filters are a great tool for creating custom views of your data.
## Configuring Filters
Vistaly filters are flexible. See the different ways you can configure them to view your data.
### Combining (composing) filters
Combining filters together is a powerful way to look at different match criteria. Add multiple conditions to create different views.
* ALL criteria - When the filter criteria is set to ALL, results are returned only if they match all of the filters.
* ONE criteria - When the filter criteria is set to ONE, results are returned if they match any one of the filters.
* NONE criteria - When the filter criteria is set to NONE, results are returned only if they match none of the filters.
### Include Full Hierarchy
`Include Filter Hierarchy?` will make it match on the filtered cards and also show their parents all the way up to the top of your tree.
### Dyanmic Filters (Custom Fields)
Adding [custom fields](/documentation/core-concepts/custom-fields) to cards will make them accessible to filters.
## Sharing Filters With Your Team
When you save a filter, they automatically are shared and usable by other members of your organization.
## Popular Filters
Check out some of the more interesting filter use cases:
### Use Case 1: High value Opportunities
Filter by Opportunities that have at least *X* Insights and high values in the [custom fields](/documentation/core-concepts/custom-fields) that track severity, pain level, or importance.
### Use Case 2: Opportunities by customer(s)
Look at your tree through the eyes of a specific customer or customer segment. Use the customer filter to reveal opportunities identified after talking to specific customer(s).
### Use Case 3: Work that’s in-flight
Use time filters to show Solutions and Opportunities that have a status of Now/Next/Later.
### Use Case 4: What’s new?
Use time filters to show everything that’s been add or updated in the last day/week/month.
### Use Case 5: Show a specific team’s work
Used in combination with assignement, filter the tree to see any cards that are assigned to a given person or team.
# Inviting Team Members
Source: https://docs.vistaly.com/documentation/core-concepts/inviting-team-members
Inviting members of your team to collaborate in vistaly.
## Two types of users
In Vistaly, there are two primary classes of users:
* **Editors** - Editors are users who can create/delete/re-organize cards on the tree, update the position of cards in the roadmap, update KPI/Outcome metric values, and attach Insights to cards.
* **Viewers** - Viewers can see everything in all of the workspaces but can't create/edit any cards. They can also [submit product feedback](/documentation/views/insights#customer-feedback).
## Editors
### Who you should add as Editors
You should **definitely** add each Product Manager (from individual contributors all the way up through product leadership).
You should **probably** add a seat for any researcher/designer/engineering lead that materially participates in the [discovery process](/guides/getting-started/the-discovery-space).
### How to add Editors
To invite team members to collaborate in a workspace, click the "+ Team" button at the top right of the workspace or go to the Manage Team page in the settings.
### Seat limits depend on your plan
* **During trial** - During your trial period, Editor seats are uncapped. When your trial is ending, you may need to remove some Editors in order to select the plan you want to move forward with
* **For "Starter" plan subscribers** - The Starter plan comes with 4 Editor seats and you can pay \$35/mo/user for up to 4 additional Editors seats (for a total of 8).
* **For "Business" plan subscribers** - The Business plan comes with 10 Editor seats and you can pay \$70/mo/user for up to 10 additional Editors seats (for a total of 20).
* **For "Enterprise" plan subscribers** - Enterprise subscriptions are customized to your needs.
## Viewers
All plans come with *unlimited* Viewers so that you can easily share context about what the Product team is working with the rest of your company.
### How to add Viewers
To invite Viewers, click the "+Team" button at the top right of the workspace or go to the Manage Team page in the settings.
Make sure to flip over to the "Viewers" tab.
## Permissions for Admins, Editors, and Viewers
When adding a user, you'll have the option give them a "Role". Roles have the following permission levels.
| | Admins | Editors | Viewers |
| --------------------------------------------------------------------------------------------------------------------- | ------ | ------- | ------- |
| Access the [Tree View](/documentation/views/tree) | X | X | X |
| Access the [Roadmap View](/documentation/views/roadmap) | X | X | X |
| Access the [Reports View](/documentation/views/reports) | X | X | X |
| Access the [Experiment Tracker](/documentation/views/test-tracker) | X | X | X |
| Make updates to card's name, status, value | X | X | - |
| Create and attach new [Insights](/documentation/views/insights) | X | X | - |
| Leave [comments](/documentation/core-concepts/commenting) on cards | X | X | - |
| Create a new [Workspace](/documentation/core-concepts/workspaces) | X | X | - |
| Manage [labels](/documentation/core-concepts/labels/) | X | X | - |
| Invite new Viewers | X | X | - |
| Invite new Editors | X | X | - |
| Invite new Admins | X | - | - |
| Add/configure the [Jira](/documentation/integrations/jira) or [Slack](/documentation/integrations/slack) integrations | X | - | - |
# Labels
Source: https://docs.vistaly.com/documentation/core-concepts/labels
Labels are designed to be a flexible tagging system for your data. Use them to annotate and filter data.
## Adding Lables
Create labels by either adding them inline or through the labels settings page.
To bulk remove, update, and change label color. Visit the settings page
> Warning: Be careful when removing a label. Removing labels also removes all references to that label.
## Filtering
The Tree view can be filtered by using the label filter.
See the [filter documentation](/documentation/core-concepts/filters) to see more advanced use cases.
# Notifications
Source: https://docs.vistaly.com/documentation/core-concepts/notifications
Get notified when important conversations happen
## Viewing notifications
The bell icon in the upper right corner of the workspace opens the notification center. The red dot indicants that there are unread notifications in the inbox.
Notifications can be in the **inbox**, or marked as **done**.
## Inbox
The inbox contains notifications marked **read** or **unread** *(indicated by the blue circle)*.
After selecting one or more notification, they may be marked as **read**, **unread**, or **done**.
## Done
Once a notification is marked as done, it remains accessible in the done tab.
## Receiving Notifications
Several events may trigger notifications. However, most notifications take place around a specific card in the workspace.
Each card may be **watched**. When a card is watched, important changes to the card will create new notifications.
### Watching/Unwatching a card
To watch a card, select the watch button in the upper right-hand corner of the card panel.
*Note: Being @mentioned in the comments, or assigned to a card, will auto-watch the card.*
To stop receiving notifications on a card, select the unwatch button in the upper right-hand corner of the card panel.
## Slack notifications
If you have enabled the Slack integration, notifications will automatically be sent to your personal Slack bot channel.
To enable Slack, see the [Slack Installation Guide](/documentation/integrations/slack).
## Notification Preferences
To control the email notifications, visit the personal settings page to set your preferences.
# Statuses
Source: https://docs.vistaly.com/documentation/core-concepts/statuses
Statuses are used to communicate risk, commitment, and progress across all card types.
## Status Framework by Card Type
Each card type in the system uses a specific set of statuses to indicate its current state in the workflow. These built-in statuses provide enhanced functionality and visual cues that improve team collaboration and communication efficiency.
### KPI Statuses
You can set upper and lower thresholds for your KPIs to define acceptable performance ranges. This helps in identifying when a KPI is performing well or when it requires attention.
For example, if you wanted to be alerted when something like "conversion rate" dips below a given percentage, you could set a lower threshold for that KPI.
| **Stage** | Commitment | Description |
| ----------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **In Bounds** | Within acceptable parameters | The KPI measurement is currently within the defined threshold range, indicating healthy performance. |
| **Out of Bounds** | Outside acceptable parameters | The KPI measurement has crossed a defined threshold boundary, requiring attention and potential intervention. |
### Outcome Statuses
Outcomes support the following statuses to communicate commitment and risk:
| **Stage** | Commitment | Description |
| --------------- | ----------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Uncommitted** | No official commitment | The outcome has been identified but not yet formally committed to by the team or organization. |
| **At Risk** | Committed but endangered | Progress toward the outcome is threatened by obstacles, delays, or resource constraints. |
| **Progressing** | Committed with active work | Work toward achieving the outcome is underway with noticeable progress, but not yet complete. |
| **On Track** | Committed and proceeding well | The outcome is being pursued according to plan, with expected progress and no significant obstacles. |
### Opportunity 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. |
### Solution Statuses
Once solutions have been ideated, use statuses to communicate when and if the team will implment them. Solutions support the following status:
| Stage | Commitment | Description |
| ----------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Idea** | No/Unknown commitment | Initial concept for addressing an Opportunity. No commitment to implementation has been made. |
| **Not now** | No commitment | Solution evaluated but intentionally deprioritized due to resource constraints, technical limitations, or strategic considerations. |
| **Later** | Committed *(Moderate Confidence)* | Planned for a future timeframe beyond the current planning horizon. Recognized as valuable but with lower immediate priority than Now/Next items. |
| **Next** | Committed | Solution approved with implementation details being finalized. Awaiting resource allocation or developer availability. |
| **Now** | Committed | Solution actively under development. Implementation work is in progress. |
Note: Using "Later" for Solutions is generally discouraged. The "Later" status is more appropriate for Opportunities (problems) where you've committed to solving them but haven't yet fully defined the problem space or solution approach.
### Experiment Statuses
Once solution assumptions have been identified, use experiment *(assumption test)* statuses to communicate how tests are progressing. Experiments support the following statuses:
| **Stage** | Commitment | Description |
| -------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Developing** | In preparation | Experiment design is being created or refined before execution. Methods and metrics are being established. |
| **Pending** | Ready for execution | Experiment is fully designed and waiting to be run. All prerequisites are in place. |
| **Running** | In progress | Experiment is currently active and collecting data. Results are not yet available. |
| **Failed** | Completed (invalidated) | Experiment has concluded and results indicate the assumption was incorrect or not supported by evidence. |
| **Passed** | Completed (validated) | Experiment has concluded and results support the original assumption, providing validation. |
## Now / Next / Later Syncing
The roadmap view automatically syncs decisions made in the tree to prioritize opportunities and solutions. View the [Roadmap Documentation](/documentation/views/roadmap#card-%26-column-statuses) to learn more about how statuses keep the roadmap in sync with the tree.
# Unmapped Cards
Source: https://docs.vistaly.com/documentation/core-concepts/unmapped-cards
Unmapped cards where cards go that don't have a clear space on the tree or are not ready to be placed there.
## Navigating to Unmapped cards
To see your Unmapped card, click the nav item in the left-side navigation. From there you can add an Unmapped Card.
## Adding from the Roadmap
You can also add an Unmapped card directly into a column on the [Roadmap View](/documentation/views/roadmap).
## Adding to the Tree
Add an Unmapped card to the tree by navigating to Unmapped cards, clicking the "Add to Tree" button on the Unmapped card you'd like to move, and selecting the parent you'd like to place the Unmapped card under.
# Workspaces
Source: https://docs.vistaly.com/documentation/core-concepts/workspaces
Vistaly workspaces contain strategy and discovery cards.
## Naming Workspaces
At the top of the Tree view is the Workspace card. Update the name of the workspace card to change the name of the workspace.
> **Note**: Each Workspace contains exactly one workspace card.
## Multiple Workspaces
To add new workspaces, open the workspace selector in the top navigation bar.
If you'd like to learn more about how many workspaces you need, see the [workspace planning](/guides/getting-started/workspace-planning) guide.
## Consultants & Fractional Executives
Consultants & Fractional Executives - If you work with multiple companies and need separate Vistaly environments for each client, contact [support@vistaly.com](mailto:support@vistaly.com) to set up multiple instances.
# Browser Extension
Source: https://docs.vistaly.com/documentation/integrations/browser-extension
Send feedback to Vistaly using the browser extension
## What it does
The Vistaly browser extension is used to push feedback from any website to Vistaly.
### Installation
1. [Click here](https://chrome.google.com/webstore/detail/jabhpgfbocbdcbabjmnbfkohbjjhneii) to download the extension in the chrome webstore.
> Note: The extension is currently only available on chrome.
2. Pin the extension
* Select the extension icon in the upper right of the browser.
* Select the pin icon next to the Vistaly extension.
### Usage
Select the Vistaly extension to a Feedback from any webpage. Then copy or draft your Feedback. When done, select the **Add Feedback** button at the bottom of the form.
The **URL** will automatically populate using your current web location. This can be particularly helpful when adding a Feedback from support tools.
# Google Sheets
Source: https://docs.vistaly.com/documentation/integrations/google-sheets
Create a simple Google Sheets integration using App Script
Use the Google Sheets integration to get data from spreadsheets into Vistaly.
# Setting up a direct sync
Following these steps will create a live sync between your Google Sheets and Vistaly.
* Step 1: Format your Sheet
* Step 2: Add the Google App Script
* Step 3: Create/Enter your API Key
* Step 4: Set the "On edit" Trigger
## Step 1 (Format your Sheet)
Add the following column headers to your spreadsheet. You can rename these, but the order is important if you don't want to modify the App Script code shared in the next step.
| A) Vistaly Card ID | B) Metric Name | C) Metric Value | D) Lasted Updated At | E) Last Updated By |
| ------------------------- | ------------------ | ------------------------ | -------------------------------- | --------------------------- |
| ID of the card in Vistaly | Name of the metric | Last Value of the Metric | When the metric was last updated | Who last updated the metric |
Note: Both `Column D` and `Column E` automatically update once a change to the metric value has been saved in Vistaly.
#### Column A (Vistaly Card ID)
This is the identifier that will link this row of your spreadsheet to a Vistaly card. You can only link Vistaly Cards that support numeric values *(KPIs, Outcomes, Key Results, etc...)*
To find a Card ID, open your Vistaly workspace, select the card you want to link and copy the last part of the URL (the `cardId` query parameter)
*ex: app.vistaly.com/w/IGOeM6Ymm1q8bcnYsuZcb?cardId=**5tx6DnTlsCRCgnWGWXjZ1***
#### Additional Columns
You can add any additional columns you need after these 5 required columns without issue.
## Step 2 (Add the Google App Script)
The App Script will set up a live sync between your spreadsheet and Vistaly.
Select `Extensions > App Script` and paste the App Script Code into the Editor.
```js theme={null}
function onEditHandler(e) {
try {
// 1. Determine what was edited
const range = e.range;
const row = range.getRow();
const col = range.getColumn();
// 2. Check if the edited cell is in column C (col = 3)
if (col === 3) {
const sheet = range.getSheet();
// 3. Update column D (Last Updated) with the current timestamp
const timestamp = new Date().toISOString();
sheet.getRange(row, 4).setValue(timestamp); // Column D = 4
// 4. Update column E (Last Updated By) with the editor's email
const userEmail = Session.getActiveUser().getEmail() || 'Unknown User';
sheet.getRange(row, 5).setValue(userEmail); // Column E = 5
// 5. Get the value in column A (ID) and column C (numeric value)
const colAValue = sheet.getRange(row, 1).getValue(); // Column A = 1
const numericValueC = Number(range.getValue()); // Column C value (numeric)
// 6. Check that column A has a valid ID (non-empty string)
if (typeof colAValue === 'string' && colAValue.trim() !== '') {
// 7. Construct the API payload
const payloadObj = {
timestamp: timestamp,
value: numericValueC
};
const payload = JSON.stringify(payloadObj);
// 8. Build the API URL
const url = `https://api.vistaly.com/v1/cards/${colAValue}/metrics`;
// 9. Prepare fetch options, including the API Key
const apiKey = PropertiesService.getScriptProperties().getProperty('API_KEY');
const options = {
method: 'post',
contentType: 'application/json',
headers: {
Authorization: `Bearer ${apiKey}`
},
payload: payload,
muteHttpExceptions: true
};
// 10. Make the POST request
const response = UrlFetchApp.fetch(url, options);
// 11. (Optional) Log the response for debugging
Logger.log('URL: ' + url);
Logger.log('Payload: ' + payload);
Logger.log('Response code: ' + response.getResponseCode());
Logger.log('Response body: ' + response.getContentText());
}
}
} catch (err) {
Logger.log('Error in onEditHandler: ' + err);
}
}
```
## Step 3 (Create/Enter your API Key)
To authenticate your Google Sheet with your Vistaly workspace, you first need to add your API Key. If you haven't created an API Key yet, [follow these steps](/documentation/integrations/vistaly-api#setting-up-your-first-api-key) to create one.
Then add your API Key in the Google App Script Editor by selecting the `Settings` page and then scrolling down to `Script Properties`. Add the property as `API_KEY` and the value as your secret Vistaly API Key and select **Save script properties**.
## Step 4 (Set the "On edit" Trigger)
The last thing you need to do is tell Google how you want the App Script to run.
Go to the `Triggers`, page and update the for to reference your App Script.
Note: If you haven't set something like this up before, you will have to authorize Google to talk to external sources.
## Testing it out
You're all set. Whenever you make changes to a value in your spreadsheet, as long as the Vistaly Card ID is set in the corresponding row, it will automatically update Vistaly.
As always, if you experience any issues getting set up, reach out to [support@vistaly.com](mailto:support@vistaly.com).
# Jira
Source: https://docs.vistaly.com/documentation/integrations/jira
Integrate Jira with Vistaly
Integrating Jira with Vistaly helps align teams by providing the context of why their work matters to customers and the business. When Jira issues and epics are linked to Vistaly cards, individual contributors can see what their work is connected to and how it's measured.
## Key Benefits
* **See strategy and delivery in one place**: View Jira issue progress directly on your roadmap cards, connecting strategic outcomes with engineering execution
* **Connect work to customer impact**: Engineering teams can trace their Jira issues back to the customer problems and business outcomes they're addressing
* **Link to any card type**: Connect Jira issues and epics to Solutions, Opportunities, Outcomes, or any other card type in Vistaly
* **Enhanced workflow support**: Create epics, link child issues to parent epics, and transition issues through your Jira workflows
* **Progress visibility**: Track Jira epic and issue status directly on Vistaly card faces in the roadmap view
* **Smart search and linking**: Search across multiple projects and issue types, or paste Jira URLs for instant connections
## Installing the Vistaly Jira App
To install the Vistaly Jira app:
1. Visit the integrations page in Vistaly and select 'Add to Jira'
2. A new window will open where you can install the Vistaly app to your Jira site
3. Select "Get app" to begin the installation
4. Choose your Jira site from the list (most teams have one site)
5. Navigate to "Manage your apps" and select Vistaly in the lefthand menu
6. Select "Allow access" to grant Vistaly permission to connect
7. Review the permissions Vistaly requests and select "Accept"
8. Choose which Vistaly organization should have access to the Jira site
Once connected, you'll see a Jira tab appear on your Vistaly cards.
## Linking to Jira from Vistaly
With the Jira integration installed and the Vistaly organization connected, any card in Vistaly will now have a Jira tab. You can link Jira issues to Solutions, Opportunities, Outcomes, or any other card type where you want to track delivery work.
Select the Jira tab on an unlinked card - this will present options to create a new Jira issue or epic, or link to an existing Jira issue. After selecting "Create & Link", you'll choose from the available Jira projects and issue types configured in your workspace.
### Enhanced Field Support
Vistaly now supports comprehensive Jira field types when creating issues:
* **User assignment**: Assign issues to team members during creation
* **Labels**: Add Jira labels to organize your issues
* **Dates**: Set due dates, start dates, and other date fields
* **Priorities**: Choose from your Jira priority levels
* **Custom fields**: Support for text, numeric, select, and multi-select custom fields
* **Epic linking**: Create standard issues and link them to parent epics
The Jira integration remembers your last selected project and issue type, making repeated issue creation much faster.
### Creating and Linking Epics
You can create Jira epics directly from Vistaly and link child issues to parent epics:
1. Select "Create & Link Epic" from the Jira tab
2. Choose your project and epic issue type
3. Fill in the epic details
4. Click "Create Epic"
When creating standard issues, you can link them to existing epics by searching for the parent epic during issue creation.
### Linking Existing Issues
If you link to an existing issue, you have two options:
1. **Search**: Use Jira's native search across multiple projects and issue types simultaneously
2. **Paste URL**: Copy a Jira issue URL and paste it to instantly link the issue
The enhanced search capability allows you to filter by project and issue type, making it easy to find the right issue even in large Jira instances.
Once the issue is created and linked, the Jira issue details and external link will be available in the Jira tab.
## Updating Jira Issues from Vistaly
Once a Jira issue is linked to a Vistaly card, you can update its status directly from Vistaly using Jira workflow transitions:
### Status Transitions
1. Open the Jira tab on a linked card
2. View the current issue status
3. Click on the status to see available transitions based on your Jira workflow
4. Select a new status to transition the issue
The status change is immediately reflected in both Vistaly and Jira, keeping both systems in sync.
## Viewing Progress in the Roadmap
When Jira issues and epics are linked to cards, their status and progress appear directly on card faces in the roadmap view.
This powerful feature allows product leaders to:
* See at a glance which initiatives are on track in Jira
* Understand delivery status alongside strategic outcomes
* Identify work that needs attention
* Connect strategic goals to engineering execution
The roadmap view shows both your strategic direction (Opportunities, Outcomes) and delivery reality (Jira issue status) in one unified view.
## Linking to Vistaly from Jira
To link from Jira to Vistaly, you can enter the Vistaly card identifier within the Jira issue. To get the card identifier, select the card in Vistaly and copy the identifier from the URL.
## Multiple Issues per Card
You can link multiple Jira issues to a single Vistaly card, which is useful for:
* Breaking down large Solutions into multiple implementation issues
* Tracking work across different Jira projects
* Managing phased delivery approaches
* Connecting related technical work to the same strategic goal
Each issue can be tracked and updated independently while maintaining the connection to your strategic context.
## Best Practices
### When to Use Jira Epics vs. Issues
Based on how teams are using the Jira integration:
* **Use Jira Epics** for:
* **Opportunities** - Large customer problems or needs that span multiple solutions
* **Large Solutions** - Complex features that require multiple issues to implement
* Multi-sprint initiatives that involve coordination across the team
* Work that breaks down into multiple smaller deliverables
* **Use Jira Issues** for:
* **Solutions** - Individual features and improvements that deliver customer value
* Specific implementation tasks that can be completed within a sprint or two
**Tracking Maintenance and Technical Debt:**
Bugs, technical debt, and "keeping the lights on" work are typically managed entirely in Jira. However, some teams create a "Maintenance" or "Non-Strategic Work" bucket in Vistaly and link these issues there. This allows you to visualize:
* How much time and energy is spent on strategic vs. non-strategic work
* The balance between new features and maintenance
* Where engineering capacity is actually going
This visibility helps product leaders make informed decisions about resource allocation and technical debt prioritization.
### Organizing Your Integration
* **Link Jira epics to Opportunities or large Solutions** - This helps track the bigger customer problems and complex features you're addressing
* **Link Jira issues to Solutions** - Connect individual features and improvements to track their delivery progress
* Use Vistaly's roadmap view to see both strategy and delivery status together
* Keep issue and epic status current to maintain accurate progress visibility on your roadmap
* Consider linking multiple Jira issues to a single Solution when breaking down complex work
### Communication and Alignment
* Share roadmap views with stakeholders to show strategy + progress
* Use Jira's link back to Vistaly to give engineers strategic context
* Update Jira issue status through your normal workflow - changes sync automatically
* Connect customer feedback in Vistaly to show engineers the "why" behind their work
## Updating the Vistaly Jira App
If a new version of the Vistaly Jira App is available, you can update it by navigating to the following url
(make sure to replace `your-jira-instance` with your appropriate identifier) and selecting "Update".
```
https://your-jira-instance.atlassian.net/plugins/servlet/upm
```
## Learn More
* View your connected Jira issues and epics in the [Roadmap view](/documentation/views/roadmap)
* Learn about [Solution cards](/documentation/core-concepts/card-types/solution) and delivery tracking
* Compare with the [Linear integration](/documentation/integrations/linear) for alternative delivery tracking
* Explore the [Vistaly API](/documentation/integrations/vistaly-api) for custom Jira integrations
# Linear
Source: https://docs.vistaly.com/documentation/integrations/linear
Integrate Linear with Vistaly
Integrating Linear with Vistaly helps align product strategy with delivery execution. When Linear issues and projects are connected to Vistaly cards, teams can see the full context of why their work matters to customers and the business, while product leaders can track delivery progress alongside strategic outcomes.
## Key Benefits
* **See strategy and delivery in one place**: View Linear project and issue progress directly on your roadmap cards, connecting strategic outcomes with engineering execution
* **Connect work to customer impact**: Engineering teams can trace their Linear issues back to the customer problems and business outcomes they're addressing
* **Bidirectional sync**: Create and update Linear issues and projects from Vistaly, and changes flow both ways to keep teams aligned
* **Smart search and linking**: Find and link Linear issues or projects using native Linear search, or paste Linear URLs for instant connections
* **Progress visibility**: Track Linear project completion percentage and issue status directly on Vistaly card faces in the roadmap view
## Installing the Linear Integration
To install the Linear integration, visit the integrations page in Vistaly and select 'Add to Linear'.
You'll be redirected to Linear to authorize Vistaly's access to your workspace. After authorization, select which Linear teams you want to connect to your Vistaly organization.
Once connected, you'll see a Linear tab appear on your Vistaly cards where you can link issues and projects.
## Linking Linear Issues to Vistaly Cards
You can link Linear issues to any card type in Vistaly - Solutions, Opportunities, Outcomes, or any other card where you want to track delivery work.
### Creating a New Linear Issue
1. Open a Vistaly card and select the Linear tab
2. Click "Create & Link Issue"
3. Choose your Linear team
4. Fill in the issue details:
* Title (pre-populated from your card)
* Description (can be AI-enhanced based on card context)
* Priority
* Assignee
* Status
* Labels
* Parent project (optional)
5. Click "Create Issue"
The issue is created in Linear and automatically linked to your Vistaly card. The Linear team selection is remembered for faster workflow next time.
### Linking an Existing Linear Issue
You have two ways to link existing Linear issues:
**Option 1: Search**
1. Open the Linear tab on a Vistaly card
2. Click "Link Existing Issue"
3. Search for your issue using Linear's native search
4. Select the issue from search results
**Option 2: Paste URL**
1. Copy a Linear issue URL from your browser
2. Open the Linear tab on a Vistaly card
3. Click "Link Existing Issue"
4. Paste the Linear URL
5. The issue is automatically detected and linked
### Updating Linear Issues from Vistaly
Once linked, you can update Linear issue properties directly from Vistaly:
* **Status**: Change workflow state using available Linear states
* **Priority**: Update priority level (No priority, Urgent, High, Medium, Low)
* **Assignee**: Assign or reassign team members
* **Labels**: Add or remove Linear labels
* **Project**: Move the issue to a different Linear project
All updates sync immediately to Linear.
## Linking Linear Projects to Vistaly Cards
Linear projects are ideal for tracking larger initiatives connected to Outcomes or Opportunities in Vistaly.
### Creating a New Linear Project
1. Open a Vistaly card and select the Linear tab
2. Click "Create & Link Project"
3. Fill in the project details:
* Name (pre-populated from your card)
* Description
* Lead
* Teams
* Priority
* Status
* Start date and target date
4. Click "Create Project"
The project is created in Linear with all your settings and immediately linked to your Vistaly card.
### Linking an Existing Linear Project
Similar to issues, you can link existing projects by:
1. Searching for the project name in the Linear tab
2. Pasting a Linear project URL
### Updating Linear Projects from Vistaly
Update project properties directly from Vistaly:
* **Status**: Change project status (Backlog, Planned, Started, Paused, Completed, Canceled)
* **Priority**: Set project priority
* **Lead**: Assign a project lead
* **Dates**: Update start date and target date
Changes sync immediately to Linear.
## Viewing Progress in the Roadmap
One of the most powerful features of the Linear integration is seeing delivery progress directly on your roadmap.
### Linear Project Progress
When a Linear project is linked to a card, the project's completion percentage appears on the card face in the roadmap view. This allows product leaders to:
* See at a glance which initiatives are on track
* Identify projects that need attention
* Understand delivery velocity across your product portfolio
* Connect strategic outcomes to engineering execution
### Linear Issue Status
Linked Linear issues display their current status on Vistaly cards, helping teams:
* Track solution delivery progress
* Understand what's in progress vs. completed
* See workflow state without leaving Vistaly
## Bi-directional Sync and Context
### From Vistaly to Linear
When you create a Linear issue or project from Vistaly, Linear cards automatically include a link back to the Vistaly card. This gives engineering teams one-click access to:
* The customer problems being solved
* Related customer feedback and research
* Strategic outcomes this work contributes to
* Success metrics and how this work will be measured
### From Linear to Vistaly
Status changes, progress updates, and metadata changes in Linear automatically sync to Vistaly, ensuring:
* Stakeholders see current progress without asking for updates
* Product roadmaps reflect real delivery status
* Strategic discussions are grounded in execution reality
## AI-Powered Description Enhancement
When creating Linear issues from Vistaly, you can use AI to generate comprehensive issue descriptions based on your card's content:
1. Click "Create & Link Issue"
2. Select "Enhance with AI" in the description field
3. AI analyzes your card context (including linked customer feedback, parent cards, and related content)
4. A detailed description is generated, including:
* Problem context
* Success criteria
* Related customer insights
* Implementation considerations
This helps ensure engineering teams have full context without manual copy-pasting.
## Multiple Linear Issues per Card
You can link multiple Linear issues to a single Vistaly card, which is useful for:
* Breaking down large Solutions into multiple implementation issues
* Tracking work across different Linear teams
* Managing phased delivery approaches
* Connecting related technical work to the same strategic goal
## Search Capabilities
The Linear integration supports powerful search:
* **Full-text search**: Find issues and projects by title, identifier, or description
* **Multi-team search**: Search across all connected Linear teams
* **URL detection**: Automatically detect and link when you paste Linear URLs
* **Real-time results**: Search results update as you type
## Best Practices
### When to Use Linear Projects vs. Issues
Based on how teams are using the Linear integration:
* **Use Linear Projects** for:
* **Opportunities** - Large customer problems or needs that span multiple solutions
* **Large Solutions** - Complex features that require multiple issues to implement
* Multi-sprint initiatives that involve coordination across the team
* Work that breaks down into multiple smaller deliverables
* **Use Linear Issues** for:
* **Solutions** - Individual features and improvements that deliver customer value
* Specific implementation tasks that can be completed within a sprint or two
**Tracking Maintenance and Technical Debt:**
Bugs, technical debt, and "keeping the lights on" work are typically managed entirely in Linear. However, some teams create a "Maintenance" or "Non-Strategic Work" bucket in Vistaly and link these issues there. This allows you to visualize:
* How much time and energy is spent on strategic vs. non-strategic work
* The balance between new features and maintenance
* Where engineering capacity is actually going
This visibility helps product leaders make informed decisions about resource allocation and technical debt prioritization.
### Organizing Your Integration
* **Link Linear projects to Opportunities or large Solutions** - This helps track the bigger customer problems and complex features you're addressing
* **Link Linear issues to Solutions** - Connect individual features and improvements to track their delivery progress
* Use Vistaly's roadmap view to see both strategy and delivery status together
* Keep project and issue status current to maintain accurate progress visibility on your roadmap
* Consider linking multiple Linear issues to a single Solution when breaking down complex work
### Communication and Alignment
* Share roadmap views with stakeholders to show strategy + progress
* Use Linear's back-link to Vistaly to give engineers strategic context
* Update Linear project status regularly to keep roadmap views accurate
* Connect customer feedback in Vistaly to show engineers the "why" behind their work
## Troubleshooting
### Linear Integration Not Appearing
If you don't see the Linear tab on your cards:
1. Check that the Linear integration is installed on your organization's integrations page
2. Ensure you have editor privileges in the Vistaly workspace
3. Try refreshing the page
### Issues or Projects Not Syncing
If changes aren't appearing:
1. Check your internet connection
2. Verify you have appropriate permissions in Linear
3. Refresh the Vistaly page to see latest updates
4. Check Linear's API status if issues persist
### Permission Issues
If you can't create or update Linear items:
1. Verify your Linear workspace permissions
2. Ensure the Linear integration has the necessary scopes
3. Try reconnecting the integration from the settings page
## Learn More
* View your connected Linear issues and projects in the [Roadmap view](/documentation/views/roadmap)
* Learn about [Solution cards](/documentation/core-concepts/card-types/solution) and delivery tracking
* Explore the [Vistaly API](/documentation/integrations/vistaly-api) for custom Linear integrations
# Microsoft Single Sign-On
Source: https://docs.vistaly.com/documentation/integrations/microsoft-sso
Using Microsoft accounts to sign in to Vistaly
## Overview
Microsoft Single Sign-On (SSO) is **available by default** for all Vistaly organizations. Your team members can sign in to Vistaly using their existing Microsoft accounts without any setup or configuration required.
Vistaly provides a pre-configured Microsoft application that supports both personal Microsoft accounts (Outlook.com) and enterprise Azure Active Directory accounts.
**Key Benefits:**
* **Available immediately** - No setup or configuration required
* **Supports both personal and business accounts** - Team members can use their preferred Microsoft account
* **Streamlined login** - Single click sign-in process
* **Enhanced security** - Leverages Microsoft's authentication and security features
## How to Use Microsoft SSO
### For Team Members
Microsoft SSO is ready to use immediately:
1. Navigate to [https://app.vistaly.com](https://app.vistaly.com)
2. Click **Sign In with Microsoft**
3. Enter Microsoft credentials (if not already signed in)
4. Grant permission to Vistaly (first-time users only)
5. You'll be automatically signed in to Vistaly
## Enterprise Azure AD Configuration
If your organization uses Azure Active Directory and has strict security policies, your IT administrator may need to pre-approve the Vistaly Microsoft application.
### Vistaly Application Details
| Property | Value |
| ---------------- | -------------------------------------- |
| Application Name | Vistaly |
| Client ID | `1ac1c83c-033d-4880-a445-11cc26029cfa` |
| Publisher | Vistaly |
### For IT Administrators
To pre-approve Vistaly in your Azure AD tenant:
1. **Sign in to Azure Portal**
* Navigate to [portal.azure.com](https://portal.azure.com)
* Go to **Azure Active Directory** > **Enterprise Applications**
2. **Add Vistaly Application**
* Search for applications using Client ID: `1ac1c83c-033d-4880-a445-11cc26029cfa`
* Or contact your Vistaly administrator for assistance with enterprise setup
3. **Grant Admin Consent** (if required by your organization's policies)
* Review the permissions requested by Vistaly
* Grant admin consent to allow users to sign in
**Note**: Most organizations do not require pre-approval, as Vistaly only requests basic profile and email permissions.
# Model Context Protocol (MCP)
Source: https://docs.vistaly.com/documentation/integrations/model-context-protocol
Connect AI assistants like Claude Desktop to your Vistaly workspace
The Vistaly MCP server is currently in early development. Features may change or break as we continue to improve the integration.
## Features
* 🔍 **Search** - Find relevant cards using natural language
* 📊 **Metrics tracking** - Update, track, and analyze import KPIs and outcomes
* 💬 **Feedback & interviews** - Send interviews and feedback to your Vistaly workspace
* 📚 **Documentation access** - Browse comprehensive Vistaly documentation, API references, and best practices
* 🔐 **Secure authentication** - Uses your Vistaly API key
* 🏢 **Organization info** - Access workspace and user details
## Quick Start
### 1. Get Your API Key
First, you'll need to create an API key in your Vistaly workspace:
1. Log into your Vistaly workspace at [https://app.vistaly.com](https://app.vistaly.com)
2. Go to `Settings` –> `API Keys`
3. Generate a new API key
*NOTE: After you create an API Key, be sure to store it somewhere secure. You will not be able to access your secret key again, but you can always recreate an API Key at any time.*
### 2. Configure Your AI Assistant
You can connect to Vistaly through various AI assistants:
1. Open Claude Desktop
2. Go to **Settings**
3. Click on **Connectors** in the sidebar
4. Click **Add custom connector**
5. Enter a name: **Vistaly**
6. Set the **Remote MCP server URL** to: `https://vst_YOUR_API_KEY@api.vistaly.com/mcp`
* ⚠️ Replace `vst_YOUR_API_KEY` with your actual Vistaly API key
7. Click **Add**
Create an `.mcp.json` file in your project root with the following configuration:
```json theme={null}
{
"mcpServers": {
"vistaly": {
"headers": {
"Authorization": "Bearer ${VISTALY_API_KEY}",
"Content-Type": "application/json"
},
"type": "http",
"url": "https://api.vistaly.com/mcp"
}
}
}
```
Then set your API key as an environment variable:
```bash theme={null}
export VISTALY_API_KEY="your-vistaly-api-key"
```
Claude Code will automatically load the `.mcp.json` configuration when you open your project. Make sure the environment variable is set before starting Claude Code.
### 3. Restart Your AI Assistant
After saving the configuration, restart your AI assistant (Claude Desktop or Claude Code) to load the new MCP server.
Your Vistaly MCP server will automatically update to the latest version when you open your LLM client. Close and reopen your client if you suspect you're missing new Vistaly MCP capabilities.
## Example Prompts for Product Managers
Once connected, you can use these practical prompts to streamline your product management workflow:
### 🔍 **Card Discovery & Research**
> *What open opportunities are we tracking in Vistaly related to user onboarding?*
> *Find all opportunities that have 'Now' or 'Next' statuses and list out all of the solutions we are exploring or building for those opportunities.*
### 📊 **Metrics & Performance Tracking**
> *Update the conversion rate KPI card to 5.8%*
### 💬 **User Research & Feedback**
> *Add the notes from this discovery call as an interview in Vistaly*
> *Take the feedback shared in this sales call and add it to Vistaly*
### 📚 **Learning & Documentation**
> *How should I think about structuring my Vistaly workspace?*
* Quick access to technical resources
* Get clear definitions of key concepts
* Perfect for when you need to understand integration options
* Great for onboarding new team members or refreshing your knowledge
## Available MCP Tools
The Vistaly MCP server provides access to these core capabilities:
* **Card Search**: Semantic search across your product tree
* **Card Details**: Get comprehensive card information
* **Comments**: Access team discussions and decisions
* **Metrics**: Submit and track KPI data points
* **Feedback**: Capture user insights and research data
* **Interviews**: Log customer research findings
* **Documentation**: Access Vistaly guides and best practices
* **Health Check**: Verify API connectivity
## Troubleshooting
### "API key required" errors
* Double-check your API key is correctly set in the Claude Desktop configuration
* Make sure you've restarted Claude Desktop after updating the config
* Verify your API key is active in your Vistaly settings
### Server connection issues
* Ensure your Claude Desktop configuration file syntax is valid JSON
* Check that the file path is correct for your operating system
* Try restarting Claude Desktop completely
* Verify Node.js 18 or higher is installed on your system
### Authentication errors
* Verify your API key is valid and hasn't expired
* Check that the API key has necessary permissions in Vistaly
* Ensure there are no extra spaces or characters in your API key
## Support
Need help? Check out:
* 🔌 **MCP Documentation**: [modelcontextprotocol.io](https://modelcontextprotocol.io/)
* 🛠 **API Reference**: [Available here](/api-reference/introduction)
* 📧 **Support**: [support@vistaly.com](mailto:support@vistaly.com)
## Related Integrations
Looking for other ways to integrate with Vistaly?
* [**Vistaly API**](/documentation/integrations/vistaly-api) - Direct API integration for custom workflows
* [**Zapier**](/documentation/integrations/zapier) - No-code automation with hundreds of tools
* [**Slack**](/documentation/integrations/slack) - Team notifications and updates
# Slack Integration
Source: https://docs.vistaly.com/documentation/integrations/slack
Using Slack and Vistaly together
## Installing Slack
To install the Vistaly app for Slack, visit the integrations page and select the 'Add to Slack' button.
After selecting the 'Add to Slack' button, you will be redirected and asked to give Vistaly access to post and receive messages to and from Slack.
After granting Vistaly permission to your Slack organization, you will receive a welcome message from Vistaly.
## Linking Accounts
The last step is to link your Slack account to Vistaly so we can send messages to you in a private channel. Send the message .
Select 'Link Accounts'
Once you Authorize, you'll be ready to use the Vistaly app for Slack!
## Adding Feedback from Slack
The primary use case for the Slack integration is for adding Feedback directly from Slack.
Many of our customers have channels that customer-facing teams use to relay feedback from customers and prospects.
The Slack integration makes it easy to quickly add Slack messages directly to Vistaly as Feedback.
You can also use the command to quickly add a Feedback from Slack.
## Adding an Unmapped Card
You can directly add an [Unmapped Card](/documentation/core-concepts/unmapped-cards) from Slack. Simply type and add a new card.
Once you return to Vistaly, the card will be waiting with the other Unmapped Cards, ready to be mapped into the workspace.
# Vistaly API
Source: https://docs.vistaly.com/documentation/integrations/vistaly-api
Integrate your workflows directly with Vistaly
Use Vistaly's API to automatically add customer feedback that lands in other tools to Vistaly and keep your KPI/Outcome(or Key Result) cards in-sync with your BI and Product Analytics tools.
### Use With Workflow Automation Tools
Use the [Zapier Integration](https://zapier.com/apps/vistaly/integrations) to make it even easier to automate feedback consolidation and metrics updates. [Get in touch](mailto:support@vistaly.com) if there are other automation tools your team is using.
## Developer Documentation
You can find the [API documentation here](/api-reference/introduction), which detail the available endpoints and how to properly form API calls.
## Setting Up Your First API Key
Account owners and editors can create and manage one or more API Keys for your integrations.
Visit to add your first API Key.
*NOTE: After you create an API Key, be sure to store it somewhere secure. You will not be able to access your secret key again, but you can always recreate an API Key at any time.*
## Update the Value of Metric Cards
Automate business metrics, important product analytics, and team-level outcomes (OKRs) updates so your workspace is always up-to-date.
### Tool-specific docs for updating metrics
* Update a metric when the value updates in [**Google Sheets**](/documentation/integrations/google-sheets)
* Update a metric from one of your BI/Product Analytics tools every week [**with Zapier**](/documentation/integrations/zapier)
## Customer Feedback
Automatically add customer feedback that lands in other tools to Vistaly via the [API](/api-reference/introduction).
Popular use cases include adding feedback collected via spreadsheet tools like Airtable and Google Sheets or form builder tools like Typeform and Formstack.
An easy way to get feedback that land in those tools into Vistaly is with the [Zapier integration](https://zapier.com/apps/vistaly/integrations).
# Zapier
Source: https://docs.vistaly.com/documentation/integrations/zapier
Leverage Zapier to automate analytics
Use the Zapier integration to get data into Vistaly from:
* **BI tools** like Looker, Tableau, Google Data Studio, etc.
* **Product Analytics tools** like Mixpanel, Amplitude, Pendo, Posthog, etc.
## Step 1 - Schedule the Zap to run automatically
You'll want to configure this Zap to run automatically at a cadence that makes sense for you. We recommend updating metric card values every week on Sunday night but feel free to update them daily if you'd prefer.
## Step 2 - Request the data from your analytics tool
The next step is to request the data you're looking for it's data source.
Every tool is different, but most of them have an API that allows you to query the data you're looking for.
### Tips for making API calls to various analytics tools
#### Posthog
First you need to get the actual ID of the Insight you want the data for. Use a tool like [Postman](https://www.postman.com/) to hit the [endpoint that gets all of your saved Insights](https://posthog.com/docs/zapier/insights#get-api-projects-project_id-insights). Look through the response for the ID of the Insight you want because the thing that looks like the ID in the URL when you're viewing the Insight doesn't work with the API.
#### Mixpanel
Go to [Mixpanel's Insights API Doc](https://developer.mixpanel.com/reference/insights-query) and fill in the and to get the correct URL to hit. On the right side of that page, fill in your Mixpanel and and it will give you the value you'll need to add as a header to the request.
#### Amplitude
Start by grabbing your [project's API key and Secret Key](https://amplitude.com/docs/apis/authentication).
[Go here](https://amplitude.com/docs/apis/analytics/dashboard-rest#get-results-from-an-existing-chart) to determine the URL for the Amplitude endpoint you'll want to hit.
Amplitude requires you to set a header with the name . The value for header should be your API Key and Secret Key (**in this format: api\_key:secret\_key**) encoded in Base64. [Here's a tool](https://www.base64encode.org/) for Base64 encoding your Api Key and Secret Key.
#### Looker
First get the [underlying Query from a saved Look](https://cloud.google.com/looker/docs/reference/looker-api/latest/methods/Look/look) and then make a request to [run that Query](https://cloud.google.com/looker/docs/reference/looker-api/latest/methods/Query/run_query).
## Step 3 - Transform the data if necessary
Every tool returns data a bit differently. Some will automatically group the data by day or week or month, some will return raw event-level data that needs to be aggregated, and others may apply filters or transformations before returning results. You may need to reshape the data, adjust time granularity, or extract specific metrics before posting to Vistaly.
Zapier has a "Code" Zap with an AI assist that will allow you to pass in the data from your API request and then help you write the code to get it into the state you're looking for.
## Step 4 - Update the metric card in Vistaly
The last step is to use Vistaly's Zapier integration to update your metric card.
To do so, you'll need to link your Vistaly account with your [API Key](/documentation/integrations/vistaly-api#setting-up-your-first-api-key).
With your Vistaly account linked, you'll need to get the ID of the metric card you want to update. You can find this by clicking on the metric card in Vistaly and grabbing the `cardId` out of the URL.
Use the data from the previous step as the value.
**You probably want to leave the "timestamp" field blank**, which will automatically default to the time we receive the API call.
# CSV Feedback Import
Source: https://docs.vistaly.com/documentation/migration-support/insights-importer
Bulk import your feedback
## Import your existing Feedback repositories
If you have an existing place where all of your customer Feedback is collected, you have a few options for importing or migrating Feedback to Vistaly.
### CSV Import
To import via CSV, head to the Inbox and click the 3-dots menu.
Download the sample CSV file to see the format needed to properly import your data. Here's everything you need to know about the uploader fields:
* * the actual thing that was said that you would like to capture
* * the date that the Feedback was given
* * if the Feedback originated from a customer support tool, include the link here
* * the email address of the person who gave the Feedback
* * the first name of the person who shared the Feedback
* * the last name of the person who shared the Feedback
* * the name of the company the Feedback sharer works for
* * if you add a website to Feedback organizations, we'll auto-group future Feedback givers with a matching email domain to that organization
If you have any existing [Persons or Organizations](/documentation/views/insights#persons-and-organizations), we'll try to automatically associate imported Feedback with them.
#### Not all fields are required!
If you don't have all of the data supported by the uploader, that's fine. Upload what you have, and the uploader will walk you through any errors it encounters with your data.
# Productboard Feedback
Source: https://docs.vistaly.com/documentation/migration-support/productboard
This guide will walk you through the process of migrating customer feedback from Productboard into Vistaly.
If your team has been adding insights to ProductBoard from Slack, ensure you follow steps 1-4 if you'd like to include messages collected from Slack as part of your migration. Otherwise, skip to step 5.
## Step 1: Create a Slack App
1. Go to [api.slack.com/apps](https://api.slack.com/apps)
2. Click the "Create New App" button
3. Choose "From scratch"
4. Name your app (e.g., "Vistaly Migration App") and select your workspace
5. Click "Create App"
## Step 2: Configure User-Level Permissions
1. In the left sidebar, click on "OAuth & Permissions"
2. Scroll down to the "Scopes" section
3. Under "User Token Scopes" (not Bot Token Scopes), add the following permissions:
* (to read messages from public channels)
* (to read messages from private channels)
* (to get channel information)
* (to get private channel information)
* (to get user information)
* (to match users by email)
## Step 3: Install the App to Your Workspace
1. Scroll up to the top of the "OAuth & Permissions" page
2. Click "Install to **Your Workspace Name**"
3. Review the permissions and click "Allow"
4. After installation, you'll see a "User OAuth Token" that starts with
5. Copy this token and store it securely - this is what you'll need for the migration
## Step 4: Channel Access
With a user token, access permissions work differently:
### Public Channels:
* The app can access the complete history of all public channels without being added to them
* This simplifies the migration process as no manual channel joining is required
### Private Channels:
* The app will have access to private channels that the authorizing user has access to
* Private channels the authorizing user is not a member of will not be accessible
* Vistaly's data migration tool will include a link to any instances it is unable to read so users can view those messages if they have access
## Step 5: Export ProductBoard Feedback
If you use ProductBoard, you'll need to export your feedback data:
1. Use ProductBoard's [export functionality](https://support.productboard.com/hc/en-us/articles/360056354854-Exporting-your-notes-into-a-CSV) to download your Notes
2. Save the exported file for the next step
## Step 6: Share Required Files with Vistaly
Share the following with us using a secure method:
1. Your Slack user token (starts with xoxp- or xoxb-) *if using Slack*
2. Your ProductBoard feedback export file
## Step 7: Upload Vistaly Feedback
The Vistaly team will return a CSV file that you can use to upload your feedback using the [bulk feedback import](/documentation/migration-support/insights-importer) feature.
## Important Security Notes
* The user token provides access to your Slack workspace data. Only share it through secure channels.
* User tokens have broader permissions than bot tokens and should be handled with extra care
* User tokens will expire if the authorizing user changes their password
* After migration is complete, you can revoke the token by:
1. Going to [api.slack.com/apps](https://api.slack.com/apps)
2. Selecting your migration app
3. Going to "OAuth & Permissions"
4. Clicking "Regenerate" or completely uninstalling the app
## Data Migration Limitations
Please be aware of these limitations:
1. **Private Channels**: The app can only access private channels that the authorizing user is a member of
2. **Direct Messages**: The app cannot access direct messages (DMs) or multi-person direct messages (MPDMs)
3. **File Access**: While the app can see file metadata, downloading files may require additional permissions
4. **Rate Limits**: Slack API has rate limits that may affect migration speed for very large workspaces
5. **Token Expiration**: User tokens expire if the authorizing user changes their password
## Need Help?
If you encounter any issues during setup, please reach out to our support team at [support@vistaly.com](mailto:support@vistaly.com).
# Insights
Source: https://docs.vistaly.com/documentation/views/insights
Embed the voice of the customer directly in your Opportunity Solution Tree
Vistaly helps product teams understand their customers' biggest problems and pain points by aggregating learnings across discovery interviews, sales calls, customer success touchpoints, and user submitted feedback.
Insights enter Vistaly from two primary sources:
* **Interviews**: Long-form conversations with customers/users/prospects to understand their problems and uncover [Opportunities](/guides/getting-started/the-discovery-space).
* **Product Feedback**: Smaller problems, pain-points, and feature requests pushed from sales/support/customer success teams, or directly from customers.
### Insights are the evidence that support Opportunities
If you've used something like Miro or Figjam to create opportunity solution trees, you're probably felt the pain of having the first-party evidence for your opportunities live in a different tool.
When insights are attached to cards in the workspace, the insights count displays on each card. Selecting the insights icon will open the insights tab and display all attached insights from customer interviews and feedback.
### Insights Rollups
It can be extremely usefull to have a roll up view of insights, so you can get a broader picture of exactly what you’re hearing from customers within any branch of your workspace.
Select any card, and view the insights tab. Directly attached insights will show at the top, and “Nested” insights will show below, along with the cards those insights are attached to.
### Navigating to the Insights Repository
You can navigate to the Insights repository page by selecting the Insights link in the top navbar.
Once on the interviews page, you can see a list of recent and historical customer interviews and feedback.
## Interviews
Interviews are for capturing learnings from discovery interviews, sales calls, customer success touchpoints, and usability testing sessions.
When you create an Interview, there are a handful of fields to be aware of:
* **Interviewers**: the people on your team conducting the Interview. To participate in interviews, colleagues will need to have [Editor Access](/core-concepts/inviting-team-members#permissions-for-admins%2C-editors%2C-and-viewers) to your Vistaly account.
* **Participants**: the people you are interviewing and the company they belong to.
* **Interview date**: interviews are sorted by date by default on the “Interviews Page”.
* **Video recording**: upload a recording of your call, and the AI Discovery Copilot (more below) will help you capture the learnings from the call.
* **Transcript** (optional): if you'd prefer to supply a transcript of the call instead of a video recording, you can do so by manually entering one on the transcript tab.
* **Notepad**: a collaborative text editor for taking notes during the call
### The AI Discovery Copilot
Upload a recording or paste the transcript of your call, and the AI Discovery Copilot will:
* Write a quick summary of what was discussed during the call
* Identify problems, pain-points, and unmet needs (a.k.a. opportunities) raised by the customer
* Find cards in your opportunity solution tree that are related to the opportunities raised by the customer
### Creating Insights with the AI Discovery Copilot
**By Uploading a Recording**
When you upload a recording or paste the transcript of your call, the AI Discovery Copilot will automatically create insights for the opportunities raised by the customer.
**When Supplying the Transcript**
If you paste in the transcript of your call, a button will appear above the transcript to run the AI Discovery Copilot on the transcript.
**Via MCP**
You can create interviews via the [MCP](/documentation/integrations/model-context-protocol) that have the transcript already populated. When an interview is created via MCP with a transcript, the AI Discovery Copilot will run auomatically.
Be sure to specify the interviewers and interviewees of the call so the AI has enough context to properly identify the opportunities raised by the customer.
### Creating Insights Manually
**From Transcripts Generated by Uploaded Recordings**
If you'd like to manually create an insight from the call transcript, you can do so by clicking the + button next to part of the transcript that you'd like to create an insight for.
**From Transcripts You've Pasted In**
If you've pasted in the transcript of your call, you can create an insight by highlight the portion of the transcript that you'd like to create an insight for and clicking "Add Insight".
**Manually Add Insights from the Notepad**
To create insights from the notepad, highlight the portion of your notes and select “Add Insight”.
If you have more than one interviewer on a call, the notepad has a built-in multiplayer experience for taking shared notes during the same Interview with your colleagues.
It's a great practice to take your own notes during the call, and discussing what opportunities you heard with the other interviewers. Don't just rely on AI to capture everything.
### Attaching Interview Insights to Cards
While Vistaly supports attaching insights to any [Card Type](/documentation/core-concepts/card-types), most of the time they will be associated with [Opportunity Cards](/documentation/core-concepts/card-types#opportunity-card).
Here are the differences between insights and opportunities:
* **Opportunities**: the “synthesized” version of a customer pain points, needs, or desires.
* **Insights**: the individual instances of customers expressing pain points, needs, or desires. The underlying evidence supporting opportunities.
**Opportunities can contain multiple insights, while insights are single instances of customers expressing pain points, needs, or desires.**
After insights are added, there a few ways to assoicate them with opportunities in the tree.
#### AI Suggested Matches
If you approve a suggested insight found by the AI Discovery Copilot, it will look through your workspaces for cards that are related to the insight.
#### Search to Add
If the Suggested Matches don't look right, or you're manually adding an insight, you can search for the card you're looking for. Search supports filtering by card type and workspace.
#### Find in Tree
Find in tree is great when you're unsure where the insight fits or if you need to add a new opportunity before attaching the insight.
## Customer Feedback
Sales, support, and customer success teams are constantly talking to customers. And customers are constantly engaging with your product. Having a way to proactively funnel that feedback to Product teams is a great way to keep your finger on the customers pulse and identify customers to reach out to for interviews.
### Feedback Inbox
When someone from a the sales/support/customer success team adds Feedback, it lands in the Inbox.
While only Editors can interact with customer interview workflows, **anyone with Vistaly view access can submit feedback.** Once feedback is shared, only editors can attach it to cards in the workspace view.
### Getting to "Inbox 0"
When you create an Insight from Feedback and attach it to a card, the Feedback is automatically marked processed.
If you get a piece of Feedback submitted that isn’t particularly relevant, you can remove it by marking it as processed.
### Import Feedback Via CSV
If you have existing customer Feedback, you can use the CSV importer to migrate Feedback into Vistaly.
To import via CSV, head to the Inbox and click the 3-dots menu.
Download the sample CSV file to see the format needed to properly import your data. Here’s everything you need to know about the uploader fields:
* `feedback_body`: the actual thing that was said that you would like to capture
* `feedback_captured_date`: the date that the Feedback was given
* `feedback_url`: if the Feedback originated from a customer support tool, include the link here
* `feedback_sharer_email`: the email address of the person who gave the Feedback
* `feedback_sharer_first_name`: the first name of the person who shared the Feedback
* `feedback_sharer_last_name`: the last name of the person who shared the Feedback
* `feedback_sharer_organization_name`: the name of the company the Feedback sharer works for
* `feedback_sharer_organization_website`: if you add a website to Feedback organizations, we’ll auto-group future Feedback givers with a matching email domain to that organization
If you have any existing [Persons and Organizations](#persons-and-organizations) records in Vistaly, we’ll try to automatically associate imported Feedback with them.
**Not all fields are required!**
If you don’t have all of the data supported by the uploader, that’s fine. Upload what you have, and the uploader will walk you through any errors it encounters with your data.
We have a [ProductBoard notes importer](/documentation/migration-support/productboard) that can be used to migrate your existing ProductBoard notes into Vistaly. If you're using another tool, please reach out to us and we can help you migrate your data.
### Make It Easy For GTM Teams To Share Product Feedback
Getting GTM teams to log into Vistaly each time they want to pass along Feedback can be challenging.
Vistaly has a few helpful integrations with third-party tools that make this easier.
#### Add From Slack
Once you’ve added the [Slack Integration](/documentation/integrations/slack) to your Slack instance, there are two ways to add Feedback from Slack.
##### Add Feedback using the slash command (`/vistaly`)
To add Feedback using the slack command, type `/vistaly` feedback and send the message. This will open the form for adding a new Feedback.
##### Add Feedback using the Slack message menu
Select the three-dot menu next to the message you’d like to convert into a Feedback. Creating a Feedback using this method will automatically populate the Feedback with the body of the Slack message.
Both methods of creating Feedback will open the Feedback form.
#### Feedback Browser Extension
After installing the [Browser Extension](/documentation/integrations/browser-extension), select the Vistaly extension icon to add Feedback.
#### Forward Feedback From Other Tools To Vistaly
If your team is currently using something like Google Forms, Airtable, Typeform, etc. to collect feedback and you're not quite ready to move away from that, Vistaly has a [Zapier integration](/documentation/integrations/zapier) that allows you to forward Feedback from other tools to Vistaly.
## Persons and Organizations
When you create interviews or receive feedback, Vistaly keeps track of who said what and which company they work for.
#### Automatic Grouping by Company
When you add someone to an interview or feedback (e.g. [steve@snowflake.com](mailto:steve@snowflake.com)), Vistaly lets you associate them with their organization (Snowflake). If you add the organization's website (snowflake.com), Vistaly will automatically group anyone with a matching email address to that same organization.
This means if you interview Steve from Snowflake today, and next week a salesperson shares feedback from Melissa at Snowflake, both will automatically be linked to the Snowflake organization.
#### See Everything from One Customer
You can view a Person's page or Organization's page to see all interviews and feedback from a single Person or everyone at that Organization in one place. This makes it easy to understand what different people from the same Organization are saying across all your conversations with them.
#### Disabling Organizations for B2C Companies
If you’re a B2C company and it doesn’t make sense to group people by their company, you can turn Organizations off in Advanced Settings.
# Reports
Source: https://docs.vistaly.com/documentation/views/reports
Reports in Vistaly provide a streamlined view of your work’s impact without overwhelming detail. They allow you to showcase key metrics and outcomes in an easily shareable format.
## Creating Reports
Vistaly's outcome-oriented reports support creating executive or team-level reports for showing progess. Add [KPI](/documentation/core-concepts/card-types/kpi) and [Outcome](/documentation/core-concepts/card-types/outcome) cards from any workspace and see how shipped product improvements influence the metrics and goals that matter.
### Adding a New Report
1. Click the **Add new report** button
2. Enter a name for your report
**Report Levels:**
* **Team-level reports:** Focus on individual trios or squads
* **Company-level reports:** Track progress across multiple trios or squads
### Working with KPIs (Perisistant)
The top section of your report displays metrics. These can be (but are not limited to):
* Business-level "board metrics" for company reports
* Key engagement metrics for team-level reports
To add metrics:
1. Click **Adjust KPIs**
2. Select one or more metrics from any workspace
**Important Features:**
* Reports exist across all workspaces, allowing you to combine KPIs from different areas of the business
* Use the sort feature to customize the order of displayed KPIs
### Working with Outcomes (Time-bound)
The bottom section of your report showcases outcomes:
1. Click **Adjust Outcomes**
2. Select one or more outcomes from any workspace
After adding an outcome, the report automatically:
* Displays related opportunities and solutions
* Groups items by Now, Next, Later, and Done categories
* Shows solution completion points on the timeline with pins
This visualization helps you identify correlations between actions taken and their impact.
## Customization and Editing
**Timeline Planning:**
* Set future end dates for solutions to display projected completion points
**Inline Editing:**
* Hover over any value to make quick changes directly in the report view
* Dates, values, and units can all be modified inline
This feature allows for efficient report management without navigating to other views.
## Sync With Your BI/Product Analytics Tools
The outcome section of the reports page is designed to show teams how their work is impacting outcomes. It's helpful if you have consistent snapshots of your data to see how outcomes change over time.
To help you create that consistent snapshot, use the [Vistaly API](/documentation/integrations/vistaly-api) to sync Oucome and KPI cards with your BI and analytics tools to pull updates on a regular basis *(weekly typically gets the job done)*.
## Low Data Environments
Reports can still be useful for communicating an outcome-oriented roadmap if you are working in a low data environment. See [these tips](/guides/getting-started/the-strategy-space#working-with-unmeasurable-goals) if you're operating in a low data environment.
# Roadmap
Source: https://docs.vistaly.com/documentation/views/roadmap
Now / Next / Later view of commitments
Vistaly’s roadmap provides a high-level view of Solutions and Opportunities that the Product team has committed to.
This roadmap view is NOT a project release plan with release dates. It’s a high-level overview of larger commitments for strategic discussions and decisions.
## Integration with Delivery Tools
The roadmap view becomes even more powerful when combined with Vistaly's [Jira](/documentation/integrations/jira) and [Linear](/documentation/integrations/linear) integrations. When you link delivery issues and projects to your roadmap cards, you can see:
* **Progress tracking**: Linear project completion percentages and Jira issue status display directly on card faces
* **Strategy + execution**: View strategic direction alongside real delivery progress in one unified view
* **Team alignment**: Engineering teams can see strategic context while product leaders track execution
This unified view helps customers get excited about seeing the full picture - both the strategic "why" and the delivery "how" - all in one place.
## Card & Column Statuses
The Roadmap view groups Solutions and Opportunities into columns based on their status.
You can think of statuses in three stages:
1. **Starting Statuses**: Upon creation, Opportunities start with a status of Identified, and Solutions start with a status of Idea
2. **Active Statuses**: As Opportunities and Solutions get committed tob, they move through the status of Later, then Next, then Now
3. **End Statuses**: Solutions get marked Done once they’ve been shipped and Opportunities get marked Addressed when the problem no longer exists for users. If you explicitly decide not to address an Opportunity or build a specific Solution, mark it as Not Now
## Roadmap Time Horizons
Active statuses are used to show the Opportunities you have committed to addressing and the Solutions your team is actively building.
Now, Next, and Later are used to communicate commitment level, clarity around the problem/solution, and time horizon.
The “further” out an Opportunity or Solution is, the less certainty surrounds when, how, and even if it will be addressed or shipped. The closer they get to Now, the more certainty exists.
### Later
Work starts as big, over-arching Opportunities (customer problems, pain points, desires) in the Later column once you’ve committed to addressing them.
The time horizon for these is generally far in the future (quarters, halves, or years depending on the business). There is a possibility that some of these Opportunities might be deprioritized in favor of addressing more pressing customer problems (and set back to Identified).
### Next
The Next column is for smaller “sub-opportunities” you’re doing discovery on and Solutions you haven’t quite started development on yet — maybe because your team is still testing designs with users or there just isn’t a dev team available to start work on it yet.
You have a good grasp on the problem you’re trying to solve, even if you don’t have a 100% clear idea of how you’re going to solve it.
You should have enough certainty around these Opportunities/Solutions that the majority of them (85%+) ultimately get shipped/addressed.
### Now
The Now column is for Solutions that are actively being developed. The Now status indicates that there is a high level of certainty around the problem being solved and the Solution your team is building to address it.
In the Now column, it becomes more feasible and realistic to start communicating delivery expectations.
## Focus on “Child” Cards
When a parent Opportunity has a sub-Opportunity or child Solution with an active status (Now, Next, Later), we only show the furthest down active child. This helps reduce the amount of clutter on the roadmap.
\#\*\* Status updates “propagate” up to parent Opportunities
When an Opportunity contains a sub-Opportunity or a child Solution with a status of Now, Next, or Later, the status of the parent Opportunity is automatically updated to match the status of the sub-Opportunity or child Solution.
If an Opportunity has multiple children with “Active” statuses, the parent will have the status of the furthest along child.
## Navigating the Roadmap
### Sorting Items
You can drag and drop items to move them to different columns as well as sort them within a given column.
Sorting items between columns is a way to more clearly communicate exactly what you’re focused on.
### Showing the "Full Story"
Trying to figure out why a solution matters? The Story section of each card expands to show why any solution fits into the bigger picture. Select More to view more context.
### Filtering the Roadmap
The filters at the top of the roadmap views will take the current selection and filter it further by assignees and labels. The results must match all selected filters to display.
### Scoping the Roadmap
The menu on the left-hand side of the roadmap view will allow you to navigate the workspace data and scope the roadmap to any selected card – answering questions like: “What work is being done to support this outcome?”
Select the bubble icon to scope the roadmap to a specific card.
### Add Unmapped Cards
The ”+” icons in the column headers let you quickly add an Unmapped Card to your Roadmap.
This can be helpful if you’re in a meeting and just need to quickly add something that you can properly add to the tree at a later time.
# Settings
Source: https://docs.vistaly.com/documentation/views/settings
Configure your organization, team, and workspace settings.
## Card Settings
Customize how card types appear and function in your organization.
### Card Type Names
Rename card types to match your organization's terminology (e.g., rename "Opportunity" to "Initiative").
### Enabled Card Types
Control which card types are available in your organization. Disable card types that your team doesn't use.
### Custom Fields
Add custom fields to card types to capture additional information specific to your workflow.
Learn more about [custom fields](/documentation/core-concepts/custom-fields).
## Team
Manage your team members and their permissions.
### Inviting Team Members
Add new members to your organization with different permission levels:
* **Owner**: Full access to all settings and features
* **Editor**: Can create and edit cards, manage insights
* **Viewer**: Read-only access to cards and insights
### Managing Roles
Change team member roles or remove members from your organization.
Learn more about [inviting team members](/documentation/core-concepts/inviting-team-members).
## Workspaces
Organize your work into separate workspaces for different products, teams, or initiatives.
### Creating Workspaces
Create new workspaces to separate different areas of your strategy and discovery work.
Learn more about [workspaces](/documentation/core-concepts/workspaces).
## Labels
Create and manage labels to categorize and filter cards across your organization.
### Creating Labels
Add custom labels with colors to help organize and filter your cards.
### Label Management
Edit or delete existing labels. Note that deleting a label removes it from all cards.
Learn more about [labels](/documentation/core-concepts/labels).
## Templates
Create and manage templates for AI-powered document drafting.
### Creating Templates
Design reusable templates to structure AI-generated documentation for your cards. Templates include sections with instructions that guide the AI to create comprehensive, consistent documents.
### Managing Templates
Edit template details, add or reorder sections, and publish templates when ready. Published templates appear in the AI drafting workflow for all organization members.
### Publishing Templates
Templates must be published before they're available for document drafting. Draft templates are only visible in template management.
Learn more about [template management](/documentation/ai-document-drafting/template-management) and [AI document drafting](/documentation/ai-document-drafting/overview).
## Integrations
Connect Vistaly with other tools in your workflow.
### Available Integrations
* **Jira**: Sync cards with Jira issues
* **Linear**: Connect cards to Linear issues
* **Slack**: Receive notifications in Slack
* **Zapier**: Automate workflows with Zapier
* **Google Sheets**: Export data to Google Sheets
* **Browser Extension**: Capture insights from anywhere
Learn more about [integrations](/documentation/integrations/vistaly-api).
## API Keys
Generate and manage API keys for programmatic access to Vistaly.
### Creating API Keys
Generate API keys to integrate Vistaly with custom tools or scripts. API keys provide secure, authenticated access to your organization's data.
### Key Management
View, revoke, or regenerate API keys as needed. Each key shows when it was created and last used.
Learn more about the [Vistaly API](/documentation/integrations/vistaly-api).
## Plans & Billing
Manage your subscription plan and billing information.
### Plan Details
View your current plan, usage, and available features.
### Billing Management
Update payment methods and view billing history.
## Advanced
Configure advanced organization settings.
### Organization Details
Update your organization's name, logo, and description.
### Company Description
The company description field provides important context about your business that AI uses to deliver more relevant and accurate results throughout Vistaly.
**How AI uses your company description:**
* **Documentation generation**: When using AI to draft PRDs, solution briefs, and other templates, your company description helps the AI understand your business domain, industry, and product focus to generate more relevant content
* **Interview insight accuracy**: AI uses your company context to better understand and extract insights from customer interviews
* **Cross-interview insight mapping**: Your company description helps AI identify patterns and connections across multiple customer interviews
**What to include:**
Provide a clear description of your company that covers:
* Your industry and market
* Your product focus and core offerings
* Your target customers or user base
* Your company's mission or value proposition
**Example:**
> Acme Inc. is a B2B SaaS company building project management software for distributed engineering teams. We focus on helping remote teams coordinate complex software projects with real-time collaboration tools and automated workflows.
The more specific your company description, the better AI can tailor its outputs to your business context.
### Customer Organizations
Enable customer organization tracking to organize insights by customer company (B2B use case).
### Outcome Polling
Configure settings for automated outcome metric collection.
## Accessing Settings
To access your organization settings:
1. Click on your profile icon in the top navigation
2. Select **Settings**
3. Choose the appropriate settings tab from the sidebar
Some settings tabs are only accessible to organization owners or editors. Viewers have read-only access to most settings.
# Test Tracker
Source: https://docs.vistaly.com/documentation/views/test-tracker
[Assumption testing](https://www.producttalk.org/2023/10/assumption-testing/\&utm_source=vistaly) is a great method for reducing the risk associated with every solution.
The *Test Tracker* view makes it easy to follow along with the status of tests.
# Tree
Source: https://docs.vistaly.com/documentation/views/tree
The Tree View unites the [Strategy Space](/guides/getting-started/the-strategy-space) and the [Discovery Space](/guides/getting-started/the-discovery-space), and drives everything that happens in Vistaly.
Vistaly's tree editor connects your [Strategy Space](/guides/getting-started/the-strategy-space) and [Discovery Space](/guides/getting-started/the-discovery-space).
It's flexible like a mind-mapping tool, but adds the structure that product teams need to unify strategy, business metrics, and goals with the discovery process.
## Building the tree
### Adding cards to the tree
Cards are added to the tree using the add card actions found in the lower right corner, below each card.
**There are rules in place to prevent some cards from being added as children to others.**
As an example, it doesn’t make sense to start with an experiment before you have a solution to experiment on. It also doesn’t make sense to start with a solution before you know which problems you want to solve.
These rules are not meant to get in the way, they are there to:
* Support automated status changes.
* Keep the tree, roadmap, and reporting views consistent and in sync.
* Enforce a sane and easy to follow structure.
### Moving cards around the tree
One of the great things about Vistaly is its ability to relocate entire portions of a tree while automatically realigning the tree without manually dragging a bunch of boxes around.
There are two ways to relocate cards (and branches) in the tree view.
* Hovering over the move action in the upper left corner of a card.
* Using the move card action in the card sub-menu.
### "Mirroring" cards in the tree
Sometimes, you may want to have a card appear in multiple places in the tree. For example, you might be tracking a customer problem that, if addressed, could improve multiple product usage metrics. You may want to show that card in the tree under each metric.
This is called "mirroring" and is done by selecting the **Mirror Card** option in the card sub-menu.
### Shifting the tree
Each card in the Tree can be moved up and down *(or left and right)*. This can be helpful when doing quick prioritization or sorting.
***If you’re looking for advanced prioritization capabilities, check out [this section](/documentation/core-concepts/custom-fields) on custom field prioritization.***
## Navigating the tree
### Hide/Show Cards
When a tree starts to get big, it’s helpful to hide portions of it while you’re working or presenting to others.
Hide and show cards by hovering over any card and selecting the hide/show icons to the left or right of the card *(or top and bottom depending on orientation)*.
Selecting **Hide Card** hides that card and all its children and descendants.
### Zooming
Use the zoom controls in the bottom left of the Tree to zoom in and out.
Zoom shortcuts:
* macOS: `⌘+scroll`
* Windows: `⊞+scroll`
### Collapsing the tree
Collapse the entire tree and start from the top by selecting the **Collapse All** option in the bottom left of the workspace.
### Focusing the tree
**Focus Mode** cuts down on extra noise by displaying all the cards immediately surrounding the card in focus.
Navigate through the Tree by opening and collapsing different sections. To re-enable Focus Mode, select Focus on card from the card sub-menu.
### Showing the Full Story
Sometimes, you may want to work on a particular path in Vistaly and see how you got there and where it’s going. Story mode removes extra noise in the tree by showing from one card all the way to the top of the tree in a straight line. This allows you to only see what’s relevant to the selected card.
Enter story mode by selecting Show Story in the card sub-menu.
**When in story mode, new cards CANNOT be added as children to cards in the story.** This is prevented to ensure newly added cards are not hidden by default. Exit story mode before working on other parts of the tree.
## Working & Viewing Mode
**Viewing mode** is designed for presenting or exploring the data. Entering Viewing mode removes controls and tightens the spacing between cards.
## Searching
Search looks across insights and cards *(in the tree and unmapped cards)* for matches. A matching indicates the search term is “close enough” to either the title or details of the card or insight. Card title matches rank higher than card details in the results.
Select the button in the side navigation to open search, or use the keyboard shortcut *(shown below)*.
Search shortcuts:
* macOS: `⌘+k`
* Windows: `⊞+k`
# Introduction
Source: https://docs.vistaly.com/guides/getting-started/introduction
Welcome to Vistaly's Knowledge Base – Find everything you need to build a world class operating system for your product organization.
## What is Vistaly?
Vistaly is the operational hub for product teams who want to build the right solutions for the right problems.
Vistaly supports product teams when answering the important questions:
> ***"Are we building this right?"*** - The execution question
>
> ***"Are we building the right thing?"*** - The strategic question
As development cycles accelerate, and time to build decreases, ensuring your teams are solving the right problems becomes more crucial than ever. Vistaly creates alignment between strategy and execution by integrating:
* **Business & Product Strategy** - Your organization's direction and priorities
* **Customer Needs & Challenges** - The problem space you're addressing
* **Solutions & Ideas** - The potential approaches to solving those problems
### What Vistaly IS NOT:
* A standalone goal-setting framework that sits separate from daily work
* Another task management tool
* A static documentation system
Instead, Vistaly is:
* A decision-making system that connects the "why" behind work to the "what" being built.
* A dynamic operational hub where strategy and discovery continuously inform each other.
## The Two Spaces
The [Strategy Space](/guides/getting-started/the-strategy-space) and [Discovery Space](/guides/getting-started/the-discovery-space) form a continuous feedback loop within Vistaly. Strategy defines the direction and success criteria that guide discovery activities, while insights and learnings from discovery efforts inform and refine the strategy. This bidirectional relationship ensures your product decisions remain aligned with business objectives while adapting to customer needs and changes in the market.
The [Strategy Space](/guides/getting-started/the-strategy-space) translates your 'why' into measurable objectives, while the [Discovery Space](/guides/getting-started/the-discovery-space) helps you determine 'what' to build and 'how' to build it. Together, they create a cohesive system where customer insights drive strategic decisions, and strategy provides the foundation for meaningful discovery.
## Five Core Workflows
Vistaly supports five fundamental workflows that form a continuous cycle of strategy development, discovery, prioritization, execution, and learning.
### 1. Communicating and Aligning on Strategy *(Strategy Space)*
Develop and maintain a living strategy that evolves with changes to the business and market.
Key Activities:
* Articulate a vision that sets guardrails and gives purpose to your product team
* Define metrics that measure business impact and the degree to which customers experience the value your product provides
* Set near-term goals that create focus for teams to rally around
### 2. Continuous Discovery *(Discovery Space)*
Systematically explore customer needs and market opportunities that are aligned with your strategic outcomes.
Key Activities:
* Conduct and document customer interviews
* Capture feedback from prospects and users
* Organize discovered opportunities by outcomes
### 3. Prioritization *(Discovery Space)*
Make informed decisions about where to invest limited resources for maximum impact.
Key Activities:
* Size opportunities using Vistaly's built-in evaluation tools
* Communicate priorities clearly to stakeholders
* Align team efforts around high-value work
### 4. Ideation & Testing *(Discovery Space)*
Generate solution approaches and validate assumptions before committing significant resources.
Key Activities:
* Brainstorm diverse solutions for prioritized opportunities
* Identify critical assumptions underlying proposed solutions
* Design experiments to test assumptions with minimal investment
* Track experiment results and extract learnings
### 5. Communicating Progress *(Strategy Space)*
Maintain alignment by sharing learnings, decisions, and progress towards your near-term goals.
Key Activities:
* Generate automated reports showing progress against near-term goals
* Show the impact of completed work on near-term goals
* Provide visibility into upcoming priorities
## What You'll Explore
Connect business growth to customer value
Find the highest impact problems to solve
How to effectively introduce Vistaly to your team
How to organize teams' work in Vistaly
## Need Help?
If you encounter anything you're unsure about, our support team is ready to assist you.
Email ✉️: [support@vistaly.com](mailto:support@vistaly.com)
# Team Onboarding
Source: https://docs.vistaly.com/guides/getting-started/team-onboarding
Vistaly is designed as a collaborative platform where teams align on strategy, discover opportunities, and track progress. While you can use Vistaly individually, its true power comes form teams collaborating within the platform.
## Why Team Onboarding Matters
Effective onboarding ensures your team:
* Quickly understands how to navigate and contribute within Vistaly
* Experience immediate value through relevant business context
* Establishes a shared language for discussing strategy and discovery
* Builds momentum through visible collaboration
All that to say – **Vistaly is designed for collaboration.**
This means getting your team to quickly understand how to collaborate in Vistaly and having them experience those benefits is critical to getting the most out of it.
## Understanding User Roles
Vistaly offers two primary user types, each with distinct permissions:
| User Type | Capabilities | Best For |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| **Editors** | - Create/delete/reoganize cards in the workspace
- Update roadmap
- Modify metric card values and parameters
- Add interviews
- Add insights
| - Team leads
- Roles interviewing customers
- Directors, GMs, etc.
|
| **Viewers** (Collaborators) | - View workspace content
- Comment on cards
- Create feedback
| - Executives
- Stakeholders
- Team members
|
## Preparing for Team Onboarding
### 1. Build a Foundation with Real Data
You'll see Vistaly's full value when you populate it with your actual business context. Before inviting team members, prepare a minimal but meaningful workspace:
#### **Create a Minimal KPI Tree:**
* Identify 2-3 business metrics relevant to your team's work
* Add these to the top of your workspace
* Include at least two levels above where your team typically works
* Don't worry about perfection—position it as a starting point for discussion
#### **Add One Outcome:**
* Connect one outcome to a leaf KPI
* Choose something familiar to your team's current focus
* If possible, add historic data points to demonstrate impact tracking
#### **Add Opportunities with Insights:**
* Import recent customer feedback or research insights
* Connect these insights to specific opportunities
* Apply rough sizing to opportunities (but toggle this off initially to avoid overwhelming new users)
#### **Add Solutions and Statuses:**
* Create a few solution ideas for high-value opportunities
* Update statuses to either "Now" or "Next" for prioritized items
* Leave some as ideas to demonstrate the full workflow
### Solutions & Statuses
Now add a few solution ideas to one or two high-value opportunities. Then update the statuses to either Now or Next. Keep a few as ideas.
### 2. Create a Now/Next Filter
Filters are flexible, one of the most commonly created filters is the Now/Next Filter. It show which opportunities and solutions are prioritized in the tree view, and removes all the clutter creating a roadmap view that shows "The Story" behind each prioritized solution.
1. Open the filter menu and select "Add Condition"
2. Add the following filter conditions:
1. Solution Status | "Matches one of" | Now & Next
2. Opportunity Status | "Matches one of" | Now & Next
3. Select "Include full hierarchy" to show all ancestor cards
4. Save the filter to make it available to all users
## Running Effective Onboarding Sessions
### Choose the Right Starting Point
The best entry point depends on your audience:
* **For product team members**: Start with the tree view
* **For executives or stakeholders**: Begin with a populated reporting view
### Tree Walkthrough Best Practices
1. **Use View Mode**
* Activate view mode to hide "add" buttons and tighten the tree display
* This creates a cleaner, more scannable presentation
2. **Reveal One Level at a Time**
* Start at the top or the highest relevant level for your audience
* Expand only one level at a time to prevent overwhelming new users
* Allow time for questions at each level
3. **Demonstrate the Now/Next Filter**
* After walking through the full tree, apply the Now/Next filter
* Show how this creates a clean roadmap-like view of priorities
4. **Connect Insights to Opportunities**
* Highlight how customer feedback connects directly to opportunities
* Show the "evidence trail" from insight to solution by selecting an opportunity with insights and opening the insight list.
### Reports Walkthrough Best Practices
#### Build the right report for the right audience
* **For product team members**: Create a report with relevant KPI cards and the teams outcome. These metrics could include engagement metrics or other performance indicators related to the outcome.
* **For executives or stakeholders**: Create a report that showcases business impact. This means including higher-level business KPIs. Depending on the audience, it could be helpful to include all current outcomes.
You can use the [Vistaly API](/documentation/integrations/vistaly-api) to sync your KPI cards your CRM, BI tools, spreadsheets, or wherever else you keep your business metrics. This way your workspace always has live, accurate data.
#### Add historic data
While not always possible, adding histoic data can help make this view more impactful. The goal of the reporting view is to keep stakeholders and teams aware of prioritized work and it's impact on outcomes.
## Getting support
If you'd like support getting a workspace prepared for an internal demo, reach out! We're here to help.
Email us at [support@vistaly.com](mailto:support@vistaly.com)
# The Discovery Space
Source: https://docs.vistaly.com/guides/getting-started/the-discovery-space
The Discovery Space in Vistaly is where product teams explore customer needs, generate solution ideas, and validate assumptions with testing.
Vistaly's discovery space is heavily inspired by Teresa Torres' [Continuous Discovery Habits](https://www.amazon.com/Continuous-Discovery-Habits-Discover-Products/dp/1736633309?utm_source=vistaly). While not a prerequisite for Vistaly, this is a fantastic resource if you're new to product discovery,
Opportunity Cards are at the heart of Vistaly's discovery process. They represent the voice of your customer by capturing their needs, pain points, and desires in a structured format that helps your team prioritize effectively.
## Opportunity Cards
Opportunity Cards document customer problems, needs, or desires worth solving. They are created based on:
* Customer conversations and interviews
* User feedback collection
Whereas product usage metrics in your [Value Exchange Model](/guides/getting-started/the-strategy-space#2-a-value-exchange-model) tell you *what's* happening, Opportunities tell you *why* it's not happening more (or less, or faster, etc.)
### Opportunity Hierarchy
Opportunity Cards in Vistaly are typically child cards of:
* [KPI cards](/guides/getting-started/the-strategy-space#layer-in-the-drivers-of-business-metrics) – *A product metric that would improve if you addressed the Opportunity. This allows you to keep a structured backlog.*
* [Goal cards](/guides/getting-started/the-strategy-space#3-pairing-the-value-exchange-model-with-near-term-focus) – *A time-bound Goal/Outcome/Key Result the team is actively working to achieve.*
* Parent Opportunities – *Larger opportunities that can be broken down into more specific sub-opportunities*
This hierarchical structure allows for transforming complex problems into manageable component, showing a clear relationship between business goals and customer needs. Additionally, the hierarchy provides a structure that makes prioritization more impactful. Instead of priortizing a flat list of features, you move closer to the problems worth solving and prioritize those first.
### Opportunity Space Example
Imagine you're working on a mobile app that delivers content to users. Your app includes a handful of ways for users to find the content they what watch, read, or listen to.
You determine and set your primary outcome to be improving the number of searches that return a successful result.
Then after some customer discovery, you:
* Identified two [top-level opportunities](#top-level-opportunities)
* Broken down one opportunity into multiple sub-opportunities
This breakdown transforms complex problems into manageable opportunity areas that are easier to evaluate and prioritize.
### Sizing Opportunities
Vistaly offers two primary methods to size and prioritize opportunities:
#### Insight Count Method
When adding insights from customer [interviews](/documentation/views/insights#interviews) or [feedback](/documentation/views/insights#feedback), an insight count will display on the face of each card. The insight count can be used as a proxy to frequency, reach, and impact potential.
> **Pro Tip** 💡\*\*:\*\* Insight count will only display when is enabled in card settings
#### Custom Fields Method
For more robust analysis, [custom fields](/documentation/core-concepts/custom-fields) allow you to evaluate opportunities across multiple dimensions.
Default custom fields for Opportunity Cards include:
| **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.
> **Pro Tip 💡**: Find the right balance with custom fields. Too many can slow down your process, while too few might not provide enough context for decision-making.
> **Pro Tip 💡**: [Custom fields](/documentation/core-concepts/custom-fields) will only display when they are enabled in [card settings](/documentation/core-concepts/workspaces#card-settings). Some custom fields will only display with data.
### Communicating Commitment
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. |
### Opportunity Space Best Practices
#### Avoid solutions disguised as outcomes (Binary Outcomes)
A common pitfall is creating "binary outcomes" that are actually solutions in disguise. For example, "Launch the AI Chatbot" is a solution, not an outcome.
This matters because starting with solutions bypasses discovery and prevents finding the best ways to solve customer problems.
> **Pro Tip** 💡: When you catch yourself proposing a solution as an outcome, ask *"Why do we want this?"* to uncover the underlying value you want to provide.
#### Embrace Imperfect Measurement
When you're working in a low data environment you may not have the data you need to even set a measurable outcome.
You don't need perfect metrics to get started:
* Begin with a **directional outcome** like "improve search discovery"
* Start customer conversations and analyze available data (but timebox it)
* Refine your measurement approach as you learn more
This approach works particularly well for new products with limited usage data, legacy systems without proper instrumentation, and novel customer workflows.
#### Know When to Skip Discovery
Not every opportunity requires extensive discovery. Consider skipping or limiting discovery when:
* The solution is mandated (regulatory requirements)
* The problem space is well-understood with extensive prior research
* Making minor improvements to existing features with few assumptions
#### Top-level Opportunities
Top-level Opportunities sit directly under an outcome in your opportunity space. They frame your discovery work and can be broken down into more specific sub-opportunities.
Teams often apply segmentation techniques to these top-level opportunities, creating a structured layer that makes it easier to organize and prioritize customer problems.
**Customer Journey Step**
This approach segments opportunities according to the steps in your customer's journey when using your product or service.
How to implement:
* Map out the key steps in your customer journey from beginning to end
* Create a top-level opportunity for each significant step
* Validate your journey map with actual customer input
**Job (Jobs To Be Done)**
The Jobs To Be Done (JTBD) framework focuses on understanding what "job" customers are trying to accomplish when they use your product.
How to implement:
* Frame top-level opportunities around the core jobs your customers need to get done
* Focus on the progress the customer is trying to make in a particular circumstance
**Actor / Role**
This approach organizes opportunities based on the different roles or personas that interact with your product.
**How to implement**:
* Identify all key stakeholders who engage with your product
* Create top-level opportunities for each distinct role
* Consider both primary users and secondary stakeholders
## Solution Cards
Solutions are actions taken to address an Opportunity. This can be launching a new feature, improving an existing feature, improving documentation, and so on.
**Popular Terms:**
* Solution **(Default in Vistaly)**
* Bet
* Feature
### Communicating Commitment
Once solutions have been ideated, use statuses to communicate when and if the team will implment them. Solutions support the following status:
| Stage | Commitment | Description |
| ----------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Idea** | No/Unknown commitment | Initial concept for addressing an Opportunity. No commitment to implementation has been made. |
| **Not now** | No commitment | Solution evaluated but intentionally deprioritized due to resource constraints, technical limitations, or strategic considerations. |
| **Later** | Committed *(Moderate Confidence)* | Planned for a future timeframe beyond the current planning horizon. Recognized as valuable but with lower immediate priority than Now/Next items. |
| **Next** | Committed | Solution approved with implementation details being finalized. Awaiting resource allocation or developer availability. |
| **Now** | Committed | Solution actively under development. Implementation work is in progress. |
Note: Using "Later" for Solutions is generally discouraged. The "Later" status is more appropriate for Opportunities (problems) where you've committed to solving them but haven't yet fully defined the problem space or solution approach.
## Assumption Cards
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.
## Experiment (Assumption Test) Cards
Experiments provide evidence to de-risk high-risk assumptions. As a result, they save time, money, and energy by preventing investment in a solution that will give little to no return on investment.
***Tip**: Consider running experiments on assumptions with weak evidence AND would run a high risk of project failure if not correctly understood.*
### Example Tests
The goal of assumption tests are to provide a lightweight way to derisk risky assumptions. Here are some common types of tests:
| **Test Type** | Description |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **One Question Survey** | A targeted, single-question instrument designed to validate a specific assumption with users. Provides quick, focused feedback on a narrow hypothesis. |
| **Visual Prototype** | Low or medium-fidelity visual representation of a solution to test user reactions and validate assumptions about usability, desirability, or comprehension. |
| **Research Effort** | Structured investigation involving interviews, contextual inquiry, or usability testing to understand user behaviors, needs, and pain points related to an assumption. |
| **Data Analysis Effort** | Examination of existing user data, metrics, or analytics to validate assumptions based on actual behavior patterns rather than stated preferences. |
| **Painted Door Test** | A technique that presents users with an interface element (button, link, etc.) for a non-existent feature to gauge interest before building the actual feature. |
Note: These test types can be combined or customized based on the specific assumption being tested and the required level of confidence.
### Communicating Status
Once solution assumptions have been identified, use experiment *(assumption test)* statuses to communicate how tests are progressing. Experiments support the following statuses:
| **Stage** | Commitment | Description |
| -------------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Developing** | In preparation | Experiment design is being created or refined before execution. Methods and metrics are being established. |
| **Pending** | Ready for execution | Experiment is fully designed and waiting to be run. All prerequisites are in place. |
| **Running** | In progress | Experiment is currently active and collecting data. Results are not yet available. |
| **Failed** | Completed (invalidated) | Experiment has concluded and results indicate the assumption was incorrect or not supported by evidence. |
| **Passed** | Completed (validated) | Experiment has concluded and results support the original assumption, providing validation. |
## Common Questions
#### Q: How many levels of opportunities should there be?
While there is no hard and fast rule on how many levels of opportunities should be in an opportunity space, we've found that between 2-4 is common.
#### Q: How many opportunities should we have?
Once again, there is no hard and fast rule. At each level you should have more than one. If you have too many straight lines of opportunities, they are typically one opportunity and can be consolidated. Going broad with the opportunity space can help you see a fuller picture
#### Q: Do opportunities change over time?
Yes. The opportunity space is dyanmic, customer needs are constantly changing. This is why it's helpful to connect customer quotes and other insights to opporutnities. When it's time to revisit them, those insight will bring you back to the original context. Use them to determine relevancy. Many times you may also find when looking at quotes that an opportunity is really two or more opportunities.
#### Q: Should we test all of our assumptions?
No. Focus on testing assumptions that are both high-risk (would cause project failure if incorrect) and have weak existing evidence. Testing every assumption would be inefficient and delay progress. Prioritize experiments for assumptions where the cost of being wrong outweighs the cost of running the test.
# The Strategy Space
Source: https://docs.vistaly.com/guides/getting-started/the-strategy-space
The Strategy Space in Vistaly is how you align the whole product organization from \"Where do we want to be in 10 years?\" to \"Where do we want to be in 3 months?\".
## The Cost of Misalignment
Aligning everyone from the C-suite down to individual product managers on the strategy is one of the most important things you can do as a product leader.
**But it's hard.**
And since it's so hard, you've probably experience some of these symptoms yourself:
* **Disconnected Feature Roadmaps**: Your product backlog feels like a grab bag of “cool ideas” rather than a coherent path to solve a user’s pressing problem or drive measurable business outcomes.
* **Perpetual Fire Drills**: The product team experiences whiplash from last minute feature requests to "close a big deal", or “must-have” features from executives.
* **Conflicting Metrics and Goals**: Marketing is aiming to double the number of free-trial signups, but the product team is focusing on existing-user engagement. Meanwhile, the CFO is pushing for cost efficiency. You have multiple priorities that rarely align.
* **Rising Churn or No Growth**: You're shipping new features, but adoption is low. Churn is creeping up. New customer counts are down. Revenue growth has stalled. Board members question your direction. The product org feels blindsided because they never had clarity on the how the business is doing and what levers drive growth in the first place.
In contrast, strong alignment between the leadership team and individual contributors creates a virtuous cycle. Everyone sees the full picture, measures progress consistently, and have productive data-informed discussions.
Everything just feels easier.
**But how do you get there?**
## What You Need To Create Alignment
After working with hundreds of product teams, here are the four components of strategy that everyone needs to have in order to create alignment:
A good product strategy starts with a Vision or Mission for the change your company wants to create in the world.
Clearly communicate who you're building for and what a better future looks like for them.
[↓ Jump to Section](/guides/getting-started/the-strategy-space#1-a-vision-for-a-better-future)
Board members and C-level leaders are focused on financial aspect of the business--things like top-line growth, retention, and gross margin.
Meanwhile, product squads are more concerned with whether customers are getting real, repeatable value from the product—and how easy it is for them to actually tap into that value.
The reality is that business metrics like revenue, retention, and top-line growth are **downstream effects** of customers getting real, repeated value from the product.
**They're the final step of a chain reaction.**
If customers don't set up your product, experience the value of using it for the first time, and continue to get the value by using it routinely, the business will struggle to grow revenue.
A "Value Exchange Model" shows how well your business generates value for your customers, which in turn creates value for the business.
[↓ Jump to Section](/guides/getting-started/the-strategy-space#2-a-value-exchange-model)
If think of a Value Exchange Model as “the rules of the game and the current score” then your near-term focus is “what you want the score to be in the next few months or quarters.”
They're the goals, outcomes, or key results you want to achieve.
Being specific about what areas of the business you're focused on now will give you the courage to say "no" to distractions that fall outside of that focus.
[↓ Jump to Section](/guides/getting-started/the-strategy-space#3-pairing-the-value-exchange-model-with-near-term-focus)
It’s all too common for companies to have this strategic context living in way too many places: slides, spreadsheets, Confluence docs, and BI and product analytics tools.
It's too fragmented for anyone to grok the full picture.
You need a single, shared workspace that connects the dots between the vision, the value exchange model, and the near-term focus.
[↓ Jump to Section](/guides/getting-started/the-strategy-space#4-a-shared-workspace-for-that-connects-the-dots)
The rest of this guide will walk you through how to use Vistaly to create alignment across your product organization.
## 1. A Vision For A Better Future
At their core, vision and mission statements articulate how your product or company will make a difference for customers and the world. It paints a picture of a future state where your users are better off because of your product.
In essence, a good vision/mission captures the why behind your work: the ultimate purpose and impact you aspire to achieve beyond day-to-day features or quarterly targets.
Here are some common pitfalls to avoid when crafting your vision/mission statement:
* **Meaningless Fluff** - One mistake is crafting a vision so broad that it says nothing meaningful. Statements like “be the leading provider of innovative solutions” could mean anything. Use plain language that contains enough specificity to inform decisions.
* **Not Customer-Centric** - Your vision shouldn't be about your revenue goals, market share, or feature set. It should flip the perspective to the customer’s benefit (e.g. “simplify group travel” rather than “grow our platform”).
* **Not Inspiring** - Missions that are dry or purely intellectual often fail to stick. Emotion and boldness are not just nice-to-haves – they are essential. So to make your vision aspirational enough to be a bit scary – if no one rolls their eyes at how ambitious it sounds, maybe it’s not ambitious enough.
### Example
**Acme Health**
> *We will create a world where everyone has access to personalized healthcare that prevents illness before it occurs. We will revolutionize healthcare delivery through AI-powered predictive action that enables proactive, personalized care for all.*
In this example:
* The organization exists to provide **personalized healthcare that knows you** and is able to **prevent illness before it occurs**. This is the foundational purpose of this company, and it positions itself against the status quo.
* They take a stance on how they will achieve this vision through *AI-powered predictive action*. This acts as the guiding policy.
### How To Do This In Vistaly
Create a Vision or Mission card to represent the enduring organizational direction. They are the stable, overarching purpose that guides all work.
**Popular Terms:**
* Vision **(Default in Vistaly)**
* Mission Statement
* Strategic Pillar
By default, the Vision/Mission Card is disabled, this keeps getting started simple. As you begin to use Vistaly across the organization, enable this card type in [Card Settings](/documentation/core-concepts/card-types/overview#adjusting-card-type-language).
## 2. A Value Exchange Model
Most product managers have an intuitive but vague sense that if their team delivers value to customers, the business will benefit.
**That simply doesn't cut it.**
This is why we see so many product squads focused on their little area of the product.
A Value Exchange Model explicitly maps how your business makes money, the value customers get from using your product that *drives* revenue growth, and how easy/difficult it is for customer to realize that value.
It turns gut feeling into a shared, visual representation that everyone can understand.
### Start With An Assessment Of How The Business Is Currently Doing
The reality is that your business must reach or maintain certain financial milestones to keep operating. A good product strategy confronts these realities head-on.
How are lagging business metrics *(like revenue, retention, or profit)* trending? These lagging metrics don't change overnight, but they show your baseline reality, and that reality is the important context that will shape your near-term strategy.
When product strategy doesn't explicitly connect to business performance, product teams often prioritize work that doesn't actually move the needle.
#### Modeling Business Metrics With A KPI Tree
"KPI Trees" go by several names: Driver Tree, Impact Tree, Value Driver Tree,
North Star Metrics (NSM) and more.
The best way to communicate how the business is currently doing is with a [KPI tree](https://www.petra-wille.com/blog/kpi-trees-how-to-bridge-the-gap-between-customer-behavior-product-metrics-and-company-goals). Organizing metrics into a KPI tree reveals the hierarchical structure, and how one metric is influenced by others.
For example, a top-level "Annual Recurring Revenue" KPI might be broken down into:
* Newly Acquired ARR
* Net Retained ARR
Each of these *"second-tier"* metrics can then be further broken down to provide even more granular detail into how they all roll up to the top-level business metric.
Creating a KPI tree is simple in theory, but it's an inherently open-ended excerise. You may have to try a few iterations before landing on the model that serves you best.
The best way to do it is to start with your company's top-level business metric and work your way down.
When building your KPI tree, focus on adding only the metrics that help make
strategic decisions. Too many connections can create confusion rather than
clarity.
#### How To Do This In Vistaly
Use the KPI card type to track business or product metrics that remain relevant over extended periods of time *(they are persistent)*.
Popular terms used to communicate this concept:
* Key Performance Indicator – KPI **(Vistaly Default)**
* Business Metric
* Health Metric
#### Examples
**Annual Recurring Revenue (ARR)\***
* Description: **Total value of recurring revenue normalized to an annual amount**
* Formula: **Monthly Recurring Revenue × 12**
* Source: **Hubspot**
**Trial-to-Paid Conversion Rate\***
* Description: **The percent of trials that purchase a subscription at the end of their trial**
* Formula: **New Paid Subscriptions / Trials Started**
* Source: **Ampltitude**
You can use the [Vistaly API](/documentation/integrations/vistaly-api) to sync
your KPI cards your CRM, BI tools, spreadsheets, or wherever else you keep
your business metrics. This way your workspace always has live, accurate data.
### Layer In The *Drivers* Of Business Metrics
Once you have your business metrics modeled in a KPI tree, the natural next question is "how do we actually drive these metrics?"
To understand this, we need to switch perspectives from what the *business cares about* (inside-out thinking) to what *your customers care about* (outside-in thinking).
#### Inside-out vs Outside-in Thinking
I hate to break it to you, but no one wakes up in the morning and thinks "I really want to buy some enterprise software today."
They just don't.
People buy things to solve problems or meet needs. The thing they're buying might just be one step in a [long chain of steps](https://longform.asmartbear.com/needs-stack/) that gets them to their ultimate goal. But fundamentally, they want to get something done, and they want to do it in the easiest way possible.
**In other words, the business metrics you care about are effectively a measure of whether your product is solving a painful problem for your customers better than their alternatives.**
#### Product Metrics As Proxies For Value
But measuring value customers get from your product **directly** is challenging:
* **Complex Journeys & Multiple Steps:** Your user’s success in reaching their end goal *(like increase sales, improve productivity)* might depend on multiple tools, business processes, or broader market conditions.
* **Data Access:** Capturing “true ROI” may require data from the user’s internal systems *(billing, analytics, etc.)*, which they're unlikely to share with you.
* **Lag Time:** The best indicators of success *(e.g., annual cost savings or increased sales)* might only become clear months or even years down the road.
Instead, we use *proxy* metrics that approximate whether the product is delivering value. For example, you might:
* Measure the time it takes to complete a specific task
* Ask users to rate how easy it was to complete a task
* Track how often users return to the product after their first use
#### Proxy Metrics Don't Have A 1-to-1 Relationship With Business Metrics
There is a difference in how two business metrics relate to one another and how business metrics and product metrics relate to one another.
The "business metrics" portion of your KPI tree will have more of an "algebraic" relationship. You can usually add, multiply, or divide the child KPIs get the value of the parent. E.g.
> **New Customers** x **New Customer ACV** = **New ARR**
But relationship between product metrics and business metrics in your KPI tree is more "correlative". The product metrics are *influencing* the business metric, but they aren't the same thing.
For example, doubling the rate at which new trials complete onboarding will likely improve conversion rate, but it's unlikely to exactly double it *(correlation vs causation)*.
#### Strategies For Picking The Best Proxy Metrics
The best strategy for identifying the right proxy metrics will depend on the level of data sophistication in place - but each strategy contains similar threads.
It comes down to understanding your users, putting yourself in their shoes, and understanding what motivates them in their journey from before they interact with your product, until after they reach their goal.
#### Low Data Sophistication - Describe In Words A Seamless User Journey
If you are pre-product, or if your team hasn't invested in proper instrumentation, you can still use qualitative *directional* descriptions of the key steps that need to be taken in order for a user to realize the value of your product.
To use Vistaly as an example, this would be things like:
* *On the onboarding side*:
* Users are able to easily map their strategy space
* Users invite their team to collaborate
* Users import product feedback and customer interviews to understand the problem space
* *On the retention side*:
* Customers use Vistaly to communicate product decisions with their team
* Customers use Vistaly to consolidate product feedback from sales/support/success teams
* Customer use Vistaly to communicate with leadership about how they're progressing on their goals/OKRs
#### Medium Data Sophistication - Product Metrics That Line Up With The User Journey
Having a baseline ideal user journey is a great start, but the team might have differing opinions on *how accurate* each step in the journey translates to user value when there is no way to measure them.
The next step is to identify actions that are measurable in-product. This will help to quantify how true accurate each of those steps are when it comes to capturing user value.
To continue the Vistaly example, this could look like:
* *On the onboarding side*:
* Users are able to easily map their strategy space
* **Metric: percent of new signups that create 30+ cards**
* Users invite their team to collaborate
* **Metric: percent of accounts with 3+ team members**
* Users import product feedback and customer interviews to understand the problem space
* **Metric: percent of new signups that import 20+ feedback**
* **Metric: percent of new signups that add 5+ interviews**
* *On the retention side*:
* Customers use Vistaly to communicate product decisions with their team
* **Metric: monthly unique Roadmap viewers per paid customer**
* Customers use Vistaly to consolidate product feedback from sales/support/success teams
* **Metric: percent of paid customers that have feedback created by 5+ users**
* Customer use Vistaly to communicate with leadership about how they're progressing on their OKRs
* **Metric: percent of paid customers with 3+ Report viewers per month**
You'll likely need to align with your team on *the best way to measure each step of the process*. Is engaging with "Feature A" the best way to measure if users truly experience the value? "Feature B"? Many both? Do they need to use it 5 times during their trial period? 10? 20?
Until you have [the next level of data sophistication](#high-data-sophistication-linear-regression-and-correlation-analysis), you'll need to rely on your team's collective experience and intuition to make these decisions. These are your data assumptions.
Encourage your team to focus on meaningful actions that correlate to the user’s *real end goal*: e.g., successfully completing a workflow, hitting a key milestone, or finishing a flow that indicates they’ve solved the problem.
“Vanity metrics” like total clicks, time in-app, or raw session counts rarely reflect real value if they don’t tie to a purposeful outcome.
Align usage metrics to the natural use frequency of your product. If your tool
is intended for monthly invoicing, “monthly workflows completed” makes more
sense than "daily active users".
#### High Data Sophistication - Linear Regression And Correlation Analysis
The holy grail of getting alignment on the best measures of customers easily and repeatedly realizing the value of your product is to use linear regression and correlation analysis.
**Correlation** measures the strength and direction of a relationship between two variables, yielding a coefficient between -1 and 1. A value close to 1 indicates a strong positive relationship, -1 a strong negative relationship, and 0 no relationship. This analysis helps identify which features or user actions are associated with key outcomes, such as retention or conversion.
**Linear regression** goes a step further by modeling the relationship between a dependent variable and one or more independent variables--e.g. **Percent of Trialers That Use Feature A** and **Trial Conversion Rate**--allowing for predictions and understanding of how changes in inputs affect outputs. This method is necessary for going from "everyone's best guess" about which leading indicators to track, to forecasting exactly how changes to a given factor will impact business metrics.
While correlation is useful for initial exploration to spot potential relationships, regression analysis provides deeper insights into causality and the magnitude of effects.
For a deeper dive on how to do this at your company, read [this post by Olga
Berezovsky on Lenny's
Newsletter](https://www.lennysnewsletter.com/p/linear-regression-and-correlation-analysis).
### How To Do This In Vistaly
Under your KPI cards for business metrics, you can add KPI cards to track the *proxy product or value metrics* that are the drivers of the business metrics.
## 3. Pairing The Value Exchange Model With Near-term Focus
The Value Exchange Model connects business and product metrics and answers the question *“How are we performing today?”* *How far are we on this journey to achieve our Vision?*
Your Near-term Focus answers the question **"What are the most important areas of this to improve in the next one to two quarters?”**
When a clear near-term focus is missing, product teams easily get distracted by the latest shiny object or last-minute requests from sales or executives.
Many teams use "Goals" to measure how well they are performing on their Near-term focus.
### What Makes For A Good Goal
Ideally, the goals you set for teams have three qualities:
* **Specific & Measurable** - Clearly define exactly what the criteria are for hitting the goal. As Jeff Gothelf puts it, a good goal answers the question ["Who, does what, by how much?"](https://jeffgothelf.com/blog/who-does-what-by-how-much-a-practical-guide-to-customer-centric-okrs/)
* **Time-bound** - Work expands to fill the time alotted. So while you don't have to have a hard cut-off date, a target deadline helps create urgency and focus.
* **Never About Shipping Something** - Goals to "ship" encourages feature factory thinking. You could ship all the new features in the world, but if no one uses them, it doesn't matter.
### Don't overload teams with goals
The point of setting goals is to create alignment and focus. As the saying goes, when everything is a priority, nothing is.
We see this all the time with teams that are starting to adopt OKRs. Product squads will get assigned 5-6 key results and the dilution of focus means no single initiative gets sufficient attention to succeed.
When working on too many goals in parallel, there's a lot of *activity* but not much *progress*. Teams feel busy, but are spending too much time ramping up and down between goals *(context switching)*.
Want to see how much waste goes into introducing too many goals? Check out our
post on ["The Project Learning Tax"](/blog/project-learning-tax)
### Working with Unmeasurable Goals
While measurable goals are ideal, you'll often encounter situations where the metrics you want to track aren't immediately available. This could be because:
* The necessary data collection isn't yet instrumented in your systems
* You're exploring an entirely new product area with no existing measurement framework
* The goal involves qualitative changes that are difficult to quantify
* The real impact might only be visible over a longer timeframe than your planning horizon
In these cases, it's better to move forward with a **directional goal** and NOT focus only on what's easily measurable.
#### Starting With Directional Goals
Directional goals describe the change you want to see, even when precise measurement isn't yet possible. They:
* Create alignment on intent and direction
* Acknowledge measurement challenges transparently
* Include plans for establishing measurement capability
**Example:**
> *Make it easier for customers integrate our product with their other tools:*
>
> * *Initial proxy: Reduction in support tickets related to integrations*
> * *Development of direct measurement: Implement tracking what percent of customers setup 1+ of our integrations*
> * *Long-term goal: Quantify how much time teams save by integrating our product with their other tools*
#### Moving from Directional to Measurable
Here are some general tips for setting up a directional goal and moving to a measurable one.
1. **Define success criteria** - What would "better" look like, even if you can't measure it yet?
2. **Identify proxy metrics** - What existing data might indicate progress?
3. **Create measurement plan** - What instrumentation needs to be built?
4. **Establish baseline** - Once measurement is possible, what's the starting point?
5. **Set targets** - With a baseline established, what's an appropriate goal?
Don't let perfect measurement be the enemy of good strategy. Starting with
directional goals and improving measurement over time is better than avoiding
important areas because they're difficult to measure.
### How To Add a Near-term Strategy In Vistaly
Vistaly supports two card types for communicating a Near-term Strategy. A qualitative card type, and a quantitative card type.
#### With *Qualitative* Cards That Describe The Progress You Want To Make
*Qualitatitive* near-term goal cards, like an Objective, help bridge the gap between long-term vision and actual execution work by *describing in words* the focus areas your team is pursuing in the current time period *(typically quarterly or bi-annually)*.
**Popular Terms:**
* Objective **(Default in Vistaly)**
* Initiative
* Narrative
* Strategy
If you utilize a goal setting framework like OKRs *(Objectives and Key Results)*, the Near-term strategic context in that framework is the Objective component.
Depending on the questions answered during onboarding, qualitative goal cards may be disabled by default. You can [enabled them](/documentation/core-concepts/card-types/overview#adjusting-card-type-language) at any time in Card Settings.
**Considerations when Crafting**
Crafting clear objectives gives teams the necessary context to execute effectively.
* **Specific Challenge Diagnosis**: Understanding of the specific challenge at hand and a compelling "why" teams can rally around.
* **Clear Directional Approach**: Establishes boundaries for acceptable solutions and builds on existing organizational strengths.
* **Focused Action Areas**: Concentrates resources where they'll have maximum impact
##### Example
Compare these examples while referencing the considerations above.
**Weak Objective**
> *Enhance our customer experience platform to drive growth and satisfaction*
**Strong Objective**
> **Challenge:**
> *Mid-market SaaS customers experience a 32% drop-off during onboarding due to integration complexity, which competitors are exploiting with simpler alternatives.*
>
> **Approach:**
> *Design an onboarding flow with a "15-minute to value" guarantee, simplifying the user interface while leveraging our advanced configuration engine.*
#### With *Quantitative* Cards That Measure If You're Making Progress
Outcome (or "Goal") cards measure success for specific objectives within a defined timeframe. They have clear start and end dates with target values to achieve.
Popular terms used to communicate this concept:
* Outcome **(Vistaly Default)**
* Key Result
* Goal
* Rock
## 4. A Shared Workspace For That Connects The Dots
A single workspace *(one that visually connects your business KPIs and product metrics)* is transformative, and supports your teams when solving a few key challenges:
* **Clarity for the Board and Execs**: Leadership wants to see exactly how you plan to move top-level metrics like ARR, net retention, or gross margin. By presenting a Value Exchange Model, they can see that you’re not just delivering outputs at random, but methodically pulling the known product levers that drive business impact.
* **Direction for Product Squads**: Meanwhile, product teams need tangible guidance on which metrics around user value—things like onboarding success or deeper product usage—will actually push those business KPIs up? By focusing on leading indicators that reflect how easily customers can access the product’s value, squads know where to concentrate their effort and can measure progress more quickly than waiting for quarter-end revenue reports.
* **A Shared Language for Alignment**: Without a unifying framework, you’ll spend too much time reconciling top-down demands (“We need another \$5M in ARR this quarter!”) against bottom-up realities (“Our product usage data shows we must improve repeat engagement to reduce churn”). A shared workspace that explicitly links business metrics to user-value metrics helps everyone see how product improvements lead up to broader revenue goals.
* **A Living Document**: Planning cycles shouldn't take weeks (or longer!) When your medium for communicating strategy and progress is a one-off slide deck, never to be used again, you have to start from scratch every time. You need a workspace that already has up-to-date data for this *strategic context* so you can spend less time debating where to apply focus, and more time actually doing the work.
This is exactly what we do at Vistaly. We're a tool that product teams use to connect all of their strategic context and run a continuous discovery process to understand which customer problems they can solve to create the biggest impact.
If this sounds interesting, [request a free trial and onboarding session](https://vistaly.com/request-a-trial).
## Additional Resources
* [KPI Trees & Time-bound Goals](/guides/metrics/kpi-trees)
* [Defining Product Outcomes](https://www.producttalk.org/2022/12/defining-product-outcomes)
* [Outcomes Are Hard](https://www.svpg.com/outcomes-are-hard/)
# Workspace Planning
Source: https://docs.vistaly.com/guides/getting-started/workspace-planning
A workspace is where teams collaborate. This guide will help you figure out how many you need.
By default, new accounts start with one workspace. See [workspaces](/documentation/core-concepts/workspaces) to learn more about creating and managing them.
## Single vs Multiple Workspaces
Vistaly supports the concept of workspaces, and choosing the right setup from the beginning can save you time later. Let's explore the different approaches:
### Single Workspace / Single Team
A single team using Vistaly will almost always need just one workspace. There are some caveats, like creating a structured backlog, or developing in a sandbox or "draft" space away from your main board, but most of the time, one workspace will do the trick.
Best for:
* Teams working on a single product
* Small to mid-sized organizations
* Teams that want to maintain all work in one consolidated view
### Single Workspace / Multiple Teams
Even when you have multiple product teams working in Vistaly, it can be advantageous to keep everything within a single workspace. It helps to see how each team's work comes together to influence the bigger picture.
Many teams initially shy away from putting everything in one workspace because they worry it will result in a "Monster" board. However, with the use of filters, statuses, assignees, archiving, labels, and tree folding, teams can create custom views that make large workspaces feel much smaller, while maintaining the benefits of having everything together.
Best for:
* Multiple teams working on related products
* Organizations that need cross-team visibility
* Scenarios where work items frequently shift between teams
> **Pro Tip** 💡: Filters allow teams to create custom views that focus their work while maintaining the big picture
### Multiple Workspaces / Multiple Teams
There are times when it make sense to completely separate workspaces.
* Teams are working on completely different products in different parts of the business
* Organizations with distinct business units that don't share resources
* Projects with different security or access requirements
Best for:
* Large enterprises with independent business units
* Organizations managing completely separate products
* Teams with different security or compliance requirements
> **Pro Tip** 💡: Start with a single workspace unless you have a specific need for separation. You can always create additional workspaces later and move entire branches from one workspace to another.
## Card Language
In the the [Strategy Space](/guides/getting-started/the-strategy-space) and [Discovery Space](/guides/getting-started/the-discovery-space) guides, there are references to several "card types". Every team use a different terms to describe similar concepts covered in these spaces. Read through guides to understand how each card type is intended to be used. Afterwards, visit the [card types settings page](/core-concepts/card-types/overview#adjusting-card-type-language) to adjust the types to match your organization's internal language.
# KPI Trees – Visualizing Metrics
Source: https://docs.vistaly.com/guides/metrics/kpi-trees
Deep dive into KPI Trees and how to improve metric and goal execution.
This guide is a visual reference for continually improving metrics using KPI Trees.
*Read time: 15 minutes*
***
## Contents
[1. **Goals vs. metrics**](#goals-vs-metrics)
[2. **Visualizing metrics (KPI Trees)**](#visualizing-metrics-kpi-trees)
[3. **Layering goals**](#layering-goals)
[4. **Using KPI Trees to avoid common problems**](#using-kpi-trees-to-avoid-common-problems)
[5. **Popular metric & goal frameworks**](#popular-metric-%26-goal-frameworks)
[6. **Learn More**](#learn-more)
***
## Goals vs. Metrics
The term ***"Metric"*** is used throughout this guide to represent measurements, whereas the term ***"Goal"*** represents the idea of achieving an outcome or target.
### Freezer Example
Let's say we are building a new kind of freezer. A freezer is only helpful if it keeps things cold, so we must measure what temperature it can hold.
*Maximum Freeze Temperature* is the metric to communicate how cold the freezer can hold a temperature.
Let's say we run the test and find it keeps items cold at 50 °F (10 °C). That's not going to be a useful freezer, and we probably should get out of the appliances business – *that, or we need to fix it.*
**Goal**: Achieve a *Maximum Freeze Temperature* of 0 °F (-17.78 °C).
With a goal in place, we now have a feedback loop and method to track progress as we iterate on the design.
The goal also communicates a clear definition of done. Once the goal is reached, there is no need to continue, especially when entering the realm of diminishing returns.
### Persistence vs. Point-in-time
Metrics can persist long after a goal has been reached, while goals tend to only be useful at a specific point-in-time.
If you're looking for a freezer to store medical supplies, you probably want to know if the freezer can maintain a specific temperature.
*Maximum Freeze Temperature* is essential, but you don't need to know how long it took engineers to develop it. The metric has **persistent value**, and the goal is only important at a **point-in-time**.
There are many persistent metrics you can track. Depending on the stage and type of company, they may vary. Here are standard persistent metrics tracked by many companies to measure health, growth, and product/service performance:
* Lifetime Value (LTV)
* Monthly Recurring Revenue (MRR)
* Retention rate
* Conversion rate
***
## Visualizing Metrics (KPI Trees)
Metrics are valuable for understanding how individual parts of a larger system work but can struggle to tell the larger story.
You may have experienced a time when the same dataset was used to tell two completely different stories. The data is not different, but the added context and how it's applied changes the story.
This illustration by Jeff Patton always hits close to home.
Dashboards and spreadsheets are prolific for tracking metrics, but they often do a terrible job with context *(how they are used and why they matter)*. Adding context typically happens in meetings, slack conversations, and presentations. This helps everyone construct mental models for interpreting the metrics.
#### **The problems with mental models**
Everyone has their own mental models, and they don't always line up *(highlighted by Jeff's illustration above)*.
Mental models are also hard to share, creating barriers for new team members. Breaking metrics into smaller parts and visualizing how they fit together takes the mental model of *'how the business works'* and turns it into a physical one. This physical model can be used as a tool to address alignment, focus, and comprehension challenges.
### KPI Trees
A KPI Tree is a tool for visually managing the context surrounding the most essential metrics influencing a service or product. KPI Trees visually represent **how 'things' work** as a model.
One of the earliest versions of a KPI Tree comes from the 1920's DuPont Analysis on visualizing ROI.
Several frameworks have been used in business contexts to visualize how metrics influence one another to create value. *KPI Trees, Driver Trees, North Star Metrics, and Impact maps are a few.*
### Building a KPI Tree
When getting started, I like to begin at the top of the tree *(or as close to the top as possible)*. KPI Trees visually represent **how 'things' work**, so having the top of the tree present is a constant reminder of what is being optimized. Then, I start asking questions to uncover anything that has the potential to influence it. I don't worry about getting everything right in the right places. It's more about getting everything out there first and refining it later. Most of the top-level metrics I see are monetary, growth, or a high-level product engagement metrics.
*Note: If you don't start at the top, that's fine. Asking, **"Why does this metric matter?"** will help expand the tree up when you're ready.*
Here are prompts to help get everything out there and build the first pass of your tree.
To expand the tree down, ask, ***"How does profit grow?"***.
In this example, profit can increase if the number of subscribers increases or if the average subscription cost goes up.
Inverting the question can account for drivers that decrease value. ***"How does profit shrink?"***
*Average Subscription Price*, *Monthly Active Subscription*, and *Operating Costs* are all input metrics to *Profit*.
This process can be repeated at each level to visualize how **inputs influence metrics** and how **other metrics influence inputs**.
### Tracing value
Looking left to right, you can examine each lever for influencing revenue.
And looking right to left, you can understand how something *closer to the edge* can influence the bigger picture.
For example, if we're managing a messaging application like Slack or Teams, we can answer the question: ***"Why does increasing the average number of messages sent per user matter?"***
### Measurement frequency
We've found it helpful to indicate the reporting timeframe of a metric and leave the frequency out of the name. This will avoid confusion when the tree is shared.
Using the previous example, **Monthly Active Subscriptions** turn into **Active Subscriptions**, and the label *measured monthly* is applied. Adding similar labels to each metric will help others follow along.
***
## Layering goals
You may have experienced a time or two when all you are doing is defining, negotiating, and communicating goals rather than delivering value. This is one symptom of not having a shared understanding of **how 'things' work**, leading to spending more time aligning and executing less.
When a team operates from a shared model, it's easier to negotiate where to invest time. When the shared model is visual, they can point to a specific area and skip the whole *'getting on the same page'* step.
If KPI Trees show **how 'things' work** –– goals describe the **next best version** of how 'things' work.
Combining KPI trees & goals can save *(what I'm sure will feel like years)* of your life by providing a clear, agreed-upon starting point that doesn't evaporate each quarter.
Pick an area, set a goal, and go.
The KPI Tree is the starting point – it's persistent. The goals create a point-in-time focus to improve the goal. Everything to meet the goal *(discovery, delivery, experimentation, etc.)* falls under the goal.
***
## Using KPI trees to avoid common problems
### No counter metric – *(Win/Lose)*
Focusing on a goal at all costs can result in negative consequences if you don't look at the bigger picture.
Blockbuster increased their revenue by charging rental late fees, which accounted for 16% of the company's revenue, angered customers *(Reed Hastings being one)*, and even led to a lawsuit.
**Fixing the problem**
Counter metrics help balance short and long-term trade-offs. Blockbuster had an easy lever to pull to increase revenue, but it came at a cost.
> *"For each success metric, come up with a good counter metric that would convince you that you’re not simply plugging one hole with another."*
>
> \~ **Julie Zhuo**, Former Meta VP – Product Design
When setting a goal, ask the question: *"What are we potentially giving up to focus on this goal?"*
* Speed for quality
* Revenue for satisfaction
* Total users for engagement per user
Link *(or add)* counter metrics to the goal in your tree. Use them as guardrails to monitor alongside progress.
### Assigning goals too "high" in the tree – (Lagging metrics)
Attaching a goal to a metric higher in the KPI tree will be harder to influence. High-level business metrics have longer lead times. If you can snap your fingers and increase profit by 50% *without serious negative trade-offs – 👋 Blockbuster*, you can safely stop reading now.
The challenge with goals attached to lagging metrics is that they almost always require research and action from multiple business areas to influence them. Likely, these other parts of the business are not used to working together, and they may even have different goals of their own, competing for time. This is a cross-functional collaboration challenge.
**Fixing the problem**
Individual product trio's goals should be set *down the tree* on the leading metrics that actually drive the up-the-tree business impact.
The further down the tree a goal is applied, the more focused the work and the shorter feedback loops.
Here's how you can model the relationship between lagging business metrics and leading product metrics 👇🏼
### Ship and forget – (No feedback loops)
*"Ship & forget"* is a symptom of delivering *a lot of work* without creating the anticipated value.
**Fixing the problem**
It takes time to see change. When tasks or development tickets are the **only way of tracking "done"**, it's easy to equate shipped work to value added.
Layering goals into the tree creates focus and acts as the benchmark for actual progress. Setting weekly or bi-weekly touchpoints to update or reflect on progress will help determine if prior work requires iteration.
Extending the KPI Tree to include projects or solutions can be a visual reminder of previous work completed when reviewing goals.
**Extra resources:**
*
Escaping the build trap
– *great book on the topic – with tactics.*
*
Scaled Feature Factories
– *post describing the problem and symptoms.*
*
Opportunity Solution Trees
– a visual framework for leveraging product discovery tactics to achieve
outcomes.
### Inability to move the needle – (No correlation)
Setting goals on leading metrics has many benefits, but like most things, it has trade-offs. When improvements to leading metrics do not result in long-term gains, time is wasted.
Let's say you are building an app, and it has a free trial period. You hypothesize that users who take a specific action while in the trial are more likely to pay for the product when the trial ends. You decide to invest in encouraging users to take this action more often.
When spending time improving the engagement metric does not improve conversions, there is no correlation between the work done, and the desired outcome.
**Fixing the problem**
If you have data, correlation analysis can show how connected two metrics are or are not. This post **does not** go into the details of correlation analysis, but if you recognize this as a challenge, check out the linked resources at the end of this section.
Since every relationship between KPIs *is not* causal, annotating the correlation between relationships *(similar to what is done in the image above)* can help determine if and when the model needs to be adjusted.
Aligning expectations on how metrics influence one another is one thing. Aligning expectations on which solutions will maximize impact is another.
> *"**Problem-Solution Fit** - this occurs when you have evidence that customers care about certain jobs, pains, and gains. At this stage you've proved the existence of a problem and have designed a value proposition that addresses your customers' jobs, pains and gains."*
>
>
> Strategyzer – Survival of the fittest
>
Discovery bridges the gaps between goals, customers, and deliverables. It connects the dots between the various opportunities (pains, gains, barriers) to the ideas for addressing them.
Mapping customer pain points as opportunities between the goal and a list of solutions creates a visual map of unmet needs. The expectation is that once they are met, the goal will progress.
Jumping straight from goals to deliverables assumes that the problem space is well understood by you, and everyone else. Visuals are great for identifying gaps.
Delivery can also be a tool for learning. If you track data and avoid falling into the *[ship-and-forget trap](#ship-and-forget-–-no-feedback-loops)*, delivery can reveal significant insights. But **is it the fastest / cheapest method of learning?** That's the million-dollar question, that also happens to be very context-dependent.
Extra resources:
*
Linear Regression and Correlation Analysis
*
Using Google Sheets function to compare datasets
*
Opportunity Solution Trees
– Mapping opportunities
### Constant whiplash – *(Context switching)*
When problems rise to the surface, they often demand attention and pull us away from our current focus. Since there are real costs to context switching, it requires balance and discipline to ensure everything doesn't grind to a halt.
**Fixing the problem**
The tree can be used to evaluate trade-offs. When problems arise, compare the areas of the tree that are negatively impacted to areas positively affected by goals.
As an example, if there are goals in place to improve retention, and someone raises a red flag that new subscribers are currently down. Note it and determine if addressing the problem right now is worth paying the context switching costs.
The same can be done if you're in an environment where opportunities constantly present themselves and compete for attention.
### Competing priorities – *(Too many goals)*
Much ink has been spilled on this topic so this section will focus on how KPI Trees can highlight the pain points and help communicate the problem clearly.
For more on this, see how there are [real costs to context switching](/blog/project-learning-tax) and ramping up on new initiatives.
**Fixing the problem**
Take one team or individual's goals and annotate the tree.
With the tree annotated and the goals sitting directly alongside why they matter, build consensus on where to apply focus. KPI Trees + Goals can make the evaluation of strategic priorities easier.
If you don't have control over assigning goals, you can still do the same exercise and use it to negotiate. Helping your team understand [the costs of context switching](/blog/project-learning-tax) helps build a case to improve focus.
*Less is more. Later in this guide, there are popular metric frameworks that emphasize creating a singular point of focus to maximize impact.*
### Achieving goals that don't feel like wins (Task/Binary Goals)
When goals are either *done* or *not done*, they are tasks. If there is only one way to deliver the goal, it is a deliverable.
This kind of goal setting suffers from the same problems as **["No correlation"](#inability-to-move-the-needle-%E2%80%93-no-correlation)**. If the task-based goals don't deliver value, or they are not the *"right"* solution to the *"right"* problem, the end result is a completed goal but an overall loss in time.
**Fixing the problem**
You have a solution in disguise when you can not use the tree to show multiple ways to address the goal.
Try turning the goal into a solution and connecting it to an actual goal or metric in the tree.
When the real goal is clearly stated, is there is room to expand the problem space and learn more?
When done correctly, this tactic will open doors to other paths to achiving the same goal. Some which may save you time and money.
***
## Popular metric & goal frameworks
There are **a ton** of frameworks and systems for setting goals and mapping metrics.
### Metric frameworks
#### **North Star Metrics (NSM)**
This framework is typically used to capture one metric that communicates the value a product delivers to its customers.
Some well-known examples:
#### One Metric that Matters (OMTM)
OMTM is similar to North Star in that it helps create focus, but with some differences:
* More of a focus on business outcomes *(compared to product value)*
* Shorter length of focus. North Star metrics don't shift. OMTM is designed to shift as you move from the most important metric now to the next most important metric.
One example could be prioritizing *user sign-ups* for a month. Once that's improved, you may realize the *conversion rate* is not great and shift your focus.
Read more
#### **Impact Maps**
*"Impact maps show assumptions and a connection between business goals, impacts on users and stakeholders, and team deliverables."*
*impactmapping.org*
#### **KPI Trees**
If you've read this guide, you're familiar with KPI Trees by now. You may also notice that many of the concepts above can be used together.
While the product North Star continues to be *Messages sent*, the current One Metric That Matters is increasing *New* Subscriptions.
### Goal Frameworks
The following are some popular goal-based frameworks we see customers using. We've analyzed them to help piece together similarities and differences so you can determine how the visual mapping concepts outlined in this guide can apply to each.
#### **OKRs (Objectives & Key Results)**
OKRs are one of the more popular goal-setting tools.
> *"OKRs are an effective goal-setting and leadership tool for communicating what you want to accomplish and what milestones you’ll need to meet in order to accomplish it."*
>
> \~ whatmatters.com
Bringing OKRs and KPI Trees together can look something like this.
#### **NCTs (Narratives, Commitments, and Tasks)**
In many ways, NCTs are similar to OKRs, with opinionated views on how action fits into goal setting.
Bringing NCTs and KPI Trees together can look something like this.
Read more
#### **GIST**
Gist is one part goal, three parts execution.
Read more
#### **Business/Product Outcomes**
If you've read Continuous Discovery Habits or follow ProductTalk's work, you may be familiar with the distinction between business and product outcomes. This distinction can solve some of the challenges mentioned above, like [dealing with lagging metrics and minimizing cross-functional dependencies](#lagging-metrics).
#### **SMART Goals & EOS Rocks**
SMART stands for **S**pecific, **M**easurable, **A**chievable, **R**ealistic, and **T**imely.
EOS stands for **E**ntrepreneurial **O**perating **S**ystem, which uses Rocks, which are SMART goals with parameters.
#### **BHAG Big Hairy Audacious Goal**
BHAG is one big goal that acts as the current singular focus. Similar to [OMTM](#omtm) but with more inspiration. Jim Collins speaking on BHAG
***
## Learn More
KPI Trees have transformed how hundreds of teams visualize relationships between metrics, align on priorities, and make data-driven decisions.
Have questions about implementing KPI Trees in your organization? Need help with a specific challenge? Our team is ready to help. Reach out at [support@vistaly.com](mailto:support@vistaly.com) for personalized guidance.
For additional perspectives on KPI Trees, check out Petra Wille & Shaun Russell's comprehensive guide.
Ready to put these concepts into practice? We created [Vistaly.com](https://vistaly.com) specifically for product and go-to-market teams who need more than flat dashboards. Our visual metric mapping tools help teams see relationships between metrics, align strategies across departments, and make informed decisions faster.
[Request a free trial](https://vistaly.com/request-a-trial) or [schedule a 30-minute demo](https://calendly.com/vistaly/30min) to see how Vistaly can transform your team's approach to metrics.
# Overview
Source: https://docs.vistaly.com/mcp-cookbook/index
Practical recipes for using AI assistants with Vistaly's Model Context Protocol integration
The MCP Cookbook provides step-by-step recipes for leveraging AI assistants like Claude to supercharge your product discovery and strategy work in Vistaly.
New to Vistaly's MCP integration? Start with the [Model Context Protocol setup guide](/documentation/integrations/model-context-protocol) to connect your AI assistant.
## Why This Works
Vistaly structures your product work as a connected graph. Insights link to opportunities. Opportunities link to outcomes. Everything is connected.
AI can walk through that graph and actually have the context it needs to be immediately useful—way different from thousands of transcripts sitting in a folder.
## Recipes
Brainstorm solutions for an opportunity with AI as your collaborator
Go wide across opportunities, deep into evidence, and reorganize your tree with an AI collaborator
Get a 20,000 foot view of your workspace for executive updates and status reports
## Getting Started
Each recipe includes:
* **Context** — When and why to use this recipe
* **Prerequisites** — What you need in your Vistaly workspace
* **The Prompt** — A complete prompt you can copy and paste to run the workflow
* **Tips** — Pro tips for getting better results
Pick a recipe that matches your current challenge and follow along with your own Vistaly data.
The MCP Cookbook is new and we'll be adding more recipes over time. If you discover prompts or workflows that work well for you, we'd love to hear about them at [support@vistaly.com](mailto:support@vistaly.com) — your contributions help the whole community.
# Run an Ideation Session
Source: https://docs.vistaly.com/mcp-cookbook/opportunity-space/ideation
Brainstorm solutions for an opportunity with AI as your collaborator
## Overview
Collaborate with AI to brainstorm solution ideas for an opportunity—starting with your own ideas, then expanding with AI suggestions, and capturing everything in Vistaly.
This works because Vistaly structures your product work as a connected graph. AI can walk through that graph to understand the strategic context before helping you ideate, making its suggestions more relevant and grounded.
## Prerequisites
* Vistaly MCP integration configured ([setup guide](/documentation/integrations/model-context-protocol))
* An opportunity (or other card) you want to ideate on
* Optional: Insights linked to the opportunity for additional context
## The Prompt
Copy and paste this prompt to start the workflow:
```xml theme={null}
Run a collaborative ideation session using the Vistaly MCP service.
## Workflow Purpose
Guide the user through a collaborative ideation session—from understanding the opportunity context to generating and capturing solution ideas.
## Key Definitions
- **Opportunities**: Customer pain-points, needs, or desires. They represent gaps that can be addressed by a product team.
- **Solutions**: Ideas or features that could address an opportunity.
- **Insights**: Evidence from customer research that supports or informs opportunities.
## Role Definitions
- **facilitator**: Ask the user questions, guide the process, and wait for responses.
- **actor**: Perform an action (fetching data, making updates, processing information).
- **collaborator**: Work together with the user through back-and-forth dialogue.
## Terminal Environment
When evaluating the output formats, links should be formatted as markdown when working in a non-terminal based environment. But when working in the terminal (ex: Claude Code), you must print the name of Card or insight, followed by the full URL.
Ask the user for a Vistaly card to run the ideation session on. They can provide:
- A Card ID (e.g., `card_abc123`)
- A Vistaly URL
- The card name or rough text to search for
**Note**: While this workflow works best with an opportunity card, you can start from any card type. If they provide something other than an opportunity, proceed anyway.
Using the Vistaly MCP server, locate the card with the input provided in step 1.
If multiple cards match, present the options for the user to choose from.
Fetch the story context using `getCardContext`:
1. **Ancestors**: Call `getCardContext` with:
- Direction: `ancestors`
- Include insights: `true`
- Include target card: `true`
2. **Descendants**: Call `getCardContext` with:
- Direction: `descendants`
- Max levels: `2`
- Include insights: `false`
- Include target card: `false`
Build a mental map of where this card sits in the hierarchy and what context surrounds it.
Present the story context using OUTPUT_FORMAT step="4".
Show the hierarchy from highest ancestor down to the target card, giving the user a clear picture of the strategic context before ideating.
Ask the user to share any solution ideas they've already been thinking about.
**Important**: Collect their ideas BEFORE you generate any of your own. This ensures their thinking isn't anchored by AI suggestions.
Generate 5 distinct solutions (different from the user's) that could address the opportunity.
Present both lists and engage in back-and-forth discussion to refine these solutions at a high-level before continuing. Don't feel you always need to agree with the user.
**IMPORTANT**: Make sure the solutions are unique and not simple variations of one another.
**NOTE**: If you need more context about specific product details:
- If running in Claude Code, read relevant parts of the codebase
- Use the Vistaly MCP documentation to learn about the existing product
1. Once you've agreed on a final set of solutions, display the ID of the target card with a link for verification
2. Ask the user to confirm before adding
3. Add all agreed solutions as children of the target card using the Vistaly MCP server
**IMPORTANT**: This must be the same card located in step 2.
Generate a summary of the ideation session using OUTPUT_FORMAT step="8".
This should be copyable markdown that can be shared in Slack, docs, or other tools.
**Progress**: Step 4 of 8 - Story Context
## Story Context
## {Card Type}: {Tag}
Labels: {Label(s)}
{Card Name}
## {Card Type}: {Tag}
Labels: {Label(s)}
{Card Name}
[...continue for all ancestor cards...]
## **{Target Card Type}**
**Labels: {Label(s)}**
**{Card Name}**
**Notes:**
- Don't print metric values
- {Tag} is reserved for opportunities: "Top-level" for topmost, "Child" for others
- Labels line only displays if labels exist
- Add space between each card
- Start with highest ancestor, end with target card
- Bold the target card's body text
- Don't print any other explanatory text
**Progress**: Step 6 of 8 - Solution Development
## Solutions
**Your Solutions:**
1. [Solution name] - [brief description]
2. [Solution name] - [brief description]
**My Generated Solutions:**
[continuing numbering from your list]
3. [Solution name] - [brief description]
4. [Solution name] - [brief description]
5. [Solution name] - [brief description]
6. [Solution name] - [brief description]
7. [Solution name] - [brief description]
Which solutions should we refine or move forward with?
**Progress**: Step 7 of 8 - Adding Solutions to Vistaly
## Solutions Ready for Vistaly
**Target Card**: [{card_name}]({vistaly_card_url}) (ID: {card_id})
**Solutions to Add:**
1. [Solution name] - [brief description]
2. [Solution name] - [brief description]
[...]
Should I add these {X} solutions to the card above?
## Ideation Session Summary
**Date**: {Today's Date}
**Target**: [{Card Name}]({vistaly_card_url})
### Context
{1-2 sentence summary of the opportunity/card and its strategic context from ancestors}
### Solutions Generated
**{X} solutions were identified and added to Vistaly:**
1. **{Solution Name}** - {brief description}
2. **{Solution Name}** - {brief description}
[...]
### Next Steps
- Review solutions in Vistaly and add any additional details
- Consider running a solution deep dive on promising solutions
- Prioritize which solutions to explore further
---
*Generated via Vistaly ideation session*
```
## Tips for Success
Always share your own solution ideas before asking for AI suggestions. This prevents anchoring bias and ensures your original thinking is captured.
While you can start from any card, opportunities work best. They have the right context (parent outcomes, linked insights) to generate relevant solutions.
The collaborative step is meant to be a discussion. Challenge suggestions that don't fit, ask for variations, or combine ideas. You're in control.
The final summary is designed to be shareable. Copy it into Slack or your team docs to keep stakeholders informed about ideation progress.
## When to Use This Recipe
* **Starting discovery on an opportunity** - Generate initial solution candidates to explore
* **Expanding your solution space** - Break out of tunnel vision with fresh AI perspectives
* **Team brainstorming sessions** - Use as a structured facilitation guide with your team
* **Capturing ad-hoc ideas** - Turn scattered thoughts into structured solutions in Vistaly
# Evaluate and Improve Your Opportunity Space
Source: https://docs.vistaly.com/mcp-cookbook/opportunity-space/restructuring-ost
Go wide across opportunities, deep into evidence, and reorganize your tree with an AI collaborator
## Overview
Collaborate with AI to restructure your opportunity space—going wide across opportunities, deep into underlying evidence, and reorganizing based on what you're actually hearing from customers.
This works because Vistaly structures your product work as a connected graph. Insights link to opportunities. Opportunities link to outcomes. AI can walk through that graph with the context it needs to be immediately useful.
## Prerequisites
* Vistaly MCP integration configured ([setup guide](/documentation/integrations/model-context-protocol))
* An existing opportunity space with opportunities and insights
* Customer evidence linked to your opportunities
## The Prompt
Copy and paste this prompt to start the workflow:
```xml theme={null}
Evaluate and refine an opportunity space using the Vistaly MCP service.
## Workflow Purpose
Guide the user through exploring and restructuring an opportunity space—a collection of interconnected opportunities that stem from a business or product outcome.
## Key Definitions
- **Opportunities**: Customer pain-points, needs, or desires. They represent gaps that can be addressed by a product team. Solving opportunities connected to outcomes should result in those outcomes improving.
- **Insights**: Evidence from customer research (interviews, feedback, etc.) that supports or informs opportunities.
## Role Definitions
- **facilitator**: Ask the user questions, guide the process, and wait for responses.
- **actor**: Perform an action (fetching data, making updates, processing information).
- **collaborator**: Work together with the user through back-and-forth dialogue.
## Common Issues to Watch For
- **Solutions in disguise**: Opportunities framed as features ("Need a dashboard") instead of problems ("Struggling to track progress")
- **Vertical opportunities**: Parent with single child—often can be merged
- **Obscure or unclear opportunities**: Hard to understand what the actual customer problem is
- **Grammar and spelling issues**: Typos or grammatical errors in opportunity titles
- **Overly broad opportunities**: Should be split into multiple opportunities or broken into its own sub opportunity space
- **Duplicated or overlapping opportunities**: Similar opportunities that should be combined
## NOT Issues
- **Solutions at any level**: Solutions can be siblings to opportunities or nested anywhere—this is valid structure
- **Deep nesting for solutions/assumptions**: Solutions with assumptions underneath is expected and fine
- **Large buckets with many children**: Not inherently a problem—only flag if insights clearly cluster into distinct themes
## Opportunity Depth Guidelines
- **1 level only**: Probably not breaking down problems enough—look for sub-opportunities
- **2-3 levels**: Healthy opportunity structure
- **4-5+ levels of opportunities**: Likely too much artificial structure—consider flattening
Ask the user to share a Card ID, URL, or name for the root of the opportunity space they want to restructure. This is typically an outcome card, but could also be a top-level opportunity.
1. Use `getCardContext` with the provided card ID:
- Direction: `descendants`
- Max levels: 4
- Include target card: true
- Exclude: comments, insights, descriptions (preserve context window)
2. Fetch parent context using `getCardContext`:
- Direction: `ancestors`
- Max levels: 3
3. Build a mental map of the full structure, and internally flag any issues you may want to explore further during full analysis.
Go level-by-level through the opportunity space, pulling insights to evaluate each opportunity.
1. **Level 1**: Call `getCardContext` on the target card with `maxLevels: 1`, `includeInsights: true`, `includeComments: true`. Evaluate the direct children and note their IDs.
2. **Level 2+**: For each opportunity at the current level, call `getCardContext` to fetch their children with insights. In Claude Code, you can make these calls in parallel (multiple tool calls in one message) for faster execution.
3. **For each opportunity**, read the linked insights and evaluate:
- **Framing vs. evidence**: Do the insights actually support this framing? Use customer language from insights to suggest better framing if needed.
- **Specificity**: Is it specific enough to act on, or too vague?
- **Solution in disguise**: Is it really a customer problem, or a feature request?
- **Needs splitting**: Do the insights reveal multiple distinct problems lumped together? Many insights doesn't always mean split—but if insights cluster around different themes, consider splitting into separate opportunities.
- **Structural issues**: Vertical opportunities (single child), overlapping with siblings
- **Spelling or grammar issues**
4. Keep notes on all issues found
5. Progress to the next level until you reach the bottom of the tree
Compile all findings using OUTPUT_FORMAT step="4".
Organize into:
1. **Structural Issues**: Vertical opportunities, duplicates, misplaced cards
2. **Framing Issues**: Solutions in disguise, non-specific, unsupported by evidence
3. **Recommended Changes**: What to merge, reframe, or restructure
After presenting, ask which changes the user wants to proceed with.
1. Confirm the specific changes to make
2. Execute changes ONE AT A TIME:
- Use `updateCard` for title/description changes
- Use `createCard` if splitting an opportunity
- Note: Cannot delete cards—suggest archiving if needed
3. After each change, confirm success before proceeding
4. Present final summary using OUTPUT_FORMAT step="5"
## Findings
**Opportunities Reviewed:** {X}
**Issues Found:** {Y}
### Structural Issues
| Opportunity | Issue | Recommendation |
|-------------|-------|----------------|
| [{Name}]({link}) | Vertical (single child) | Merge with child: "{child name}" |
| [{Name}]({link}) | Overlaps with {other} | Consider merging or differentiating |
| [{Name}]({link}) | Needs splitting | Insights cluster around {X} distinct themes—suggest splitting |
### Framing Issues
| Opportunity | Issue | Current Framing | Suggested Framing |
|-------------|-------|-----------------|-------------------|
| [{Name}]({link}) | Solution in disguise | "Need a dashboard" | "Struggling to track team progress" |
| [{Name}]({link}) | Non-specific | "Want better experience" | "Frustrated by slow load times on mobile" |
| [{Name}]({link}) | Unsupported | "Users hate X" | "Users confused by X" (based on insights) |
| [{Name}]({link}) | Spelling/grammar | "Usres cant find there data" | "Users can't find their data" |
### Summary
- **{X}** opportunities to reframe
- **{Y}** structural changes recommended
- **{Z}** opportunities look good as-is
**Ready to proceed with changes?** Which would you like to tackle first?
## Changes Complete
### Updates Made
1. ✅ **[{Opportunity Name}]({link})**: {What changed}
2. ✅ **[{Opportunity Name}]({link})**: {What changed}
3. ✅ **[{Opportunity Name}]({link})**: {What changed}
### Summary
- **{X}** opportunities reframed
- **{Y}** structural changes made
- **{Z}** cards created/merged
Your opportunity space is now restructured and ready for prioritization.
```
## Common Pitfalls to Watch For
When analyzing opportunities, watch for these common issues:
**What it looks like:** "Users need a dashboard" or "Customers want faster load times"
**The problem:** These are solutions, not opportunities. They skip past the underlying need.
**How to fix:** Ask "why?" — What's the underlying need that a dashboard would solve? Reframe as the customer's actual problem.
**What it looks like:** A parent opportunity with only one child opportunity beneath it.
**The problem:** This often indicates unnecessary abstraction. The parent and child might be saying the same thing at different levels.
**How to fix:** Consider combining them. If they're truly distinct, the parent should have multiple children representing different facets of the problem.
**What it looks like:** "Users want a better experience" or "Customers need it to be easier"
**The problem:** These are too vague to act on. They could apply to almost any customer or product.
**How to fix:** Look at the underlying insights. What specific pain are customers expressing? Use their language to make it concrete.
## Tips for Success
Don't pull all insights across multiple levels at once. Go level-by-level and be selective about when you need the full evidence.
Claude Code's Plan mode is great for the analysis phase. Document your findings before making any changes to the tree.
Always confirm changes one at a time. This keeps you in control and creates a clear record of what was restructured.
As you navigate, keep notes on patterns you see. Share these observations before proposing changes—they often reveal larger restructuring opportunities.
# Generate a Workspace Summary
Source: https://docs.vistaly.com/mcp-cookbook/reporting/workspace-summary
Get a 20,000 foot view of your workspace for executive updates and status reports
## Overview
Generate executive-level summaries of your Vistaly workspace—what's happening, what's prioritized, and what's changed. Perfect for stakeholder updates, leadership reviews, or keeping yourself oriented across a large workspace.
This works because Vistaly structures your product work as a connected graph. AI can walk through that graph, cluster by priorities, and generate a summary that captures the strategic context.
## Prerequisites
* Vistaly MCP integration configured ([setup guide](/documentation/integrations/model-context-protocol))
* An existing workspace with outcomes, opportunities, and solutions
* Cards with statuses set (Now, Next, Later, Done)
## The Prompt
Copy and paste this prompt to start the workflow:
```xml theme={null}
Generate an executive-level summary of a Vistaly workspace using the Vistaly MCP service.
## Workflow Purpose
Create a 20,000 foot view of a workspace—what's being worked on, what's coming up, and what's recently completed. Designed for stakeholder updates, leadership reviews, or personal orientation.
## Key Definitions
- **Outcomes**: Measurable results the product team is trying to achieve
- **Opportunities**: Customer pain-points, needs, or desires that connect to outcomes
- **Solutions**: Ideas or features being built to address opportunities
- **Experiments**: Tests validating assumptions before committing to solutions
## Role Definitions
- **facilitator**: Ask the user questions, guide the process, and wait for responses.
- **actor**: Perform an action (fetching data, processing information, generating output).
- **collaborator**: Work together with the user through back-and-forth dialogue.
## Status Meanings
- **Now**: Actively being worked on
- **Next**: Queued up, coming soon
- **Later**: On the backlog, not yet prioritized
- **Done**: Completed work
## Terminal Environment
- When evaluating the output formats, links should be formatted as markdown when working in a non-termial based enviroment. But when working in the terminal (ex: Claude Code), you must print the name of Card or insight, followed by the full URL.
Ask the user to share a Card ID, URL, or name for the root of the workspace they want summarized. This is typically an outcome or top-level strategic card.
Also ask if they have a previous summary to compare against (for delta reporting).
Traverse the tree **one level at a time**, deciding which branches to explore further. This prevents context overflow on large workspaces.
**1. Fetch Ancestors**
Use `getCardContext` with the provided card ID:
- Direction: `ancestors`
- Max levels: 10
- Include target card: true
- Exclude: insights, comments, descriptions
**2. Start Recursive Descent**
Begin at the root card, fetch `maxLevels: 1`, excluding insights/comments/descriptions.
**3. For Each Card Returned, Evaluate and Decide:**
| Card Type | Status | Action |
|-----------|--------|--------|
| **Objective, KPI, Outcome** | (any) | Always continue down |
| **Opportunity** | Now | Continue down + fetch insights for this card |
| **Opportunity** | Next | Continue down + fetch insights for this card |
| **Opportunity** | Done | Continue down (no insights) |
| **Opportunity** | Identified | Fetch 1 more level for context, then stop |
| **Opportunity** | Later | Fetch 1 more level for context, then stop |
| **Solution** | Now | Continue down + fetch insights |
| **Solution** | Next | Continue down + fetch insights |
| **Solution** | Done | Continue down (no insights) |
| **Assumption, Experiment** | (any) | Record but don't expand further |
**4. Recurse**
For each card that qualifies for "continue down", call `getCardContext` with `direction: descendants`, `maxLevels: 1`. Repeat step 3 until no more qualifying children.
**5. Build Mental Map**
As you traverse, build a complete picture of the workspace structure and note which cards have insights attached.
Group all cards by type and status:
**By Type:**
- **Strategic layer**: Outcomes, KPIs, Objectives
- **Discovery layer**: Opportunities
- **Execution layer**: Solutions, Assumptions, Experiments
**By Status:**
- **Now**: What's actively in focus
- **Next**: What's queued up
- **Later**: What's on the backlog
- **Done**: What's been completed
Count cards in each cluster and note the distribution.
Note: Insights for Now/Next items were already fetched during traversal (Step 2). Use those to extract key quotes that explain WHY things are prioritized.
Create the workspace summary using OUTPUT_FORMAT step="4".
Include:
1. **Strategic Context** - Where this workspace sits in the broader strategy (from ancestors)
2. **Workspace Overview** - High-level composition and distribution
3. **Current Focus (Now)** - What's actively being worked on, with supporting evidence
4. **Coming Up (Next)** - What's queued up
5. **Recently Completed (Done)** - What's shipped
6. **Key Themes** - Patterns or clusters you observed
If the user provided a previous summary:
1. Compare the current state to the previous summary
2. Identify:
- New cards added since last summary
- Cards that moved from Next to Now
- Cards that moved to Done
- Any significant shifts in priority or focus
3. Add a "What's Changed" section to the summary
## Workspace Summary: {Outcome/Card Name}
**Generated**: {Today's Date}
**Scope**: [{Starting Card Name}]({link to card})
---
### Strategic Context
{1-2 sentences on where this workspace sits in the broader product/company strategy, based on ancestor cards}
---
### Overview
| Layer | Count | Now | Next | Later | Done |
|-------|-------|-----|------|-------|------|
| Opportunities | {X} | {X} | {X} | {X} | {X} |
| Solutions | {X} | {X} | {X} | {X} | {X} |
| Experiments | {X} | {X} | {X} | {X} | {X} |
**Total Cards**: {X}
---
### Current Focus (Now)
#### [{Opportunity Name}]({link})
{Brief description of what this opportunity is about}
**Why this matters:**
> "{Key quote from insight}"
**Active work:**
- [{Solution name}]({link}) - {status}
- [{Experiment name}]({link}) - {status}
#### [{Opportunity Name}]({link})
{Repeat for each "Now" opportunity}
---
### Coming Up (Next)
| Card | Type | Notes |
|------|------|-------|
| [{Name}]({link}) | Opportunity | {Brief context if available} |
| [{Name}]({link}) | Solution | Under: {parent opportunity} |
---
### Recently Completed (Done)
| Card | Type | Completed |
|------|------|-----------|
| [{Name}]({link}) | Solution | {Date if available} |
| [{Name}]({link}) | Experiment | {Outcome: passed/failed} |
---
### Key Themes
- **{Theme 1}**: {Brief observation about patterns in the workspace}
- **{Theme 2}**: {Another observation}
---
*Summary covers {X} cards across {Y} levels of hierarchy.*
### What's Changed
**Since**: {Date of previous summary}
**New Work:**
- [{Card name}]({link}) - {Type} added under {parent}
**Priority Shifts:**
- [{Card name}]({link}) moved from Next → Now
**Completed:**
- [{Card name}]({link}) - {Type} marked Done
**Removed/Archived:**
- {Card name} - no longer in workspace
```
## Tips for Success
Choose a starting card that captures the scope you want to summarize. An outcome gives you a focused view; a higher-level objective gives you broader coverage.
Keep your generated summaries so you can use them for delta comparisons. Copy the output to a doc or note for next time.
For very large workspaces, you may want to generate summaries for sub-sections rather than the entire tree.
The output format is designed to be shareable. Copy it into Slack, email, or your team's update channel.
## When to Use This Recipe
* **Weekly/monthly leadership updates** - Quick status on what's in progress
* **Onboarding to a new workspace** - Get oriented on priorities and structure
* **Pre-meeting prep** - Understand the current state before a planning session
* **Tracking progress over time** - Compare summaries to see how work is evolving