Unclassified

24 — Shared Workbench Story

Status: CANONICAL · Commercial OS
Owner: Product Marketing
Last verified: 2026-07-21

Purpose

How to tell the Shared Workbench — the surface where the category's promise becomes visible. The Workspace is the environment; the workbench is where hands touch work.

Definition (verbatim): A role-composed working surface, projected from the Adaptive Spine, where a human and their Twin collaborate on the same live work.

1. The Story

A bench, in a workshop, is where the work actually sits — tools within reach, materials in front of you, and if you share the bench with a colleague, you both see the same piece, touch the same piece, and neither of you narrates the work to the other from another room.

That's the idea, made digital. Your workbench opens on your work: the accounts you own, the focus of the moment, the three beats — what changed, what needs you, what's prepared. It is composed for your role: a CSM's bench carries account health, commitments, meeting prep; a sales bench carries pipeline truth and deal signals; a RevOps bench carries data quality and process state. Same Spine underneath; different bench per role (Projection Engine).

And it is shared — this is the word that carries the category. Your Twin is not in a sidebar narrating; it is at the bench: its notice lands on the account it noticed; its prepared brief sits with the meeting it prepared; its proposal appears where the decision belongs, evidence attached. You work on the same object. That is the difference between collaboration and chat — and no copilot or assistant has it, because they have no bench: only a host app or a transcript.

2. The Interaction Grammar (what a user can always do)

The four controls — the human control grammar (product doctrine, fixed):

Loop	Control	At the bench it means
Observe	Store in Spine	"This fact/commitment/decision matters — keep it, governed."
Orient	Ask Your Twin	"Explain this work from its actual context."
Decide	Assign Your Twin	"Prepare the analysis/draft/plan — bounded, grounded."
Act	Approve Twin's Action	"Execute this reviewable action across my tools."

The Twin's contributions arrive as graded interventions — NOTICE → EXPLAIN → RELATE → PREPARE → SUGGEST → PROPOSE — least interruptive first, silent when nothing is grounded (interaction laws).

3. Boundary Discipline

A workbench is not a dashboard (it's read-write, it acts), not a feed (composed by work context, not recency), not a chat surface (interventions live in the work's semantic slots; a deeper Ask flow opens only when the user asks).
No permanent Twin rail, bubble, or destination competing with the work — doctrine law.
The acceptance test (quote it): "Can the user perform the approved capabilities of their connected work tools from this Workbench, without tool juggling or reconstructing context?" Required answer: yes.

4. Audience Renderings

Audience	One line
Practitioner	"Your morning, pre-assembled: what changed, what needs you, what's already prepared — and a Twin at the bench, not in a tab."
Executive	"Every role gets a bench composed from the same truth — so handoffs, coverage, and reviews stop being reconstruction projects."
Technical	"Role + focus + canonical state + authority + capabilities → composed surface; interventions are placement-aware and evidence-bound."

5. Proof Beats

The three beats on open (no searching, no assembling).
An intervention landing in place — the risk notice on the account card, not in a chat log.
Ask → Assign → Approve on one real work item, end to end, with the audit trail shown.
Role switch: same entity, different bench composition.

KPIs: daily bench opens/seat; interventions acted-on rate (accepted+edited / surfaced); % of connected-tool actions performed from the bench vs. in the tools (75).