{"slug":"business/23-workspace-story","title":"23 — Workspace Story","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/23-workspace-story.mdx","bytes":4630,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Product Marketing\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nHow to tell the Workspace — the category-carrying concept. The Spine story explains what we own; the Workspace story explains where work now happens.\n\n**Definition (verbatim):** _The single environment where an organization's people and their Twins do their work._\n\n---\n\n## 1. The Story\n\nWork used to live in one place — then software unbundled it into a hundred. Every job got an app; every app got a login, a truth, and a tab. The promise was specialization. The price was that _work itself_ — the connected, contextual, decision-making whole of it — stopped living anywhere. People became couriers between the places their work was stored.\n\nThe Workspace is where work moves back together. Not by replacing your tools — they stay, connected — but by giving the _work_ a home above them. Inside the Workspace, each person gets a Shared Workbench composed for their role and current focus; every workbench is projected from the same Spine of truth; every person works beside their Twin; every consequential action passes through governance. One environment. The tools become capabilities. The tabs become history.\n\n**The claim under the story:** people should not work across dozens of disconnected applications. People should work inside one Workspace. That sentence is the category ([05](../02-category-market/05-category-definition.md)).\n\n## 2. What the Workspace Is Not (boundary discipline)\n\n| Not                                 | Because                                                                                        |\n| ----------------------------------- | ---------------------------------------------------------------------------------------------- |\n| Another app beside the stack        | It's the environment _above_ the stack; apps become endpoints                                  |\n| A portal or launcher                | Nothing launches elsewhere; the work happens here                                              |\n| A dashboard suite                   | Workbenches are read-write operational surfaces — \"Dashboards show work. Workbenches do work.\" |\n| A chat product with tools           | Collaboration is on shared state, not in a transcript                                          |\n| A replacement for systems of record | Tools stay; truth is assembled, not migrated                                                   |\n\n## 3. The Composition Rule (why it doesn't become a junk drawer)\n\nEvery surface in the Workspace is composed from: **role + department + active focus + canonical work state + authority + available capabilities** (layer-model doctrine). Nothing appears because a vendor wanted a widget there; everything appears because the person's current work warrants it. This is the answer to \"won't one workspace become another everything-app?\" — composition is governed by work context, not by feature count.\n\n## 4. Audience Renderings\n\n| Audience     | One line                                                                                                                    |\n| ------------ | --------------------------------------------------------------------------------------------------------------------------- |\n| Practitioner | \"All your tabs had a baby, and it's calm: one bench with your accounts, your signals, your prepared work.\"                  |\n| Executive    | \"Your teams work in one governed environment instead of thirty apps — and the work compounds instead of scattering.\"        |\n| IT           | \"Tools stay; access is scoped; the workspace composes what each role may see and do, from one policy model.\"                |\n| Investor     | \"The workspace is the demand surface; the Spine is the moat. Own where work happens, and the stack reorganizes around you.\" |\n\n## 5. Proof Beats\n\n1. Morning open: _what changed / what needs you / what's prepared_ — the three beats live.\n2. Cross-tool work without leaving: read CRM truth, see support signal, send governed email — zero tab switches.\n3. Role composition: same account, CS workbench vs. sales workbench — same truth, different bench.\n\n**KPIs:** % of user's workday inside the workspace (vision metric); tab-switch reduction reported in design-partner interviews; daily workbench opens/seat ([75](../13-operations/75-customer-success-metrics.md)).\n\n---\n\n**Related:** [24 Workbench Story](24-shared-workbench-story.md) · [05 Category Definition](../02-category-market/05-category-definition.md) · [19 Product Narrative](19-product-narrative.md)\n"}