23 — Workspace Story
Status: CANONICAL · Commercial OS
Owner: Product Marketing
Last verified: 2026-07-21
Purpose
How to tell the Workspace — the category-carrying concept. The Spine story explains what we own; the Workspace story explains where work now happens.
Definition (verbatim): The single environment where an organization's people and their Twins do their work.
1. The Story
Work 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.
The 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.
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).
2. What the Workspace Is Not (boundary discipline)
| Not | Because |
|---|---|
| Another app beside the stack | It's the environment above the stack; apps become endpoints |
| A portal or launcher | Nothing launches elsewhere; the work happens here |
| A dashboard suite | Workbenches are read-write operational surfaces — "Dashboards show work. Workbenches do work." |
| A chat product with tools | Collaboration is on shared state, not in a transcript |
| A replacement for systems of record | Tools stay; truth is assembled, not migrated |
3. The Composition Rule (why it doesn't become a junk drawer)
Every 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.
4. Audience Renderings
| Audience | One line |
|---|---|
| Practitioner | "All your tabs had a baby, and it's calm: one bench with your accounts, your signals, your prepared work." |
| Executive | "Your teams work in one governed environment instead of thirty apps — and the work compounds instead of scattering." |
| IT | "Tools stay; access is scoped; the workspace composes what each role may see and do, from one policy model." |
| Investor | "The workspace is the demand surface; the Spine is the moat. Own where work happens, and the stack reorganizes around you." |
5. Proof Beats
- Morning open: what changed / what needs you / what's prepared — the three beats live.
- Cross-tool work without leaving: read CRM truth, see support signal, send governed email — zero tab switches.
- Role composition: same account, CS workbench vs. sales workbench — same truth, different bench.
KPIs: % of user's workday inside the workspace (vision metric); tab-switch reduction reported in design-partner interviews; daily workbench opens/seat (75).
Related: 24 Workbench Story · 05 Category Definition · 19 Product Narrative