Workspaces
A Workspace is the bounded area of work that In Parallel tracks — the team, project, program, or account that gets its own Living Execution Plan.
Overview
Every Workspace in In Parallel has one Living Execution Plan, one Execution Memory — the accumulating record of decisions, commitments, and ownership changes — and one place where your team stays aligned over time. Getting the Workspace right means the plan stays relevant and the signals In Parallel captures from meetings are meaningful. Getting it wrong means the plan feels noisy or disconnected from how the work actually runs. Most teams start with one Workspace, prove the value, then add more.
Prerequisites
An In Parallel account with your calendar connected
A clear sense of which team, project, or program you want to track first
Creating a Workspace
1. Open the Managing section
The Managing section in the left nav shows all your Workspaces and lets you switch between them or create new ones. Click Managing to expand it, then click the + icon in the Managing header.
2. Name and describe your Workspace
Click the + icon to open the creation form. The name should match how people already talk about this work. The description is labeled optional, but filling it in directly improves the quality of AI-generated priorities and plan summaries — In Parallel uses it to understand what this Workspace covers.
Fill in the name, add a description of what this Workspace covers, then click Create.
3. Land on your Execution Plan Dashboard
In Parallel creates the Workspace and takes you straight to its dashboard — a default set of Living Execution Plan widgets is configured automatically. You don't need to set up the dashboard manually.
Note: Add at least one goal before your first meeting — even a rough milestone gives In Parallel the context it needs to surface accurate priorities from day one. The dashboard can be customised with additional widgets, but that's covered separately.
Choosing the Right Workspace
Getting the Workspace boundaries right matters more than most other setup decisions. A well-scoped area stays coherent and useful. A poorly scoped one fills with noise.
The quick test
Ask yourself: "What outcomes am I accountable for executing?"
If the answer spans multiple unrelated cadences, owners, or success metrics, you're looking at multiple Workspaces — not one. A good scope has:
Clear ownership — one person accountable for outcomes
A real cadence — a recurring meeting or review rhythm where decisions actually happen
Meaningful decisions — real tradeoffs, priority shifts, and ownership changes occur here
Workspace types
In Parallel can be used to manage many types of Workspaces depending on the user's need. There are no specific Workspaces that can only be used. Here are some examples of the types of Workspaces In Parallel has been used to manage:
Type | Use when... |
Team | Managing a team's ongoing execution — stable membership, steady rhythm |
Project | A defined outcome with a clear start and end |
Program | Multiple projects rolling up to a shared outcome with shared dependencies |
Portfolio | Strategic oversight over multiple initiatives |
Account | External commitments and internal coordination for a specific customer |
Business area | A function running ongoing priorities (RevOps, Finance Ops, etc.) |
Naming your Workspace
Naming seems like a small decision but it affects adoption — people need to recognize the Workspace instantly and connect it to a real meeting or work rhythm.
Good names:
Match how people already talk about the work
Imply execution responsibility, not aspiration
Are easy to say in meetings and updates
Examples: "Platform Migration", "Product Weekly", "Q2 Growth Program", "Revenue Operations", "Customer X Delivery"
Names to avoid:
Vague: "Everything", "Company", "Ops Stuff"
Overly strategic: "Transformation", "Innovation", "Future"
Disconnected from any cadence
If you can't explain the Workspace in one sentence, it's probably too broad.
Workspace hierarchy
Workspaces can be arranged as a parent program with sub-Workspaces nested underneath. A parent usually represents the program or portfolio level ("Growth Projects", "2026 Holiday Peak"), and sub-Workspaces represent the individual initiatives running inside it ("Back-to-School Campaign", "Single-page Checkout"). Each Workspace still has its own Living Execution Plan, goals, meetings, and Findings — the hierarchy links them into a structured rollup, it doesn't merge their data.
How the hierarchy shows up in the UI
The Managing nav on the left lists your Workspaces with a small disclosure arrow next to any parent. Expand a parent to see its sub-Workspaces as indented rows; click a sub-Workspace to switch into it.
The parent's dashboard can host the Program timeline widget, which renders one row per sub-Workspace — a portfolio view showing start/end, owner, and health across the programs underneath.
Sub-Workspaces work the same as any other Workspace. Meetings, goals, and Findings stay local to the sub-Workspace; they don't bubble up automatically. The rollup surfaces are widget-driven, not inheritance.
Setting up parent/sub relationships
Assigning a parent and its sub-Workspaces is a one-time admin change — it isn't currently self-serve. Ask your Customer Success contact to set the relationship up; they can link existing Workspaces in either direction (promote an existing Workspace to a parent, nest an existing Workspace under a parent, or create the full structure in one pass).
Once the hierarchy is in place, it persists — you manage members, meetings, and plans inside each Workspace as normal, and the parent's roll-up widget reflects the change automatically.
Tip: Start flat. Most teams see the most value from one well-scoped Workspace with a clear owner and goal before introducing a parent/sub structure. Add the hierarchy once you have two or more Workspaces whose progress naturally needs to be read side-by-side.
Frequently Asked Questions
How many Workspaces should I create? Start with one — whichever team or initiative you most need to keep aligned. Add more once the first one is working well. There's no hard limit, but each Workspace works best when it has a clear owner, a real meeting cadence, and at least one goal.
Can I rename or edit a Workspace after creating it?
If you want to change the name of a Workspace, please ask your Customer Success contact to help.
What's the difference between a Workspace and a project in my project management tool? A Workspace is about execution reality — the decisions made, priorities shifted, risks surfaced, and ownership established in real meetings. It's not a task list or a project tracker. Think of it as the layer that keeps a team aligned on what matters and why, updated automatically from meetings rather than by manual input.
Can one person own multiple Workspaces? Yes. A team lead might own a Team scope for their group and a Project scope for a specific initiative. The Personal Dashboard aggregates tasks and goals across all your Workspaces, so nothing falls through the gaps.
What if I set up the Workspace incorrectly? Nothing is permanent. Update the name, description, and goals at any time. The history of decisions and meeting captures stays attached to the Workspace regardless of edits.
Related



