Workspace Planning

By default, new accounts start with one workspace. See 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 and the discovery space sections of this guide, 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 to adjust the types to match your organization’s internal language.